sap advanced planning and optimization, data management ... · pdf file5.4 deleting change...

User Guide PUBLIC

Document Version: 1.1 – 2016-12-16

SAP Advanced Planning and Optimization, Data Management Toolkit

Content

1 SAP Advanced Planning and Optimization, Data Management Toolkit. . . . . . . . . . . . . . . . . . . . 3

2 Master Data Deletion Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Deleting Data using the Master Data Deletion Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Displaying Application Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.3 Enhancement of Deletion Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Change Log Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.1 Configuring the Change Log Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133.2 Specific Use of Wild Card Entries in the Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.3 Displaying Database Change Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.4 Display Change Log Monitor Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.5 Reorganizing Notes and Database Entries Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.6 Reorganizing Notes and Database Entries in the Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4 CIF Postprocessing Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.1 Displaying Postprocessing Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.2 Working on Postprocessing Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194.3 Lock Concept in CIF Postprocessing Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5 Change Monitor for LiveCache Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.1 Authorizations and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235.2 Displaying Logged LiveCache Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.3 Result Screen of Change Monitor for LiveCache Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.4 Deleting Change Records in Batch Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265.5 Configuring Change Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.6 Result Screen of Configuration of Change Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.7 Adjustment of Date Settings in Change Log Monitor Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 325.8 Change Recording Throughout the Lifecycle of a Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.9 Performance with Activated Change Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

2 P U B L I CSAP Advanced Planning and Optimization, Data Management Toolkit

Content

1 SAP Advanced Planning and Optimization, Data Management Toolkit

SAP Advanced Planning and Optimization, data management toolkit is an add-on to SAP Advanced Planning and Optimization (SAP APO), within SAP Supply Chain Management (SAP SCM). It is used to increase the productivity in operating the SAP APO system.

The toolkit offers the following features:

● Master Data Deletion ReportYou can use this feature to identify and remove master data that is no longer used within SAP APO, in an automated recursive way. You can use it to delete the objects in a correct sequence, while considering the remaining dependencies. This reduces the effort required for preparing a concept on data deletion process and deleting the data

● Change Log MonitorYou can use this feature to track changes made to time series key figure values in Demand Planning or Supply Network Planning in SAP APO. It simplifies internal communication as the information, the time, and the user who provided the information are all visible in the system.

● CIF Postprocessing CockpitYou can use this feature to allow simultaneous Core Interface (CIF) postprocessing for multiple ERP systems with multiple users. Multiple users can work on interfaces clearing at the same time. You can reduce processing time and costs. You can also get the correct planning picture faster.

● Change Monitor for liveCache OrdersYou can use this feature to track changes made to the liveCache orders data based on the change log monitor configurations.

System Landscape

The SAP Advanced Planning and Optimization, data management toolkit is part of the SAP SCM system landscape. However, to use some of its features, a connection to SAP ERP systems is necessary.

SAP Advanced Planning and Optimization, Data Management ToolkitSAP Advanced Planning and Optimization, Data Management Toolkit P U B L I C 3

Figure 1: System Landscape for SAP Advanced Planning and Optimization, data management toolkit

Related Information

Master Data Deletion Report [page 5]Change Log Monitor [page 10]CIF Postprocessing Cockpit [page 18]Change Monitor for LiveCache Orders [page 22]


SAP Advanced Planning and Optimization, Data Management Toolkit

2 Master Data Deletion Report

Master data deletion report (MD deletion report) is part of the SAP Advanced Planning and Optimization, data management toolkit, an SAP Advanced Planning and Optimization add-on. You can use the MD Deletion Report to remove obsolete SCM-APO master data and the linked transaction data, in an automated recursive way.

CautionThe MD Deletion Report will delete data in SAP APO. Select your data judiciously to prevent unwanted data loss. The MD Deletion Report should be handled by an SCM-APO master data expert.

You can use the following modes provided by the report:

● Deletion Mode: The report deletes all selected transaction and master data.● Set Deletion Flag (Only): The report sets the deletion flag if no further dependencies exists for location

product, product and location.● Set Deletion Flag (with TA data): The report deletes all transaction data, and sets the deletion flag on

location product level. If there is no further dependent data for the product, the report also sets the deletion flag on the product level, and on the location level.

You can use the simulation mode for both Deletion Mode and Set Deletion Flag. In this simulation mode the report determines obsolete master data and corresponding transaction data. Regardless of the mode you select, a log is displayed at the end of the program.

You can schedule the report as a background job.

Related Information

Deleting Data using the Master Data Deletion Report [page 6]Enhancement of Deletion Report [page 9]Displaying Application Logs [page 9]

SAP Advanced Planning and Optimization, Data Management ToolkitMaster Data Deletion Report P U B L I C 5

2.1 Deleting Data using the Master Data Deletion Report

You can use MD Deletion Report to delete obsolete SCM-APO master data and the related transaction data. You can schedule the report to be executed as a background job.

Context

CautionThe MD Deletion Report will delete data in SAP APO. Select your data judiciously to prevent unwanted data loss. The MD Deletion Report should be handled by an SCM-APO master data expert.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit APO Master Data Deletion APO Master Data Deletion Report (transaction /APOTK/MD_DELETION).

2. Select the mode in Main Parameters.a. To delete master data and related transaction data, select Deletion Mode.b. To only set the deletion flag on location product, product and location level, select the Set Deletion

Flag (Only)c. To delete all transaction data and to set the deletion flag on location product level, select the Set

Deletion Flag (with TA data)..

If there is no further dependent data for the product, the report also sets the deletion flag on the product level, and on location level.

3. Optional: To display a log of the data selected for deletion without actually deleting the data, select the Simulation Mode.

4. Enter the model.

Only data assigned to the selected model is selected and processed.5. Enter the planning version.

Only data assigned to the selected planning version is selected and processed. If the active planning version is selected, all other planning versions are also processed.

6. Enter the product number and the location.

If you enter a wildcard (*) as product number, the report considers all products in the selection.7. Optional: You can enter the location type to restrict the location selection.8. In Advanced Options, you can do the following:

a. Select the server group.


