TAANA table analysis

There is a transaction TAANA that does table analysis.

To set it up:  Transaction TAANA -> Table Analysis Menu -> Perform -> Enter Table Name e.g. CDCLS

Now go into the advance selection options for Analysis Variant.

Then select the "Ad Hoc Variant" button at the bottom.

Next move the OBJECTCLAS column from the right to left pane and select the green tick.

Make sure the ad hoc variant is ticked and use the green tick to leave this screen.

You should now be back at the first screen. Make sure "In the Background" is selected and use the green tick. Schedule whenever suits.

Once it has finished running you can go back to TAANA and select the CDCLS node and double click the green line - this will display all the

entry counts per object type.  

In our example we could see the majority of records by far were object type COND_A (PRICING CONDITIONS)

Table TCDOB - will tell you which tables are covered by which object and a description for each object

CDHDR Object class

DEBI -  Customer master changes
VERKBELEG - Sales order changes

FB04 - FI Accounting document Change logs

FI Accounting document Change logs

 

Go to FB04 transaction.  Click on Environment -> Multiple display.  Follow as per screenshots below.  Please call me if you find any issues.  Thank you.

 

 

 

 

 

 

Change logs - Program to report RSSCD200

RSSCD200 program

RSSCD100

Activate change documents

Activate change documents:

http://wiki.scn.sap.com/wiki/display/PLM/Activate+change+documents

Steps to enable logging of changes in change documents

Good Link:

http://wiki.scn.sap.com/wiki/display/Snippets/Steps+to+enable+logging+of+changes+in+change+documents

SCU3 - To read changes to tables

 

Transaction SCU3 can be used to read changes to tables, this is useful with transactions such as WE20 (EDI partner profile as not all transactions include a charge history screen)

The system parameter rec/client must be activated  

rec/client = off

- Table change logging inactive

rec/client = all

-  Table change logging active in all clients  (See Warning below)

rec/client = <client 1>...

- Table change logging active in specified clients

Setting the REC/CLIENT parameter to All can seriously impair SAP system performance. SAP recommends you do not use the value All. You should limit automatic logging to one client

Within SE13 we can see the checkbox ‘Log data changes’ is assigned to a table

In an ECC 6 system running SE16 against DD09L shows approx. 31k tables with this flag activated (DD09L-PROTOKOLL EQ ‘X’) However these are generally customizing type tables (non-transportable)

Deleted sales order - check changes

To know who deleted the sales order run the program RVSCD100  Or you can go to VA03 with the order number, do not go into VA03 screen, instead go to 'Environment->changes' from front screen.
Or, you can check in CDHDR/CDPOS table.

Reference: http://scn.sap.com/thread/1041663

For delivery:  Go to VL03N and go to environment -> changes

Change doc. object   =   EINKBELEG  for Purchase Order

 

                                 = VERKBELEG  for sales order

   

                                 = LIEFERUNG for  Outbound delivery

CDHDR - Address changes in sales document

Address (ship-to) changes in sales document will not be shown in change logs. But still logged in CDHDR table.  Object-class is ADRESSE and give  object-id as ‘SD01XXXXXXXX’ where ‘XXXXXXXXX’ is address number which can be fetched from VBPA table in ‘Address’ field.

CDHDR object class for Purchase order

To fetch creation time from CDHDR for Purcahse order:

Go to CDHDR -> give Object class as EINKBELEG and object id as PO number.

CDHDR object classes:

To get all object classes, go to SCDO tcode - here you can search for object class