Sap system training pdf

The framing and the static loads are shown in. Figure Significant Features of Model and Proudly developed in the United States of America. October Concrete Frame. Design Manual. Mitesh Surana.

Oral Buyukozturk. Fall This tutorial provides the basic steps of performing a frame analysis using SAP. It is based on the design project example shown below, the complete solution of which is provided as a handout. The SAP Building.

Analysis Program Computers AISC Manual. American Institute of Steel Construction. AISC Seismic. American Institute of Steel Luttrell, Larry D. This manual is therefore expected to be useful for the department in future conduction of training programs on "Structural Analysis and Earthquake. Municipal and other professional engineers, designers, architects Welcome to GAP.

The name was chosen to reflect the aim of the system, which is introduced in this tutorial manual. In this transaction the work processes cannot be managed as in SM50, it is only a monitor view.

Transaction SU56 Using this transaction we can monitor the number of objects that are buffered from individual user authorization roles and profiles. This is only a monitoring tool, no further action can be taken from within this transaction. We can use this to analyze for a particular user, or reset the buffer for the user Transaction SSAA This is a combination of different transaction that are to be executed by a Basis person on a daily , weekly, monthly, on implementation and on upgrade of the system.

On execution with Function key F8 or Choosing the icon. Further each node indicating in Red colour indicates this transaction is not executed today, on execution the Red turns to Green, indicating this action was performed today. But it does not ensure the Basis consultant did a proper review of the results and took any action.

But this acts as a check list which a Production support member is to perform as per the SAP standard guidelines for a proper functioning of SAP System. This one transaction does almost cover the transaction that are discussed in this document separately.

As in Solaris Chemtech we have implemented the Central User administration model, all System and clients cannot perform all these mentioned function using SU Each SAP systems client , and are not included in this model.

The transaction further includes multiple tabs within in which other information is to be maintained as required and some are mandatorily to be maintained. The General information contains, Name of user in 2 parts — Last and First.

On saving the user will be distributed to the respective child systems which were assigned when assigning roles under the Tab - Roles. The user in turn is transmitted to the child systems in the form of IDoc Intermediate Document that can be monitored using the transaction WE02, the status of the IDoc.

Under each node we have further nodes that can be executed with values to restrict the scope of report and analyze report. Transaction SU10 We use this transaction to perform a change, it be either addition or deletion of any common role for few of the User id or change Company address, Parameter, Output device or even delete Users from the system. This transaction can also be effective from System UED and Client for addition or deletion of a user.

Only if the set of Users are to be Locked or Unlocked then it can be done in the respective system and client using this transaction. Transaction PFCG To create a role with a set of authorization to execute a set of transactions, this transaction is used. In the initial screen a name for the role to be created is maintained, we can create a Single role or a composite role basically. Further a role can also be created by copying an existing role as template, import from a file on User PC, import from another system using RFC or make the role as child and is created by deriving from another Role.

When the role is created by deriving from another role, then such roles are known as Derived Role. Mainly there are following kinds of roles; Single Role Derived Role Composite Role A single role is included with a set of transactions; this can also be done by multiple ways like — directly adding Transaction using the button Transaction or Selecting from the SAP Menu, from other role, from area menu, Import from file or Derive from another role as in picture.

After including the transactions and saving, move the Authorizations Tab to maintain other details for the transaction to be effective. As a transaction is made up of a authorization class, authorization objects and activities that complete the values for anyone to execute a transaction. If any of the values is missing or not maintained then the user to whom the role is assigned will not able to transact and complete the transaction.

In the Authorizations tab we maintain authorization and generate profile for the role. In the picture below notice the authorization class is at the end of the each node of the tree. Depending upon the combination of values the role will permit for executing the transaction assigned to, after generating the Role. Within this transaction using the utilities from the menu bar we can switch to other transactions, to generate the roles in mass, adjust text of the role with the Central user administration system and compare the user assigned to roles.

Transaction PFUD In this transaction as referred in the previous transaction, we perform User master comparison for a set of Roles using ranges or list of roles. With the execution of this transaction the users who are assigned with these roles will be compared and updated, thereby effectively included into the buffer of the User authorization. Transaction SU02 With this transaction we maintain the profiles manually for a profile, but this is rarely used unless we need a profile which is not generated via a role.