Master Data Deletion Report

b. Retain the default setting for Max. WP Usage (%).

The maximum work process usage of parallel tasks, in percentage, on the Advanced Options screen of the MD Deletion Report must be lower than or equal to the value maintained in the settings of the CCMS: RFC Server Group Maintenance.

c. Optional: Define the level of detail for the log written during the execution of the deletion program.d. Optional: Select Check LocProd Not in Active IM to check if the current location product is still in use in

an active integration model.e. Optional: Select Show technical Log to display the technical details.f. Optional: Select Only MD with Deletion Flag to consider only the master data for which the deletion flag

has already been set.g. Optional: Specify the number of resources to be deleted in one package.h. Optional: Specify the threshold above which parallelization will be used for deletion of products.

9. Select the objects you want to delete.

There are several checks on dependencies between the selected objects.

Objects Details and Dependencies

Products (Global Data) The report checks the where-used list of the product first, and if no further use is determined, it deletes the product data.

Location Product The report checks if the location product has dependent transaction data, and if no further use is determined, it deletes the location product data.

Dependencies: All dependent transaction data must be deleted before deleting location products. The data on location product level is deleted depending on the selected planning version.

Location Product Hierarchies The report selects and deletes a location product from a hierarchy. If the location product hierarchy has no further use, the hierarchy itself is deleted.

MM Schedule Agreements The report selects and deletes MM schedule agreements.

SD Schedule Agreements The report selects and deletes SD schedule agreements.

Production Process Model (PPM) The report selects and deletes the PPM.

Dependencies: The liveCache orders must be deleted beforehand.

Production Data Structure (PDS) The report selects and deletes the PDS.

Dependencies: The liveCache orders must be deleted beforehand.

External Procurement Relationships The report selects and deletes external procurement relationships.

Dependencies: All dependent product-specific transportation lanes must be deleted beforehand.

LiveCache Orders The report selects and deletes liveCache orders.

Delete Stock The report selects and deletes all kinds of stock.


Objects Details and Dependencies

Interchangeability Groups The report selects and deletes interchangeability groups.

MM Quota Arrangements The report selects and deletes MM quota arrangements.

Product Hierarchies The report selects and deletes a product from a hierarchy.

Dependencies: If the product hierarchy has no further use, the hierarchy itself is deleted.

Product-Dependent Transportation Lanes The report selects and deletes the product-dependent transportation lanes.

Dependencies: Before you select this checkbox, delete the data dependent on the following objects:○ Materials management (MM) schedule agreements○ Materials management (MM) quota arrangements○ Sales and Distribution (SD) schedule agreements

Locations The report selects and deletes locations. The report checks the where-used list of the product first, and if no further use is determined, it deletes the location data.

Setup Groups The report selects and deletes setup groups.

Dependencies: The corresponding resources must be deleted before deleting the setup groups.

Setup Matrixes The report selects and deletes setup matrixes.

Dependencies: The corresponding resources must be deleted before deleting the setup groups.

Resources The report selects and deletes the specified resource types. Resource types can be selected.

Dependencies: The production process model (PPM) and production data structure (PDS) data, along with the resources must be deleted beforehand.

Product-Independent Transportation Lanes The report selects and deletes the product-independent transportation lanes.

Condition Tables The report selects and deletes condition tables that are related to the selected location.

Dependencies: Only location-dependent condition tables are deleted.

10. Execute the report.

The application log is displayed.

Related Information

Displaying Application Logs [page 9]Master Data Deletion Report [page 5]


Master Data Deletion Report

2.2 Displaying Application Logs

You can evaluate the logs written by the deletion report. Deletion Log Display displays the hierarchical view of application logs. The application log is saved for processing. You can choose the level of detail of the application log in the advanced options.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit APO Master Data Deletion Deletion Log Display (transaction /APOTK/MD_DEL_LOG ).

2. Enter your selection in Object Criteria and Administrative Criteria.3. Execute the report to display the logs.

The results are displayed in a hierarchical view, grouped by the planning version.

Related Information

Master Data Deletion Report [page 5]Deleting Data using the Master Data Deletion Report [page 6]

2.3 Enhancement of Deletion Report

MD Deletion Report can be enhanced with several BAdIs.

You can use the BAdI methods for each master data or transaction data object to read and delete customer-specific dependent data objects. You can filter or enrich the selection of the location products with your specific selections.

Related Information

Master Data Deletion Report [page 5]Deleting Data using the Master Data Deletion Report [page 6]


3 Change Log Monitor

The change log monitor is part of the SAP Advanced Planning and Optimization, data management toolkit, an SAP Advanced Planning and Optimization add-on. You can use it to log and monitor changes made to planning data in the Demand Planning (DP) and Supply Network Planning (SNP) environment.

The following information is recorded in detail in the change log:

● User who makes the change● Planning area● Key figure● Planning version● Planning characteristics that have been changed● Date and time of change● Bucket that is changed● Old value● New value● Unit of measurement● Indicator that shows whether the change was done online or in batch mode

The change log monitor saves all changes made to key figures in the planning book, provided that you have maintained the appropriate configuration setting for the changes done. The change log monitor also logs the changes generated by macros, process chains, or, for example, changes generated when data is loaded from InfoCubes or copied between planning areas.

The change log monitor creates a change log only for the current planning level, that means, the level at which the change is made. Dependent changes that are created by disaggregating the change from the current planning level to the lower levels, or aggregating them up to the higher levels in a planning hierarchy, are not logged.

ExampleConsider the following initial situation: For region 1, there are three customers in a customer group.


Change Log Monitor

Figure 2: Initial Situation

There is currently no quantity set up at any level, that is, the quantity is zero at all levels.

When the planner enters a quantity of 15 at the customer group level, this quantity entered by the planner is saved once at the customer group level.

Figure 3: Change saved at the Customer Group Level

At the same time the quantity is prorated down by the system to the customer level, and each customer gets an equal portion of 5. However, in the change log monitor only the change done by the planner, that is, the creation of 15 at customer group level, is considered, and a respective change log is created.

