Describing MDNI- Master Data Native Integration

• The feature is currently available mainly with the SAP Ariba Procurement solutions integrated with SAP ERP or SAP S/4HANA on-premise using CIG. With SAP Ariba Sourcing solutions currently only Product Master Data integration is supported.
• The master data is sent from SAP system to MDNI through CIG in XML format.
• The feature allows to export master data from multiple SAP on-premise systems.
• The master data exported from each SAP system is identified by a System ID.
• The feature uses standard web services in SAP system.
• The master data will pass through CIG without any mappings.
• Master data upload can be done through full uploads or incremental uploads.
• In a full upload, the full object will be uploaded each time. If the object already exists, it will be deactivated before being loaded again.
• In an incremental upload, only the incremental changes will be uploaded. If the object does not exist it will be created.
• ERP sends an XML file corresponding to the master data object.
• To ensure that the file is in a format that allows the SAP Ariba applications to consume the data, WSDL files corresponding to each data object need to be uploaded to the Master Data Integration Service.
  • Uploading WSDL files will be done by Ariba. Customer doesn't have any action item here.
• The WSDL files use the corresponding APIs.

This feature currently supports only full-load export of the following master data objects:

• Company Codes
• Cost Centers
• Plant
• Asset/Asset Class
• Material Group
• Purchasing Organizations
• Exchange Rate
• Purchasing Group
• Internal Order
• Currency
• Plant Purchasing Organization
• Tax Code
• Payment Terms
• Account Assignment Category
• General Ledger Account

This feature currently supports incremental-load export of the following master data objects:

• General Ledger Account
• WBS Element
• User

• SAP Ariba solutions are integrated with SAP system using CIG.
• MDNI service is integrated with SAP Ariba applications. To enable this feature, log a Service Request.
• Download & install SAP Ariba AddOn from SAP Service Market Place. For MDNI, minimum supported SP level of the SAP Ariba AddOn is SP7.
• MDNI feature is configured on SAP Ariba AddOn.
• CIG’s SSL certificate is uploaded in Trust Manager in your SAP system.
• CIG is enabled in your SAP Ariba applications realm & you have secured P User ID & password information.

• FPC (Federated Process Control) or multi-ERP integration is not supported.
• FMD (Flex Master Data) or an extract of a new custom master data object is not supported.
• Adding custom fields to the extracts are not supported.
• Currently an incremental export is supported only for:
  • General Ledger Account
  • WBS Element
  • User

1. Using the transaction code SPRO, navigate to Integration with Other SAP Components → SAP Ariba Cloud Integration Gateway → Master Data Native Integration → Interface Setup.
2. Click IMG-Activity for Configure the Outbound Connections to Send Messages – The Interface Setup for Ariba MDNI screen appears.
3. Under Interface Setup for Web Service section, perform the following activities:
   1. Select Data Center.
   2. Under Connection Instances, select one of the following to indicate if the connection is to a Production or Test instance of CIG:
      • Connect to Cloud Integration Gateway Production Instance
      • Connect to Cloud Integration Gateway Test Instance
   3. Under Logon Data, select one of the following types of authentication methods
      • Select User ID / Password and enter authentication information to connect to SAP Ariba Cloud Integration Gateway. This will be your P User ID & Password.
      • Select X.509 SSL Client Certificate and choose the Certificate Name (ARIBA, for example). The same certificate used for Certificate Based Authentication need to be added here & it will be stored in SOA Manager.
   4. If you are using proxy server, under HTTPs Proxy Options, enter the following values:
      • HTTP proxy name in the Name of Proxy Host field. For example, proxy.abc.com.
      • Port name in the Port Number of Proxy Host field. For example, 8080.
      • User Name for the Proxy Server in the User Name of Proxy Server field. For example, abc_proxy.
      • Enter the password for the registered user name in the Proxy User Password field.
   
4. Choose from the available / supported master data objects to set up web services for the outbound data sent to CIG.
5. Click Execute button.

1. Run the transaction code ARBCIG_MDNI.
2. The SAP Easy Access Master Data Native Interface Transactions screen appears. The screen lists the master data objects that are available for export.
3. Double-click on the master data object you want to export. For example, Company Code.
4. The extract screen for the master data appears. For example, Company Code Extract for MDNI.
5. Click on Fields for Selection. The Dynamic Selection screen appears.
6. Expand the node & you can see fields available for defining filters.
7. Double-click on a required field for which you want to set filters & define values for filtering. This is a standard SAP screen which allows you to either define specific values or ranges or define values to be excluded.
8. Input required filter values.
9. Click on Apply Selected Items.
10. Click on Execute button.
11. Added filters will be shown on the screen.
12. Click Save, the Variant Attributes screen appears. This is a standard SAP screen.
13. Specify the variant to export master data from SAP system.

    Example: CC_Extract.

    
14. Click Save.
15. Check Display Data box & click Execute only to display the XML document of the master data extract. The Display XML Document screen appears. You can check the details of the master data export.
16. When you choose Display Data option, master data records will not be sent to MDNI / SAP Ariba applications.
17. Click Execute (without checking Display Data Box) to export master data to SAP Ariba Procurement solutions based on the selected criteria.

The Display logs screen appears.

Here, you can check the status of the master data export.

• Message types are distinguished by colored icons:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Native Integrationusing the transaction code SPRO.
2. Click on IMG-Activity for Maintain Timestamp for Master Data Native Integration – The Change View "Date and Time stamp for Master Data": Overview screen appears.
3. Click New Entries.
4. Enter the following values:
   • Extract: Select from the list.
   • Realm: Enter realm name.
   • Date Time Stamp: Add date & time in YYYYMMDDHHMMSS format.
   
5. Click Save.

1. Run the transaction code SM36. The Define Background Job screen appears.
2. Click on Job Wizard.
3. On the Create a job screen, Click Continue.
4. On the General job information screen, define a job name. For example, Company Code Extract; define Job Class, for example, A – High priority & then click Continue.
5. On the Job definition: Job step screen, select ABAP program step & then click Continue.
6. On the ABAP program step screen, define ABAP Program Name. For example, ARBCIG_MDNI_COMPANYCODE & in the Variant field, select the variant for that specific master data object you created earlier. For example, CC_Extract & then click Continue.
7. On the Multi-step option screen, click Continue.
8. On the Job definition: Start conditions screen, select a condition. For example, Date/time & then click Continue.
9. On the Definition of start at date/time screen, define Scheduled Start date & time. Additionally, you have an option to define Periodic jobs by checking Period checkbox & then click Continue.
10. If you want to define Periodic jobs by checking Period checkbox, on the Period Definition screen you need to select frequency. For example, Weekly & then click Continue.
11. On the Set job screen, click Complete.

Program names to be used while scheduling jobs:

• ARBCIG_MDNI_ACCOUNTCATEGORY
• ARBCIG_MDNI_ASSET
• ARBCIG_MDNI_COMPANYCODE
• ARBCIG_MDNI_COSTCENTER
• ARBCIG_MDNI_CURRENCY
• ARBCIG_MDNI_EXCHANGERATE
• ARBCIG_MDNI_GLACCOUNT
• ARBCIG_MDNI_INTERNAL_ORDER
• ARBCIG_MDNI_MATERIALGROUP
• ARBCIG_MDNI_PAYMENTTERMS
• ARBCIG_MDNI_PLANT
• ARBCIG_MDNI_PLANT_PURORG
• ARBCIG_MDNI_PURCHASING_GROUP
• ARBCIG_MDNI_TAXCODE
• ARBCIG_MDNI_USER
• ARBCIG_MDNI_WBS