During SAP implementation or Support project, a functional consultant receives many customizing request based on functional design document or Incident Number. And life becomes very difficult when configurational request becomes dynamic in nature due to unfreezed functional design or change in Client business decision, i.e. Functional consultant receives multiple iteration of this configurational request. So it becomes important to quickly and efficiently track and analyze changes to customizing tables whenever slippage happens. This is an articulation to demonstrate various approach of tracking configurational/customizing changes performed during project realization phase.
To give a good insight on the approach, let’s consider a simple exercise of configurational request .i.e. Define order reasons: In this menu option you define the possible order reasons. They describe the reasons which led to an inquiry, quotation or order. When processing a sales document, you can specify the order reason in the overview at header level. It then applies to all the items.
Navigate to Utilities menu and press “Change Logs” option:
Here, there is provision to enter a date range to check the change log and once the desired date range is entered, execute button is hit.
Here the catch would be to make a note of Customizing table or object (maintenance views, view cluster or individual Customizing transactions) and use it in the following report to check the table changes specifics.
Following reports needs to be executed for table log changes:
1. Program RSTBHIST/Transaction code SCU3 or Program RSVTPROT (an ABAP/4 program)
Pre-condition to be checked in system for table to be logged:
1. In the technical settings of the table, checkbox “Log data changes” is marked. You can go to the technical settings via Transaction SE13.
2. Logging is also set in the system profile.
DBTABLOG :- Change customized table log is maintained in the table and Function Module : DBLOG_READ useful to read the change log by passing the tables that you want to read in the parameter :- OBJ_LIST.