Processing Scheduling Agreements (SAP Library

Processing Scheduling Agreements

Use

Professional purchasers can now create purchase scheduling agreements in the Enterprise Buyer system.

Integration

After a scheduling agreement is created with the Process Contracts application, it is distributed to SAP APO and to the R/3 backend system.

An external procurement relationship with type scheduling agreement is created in SAP APO
An MM scheduling agreement is created in the R/3 backend system

During planning, APO generates schedule lines for this scheduling agreement and generates a scheduling agreement release. This is transferred to the R/3 System as schedule lines.

Subsequently, a goods receipt is posted and an invoice entered in the R/3 backend system against the scheduling agreement.

The goods receipt is transferred to SAP APO where the quantities are updated.

Purchase scheduling agreements are distributed to the R/3 backend system via the Middleware. They are transferred to APO via queued RFC (qRFC). Scheduling agreements are transferred when they are created and each time they are changed. You can use the reports CRM_APO_CONTRACT_UPLOAD and CRM_R3_CONTRACT_UPLOAD for initial data transfer.

Only scheduling agreements without errors and with status Released are transferred.

Prerequisites

You are using the Materials Management functionality in a backend R/3 System.

You are using SAP APO (Advanced Planner and Optimizer).

You have applied the SAP Notes 194969 (APO-CIF: Enhancement to EKPO-APOMS), 318477 (CRM scheduling agreements: Adjustments in the standard R/3 System), and 199028 (APO-CIF: Interface MM-PUR <-> APO 3.0A) in the backend R/3 System.

If you have installed the latest Support Package, you may not need to apply the above notes.

If you are using both the scenarios for direct materials and scheduling agreements with the same plant, you must have activated the user exits EXIT_/SAPAPO/SAPLCIF_G_EP_002 and EXIT_/SAPAPO/SAPLCIF_PUB_002. Normally, SAP APO cannot send purchase orders and scheduling agreement releases to different systems. However, contract release orders for direct materials have to be sent to the Enterprise Buyer system, whilst scheduling agreement releases orders are sent to the R/3 backend system. We recommend, in this case, that you define the R/3 backend system as default target system in the Customizing for SAP APO and that you use the user exit to define the conditions under which the Enterprise Buyer system is to be called.
You have performed the initial download of conditions from the R/3 backend system. For instructions, refer to the SAP CRM Setup and Download Guide (SDG). Although you will not need all the conditions, we recommend that you download them all as filtering out the conditions you do not require is time-consuming.
You have assigned the condition types you are using in Enterprise Buyer to the condition group you created.

Path in the Implementation Guide (IMG): Enterprise Buyer professional edition ® Purchase contract/Purchase Scheduling Agreement ® Define Condition Groups for Purchase Scheduling Agreement

You have defined a condition group and assigned the condition types you are using to this condition group.

Path in the Implementation Guide (IMG): Enterprise Buyer professional edition ® Purchase contract/Purchase Scheduling Agreement ® Define Condition Groups for Purchase Scheduling Agreement

You have entered the condition group you created in the item category type definition.

Path in the Implementation Guide (IMG): Enterprise Buyer professional edition ® Purchase contract/Purchase Scheduling Agreement ® Define Item Categories

You have entered the condition types you are using in Enterprise Buyer in table MNTCNT in the backend R/3 System.

Customizing Settings

Maintain Organizational Data Profile	You have defined the organizational data profile. You require the profile 000000000004 for scenario BBP. The purchasing organization and purchasing group are mandatory. Path in the Implementation Guide (IMG): Enterprise Buyer professional edition ® Purchase contract/Purchase Scheduling Agreement ® Maintain Organizational Data Profile
Set Texts	Default text types are supplied. You can use this Customizing activity to define further text types if required. Path in the Implementation Guide (IMG): Enterprise Buyer professional edition ® Purchase contract/Purchase Scheduling Agreement ® Set Texts
Define Date Types, Duration Types, and Date Rules	Standard date types are supplied. If you wish to define rules for how the contract start date is determined, you can do this using this Customizing a Do not delete the date types CONTSTART and CONTEND! Path in the Implementation Guide (IMG): Enterprise Buyer professional edition ® Purchase contract/Purchase Scheduling Agreement ® Define Date Types, Duration Types, and Date Rules

Features

Searching for Scheduling Agreements

On the left of the screen, there is a locator, which is divided up into the following areas: Find, Work list, Calendar.

Find	You can search for scheduling agreements using the following criteria: Vendor Status (open, in processing, released, completed, or any user-defined statuses) Transaction type: Purchase scheduling agreement, or any user-defined transaction type
Worklist	This tab card contains a list of the scheduling agreements to be processed. You can choose whether you want to process your own scheduling agreements (scheduling agreements in which you are entered as business partner), those for your department or those for your group.
Calendar	You can display a calendar.

For more information about the locator, see the CRM documentation Locator.

Scheduling Agreement Header Data

General	You select a vendor and a plant.
Administration	You can change the Posting date. In the standard version, the current day's date is defaulted.
Org. data	The purchasing organization and purchasing group are inserted automatically.
Price Agreements	In the scheduling agreement, unlike in the contract, price agreements are possible at header level. Unlike for contracts, there is no fixed condition groups. You can use any that have been defined in Customizing. Unlike in contracts, you can define discounts. For information about condition maintenance, see the CRM documentation Maintaining Conditions
Partners	You can choose a different address.
Status	You can display the status, that is, Open, In process, Released, Completed. You set status Released manually. This status is precondition for subsequent processes, that is distribution to APO and R/3, creation of a release call-off. You can also display the distribution status.

Scheduling Agreement Item Overview

Product	When you enter a product, the description, unit of measure, and product category are inserted automatically. A partner product ID may also be supplied.
Target quantity, target value	You can enter a target quantity or target value. (You normally enter one or the other, not both.) The release value and release quantity of the scheduling agreement are updated when a release order is ordered. Target value and target quantity are available at item level only. Currently, the target value and target quantity are not checked against the current value/quantity.

Scheduling Agreement Item Detail

Partner

The partner information is automatically taken over from the contract header. You can change the plant and user, but not the vendor.