SAP Advanced Planning and Optimization, Data Management ToolkitChange Log Monitor P U B L I C 11

Later, the planner increases the quantity from 5 to 10 for the second customer from Region 1.

Figure 4: Change Saved at the Customer Level

Again the system saves the quantity of 10 at the customer level, and adjusts the quantity at customer group level from 15 to 20 accordingly. This time a change log is created for the change done by the planner at the customer level.

Related Information

Configuring the Change Log Monitor [page 13]Reorganizing Notes and Database Entries Online [page 16]Displaying Database Change Records [page 15]Reorganizing Notes and Database Entries in the Background [page 17]


Change Log Monitor

3.1 Configuring the Change Log Monitor

You can configure the change log monitor to define the scope of the changes to be recorded. You can also set up detailed settings for each configuration setting. For example, you can configure whether a change should be recorded as a planning book note or a database record, or both.

Context

When you make a change, the system evaluates the configuration settings. If there is a configuration setting which matches the parameters of the change, a change log is created.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit Change Log Monitor Change Log Monitor (transaction /APOTK/CLM).

2. Optional: To restrict the configuration settings, enter the user, planning area name, key figure, and planning version in Selection of Change Criteria.

3. Optional: To display all change records that have been created by background activities, select the checkbox Changes in Batch in Selection of Change Criteria.

4. Optional: To display all change records which have been created during online activities , select the checkbox Interactive Changes in Selection of Change Criteria.

5. Select Configure Change Log Settings on the entry screen of the change log monitor.6. To define a new configuration setting choose Append Row and enter the following values:

a. Enter the ID of the user who triggered the change. If changes are made in batch mode, enter the ID of the user who scheduled the job.

b. Enter the planning area, planning area key figure, and the planning version in which the change is done.

c. To enable the logging of changes via notes select the Activate Notes checkbox.d. To enable the logging of changes via database entries select the Activate DB. Records checkbox.e. To prevent the recording of changes during an InfoCube upload, select the No Log for IC Upload.f. To prevent the recording of changes during the copying of data between key figures and planning

version (Copy/Version management with transaction /SAPAPO/TSCOPY), select the No Log for C/V Mgmt..

Uploading data from an InfoCube and copying of data between key figures and planning version can be performance-intensive tasks, especially if change recording is enabled. It is recommended that you keep the logging volume as small as possible.


Related Information

Specific Use of Wild Card Entries in the Configuration Settings [page 14]

3.2 Specific Use of Wild Card Entries in the Configuration Settings

You can use either a concrete value or a wildcard entry in the different fields when configuring the change log settings.

If you use the wildcard, (*) as the input for any field of the configuration setting, then all values that are possible for this field are allowed.

However, mixed strings consisting of a concrete value and the wildcard character are not allowed. For example, you cannot use D01* to record the changes for all the users starting with 'D01' (such as D01234, D01235, D01236 and D02345). For this, you have to either create separate configuration settings for each user, or you have to create one setting with the wildcard character for the user name. If you choose the latter option, the changes for all users in the system will be recorded.

If there are several entries in the configuration table that match the parameters of the change, then the configuration setting with the most appropriate key is taken into account.

Example

Table 1: Wildcard Entries

Name Planning Area Key figure Planning Version Logging Active for Notes

Logging Active for Database

* * * * X

D01234 * * *

Here, if the user who makes the change is not D01234, then only the first configuration setting is valid. Changes will be recorded as planning book notes.

However, if the user who makes the change is 'D01234', both configuration settings could be applied. The user ID 'D01234' is within the range of the wildcard (*) for the first configuration entry, and also the concrete value (D01234) matches the current change case.

But the key specified in the second configuration setting is more concrete than the key specified in the first configuration setting. In the second configuration setting, 1 of 4 parameters have a concrete match (that is, a concrete value against concrete value), while 3 of 4 parameters have a wildcard match (concrete value against wildcard entry in the configuration setting). For the first configuration settings all 4 parameters have a wildcard match (concrete value against wildcard entry in the configuration setting). So, as the second configuration setting is more concrete than the first configuration setting, the system will apply this setting and no change log will be created in the corresponding change case.


Change Log Monitor

NoteIf you have more than one configuration setting with exactly the same parameters in the configuration table, then the system always applies the first setting in the table. We recommend that you do not maintain more than one configuration setting with exactly the same values in all four parameters.

3.3 Displaying Database Change Records

You can display the database entries which have been recorded so far by the change log monitor.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit Change Log Monitor Change Log Monitor (Transaction /APOTK/CLM).

2. Enter the planning area name in Selection of Change Criteria.3. Optional: Enter the user name, the key figure and the planning version in Selection of Change Criteria to

restrict your results.4. Optional: Enter the date and time in Selection of Change Time to restrict your change criteria. If you do not

enter specific dates, the system uses the default change time.

The change time is the time at which the change has been recorded.5. Optional: Enter the period in Selection of Changed Periods to restrict your change criteria. If you do not

enter a specific period, the system uses the default period.

The changed period is the new period to which the key figure was set.6. Select Display DB Change Records on the entry screen of the change log monitor.

The dialog box Select Characteristic Values Combinations appears. It is dynamically generated depending on the planning area selected.

7. Optional: To further restrict your selection, enter additional values in this dialog box.8. Confirm your selection.

Results

The database entries selected according to the given criteria are displayed.


3.4 Display Change Log Monitor Notes

The logs which have been recorded in planning book notes are created and attached to the respective cell in the planning grid of the planning book. They are not accessible from the change log monitor transaction. To view the notes, you can either use the standard transaction Note overview (Transaction /SAPAPO/SDP_NOTES) or you can display the notes in the planning book itself in the interactive planning transaction (Transaction /SAPAPO/SDP94).

If a note exists, a note icon appears on the left-hand side of the cell. You can select Display Note from the context menu to view the note. The most recent changes are listed at the top.

You can also enter personal comments in the note.The personal comments will be kept even when new changes are recorded and the notes are enhanced by the change log monitor.

