Data Exchange Between SAP APO and SAP R/3

Send Release (Customer)

The customer sends operative delivery schedules and forecast/planning delivery schedules by IDoc (DELFOR02).

Effects in the Systems Involved

SAP APO (Customer)	SAP R/3 (Customer)
Scheduling agreement schedule lines and release schedule lines from the operative delivery schedules are displayed in the product view/product planning table ( SchLne / SAg Rel. ) The operative delivery schedule and forecast/planning delivery schedule can be displayed in the function for displaying scheduling agreement releases.	If you work without confirmations, the schedule lines from the operative delivery schedule are transferred to the R/3 system when the release is created in the SAP APO system. In the external procurement relationship you can specify whether the schedule lines should be copied from the SAP APO system to the SAP R/3 system when the operative delivery schedule is created or when it is output. You define this in the external procurement relationship under update liveCache ( 10 – At Time of Generation of Operative Delivery Schedule, 40 – At Time of Output of Operative Delivery Schedule). If you use Internet releases then you can make the setting update liveCache ( 70 On confirmation of operative delivery schedule in SWP ). In this case, the schedule lines are only transferred to the SAP R/3 system when the vendor acknowledges the release in the Supplier Workplace . The called-up quantities from the operative delivery schedule are displayed in the requirements/stock list (MRP element SchLne ) and the scheduling agreement as scheduling agreement schedule lines. If you work with confirmations , the schedule lines from the operative delivery schedule are only transferred to the R/3 system when the confirmation is received.

SAP APO (Customer)

SAP R/3 (Customer)

Scheduling agreement schedule lines and release schedule lines from the operative delivery schedules are displayed in the product view/product planning table ( SchLne / SAg Rel. )
The operative delivery schedule and forecast/planning delivery schedule can be displayed in the function for displaying scheduling agreement releases.

If you work without confirmations, the schedule lines from the operative delivery schedule are transferred to the R/3 system when the release is created in the SAP APO system.

In the external procurement relationship you can specify whether the schedule lines should be copied from the SAP APO system to the SAP R/3 system when the operative delivery schedule is created or when it is output. You define this in the external procurement relationship under update liveCache ( 10 – At Time of Generation of Operative Delivery Schedule, 40 – At Time of Output of Operative Delivery Schedule).

If you use Internet releases then you can make the setting update liveCache ( 70 On confirmation of operative delivery schedule in SWP ). In this case, the schedule lines are only transferred to the SAP R/3 system when the vendor acknowledges the release in the Supplier Workplace .
The called-up quantities from the operative delivery schedule are displayed in the requirements/stock list (MRP element SchLne ) and the scheduling agreement as scheduling agreement schedule lines.
If you work with confirmations , the schedule lines from the operative delivery schedule are only transferred to the R/3 system when the confirmation is received.

Receive Release (Vendor)

The customer sends operative delivery schedules and forecast/planning delivery schedules by IDoc (DELFOR02). The due delivery schedule, which contains the requested quantities from both schedules, is generated in the vendor’s SAP APO system.

Effects in the Systems Involved

SAP APO (Vendor)	SAP R/3 (Vendor)
The requested quantities are displayed in the product view/product planning table ( SD SA Rel./<...>/Conf.). The operative delivery schedule, forecast/planning delivery schedule and due delivery schedule are displayed in master data maintenance for the sales scheduling agreement.	The confirmed requested quantities are transferred to the SAP R/3 system when the confirmation is generated.

Generate/Send Confirmation (Vendor)

You can manually or automatically confirm your customer’s requested quantities.

The confirmation is transmitted to the customer as an IDoc with the type DELFOR01 (Delivery Schedule/JIT Schedule ).

Effects in the Systems Involved

SAP APO (Vendor)	SAP R/3 (Vendor)
Confirmed quantities are displayed in the product view/product planning table ( SD SA Rel./<...>/Conf.). The requested quantities (in other words, the due delivery schedule) are displayed as SD SA Rel./<...>/Requst. The confirmed quantities are MRP-relevant (regardless of whether the confirmation has been sent to the customer or not). The confirmation is displayed in the sales scheduling agreement (master data maintenance of the sales scheduling agreement Delivery Schedules/Confirmations).	The confirmed quantities are displayed as schedule lines in the JIT or forecast delivery schedule in the sales scheduling agreement. Only the last confirmed quantities are displayed. The transfer of the schedule lines to the SAP R/3 system over the CIF is linked to the generation of confirmations. In the control profile you define whether the generation of schedules in the linked OLTP system is triggered by the confirmation and/or the due delivery schedule. This is defined using the following indicator: Planning Indicator Schedule Types defines how the MRP and delivery relevance of the operative delivery schedule and forecast/planning delivery schedule is set in the linked OLTP system. Release transmission specifies which data should be transferred to the linked OLTP system as a release when a confirmation is generated in the SAP APO system .

