Prerequisites for the APO Scheduling
Agreement
If you use APO scheduling agreements (with planning and release creation in the SAP APO system) then you should ensure that the following prerequisites are met in the SAP R/3 system and SAP APO system:
SAP APO System
APO Scheduling Agreement
You must transfer your procurement scheduling agreements to the SAP APO system. You can transfer the procurement scheduling agreements from the SAP R/3 system to the SAP APO system over the Core Interface (CIF). (See SAP R/3 System)
Procurement scheduling agreements are created as external procurement relationships in the SAP APO system.
In the external procurement relationship you must:
· Reassign the release creation profile (release creation profile)
· Select which schedule types (operative delivery schedules and forecast/planning delivery schedules) you want to use (Scheduling Agreement with Forecast)
If you want to work mainly with forecast/planning delivery schedules then you can use the Business Add-In (BAdI) /SAPAPO/PWB_TPSRC_IN to define that the indicator is automatically selected when the external procurement relationship is created. Using this BAdI you can also influence other data relating to the external procurement relationship or the transportation lane.
· Define at what time the schedule lines should be transferred to the SAP R/3 system (update liveCache)
· Define whether you want to send Internet releases (Internet release)
· Define whether you want to receive confirmations from your vendors (Process)
· Assign the confirmation profile (Confirmation profile).
Customizing – General Settings
In Customizing for Advanced Planning and Optimization (SAP APO), set external procurement for the destination location (for example, the plant) in the Publ.Type field under Basis Settings → Integration → Publication → Maintain Distribution Definition.
Authorizations
You can use the authorization object C_APO_EXPR to define which activities a user is allowed to carry out. For example, you can control whether a user can create releases, enter confirmations, or change master data.
Maintaining the Release Creation Profile
Define the release creation profile in Customizing for Advanced Planning and Optimization (SAP APO), under Supply Chain Planning → Collaborative Procurement → Procurement Scheduling Agreement → Maintain Release Creation Profile.
For example, you can define that schedule lines that lie in the past and have already been sent to the vendor are totaled and displayed as backlog in the operative delivery schedule. (Backlog is only transmitted in the operative delivery schedule).
You can also define whether the requirements date sent is the pickup date or the delivery date.
You then assign
this release creation profile in the external procurement relationship to the
scheduling agreement item on the 
Scheduling Agreement tab
page.
If you have maintained tolerances for the release creation in the release creation profile, then these are only taken into account if you use a constant planning calendar (for example, without weekends).
See also Release Creation Profile (APO Scheduling Agreement)
Stopping and Releasing Scheduling Agreement Releases
If you want to stop scheduling agreement releases, you must define the relevant criteria in Customizing for Advanced Planning and Optimization (SAP APO) under Supply Chain Planning → Collaborative Procurement → Procurement Scheduling Agreement → Maintain SA Release Creation Profile on the Dynamic Stopping tab page.
The SAP APO system can only stop releases against APO scheduling agreements, because in the SAP APO system, releases are generated against this type of scheduling agreement only.
The SAP APO system can only stop SA releases generated by the release creation program (transaction /SAPAPO/PWBSCH1).
SA releases generated manually in the product view are not stopped.
You can release stopped SA releases in the function for processing SA releases.
If you are using an SAP R/3 system (Automotive), you can also stop releases against OLTP scheduling agreements.
You can specify whether an SA release is to be stopped either in the additional data for the SA item (static stopping, that is, always), or in the SA release creation profile (dynamic stopping, that is, on the basis of certain criteria). You can specify this for each release type.
For more
information see the SAP Library for SAP for Discrete Industries under SAP for Automotive
→ Scheduling Agreement → Automotive: Enhancements for Scheduling Agreement
Releases (FRC or JIT Delivery Schedules) →
Stopping and Releasing SA Releases.
See also Stopping and Releasing SA Releases
Settings for Scheduling Agreement Releases Output (SAP APO System)
You must define the output of scheduling agreement releases in the SAP APO system.
For more
information on the settings for outputting scheduling agreement releases, see
Setting
Message Actions (Scheduling Agreement Release).
Inbound Delivery
If an inbound delivery is registered during parking with multi-level automotive goods receipt, it is given the status In Plant. This status is transferred from the SAP R/3 system to the SAP APO system over the APO Core Interface (APO-CIF) at the same time as the inbound delivery.
The system can take inbound deliveries with this status into account as category IW when calculating the days’ supply or the receipt days’ supply.
Make the necessary settings in Customizing for Advanced Planning and Optimization (SAP APO), under Supply Chain Planning → Production Planning and Detailed Scheduling (PP/DS) → Product Planning Table → Define Days’ Supply Types.
Display Last Deliveries
If you want to use this function, you must:
· In the R/3 system
¡ Assign a confirmation control key with the internal confirmation category 2 (inbound delivery) to the APO scheduling agreement.
¡ Transfer the data on the deliveries from the OLTP system to the APO system over the CIF.
To do so, set the POs/Requisitions indicator in the integration model of your OLTP system.
This means that the last deliveries are displayed in the external procurement relationship.
· In the SAP APO system
¡ Make the relevant settings on the Last Deliveries tab page in the release creation profile of the APO scheduling agreement.
This means that the last deliveries are determined when release creation takes place and sent to the vendor in the release.
The last deliveries are transferred from the SAP R/3 system to the SAP APO system over the CIF when inbound deliveries are created or changed and when goods movements take place and they are displayed in the external procurement relationship.
See also
Inbound Delivery,
Goods Receipt and Invoice/Credit Memo
Settings for Confirmation Receipt (CMDS)
If you receive confirmations from vendors within Collaborative Management of Delivery Schedules, then you must make settings for the process with confirmations for the relevant scheduling agreement item in the external procurement relationship.
For confirmations that you receive for SA releases, you can define in Customizing for Supply Chain Planning how incoming confirmations are checked, or under which conditions an alert is generated upon receipt of a confirmation.
The confirmation profiles (or procedures) delivered in the standard system control whether, upon receipt of a confirmation:
· An alert is always generated (no tolerance check).
If you only receive confirmations in exceptional cases then you should use the confirmation profile (Alert Always with Conf. Receipt), so that an alert informs you of every incoming confirmation.
· The current confirmation is compared with the last confirmation (tolerance check).
· The current confirmation is compared with the operative delivery schedule (tolerance check).
For the process with confirmation you must make the following settings in Customizing for Supply Chain Planning under Collaborative Procurement → Confirmation Receipt:
...
...
1. Define checking procedures
2. Define tolerance profiles
In the tolerance profile you can set an individual or a totals check.
¡ Individual Check
If you want an individual check of quantity and date pairs then you can either choose either an exact-to-the-day or to-the-second check. Select Check Time Stamp.
In this way you can define a more exact check for the near future and a more approximate check for the distant future.
¡ Totals Check
If you want to carry out the totals check for periods in your planning calendar then you must create a planning calendar in Customizing for Advanced Planning and Optimization under Master Data → Calendar → Maintain Planning Calendar (Time Stream), and assign this planning calendar to the tolerance profile.
3. Define confirmation profiles
4. Assign the confirmation profile to the required item in a procurement scheduling agreement in the external procurement relationship. (Master Data → Procurement Master Data → External Procurement Relationship).
See also:
Collaborative
Management of Procurement and Sales Scheduling
Agreements
Alert
Monitor for the Procurement Scheduling Agreement
Migration of Procurement Scheduling Agreements
For more information, see the SAP Note 658691.
SAP R/3 System
Document Type of Scheduling Agreement
As a rule, the APO scheduling agreement in the SAP R/3 system is a scheduling agreement with the document type LP or a scheduling agreement without release documentation.
If you use scheduling agreements of the document type LPA without confirmation control key then no default quantities can be determined from the release upon goods receipt.
If you use scheduling agreements of the document type LPA with confirmation control key then the default quantities from the confirmation (shipping notification) are used.
As a rule, the OLTP scheduling agreement in the SAP R/3 System is a scheduling agreement with the document type LPA.
Material Master
You should assign the MPR type X0 (W/o MRP with BOM Explosion) to the materials used. You do this in the material master, on the MRP 1 tab page.
Release Creation
The schedule lines and releases for APO scheduling agreements are generated in the SAP APO system. You specify this in the additional data for the scheduling agreement item by choosing the setting Generate and output SA release in APO for the External Planning indicator.
Note that you must not have any items with different External Planning settings in a scheduling agreement because this leads to problems in the message determination process. In other words, all items of a scheduling agreement must be planned either in the SAP APO system or in the OLTP system.
If delivery schedule lines already exist for an SA item, the setting for the External Planning indicator can no longer be changed.
Create and Activate Integration Model
Create an integration model that contains material masters, plants, delivery schedule items, vendors, stocks and purchase orders/requisitions (for transferring the release schedule lines or shipping notifications/inbound deliveries).
Activate the model.
In the SAP R/3 system, choose Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate.
Change Transfer
A change transfer only takes place for certain data, for example for External Planning (APOMS) or Deletion Indicator (LOEKZ) that are defined as change-relevant fields for the message type CIFSRC (APO CIF: Change Documents for Sources of Supply).
For a change transfer in SAP R/3, choose Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Change Transfer → Master Data.
If you want to transfer additional fields to SAP APO then you must add these fields to the change-relevant fields. For example, you can add the vendor material, that is used when confirmation are received to determine the relevant scheduling agreement.
Choose Tools → ALE → ALE Development → IDoc → Engineering Change Management → Define Change-Relevant Fields, to add fields.
For more
information about change transfers see
Distribute Master Data
Using the Shared Master Data Tool.
Customer-Specific Enhancements and BAdIs
As of SAP R/3 Release 4.6C with Plug-In PI 2001.2, the following enhancements are available:
SAP APO → SAP R/3
· CIFPUR02 (Enhancement Purchase Order Interface (Inbound),
To change purchase order data from the SAP APO System before a purchase requisition, scheduling agreement schedule line or a purchase order is created in the OLTP system.
· EXIT_SAPLCPUR_001 Customer Exit Receiver Module for APO Purchase Order Documents (Inbound),
To change scheduling agreement schedule lines for example.
SAP R/3 → SAP APO
· CIFPUR01 Enhancement for the Transmission of Customer-specific Purchase Order Fields (SAP R/3 → SAP APO)
EXIT_SAPLMEAP_001 – Customer Exit for Selecting Customer-Specific Purchasing Data, to control which scheduling agreement, contract and purchasing info record data you send from your SAP R/3 system to your SAP APO system.
· CIFSRC01 (Enhancement for the Transmission of Customer-specific Fields, Sources of Supply)
To control which data for scheduling agreements, contracts and purchasing info records are sent from the OLTP system to the SAP APO system.
· EXIT_SAPLCSRS_002 Customer-Exit for Selection of customer-specific scheduling agreement data
· EXIT_SAPLCSRS_004 Customer-Exit for customer-specific selection of vendor/plant location
SAP APO
· MMPUR Enhancements
¡ EXIT_/SAPAPO/SAPLMMPURREL_004, to change release header and schedule lines when the release is created in the SAP APO system.
¡ EXIT_/SAPAPO/SAPLMMPURREL_005, to change the IDoc data that is generated when release output takes place.
For more
information about Business Add-Ins see
Business Add-Ins for
External Procurement.
For more
information on the CIF, see the SAP Library for Advanced Planning and
Optimization (SAP APO) under
Integration of SAP APO
and SAP R/3.