The below document shares knowledge of how to display the relevant fields in SCM APO Master Data for Change Documents.
To save every desired field for Change Documents there are two essential settings are required:
SPRO/ SAP Reference IMG/ Advanced Planning and Optimization/ Master Data
.../Product > Product + Location-Product + Profiles (Please Note! Version-Dependent Product Master Data is not tracked by the Change Documents tool. Only the active version is considered.)
.../Partner Dependent Data / Products / Locations
/Activate Change Documents
- Tick the relevant flags eg. Product (please see below image)
NOTE: Change Document Records are only created from the date the flag was switched on. From the time period when the flag was not set there are no records created therefore no change documents display is possible. Eg. If the flags are switched on regularly but switched off for a month between 2013 June-July then no records will be created and displayed in that time period.
NOTE: Standard SAP Programs consider to write the Change Documents tables. However there can be several extrernal applications which do not create change log during editing the master data.
2. “Data Element” / “Change Document Flag”
Check the corresponding Data Element / “Further Characteristics” tab / “Change Document” flag
This is another pre-requisite apart from Customizing for storing the before and after image of the field in the CDHDR and CDPOS tables and to display that in change documents transaction for the relevant field. (please see below image). This is a SAP Standard delivered setting.
3. The Field has to exist in the master data object's change document structure:
Search the respective object's package, and look for a structure name with a pattern like: /SAPAPO/*CD*
- Example for Location change document structures: package /SAPAPO/LOC
/SAPAPO/CD_LO_CD_LC Change Document Structure
/SAPAPO/CD_LO_CD_LM Change Document Structure
/SAPAPO/CD_LO_CD_LO Change Document Structure
/SAPAPO/CD_LO_CD_LS Change Document Structure
/SAPAPO/CD_LO_CD_LT Change Document Structure
There are several fields that cannot be monitored in Change Document transactions. For these fields, a custom solution can be worked out where SAP Note: 2240684 can give a guidance.
/N/SAPAPO/PROD_CD_READ – Product/Location-Product Change Documents
/N/SAPAPO/LOC_CD_READ – Location Change Documents
/N/SAPAPO/TR_CD_TLANE – Transportation Lane Change Documents
/N/SAPAPO/TR_CD_QUOTA – Quota Arrangements Change Documents
Change documents are also available for Interchangeability Groups with REPORT (SE38):
CDHDR - Change document header - Stores the header data of every single change
CDPOS - Change document items - Stores the change item for every single change made on the monitored objects
How to use the change document transactions (selection criteria):
The above mentioned Change Document transactions can seem to behave differently than transactions usually. This topic is to help users to create precise selection criteria to find the wished results.
1, The transactions' user interfaces are common from the header point of view. Beware the dates selection when try to display entries.
2, With the selection criteria be as specific as you can. Avoid using wildcards. Use F4 help instead to specify the entries. The wildcards are not working as expected usually in transactions. It works rather like a 1-character substitution instead of substituting any remaining characters in the field. The business object no. length has to be precisely defined (together with * (stars).
You may review the following TEST CASE for examples.
3, Technical background:
In general the different usage of the transaction comes from the database table's structure behind it. All change documents recorded for any application are stored in common change document database tables (CDHDR, CDPOS). All Products, Locations, Transportation Lanes, Quota, etc… and a lot of other applications store change documents in these tables. This means that the Change Documents DB tables are not application specific.This leads to the necessity of having some generic approach on how to identify Change Documents, which are already stored in the Database, based on selections. Each application has its own interface to Change Documents.
In case of defining a selection in the UI application (eg.: /n/sapapo/tr_cd_tlane), the structured fields to where you have written your entries are moved from the UI into a single (long) character variable, and this is used for the selection. This means that every field counts as it is entered, even the spaces in the fields are part of this concatenated key.
Eg. SE11 CDPOS
Custom Change Pointers in SCM APO for Master Data objects:
- It is possible to create custom message types in BD52 transaction for different master data objects, like product or location in APO. In this case if you change the object, the event will be logged in BDCP2 database table.
- The Change Pointers are tied to the Change Documents functionality and they use the CNA (Change Notification Agent framework).
- Therefore the respective object flags must be set up in SPRO > SCM Basis > Master Data > Product > Activate Change Documents (or Location > Activate Change Documents and so on).
2240684 - Change Notification Agent usage in SCM