SAP Article migration

Several articles that I recorded when I was learning SAP. My old blog was completely closed and moved here. It may be useful in the future.

SAP Installation
Finally I have finished installing the system. It spent me a whole day!
All things went well during the installation by following the instructions. one notes: when installing the database instance, there's a step to select the "cd kernal" package location. the package is just located in a 40G removable disk with the disk driver "I ". after I chose the disk "I" in the CD browser dialog, the cursor went wating status, then I kept waiting. an hour later I felt something's Wrong and closed the CD browser dialog. it didn't interrupt the installation progress. so I coped the package path derectly into the package location input, and went throug next step without any errors. it just waste me an hour!
When logged on after installation, there's always the illegal memory read & write errors. in some of the operations the error messages in the system status bar was such as "incorrect local time ". I changed my regional settings from China to United States, it seemed no effect. finally after restarting the operating system, the errors disappeared. perhaps it's because of the regional settings, or caused by the adjustment of the system datetime.
Another thing, don't forget to disable the database automatically log archive option. Otherwise the disk space usage may increase very large.

SAP Authorization Concepts
2.1 SAP Authorization Concept
The SAP authorization concept is based upon the logical relationship between a user ID and the range of system authorizations with which it can be associated. the architecture of the authorization system is based upon the utilization of several individuals but related logical components: Profiles, Objects, Fields, and Authorizations. the user ID refers exclusively to profiles. each profile grants a set of specific system access authorizations to user. figure 2 into strates the hierarchical authorization concept in SAP.

2.2 Composite Profiles
Composite profiles refer to the varous employee roles available in the corporation (for instance: Purchasing/logging ing Clerk or Accounts Agent ). as the name suggests, composite profiles may contain in multiple user IDs necessary to perform all the business operations associated with a participant role. A composite profile may encapsulate another composite profile (s ). in practice, a model composite profile shocould be recognized for each possible role in the organization, which may be used to produce hybrid composite profiles. the over-existence of the hybrids can defy the very purpose of composite profiles and they shoshould be created only when specific needs arise.

2.3 User Ids
User ids allow access to SAP applications. each user must have a corresponding profile specifically assigned. in scenarios situations, multiple composite profiles can be assigned to a user ID, depending on the role (s) an individual user is responsible for, in the business processes.

2.4 Authorizations
Authorizations are the key building blocks of SAP security. authorization is the process of assigning values to fields present in authorization objects. in SAP, access to all system functionality is achieved through a complex array of authorizations. sometimes users find that they lack the necessary authorizations to perform a certain function in the system, in which case the message: "You are not authorized... "is displayed at the bottom of the screen.
An authorization process may ask for second associated authorization process which in turn asks for third and so on. For example, the task of paying a vendor invoice may require 10 different authorizations.

SAP Client Copy
The SAP system configuration is complex. During the practice, beginners may change the configuration and data of the IDES system, but cannot restore the system. Therefore, a common method is to create a new Client and Copy configurations and data from an existing Client. In this way, it does not matter if the Client is destroyed during operations under the new Client.
Client Copy procedure
Log on to SAP and use SCC4 to enter the Client management interface.
Click the button in the Red Circle to enter the editing status and confirm the pop-up message prompt box.

Click New Entries to create a Client.
Fill in the information. Note that the Client Role should select T Test, and the next few options should use the default value on the image. The newly created Client is 100.
Save and exit.
Use SAP * and password pass to log on to the new Client. Run T Code SCCL to enter the Client Copy Interface
As shown in the figure above, select SAP_ALL for Selected Profile, and select 800 for both Source Client and Source Client User Masters because I want to Copy data from 800.
Test Run indicates to perform the Test, instead of formally performing the Client Copy operation. You can select this option first. After the Test is complete, remove this option and perform the formal Client Copy operation.
The Schedule as Background Job button indicates that the Client Copy operation is performed in the Background Job. In this way, you can use T Code SCC3 to view the progress of the Client Copy operation in the Background; start Immediately indicates immediate execution on the foreground.
The button next to Start Immediately is used to set how many parallel processes are used to execute this operation and can be modified.
The disk space required by a Client is between MB and MB without business data.
T Code SCCL is Local Client Copy. to Copy the Client from other installation instances, use SCC9 (Remote Client Copy ).
Client Copy takes a long time.

