caswings.blogg.se - Ariba fieldglass

The error is posted in a comment on the Fieldglass invoice. Fieldglass acknowledges receipt of the error and reverses the purchase order for the invoiced amount.Ariba Network sends the status update to Fieldglass and reverses the corresponding purchase order for the invoiced amount.Ariba Network receives the status update and identifies the corresponding invoice as a Fieldglass invoice through the extrinsic Ariba.SpendCategory, which is set to Contingent Labor.The status update includes the reason for the error and states that the invoice needs to be corrected in Fieldglass. SAP Ariba Buying and Invoicing changes the status of the invoice, invoice reconciliation, and payment to Rejected, reverses the corresponding purchase order for the invoiced amount, and sends a status update to Ariba Network.

The ERP system validates the invoice information, rejects it, and sends an error to SAP Ariba Buying and Invoicing.

The external ERP system receives the invoice information in the form of an OK-to-pay file from SAP Ariba Buying and Invoicing.

Detailed steps follow each diagram.įieldglass integrations with SAP Ariba Buying and Invoicing (without the separate SAP Ariba Invoice Management solution)

The following sets of high-level steps describe what happens when the ERP system sends an error rejecting a Fieldglass invoice. It’s not simple to run - unlike SAP’s old slogan of “Run Simple” used to say.Workflows for Fieldglass invoice rejections from external ERP systems S/4HANA then needs to integrate to the SAP Cloud Platform applications that will themselves need to integrate with each other as they slowly migrate to an underlying SAP Cloud Platform that includes a range of areas described in this second of three briefs in Spend Matters’ PRO research series. For example, SAP Ariba product managers have to deal with their individual platforms/ecosystems (SAP Ariba, Fieldglass, and Concur), but also with integrating to the Ariba Network, relevant SAP applications (e.g., Integrated Business Planning), with partner apps in each of those ecosystems, and the move toward an SAP-centric application stack and platform stack.įor example, SAP has its own journey from ECC to SAP S/4HANA in the cloud via S/4HANA Cloud Foundation, S/4HANA Cross Engineering, S/4HANA Enterprise Architecture, and other toolsets. As the new operating unit eventually becomes “one” from a product perspective as well, it is important to realize the level of complexity that SAP will confront along the way. In late April, SAP announced its “Intelligent Spend Group,” a combination of SAP Ariba, SAP Fieldglass and SAP Concur.