We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-hr] Custom T-Code to maintain standard tables

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by LindaSue (SAP Coordinator)
on Oct 25 at 2:53 PM
Mark this reply as helpfulMark as helpful
Hello CL,
Just replying to your question "Could you please elaborate what do you mean by converting the IMG activity to Current Setting".

On occasion, we have chosen to maintain a table directly in Production, thereby avoiding the maintenance in DEV and the resultant transports. An example of this is the Exchange Rate table (OB08), which we maintain directly in Production.

There are 2 steps required to achieve this:

1) Convert the IMG activity to "Current Settings"
In transaction SPRO, navigate to the IMG activity (but don't run it)
From the menu, select Edit -> Display IMG activity
Click on the Maint.objects tab
Select the "Current Settings" checkbox next to each customizing object
Note the "Current setting transaction" displayed at the top of the screen.
This is the transaction you will need to add to the user role(s).


2) Modify the recording routine
For each customizing object you convert to "Current Settings", you need to ensure that if it is touched in DEV it will not trigger a transport. If you don't do this step, you risk that a user might someday transport the table from DEV and run over what you have in PRD.

Run transaction SE54
Enter the customizing object you just flagged as "Current Settings"
Select Generated Objects
Click on Create/Change
Provide an Access key (you have to register this change in OSS)
Select the recording routine "no, or user, recording routine".

Hope that helps,
Linda

---------------Original Message---------------
From: mySAP-HR
Sent: Monday, October 11, 2010 5:29 AM
Subject: Custom T-Code to maintain standard tables

Hi,

We have created a custom T-Code for user to maintain a cluster tables directly in our production client. The problem is that each time user needs to do this, our Basis guy will need to open up the production client so that user can maintain the tables directly in production. Apparently, this cannot be the long-term solution.

What is the best solution to this issue? Does anyone has similar experience to share here?

Appreciate any advise.

Thanks & Rgds,
CL

__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
Most Popular White Papers

In the Spotlight
Toolbox.com for iPhone: Ask Questions & Get Answers Anywhere. Use the New iPhone App
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language