Validation of Supplier Confirmations (Áèáëèîòåêà SAP - Àíàëèç íåäîïîêðûòèÿ ïîòðåáíîñòè)

Show TOC

Validation of Supplier Confirmations

Use

SAP Supply Network Collaboration (SAP SNC) performs a standard validation for the following supplier confirmations:

● Scheduling agreement (SA) confirmations

● Purchase order (PO) confirmations created in Extended Confirmation Management (ECM)

● Location product confirmation (LP confirmation)

Çàìåòêà

LP confirmations are only relevant for shortage analysis in Service Parts Planning of SAP Advanced Planning and Optimization (SAP APO). For more information, see SAP Library for SAP APO under Service Parts Planning ® Analysis, Monitoring, and under Reporting for Service Parts Planning ® Shortage Analysis ® Shortage Monitor ® Processing Location Product Confirmations.

In this document, you find an overview of the processes in which SAP SNC executes validation, and the standard validation profiles that SAP SNC uses for these processes.

Validaton of Activities on the Web User Interface (Web UI)

The following table contains processes and profiles for activities on the Confirmation tab page for SA confirmations and on the ECM confirmation screen:

Process	Technical Process Name	Validation Profile	Note
The supplier saves the confirmation as a draft (by using the Save function for a confirmation that has the status To Be Saved as Draft or Draft).	SCONF_SAVEDRAFT	SCN2	None
The supplier publishes a confirmation (by using the Save function for a confirmation that has the status To Be Published).	SCONF_SAVEPUB	SCN1	Relevant for PO confirmations: If the PO confirmation has been successfully validated and saved with the status Published, SAP SNC updates the PO using the ORDERSCON_SAVE process: SAP SNC copies the confirmation schedule lines to the purchase order and updates the confirmation status of the PO. For more information, see Purchase Order Status and Validation in Purchase Order Collaboration.
The supplier publishes a confirmation that has already been published once (by using the Save function for a confirmation that has the status Published). The customer reviews a confirmation and changes the review status to Reviewed or On Hold.	SCONF_SAVE	SCN0	Relevant for PO confirmations: If the PO confirmation has been successfully validated and saved, SAP SNC updates the confirmation schedule lines and the confirmation status of the purchase order. For more information, see note for SCONF_SAVEPUB process.
The supplier cancels a confirmation.	SCONF_CANCEL	SCNX	The SCNX profile is used for manual cancellation on the confirmation screen and for background processes (see below). Since these processes must always be possible, the profile does not contain validation checks in the standard system.

For more information, see Creating Scheduling Agreement Confirmations and Processing of SA and PO Confirmations on the Confirmation Screen.

Çàìåòêà

On the ECM confirmation screen, the supplier can publish a purchase order (by using the Publish PO function for a PO confirmation that has the status Published). This process (ORDERSCON_PUBLISH) uses the standard validation profile POC3 for the publication of POs. For more information, see Validation in Purchase Order Collaboration.

Validation in Background Processes for ECM and LP Confirmations

The background processes use the SCNX profile. Since these processes must always be possible, the profile does not contain validation checks in the standard system (also see manual cancellation in the Validation of Activities on the Web User Interface (Web UI) section above). The following table contains the background processes:

Process	Technical Process Name	Validation Profile	Note
The supplier sends a purchase order confirmation from his or her backend system to SAP SNC by EDI.	SCONF_SAVEPUB_EDI	SCNX	Since the SCNX profile does not contain validation checks (see above), SAP SNC checks the purchase order using the validation checks of the REPLORDER_CONFIRMATION purchase order process. For more information, see Validation in Purchase Order Collaboration.
The report for updating the statuses for confirmations on the basis of ASNs assigns ASNs to a confirmation. For more information, see Update Confirmations Based on ASNs.	SCONF_CLOSE_BY_ASN	SCNX	None
The report for updating the confirmation based on ASNs closes an overdue confirmation. For more information, see Update of Supplier Confirmations.	SCONF_CLOSE_ODUE	SCNX	None
SAP SNC closes an obsolete confirmation schedule line when a changed purchase order arrives. For more information, see Closing Purchase Order Confirmations Based on Purchase Orders.	SCONF_CLOSE_BY_POCHANGE	SCNX	None
SAP SNC generates a confirmation request for a request schedule line of a purchase order or a release. For more information, see Generation and Update of Confirmation Requests.	SCONF_REQUEST	SCNX	None
The preprocessing program for archiving sets the status o a confirmation to Archivable.	SCONF_ARCHIVE	SCNX	None

Validaton in Background Processes for SA Confirmations

The following table contains background processes that are only relevant for SA confirmations:

Process	Technical Process Name	Validation Profile	Notes
SAP SNC closes an obsolete SA confirmation when a new release is received. For more information, see Closing Scheduling Agreement Confirmations Based on Releases.	SCONF_CLOSE_BY_RELEASE	SCNX	For more information about the SCNX profile, see section Validation in ECM Background Processes above.
SAP SNC updates the release number in an SA release that is still up-to-date when a new release is received.	SCONF_RELEASE_UPDATE	SCNX	For more information about the SCNX profile, see section Validation in ECM Background Processes above.
The supplier sends an SA confirmation to collaborative release management (CMDS) in SAP Advanced Planning and Optimization (SAP APO). For more information, see Sending Scheduling Agreement Confirmations to SAP APO.	SCONF_SEND	SCN3	None