The Ariba Network Adapter for SAP NetWeaver supports receiving order confirmations from Ariba Network for the following:
● Confirmation of orders with or without delivery dates at the header or line-level.
● Confirmation of orders containing partially confirmed, rejected, and back-ordered line items. ● Confirmation of orders containing line items with multiple schedule lines (delivery dates). ● Comments at the header and line-item levels.
Note
A PO item that contains service line items can only be confirmed or rejected in its entirety, not at the individual service line-item level.
If a delivery date is provided in Ariba Network when creating a confirmation request, the delivery date is derived from the confirmationRequestt cXML. Otherwise the delivery date is determined from the corresponding PO item.
You must configure the integration scenario for the Order Confirmation transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario. The SAP ERP administrator must configure the SAP ERP system to collect order
confirmations for purchase orders and to support comments. To configure SAP ERP enhancements for comment support, see Configuring Implicit Enhancements for Comments in Order Confirmations [page 300] .
Mapping Limitations
The Order Confirmation transaction has the following mapping limitations:
● Order confirmations are stated at the purchase order line-item level only. SAP does not support header level purchase order confirmation. With the exception of unit price and backordered delivery date, purchase order line items cannot be overwritten.
● A new order confirmation completely overwrites prior confirmations against a purchase order line-item. Suppliers must resend the entire confirmation picture for the relevant purchase order line.
● Delivery date is always required at 'ConfirmationStatus' in the input cXML document if the header level and line level statues are 'Backordered'. Delivery date is required at 'ConfirmationStatus' level if header level statuses are 'detail' and 'except'.
● In the cXML for an order confirmation sent from Ariba Network, the adapter does not support the operation = “update” and type = “allDetail”.
● Only order confirmations for the purchase orders that are pulled from ERP using the OrderRequest transaction is supported.
● Ariba Network Adapter for SAP NetWeaver does not support order confirmations for service purchase orders at the line-item level.
● The IDoc fails when an order confirmation only contains partially rejected line items. For example, if the quantity for a line item is 100, you cannot partially reject only 50 units for that line item. You can partially accept 50 units and also partially reject or back order the remaining 50 units for the line item. You must ensure that you maintain the Overdelivery Tolerance and Underdelivery Tolerance limits for the line item. However, Ariba Network Adapter for SAP NetWeaver supports order confirmations that are partially accepted, rejected, or back ordered for a line item. For example, if the quantity for a line item is 100, you can partially accept 50 units and also partially back order or reject the remaining 50 units for the line item.
● Purchase orders containing service items may only be confirmed at the outline item level.
● Purchase orders containing a combination of service and material items may only be confirmed at the header level.
● When purchase orders contains advanced pricing details, the unit conversion value from Ariba Network to SAP is not supported.
● The cXML header-level except status for order confirmations created in Ariba Network is not supported. ● Partial rejection of a line item in an order confirmation is not supported. Full rejection of an item in an order
confirmation sets the deletion flag on the item in SAP.
Workflow
The following is a description of the end-to-end workflow for order confirmation:
1. A buyer creates a purchase order in the SAP ERP that may or may not include service line-items, and may or may not include line items with multiple delivery dates.
2. In Ariba Network a supplier receives the purchase order and creates an order confirmations based on the purchase order.
The confirmation order can contain comments at the header and line-items levels.
3. Ariba Network sends the confirmation order to the SAP PI system as a ConfirmationRequest cXML document.
4. The SAP PI system maps the ConfirmationRequest to an ORDRSP.ORDERS05 IDoc and sends it to the SAP ERP system.
5. SAP ERP processes the order confirmation, and the original purchase order is updated with the confirmation information received from Ariba Network.
To configure the Order Confirmation:
1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario.
3. Configure the Communication Channels. 4. Activate the new configuration.
Note
Ensure that the design is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD, see the “About Configuring the System Landscape Directory” [page 61] section.