ARIBA BUYING INTEGRATION
Configuration Guide
Dipl.-Wirtsch.-Ing. Hans-G. Emrich
April 2024
1 Ariba Buying Integration ...................................................................................................................................3
1.1 Ariba Buying Configuration ......................................................................................................................3
CIG Configuration................................................................................................................................3
[Link] CIG Enablement .........................................................................................................................3
[Link] Certificate Maintenance ..............................................................................................................4
[Link] Send SAP Information to SAP Ariba CIG ...................................................................................7
[Link] Connections ...............................................................................................................................9
[Link] Integration Project for Ariba Buying .......................................................................................... 11
[Link] Custom Mappings .................................................................................................................... 16
[Link].1 Ariba PO: Vendor ID Mapping ........................................................................................... 16
[Link].2 Ariba PO: Short Text Mapping ........................................................................................... 16
[Link].3 AIBA PO: GR_RCPT mapping........................................................................................... 18
[Link].4 Ariba PO: Delivery Point Mapping ..................................................................................... 18
[Link].5 Ariba PO: Longtext Mapping.............................................................................................. 18
CIG Add-On Configuration ................................................................................................................ 19
[Link] Disable Middleware .................................................................................................................. 19
[Link] Create Port Definition ............................................................................................................... 20
[Link] Create Logical System ............................................................................................................. 21
[Link] Configure Receiver Port ........................................................................................................... 22
[Link] Interface Set Up ....................................................................................................................... 24
[Link] Configure Incremental Extract Events ...................................................................................... 27
[Link] Configure Ariba Event Linkage ................................................................................................. 29
[Link] Configure Connection Parameters ........................................................................................... 31
[Link] Map Variant and Partition ......................................................................................................... 32
[Link] Maintain Date & Time Stamp ............................................................................................... 33
[Link] Maintain Timestamp ............................................................................................................. 33
[Link] Maintain User Profiles .......................................................................................................... 35
[Link] Cross application Parameters .............................................................................................. 37
Page 1 of 69
[Link] Cross Application Filters ...................................................................................................... 37
[Link] Procurement Parameters ..................................................................................................... 39
[Link] Procurement Filters.............................................................................................................. 40
[Link] BAdIs for Master Data Export in CIG AddOn ....................................................................... 43
Integration of Master Data................................................................................................................. 44
[Link] Master Data Upload ................................................................................................................. 44
[Link] Load Translations ..................................................................................................................... 51
[Link] Cost-Center Approver .............................................................................................................. 52
Integration of transactional data ........................................................................................................ 54
[Link] PO Status Update .................................................................................................................... 55
[Link].1 PO Header Status: Goods Receipt .................................................................................... 56
[Link].2 PO Header Status: Invoice ................................................................................................ 60
[Link].3 PO Closure Status ............................................................................................................. 62
Maintain Parameters for Invoice........................................................................................................ 66
Configure Invoice Status Update Transaction ................................................................................... 66
[Link] Schedule Job for Invoice Status Update................................................................................... 69
[Link] Schedule Job for Remittance Information to be sent from ERP to Ariba Invoicing ................... 69
Page 2 of 69
1 Ariba Buying Integration
In the following chapters, configuration settings made for the integration between Ariba Buying and ERP will be
described.
1.1 Ariba Buying Configuration
CIG Configuration
[Link] CIG Enablement
CIG is enabled in both, parent and child site.
Page 3 of 69
[Link] Certificate Maintenance
The CIG Certificate was downloaded and provided to Hirschmann for the maintenance in STRUST and also
maintained in the Parent & Child Realm of the Buying Solution.
Page 4 of 69
Save as Base-64-encoded:
The tenant certificate was maintined in the Integration Tookit Security in Core Administration for parent and child
sites.
Page 5 of 69
Page 6 of 69
[Link] Send SAP Information to SAP Ariba CIG
To ensure that SAP system communicates with SAP Ariba Cloud Integration Gateway, send SAP ERP or SAP ERP
information such as, version, system ID, system time zone, system client, and ERP software component to the SAP
Ariba Cloud Integration Gateway.
This step can only be done once the basic Connection Tasks are fulfilled. It is necessary, since it provides relevant
and most important, reliable connection-information to the CIG. For this step we will need puser and password.
Following puser and password are in use:
Puser : P002467
Password : Apsolut2020@
Page 7 of 69
Testing this function resulted in a SSL Handshake error
This issue was solved by reviewing the SSL / TLS 1.2 -Settings with the ERP Basis and maintaining ssl/ciphersuites
correctly.
After this step, System information is available in the CIG Basic-Information.
Page 8 of 69
[Link] Connections
Following connections were created in the CIG.
Connecting to the test system DRW:
Page 9 of 69
This Connection was later on switched to quality system QRW and tested via CIG Connection Test:
Page 10 of 69
[Link] Integration Project for Ariba Buying
After system information have been sent to the CIG create cloud integration project. Cloud integration project
contains connection and mapping information and is needed to transfer Purchase Order to the ERP system.
Therefore one integration project per child realm should be created. For Hirschmann, this means one project for
the Procurement- and one for the Commerce Automation Solution needs to be created.
Basic data:
Connection:
Page 11 of 69
Connection for Ariba Network project.
Page 12 of 69
Page 13 of 69
Cross Reference Parameter:
Cross Reference UOM Template:
No UOMs to be maintained.
Cross Reference Lookup Table:
Not used for Hirschmann.
Realm ID:
For Both Projects, the test Child-RealmID is maintained.
Page 14 of 69
After this Setup, the integration project for Ariba buying and for commerce automation are created.
Page 15 of 69
[Link] Custom Mappings
For every Ariba Document a mapping can be created, changed or enhanced in the Ariba CIG.
[Link].1 Ariba PO: Vendor ID Mapping
For POs a custom Mapping was created to achieve leading zeros in front of Supplier IDs for Outbound POs, since
the value is used like that for validations in the Backend and some Vendors where initially loaded withouth leading
zeros.
Mapping:
Associated function:
[Link].2 Ariba PO: Short Text Mapping
To use the Ariba Product Name as short-text in the ERP, below Mapping was created. It is mapping the Short
Name from the custom Segment with the name “ShortNameExport”.
Page 16 of 69
The Short-Text is also mapped per Item. This is achieved by adding a Target Position Variable for the Target
Section. This Variable can then be used to match a new Source Condition. For us, the Target Variable needs to
match the PO-Item to be matching for each Item.
Associated Function:
To restrict the String-Length to always fit the ERP Field Length, a Substring Function was added to only select the
first 40 characters.
Page 17 of 69
[Link].3 AIBA PO: GR_RCPT mapping
This mapping is also applying for each item.
Substring Function:
[Link].4 Ariba PO: Delivery Point Mapping
Substring Function:
[Link].5 Ariba PO: Longtext Mapping
The ERP Long-Text was mapped from the Ariba Item Description. Here a new Segment was created for each Item
in the PO. The mapping was set up to create a new Segment for a single item in case the Text Line is longer than
132 characters.
Page 18 of 69
CIG Add-On Configuration
[Link] Disable Middleware
Hirschmann will not be using Middleware, so no Parameter needs to be set.
Page 19 of 69
[Link] Create Port Definition
Page 20 of 69
[Link] Create Logical System
The logical system was created by the Basis team.
Page 21 of 69
[Link] Configure Receiver Port
Page 22 of 69
Page 23 of 69
[Link] Interface Set Up
To enable the flow of messages between ERP and SAP Ariba Procurement / Ariba Network Solution the interface
should be set up. This setting needs to be done in every System. The Logical Port setting is overwritten each time
you run the interface settings for outbound web services.
Due to authorization issues this task was done by Basis Team as seen below.
Since the project scope changed slightly, even though in the current stage not every interface implemented is in
use, the interfaces are still completely set, to already fulfill possible future requirements.
Page 24 of 69
Page 25 of 69
Even if the log doesn´t contain any error, check if ARIBA ICF services were created, check hierarchy and external
aliase. In this case, all Services where successfully created.
Page 26 of 69
[Link] Configure Incremental Extract Events
Users need to configure the incremental extract to run the incremental load for Master Data. This is a one-time
activity & a mandatory configuration.
Page 27 of 69
Page 28 of 69
[Link] Configure Ariba Event Linkage
Users need to link the incremental extract events with the corresponding function module.
Following entries were added to event linkages.
Page 29 of 69
Page 30 of 69
[Link] Configure Connection Parameters
Users need to add the realms for each Ariba solution that can be used to process master data events. This is
needed to define Realm Name & Ariba Solution relationship in order to determine the appropriate target URL.
For the Q and D Systems, this was maintained as follows:
Page 31 of 69
[Link] Map Variant and Partition
Maintain for Test child and parent:
Page 32 of 69
[Link] Maintain Date & Time Stamp
Users need to maintain Date & Time Stamp for an incremental extract of Master Data. This was done for Internal
Orders, WBS Elements, Supplier- and User Data
[Link] Maintain Timestamp
For PO_Close, Remittance Export and Invoice Status, Timestamps where maintained. These Timestamps are
updated each time the scheduled Job did run.
Page 33 of 69
Page 34 of 69
[Link] Maintain User Profiles
Users need to maintain user roles mapped to the corresponding realm (Parent & Child / Test or Prod).
User groups to upload:
Requester ZR3_LOA_EK_BANF_ORG01 Purchase Requisition ATRW
Buyer ZR3_LOA_EK_EINKAUF_ORG01 Purchase Buying ATRW
Accounts Payable ZR3_LOB_MM_LOG_REPRF_ORG01 Logistics Invoice Verification ATRW
IT Admins ZR3_ARA_ARIBA_IT_ADMIN Ariba IT Administration
Page 35 of 69
Page 36 of 69
[Link] Cross application Parameters
Temporary directory was created by Hirschmann.
The TEMP_DIRECTORY parameter specifies the temporary file path in the application server to save master data
CSV files generated by ARBCIG_MASTER_DATA_EXPORT.
This parameter should be maintained in the table ARBCIG_TVARV for parent and child sites.
[Link] Cross Application Filters
Users need to configure selection criteria to filter Master Data records to import for more than one SAP Ariba
solution.
Page 37 of 69
Page 38 of 69
[Link] Procurement Parameters
Maintain procurement related parameters.
Page 39 of 69
[Link] Procurement Filters
Page 40 of 69
Page 41 of 69
Page 42 of 69
[Link] BAdIs for Master Data Export in CIG AddOn
BadI for master data export needs to be implemented by Hirschmann to receive Additional User-Data (Supervisor
& Approval Limit) as well as to select suppliers by their classification.
Following methods will be implemented by Hirschmann and where desribed in the third chapter:
IF_EX_ARBCIG~PUBLISH_VENDOR
IF_EX_ARBCIG~ PUBLISH_SUPPLIER_LOC
IF_EX_ ARBCIG_MASTERDATA~UPDATE_WHERETAB
IF_EX_ARBCIG~MODIFY_USER
Page 43 of 69
Integration of Master Data
Before running Master Data Export Program (ARBCIG_MASTER_DATA_EXPORT), customizing settings in
previous chapters should be done. For the Demo Realm and to start working in the Ariba Buying, Master Data was
exported in test-runs and imported manually.
[Link] Master Data Upload
When Master Data is initially loaded from the Report, the following structure should be used to prevent from
inconsistences.
Use Tcode SA38 / SE38 / SE80 and process programm ARBCIG_MASTER_DATA_EXPORT.
Load organizational Data to the child site:
Use the Variant: “01_ORG_FULL”
Page 44 of 69
Load accounting data to the child site:
Use the Variant: “02_ACC_FULL”
Page 45 of 69
Load cross-application data to the child site:
Use the Variant: “03_CA_FULL”
Page 46 of 69
Load user data:
The Import control parameter is set automatically by the CIG Add-On depending on site realm used.
First load supplier data to the parent site: Use the Variant 04_USER_FULL
After a short time period, the users should be visible in the child – realm aswell. Now the Child-Data can be loaded
by using the Variant:” 041_User_FULLC”
Page 47 of 69
Page 48 of 69
Load Supplier Data:
First load Supplier-only Data to the Parent-Site:
Use the Variant “05_SUPPL_FULL”
Afterwards load Supplier Data including Location and Purchase Org assignment to the Child:
Page 49 of 69
Use the Variant “06_SUPPL_FULL”:
Afterwards the Cost-Center Approver Data can be loaded.
Page 50 of 69
[Link] Load Translations
To Upload Translations for Master Data Elements, another Report is used. The Translations have to be loaded to
the child, just like the accounting data is.
Use Tcode SA38 / SE38 / SE80 and process programm ARBCIG_MASTER_DATA_LANG_EXPORT.
Page 51 of 69
[Link] Cost-Center Approver
Since this is a non-Standard Master Data Upload, the Job Execution is described below:
In order to fill the cost center owner lookup tables in Ariba we need to generate below two CSVs
COSTCENTEROWNERS_FP.csv and COSTCENTEROWNERS_K.csv.
To achieve this we need to first run the report Z1_CO_RESPONSIBLES to fetch cost center owners and fill the
ERP tables with appropriate cost owners.
1. Run Report : Z1_CO_RESPONSIBLES1.
First select the Variant and child Partition we need to upload the data. Select COSTCENTEROWNERS_K from the
dropdown and execute the Report.
After doing so, execute the report once again with selecting COSTCENTEROWNERS_FP.
Once this is done, we will have all the cost centers owners in respective tables. Now we need to run below report
to send data to Ariba.
Page 52 of 69
2. Run Report Z1_LOOKUP_UPLOAD_TAB
Here again we need to run the report once for each of the options from dropdown for Lookup-file without test mode.
This then sends the data to the Ariba Solution.
Page 53 of 69
Integration of transactional data
Interfaces for the following transactions were activated for the Buying Solution.
Inbound to SAP Ariba Buying:
• PO Status Update / PO Close
• Goods Receipt Export
• Invoice Status
• Payment Remittance
Outbound from SAP Ariba Buying:
• PO Create
• PO Change
• PO Delete
• Goods Receipt
• Payment Request (Invoice)
Page 54 of 69
[Link] PO Status Update
Page 55 of 69
[Link].1 PO Header Status: Goods Receipt
Paramters for GR Export where maintained.
Page 56 of 69
A Message Output Control was set up to determine the GR export.
Page 57 of 69
[Link].1.1 Maintain Movement types:
Movement Type 101 (GR) and 102 (GR-Reversal) where maintained.
Page 58 of 69
Page 59 of 69
[Link].2 PO Header Status: Invoice
This status is used to close POs when a PO I fully paid in ERP. The new Output Type ARB1 was created for
Application MR:
Page 60 of 69
Page 61 of 69
[Link].3 PO Closure Status
To transfer the close-status for POs from the ERP to the Ariba Buying Solution, following activities are done.
Enter Transaction SWEC and select below document to maintain Field restrictions for PO Closure Status Export.
Go to the Field-Restrictions Screen of the document and choose the Condition Editor:
Page 62 of 69
In the Utilities Section, choose the Settings Menu and enable the traditional editing mode:
With clicking “Insert row”, two new rows need to be added.
In the next Screen, the following values need to be entered exactly as shown and can then be saved in a transport.
Following to that, Enter TCode SWE2 and create a new Entry:
Page 63 of 69
The following Entry was maintained:
After this setting is done, the settings are transported and the timestamp for the export event can be set in the
quality System. This value is updated with every Trigger of the Export Program:
Page 64 of 69
In the Quality and production System, a Background Job for the Program ARBCIG_BUY_POCLOSE has to be
scheduled with the transported Variant POCLOSE_EXPORT.
Page 65 of 69
Maintain Parameters for Invoice
Configure Invoice Status Update Transaction
To send Invoice Status Updates from ERP, the following setup needs to be done.
Page 66 of 69
Page 67 of 69
Page 68 of 69
[Link] Schedule Job for Invoice Status Update
A Job for the Program ARBCIG_INV_STATUS_EXPORT was maintained to be processed.
[Link] Schedule Job for Remittance Information to be sent from ERP to Ariba Invoicing
A Job for the Program ARBCIG_REMITTANCE_EXPORT was maintained to be processed.
A Parameter in Ariba was enabled by the Ariba Support Team to also send the Remittance Update to the Ariba
Network Buy- and Supplier Side.
Page 69 of 69