The change log monitor can distinguish between the value 'zero' and no entry, if you have defined 'zero' as a possible value in the Customizing for the respective key figure.

3.5 Reorganizing Notes and Database Entries Online

You can use the reorganization functionality of the change log monitor to delete entries from notes or the database, or both.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit Change Log Monitor Change Log Monitor (Transaction /APOTK/CLM) .

2. Enter the planning area name in Selection of Change Criteria.3. Optional: You can enter the following infomation in Selection of Change Criteria to restrict the change logs

you want to delete.a. Enter the user name and the key figure.b. To delete all change records that have been created by background activities, select the checkbox

Changes in Batch.c. To delete all change records which have been created during online activities , select the checkbox

Interactive Changes.4. Enter the date up to which the change logs should be deleted in Selection of Deletion of Notes and DB

Change Records. Change logs will be deleted up to the date entered, but the date entered is not included for deletion.

5. Optional: To delete all change records that have been saved as planning book notes , select the checkbox Delete Notes in Selection of Deletion of Notes and DB Change Records.

6. Optional: To delete all change records that have been stored as database records, select the checkbox Delete Database Records in Selection of Deletion of Notes and DB Change Records.


Change Log Monitor

7. Enter the planning version in Selection of Deletion of Notes and DB Change Records.

NoteThe sytem will use the planning version from Selection for Deletion of Notes and DB Change Records. The entry for the planning version in Selection of Change Criteria will be ignored.

8. Select Reorganize Change Logs on the entry screen of the change log monitor.

The dialog box Reorganization of Change Logs appears.9. Confirm that you want to delete the change logs.

The system deletes the notes or database entries or both, and displays the the number of entries deleted.

Related Information

Reorganizing Notes and Database Entries in the Background [page 17]

3.6 Reorganizing Notes and Database Entries in the Background

You can use the report Change Log Monitor - Deletion of Change Logs in Background to automate the reorganization of change log records by scheduling a regular reorganization job. You can also execute this report in online mode.

Procedure

1. To access this report on the SAP Easy Access Screen, choose Advanced Planning and OptimizationAPO Data Management Toolkit Change Log Monitor Change Log Monitor - Deletion of Change Logs in Background (transaction /APOTK/CLM_DEL_BATCH).

2. Enter your selections in Selection of Change Criteria and Selection of Deletion of Notes and DB Change Records.

3. Save the selections as a variant.4. Plan the background processing for the different variants.

Related Information

Reorganizing Notes and Database Entries Online [page 16]


4 CIF Postprocessing Cockpit

The CIF Postprocessing Cockpit (PPC) is part of the SAP Advanced Planning and Optimization, data management toolkit, an SAP Advanced Planning and Optimization (SAP APO) add-on. You can use it to work on postprocessing records which have been created by Core Interface (CIF) error handling.

This function is based on the transaction for postprocessing in SAP APO (CIF Postprocessing, transaction code: /SAPAPO/CPP). The main features of PPC are multiple system capability and the locking concept on transaction ID level.

Related Information

Displaying Postprocessing Records [page 18]Working on Postprocessing Records [page 19]Lock Concept in CIF Postprocessing Cockpit [page 20]

4.1 Displaying Postprocessing Records

You can use the program APO Core Interface Post Processing Cockpit to display and work on postprocessing records which have been created by CIF error handling. This program can be used by multiple users at the same time.

Prerequisites

You can only select those systems that you have maintained in the system table in Customizing, and which also have CIF error handling enabled. For this, see Customizing under Integration with SAP ComponentsIntegration via APO Core Interface (CIF) Basic Settings for Creating the System Landscape Assign Logical System and Queue Type .

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit Post Processing Cockpit APO Core Interface Post Processing Cockpit (transaction /APOTK/PPC ).


CIF Postprocessing Cockpit

2. Enter one or more target systems.3. Optional: You can filter the results further by entering the order category.

The order category in SAP APO is integrated with SAP ERP via APO Core Interface (CIF). Order categories are, for example, In-House production, External procurement or Customer Order.

4. Optional: You can filter the results further by entering the error status assigned to the postprocessing records.

5. Optional: Select the processing status of a postprocessing record . Otherwise the system uses the default processing status: Still for Processing.

6. Confirm your selection.

The postprocessing cockpit is displayed.

Related Information

Working on Postprocessing Records [page 19]

4.2 Working on Postprocessing Records

You can use the CIF postprocessing cockpit to work on postprocessing records created by CIF error handling.

Context

The cockpit screen is based on the transaction /SAPAPO/CPP.

For more information on CIF Postprocessing, see SAP Help portal at http://help.sap.com and choose Supply Chain Management SAP Supply Chain Management (select a relevant release, for example) SAP

SCM 7.0 Application Help SAP Advanced Planning and Optimization (SAP APO) Integration via Core Interface (CIF) Technical Integration Core Interface (CIF) Administration CIF Error Handling CIF Postprocessing .

The navigation tree in the left pane outlines the structure of the post processing records as follows:

● The top node of the structure comprises the sender(source) and receiver(target) logical systems of the data transfer.

● The lower nodes indicate the SAP APO object type, then the location (plant), and finally the product (material).

● The number of the assigned records with the status 1 – Still for Processing is displayed in brackets.

If the text of a node appears as Unknown (for logical systems) or ??? (for SAP APO object type, location or product) then the corresponding field of the postprocessing record was not filled.

SAP Advanced Planning and Optimization, Data Management ToolkitCIF Postprocessing Cockpit P U B L I C 19

http://help.sap.com

Procedure

1. To display all post processing records assigned to a particular level, choose a node in the navigation tree from the Post Processing Cockpit screen.

2. To start the postprocessing, select at least one record and choose Start Postprocessing.

The standard transaction for postprocessing in SAP APO (CPP) is called.

The selected records determine the selection criteria for the postprocessing. Dependent records are also selected. Source system and transaction ID (TID) of the logical unit of work (LUW) are transferred to identify the records. While you are working on the selected record and all dependent records, the system locks these records to prevent other users from editing the same records.

