The networks are locked. If a network cannot be locked, processing terminates and the system automatically tries to carry out processing at a later time.

Subject to the Customizing settings for the update counter, the system checks whether the changes made in SAP APO are based on the current version of the network in SAP R/3. If not, according to the Customizing settings, processing terminates or the networks that are not up-to-date are transferred again to SAP APO. For more information about update counters, see Cross-System Update Logic .

The activities of the network are not updated if the network is explicitly listed in table CT_AUFNR_SCHED_IN_R3 in method CHANGE_NETWORK_INBOUND in BAdI BADI_CIF_NETW_IN (that is, the capacity requirements of the network are planned in SAP R/3). The activities of the network are also not updated if the network activity dates received from SAP APO do not differ from the ones in SAP R/3.

The first start date of all network activities is entered as the scheduled start date and the last end date of all activities is entered as the scheduled end date. The fields for the order start date and order end date are not changed.

Networks that have been sent from SAP APO to SAP R/3 and have been updated in SAP R/3 are not retransferred directly to SAP APO.

The system checks whether the activity allows updates. Activities with the status ‘deleted’, ‘deletion flag’, technically completed’, ‘completed’, or ‘blocked’ cannot be updated. In such cases, processing of the SAP logical unit of work(SAP LUW) terminates.

The start and end dates from SAP APO are written to the fields for the earliest and latest dates of the activity in SAP R/3. The activity then gets the status ‘Date set by external system’ to prevent scheduling from moving the activity, and the status ‘Dispatched’ to ensure scheduling relevant fields can not be changed. No scheduling dates are set. If you want to change scheduling-relevant fields, you have to execute report PRJ_DEALLOCATE_NETW_ACTIVITIES in transaction SE38 for the network. This report deletes the statuses and you can enter data in the scheduling-relevant fields and change the dates during scheduling.

When scheduling the affected networks, the system adjusts the dates of objects below the activities, such as the dates of component requirements, purchase requisitions, activity elements, and so on.

The above data is transferred each time, but the data is changed in SAP APO only by an ATP check.

If SAP APO interchangeability has not occurred, the confirmed quantity from the ATP check and the missing parts indicator are updated.

The ‘confirmed quantity in SAP R/3’ = ‘confirmed quantity in SAP APO’ + ‘withdrawal quantity in SAP R/3’ is set, because in SAP APO the confirmed quantity always refers to the requirement quantity that is still open, whereas in SAP R/3 the confirmed quantity always refers to the requirement quantity.

If SAP APO interchangeability has occurred, a new follow-up reservation can be created, and the requirements quantity can be changed, because a part of the original requirements quantity is transferred to the substitution component.