Presentation on theme: "0 UMN 2011 ERP Terapan SAP BASIS General Concept Session # 3."— Presentation transcript:
0 UMN 2011 ERP Terapan SAP BASIS General Concept Session # 3
SAP BASIS John Natal 2011 / UMN 1 Provides the runtime environment for all SAP applications Optimally embeds the application in the system environment Defines a stable architecture framework for system enhancements Contains the tools for administering the entire system Allows the distribution of resources and system components Provides interfaces for decentralized system parts and external products.
Navigation – Screen Element John Natal 2011 / UMN 2
Navigation – Screen Element John Natal 2011 / UMN 3 Command field: to go to applications directly by entering the transaction code. You can find the transaction code relevant application under System --> Status. Menu bar: depend on which application you are working in. These menus contain cascading menu options. Standard toolbar: The application toolbar shows you which functions are available in the current application. Title bar: The title bar displays your current position and activity in the system. Check boxes: Checkboxes allow you to select several options simultaneously within a group. Radio buttons: Radio buttons allow you to select one option only. Status bar: The status bar displays information on the current system status, for example, warning and error messages. A tab provides a clearer overview of several information screens. Options: You can set your font size, list colors, and so on here.
SAP Easy Access - Standard John Natal 2011 / UMN 4 SAP Easy Access is the standard entry screen displayed after logon. Using the menu path Extras Set start transaction you can select a transaction of your choice to be the default entry screen after logon. You navigate through the system using a compact tree structure that you can adapt to your own specific requirements. Use the menu path Extras Settings to change your view of the tree structure. You can use this to display technical names (transaction codes). You can also create a Favorites list of the transactions, reports, files and Web sites you use most. You can add items to your favorites list using the Favorites menu option or by simply dragging & dropping them with the mouse.
SELECTING FUNCTION John Natal 2011 / UMN 5
Role-Based User Menu John Natal 2011 / UMN 6
Role-Based User Menu A role describes a set of logically linked transactions. These transactions represent the range of functions users typically need at their workstations. Activity groups (user roles) have to be set up using the Profile Generator so that users of the SAP System can work with user-specific or position-related menus. The authorizations for the activities listed in the menus are also assigned to the users using activity groups. With Release 4.6, predefined activity groups (user roles) from all application areas are included in the standard system. Users who have been assigned to an activity group can choose between the user menu and the SAP standard menu. The above screen shows the role -based user menu for the “Accounts Receivable Supervisor” as an example. You can find other roles that are supplied in the standard SAP System with the corresponding activity groups using the Other menu pushbutton in the SAP Easy Access initial screen. John Natal 2011 / UMN 7
Field Help – F1 F4 John Natal 2011 / UMN 8 Use F1 for help on fields, menus, functions and messages. Use F4 for information on what values you can enter.
SAP Online Help John Natal 2011 / UMN 9
System Function – User Profile John Natal 2011 / UMN 10
SAP Data Structure John Natal 2011 / UMN 11
SAP Data Structure R/3 System clients are organizationally independent. Each client has its own data environment with its own master data, transaction data, user master data, and customizing parameters. Users in different clients co-exist in the same R/3 System, but their data is isolated and cannot be accessed from another client. Only users with the necessary authorizations can view or process data in a specific client. This isolation concept is reflected in R/3 table design, both at the application level and in Customizing, which is a customer-specific adaptation of the R/3 System. This adaption is called client-specific customizing. Apart from this, there are also system-wide adjustments (which usually have to be made only once, such as printer settings) that affect all clients of an R/3 System. This adjustment is called cross-client customizing. Client 000 is defined as the SAP standard and the customer cannot change it. This client serves as a copy template for the creation of further clients. The repository is also cross-client. It consists of ABAP reports, menus, dynpros, all dictionary objects (tables, data elements, and domains), CUAs, and so on. Like cross-client customizing, repository objects affect all clients of an R/3 System. John Natal 2011 / UMN 12
R/3 System logon Steps John Natal 2011 / UMN 13
Defining Instance & Application Server John Natal 2011 / UMN 14
Starting an R/3 Instance John Natal 2011 / UMN 15
Before Stopping the R/3 system John Natal 2011 / UMN 16
Stopping the R/3 System John Natal 2011 / UMN 17
R/3 System Administrator The main tasks of a system administrator are to: –Perform all periodic tasks to check system health –Perform tasks as required (such as “Add user”) –Watch the system for error and alert situations All the periodic and occasional tasks of a system administrator can be performed using the System Administration Assistant (transaction SSAA) The System Administration Assistant provides a single point of control for the entire system landscape. John Natal 2011 / UMN 18
Users in R/3 Environment John Natal 2011 / UMN 19