Ariba Order Confirmation Deviation Workflow in SAP S/4HANA – A Developer’s Guide

[Shravan_]

In today's dynamic supply chain environment, effective collaboration between buyers and suppliers is crucial. SAP Ariba Supply Chain Collaboration (SCC) enhances this collaboration by integrating seamlessly with SAP S/4HANA, enabling efficient management of processes like order confirmations, especially when deviations occur.

When suppliers confirm POs with changes in price, quantity, or delivery dates, businesses need control before those updates reach S/4. This post presents a flexible, workflow-driven solution to efficiently manage such deviations and ensure smooth procurement operations.

Business Need

When suppliers confirm purchase orders (POs) in SAP Ariba SCC, they might propose changes to:

• Price → Requires Buyer approval

• Quantity → Requires MRP Controller approval

• Delivery Date → Managed via Ariba SCC configuration

• Rejection of PO Items → Routed based on predefined workflows

To ensure these changes are systematically reviewed before being updated in SAP S/4HANA, implementing a custom deviation workflow is essential.

Process Overview

Part 1: IDOC Handling & Deviation Check

The process initiates when Ariba sends a confirmation back to S/4HANA. The system then:

1. Receives the Inbound IDOC (ARBCIG_ORDRSP).

2. Checks for Deviations in price or quantity or rejection.

3. Triggers the Appropriate Workflow based on the type of deviation detected.

Flowchart:

Note: The above image illustrates the flow from receiving the IDOC to triggering the necessary workflows based on detected deviations.

Part 2: Workflow for Approvals (Price, Quantity, Rejection)

Depending on the deviation type, the system:

1. Routes the Workflow to the appropriate approver (Buyer, MRP Controller, or designated Approver).

2. Allows the Approver to Approve or Reject the proposed changes via Fiori or SAP Inbox.

3. Updates the PO Accordingly based on the approval decision and sends the update back to Ariba.

Flowchart:

Note: This image showcases the approval process for different deviation types, ensuring clarity in workflow routing.

Technical Implementation Highlights

Integration with SAP Ariba SCC

SAP Ariba SCC is an extension of the Ariba Network that enhances buyers' ability to collaborate with suppliers on direct materials in supply-chain tasks like planning, procurement, and invoicing. It allows for real-time collaborative exchanges of planning/forecasting, purchasing, inventory fulfillment, and payment transactions between buyers and suppliers, improving traceability and end-to-end visibility of supply chain operations.

Key Features:

• Real-Time Visibility: Access current information on inventory, orders, and shipments, enabling informed decision-making and swift responses to supply chain changes.

• Order Management: Create, track, and manage purchase orders and shipment notifications, streamlining order processing and ensuring accurate fulfillment.

• Collaborative Forecasting: Enable joint forecasting and planning with suppliers, enhancing demand prediction accuracy and reducing discrepancies.

For more detailed information, refer to the SAP Ariba Supply Chain Collaboration Overview.

Integration with SAP S/4HANA

The integration between SAP Ariba SCC and SAP S/4HANA is facilitated through the SAP Ariba Cloud Integration Gateway, which serves as middleware, allowing for seamless data exchange between the two systems. This integration ensures that supplier data, order details, and inventory information are synchronized across systems, providing a unified view of supply chain activities.

For more details on the integration process, see Implementing the Key Configuration Tasks for Supply Chain Collaboration.

Custom Enhancements

• User Exit: EXIT_SAPLEINM_007 (MM06E001) – Handles incoming IDOC checks.

• Business Object: ZSTPPOVARI – Triggers workflows.

• Custom Tables:

  • ZTSTP_PO_VARIANC: Captures deviation per PO line.

  • ZTSTP_REJECTCODE: Defines routing rules based on rejection reasons.

• Status Handling: IDOC is set to status 72 when a deviation is detected.

Workflow Actions

• Custom Workflow Templates: Based on Task 8267 for:

  • Price Deviation: Routed to Buyer.

  • Quantity Deviation: Routed to MRP Controller.

  • Rejection: Routed based on reason code.

• Approval Platforms: Workflows are actionable via SAP GUI or Fiori.

• Notifications: Emails and Fiori UI contain buttons for Approve and Reject actions.

• Decision Logging: All decisions are logged in PO item texts and sent back to Ariba.

For more information on configuring deviation approvals, refer to Configurations for Deviation Approval.

Additional checks 

• Fallback Approvers: If no email/SAP ID is found, use default via TVARVC configuration.

• Auto-Cancel Workflows: When a PO line is deleted or closed before approval.

• Retry/Error Handling: If the PO is locked, implement retry logic (up to 20 times) before failure.

• Mandatory Comments: On rejection, users must enter a reason.

• Net Price Sync: Ensures updated values post-approval are written to the PO.

In conclusion, this custom solution offers robust control over supplier-initiated changes in Ariba, ensuring transparency, traceability, and proper approval routing within SAP S/4HANA. By combining IDOC enhancements, workflow automation, and clear notifications, it delivers a scalable, developer-friendly approach that supports both operational accuracy and compliance. It also empowers procurement teams to make informed decisions while maintaining seamless integration between Ariba SCC and S/4HANA.

For more detailed guidance on implementing these configurations, see Workflows for Order Confirmation Deviation Approval.