Happy Friday and a good time for writing the second blog about the integration between IBP and Ariba.
I explained in the first post that we have a simple puzzle to solve, two pieces to connect and no adhesive needed in between. No code, no middleware, no complexity! But the pieces must fit so let’s see what is needed to equip Ariba SCC for the integration with IBP.
I start by explaining that the Ariba buyer I am using for the connectivity with IBP is enabled for multi-ERP integration. This means that one Ariba buyer can exchange information with multiple underlying ERP systems. In my case, there are no multiple ERP systems, but multiple IBP systems as I am operating in a demo landscape.
As a buyer, using the Ariba Network platform interface, you need to maintain the connectivity with IBP as it follows:
- Maintain the IBP Applications ID(s)
Ariba Network -> Administration -> Configuration -> Business Applications IDs
Here you need to create an entry for the same system ID that was maintained in your IBP system. It can also be that this field was left empty in the IBP backend, and then the unique logical system ID of the IBP system is used. With the current release, 1708, you have no visibility to see this SID from the Fiori UI, but this is will be enhanced in the future.
- Maintain the Supplier alias
Ariba Network -> Supplier Enablement
Under this tab, one can find the list of active suppliers with whom the buyer is enabled to do business. Choose the supplier(s) required for collaboration and hit the Edit option.
In the Edit preferences screen, drill down to the section “Enter supplier identifiers for the procurement application”. Add a new entry, choose the IBP system ID and type in the corresponding Supplier ID as used in IBP.
And that’s all from Ariba Network’s side. In the next blog, we will see how to run the integration E2E.