3. To display the application log, double-click on a record. You can also select a record and choose Show Application Log from the menu bar.

4. To display all postprocessing records which have been created earlier, select a record and choose Show History from the menu bar.

5. To display any existing note belonging to a record, select the record and choose Show Note from the menu bar.

You can create and edit notes using the transaction CPP.6. To refresh the selected data, choose New Selection.

The selection criteria will be reused.

Related Information

Displaying Postprocessing Records [page 18]

4.3 Lock Concept in CIF Postprocessing Cockpit

When you execute the standard transaction CPP, the entire logical system selected is locked. In contrast, the CIF postprocessing cockpit applies locking only on Transaction ID (TID) level and on the logical system.

Locking in PPC means that TIDs of dependent records are also locked, because the system also selects dependent records when the transaction CPP is executed. The lock is kept until the user leaves the postprocessing in CPP transaction (by returning to the PPC screen, or by closing the window).

The normal CIF processing is interrupted if locks are kept on the table with the postprocessing records for a long time. To avoid this in PPC, the locks are not set on this table, but on a second table created for this purpose. The TIDs of records in use and their logical system are locked in the second table. When a postprocessing record is saved after editing, a lock is applied and released immediately.


CIF Postprocessing Cockpit

Figure 5: Lock Concept

Example● User A works on a record with TID 123 belonging to logical system Alpha.● User B cannot work on the same record at the same time, so he or she chooses a record with TID 567 in

logical system Alpha.

Related Information

CIF Postprocessing Cockpit [page 18]

SAP Advanced Planning and Optimization, Data Management ToolkitCIF Postprocessing Cockpit P U B L I C 21

5 Change Monitor for LiveCache Orders

The change monitor for liveCache orders is part of the SAP Advanced Planning and Optimization, data management toolkit, an SAP Advanced Planning and Optimization add-on. You can use this to keep track of changes that have been made to orders in SAP APO and orders which have been created,changed, or deleted in the ERP system, and which are transferred through the Core Interface (CIF) to SAP APO.

CautionEnter your configuration data judiciously to record or track only changes that you want to record. If you enter too many wildcards (*) the system performance could be negatively impacted. Your selection of the time period , the user and even the order category, is important.

Document types whose changes can be recorded with the Change Monitor include the following:

● Purchase requisitions● Purchase orders● Stock transfer orders● Stock transfer requisitions● Sales scheduling agreements● Planned orders● Forecast● Forecast reduction (via GI booking in ERP)● Sales orders● Production orders● Process orders● Deliveries● ASN● Reservations● Stock

The following transactions are supported:

● /SAPAPO/SDP94 (APO)● /SAPAPO/MC90 (APO)● /SAPAPO/MD74 (APO)● SNP heuristic run (APO)● VA01/VA02 (ERP)● ME51/ME52/ME51N (ERP)● ME21/ME22/ME21N (ERP)● MD11/MD12 (ERP)● ME59N (ERP)● VL01N/VL02N (ERP)● /SAPAPO/RELEASE_FORECAST_TO_SNP (APO)● /SAPAPO/RRP1 (APO)


Change Monitor for LiveCache Orders

● /SAPAPO/RRP2 (APO)● /SAPAPO/RRP3 (APO)● Detailed Scheduling Planning Board (APO)● PP/DS Heuristics (APO)● COR1/COR2 (ERP)● /SAPAPO/BOPI (APO)

Prerequisites

You have installed the following SAP Notes:

● 2346966● 2372329

5.1 Authorizations and Roles

To use the Change Log Monitor for liveCache orders, you need to have certain authorizations assigned to your user profile, according to the action you want to execute with the Change Log Monitor for liveCache orders.

One or several roles can be assigned to your user profile, depending on the tasks that you have to perform.

For example, if a user is only supposed to view change records and make changes to the change log configuration, but shouldn’t be able to delete the change records, you would only assign that role to this user profile which allows the user to work with configurations and to view change log entries. Here, the user will not be able to use the report, Deletion of Change Records in Batch Mode.

The authorization object /APOTK/OB that is used, has the following activities:

● Activity H2 (Activate Logging) is necessary to create configuration entries with the transaction /APOTK/OBCLM_CONF.

● Activity 65 (Reorganize) is necessary to delete change log entries with the transaction /APOTK/OBCLM_DEL.

5.2 Displaying Logged LiveCache Orders

You use Change Monitor For LiveCache Orders to display the change log entries. You can enter the selection criteria that you want to apply to the list of logged liveCache orders.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit LVC Order Based Change log Monitor Change Monitor for liveCache orders (transaction /APOTK/OBCLM_DISP).

SAP Advanced Planning and Optimization, Data Management ToolkitChange Monitor for LiveCache Orders P U B L I C 23

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2346966

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2372329

2. In the pane Selection Criteria, enter the selection criteria for the list of logged liveCache orders. You can enter data in the following optional fields:

○ User○ Planning Version○ Order Number○ Product Number○ Location○ Category

