On SAP, some tables are delivered as “customizing tables” when they supposed to be set as “Master Data tables” and allow you to maintain those tables in Production environment, instead following the “normal” path DEV-QAS-PRD system using transport requests.
One good example for this are the tables mentioned on my posting about Tax Dynamic Exception tables. Those tables are considered “Tax Master Data” on Brazilian Localization (and they are only used for Brazil).
A good reason to make those tables “maintained” in Production is for example if you have to create a dynamic exception to a certain tax table, J_1BTXCOF for instance, to calculate a different tax rate to a combination of Customer and Material (or even to a specific material or a specific Customer/Vendor)…
You will not be able to do that in DEV, since you don’t have (or you supposed not have) master data in DEV, that you can add to the table and transport it to PRD.
Many companies in this case they make the PRD environment “open” to allow the maintenance on those tables, which is a high risk, and for lack of information, knowledge or even lack of time to discuss this subject during an implementation, the subject is left behind and the PRD is open for change for a long period (or open and close every time when the change is needed, very painful for users and Basis right?)
What many people doesn’t know is that SAP has a OSS Note to support allow specific tables to be maintained in PRD without needing to open the environment for changes or transporting data from other clients.
By doing that, you increase the security on your PRD system and increase the business process speed to maintain the data when it is required without having to wait someone open the client, wait the user do the maintenance and close the client again.
1 – Open system with transaction code:
Example of transaction to “open” in PRD:
SPRO > Financial Accounting > Financial Accounting Global Settings > Tax on Sales/Purchases > Calculation > Settings for Tax Calculation in Brazil >Tax Rates >
> Maintain Default Tax Rate Values tcode: S_ALR_87003324
> Maintain IPI Values tcode: S_ALR_87003326
> Maintain IPI Material-Dependent Exceptions tcode: S_ALR_87003329
> Maintain IPI Dynamic Exceptions tcode: S_ALR_87100870
> Maintain ICMS Values tcode: S_ALR_87003332
> Maintain ICMS Material-Dependent Exceptions tcode: S_ALR_87003334
> Maintain ICMS Dynamic Exceptions tcode: S_ALR_87100868
> Maintain ICMS-Complement Exceptions tcode: S_ALR_87003230
> Maintain SubTrib Values tcode: S_ALR_87003232
> Maintain SubTrib Material-Dependent Exceptions tcode: S_ALR_87003236
> Maintain SubTrib Dynamic Exceptions: S_PL0_09000292
> Maintain ISS Values tcode: S_P6D_40000012
> Maintain PIS Values tcode: S_P6D_40000013
> Maintain COFINS Values tcode: S_P6D_40000014
> Maintain Withholding Tax Rates and Assign Official Collection Codes: S_P6D_40000030
To change the status for a transaction to “open” for maintenance in PRD while keeping the client closed, follow the steps below:
a) Check the table name that the transaction use
b) At Production Client, run transaction SE54, inform the table or view name and check “Generate Objects” and then click “Create/Change”. Select “No, or user, recording routine”, click in Save (create the change request) and hit enter
c) This procedure has to be done in a client where PRD is “closed” for changes.
2 – Open system without a transaction code
This is used to the activities that are reachable only via SPRO, but it doesn’t have a specific transaction assigned. It is possible to add the SPRO Activity to a Menu that the user can access. To do that, follow the procedure:
• Go to the IMG, and display the IMG structure.
• Position the cursor on the corresponding IMG activity and select the menu options “Edit -> Display IMG activity”.
• On the following screen, select the tab page “Maint.objects”.
• There you can see a list of the assigned Customizing objects.
• By double-clicking on the corresponding line, you navigate to the Customizing object and can directly set the flag ‘Current settings’ there.
• As an alternative you can also call Transaction SOBJ. There, you must directly enter the Customizing object and can then set the flag directly.
Oss Notes that you can use for reference: 78329 / 135028 / 77430
Leandro da Pia Nascimento
- SAP Managed Tags:
1 Comment
