Cross-System Update Logic 

Use

Inconsistencies can occur in an integrated system landscape if you change orders in parallel in SAP APO and SAP R/3, then save the changes and transfer them to the relevant target system. You can use cross-system update logic to prevent this type of data inconsistency without having to lock the objects on a cross-system basis. The cross-system update logic assigns a higher priority to order changes in SAP R/3 than to parallel changes in SAP APO.

Cross-system update logic influences system behavior in the following ways:

·        If an order is changed at the same time in both SAP APO and SAP R/3 and the changes are transferred to the relevant target system, SAP R/3 inbound automatically recognizes that the changes from SAP APO refer to an older data status than the situation in SAP R/3. The order changes from SAP APO are ignored.

·        If an order is changed in SAP R/3 and transferred to SAP APO while a change to the same order is being posted in SAP APO, SAP APO recognizes this situation when the order is saved and prevents the data from being saved. In dialog mode, you can choose whether SAP APO should save other orders from the same transaction or whether it should reject (rollback) the entire transaction. In background mode, the system always rejects the entire transaction.

·        Cross-system update logic is not active as standard.

Prerequisites

·        You are using SAP APO 4.0 and SAP R/3 Plug-In 2003.1.

·        Cross-system update logic is activated either in the CIF Customizing in SAP R/3 under Basic Settings for the Data Transfer → Change Transfer → Change Transfer for Transaction Data in the IMG activity Activate Cross-System Update Logic, or by calling transaction CFC9. Make the required settings under Update Logic for Manufacturing Orders, Update Logic for Networks, or Update Logic for Sales Scheduling Agreements.

Features

After the target system has been determined successfully, each change to an order in SAP R/3 means that the update counter is increased by the value 1. The current value of the update counter is transferred to SAP APO.

The update counter is not increased in the following situations:

¡        Transfer using an initial data transfer.

¡        Reconcile using the CIF compare/reconcile function.

¡        Transfer of a change from SAP APO that leads to the posting of the order in SAP R/3 and not to a retransfer to the calling SAP APO system.

¡        A target system could not be determined.

When you activate cross-system update logic, you can choose between the following settings:

...

       1.      Use update logic, no automatic retransfer

When parallel changes are made, SAP R/3 inbound uses the update counter to recognize whether different order statuses exist. If this is the case, the system rejects the change from SAP APO but the different order statuses are retained. You can then use the CIF comparison/reconciliation of transaction data in SAP APO to analyze and rectify this inconsistency.

       2.      Use update logic, automatic retransfer

As described above, the system recognizes different order statuses that exist. In this case, the current order status in SAP R/3 is automatically transferred to SAP APO, which ensures that cross-system data consistency is retained.