We enter the profile value to be manually modified and continue, which brings new screen that can be expanded by double clicking the row Here in this above we maintain values to the elements and then activate the profile using the Activate icon button. Transaction SU03 In this we can maintain new authorization class that is to be used as Customer authorization objects for which the authorization objects and elements also to be created and combined to the class to form a authorization check for a z- transaction.

This requires knowledge of data elements, authorization objects and creating Z-transactions which is not in the scope of this document. Transaction RZ20 This is another transaction that gives a tool to perform the system administration that was done using transaction SSAA. In this transaction we have a tree structure that performs a set of transactions and also keeps a track of all the alerts that were captured during the operation of the system.

There are 2 state of status — Current and Open. In the current status it gives information of the current readings from the system and in Open status it gives all the messages and lists error messages in counts, these can be displayed by clicking over the alerts and analysis is done if the alerts are repetitive in nature. A released change request can be further imported into other system as per the configuration in Transport management System.

The change request is released by the person who has created from respective client. Transaction STMS To move a modified program or customizing setting from development to other system, the transport management system is used. Primarily the The TDC will contain the standard file structure under which the all the files are stored and shared across to other system which are integrated to this TDC.

Further in the systems, a Transport route is configured as how the change requests can move from one system to other. Change requests are imported into a system when it is in the buffer of a system where it is required.

This is controlled within the change request as to what is the target system when it was created. Firstly the client where the import is to be performed is entered, where the client dependent objects in the change requests get to the right client.

And Client independent objects will have effect across all clients even though we import to client The Request can be imported in a Synchronous mode or Asynchronous mode. If the Synchronous is used then the session is active till the completion of import and if the session ends or breaks then the import fails. The last tab Options, in the import screen contains certain check box which can be flagged to perform special action in addition to the normal Import og change request.

Transaction RZ10 To maintain a SAP system certain profiles are created which control the starting of system, setting the different parameters for running a SAP System properly as desired. There are normally 3 kinds of profiles — 1. Default profile 2. Start profile 3. Instance profile The Default profile contains those parameters which is applicable to all instances of the SAP system. A Instance profile contains all those parameters that are relevant only to that instance as described above.

Normally a typical profile contains, Administrative data, Basic maintenance and extended maintenance views. Each change in a profile requires a restart of SAP system to get effective. Transaction RZ04 In this transaction we create the different operation modes distributed on an hourly basis of a day.

Using the Operation mode from the menu bar, we can create multiple operation modes like Shift A, Shift B shown in picture. Further for each operation mode we can assign the host, start profile and instance profile. By this way, without requiring to stop and start the SAP system , we can distribute the allocation of work processed between the dialog and background processes in certain period of time.

This feature can also be activated for a particular day only by assigning the Operation mode for a particular day of the year or a range. Transaction SM63 This transaction code is used for managing the operation modes to the 24 hours of a day.

This can be done by selecting a begin time and end time and then assign a particular operation mode as required. The number of users who connected with different logons can be viewed. Find what is the response time for each logon groups Transaction SP11 This transaction is for monitoring the number of Temse objects Temporary Sequential Objects that were created for each job.

These jobs can be print jobs, batch jobs, background jobs. The information gives the number of objects created, storage occupied, existing in which all clients, by user-wise. The information you enter here is essential for drawing up your Business Blueprint. The answers to the questions form part of the Business Blueprint. Sales and Distribution. It is not recommended that you change or enhance this level of the organization structure. Sales area data.

The business process definitions create your Business Blueprint. In case of a local rollout, the Global Solution Package must have been delivered. This means determining who attends, which business processes are discussed, and other applicable topics. To ensure effective meetings, you should send all relevant materials and business process guidelines to the participants prior to the workshops.

This activity deals with determining whether standardization is, or ought to be, one of your objectives. It is organized according to enterprise area. Nonetheless they should be kept in mind and local detailed requirements coming up during this task should be fed back to the core team, especially if deficient areas are detected.

