SAP Fieldglass Initiated 4R2 Workflow
In the 4R2 workflow, purchase order processing and approval for statements of work is also handled through SAP Integration Suite, the managed gateway for spend management and SAP Business Network.
After the Statement of Work is created in SAP Fieldglass, a purchase requisition request is sent from SAP Fieldglass to SAP Integration Suite, the managed gateway for spend management and SAP Business Network, and then to SAP S/4HANA. The purchase requisition response is returned to SAP Fieldglass, after which SAP Fieldglass sends the purchase order request to SAP S/4HANA. SAP S/4HANA processes and approves the purchase order, and the approval result is sent back to SAP Fieldglass using the SOW XML Upload process. This ensures that SAP Fieldglass receives timely and accurate purchase order confirmations, enabling users to monitor approvals, statuses, and responses entirely within SAP Fieldglass. The 4R2 workflow relies on continuous integration availability and supports consistent, transparent, and reliable purchase order management across both public and private SAP S/4HANA cloud editions.
You can create and approve statements of work using SAP Fieldglass and SAP Integration Suite, the managed gateway for spend management and SAP Business Network.
-
Create a statement of work in SAP Fieldglass.
-
SAP Fieldglass automatically submits the corresponding purchase requisition (PR) to SAP Integration Suite, the managed gateway for spend management and SAP Business Network.
-
SAP Integration Suite, the managed gateway for spend management and SAP Business Network, forwards the PR to SAP S/4HANA and returns the requisition status to SAP Fieldglass through the Requisition Response Upload process.
-
After requisition approval, the purchase order (PO) request is sent from SAP Fieldglass to SAP Integration Suite, the managed gateway for spend management and SAP Business Network instead, as per the 22K workflow.
-
SAP Fieldglass receives the approved purchase order through the SOW XML Upload process, based on the 4R2 integration flow.