Show TOC

 Transfer to Compare Project Orders/Networks

Use

You can execute a comparison/reconciliation, also known as a delta report, in SAP APO to compare the network headers in SAP APO for selected plants with the networks that exist for those plants in SAP R/3. You can also select whether the network activities and component requirements should also be compared.

Subject to the result of the comparison, you can select project orders to:

Delete them in SAP APO

Update them from SAP R/3 ( refresh transfer )

Integration

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 .

When triggered by the delta report for comparison purposes, the following data is collected in SAP R/3 and passed to SAP APO:

All combinations of network type and plant are read from the SAP R/3 database, if they contain the plants selected by you and are contained in an integration model. To avoid performance problems, you should enter at least one plant in your selection.

SAP R/3 determines the network headers that have a network type and plant that match the combination of network type and plant found. The following is not passed to SAP APO:

Networks with status ‘deleted’, ‘deletion flag’, ‘technically completed’, and ‘completed’

Networks without operations

Networks that are not contained in an active integration model

Subject to the data you request, SAP R/3 also reads the activities and component requirements of the remaining networks from the database.

SAP R/3 data is filtered and converted. It is then passed to the calling function module, which uses the data only for comparison purposes and therefore does not update it to the live Cache.

In SAP APO, a list of networks appears for which the report has determined differences. If you use iteration, you can trigger retransmission to compare the incorrect networks again. In such a case, SAP R/3 reads only the network headers from the database that appear in the list of incorrect networks.

You can trigger an update of a network that contains differences by transferring the network data from SAP R/3 to SAP APO (refresh transfer). SAP APO updates the data in the live Cache.

Business-Add-Ins (BAdIs)

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

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/notesInformation published on non-SAP site .

See also:

Initial Data Transfer for Project Orders/Networks

Change Transfer and Deletion for Project Orders/Networks

Refresh Transfer to Update Project Order/Network Data

Data Transfer

CIF Error Handling

CIF Comparison/Reconciliation for Transaction Data