Outputting Scheduling Agreement Releases (SAP Library - Procurement Scheduling Agreement (SCM-APO-CPR-SCH))

Outputting Scheduling Agreement Releases

Use

The schedule lines in a scheduling agreement (SA) release inform the vendor of exact required delivery quantities and dates. The delivery schedule lines transmitted to the vendor in an SA release can be viewed at any time and you can trace their history (see Processing Scheduling Agreement Releases).

You can use this report program to send releases against APO scheduling agreements to the relevant source locations, (e.g. vendors) on a regular basis. You can transmit SA releases by e-mail, XML, or the Internet, or in hardcopy form and by fax.

In the SAP APO system, actions are generated for SA releases which you can then process (output). You use actions to control the creation and output of SA releases. (See also Setting Message Actions)

The Post Processing Framework (PPF) replaces message control (which has been used in SAP R/3 until now) and provides a standardized interface to any type of output medium. SAP Smart Forms are used for creating and maintaining forms for mass printing.

For more information, see the SAP Library for mySAP Technology Components under Post Processing Framework (PPF) and SAP Smart Forms (BC-SRV-SCR).

Note

This function can only be used to output SA releases against APO scheduling agreements. SA releases against OLTP scheduling agreements are output in the OLTP system.

For more information, see the SAP Library for Purchasing (MM-PUR), under Vendor Outline Agreements (MM-PUR-OA) → Scheduling Agreement.

Integration

Automotive / SAP for Discrete Industries

If you implement an SAP R/3 system (Automotive) then the unloading point stored in the additional data for the scheduling agreement is displayed as the Staging Area on the This graphic is explained in the accompanying text Scheduling Agreement tab page in the external procurement relationship.

If you want to copy the unloading point from the SAP R/3 system to the SAP APO system you must use the Customer-Exit CIFSRC01 (EXIT_SAPLCSRS_002 Customer Exit for Selecting Customer-Specific Scheduling Agreement Data).

SAP Enterprise Portals - Business Package for Automotive Suppliers

If you use Internet releases, then your vendors can view and acknowledge these releases in the Supplier Workplace (SWP), which your vendors can access over the Internet.

To make this possible, you must select Internet Rel. in the external procurement relationship and set the update of the liveCache there accordingly (70 – At Time of Confirmation of Operative Delivery Schedule in SWP). You make these settings to define at what time the schedule lines are transferred to the connected OLTP system (generally an SAP R/3 system).

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.

For more information about the Supplier Workplace, see the SAP Library for Discrete Industries under Link to external website Supplier Workplace.

Background documentation

For Internet releases, no actions are generated at the time that the release is created.

For more information see Procurement Using an APO Scheduling Agreement.

Prerequisites

Maintaining the Release Creation Profile

You can maintain a release creation profile in Customizing for Advanced Planning and Optimization, under Supply Chain Planning à Collaborative Procurement à Procurement Scheduling Agreement à Maintain Release Creation Profile. You can then assign it to an APO scheduling agreement in the relevant external procurement relationship.

For more information, see Release Creation Profile (APO-Scheduling Agreement).

Setting Messaging Actions

If you wish to output SA releases using this program, then Processing via selection report must be set as the dispatch time. (Supply Chain Planning → Collaborative Procurement → Procurement Scheduling Agreement →Define Actions for the Output of Scheduling Agreement Releases.)

Background documentation

You can set in the external procurement relationship whether the operative delivery schedule, that is its schedule lines, are transferred to the SAP R/3 system when the release is created or output in the SAP APO system. You define this in the update liveCache field (10 – At Time of Generation of Operative Delivery Schedule, 40 – At Time of Output of Operative Delivery Schedule).

For more information on the prerequisites, see Prerequisites for the APO Scheduling Agreement and Setting Messaging Actions.

Features

This report processes actions for scheduling agreement releases selected according to the criteria entered.

Activities

1. Choose Supply Chain Collaboration → Collaborative Procurement → Scheduling Agreement Releases →Issue Releases.

On the next screen, enter your selection criteria.

1. Select the desired scheduling agreements and choose This graphic is explained in the accompanying text .

A list of actions for SA releases appears.

There you see the status, indicating whether the action has been processed or not and if so, whether or not processing was successful.

The following statuses are possible:

This graphic is explained in the accompanying text Processed

This means that the SA release has already been output, but it can be output again.

This graphic is explained in the accompanying text Not yet processed

This graphic is explained in the accompanying text Incorrectly processed.

Background documentation

The application key you see in the list of actions is made up of the following:

- Scheduling agreement number

- Item number

- Release type (operative delivery schedule or forecast/planning schedule; technical values 1, 2)

- Release number

2. To output operative and forecast/planning delivery schedules, select the required actions for SA releases and choose This graphic is explained in the accompanying text .

You can also send actions for SA releases several times or choose another printer.

The SA release is sent to the address in the external procurement relationship. If no address is recorded there, it is sent to the address in the source location (address number in source location).

Further functions are available to you in the list:

This graphic is explained in the accompanying text Preview

If “printout” has been defined for the selected action for the SA release, you can view the print preview.

This graphic is explained in the accompanying text Processing log

The processing log is only available in the case of incorrectly processed actions for SA releases (status This graphic is explained in the accompanying text Incorrect).

During the output of actions for SA releases, the print-dependent data is updated. Print-dependent data is, for example, the data in the SA release such as the processing data (time stamp) or liveCache (if defined in the external procurement relationship).

Note

When displaying scheduling agreements, you see from the status which SA releases have already been sent.