The measures that need to be taken to achieve this depend on the analysis: y High, through Customizing y Medium, through enhancement y Low, own transactions. The number of transactions related to the business process will be displayed on the business process transaction matrix when you choose Business process transactions. You should only make changes with the support of consultants. The objective of this step is to develop a set of roles small enough to allow flexibility in organizational design yet large enough to enable some degree of standardization throughout the company.

Finally a report needs to be generated listing all business processes, transactions and roles. The report should then be distributed to all teams for confirmation. Once the report has been confirmed, no changes should be undertaken without formal change control. The project team can use this substructure to determine the user profiles they require for their specific project. It is possible to define, copy and rename user roles.

You can also display the functions assigned by SAP to user roles for each structure item. The Business Blueprint serves as your conceptual master plan, and becomes a detailed written document. This document shows you the business requirements in detail, and serves as the basis for organization, configuration and, if necessary, development activities.

This contains business processes and scenarios, gaps between business processes and system functions, reports, models, conversions and interfaces. Furthermore, the baseline scope needs to be reviewed at this time. It is critical that quality checks be performed throughout the phase, as tasks are completed. The Business Blueprint ensures that everybody has an accurate understanding of the final scope of the project regarding business processes, organizational structure, and system environment.

You must address issues regarding changes in scope, impact on budget, and resource planning. Although quality checks are performed when specific tasks are completed, it is critical to review them together because individual results from one task may have an adverse impact in another area of the project.

Upon completion of this quality check, signoff is obtained and the project proceeds to the next phase. The objectives are final implementation in the system, an overall test, and the release of the system for production live operation. The project team needs to get the corresponding training in these areas. Security - Authorisation, Administration or Internal Auditor responsible for managing the system security and authorization environment and may be combined with other technical administrative roles.

A review provides an independent and objective management review of the customer implementation project, identifies any risks to the project goals and recommends appropriate corrective actions. Also during the realization phase, end user training and documentation is defined, developed, and finalized. This training shows the many business and technical options available to your company and how to configure the system to meet your company needs.

To define an evaluation and improvement process, communicate this information to the course developers, and develop the course outlines are further tasks involved in this activity. In this activity, you will finalize the training curriculum and job roles, develop a training logistics plan, test the training system, conduct a train-the-trainer, and finalize end user training content and documentation materials.

The Level 2 preparation is also crucial to obtaining the special configuration knowledge for the applications in the Level 3 training. Ideally, the Level3 training should be completed prior to, or early in, the Baseline Configuration.

In this way, the project members should be able to go over the training again, and then be able to apply quickly their newly gained knowledge in Final Configuration. However, initial testing and verification of the test plans should begin earlier in the development or quality assurance systems during phase three.

The Baseline block comprises the priority requirements of the company, ensuring that they can be implemented quickly. Requirements that need programming or enhancements to the SAP system are addressed in separate work packages in the Realization Phase.

To make configuration easier, create two or more cycles. Each cycle, based on the value chains in the enterprise, includes the functions and processes you need. Depending on the scope of implementation, create an appropriate number of cycles cycle 1, cycle 2 through to cycle n. Configure these cycles sequentially.

Only once this is completed can you then configure the business processes in the Baseline configuration and the Final configuration. Supporting documents, which provide the additional detail to actually carry out configuration and testing, are produced using templates accelerators designed for this purpose.

You should use the Project Implementation Guides to plan and organize the necessary Customizing activities for your project. When you set up your Project IMGs or Release projects, keep to the standards for using status indicators, for scheduling, and for documentation, which you defined in the task Define Project Documentation under the work package Project Procedures project Preparation phase.

This is the more common method, whereby consultants manually identify the components of the IMG that must be configured according to the project scope. Specify a project name and description, select the countries and save the Project IMG. If you maintained this information in the Admin Tool, you only need to confirm it here. The Master Lists reflect the definitions defined in the Business Blueprint document. The various worksheets used to control and drive the configuration and confirmation process are derived from those Master Lists.

The Blueprint is the reference source for answering all questions about requirements definition in Phase 3, Realization.