Skip to Content

Introduction:

 

In SAP there are lots of standard customizing tables. In these tables, entries are maintained from SPRO settings. Ideally whenever these
entries are maintained, they ask for a transport to save data change further user needs to move these transport every time from development environment to production environment if he doesn’t have access to maintain these SPRO settings directly in production.

 

This document deals with the process of maintaining standard customizing table entries without using transport. This enables users to directly maintain entries in production environment.

 

Note of caution:

 

Ideal way to maintain any standard customizing table is via SPRO settings. You should ask user to do that way only as this keeps all the
environments in sync. This workaround should be used only if there is no business impact if this standard table is directly maintained in production system. So do analyze all the above options before implementing below approach.

  

Detailed Requirements / Technical Description:

Suppose if requirement is to maintain values of planners in SAP APO system. Ideally this is done via path: – SPRO > SAP Reference IMG > SAP – Implementation guide > Advanced Planning and Optimization > Master Data > Specify Person Responsible (Planner)

IMG 1.jpg

If any change is done to any of the above entries, it asks for a transport as shown below:-

IMG 2.jpg

Now to maintain these entries directly we create maintenance view on a table, create its table maintenance generator and assign a Tcode which will be used to maintain this table maintenance generator.

Steps to create maintenance view and table maintenance generator are as follows: –

     1. Go to SE11 and select view and enter view name as required and click on create :-

       IMG 3.jpg

     2. Select last option as Transaction with parameters and enter a short description as shown below: –

       IMG 4.jpg

     3. Enter the short description and table name on the next screen:

       IMG 5.jpg

     4. Now select view fields tab and enter all the field names which are supposed to be maintained by this view. By Default it shows only           key fields.

        IMG 6.jpg

After entering fields, save and check the view and activate it. Your maintenance view is created.

Next is to create table maintenance generator for this maintenance view. Steps for that are as follows:-

     1. Go to utilities àTable Maintenance Generator as shown below:

          IMG 7.jpg

     2. On reaching to next screen, enter values of authorization group, function group and click on Find Scr. Number(s) button.

        IMG 8.jpg

     3. It will suggest you screen numbers as below: –

       IMG 9.jpg

Now click on create button. On clicking on create it will ask you for a package in which you need to save this. Assign proper package. Your maintenance generator is created.

Finally you need to create a T-Code which will call table maintenance generator of above maintenance view. Steps to create T-Code are as follows: –

     1. Go to SE93 > Enter T-Code name > Click on create.

       IMG 10.jpg

     2. Select last option as Transaction with parameters and enter a short description as shown below: –

      IMG 11.jpg

     3. Enter values as below for Transaction and select check boxes of skip initial screen and GUI support:-

      IMG 12.jpg

     4. After this scroll the screen down and enter values as below in default values: –

      IMG 13.jpg

On saving your transaction is created. Now you can maintain table entries without including them in transport.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Vinod Kumar

    SAP standard customization settings which are allowed to be maintained in production environment are marked as “Current settings” in transaction SOBJ. 

    I feel, by the method mentioned by you, SAP standard settings for customizing objects are overridden which is dangerous.

    Even if you know the business implications it is not advisable to change a customizing table entries in production, which are not set as maintainable in production with SAP standard settings.

    Regards, Vinod

    (0) 
  2. Thomas Zloch

    Yes, the “current settings” flag should be the way to do this if required. A typical example is the FI posting periods in V_T001B, which are often maintained by the business users directly in PRD.

    The new maintenance view for your workaround must be transported through the landscape once, so I assume that the integration managers / approvers will question the motivation behind this change before it goes live. 😉

    Thomas

    (0) 
  3. Siddarth Jain Post author

    Hi Vinod / Thomas,

    I agree with you both as well on the point which you made. That is the reason I have added Note of Caution in the beginning of the document itself. Please read the below contents for your reference.

    Note of caution:

     

    Ideal way to maintain any standard customizing table is via SPRO settings. You should ask user to do that way only as this keeps all the
    environments in sync. This workaround should be used only if there is no business impact if this standard table is directly maintained in production system. So do analyze all the above options before implementing below approach.

    Thanks

    Siddarth

    (0) 

Leave a Reply