Maintaining Posting Periods on productive client.

[Former Member]

hi all.

Is there any way of maintaining posting periods "OB52" (IMG activity) without changing the status of productive client to modifiable. I know one way is to maintain the posting periods in dev and then transport. Is there any other way? (directly in production) and also what is the recommended method for doing this.

[Former Member · Accepted solution]

Hello Rizwan,

You can maintan OB52 in productive client by keeping the client as productive.The settings in SCC4 have to be like this :

Client Role: Production

Changes and Transport for client specific objects: Not allowed.

Client Independent object changes: No changes to Repository and cross client authorization objects allowed.

These settings will allow users to maintain OB52 in production clients but won't allow them access to maintain general customizing.

Further you would need to assign authorizations for S_TABU_DIS as mentioned by Barry.

OB52 is nothing but a view of table T001B. The authorization group for T001B table in table maintainence generator is FC31.

So whosever needs to maintain OB52 needs to have proper authorization for this table via S_TABU_DIS.

The values assigned have to be :

Activity 02,03

Authorization Group: FC31.

Also you can check whether OB52 is allowed for maintainence in production.

For this go to transaction SOBJ. Then check the check box against enter conditions and click on display. A pop up would come up. here you can give the view name V_T001B. In the resulting screen check for the check box against Current Settings. If it is checked then OB52 is open for maintainence in production client.

There is one more method:

Go to SPRO. Then to SAP Reference IMG. Go to the node for opening and closing posting periods. You can also search for this using Control+F option. Use the search string " Open and Close Posting Periods".

Once there click on it. Then in menu bar go to EDIT and then to display IMG activity. In the next screen to go tab Maint. objects under the selection block Assigned objects. Here you will find an entry for table V_T001B. Double click on it a new screen appears. Here just check if the check box against current settings is checked. If it is then OB52 can be maitained in production clients.

Please award points if the answer was helpful to you.

With Regards.

Ruchit

[akumar_678571]

Dear Javed,

Thanks, it was useful . could check the settings as you have guided .

Regards

Ajay Kumar

[Former Member]

We have our productive client set to No changes allowed and no changes to repository or cross-client customising objects, and are still able to run OB52 and OKP1.

This is controlled through our User Profile.

[Former Member]

Hi Barry,

Is it possible to change client dependent or client independent changes even when the system is configured as not allowed?U r able to do it through userprofiles?

I feel new to this concept.

Can u elaborate?

Regards,

Bapujee Naidu

[Former Member]

We've been using OB52 in Production since we went live, 5 Years ago...

Here are the Authorisation objects needed to change these entries.

For OB52:

S_TCODE RC=0 TCD=OB52;

S_TABU_DIS RC=0 ACTVT=02;DICBERCLS=FC31;

For OKP1:

S_TCODE RC=0 TCD=OKP1;

S_PROJECT RC=0 PROJECT_ID= ;APPL_COMP= ;PROJ_CONF= ;ACTVT= ;

S_TABU_DIS RC=0 ACTVT=02;DICBERCLS=KC;

[Former Member]

Thanks alot Barry !

Regards,

Bapujee Naidu

[Former Member]

Hopefully this resolved your issue.

Best wishes

Barry