Acceptance at Origin

This function enables a public-sector entity to accept goods at the supplier's plant prior to their receipt, testing, and final acceptance at the public sector requester's location. The risk of losing goods, usually assumed by the supplier, is assumed by the public sector entity, especially when the risk of loss is expected to be high (for example, in a war zone or disaster area).

The acceptance at origin function can be combined with the quality management (QM) inspection function to provide an end-to-end Origin Inspection and Acceptance process. Acceptance at origin includes Funds Management (FM) integration for the proper timing of the posting of invoices and payments.

Integration

Information about retention is transferred from the SAP ERP material master to the SAP Supplier Relationship Management (SAP SRM) product master table.

Prerequisites

You have done the following:

In SAP ERP:

You have added the Origin Acceptance checkbox to the SAP ERP material master table and you have replicated the data to the SAP SRM product master.

To add this checkbox to the material master table, enter Customizing for Material Master (transaction OMT3), select screen sequence 21, choose screen 14, and exchange subscreen 2313 for subscreen 2314 (line 4). You can now see the Origin Acceptance checkbox on the Purchasing view.

In SAP SRM:

You have activated the business function SRM, Cross-Industry Functions (SRM_CROSS_INDUSTRY_1). Note that you can only use this business function in conjunction with the business function SRM, Procurement for Public Sector (SRM_PUBLIC_SECTOR_1). In other words, you must activate both business functions.

You have enhanced the SAP SRM product master table by adding the Origin Acceptance checkbox. You can do this in Customizing for SAP Supplier Relationship Management under Start of the navigation path Cross Application Components Next navigation step SAP Product Settings for Product Maintenance Define Views End of the navigation path .

Create the view ISPS_PRODUCT with the description Procurement for Public Sector, position 22 (Customizing activity COM_PRODUCT_VIEWS).
To use the set type ISPS_MARA in the product master table, you must assign it to material types, product subtype MAT_, in hierarchy R3PRODSTYP using transaction COMM_HIERARCHY.

Integration of SAP ERP and SAP SRM:

You have integrated SAP ERP with SAP SRM by implementing the Business Transaction Event (BTE) exit PROCESSCRM0_200 (function module /SAPPSPRO/MATE_PROCESSCRM0_200 and BTE Customizing) in SAP ERP and the Business Add-In (BAdI) PRODUCT_R3_ADAPTER in SAP SRM.

For more information, see SAP Note 1098232.

Features

Acceptance at origin allows acceptance of goods at the supplier facility before shipment to destination. It can be combined with the quality management inspection functionality to provide an end-to-end Origin Inspection and Acceptance process. The function includes FM integration for proper timing of posting of invoices and payments.

When you enter a goods movement in the system, you must enter a movement type to differentiate between the various goods movements. The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.

The standard SAP ERP movement types 105 (release from goods receipt blocked stock for purchase order) and 103 (goods receipt for purchase order into goods receipt blocked stock) did not meet the requirements for acceptance at origin. The new movement types 107 and 109 (reversals 108,110) have been introduced for these purposes.

Example

The purchaser inspects and accepts the goods at origin (at the supplier's facility).
The supplier ships the goods to the destination.
The purchaser acknowledges acceptance but does not perform the final goods receipt until the goods arrive at the final destination.
The system acknowledges the origin acceptance posting by updating the purchase order history.
The system shows that the items are IN TRANSIT to their final destination and prevents them from being available for use.
When origin acceptance is posted, the system allows proper financial postings. The system also allows for payments prior to the arrival of the goods at the purchaser's location.
When the items arrive, the system posts the final goods receipt in the logistics system and acknowledges their final receipt. The system then updates the PO history.
The system only posts a final receipt quantity that is equal to or less than the amount that was accepted at origin. It is only at this point that the items become available for use in the logistics system (that is, the items change from status in transit to available for use). There are no financial postings here, as these occurred earlier (however, a reversal transaction can be posted here).