SAP APO (Vendor)

SAP R/3 (Vendor)

Confirmed quantities are displayed in the product view/product planning table ( SD SA Rel./<...>/Conf.).

The requested quantities (in other words, the due delivery schedule) are displayed as SD SA Rel./<...>/Requst.
The confirmed quantities are MRP-relevant (regardless of whether the confirmation has been sent to the customer or not).
The confirmation is displayed in the sales scheduling agreement (master data maintenance of the sales scheduling agreement Delivery Schedules/Confirmations).

The confirmed quantities are displayed as schedule lines in the JIT or forecast delivery schedule in the sales scheduling agreement.

Only the last confirmed quantities are displayed.

The transfer of the schedule lines to the SAP R/3 system over the CIF is linked to the generation of confirmations.

In the control profile you define whether the generation of schedules in the linked OLTP system is triggered by the confirmation and/or the due delivery schedule. This is defined using the following indicator:
- Planning Indicator Schedule Types defines how the MRP and delivery relevance of the operative delivery schedule and forecast/planning delivery schedule is set in the linked OLTP system.
- Release transmission specifies which data should be transferred to the linked OLTP system as a release when a confirmation is generated in the SAP APO system .

Receive Confirmation (Customer)

The customer receives the confirmation as an IDoc with the type DELFOR01 (Delivery Schedule/JIT Schedule ).

Effects in the Systems Involved

SAP APO (Customer)	SAP R/3 (Customer)
The confirmed quantities are displayed in the product view as elements with the category SA-ConfRel .	If you want to work with confirmations you must have selected the Process with Expected Confirmations on the Scheduling Agreement tab page of the external procurement relationship. This means that the schedule lines from the operative delivery schedule are only transferred to the R/3 system when the confirmation is received. In the procurement scheduling agreement only the schedule lines from the last (that is, the current) release are displayed. The confirmed quantities are displayed in the requirements/stock list (MRP element SchLne ) and in the scheduling agreement as scheduling agreement schedule lines. If you want to work without confirmations you must have selected the Process without Confirmations or Process with Confirmations in Exceptional Cases in the external procurement relationship. This means that the schedule lines from the operative delivery schedule are transferred to the R/3 system when the release is created in the SAP APO system.

SAP APO (Customer)

SAP R/3 (Customer)

The confirmed quantities are displayed in the product view as elements with the category SA-ConfRel .

If you want to work with confirmations you must have selected the Process with Expected Confirmations on the Scheduling Agreement tab page of the external procurement relationship.

This means that the schedule lines from the operative delivery schedule are only transferred to the R/3 system when the confirmation is received.

In the procurement scheduling agreement only the schedule lines from the last (that is, the current) release are displayed.
The confirmed quantities are displayed in the requirements/stock list (MRP element SchLne ) and in the scheduling agreement as scheduling agreement schedule lines.

If you want to work without confirmations you must have selected the Process without Confirmations or Process with Confirmations in Exceptional Cases in the external procurement relationship.

This means that the schedule lines from the operative delivery schedule are transferred to the R/3 system when the release is created in the SAP APO system.

Process with SNP

On the Scheduling Agreement tab page in the external procurement relationship you can set a Process Without Releases with Confirmation in SNP. This means that planning in Production Planning and Detailed Scheduling (PP/DS) or in Supply Network Planning (SNP) generates requirements (schedule lines with the ATP categories SchLne or SNP SA SL). These schedule lines are no longer transmitted to vendors in releases. Instead, vendors confirm the schedule quantities in Collaborative Procurement Planning in SNP, over the Internet.

For this process schedule lines must be confirmed because only then are they transferred to the linked SAP R/3 system and displayed in the product planning table/product view with the ATP category SA Conf-Rel. .

(See Procurement Scheduling Agreements in Heuristic-Based SNP Planning )

Post Outbound Delivery (Vendor)

The outbound deliveryis created in the vendor‘s SAP R/3 system and an ATP check can be carried out at the same time. It appears as the MRP element Deliv. in the requirements/stock list.

The outbound delivery data is transferred to the SAP APO system over the APO Core Interface (CIF). The delivery reduces or cancels out releases and confirmations in both systems.

Effects in the Systems Involved