SAP Client Copy Error
There is too much data in IDES 800. to Copy a Client, you need to process more than 27000 tables, which may involve about million data records! Because the current progress is less than 50%, Copied Lines is 26,030,610, and Deleted Lines is 3,407,922. No way, I want to use 800 as the basis, refer to Help Online learning, and I am afraid that this Client will not be able to run.
I ran it at the front-end yesterday and it was not long before. I processed more than 6000 tables. When I had about 10 million data records, I encountered an error. It was generally said that the Oracle rollback segment was not enough space. The details are as follows:
Runtime errors DBIF_RSQL_ SQL _ERROR
Exception CX_SY_OPEN_ SQL _DB
Occurred on 16.05.2006 at 22:52:50
> Short dump has not been completely stored. It is too big.
An SQL error occurred when accessing a table.
What happened?
For this operation, the ORACLE instance needed additional
Storage space in a rollback segment.
The expansion of this rollback segment failed.
What can you do?
You cannot eliminate this error yourself.
Please inform your database administrator.
Make a note of the actions and input which caused the error.
-
To resolve the problem, contact your
SAP system administrator.
With transaction ST22, for dump analysis, you can see and manage
Termination messages and, in particle, save them for longer periods
Time.
Make a note of the actions and input which caused the error.
You can use ST22 to view the dump log, which is not readable in many places and contains too much content. You can roughly find out which table or database instance the error occurs. I don't understand Oracle either, so I can only get a mess and start again.
First, the 3 GB switch of the operating system is enabled and the machine is restarted. Then, all data files and rollback segment file growth of the ides database in Oracle are set to "unlimited ", especially those data files with System and Temp words. Expanded the initial size of the Temp data file, because it seems to be dozens of MB, it feels too small, and it seems to be set to not allow automatic growth, this is probably the problem. Remember to set the initial size of the Temp data file to 10 Gb. Poor hard disk, about 80 GB space, after such a toss, there is no space left. After the Copy operation is complete, the database settings are adjusted back, which can save a lot of space.
Now the Background is running, and SCC3 is used for viewing. The progress is normal. When Client Copy is restarted, it starts from the location where an error occurred yesterday and saves a lot of time.
Now, we have processed 20000 tables, with 7000 remaining tables. It is estimated that there will be no more problems. It is estimated that the financial FI/CO table contains a large amount of data (800 in IDES is the Central FI Syst). Now the table processing speed is very fast.
To commemorate

Note: After Client Copy is complete, all users and passwords in the Target Client are set exactly the same as those in the Source Client. For example, if I Copy 800 to 100, the password of SAP * in the previous 100 is pass. After Copy, the password of SAP * is changed to 800 in 06071992.

SAP Logical System
Unable to save the purchase order today, prompting the Client not to specify the Logical System. Remember that the Logical System was not defined when Client 100 was created.
What is a Logical System? What is the purpose?
'Logical system' is used to identify an individual client in a System, for ALE communication between SAP systems.
What is ALE Converter?
An Application Link Enabling (ALE) converter acts as a bridge between SAP applications and another application. it takes es Intermediate Documents (IDocs) from one or more of SAP applications instances and makes the converted data to that application. it also takes data from an external application, convert it to the appropriate IDoc format, and send it to SAP applications. the communication method between the SAP applications and the ALE Converter must be transactional RFC (tRFC ).
Instructions in the help document:
System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto-> Detail ).
The logical system is relevant in the following SAP areas:
* ALE general: two or more logical systems communicate with one another.
* ALE-ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
* Workflow objects: the logical system in which the object is located is always encoded in an object's key.
When maintaining the logical system, note the following:
* The logical system must be unique company-wide. it must not be used by any other system in the ALE integrated group. in a production system, the logical system must not be changed. if the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
Define Logical System
A Logical System can only be used by one Client. Therefore, when you specify a Logical System for the new Client, you must define a new Logical System.
Use Transaction Code SALE to select the menu shown in the following figure.

Next, click "New Entries", enter the Logical System and Name, and save the settings. Of course, regular companies may have a set of naming rules when defining the Logical System. For example, 000CLNT100 is used. The first three digits are SAP System Number. CLNT stands for the abbreviation of Client, and 100 is the Client Number. Define the Client in IDES, as long as it is not duplicated with the existing.
I don't know why when saving it. The following prompt box is displayed.

I chose Create request. In the following dialog box, I only entered the description. After saving the description, an LZBK900002 Request is generated. OK. The Logical System is defined.

Next, you can select "Assign Client to Logical System" in Figure 1, or use SCC4 to enter the Client maintenance interface and specify a Logical System for the Client you have created.
The importance of Logical System in the System can be seen from the above description. Therefore, do not modify the existing Logical System in general at the beginning of the course, and the Logical System settings of the existing Client (only to maintain those clients created by yourself). Otherwise, System errors may occur.
After the Logical System of Client 100 is maintained, the purchase order can be created successfully.