As these fields are optional, you can also leave them empty. If you enter values for more than one selection criterion, then the selection criteria will be combined according to the AND principle. This means, for example, if you enter a value in Material and a value in Location, then the list of existing logged liveCache orders will have all objects that fit both criteria (that is, those that have the same material number and location number as the one entered.

3. In the pane Selection of Change Date/Time, you can restrict your selection for the next action to a time frame within which the change has to be made.

Every time a change is made to a document (and the change is written to the liveCache) the point in time at which the change was made is recorded . This is to ensure that you can later see in the change record when the change was made.

The time that you enter into Selection of Change Date/Time is displayed and maintained in the local time zone of the user who uses the change monitor.

If you want to see only the changes made in the last two weeks, you could set the date/time as follows:

Date: Today – 2 weeks To: Today

Time: 00:00 Till: 23:59:59

4. In the pane Selection of Changed Period, enter the time frame for which changes have been made. The changed time is the (new) requested date in a document.

If you want to see only the changes where the new requested date was set to a date within the next 4 weeks, you could set the date/time as follows:

Date: Today To: Today + 4 weeks

Time: 00:00 Till: 23:59:59

The times in the selection box are also in the local time zone of the user using the change monitor, and are converted into the UTC reference time during execution.


The result screen is displayed.

Related Information

Result Screen of Change Monitor for LiveCache Orders [page 25]



5.3 Result Screen of Change Monitor for LiveCache Orders

On the result screen you can view all existing logged liveCache orders that fit the selection criteria from the selection screen. All the fields are read-only. The report has a Refresh button which allows you to always view the current state of the logged data.

Of course not all of the information available might be useful for you , if you want to have a look at the change record. Some of the information (for example, internal GUIDs) is of a technical nature, and needs to be written to the change record to gather the other information.

You can customize the layout of the standard ALV grid to display information according to your needs.

The most important parameters of a changelog record are the following:

1. Planning Version, Order Number, Item Number, ATP CategoryChange records are recorded at the schedule line level. That means each change which leads to the creation, adjustment or deletion of schedule lines, leads to one or several new change record entries.

2. Change Time, Change UserThe two parameters tell you at which point in time the change was made and by whom.

3. Product, Location, SublocationThese three columns contain the product/location information. If, in the document, a sublocation was entered as additional information, then this sublocation should be in the field Sublocation.

4. Old date (requested), Old quantity (requested), New date (requested), New quantity (requested)These four columns contain information about the old requested date and quantity, and the new requested date and quantity.

5. Old date (confirmed), Old quantity (confirmed), New date (confirmed), New quantity (confirmed)These four columns are only relevant if an ATP check was executed for the document under investigation. Otherwise the old and new confirmed quantity will be set to 0 and the old/new dates will be set to the dates of the corresponding requested dates.

6. Old quantity (allocated), New quantity (allocated), Old quantity (withdrawal), New quantity (withdrawal)These four columns contain information about the old allocated and withdrawal quantities, and the new allocated and withdrawal quantities.

7. Old Location, Old Product, Old SublocationThe old location, product, sublocation information is shown in these columns. Except for the case where an order is created (and no old information is available) these columns should always be filled. So if for example, the document/item/schedule line was kept, but the location, product and/or sublocation was changed, you should be able to see it by comparing these values with the ones mentioned in point 3. Product, Location, Sublocation.

8. Change ActionThe change action can ease the analysis of the changelog entries. When a change record is saved, the system compares certain values in the change record (for example, the new dates/quantities against the old dates/quantities). The system then sets the appropriate change action indicator. The order object can have the following change actions:○ C: Order Created○ Q: Quantity Changed○ D: Date Changed○ X: Quantity and Date Changed○ R: Order Deleted○ U: Other Order Change (e.g. Change of Storage Location)


○ L: Location Changed○ P: Product Changed

So, by looking at the change action indicator first, you can quickly determine what change has been done to the document. However the change action indicator just mirrors the behavior of how schedule lines are managed in the liveCache. This is not done in the same way for all document types.For example, if you change the date on a purchase requisition, the corresponding schedule line in the liveCache will be adjusted, and you can see a change record later with the change action D: Date Changed.If, on the other hand, you change the date on an item/schedule line in a sales order, then the existing schedule line will not be simply adjusted in the liveCache. Instead the old schedule line will be deleted and a new schedule line, containing the new dates and quantities will be created. Therefore you will also have two change records in the database after a change of the date in a sales order. The first record would have the change action R (which means the schedule line has been deleted) and the second record would have the change action C (schedule line was created).

9. Calling Program, Transaction code, Background Indicator, Background job nameCalling Program should always be filled. It contains the program which was used to make the change to the document. The Transaction Code is usually filled if a program is executed in online mode via a transaction code, but is empty if the program has been executed in the background. The Background Indicator is a flag which shows you whether a program was executed online or in batch mode. The name of this background job should be filled in the column Background job name.

10. User name ECC and Transaction code ECCIf the change for which the change record was created happened in the ECC system, you will only see the name of the RFC user (usually generic, and which was used to transmit the change to APO) in the change record as change user.This will help you see that the change happened in the ECC system and was transmitted via the Core Interface (CIF) to APO.But if you want to find out which user in the ECC system triggered the change with which transaction, you need additional information.Therefore the two columns Username ECC and Transaction code ECC contain the information about the user and the transaction code from the ECC system. The columns are only filled if the change happened in the ECC system. If the change which led to the creation of the change record happened in APO, then these two columns will be empty.

5.4 Deleting Change Records in Batch Mode

You use Deletion of records in batch mode to delete obsolete change log entries.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit LVC Order Based Change log Monitor Deletion of records in batch mode (transaction /APOTK/OBCLM_DEL .

2. In the pane Selection Criteria, enter the selection criteria for logged liveCache orders deletion.. You can enter data in the following optional fields:



○ User○ Planning Version○ Order Number○ Product Number○ Location○ Category

As these fields are optional, you can also leave them empty. If you enter values for more than one selection criterion, then the selection criteria will be combined according to the AND principle. This means, for example, if you enter a value in Material and a value in Location, then the logged liveCache orders deletion will be applied to all objects that fit both criteria (that is, those that have the same material number and location number as the one entered.

3. In the pane Selection Of Change Date/Time, you can restrict your selection for the next action to a time frame within which the change has to be made.

The time that you enter into Selection Of Change Date/Time is displayed and maintained in the local time zone of the user who uses the change monitor.

If you want to delete only the changes made in the last two weeks, you could set the date/time as follows:

Date: Today – 2 weeks To: Today

Time: 00:00 Till: 23:59:59

TipYou should run the deletion report regularly, for example, to delete all data older than one week. We recommend that you keep the database table as small as possible for a better performance.

4. In the pane Test option, you can set the Test mode flag. In this case the selection will be done, but nothing will be deleted. Using this, you can view the number of records selected for deletion.


The result screen is displayed. Here you can see the execution log with the number of selected records, number of deleted records and so on, which fit all the selection criteria you entered on the selection screen.


5.5 Configuring Change Recording

You use Configuration of change recordingto configure the writing of the change logs.

Procedure

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization APO Data Management Toolkit LVC Order Based Change log Monitor Configuration of change recording (transaction /APOTK/OBCLM_CONF.

2. In the pane Selection Criteria, enter the selection criteria for logged liveCache orders deletion.. You can enter data in the following optional fields:

○ User○ Planning Version○ Product Number○ Location○ Category○ Calling Program

As these fields are optional, you can also leave them empty. If you enter values for more than one selection criterion, then the selection criteria will be combined according to the AND principle. This means, for example, if you enter a value in Material and a value in Location, then the list of existing configurations will be applied to all objects that fit both criteria (that is, those that have the same material number and location number as the one entered.


The result screen is displayed.

Related Information

Result Screen of Configuration of Change Recording [page 28]

5.6 Result Screen of Configuration of Change Recording

On the result screen you can view all existing configurations which fit ther selection criteria you entered on the selection screen. You can create, change and delete configurations.

You can also view some technical fields: Created By (user created a configuration), Changed By (user changed a configuration), Change Time (time of the last change). These fields are read-only.

During the configuration creation you can create one or several entries in which you define events for which liveCache order logs should be created.



Defining the Configuration Entries: First Section

In the first section of a configuration entry you define the field values for which a logging will be executed : User, Planning version, Product, Material Group, Location, ATP category and Calling Program (the program name was chosen instead of the transaction code, because the transaction code is not available in batch mode, while the program name is always determinable).

You can either enter concrete values (like 000 for the planning version) or you can enter the wildcard, (*). Use * when you don’t want to specify a particular value, and want to include all possible values.

NoteOnly the symbol * works as a wildcard character. Other commonly used wildcard characters (like ?) are not supported.

It’s not possible to work with mixed strings. For example, if you want to have logging enabled for all users starting with X04, and define a mixed string like this: X0*, it will not work. You either have to define individual entries for each user, or you have one entry with * as wildcard character, which means that logging will be enabled for all users. Don’t leave the cells blank - always enter a concrete value or the wildcard character.

User name in the configuration entryIf users execute transactions online, the changes that they make to the documents are saved with their user name (as the user who made the change to the order object in the liveCache). Then, the change is recorded, provided that you have defined an appropriate entry in the configuration. On the other hand, usually dedicated batch/CIF users are used to make changes for the following,: changes made by batch jobs, document changes made in the ERP system, and changes transferred through the Core Interface to APO . This has to be considered for the set up of the change monitor configuration.

Depending on the process for which the change recording is activated, a separate entry for the batch/CIF user (besides the entries for the online users) might be needed in the configuration of the change log monitor.

ExampleA user creates a purchase requisition in an SNP Planning book. The creation of this purchase requisition has to be recorded by the change log monitor. The user has the ID X12345. For the CIF transfer from the ERP system to APO, the user RFCDIAUSER is used.

This is how the process works technically:Figure 6: Purchase Requisition Creation with ERP Key Completion


1. The user creates the purchase requisition in SNP and saves the order.2. The order is created in APO with an APO order number. The dataset is written to the liveCache.3. Now, the system evaluates for the first time whether a change record should be created.4. If there’s an appropriate entry in the configuration settings (which contains the ID for the user who

created the document) a change record is written to the change record table. At this point in time, the change record contains the APO order number.

5. A request for an ERP order number is sent to the ERP system.6. The ERP order number for the purchase requisition is determined in the ERP system.7. The ERP order number is sent back to the APO system via the Core Interface. The update record is sent

with the user RFCDIAUSER.8. An update is made to the purchase requisition in APO. The APO order number is replaced with the ERP

order number in the document. Afterwards, the changed order is written back to the liveCache.9. Now it’s checked for the second time whether a change record should be written. The change monitor

has recognized that this isn’t really another change on the document (regarding dates/times and so on.) but just a replacement of the order number (key completion case). Nevertheless the existing change document in the change record database can only be updated if there’s an appropriate configuration setting in the change monitor configuration. In this case the configuration setting has to include the user RFCDIAUSER.

10. If an appropriate setting is found in the configuration settings, the existing change log entry is updated.

This example illustrates that you have to evaluate which configuration setting has to be made for the Change Log Monitor configuration, for each process to be recorded.

Defining the Configuration Entries: Second Section

The second section of a configuration entry contains the date/time settings (again in the local time zone of the user who maintains these settings) for which a change recording should be executed.



There are two subsections in this second section: The change date/time and the new requested date/time. It’s crucial to understand the difference between these two subsections.

The time frame entered for the change date/time is the time frame in which changes are done. That means every change that is done at a point in time which lies within the time span defined in the first subsection will be recorded. So the data entered in here has the same meaning as the one entered in the second selection box Selection of change date/time at the entry screen of the change log monitor.

On the other hand, the time span entered in the second subsection corresponds to the third selection box Selection of changed periods on the entry screen of the change log monitor. That means the new requested date in the document has to be situated within the timespan of the second subsection, for the change of the document to be recorded.

NoteFor the date/time settings, the wildcard character * is not permitted. If you want to ensure that the time frame that you enter into the subsections is not too narrow, set it as follows: 01.01.2010 00:00:00 – 31.12.2099 23:59:59. This has the same effect as the wildcard character : all changes are within this time frame and are therefore recorded.

Defining the Configuration Entries: Third Section

In the third section of the configuration entry, you can switch on or switch off change recording for changes which happen in background mode. You can also activate the respective configuration entry by selecting IA logging. Also, as described earlier, you can view the user that created a configuration, the user that changed a configuration, and the time of the last change.

Regarding switching off change recording in background mode, you may want to have the changes recorded if they are made by users in the online mode, but not when the changes happen due to a job that is scheduled in the background mode. So with this checkbox, you can control the recordings and distinguish between the changes that are made online and changes that are made in the background mode.

NoteOnly activated configuration entries will be taken into account. For an entry to be disregarded by the Change Log Monitor, you can deactivate it and don’t have to delete it from the configuration settings. To activate it again, select the checkbox IA logging.

In this report, you can choose Deactivate all entries to deactivate all configurations at once.

Related Information

Adjustment of Date Settings in Change Log Monitor Configuration [page 32]


5.7 Adjustment of Date Settings in Change Log Monitor Configuration

You have to set up dates (from and to) for the change horizon and the changed horizon.

This is described in Result Screen of Configuration of Change Recording [page 28].

If you do not want to restrict the change recording via the two horizons, you can set very broad time frames (for example, 01/01/2010 – 31/12/2099). On the other hand, if the horizons play a role in your change recording strategy, you can also define narrow time frames. If the time frames are narrow, the system will, at some later point, progress beyond the horizons defined in the configuration settings. Thus the change recording will stop if you don’t adjust the horizon settings before the horizon is crossed.

ExampleYou have defined the change horizon from today until two weeks into the future. This means that for the next two weeks changes will be recorded. But after the two weeks no changes will be recorded anymore. So if you still want the changes to be recorded after the two weeks, you have to alter the configuration settings and move the change horizon ahead again by 2 weeks.

You may have a rolling horizon for the changed horizon, for example, to have all changes recorded that affect due dates within the next four weeks. So if you set up the changed horizon today (From: today; to: today+4 weeks) , next week the change horizon will only cover three weeks (as one week would have passed). So you will have to alter the configuration settings again and move the changed horizon one week ahead.

Related Information

Result Screen of Configuration of Change Recording [page 28]

5.8 Change Recording Throughout the Lifecycle of a Document

You can use the change log monitor for different purposes. For example, you can set up change recording to find out what a certain planning run does and how it changes the documents or set up the configuration of the change log monitor just for certain document types. You can also use change log monitor for a seamless documentation of all changes done to a document, from its creation until the document is outdated, deleted or its requirements are transferred to a successor document.

For such a seamless documentation, ensure that you have set the configuration settings appropriately. Otherwise it could be that certain changes made to the document don’t match the settings in your configuration and therefore are not recorded.



ExampleYou have set up the change recording for all document changes that will be made in the next two weeks (Change date: today To: today + 2 weeks) and whose new requested date is within the next 4 weeks (Changed date: today to: today + 4 weeks).

Table 2: Example of Change Recording: Lifecycle of a Sales Order

Change Action Meets Change Date Time Frame

Meeets Changed Date Time Frame

Change Recorded

Order Created

New date (Requested): Today + 3 weeks

New quantity (Requested): 50 PC

Yes Yes Yes

Quantity Changed



Yes Yes Yes

Date Changed



Yes No No

Quantity Changed

New date(Requested): Today + 5 weeks


Yes No No

Quantity and Date Changed



Yes Yes Yes


5.9 Performance with Activated Change Recording

If change recording is activated, there will be impact on the performance of the transactions which are used to create, change and delete documents, and whose changes may be subject to the creation of a change record.

For each change that is done in the respective transaction, the change log monitor functionality is called, the configuration settings are checked against the data which is changed, old data is read from the liveCache (if the order is changed or deleted), the change record is assembled and finally it is written to the database. The impact on the performace will vary.

For online transactions (for example, like the product view (TA: /SAPAPO/RRP3) or the Interactive Demand Planning (TA: /SAPAPO/SDP94)) where the user only changes a view document, the performance impact is barely measurable.

On the other hand, if you have programs which manipulate a lot of documents in a very short amount of time, you could encounter a significant drop in the performance of these programs due to the change recording.

Some examples of programs which have to be taken into account when considering the performance implications are as follows:

● Batch programs which perform a mass update on a large amount of documents● Documents transfer through the Core Interface, if several hundreds of documents are transferred at once● Automatic planning runs like for example, the SNP Heuristic can cause performance issues if a lot of

documents are changed in the planning run.

As the performance of a system depends on several factors (such as number of changes made in which time frame, available hardware, system load caused by other processes, and so on), no general recommendation on how to set up the change log monitor can be given beforehand. You have to consider the performance situation for the specific case.

However, if you encounter performance issues, there are some guidelines on the parameters that can be changed in order to improve the system performance.

You can use the configuration settings described in Configuring Change Recording [page 28] to influence the system performance.

If you have no configuration settings or if the configuration settings are deactivated, you will have the best possible system performance (with regards to the system on which the change log monitor is installed).

If you want to log certain changes with the change log monitor and encounter performance issues, you can reduce the amount of changes that are logged.

The two best-suited parameters for improving the system performance are the user name and the program name. These two parameters are the first to be evaluated by the change log monitor functionality. If the change is done by a program and/or a user that is not in the configuration settings, thes system will leave the change log monitor functionality and will continue with the execution of the standard routines.

So to reduce the performance burden you could, for example, reduce the number of programs/users for which a change recording is executed.

The other parameters available in the configuration settings offer only slight improvement possibilities in terms of performance tuning. The reason is that for the other configuration settings the change log monitor has to create the respective change record first. Only then it checks against these settings in the configuration and decidse whether a change record should be written to the database. If data in the change record is in line



with the settings in the configuration, the record will be written to the database. If not, the record will be discarded.

The two parameters user name and program name are evaluated early on in the change log monitoring functionality. Reducing the scope on these two parameters should lead to a significant performance improvement. Reducing the scope on the other parameters can also lead to a performance improvement, but the performance gain will only be a little, as the change record has already been compiled in the background and only the process of writing the record to the database is skipped.

The report Configuration of change recording has a check on the number of wildcards (*), to caution you when you create configurations that can lead to performance issues. The program checks the list of configurations, which should be saved. If there is a configuration with more than 2 wildcards (*), the report gives you a warning message.


Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


Important Disclaimers and Legal Information

http://help.sap.com/disclaimer/

SAP Advanced Planning and Optimization, Data Management ToolkitImportant Disclaimers and Legal Information P U B L I C 37

go.sap.com/registration/contact.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx