Show TOC

 Enhancements: Reconciliation of Cumulative Quantities, Release Creation and Output

Use

In scheduling agreement processing, you can define cumulative quantity reconciliation or send additional data to your vendor in the release IDoc.

In scheduling agreement processing, customers and vendors can carry out reconciliation based on the quantities actually received (goods receipt) or the quantities promised by the vendor (inbound deliveries).

Integration

When reconciling the cumulative quantities, you can obtain information about cumulative quantity imbalances through an alert in the SAP Inventory Collaboration Hub (SAP ICH).

If the cumulative quantities of a scheduling agreement item differ from the cumulative delivery quantity, an alert is generated in the ICH and is displayed there in the Alert Monitor, in the Shipping Notification area.

For more information, see the SAP Library for mySAP Supply Chain Management under SAP Inventory Collaboration Hub (SAP ICH) .

Features

Reconciliation Using Cumulative Quantities

In the ERP scheduling agreement item, you can define which cumulative quantities are used as the basis for the reconciliation with your vendor. You can define whether you want to carry out the reconciliation on the basis of the actual quantities (that is, the goods receipt quantities) or the promised quantities (that is, the inbound delivery quantities).

In the ERP scheduling agreement item you can also prevent cumulative quantities from being transferred in scheduling agreement releases.

Note Note

If you do not want to send the cumulative quantities to the vendor in the release you can exclude the data from the transfer. You define this in the additional data for the ERP scheduling agreement item.

This setting is then transferred to SAP APO and displayed in the master data. In SAP APO, the system does not transfer any cumulative quantities to the vendor in the release for these scheduling agreement items.

End of the note.

This data is transferred from SAP ERP to SAP APO, and displayed on the Scheduling Agreement tab page in the external procurement relationship.

You can carry out reconciliation with your vendor once a year or you can correct the agreed cumulative quantities at any time during the year.

It may be necessary for you to inform your vendor by system message or email that you are planning to carry out a reconciliation.

Release Creation (Service Parts Planning)

When creating releases, the system checks the release status of the SA item. This means that the SA item must have the status RELOK ( OK to Release ) in order for a release to be created.

The system only checks the release status if you are working with Distribution Requirements Planning (DRP) within Service Parts Planning (SPP).

You can find the distribution resource planning (DRP) functions in the SAP Easy Access menu under Start of the navigation path Advanced Planning and Optimization Next navigation step Service Parts Planning (SPP) Next navigation step Planning Next navigation step Distribution Requirements Planning (DRP) Next navigation step Scheduling Agreement Releases End of the navigation path .

The release is carried out in External Procurement - Delivery Schedule Maintenance . Start of the navigation path (Scheduling Agreement Releases Next navigation step External Procurement – Delivery Scheduling Maintenance) End of the navigation path

Note Note

You cannot use OLTP delivery schedule items for Service Parts Planning (SPP) because schedule lines in the planning horizon, for example, that have been sent to the vendor in a release, can no longer be deleted in SAP APO.

You cannot change schedule lines relating to OLTP scheduling agreement items in SAP APO, in the functions: Planning Service for Distribution Requirements Planning, External Procurement - Delivery Schedule Maintenance (transaction /SAPAPO/SPPDRPSB), product planning table (transaction /SAPAPO/RRP3) or SNP planning board.

End of the note.

You can also use the Business Add-In (BAdI) SMOD_MMPUR ( BAdI: Enhancements for Procurement Scheduling Agreement ) to influence release creation.

Using the method READ_TPSRC of Business Add-In SMOD_MMPUR ( BAdI: Enhancements for Procurement Scheduling Agreement ), you can override the fields of the release creation profile or enter data from the product master in these fields.

Creating Releases and Reconciliation Using Agreed Cumulative Quantities

If the system re-determines the agreed cumulative quantity in SAP ERP on the planned execution date, the system will create a release even if the schedule lines have not changed. (The cumulative quantity sent to the vendor in the next release is set to 0 or is significantly less after the cumulative quantities have been reconciled.)

The release contains the existing schedule lines and the updated cumulative quantities.

If you manually correct the agreed cumulative quantities in SAP ERP, the system does not create a release.

Release Output

You can use the new Smart Form /SAPAPO/SF_SARELEASE_TEMP_SPP to output releases. This contains fields such as the reason for ordering.

There are six rows with 70 characters each for each note.

Release Transmission by IDoc

In this process, you can transfer additional data in the IDoc DELFOR02 Delivery Schedule/JIT Schedule (message type DELINS) to your vendor.

The following data is transferred again and filled in segment E1EDP16 Schedule Lines Forecast/JIT Delivery Schedule for Suppliers , in which the schedule line data is transferred:

  • Reason for Ordering (BSTGRU)

    The reason for ordering is displayed in delivery schedule maintenance for external procurement (transaction /SAPAPO/SPPDRPSB).

  • The means of transportation (TRANSPTP and description TRANSPDESC) are transferred.

  • Inbound Delivery Date (LDATUV – Planned Goods Receipts Date “From” , LZEIT – Scheduled Goods Issue Time , LDATUB – Planned Goods Receipt Date “To” )

  • Outbound Delivery Date (WDATUV – Scheduled Goods Issue Date From , WZEIT – Scheduled Goods Issue Time , WDATUB – Scheduled Goods Issue Date To )

    Background documentation 

    The inbound and outbound delivery dates are transferred in the IDoc.

  • In SAP APO, the system transfers the reconciliation date and the agreed cumulative quantities in segment E1EDK09 in the fields CYEFZ and CYDAT (for technical reasons, this can only occur in SAP APO as only one release can only be sent per IDoc; not in SAP ERP).

    The field ABDAT Reconciliation Date for Agreed Cumulative Quantity is used in SAP ERP.

  • Notes

    Notes are transferred in the fields TXT01 - TXT14 in segment E1EDP15 – Item Texts Forecast/JIT Delivery Sched. for Suppliers.

    You can create notes on the Note to Supplier tab page for external procurement documents.

    Background documentation 

    Depending on the control type specified in the scheduling agreement item, the system enters the following data (depending on the settings of the control type in the additional data of the scheduling agreement item, the system calculates the dates based on the customer’s goods receipts or the vendor’s inbound deliveries):

    • AKUEM – Current Cumulative Quantity Received

    • MFADT – Cumulative Production Go-Ahead Quantity Requirements

    • MFRFZ – Material Go-Ahead for Cumulative Requirements

    • FZABR – Cumulative Received Quantity of the Schedule Line

    • /SAPAPO/WMENG – Released Quantity/Requested Quantity

For more information, see the documentation on Service Parts Planning (SPP) .