All required iflows for the customer need to be deployed, in this example the following are deployed:.
Furthermore, two iflows need to be edited to determine to which SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network the payload must go to based on whether it is a Sourcing & Contracts or a Commerce Automation one. SAP Integration Suite needs to be implemented as a middleware using the SAP ERP and SAP S/4HANA Integration with SAP Ariba package. To summarize: in this business case, 2 different SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network (ex CIG) accounts are in use, alongside a single SAP ERP system.įrom left to right: the connection is from the SAP ERP to SAP BTP Integration Suite and then Integration Suite bifurcates the payloads to the corresponding SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network account. One account is used for SAP Business Network (Ariba Network / Commerce Automation) while the other is used for SAP Ariba Sourcing & Contracts. This global company has two different Ariba Accounts, and therefore two different ANIDs and two different SAP Ariba Realms. Business CaseĪ customer wants to migrate an SAP Ariba realm to the SAP Ariba realms of the global company. Disclaimer: SAP Ariba Cloud Integration Gateway (CIG) has been renamed to SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network, some graphics may still refer to the previous name, mainly due to size restrictions.
0 kommentar(er)
