Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SCU3 Configuration

Former Member
0 Likes
2,316

For an issue I want to view the log details of the tables , so i checked on scu3 t-code . But i m getting an message popup that

" Table logging is not currently active in your system."

What are the steps to activate the logs in scu3 t-code .Kindly guide me .

3 REPLIES 3
Read only

Former Member
0 Likes
1,013

Hi rakesh, with that it ask whether want to activate Yes/No ... that time u give Yes and go to the List of Logged Tables

Suku

Read only

Former Member
0 Likes
1,013

Hi,

request the BASIS team to active the log.

Read only

Former Member
0 Likes
1,013

Hi rakesh,

when jobs are deleted, they`re gone. no way to know who deleted them, when they were deleted... unless you activate traces on tables:

TBTCP

TBTCO

TBTCS

but this is not advisable because these traces will become huge because SAPSYS works a lot with those tables.

You have the following options for determining the user names of the changing administrators in the CUA central system:

● Manual analysis

If the associated IDocs were not deleted, in the central system, you can use the time in details transaction BDM2 IDoc Tracing to determine the creator of an outbound IDoc in the change documents of the child system and therefore determine the user administrator.

● Table logging

You can generate suitable change documents for role and profile assignments in the CUA central system by activating table logging for tables USLA04, USL04, and optionally USZBVSYS with transaction SE13. You can activate the table logging framework with profile parameter rec/client. You can analyze the table logging with transaction SCU3 or the reports RSTBHIST or RSVTPROT.

For technical reasons, the system does not currently log the changes, but rather logs the previous and the new statuses of all assignments at each change. This means that large quantities of data are produced, which makes analysis more difficult. To use table logging efficiently, import the correction from SAP Note 935510. This means that the system now logs only the differences from the previous status of the system-specific roles and profile assignments in tables USL04 and USLA04.

see these links

http://www.thesapconsultant.com/2005/11/automatic-table-history.html

http://www.saptechies.com/how-to-activate-the-img-change-log/

http://help.sap.com/saphelp_nw04s/helpdata/en/c7/69bcbaf36611d3a6510000e835363f/content.htm

http://books.google.co.in/books?id=ASekwAiAXdMC&pg=PA290&lpg=PA290&dq=Tableloggingisnotcurrentlyactiveinyoursystem%2Bsap&source=web&ots=BS4a5zNH4z&sig=t9dN6LsiGi8DcKR0DKDutzznYJU&hl=en&sa=X&oi=book_result&resnum=1&ct=result#PPA289,M1

i hope the above info will solve ur issue.

happy solving,

thanks

karthik