Client Tasks
Client Copies within the Same SAP System
*** SAP’s terms for the sending and receiving clients can be confusing. The “target” client is the client into which data is to be copied. The “source” client is the client which contains the data to be copied. Also, remember that all client copies are destructive and will delete all data before copying in the new data. The only exception is when the SAP_USER profile is used. In this case, only user master data is deleted from the target client before the new user master data is copied. ***
1. Create the target client if necessary. 2. Log on to the target client in the appropriate SAP system. If the target client is new, use “SAP*” for the user and “pass” for the password. 3. Go to transaction SCCL for Local Client Copy. 4. On the Client Copy – Copy a Client screen, use the Selected profile dropdown to select a profile that matches your needs. Use SAP_ALL or SAP_UAPP to copy all data except change documents, SAP_USER to copy only user master data, or one of the other SAP provided client copy profiles. Type the Source client and Source client user masters in the provided boxes. These two boxes should contain the same client number unless the data is to come from one client and the user master data from a different client. Once all information has been provided, click the Schedule as background job button. If you receive a Change documents will not be copied message in the bottom status bar, click the green √ next to the transaction command field at the very top of the screen to continue. 5. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button. 6. On the Verification popup, check that everything is correct and click the Continue button. 7. On the Start Time popup, if you want the client copy job submitted right away, click the Immediate button. To schedule the copy for a later date and\or time, click the Date\Time button. In the Date\Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. If the user is SAP* due to a new client, you may receive a date validation error if you use the date format of MM-DD-YYYY. Try other variations such as DD.MM.YYYY, MM\DD\YYYY, YYYY.MM.DD, YYYY\MM\DD, and YYYY-MM-DD. Click the Save picture-icon. 8. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue. 9. You will receive a client copy confirmation message. You can monitor this copy by using transaction SCC3. You may now leave the SCCL transaction.
Client Copies between Different SAP Systems
*** SAP’s terms for the sending and receiving clients can be confusing. The “target” client is the client into which data is to be copied. The “source” client is the client which contains the data to be copied. Also, remember that all client copies are destructive and will delete all data before copying in the new data. The only exception is when the SAP_USER profile is used. In this case, only user master data is deleted from the target client before the new user master data is copied. ***
1. Create the target client if necessary. 2. Log on to the target client in the appropriate SAP system. If the target client is new, use “SAP*” for the user and “pass” for the password. 3. Go to transaction SCC9 for Remote Client Copy. 4. On the Client Copy – Copy a Client screen, use the Selected profile dropdown to select a profile that matches your needs. Use SAP_ALL or SAP_UAPP to copy all data except change documents, SAP_USER to copy only user master data, or one of the other SAP provided client copy profiles. Since this is a client copy that uses data from a client in another SAP system (or remote client), a Source destination must be provided. This is a RFC connection pointing to a specific client in another SAP system. If there is no RFC connection to the client you wish to copy, you will need to create one. Otherwise, use the dropdown to select the remote source client. To test that your select Source destination RFC connection will work, click the RFC system check button. Once the proper remote source client has been selected, the System name and Source client boxes will fill automatically. Once all information has been provided, click the Schedule as background job button. If you receive a Change documents will not be copied message in the bottom status bar, click the green √ next to the transaction command field at the very top of the screen to continue. 5. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button. 6. On the Verification popup, check that everything is correct and click the Continue button. 7. On the Start Time popup, if you want the client copy job submitted right away, click the Immediate button. To schedule the copy for a later date and\or time, click the Date\Time button. In the Date\Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. If the user is SAP* due to a new client, you may receive a date validation error if you use the date format of MM-DD-YYYY. Try other variations such as DD.MM.YYYY, MM\DD\YYYY, YYYY.MM.DD, YYYY\MM\DD, and YYYY-MM-DD. Click the Save picture-icon. 8. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue. 9. You will receive a client copy confirmation message. You can monitor this copy by using transaction SCC3. You may now leave the SCC9 transaction.
Limiting a Client Copy to Refresh User Master Data
Sometimes you need to retain the data residing in a client but refresh the roles, users, and other security components that have changed in DEV client 100. Since role changes don’t transport across the other clients maintained via Central User Administration, a user master client copy can be used on any client in the SAP landscape.
1. Log on to the appropriate client on the appropriate SAP system. 2. If the user master data is coming from a client within the same SAP system, go to transaction SCCL. If the user master data is to be copied from a client in another SAP system, go to transaction SCC9. 3. On the Client Copy – Copy a Client screen, use the Selected profile dropdown to select profile “SAP_USER”. Type in the same client for both the Source client and Source client user masters. This should be the client that contains the user master data you want to copy. If this is a user master copy that uses data from a client in another SAP system (or remote client), a Source destination must be provided. Once all information has been provided, click the Schedule as background job button. If you receive a Change documents will not be copied message in the bottom status bar, click the green √ next to the transaction command field at the very top of the screen to continue. 4. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button. 5. On the Verification popup, check that everything is correct and click the Continue button. 6. On the Start Time popup, if you want the client copy job submitted right away, click the Immediate button. To schedule the copy for a later date and\or time, click the Date\Time button. In the Date\Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. Click the Save picture-icon. 7. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue. 8. You will receive a client copy confirmation message. You can monitor this copy by using transaction SCC3. You may now leave the SCCL or SCC9 transaction, whichever is appropriate.
1. Log on to any client in the “target” SAP system. 2. Go to transaction SCC3. 3. On the Client Copy\Transport Log Analysis screen, click the All clients button. 4. From the list of Client copy logs, double click on a client to view summary information for all client copies where this client was the target client. Double click on any of these summary lines to see statistics for a particular copy client job. 5. You may now leave the SCC3 transaction.
*** Before adding a new client you should first ask if it will be used in communications with other clients (Central User Administration, source for client copies, etc.) If so, the new client will need to be assigned a Logical System ID that is unique among all the SAP systems in the landscape. It is recommended that all new clients be assigned to a Logical System ID as soon as they are created. ***
1. Log on to any customizable client in the appropriate SAP system. 2. Go to transaction SCC4. 3. On the Display View “Clients”: Overview screen, click the pencil and glasses picture-icon to switch into change mode. 4. On the Display View “Clients”: Overview popup, click the green √ to dismiss the informational message. 5. On the Change View “Clients”: Overview screen, click the New Entries button. 6. On the New Entries: Details of Added Entries screen, fill in Client number and description and the City. Use the Logical system dropdown to assign a logical system ID to the client. Type “USD” in the Std currency box. Select a Client role from the client role dropdown (remember that there can only be one Productive client per SAP system). In the Changes and transports for client-specific objects, Client-independent object changes, Protection: Client copier and comparison tool, and Restrictions when starting CATT and eCATT sections, select the necessary restriction levels from the provided dropdowns. Once all information has been provided, click the Save picture-icon. 7. You will see a Data saved in the status bar at the bottom of the screen. You may now leave the SCC4 transaction.
1. Log on to the client to be deleted. 2. Go to transaction SCC5. 3. On the Delete Client screen, verify that you are deleting the correct client. If you also want the client deleted for T000 (ie the scc4 entry), put a √ in the □ to the left of Delete entry from T000 by clicking the □. Click the Background button. 4. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button. 5. On the Verification popup, check that everything is correct and click the Continue button. 6. On the Start Time popup, if you want the client delete job submitted right away, click the Immediate button. To schedule the delete for a later date and\or time, click the Date\Time button. In the Date\Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. Click the Save picture-icon. 7. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue. 8. You will receive a client copy confirmation message. Don’t panic, it looks like a client copy confirmation and says nothing about this being a delete job. You can monitor this copy by using transaction SCC3. You may now leave the SCC5 transaction.
Restriction Change Levels in a Client
When adding a new client to a SAP system, the information listed in the SCC4 can be confusing. This is a brief explain of the available client restrictions.
Client role:
The category indicates the role of the client in your R/3 system.
Possible roles are:
* Production client * Test client * Training client * Demo client * Customizing client * SAP reference client
This field should be maintained by the customer for Documentary purposes. Release 3.0 also ensures the following:
If there is a productive client in the target system, no client copy (remote copy) which also selects cross-client customizing objects may be imported into the system. If cross-client settings are imported, inconsistencies may occur in all clients.
In a productive client, customizing settings that can be maintained as "current settings" can be excluded from a client lock or transport links; this means current settings (e.g. exchange rates, posting periods) can always be maintained in a productive client without recording changes. SAP is planning to link further effective functionality to this flag, to enable adequate protection of a productive client in a system with further (test) clients.
Other settings for a client:
Change and transports for Client Dependent Objects
Changes without automatic recording – the client can be customized although the system will not generate change requests.
Automatic recoding of changes – the client can be customized and all changes are generated into change requests.
No changes allowed – no modifications can be made to the client – it is protected or locked. This is the usual configuration for a production client where customization should not be performed.
No transports allowed – changes are allowed but cannot be transported.
Client-Independent Object Changes
Changes to repository and client-independent customizing allowed – no restrictions on this client for changes and development.
No changes to client-independent customizing objects - allows for development on repository objects but not client-independent customizing.
No changes to repository objects – lets users perform client-independent customizing but no development or modifications to repository objects.
No changes to repository and client-independent customizing objects – this setting prohibits any client-independent modifications and is common on Production systems.
Creating a Logical System ID to be Assigned to a Client
A logical system gives a client a unique “name” which can be referenced by other clients within the SAP landscape. Once you have created a logical system, use the SCC4 transaction to assign the logical system to a client. Normally, you create the logical system before creating a client so that both start out together. Adding a logical system to a client after the client has been in existence and in use to a long time period could cause referencing problems between that client and the rest of the SAP systems.
1. Log on to any customizable client in the appropriate SAP system. 2. Go to transaction SALE. 3. On the Display IMG screen, expand the navigation tree like so:
Application Link Enabling (ALE) Sending and Receving Systems Logical Systems Define Logical System
4. On the Display IMG screen, click the clock picture-icon to the left of Define Logical System. 5. On the Display IMG popup, click the green √ button to dismiss the informational message. 1. On the Change View “Logical Systems”: Overview screen, click the New Entries button. 2. On the New Entries: Overview of Added Entries screen, fill in the Log. System and Name. The logical system should match the naming convention already in place: LS<SID><Client Number>, such as “LSDEV100” for DEV Client 100. The description should be uniform as well such as “Logical System for DEV Client 100”. Click the Save picture-icon. 3. On the Prompt for Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Click the green √ to continue. 4. You will receive a Data saved message in the status bar at the bottom of the screen. You may now leave the SALE transaction.
Communications Tasks
Creating, Modifying, and Deleting RFC Connections
1. Log on to any client on the appropriate SAP system. 2. Go to transaction SM59. 3. On the Display and maintain RFC destinations screen, click the Create button. 4. On the RFC Destination screen, type in a RFC destination name. This name should contain meaningful information such as the SID of the SAP system and\or any client numbers. Select the Connection type from the connection type dropdown, and type the connection specifics in the Description box. If the connection type is a “3” (another SAP system), fill in the necessary client logon information in the Logon section. Fill in the Language, Client, User, and Password for an existing user in the target RFC SAP system. This user should be a system or communication user (ie RFC_USER or ALEREMOTE), not a dialog user. Once all this information is provided, press Enter. 5. In the Technical settings section of the RFC Destination screen, type in the name or IP address of the Target host. If the target is another SAP system, enter the number of System number (00 for all SAP systems except BW QAS which needs a 01). Press Enter. 6. On the RFC Destination screen, click the Save picture-icon. You will receive a Destination saved message in the status bar at the bottom of the screen. You may now leave the SM59 transaction.
1. Log on to any client on the appropriate SAP system. 2. Go to transaction SM59. 3. On the Display and maintain RFC destinations screen, expand the appropriate RFC destination navigation level and double click the RFC destination to be changed. 4. On the RFC Destination screen, make any necessary changes. Once the information is changed, click the Save picture-icon. 5. You will receive a Destination saved message in the status bar at the bottom of the screen. You may now leave the SM59 transaction.
1. Log on to any client on the appropriate SAP system. 2. Go to transaction SM59. 3. On the Display and maintain RFC destinations screen, expand the appropriate RFC destination navigation level and click the RFC destination to be deleted. Click the Delete button. 4. On the Delete destination popup, click the Yes button. 5. You will not receive a confirmation message. You may now leave the SM59 transaction.
Database Tasks
Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – MS SQL Server
Database statistics refresh jobs should be scheduled to run twice daily on all the SAP systems. But occasionally a manual refresh needs to be done due to table reorganization, index rebuild, etc.
1. Log on to the server using the <sid>adm user ID. 2. Open the MS SQL Server Enterprise Manager. 3. Expand the navigator tree until you see the Management entry. Expand it. 4. Right-click on Database Maintenance Plans and click New Maintenance Plan. 5. Use the wizard to create the job you need. 6. You may now close the Enterprise Manager session and log off the server.
Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – Oracle
1. Log on to the appropriate SAP instance any client. 2. Go to transaction DB13. 3. On the DBA Planning Calender for Oracle Database <SID>: Maintain screen, double-click on a blank line on any day in the future. 4. On the Schedule Action for <Day>. DD.MM.YYYY popup, use the radio button to turn “on” the task you want to do. For each action, you need to fill in the Start Time in military time format, the Period (Weeks) which is how many weeks between running of this job – blank for one time only, 1 for weekly, 2 for bi-weekly, etc. and Calender if you want to use any calendar except the SAP supplied standard Factory calendar.
These are the details for each action:
Whole database offline + redo log or Whole database offline backup or Whole database online + redo log or Whole database online backup Generic tape names for database backup Database backup profile – usually init<SID>.sap Options for ReDo log backup Redo log backup Generic tape names for database backup Options for ReDo log backup Partial database offline backup or Partial database online backup Tablespace names to be included in the back up Generic tape names for database backup Database backup profile – usually init<SID>.sap Check and update optimizer status Tablespace names to be included in the statistics run Adapt next extents Tablespace names for next extents adaption Check database N\A Verify database Tablespace names to be verified Database backup profile – usually init<SID>.sap Cleanup logs N\A
5. You may now leave the DB13 transaction.
Jobs, Job Logs, and the Job Queue
1. Log on to the appropriate SAP instance and client using BATCH_USER. 2. Go to transaction SM36. 3. On the Define Background Job screen, fill in the Job name field with the new job name. Select a Job Class priority of A for High, B for Medium, and C for Low. It is SAP’s recommendation that all client-owned jobs begin with a Z for identification purposes. And most Basis people recommend the next two characters be the initials for the SAP module for which the SAP instance runs. Like ZBC* for a Basis job, and ZHR* for a Human Resources job. Click on the Specify start condition button or press F5. 4. On the Start Time popup, click the Immediate button to start the job right away, or click the Date\Time button to specify a date\time in the future for which the job run. Click “on” the Periodic job radio button and then click the Period values button if you want to schedule to job to run on a periodic basis. Provide the periodic values and click Save back to the main Define Background Job screen. 5. On the main Define Background Job screen, click the Step button. 6. On the Create Step 1 popup, fill in the ABAP program Name and any Variant needed to run the program – you had to have created the variant using BATCH_USER before using it here. Then click Save once more. 7. Back on the Define Background Job screen, check that all the job information is correct and then click the Save button one last time.
Modifying a Released or Scheduled Job
1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job to be changed. In order for a job to be changed, it has to have a status of Schedule or Released so turn those statuses “on” and turn the rest “off”. Click on the Execute button. 4. On the Job Overview screen, click “on” the line containing the job to be changed and then click Job → Change. 5. On the Change Job screen, make your changes and then click Save. If you have more than one occurance of the same job in your list, you must change each job scheduled to run earlier than that job you just changed. Once the job you changed runs, all occurences of the jobs running after that date will be changed as well.
Deleting a Released of Scheduled Job
1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job to be deleted. In order for all occurances of a job to be deleted, all statuses of the job should be checked “on”. And enter an all-encompassing date like 01-01-1990 through 12-31-2010. Click on the Execute button. 4. On the Job Overview screen, click “on” all the perpetent line containing the job(s) to be deleted and then click on the Delete job from database button. 5. On the Delete Scheduled Jobs? popup, confirm the deletion.
1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job you want to view. In order for all occurances of a job to be viewed, all statuses of the job should be checked “on”. Click on the Execute button.
Deleting an Active aka Runaway Job
Opinions on this topic vary so these are good guidelines to use. These are pretty much in the order they should be tried: 1. Kill the session via SM37 or SM04.
1. Log on to the appropriate SAP instance and client. 2. Go to transaction SE38 and type in Program name RSBTCDEL and click on the Execute button. 3. On the Delete batch jobs screen, fill in the filtering information you need. It is suggested that Delete with forced mode be “on”. Click on the Execute button. 4. A status message will appear in the bottom Status Bar as the list of job logs to be deleted is built. Once all the specified job logs have been deleted, a final total of jobs logs cleaned will appear in the bottom Status Bar.
Support Package and Binary Patch Tasks
In order to apply new support packages and kernel patches to a SAP system, several preparation steps are required:
· Checking for new SPAM updates, support packages and kernel patches · Downloading the new SPAM updates, support packages, and kernel patches · Preparing the new SPAM updates, support packages, and kernel patches for application · Applying the new SPAM updates, support packages, and kernel patches · Mass recompiling all programs used in patched components
Be aware that SPAM\SAINT update and support package application occurs within the SAP system using the SPAM transaction. These corrections are changes to ABAP program code and must be handled in a special way by SAP. Kernel patches, on the other hand, are fixes to SAP executables found on the SAP server. Kernel patches must be applied when the SAP instance is down.
Please refer to the Check for New SPAM Updates, Support Packages and Kernel
Checking for New SPAM Updates, Support Packages and Kernel Patches
To check if SAP has released any new software fixes for your release of SAP, you need to know your current support package and kernel release levels.
The patching process consists of:
- finding you current patch levels - finding what patches you should be applying - downloading the patches - unCARing the patches - loading the patches into the patching EPS queue - applying the patches
Find your Current SPAM Update and Support Package Level
Method One:
1. Log on to your SAP instance, any client. 2. On any SAP screen, click System → Status… 3. On the System: Status popup, click the Component Information button. 4. On the System: Component Information popup, you will see the support package level for each component installed in your current SAP instance.
Method Two:
1. Log on your SAP instance, any client. 2. Go to transaction SPAM. 3. On the Support Package Manager screen, turn “on” the radion button beside the Imported Support Packages in the Directory section of the screen, and then click Display button. 4. On the OCS Package Directory: Imported Packages screen, you will see a list of all SAP Support Packages imported into your current SAP instance.
Find your Current Kernel Patch Level
Method One:
1. Log on to your SAP instance, any client. 2. Go to transaction SM51. 3. On the SAP Servers screen, click on the server for which you need the information and then click on the Release Notes button. 4. On the SAP Release Information from Server screen, look down the SAP R/3 Kernel information section until you find Kernel Patch number. To the right, you will find the current patch level of your current SAP instance.
Method Two:
1. Log on to the SAP instance sever. 2. Open a DOS-window and use a Screen Buffer Size of 9999. 3. At the DOS prompt, type:
disp+work –v¬
and press ENTER. 4. Scroll back up the listing to where you entered the command in step c. 5. Scroll down the listing untill you find a line beginning patch number. To the right is the patch number for the SAP instance hosted on this server.
Find the Most Current SAP Support Packages
It should be noted here that sometimes an older SAP may run on a newer SAP Basis level. For example, CRM 4.0 has a Basis level of a 6.20 instance but runs on a 6.40 kernel. So make sure that the kernel patches you download match the SAP R/3 Kernel located via SM51.
1. Log on to the SAP Marketplace using an OSS ID with Administration rights – http:\\service.sap.com\patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for CRM Basis expand as follows:
Support Packages and Patches My Company’s Application Components SAP ERP SAP ERP 2004 Entry by Component SAP ECC Server SAP BASIS 6.40
3. Scroll down the Download screen until you find your current package level. Any support packages after your current level will need to be applied to your SAP System. 4. You may now leave the SAP Marketplace.
Find the Most Current SAP SPAM Update
1. Log on to the SAP Marketplace using an OSS ID with Administration rights – http:\\service.sap.com\patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for SPAM\SAINT for CRM 6.20 expand as follows:
Support Packages and Patches My Company’s Application Components SAP SPAM\SAINT UPDATE SPAM\SAINT UPDATE 6.40 SPAM\SAINT UPDATE 6.40
3. Click the Download tab of the SPAM\SAINT UPDATE screen. Find the SPAM\SAINT Update – Version XXX value. If this SPAM version is higher than you current SPAM version, you will need to download and apply the latest SPAM update. 4. You may leave the SAP Marketplace.
Find the Most Current SAP Kernel Patches
1. Log on to the SAP Marketplace using an OSS ID with Administration rights – http:\\service.sap.com\patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for CRM 4.0 expand as follows:
Support Packages and Patches My Company’s Application Components SAP ERP SAP ERP 2004 Entry by Component SAP ECC Server SAP KERNEL 6.40 32-BIT UNICODE ORACLE & #DB independent - OR - MS SQL SERVER & #DB independent
3. Scroll down the Download screen until under the File Name column you find SAPEXEDB*.SAR files. Unless SAP has instructer you to use a different kernel, the most recent SAPEXEDB*.SAR is the one you need to download. You may leave the SAP Marketplace. 4. Now go to the @Database independent section in the same list as ORACLE was displayed. Scroll down the page until you find the SAPEXE*.SAR that matches the same number as the SAPEXEDB*.SAR you found in the previous step. These two files will give you a complete kernel replace. 5. You may leave the SAP Marketplace.
1. Log on to the SAP Marketplace using an OSS ID with Administration rights – http:\\service.sap.com\patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for SPAM\SAINT for CRM 6.20 expand as follows:
Support Packages and Patches My Company’s Application Components SAP SPAM\SAINT UPDATE SPAM\SAINT UPDATE 6.40 SPAM\SAINT UPDATE 6.40
3. To download a SPAM\SAINT update, click on the SPAM\SAINT Update Title hyperlink. Click the Download button. On the File Download popup, click the Save button. On the Save As popup, select a location to store the SPAM\SAINT update and click the Save button. Alternatively, you may add the patch to your SAP Download Manager and download all patches in one batch group. 4. Once you have downloaded your SPAM\SAINT updates, you may leave the SAP Marketplace.
1. Log on to the SAP Marketplace using an OSS ID with Administration rights – http:\\service.sap.com\patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new patches for CRM Basis expand as follows:
Support Packages and Patches My Company’s Application Components SAP ERP SAP ERP 2004 Entry by Component SAP ECC Server SAP BASIS 6.40
3. To download a support package, click on the package Title hyperlink. Click the Download button. On the File Download popup, click the Save button. On the Save As popup, select a location to store the support package and click the Save button. Alternatively, you may add the patch to your SAP Download Manager and download all patches in one batch group. 4. Once you have downloaded as many support packages as you need to apply, you may leave the SAP Marketplace.
1. Log on to the SAP Marketplace using an OSS ID with Administration rights – http:\\service.sap.com\patches. 2. In the navigator tree on the right-hand side of the My Application Components screen. For example, to find new kernel patches for CRM 4.0 expand as follows:
Support Packages and Patches My Company’s Application Components SAP ERP SAP ERP 2004 Entry by Component SAP ECC Server SAP KERNEL 6.40 32-BIT UNICODE ORACLE & #DB independent - OR - MS SQL SERVER & #DB independent
3. To download a kernel patch, click on the SAPEXEDB_<version>.SAR hyperlink. Click the Download button. On the File Download popup, click the Save button. On the Save As popup, select a location to store the kernel patch and click the Save button. Alternatively, you may add the patch to your SAP Download Manager and download all patches in one batch group. 4. Now backup a step and instead of clicking ORACLE, click #Database independent. The full path would look like this:
Support Packages and Patches My Company’s Application Components SAP ERP SAP ERP 2004 Entry by Component SAP ECC Server SAP KERNEL 6.40 32-BIT UNICODE ORACLE & #DB independent - OR - MS SQL SERVER & #DB independent
5. This produces a list of database independent kernel patches. Scroll down the Download screen until under the File Name column you find SAPEXE_<version>.SAR. Use the same instructions in step 5 to download the patch. Make sure that the version number of your database independent files matches the version number of your MS SQL Server dependent file. 6. Once you have downloaded the kernel patch, you may leave the SAP Marketplace.
Download Other SAP Binary Patches
Unlike SPAM\SAINT updates, support packages, and kernel patches, the storage location for other SAP binary patches can be either SAP Marketplace or sapserv1. SAP Marketplace is the normal respository but if you can’t find your patch there, go look on sapserv1.
***Due to the shutdown of the sapserv1x servers in April, this section has been discontinued. Everything should now to accessible via SAP Marketplace.***
Prepare a SPAM\SAINT Update or Support Package for Application
Once you have downloaded your SPAM\SAINT Update and\or support package(s), they must be moved to the appropriate transport directory and uncompressed. For convenience sake, I always move a copy of sapcar.exe from the \usr\sap\<SID>\SYS\exe\run directory to the c:\windows\system32 directory.
1. For a SAP instance, move the downloaded K*.?AR file to the \usr\sap\trans\tmp directory on the SAP Transport Domain Server which is normally the DEV server of a SAP “Flavor”. 2. Log on to the appropriate server as <sid>adm. 3. Type the following:
cd \usr\sap\trans ¬ sapcar -xvf “tmp\*.?AR” ¬
This will unCAR all CAR and SAR files in the \usr\sap\trans\tmp directory to the \usr\sap\trans\EPS\in. 4. Log off the server. 5. Log on client 000 of the appropriate SAP system. 6. Go to transaction SPAM. 7. From the menu bar of the Support Package Manager screen, click Support Package → Load Packages → From application server. 8. On the SPAM: Confirm upload popup, click the green √ picture-icon. The progress of the support package loads will show in the status bar at the bottom of the screen. 9. Scroll down the SPAM: Uploading Packages from the file system screen to make sure your SPAM\SAINT update is listed. Use the Go Back icon to return to the previous screen. 10. You may now leave the SPAM transaction.
Prepare a Kernel Patch for Application
Kernel patches must be applied on the SAP server. The SAP instance must be down before a kernel patch can be applied.
1. Logon the server to be patched as <sid>adm. 2. The downloaded SAPEXE*.SAR and SAPEXEDB.SAR files must be uncompressed using SAPCAR.EXE. You can place the SAPEXE*.SAR files in any directory and use the sapcar –xvf “*.?AR” to unCAR the files. 3. You may now leave the server.
Prepare other SAP Binary Patches for Application
Use the same procedure as Preparing a Kernel Patch for Application.
Application of SPAM\SAINT Updates Before you apply the most current SPAM\SAINT, please pull the OSS Note 484219 - Known problems with transaction SAINT in Basis Release 6.20 or for whatever version you are using and review any problems you may have adding the SPAM\SAINT patch.
Once you have loaded the latest SPAM\SAINT update into your support Package manager buffer, you need to apply the update to your SAP system.
1. Log on client 000 of the appropriate SAP system. 2. Go to the SPAM transaction. 3. From the menu bar of the Support Package Manager screen, click Support Package → Import SPAM\SAINT update. Click the green √ picture-icon to continue. 4. The progress of the SPAM\SAINT update application will be displayed in the status bar at the bottom of the screen. These messages look very similar to the messages generated during a change request transport. 5. When the Restart SPAM popup appears, click the green √ picture-icon to leave the SPAM transaction. 6. Go to the SPAM transaction. You may notice programs compiling in the status bar at the bottom of the screen. This is normal. 7. Once you are again on the Support Package Manager screen, verify that the SPAM status in the Status section of the screen contains a green light. 8. You may now leave the SPAM transaction.
Application of SAP Support Packages
Before applying any support packages to your SAP system, release all “repair” change requests to prevent error messages due to locked resources. Repairs are usually advanced corrections obtained from SAP Notes that are eventually accumulated into support packages. So the same objects “repaired” in the advanced corrections will be “repaired” during the application of the support package. Releasing the repair change requests allows the support package to overlay the temporary advanced correction “fix”.Before you apply the most current SPAM\SAINT, please pull the OSS Note 782140 - OCS: Known problems with Support Packages in Basis Rel.6.20 or for whatever version you are using and review any problems you may have adding the SPAM\SAINT patch.
Once you have loaded the latest support packages into your support Package manager buffer, you need to apply the packages to your SAP system.
1. Log on client 000 of the appropriate SAP system using a adminitrator user ID that is not DDIC or SAP*. 2. Go to the SPAM transaction. 3. On the Support Package Manager screen, click the Display\Define button to build your import queue. On the Component Selection popup, click on the Comp. ID having support packages you want to install. The component order support packages should be applied is SAP_BASIS, SAP_ABA, SAP_APPL, and PI. 4. A list of all application support packages for the selected component will appear in the Define Queue popup. Select the support packages you want to apply. See SAP Note 782140 for information on restrictions to grouping support packages into queues. The Package ID with the green √ to the left is the highest support package to be placed in the queue. All lower number support packages for this component will be applied as well. Click the green √ picture-icon to confirm the queue. 5. From the menu bar of the Support Package Manager screen, click Support Package → Import queue. 6. On the SPAM: Import Queue popup, read the displayed information and then click the green √ picture-icon to continue. 7. The progress of the support package application will be displayed in the status bar at the bottom of the screen. These messages look very similar to the messages generated during a change request transport. 8. When the Imported successfully Information popup displays, click the green √ picture-icon to continue. 9. On the Support Package Manager screen, verify that the SPAM status in the Status section of the screen contains a yellow light and the Next action value is Confirm queue. To confirm that your support packages applied completely, click the green √ picture-icon. A Support Package queue was confirmed message will appear in the status bar at the bottom of the screen. 10. You are ready to build another support package queue, or if you have applied all the necessary support packages, you may now leave the SPAM transaction.
Application of SAP Kernel Patches
*** It is recommended that the \usr\sap\<SID>\SYS\exe\run directory be copied to \usr\sap\<SID>\SYS\exe\backup_run before replacing the kernel ***
1. Log on to the appropriate server as <sid>adm. 2. Double check that the SAP instance, SAPOSCOL, and SAP<SID>_00 services are stopped. 3. To apply the new kernel patch to a R/3 instance, copy the new files into usr\sap\<SID>\SYS\exe\run directory. If prompted for overwrites, say yes to all. 4. After the successful completion of the kernel patch, you may bring the instance back up and log off the server.
Application of other SAP Binary Patches
Use the same procedure as Application of SAP Kernel Patches.
Other SAP Issues
SAP System Response Troubleshooting
1. What has changed since the performance is poor?
2. Any signs of general problems in the System Log - SM21?
3. Places to look:
4. If only few transactions are affected by the performance problem, you should additionally note the following points:
1. Check whether modifications were made in the affected or related transactions. 2. ST03: Display the corresponding performance records. 3. SE30: Carry out a runtime analysis for the affected transactions. 4. ST05: If the database times are high, you should generate an SQL trace of the affected transactions to find out whether the database access is carried out in a useful way.
5. Look for tables that have experienced unusual monthly growth.
1. DB02 → Space Statistics button 2. Press Enter on the Tables and Indexes popup 3. History → All objects off\on 4. Click the Months button 5. Click on the first number under the Rows – Chg\Month header and click the Sort button. 6. The sorted results shows the top tables when it comes to rows changes per month. These tables are your “database hogs”.
6. What is considered “normal” response time?
Performance Standards:
Response time -- 1 second (dialog), < 1 second (update) CPU time -- approx 40% of average response time Wait time -- < 1% of average response time Load time -- < 10% of average response time DB request time -- approx 40% of average response time
Database Standards:
Direct reads -- < 10 ms Sequential reads-- < 40 ms Changes -- < 25 ms
High Value Indications:
DB request time –- Database or index problems Load time -- Buffer problems Wait time -- Not enough work processes Locked tasks Long running transactions
SAP System Start Up Troubleshooting
Whether you are trying to start a brand new SAP instance, or an old one, there are some very specific places to look for information.
If this is a brand new SAP instance, and the installation completed 100% successfully, you know that the instance itself must be viable. If your installaion was never able to complete due to the instance not being able to start up, the issue is probably due to lack of resources. Use the sapinst directory to search the installation logs and find your problem. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. If you have a test searching tool, look for “error” in all files with the suffix “.log”.
If your SAP instance has been up and running fine for a good while, then something has probably changed that makes it not come up.
· have you changed any instance paramters? · did you do a kernel replacement for some reason? · have there been SAP Support Packages applied that might necessitate a kernel replacement? · have there been OS patches? · is the database archiver stuck or hosed? · has a crucial directory run out of space? · has a semaphore or ipc segment gotten stuck from a previous run? · is your memory so fragmented that it can’t get enough primary space to start the instance? · has someone changes the directory privileges?
Go to the \usr\sap\<SID>\DVEBMGS00\work directory and do sort the files by date/timestamp order for ease of viewing. The most useful information can be found in the dev_wx, dev_ms, dev_disp, dev_rfcx, and stderrx files.
If all else fails, zip the contains of the \usr\sap\<SID>\DVEBMGS00\work directory, open a problem with SAP, and attach the zipped file to it. Also provide them with the answers to the above questions as well as your current hardware and database platforms, patch level for SAP support packages, kernel, and the OS, and anything else you might think useful.
The Delicate Art of SAP Note Search
How often have you seen a posted message saying "I have searched through SAP Notes and can find nothing related to this matter."? And how often have you gone to SAP Marketplace and done a search yourself and found a hit? If we only had a had a nickle...
If a user seems to be experiencing SAPGui errors, several things need to be checked:
· Is the operating system on the user’s workstation patched to the level recommended by SAP? · Is the user using a version of SAPGui that is too old for his workstation? · Is the user using a version of SAPGui that is not certified for his operating system? · Is the user’s workstation having resource problems? · Is the user’s workstation connected to the LAN? · Can a different user reproduce the same error on the same workstation? · Are there any SAPGui patches that have not been applied?
Most SAPGui problems can be solved by either a) deleting and reinstalling SAPGui on the workstation, or b) deleting and installing a newer version of SAPGui.
Make sure that these lines were added to the services file on the user’s workstation:
After you have successfully configured your SAPGui, add these three lines to the bottom of your \Windows\system32\drivers\etc\services file:
sapdp00 3200\tcp sapmsR3I 3600\tcp #
If you have SAP Instances using System Numbers other than 00, you will have to add their equivalents to the services file as well. Also, check if you are having connection problems due to firewall restrictions. And, be sure that your Insert Key is set so that you can type your password in properly – you can delete whatever is in the password field in order to enter your password.
If you have never tested connectivity to a SAP instance on the workstation having the connection problem, first you need to make sure that the workstation can connect to the SAP server in some non-SAPGui way. Let’s say your user us trying to connect to System ID (SID) DEV, System Number 00, and IP address 10.1.10.11. Open a DOS-Windows and type this:
telnet 10.1.10.11 3200¬
For information regarding operating system, resource, and hardware requirements for running SAPGui, see SAP Note 26417 - SAP GUI Resources: Hardware and software.
Central User Administration is Not Transferring Change from the CUA Parent Client
If CUA stops sending changes from DEV to QAS or PRD, something in the RFC setup has changed. Either the password or the user type for RFC_USER was changed, or the SM59 RFC connection to was changed and is no longer working.
Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring. Look for the user you tried to transport but could not. You might see “You are not authorized to change users in group” or “No authorization for group users in role”. This does not mean that YOU are not authorized, it means that the RFC_USER doing the ALE communication between the SAP systems is not authorized.
First, reset the RFC_USER password in DEV, QAS, and PRD. And make sure that the user type is Communication and not dialog. Now go to sm59 and do remote logins using the QAS RFC connections. If they work (ie nothing seems to happen after you click the remote logon button) everything should now be fixed. If you get a logon screen for QAS, change the password in the sm59 screen to the same password you changed RFC_USER to in DEV and QAS.
Retry your user change. If it still doesn’t go to QAS, maybe the QAS system is hosed and down.
See also http://sites.google.com/site/saparchives/Home-SAP-BASIS http://sites.google.com/site/saparchives/sap-basis-transactions http://sites.google.com/site/saparchives/Home-SAP-BASIS/SAP-BASIS--unknown-sap-tricks http://sites.google.com/site/saparchives/SAP-BASIS-everything-about-sap-clients http://sites.google.com/site/saparchives/frequently-used-procedures http://sites.google.com/site/saparchives/SAP-BASIS-BASICS http://sites.google.com/site/saparchives/SAP-BASIS-what-is-asap http://sites.google.com/site/saparchives/SAP-BASIS-configuration http://sites.google.com/site/saparchives/SAP-basis-operation---unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-2---unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-1---windows http://sites.google.com/site/saparchives/SAP-basis-operation-2---windows http://sites.google.com/site/saparchives/SAP-basis-operation-3---windows http://sites.google.com/site/saparchives/SAP-basis-interview-questions http://sites.google.com/site/saparchives/sap-training-courses-ecc-60 http://sites.google.com/site/saparchives/sap-basis-refference-steps-1 http://sites.google.com/site/saparchives/SAP-basis-transactions
Important SAP Marketplace Links
Inbox http:\\service.sap.com\inbox Read messages from SAP to you Installation Guides http:\\service.sap.com\instguides Download SAP product installation guides License Keys http:\\service.sap.com\licensekey Request New Permanent License Key Messages to SAP http:\\service.sap.com\message Open problems with SAP QuickLinks Page http:\\service.sap.com\quicklinks An index of SAP links Oracle DBA Page http:\\service.sap.com\dbaora Page for Oracle DBA Material OSS Notes http:\\service.sap.com\notes Search the SAP Notes Database Patches http:\\service.sap.com\patches Download SAP software patches Remote Connection http:\\service.sap.com\remoteconnection Learn about the OSS connection and order it from SAP Service Connection http:\\service.sap.com\serviceconnection Open a Service Connection for SAP to access your SAP landscape Software Distribution http:\\service.sap.com\swdc Download new images of Installation CDs & DVDs SSCR http:\\service.sap.com\sscr Register Developers and Changes made against SAP objects User Administration http:\\service.sap.com\user-admin Add\Change OSS ID user information
SAP BASIS - INDIA |
SAP BASIS Tutorial 3 - Windows |