Change Transfer and Deletion for Project Orders/Networks

Use

If a network is changed and saved in SAP R/3, the current status is transferred automatically to SAP APO if the network type and plant exist as filter objects in an active integration model. This also applies when confirmations are posted for the network. This does not apply if goods issues are posted for a network, because goods issues trigger a transfer of stock and reservation updates in SAP APO if they are contained in an active integration model.

Integration

This graphic is explained in the accompanying text.

This section describes only the aspects that differ from those during the initial data transfer. You should read this section together with Initial Data Transfer for Project Orders/Networks . You do not need to generate an integration model again, unless you create new network types or plants

Change Transfer and Deletion

Networks with statuses ‘deleted’, ‘deletion flag’, ‘technically completed’, and ‘completed’ are transferred to SAP APO and deleted in SAP APO.

The update counter increases by one if you have set the usage of update counters in Customizing. For more information about update counters, see Cross-System Update Logic .

If an activity is confirmed or a confirmation for an activity is canceled, SAP R/3 checks whether the activity has the status Date Set by External System . If so, that status and the Dispatched status of the confirmed activity are reset and the whole network is scheduled. However, activities in the network that have the status Date Set by External System keep their dates. For confirmed activities, the remaining work (and possibly the dates) is adjusted. After scheduling, the network is sent to SAP APO.

If you plan capacity requirements of a network in SAP R/3, that is, you explicitly name a network in Business Add-In (BAdI) BADI_CIF_PS_NETWORK and BADI_CIF_PS_NETW_IN as being scheduled in SAP R/3, it does not have the status Date Set by External System and, therefore in the standard case, it is not scheduled after a confirmation. As a result, in SAP R/3 the planned start/end dates are not adjusted to the actual dates. Since in SAP R/3 component requirements are aligned to the planned start/end dates, in SAP APO the planned start/end dates determine the start and the end of the activity. Partially confirmed activities have the status Started in SAP APO.

Business Add-Ins (BAdIs)

BAdIs in SAP R/3 and SAP APO enable you to control the transfer of the data. For more information, see Enhancements for the Integration of Project Orders/Networks .

Monitoring of Transferred Data

This graphic is explained in the accompanying text.

If several networks are changed simultaneously, they are registered only in one queue that can have only one network number in its name.

You can monitor the data that has been transferred to SAP APO. For more information, see Monitoring .

If problems occur during the transfer, you can use core interface (CIF) error handling, where you can trigger retransfer of the networks. For more information, see Transfer to Compare Project Orders/Networks , Refresh Transfer to Update Project Order/Network Data , and CIF Error Handling .

Prerequisites

The following settings are required to transfer networks to SAP APO:

An RFC connection exists between SAP R/3 and SAP APO.

The relevant master data and transaction data is integrated with SAP APO.

An active integration model exists for networks

SAP Notes 689172, 695304, and 713675. For more information, see these notes on the SAP Service Marketplace at http://service.sap.com/noteshttp://service.sap.com/notes .