Purpose

In procurement using OLTP scheduling agreements, SA delivery schedule lines and SA releases (specific types of delivery schedule) are only generated in the OLTP system.

In this process, you first create purchase requisitions in SAP APO that reference an OLTP scheduling agreement. You must convert these purchase requisitions into schedule lines, either in SAP APO or in the OLTP system. These OLTP schedule lines are fixed in SAP APO and cannot be changed.

During release creation in the OLTP system the schedule lines and the purchase requisitions can be copied to the release. In the release the vendor receives both the schedule lines for the short-term and purchase requisitions for the more distant future.

As soon as inbound deliveries and goods receipts relating to the SA releases are created in the OLTP system, the relevant data is transferred to the SAP APO system.

Invoices are also posted in the OLTP system.

The following figure illustrates the process (with conversion in SAP APO):

Prerequisites

In order for a scheduling agreement item to be planned as an OLTP scheduling agreement in the SAP APO system, the following conditions must be fulfilled in the OLTP system:

In the additional data for the scheduling agreement item, choose the settingGenerate and output SA release in R/3for the External Planning indicator.

In most cases, the OLTP scheduling agreement in the SAP R/3 system is a scheduling agreement with the document typeLPA, for whose document type the Release Docu. indicator has been set under Scheduling Agreement → Define Document Types in Customizing for Purchasing.

If delivery schedule lines already exist for an SA item, the setting for the External Planning indicator can no longer be changed.

Transfer the SA item to the SAP APO system via APO Core Interface (CIF) .

If you want to send unconverted purchase requisitions in the SA release you must use the customer exitMEETA001 (EXIT_SAPLEINL_001). For more information and for example coding, see SAP Note 409394.

For more information about the prerequisites, see Prerequisites for the OLTP Scheduling Agreement .

Integration

If you want to work with Internet releases, you must use the Supplier Workplace (SWP), which your vendors can access via the Internet. Your vendors can display and acknowledge scheduling agreement releases via the Internet. In addition, they can access certain information about the scheduling agreement, delivery schedule lines, goods receipts, agreed prices and so on, in the customer system.

If you want to use Internet releases, you must specify this by means of the Activate Internet Release indicator in the release creation profile on the Internet tab page.

If your vendor wants to view his or her Internet releases in the Supplier Workplace, not only the Internet releases from the SAP R/3 system are selected and displayed, but also those from the SAP APO system. These are transferred from the SAP APO system to the SAP R/3 system by RFC.

(See Procurement Using an APO Scheduling Agreement ).

For more information about the Internet release, see the SAP Library for Materials Management (MM) under MM – Purchasing in the section http://help.sap.com/saphelp_470/helpdata/en/6e/637b38180fee45e10000009b38f8cf/content.htmInternet Release and for SAP for Discrete Industries under SAP for Automotive in the section http://help.sap.com/saphelp_di46c2/helpdata/EN/fe/1371386afa2045e10000009b38f889/content.htmSupplier Workplace .

Process

Procurement using an OLTP scheduling agreement is carried out as follows:

In automatic or interactive planning, a source of supply of the procurement category OLTP scheduling agreement is determined to cover a product requirement. A purchase requisition is created in the SAP APO system and a corresponding purchase requisition is automatically generated in the OLTP system. The relevant item of the OLTP scheduling agreement is assigned to this requisition as a fixed source of supply.

You convert these purchase requisitions into schedule lines, either in SAP APO or in the OLTP system. After this conversion the schedule lines are fixed and are available both in SAP APO and in the OLTP system.

You should note that OLTP schedule lines are fixed in SAP APO and cannot be changed. For this reason, you should only convert purchase requisitions that you no longer wish to use in planning (for example, purchase requisitions within the delivery time).

If the resulting requirement is higher planning does not adjust the fixed OLTP schedule lines; instead it generates new purchase requisitions.

See the example below.

You can convert a purchase requisition in the SAP APO system into a schedule line in the following ways:

In SAP APO

You convert the purchase requisition into a schedule line in SAPAPOby setting the conversion indicator for the purchase requisition.

You can either carry out the conversion interactively (for example, in the product view) or in the background ( Production Planning → Manufacturing Execution → Conversion of Orders/Purchase Requisitions ).

In conversion in the background, you can select the purchase requisitions that you want to convert based on the opening date. This means that only purchase requisitions with a date that is close to today’s date are converted.

For more information about converting purchase requisitions in the SAP APO system, see Mass Transfer and Mass Conversion of Orders .

The following figure illustrates the process:

In the OLTP System

Youconvert the purchase requisition in the OLTP system, for example, in the function for processing assigned requisitions. After this conversion the schedule lines are fixed and are available both in SAP APO and in the OLTP system.

For more information about processing assigned purchase requisitions in the SAP R/3 system, see the documentation for Purchasing(MM-PUR), section Optimized Purchasing (MM-PUR-SQ) .

The following figure illustrates the process:

In the OLTP system you generate SA releases (forecast or JIT delivery schedules) for these schedule lines and output them.

To copy unconverted purchase requisitions, in addition to the schedule lines, to the SA release you must use the customer exitMEETA001 (EXIT_SAPLEINL_001). (See SAP Note 409394).

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

You post inbound deliveries received from your vendor relating to an SA release in your OLTP system. The data is then automatically transferred to the SAP APO system. The notified quantity reduces or cancels out the schedule lines and SA releases.

When the product is delivered, you post the goods receipt in your OLTP system. The data is automatically transferred to the SAP APO system. There, the stock figure increases and the schedule lines and SA releases are reduced or canceled out accordingly.

Invoices received are posted in the OLTP system. If the OLTP system is an SAP R/3 system, you can also use the Evaluated Receipt Settlement (ERS) function.

For more information, see Inbound Delivery, Goods Receipt, and Invoice/Credit Memo .

For more information, see the documentation for External Procurement under Planning and Source of Supply Determination in External Procurement .

Example

You need a product on four different dates in the month of October.

Purchase requisitions (PRs) are then generated for these requirements in planning. You then convert only the first two purchase requisitions into schedule lines. The converted purchase requisitions are deleted and the schedule lines are fixed.

Since you are using the relevant customer exit, not only both schedule lines but also the requirements from both PRs are sent to the vendor during the release creation process.

The following figure illustrates the process: