Publication of Planning Results (SAP Library - SAP Advanced Planner and Optimizer (SAP APO))

Publication of Planning Results

Possible Uses

Report /SAPAPO/RDMCPPROCESS (transaction /SAPAPO/C5)

Planning results are published using the function module /SAPAPO/DM_CP_PUB . In this function module, orders that have been created, changed, or deleted by the APO application (SNP/PPDS) are transferred. Change pointers are either recorded or processed directly, in conjunction with a parameter. Change pointers are either recorded or processed directly, in conjunction with a parameter. Once they have been processed, the change pointers are deleted.

The APO system offers two types of retransmission:

a) Direct publication – valid for Production Planning and Detailed Scheduling

Changes to objects are directly extracted and sent using the APO system’s standard setting.

b) Periodic publication – valid for Supply Network Planning

Direct transfer is not carried out for the results from Supply Network Planning. Per default, here the results are called up via a report. This report is to be scheduled periodically.

The report is processed in the background and can be terminated at any time (menu path: System à Services à Job Definition)

Both the immediate and periodic modes are delivered as a standard setting for each application.

Prerequisites

To set up the retransmission of transactional data, you must define a receiving system in APO.

The Implementation Guide provides information on assigning a logical system: APO - Implementation Guide ® Advanced Planner and Optimizer (APO) ® Basis Settings ® Integration ® Business System Group.

The distribution definitions for the corresponding publication type must be defined for all objects that are new, that originated in APO, and that are to be transferred to an OLTP system (transaction /SAPAPO/CP1). Only in certain circumstances do distribution definitions have to be maintained for changed objects. For the following publication types, changes to object instances which have already come from an OLTP system can be sent without a distribution definition (this is because the information regarding which system the object instances came from is already saved in the APO inbox):

CO Sales order (expected from Support Package 4)
IP In-house production
EP External procurement
PC Production campaign
RV Manual reservations (expected only from Support Package 4)

For the following publication types, if the distribution definition is not maintained, no target system can be identified and no transfer can take place, even if the objects originated in the OLTP system:

FO Planned independent requirements
SH Transport
DL Delivery
CF Confirmation (IS Automotive)
CD Confirmation deletions (IS Automotive)
RP Reporting points (IS Automotive)
RV Reservations

Publication of planning results has changed fundamentally in APO Release 3.0A. The advantages of this change are:

Control of distribution, independent of Business System Group
Improvement in performance, thanks to the omission of key completion
Lookup information in inbound- and outbound processing allows realignment when changing distribution criteria of an object instance
Individual transfer blocks are independent, as objects are distributed over more channels

Process Flow