Project 3
Business 270
MW 2pm-315pm
Western Michigan University
Dan Miller
Table
of Contents Pages
Cover Page
Table of Contents
Executive Summary 1
Introduction 2
Menu Paths 3-4
Icons 4-5
Transaction Codes 5
Navigational Issues in SAP 6
Additional Material 7
In-Depth Navigation 7-8
Logical Progression 8
Website Help 8-9
References 10
Team Self-Evaluations 11-12
Executive Summary
The basic idea behind this project was to help our group learn to navigate and use the SAP R/3 program by following the tutorial handout given to us in class and then to evaluate the handout. We found that the handout was very useful to beginners using the program who needed to learn the basics about the SAP R/3 program such as logging in, the navigation of the program, how to use the menu paths, basic program icons, and how to use transaction codes. We also discuss in some detail the navigational issues in the SAP R/3 program, such as menu paths and the use of transaction codes. Then we went to the website http://help.sap.com to look for material that could be added to future project 3 assignments. We added our thoughts on adding more navigational reading, more in-depth features that we felt would be helpful to users of the SAP R/3 program, more logical information that should be used in the progression beyond navigation that we felt would be helpful to users, and the use of the help website http://help.sap.com.
Introduction
The purpose of the ten-page handout is to explain how to login and navigate through the SAP system. The SAP system is beneficial to improving business processes for information technology. The SAP system is used for large-scale computer information systems. Large, complex organizations require billions of dollars for enterprise information software. The use of the SAP system improves performance and new opportunities within organizations to create wealth.
The purpose of the first step in the handout was to explain the login process. We were required to input our user name and password along with the language of choice. After logging in we navigated the menu system and learned about transaction codes. The menu expands into other sub files and categories such as logistics, accounting, human resource, information systems, and office. We focused on logistics, sales and distribution areas. The handout showed in detail how to create your own sales order. Also it explained both the lookup, trace back functions and how to save the order to your favorites. Transaction codes offer another way to navigate the system because every transaction is given a code number. Users are able to type in the code directly without having to go through the menu.
The logging in process begins by going to the start menu and clicking on programs. Next, class applications are selected from the menu and then SAP applications. Third, SAP front end is selected and finally SAP logon. When the logon screen pops up, an idea is asked for which is similar to Bus270G-12 for example and a password that was selected by the user must be entered.
The purpose of the ten-page handout was to introduce us to SAP and provide us with the basic tools for navigating SAP. The handout provides useful information in regards to navigating the system in an efficient way. The handout provides different options such as menu paths and transaction codes for navigating through SAP. The handout provides purpose and explanations for icons such as the back, cancel, execute, and save functions.
Menu Paths
The menu paths tutorial of this program starts out very simple and then goes into great depth through a step by step process. The tutorial starts out identifying and helping the user navigate through the main menu system that appears at the initial screen after the user logs in. The tutorial then shows the user how to create a new sales order by navigating through the menu paths. The tutorial then has the user create a new sales order for later on in the tutorial process. After creating the sales order the tutorial gives the user a straight list of the different menu paths to take to be able to create a new sales order again. This list appears in bold like this: Logistics >Sales and Distribution > Sales> Order> Create. After showing the user the exact list of menu paths to take the tutorial then tells the user that after awhile the tree-structure menu path can get confusing and so to collapse the menu back to its original starting point by clicking the standard menu icon.
The tutorial then shows the user how to add the create sales order menu to the favorites menu so that the user doesn’t have to go through the menu tree to get to their most used items again. To add menu paths to the favorites menu path all that the user has to do is go to the original menu path and drag and drop the path that they want into the favorites menu path. The menu paths portion of the tutorial then shows the user how to rename the menu paths that the user has put in their favorites menu by using the change tool in the favorites toolbar or by clicking Ctrl+Shift+f3 at the same time. To finish out this portion of the tutorial the user is then asked to test their shortcut that they placed in the favorites section to be sure that they followed all of the steps correctly and that their new shortcut works properly.
Icons
There is a section of reading on important Icons in the SAP handout. The icons make SAP navigation quicker and easier for the user. If one does not know the function of a particular icon, just put the mouse pointer over the icon and a description will quickly appear. The icons include Enter, Back, Cancel, Exit, Execute, and Save.
The Enter icon is represented by a check mark and allows a user to go to the next step in a transaction after entering information into the initial screen. The Enter icon gives the same result as using the Enter key. The Back icon is shown as an arrow pointing to the left. It allows a user to exit a transaction, without saving any information. The Cancel icon is represented by an X. Its function is just like the Back or Exit icons. The Exit icon is an arrow pointing up. It allows a user to exit a transaction and typically moves the user closer to the main screen than the Back or Cancel icon. The Execute icon is a clock with a check mark and is used to begin a process that is time consuming. The Save icon is a picture of a floppy disk, which you would click on to save a completed transaction.
Transaction Codes
On most programs there are toolbars for navigation, which contain separate files that include subcategories. The toolbar represents a compacted menu that stores programs and their available options or pathways. Another way to navigate the R/3 system is through transaction codes. Every transaction for the R/3 system is given a transaction code. The codes allow the users to enter these numbers as another means of going directly to a transaction. This option of navigation through the Sap system is a process most use frequently but in due time will be removed completely.
Navigational Issues in SAP
The information in the handout about SAP’s navigational issues gave an overall broad picture of the main components of using SAP. It starts of explaining the logging in process and directions on creating a new password. The navigation process can be difficult at first but the only way of become an efficient user is through exposure to the system itself.
There are two ways of getting to where you want to go. The first are menu paths. Menu paths branch out in a tree like structure with each category and sub-category leading to the entry type desired. Transaction codes may also be used, and require you to enter a code for a specific entry type. Every transaction is given a code number and after entering this code into the command field you will be taken directly to that transaction type.
The handout provides explanations for the different icons and what their functions are. The primary icons used are the back, cancel, exit, execute, and save functions. By just entering a transaction it does not mean that you have saved the transaction. To ensure that your transaction has been saved you must save regularly. Overall the handout provides the primary functions of SAP and their importance and relevance to us. The more that you use the SAP the easier that navigation will come to the user.
Additional Material
We found additional material on navigation using the website http://help.sap.com. There was detailed information on SAP’s purpose, Integration, and Features. The purpose is ultimately to retrieve all the information necessary to perform business functions. Some of SAP’s features include: Caching, Active-X Free Portal, and Navigation iViews. There are also three different types of navigation, including Top-Level, URL, and Object Based.
There is a link to a lot of information on Navigation Hierarchy, which is a structure of navigation nodes. It can be made through a tree, list, or any other structure that can correctly organize the nodes.
Another set of information introduced the new topic of Dynamic Navigation, where Navigation objects can be assigned as context-sensitive dynamic navigation iViews to pages and iViews. Dynamic navigation iViews typically contain interface controls to retrieve data related to the content a user has entered. When an open page does not have dynamic navigation iViews, the Dynamic Navigation area is not displayed in the navigation panel.
In-Depth Navigation
We thought that the navigation portion of the SAP R/3 tutorial could have been enhanced by showing the user how to set their easy access settings so that they can configure their menus to show up the way they wanted them to in the future. By using this feature the user could make it so that only their menu paths located in their favorites menu bar appear. The user could also choose to have their favorites appear at the bottom of the menu paths list or to hide the graphics that show up on the right hand side of the screen. We also thought that the user would be better served by including tips on how to set up SAP Shortcuts so that the user would have direct access to transactions, reports, and system commands. This way they could access certain items directly from their desktop or by storing their shortcuts directly onto their system which would save the user time in navigating through other menus.
Logical Progression
A logical progression beyond Sales Order Processing could be improved technology to make the process run smoother and avoid delays in the transport of goods needed by certain firms, through faster and better communication. More departments within a company such as the marketers and buyers could work closer together to help reach the particular company’s goals in efficiency and customer service, as well as being able to keep desirable products more accessible to clients for faster product delivery . Corporations will definitely be looking to improve on presents methods of ordering to make things more convenient and cost effective for their employees and themselves. A more interactive technology or more user-friendly technology may be the next step for Sales Order Processing.
Website Help
From the online
website http://help.sap.com, under the section called Information Center, we
found interesting facts about SAP Information Design. On this page was a search
would with the look-up option for 4 sub-categories which listing these options:
BBLibrary only, Baseline Packages, Industry Packages, and Cross-Industry
Packages. Also, there was a document that explained the information design
look-up function. We found this interesting because it explained exactly step
by step how to efficiently use this function. An example, the documentation of a
"process" always begins with information on the purpose of the
process, followed by any prerequisites and then the actual process flow. Not
everyone would need to use this option from the online website. However, the
knowledge of it would only benefit future questions when in need of a look-up
function.
References
Course Pack BUS 270 Spring 2005 pgs. 135-149, March 9, 2005
http://help.sap.com,
March 9, 2005
Team Self-Evaluations
Anthony Buck’s Self-Evaluation
From the completion of this assignment I learned how to navigate through the SAP R/3 program. Also upon completing part three of the assignment I know that there is a lot of information about the SAP R/3 program that the tutorial does not go into and that I would have to learn on my own in the future. I also learned why companies would want a program like this to save time on generating reports instead of doing them all by hand. I believe I put in a good effort into completing this project and in learning more about the SAP R/3 program.
In this project I learned the basics of SAP, and how to efficiently use the system. There are many positives to using the SAP system and I have a better understanding for the SAP system. I will be able to apply the new skills in future business because as an accounting major I will probably be using something similar to SAP in my business experiences.
Our team functioned well as a group and we were all able to work as a group and complete our project. We were forced to trust each other in accomplishing the project and it all turned out well. Everyone met on time at the time we allocated and finished our project ahead of time.
In project three we were introduced to SAP R/3 and some of its functions. This is software used for sales orders and is actually quite helpful when used correctly. It makes ordering product easy and keeps confusion to a minimum using technology instead of companies placing phone orders to meet the supply and inventory needs. Learning SAP will definitely help in any future business I may be involved in, especially in the buying department. Learning this probably will not help me anywhere in my personal life, but the skills that our group has developed in this and other projects definitely help when we try to work as a cohesive unit. We worked well together as we usually do on these projects.
Project 3 was not too hard. We had to read a handout in our coursepack and use its information to navigate in SAP. I had never used SAP before so obviously I now know how the program works and what can be done using it. I found it to be an effective and organized way of completing Sales Orders.
My group worked well together and everyone did an equal part in our final report. We had to meet twice to get everything accomplished and we did so. I am happy with the end result of this project.
Nicole Maggio’s
Self-Evaluation
This project was intimidating due to the actual use of the SAP program but that stress was eased from Team Whiskey working together. We knew there was no other way to figure out this program than actually hands-on doing the handout. We worked together through the quirks and confusion of complex steps. We all contributed to the project braking up the ideas of the paper for all of us to reflect on. The ideas were similar but needed to be shared to create the best information in our assignment. No one in the group showed negativity or sarcasm towards completing the project. I believe our team meetings and communication level is very strong within our group, Team Whiskey.