SAP R/3 (Vendor)	SAP APO (Vendor)
The outbound delivery appears in the requirements/stock lists as MRP element Deliv. with the corresponding quantity. JIT and forecast delivery schedules are reduced or canceled out.	In the product view/product planning table ( SD SA Rel./<...>/Request), the requested quantity of the due delivery schedule is reduced by the amount of the delivery quantity). In the product view/product planning table ( SD SA Rel./<...>/Conf. ), the confirmed quantity is reduced by the amount of the delivery quantity. An element of the category Deliv. is generated in the product view/product planning table. The cumulative delivered quantity in the sales scheduling agreement is increased (master data maintenance of the sales scheduling agreement on the Scheduling Agreement tab page).

SAP R/3 (Vendor)

SAP APO (Vendor)

The outbound delivery appears in the requirements/stock lists as MRP element Deliv. with the corresponding quantity.
JIT and forecast delivery schedules are reduced or canceled out.

In the product view/product planning table ( SD SA Rel./<...>/Request), the requested quantity of the due delivery schedule is reduced by the amount of the delivery quantity).
In the product view/product planning table ( SD SA Rel./<...>/Conf. ), the confirmed quantity is reduced by the amount of the delivery quantity.
An element of the category Deliv. is generated in the product view/product planning table.
The cumulative delivered quantity in the sales scheduling agreement is increased (master data maintenance of the sales scheduling agreement on the Scheduling Agreement tab page).

Enter Shipping Notification/Post Inbound Delivery (Customer)

Inbound delivery takes place in the SAP R/3 system.

The inbound delivery data is transferred to the SAP APO system over the CIF. (Select the POs/Requisitions indicator in the integration model).

Effects in the Systems Involved

SAP R/3 (Customer)	SAP APO (Customer)
An MRP element PO memo (shipping notification) is displayed in the requirements/stock list. Either the delivery schedule line or the open quantity of the delivery schedule line is reduced.	In the product view an element with the category PO memo appears, for the amount of the notified quantity. Schedule lines, the release and the confirmation are reduced.

The status of the inbound delivery (which is assigned during parking with multi-level automotive goods receipt in the linked SAP R/3 system (as of DI 4.6C1)) is displayed in the SAP APO system.

If an inbound delivery is registered in the SAP R/3 system, the system assigns it the status In Plant . This status is displayed in the confirmation overview for the scheduling agreement.

The registered inbound delivery with the status In Plant is displayed in the SAP APO system in the product view/product planning table. The category of the inbound delivery changes from PO memo to In Plant .

Post Goods Issue (Vendor)

The goods issue takes place in the vendor’s SAP R/3 system and cancels the outbound delivery, reduces the stock and increases the cumulative issued quantity.

The goods issue data is transferred to the SAP APO system over the CIF.

Effects in the Systems Involved

SAP R/3 (Vendor)	SAP APO (Vendor)
The goods issue: Cancels the outbound delivery Reduces the stock Increases the cumulative issued quantity.	The goods issue: Reduces the outbound delivery (element Deliv. in the product view/product planning table) Reduces the stock (element STOCK in the product view/product planning table) Increases the cumulative issued quantity in the sales scheduling agreement.

Post Goods Receipt (Customer)

The goods receipt takes place in the SAP R/3 system and increases the cumulative received quantity and the stock.

Offsetting of the quantity of goods received takes place, based on shipping notifications.

Effects in the Systems Involved

SAP R/3	SAP APO
If you use shipping notifications then the goods receipt reduces the scheduling agreement schedule line and the notified quantity. If you do not use shipping notifications then the goods receipt reduces the scheduling agreement schedule line. The stock increases.	If you use shipping notifications then the goods receipt reduces the scheduling agreement schedule line ( SchLne ), the release ( SAg Rel. ), the confirmation ( SA Conf-Rel. ), and the notified quantity ( PO memo ). If you do not use shipping notifications then the goods receipt reduces the scheduling agreement schedule line, the release and the confirmation. The stock (element STOCK in the product view ( elements )/product planning table) is increased. The cumulative received quantity in the procurement scheduling agreement is increased.

SAP R/3

SAP APO

If you use shipping notifications then the goods receipt reduces the scheduling agreement schedule line and the notified quantity.
If you do not use shipping notifications then the goods receipt reduces the scheduling agreement schedule line.
The stock increases.

If you use shipping notifications then the goods receipt reduces the scheduling agreement schedule line ( SchLne ), the release ( SAg Rel. ), the confirmation ( SA Conf-Rel. ), and the notified quantity ( PO memo ).
If you do not use shipping notifications then the goods receipt reduces the scheduling agreement schedule line, the release and the confirmation.
The stock (element STOCK in the product view ( elements )/product planning table) is increased.
The cumulative received quantity in the procurement scheduling agreement is increased.