1) Execute Transaction Code SA38/ SE38.
2) Write the report name RSBDCOS0
3) Execute the Report
4) Type any OS Level Command and do work from GUI
Friday, July 3, 2009
Execution of OS Level command from SAPGUI
Step by Step Procedure to Execution of OS Level command from SAPGUI
1) Execute Transaction Code SA38/ SE38.
2) Write the report name RSBDCOS0
3) Execute the Report
4) Type any OS Level Command and do work from GUI
1) Execute Transaction Code SA38/ SE38.
2) Write the report name RSBDCOS0
3) Execute the Report
4) Type any OS Level Command and do work from GUI
How to Clear SCOT Error from Production Server
How to Clear SCOT error form Production Server
1) Execute SCOT transaction
2) Go to Utilities
3) Overview of Send orders
4) Go to SOST transaction and Select all error messages . You can use Tab send status for this and by using the respective tick marks.
5) Select Error Data and Repeat Data
6) Go to SM37, select the respective Jobs , Copy the Jobs and Release with an authorized user or your ID.
7) Check with SCOT transaction all error data has cleared.
1) Execute SCOT transaction
2) Go to Utilities
3) Overview of Send orders
4) Go to SOST transaction and Select all error messages . You can use Tab send status for this and by using the respective tick marks.
5) Select Error Data and Repeat Data
6) Go to SM37, select the respective Jobs , Copy the Jobs and Release with an authorized user or your ID.
7) Check with SCOT transaction all error data has cleared.
Thursday, July 2, 2009
How to disable Import All option from STMS in SAP.
How to Remove Import All Option from STMS in SAP
Any changes made in the development server needs to be transported to the Quality server for checking and then finally in Production server.
So Importing the Transport Requests is the critical. Sometimes by mistake if one click on the button Import All in the production environment all the Transport Request which is in released status or already Imported to Production can be directly Imported to the production environment (Which may not be required in the Production). This will create great impact in the production Server.
To avoid such situation, IMPORT ALL Icon should be disabled in STMS.
Procedure to Disable IMPROT_ALL Icon in STMS:-
1) Go to STMS Tcode
2) Go to Menu Option Overview
3) Select System
4) Choose SAP SYSTEM
5) Go to Transport Tool Tab
6) Create Parameter "NO_IMPORT_ALL" with value 1 (True)
7) Save it.
Once it is done the Import_ALL icon will be Disabled from STMS.
Any changes made in the development server needs to be transported to the Quality server for checking and then finally in Production server.
So Importing the Transport Requests is the critical. Sometimes by mistake if one click on the button Import All in the production environment all the Transport Request which is in released status or already Imported to Production can be directly Imported to the production environment (Which may not be required in the Production). This will create great impact in the production Server.
To avoid such situation, IMPORT ALL Icon should be disabled in STMS.
Procedure to Disable IMPROT_ALL Icon in STMS:-
1) Go to STMS Tcode
2) Go to Menu Option Overview
3) Select System
4) Choose SAP SYSTEM
5) Go to Transport Tool Tab
6) Create Parameter "NO_IMPORT_ALL" with value 1 (True)
7) Save it.
Once it is done the Import_ALL icon will be Disabled from STMS.
Time Zone conflict between 000 client and other clients in SAP
While executing the transaction code ST03N in SAP some time problem comes that there is a conflicts in Time Zone between 000 and other clients in the same system.
Solution:-
1) Execute the transaction code stzac in both of the respective clients.
2) Check whether System Time Zone and User's Default Time Zone are same in both the clients.
3) If not the maintain both the Time Zone i.e., System Time Zone and User's defaults Time Zone Same in both the clients.
While Saving it will create a Transport Request.
Again check with the Transaction Code ST03N you will find conflict has been resolved
Solution:-
1) Execute the transaction code stzac in both of the respective clients.
2) Check whether System Time Zone and User's Default Time Zone are same in both the clients.
3) If not the maintain both the Time Zone i.e., System Time Zone and User's defaults Time Zone Same in both the clients.
While Saving it will create a Transport Request.
Again check with the Transaction Code ST03N you will find conflict has been resolved
SAP Security related activities in Upgrade
The SAP system profile parameter auth/no_check_in_some_cases has the value
“Y”. If the profile parameter is set to .N, the value must be changed. (This ensures better security).
If roles were already used in the source release, they must be updated. Transactions that were selected in the menu of existing roles can be protected using additional authorization objects in the target release. This means that tables USOBT_C and USOBX_C have to be updated as well as the existing roles.
The SU25 tcode is used for to fill the customer tables of the profile generator the first time the profile generator is used, or update the customer tables after an upgrade.
1. SU25
Step 2A
Compares the new USOBT and USOBX tables with USOBT_C and USOBX_C.
This compares the Profile Generator data from the previous release with the data for
the current release. New default values are written in the customer tables for the
Profile Generator
Step 2B
Add any new transactions/updates to tables USOBX_C and USOBT_C.
If you have made changes to the check indicators or field values in transaction
SU24, you can compare these with the new SAP defaults. You can see the values
delivered by SAP and the values that you changed next to each other, and can make
an adjustment, if desired.
Hint:
Steps 2A and 2B make changes to the customer tables of the Profile Generator.
If you want to transport these changes, choose step 3 in transaction .SU25. Before implementing any changes in system, take corresponding business approval for all role changes. The step 2C and 2D step will clearly identify the roles affected and new tcodes introduced in new systems.
Step 2C
This step guides you through all the roles that are affected by newly added authorization checks and that have to be changed to correspond. The corresponding authorization profiles need to be edited and regenerated. You can jump directly to role maintenance.
SU25, 2C step also contains the new SAP roles introduced.
If you go to one by one role, there are some authorization objects that are got affected during upgrade. We can categorize these authorization objects as below:-
1. Standard New – These are new authorization objects that are introduced in new system for corresponding tcode.
2. Manually new - It shows the authorization objects which were manually added in old system. Some of the values got updated for this also.
3. Standard Updated - Updated means, in old system if you have kept the standard values as it is, SAP has updated these standard values (u can check this one in SU24 check indicators).
4. Maintained New- Some of the organizational values introduced as field in authorization object.
After maintaining all new authorization objects, you can save it and generate the profile. If you get back to SU25 2C step shows all the roles with green signal. Means all roles saved and generated.
SU25, 2C step also contains the new SAP roles introduced.
After generating all profiles in SU25 2C step, you can jump to 2D step.
Step 2D
If you execute this step, it will show the list of roles and old tcode and corresponding new tcode.
If business wants to use new tcode, then u can replace old tcodes by new one by clicking on automatically adjust menu. Otherwise go to manually adjust menu and generate the profile.
The new tcodes are introduced in 2D step, this doesn't means the old tcodes are no longer exists in new system. We have to check manually for each and every tcode.Some tcode does not exists in new systems. FOr e.g. RZ02 is replaced by RZ20 in ECC6. RZ02 no longer exists in ECC6.
STEP 3
This step transports the changes made in steps 1, 2a, and 2b. Tailoring the Authorization Checks .This area is used to make changes to the authorization checks.
STEP 4
Changes to the check indicators are made in step 4. You can also go to step 4 by calling transaction-SU24.
You can then change an authorization check within a transaction.
1. When a profile to grant the user authorization to execute transaction is generated, the authorizations are only added the Profile Generator when the check indicator is set to Check/Maintain.
2. If the check indicator is set to do not check, the system does not check the authorization object of the relevant transaction.
Review Items:-
Security Related Parameters
You can compare and check security related parameters from old release to current release.
Review users (via SU01) to check for any new or changed fields on the user masters (Check especially background user-ID for authorizations, to avoid cancellation of batch jobs).
“Y”. If the profile parameter is set to .N, the value must be changed. (This ensures better security).
If roles were already used in the source release, they must be updated. Transactions that were selected in the menu of existing roles can be protected using additional authorization objects in the target release. This means that tables USOBT_C and USOBX_C have to be updated as well as the existing roles.
The SU25 tcode is used for to fill the customer tables of the profile generator the first time the profile generator is used, or update the customer tables after an upgrade.
1. SU25
Step 2A
Compares the new USOBT and USOBX tables with USOBT_C and USOBX_C.
This compares the Profile Generator data from the previous release with the data for
the current release. New default values are written in the customer tables for the
Profile Generator
Step 2B
Add any new transactions/updates to tables USOBX_C and USOBT_C.
If you have made changes to the check indicators or field values in transaction
SU24, you can compare these with the new SAP defaults. You can see the values
delivered by SAP and the values that you changed next to each other, and can make
an adjustment, if desired.
Hint:
Steps 2A and 2B make changes to the customer tables of the Profile Generator.
If you want to transport these changes, choose step 3 in transaction .SU25. Before implementing any changes in system, take corresponding business approval for all role changes. The step 2C and 2D step will clearly identify the roles affected and new tcodes introduced in new systems.
Step 2C
This step guides you through all the roles that are affected by newly added authorization checks and that have to be changed to correspond. The corresponding authorization profiles need to be edited and regenerated. You can jump directly to role maintenance.
SU25, 2C step also contains the new SAP roles introduced.
If you go to one by one role, there are some authorization objects that are got affected during upgrade. We can categorize these authorization objects as below:-
1. Standard New – These are new authorization objects that are introduced in new system for corresponding tcode.
2. Manually new - It shows the authorization objects which were manually added in old system. Some of the values got updated for this also.
3. Standard Updated - Updated means, in old system if you have kept the standard values as it is, SAP has updated these standard values (u can check this one in SU24 check indicators).
4. Maintained New- Some of the organizational values introduced as field in authorization object.
After maintaining all new authorization objects, you can save it and generate the profile. If you get back to SU25 2C step shows all the roles with green signal. Means all roles saved and generated.
SU25, 2C step also contains the new SAP roles introduced.
After generating all profiles in SU25 2C step, you can jump to 2D step.
Step 2D
If you execute this step, it will show the list of roles and old tcode and corresponding new tcode.
If business wants to use new tcode, then u can replace old tcodes by new one by clicking on automatically adjust menu. Otherwise go to manually adjust menu and generate the profile.
The new tcodes are introduced in 2D step, this doesn't means the old tcodes are no longer exists in new system. We have to check manually for each and every tcode.Some tcode does not exists in new systems. FOr e.g. RZ02 is replaced by RZ20 in ECC6. RZ02 no longer exists in ECC6.
STEP 3
This step transports the changes made in steps 1, 2a, and 2b. Tailoring the Authorization Checks .This area is used to make changes to the authorization checks.
STEP 4
Changes to the check indicators are made in step 4. You can also go to step 4 by calling transaction-SU24.
You can then change an authorization check within a transaction.
1. When a profile to grant the user authorization to execute transaction is generated, the authorizations are only added the Profile Generator when the check indicator is set to Check/Maintain.
2. If the check indicator is set to do not check, the system does not check the authorization object of the relevant transaction.
Review Items:-
Security Related Parameters
You can compare and check security related parameters from old release to current release.
Review users (via SU01) to check for any new or changed fields on the user masters (Check especially background user-ID for authorizations, to avoid cancellation of batch jobs).
Thursday, November 20, 2008
Report RSBTCDEL2 to delete old jobs
The job SAP_REORG_JOBS is a standard job which runs a report RSBTCDEL2 to delete old, canceled, inconsistent, non-deleted jobs from the system. But the SAP systems older than release 4.7 used RSBTCDEL report to delete the old jobs. But in those systems, after upgrade it may not run and create a dump TSV_TNEW_PAGE_ALLOC_FAILED as the old jobs get accumulated and cause memory problem.
1. Create a new variant in Transaction SE38 specifying the number of day’s range after which the jobs need to get deleted from the system.
2. Change the job from released to scheduled and delete the old RSBTCDEL report. Schedule it with the new job RSBTCDEL2
click on save
The job will now work fine since the program and Variant have been replaced.
Subscribe to:
Posts (Atom)