Release processing in SAP Supply Network Collaboration (SAP SNC) supports procurement processes on the basis of scheduling agreements. A scheduling agreement is an outline agreement between a customer and a supplier. It specifies the total quantity of the products that a supplier is to deliver to the customer in a specific time period. The customer performs exact planning at regular intervals and determines what exact demand quantities are to be released from the scheduling agreement on certain dates. To inform the supplier about the current demands, the customer sends a scheduling agreement release for one or several products to SAP SNC. For each item, the scheduling agreement release contains schedule lines. Each schedule line contains a demand for a product with a quantity and a date/time. In Forecast (FCT) type Schedule Lines it is common to define the start and the end date of the Delivery. If the interval is typical, the Period on Release Details screen can be "Day", "Week" or "Month". In any other cases the period will be displayed as "Interval".
The supplier can display the releases in the SAP SNC Web interface (Web UI) and supply the customer based on the schedule lines in the up-to-date release. To inform the customer about probable delivery quantities and date/times, the supplier (or the customer on behalf of the supplier) can create scheduling agreement confirmations in the SAP SNC Web UI. The customer can see the scheduling agreement confirmations in the SAP SNC Web UI. To inform the customer about a forthcoming delivery, the supplier sends the customer an advanced shipping notification (ASN). The supplier can create the ASN manually in SAP SNC or send it from his or her backend system.
When the customer updates his or her planning, that customer sends a new scheduling agreement release to SAP SNC. This replaces the predecessor release, and the supplier delivers on the basis of the new release. Both the customer and the supplier can view the delivery progress details in release processing. This includes the cumulative received quantity or data for the deliveries that have already been made.
There are special release alerts in SAP SNC for release processing. SAP SNC can use alert notifications to notify a supplier (for instance by e-mail or by fax) in the following cases, for example:
- When a new release has arrived.
- When the supplier has not yet confirmed acknowledgement of the release in SAP SNC after a certain deadline has passed.
Therefore, the supplier only has to call release processing specifically if his or her intervention is required.
Scheduling Agreement Release
- ME32L - Change Scheduling Agreement
- ME38 - Maintain Sched. Agreement Schedule
- /SAPAPO/SPPDRPSB - Ext. Procurement - Schedule Maint.
- /SAPAPO/PWBSCH1 - Create SA Release(s)
|/SCA/DM_BOL_REL_READ||Can be used to display releases in SAPGui|
|/SCMB/DM_BOL_REL_MES_CREATE||Can be used to simulate incoming DSN XML message; create new version of release||Most systems have a variant maintained|
|/SCA/DM_BOL_REL_DELETE||Can be used to delete old releases|
|/SCA/BIF_I_DELSCHED||BAdI for XML-Interface DeliveryScheduleNotification_In|
|/SCA/BIF_MI_ITMBPRT||BAdI for Mapping the Item-BuyerParty (Inbound)|
|/SCF/DS_DOWNLOAD||BAdI for Release Excel Download|
|/SCF/ICH_DUELIST||Due List, R/R List, Calculation of Due Quantity|
|/SCF/RELEASE_UI||BADI for Release Overview and Detail Screen|
|/SCA/REL_UNLOAD_PNT||Update Unloading Point Master Data for Release|
|/SCA/UNACKNRELBADI||Read the number of days|
|/SCA/BOL_REL_LANGU||BAdI: Language for Printing Scheduling Agreement Releases|
|/SCMB/SV_RELEASE||BAdI: Processing of Scheduling Agreement Releases|
|/SCA/CL_SVRELEASE||This is the main BOL object that does the BOL logic|
|/SCA/CL_RELEASE||This performs the mapping between BOL and ODM, save and read|
|/SCF/CL_FRMBOX_CUMQTY||This is the UI class od the Cumulative Quantity tab on release details|