Configuring Purchase Order Integration in SAP Ariba Procurement Solutions

Managing the Data Definition

Objective

After completing this lesson, you will be able to understand the importance and relevance of reviewing and accepting the data definition changes.

Managing the Data Definition

Data Definitions

In SAP Ariba Buying and Invoicing, Data Definitions are structured configuration objects that define data fields, their meanings, and their behavior across documents such as requisitions, purchase orders, receipts, and invoices. They specify the structure and fields of data used within the SAP Ariba application, including what data is collected, displayed, or transferred during procurement transactions.

Data Definitions serve as templates or schemas that govern the organization and processing of information. They define fields and their properties, such as field name, data type, required/optional status, default values, labels, and descriptions. They are the blueprints for fields.

Data Definitions are foundational for customizing and controlling the capture, validation, transmission, and reporting of procurement data. They ensure SAP Ariba captures the necessary business information in a consistent, controlled, and system-compatible manner. Data Definitions allow Buyers to:

  • Add custom fields
  • Control user input
  • Enable smooth integration with backend systems
  • Enforce business rules
  • Support reporting and analytics
  • Ensure compliance, reporting, and custom business rules

In the context of SAP Ariba Procurement Solutions integration with SAP ERP or SAP S/4HANA via the SAP Integration Suite, managed gateway for spend management and SAP Business Network, integration events send and receive data to and from the SAP system. Each event has a defined Data Definition outlining the data and structure for successful integration.

SAP Ariba may introduce new fields in integration events to support newer workflows, features, or enhancements, and send more information to the backend SAP system. Changes to the data definition, such as new fields or field order changes, can break the integration of these imports or exports with your SAP system.

To address this issue, update your existing events to incorporate the Data Definition changes in the integration events. Review the field changes and accept them if desired. Accepting these changes is optional and ensures SAP Ariba’s Data Definition changes won’t be incorporated into your data imports or exports until you explicitly accept them. If you don’t accept the changes, your integration will still work, but without the new fields.

This process applies to new custom fields as well. SAP Ariba doesn’t add new custom fields to an integration event until you accept the changes to the event’s Data Definition.

When new standard SAP Ariba fields and custom fields are added to the Data Definition of any event, you must accept all the fields. If you don’t accept standard SAP Ariba fields, you can’t add new custom fields. You must either accept all the fields (custom fields and new standard SAP Ariba fields) or accept nothing. You can’t accept only new custom fields.

After accepting changes to the Data Definition, you can revert to the previously accepted Data Definition if needed.

  • You must review and, if necessary, accept changes to all tasks (imports or exports), because all documents must adhere to the WSDL for the event, regardless of whether they are import or export tasks.
  • You need to review and accept the changes made to the Data Definition in order to avail new functionalities or enhancements done to the existing functionalities as appropriate to your requirements.
  • You must be a member of the Integration Admin or Customer Administrator group to manage and accept the changes to Data Definition.

Accepting the Data Definition Changes to Individual Fields

SAP Ariba Procurement solutions provide you with the flexibility to review and accept the changes to individual fields in the Data Definition.

Your administrator must enable the parameter that allows accepting field-level data definition changes in the Intelligent Configuration Manager.

Application.Messaging.Integration.EnableAcceptingFieldLevelDataDefinitionChanges

To do so, you must be a member of the Integration Admin or Customer Administrator group.

Screenshot showing the option to accept data definition changes to individual fields in SAP Ariba.

This parameter allows users in the Integration or Customer Administrators group to accept field-level Data Definition changes. If enabled, users can select one or more fields to accept changes for. Select the checkbox next to the fields you want to accept.

After reviewing and accepting changes across all groups, the Publish All Changes button will be enabled. Select it to add the selected fields to the event/task schema or Data Definition, making them available for integration.

See the sample screenshot:

Screenshot showing the field-level data definition changes in the SAP Ariba Intelligent Configuration Manager.

Accepting the Data Definition changes at the field level ensures that:

  • Updates are intentional
  • Ensures only validated and approved configuration (field updates) are introduced and move forward
  • Integration remains stable
  • User experience is protected
  • Configuration governance is maintained
  • Target environments receive only correct and approved changes

It is a critical step for safely migrating and maintaining configurations in SAP Ariba Procurement solutions. This approval step ensures that only intentional, validated, and business-approved changes are applied to the environment.

Reverting the Data Definition Changes to Export and Import Tasks

When working with Data Definitions across environments (Test, Production), administrators may accept incorrect, unintended, or incompatible changes.

SAP Ariba Procurement solutions offer flexibility to undo or revert changes to the most recent version of a data export or import task. Reverting ensures stability, prevents inconsistencies, and maintains approved configurations.

Reasons to Revert:

  • Unexpected behavior in import/export tasks
  • Integration breaks due to field mapping mismatches
  • Testing or validation issues with updated definitions

Benefits of Reverting:

  • Protects system stability
  • Ensures configuration governance
  • Prevents integration failures
  • Reduces risk in production
  • Maintains consistency
  • Supports controlled change management

Reverting changes to Export and Import tasks prevents incorrect updates, maintains approved configurations, ensures stable integrations and document processing, and protects end-to-end procurement operations. It’s a key safeguard in configuration migration and system maintenance.

To revert to the previously accepted Data Definition:

  1. Choose Revert in the Actions drop-down for the data export or import task on the Data Definition page.
  2. Review and accept the reversal for each group of fields with Needs Review status.
  3. Revert all changes to the data export or import task for any change to be reverted.
  4. Accept all changes, then publish.Screenshot showing the Revert action in the Actions drop-down for a data export or import task on the Data Definition page.
To revert the previously accepted data definition, you must be a member of the Integration Admin or Customer Administrator group.In parallel to reviewing and accepting the Data Definition changes in the SAP Ariba Procurement site/realm, ensure that the necessary software components for the SAP Integration Suite, managed gateway for spend management and SAP Business Network AddOn (e.g., ARBCI1, ARBCI2, and ARBCIGR, as applicable) are upgraded to the latest version in your SAP system to consume the new fields sent from the SAP Ariba Procurement solutions.

Summary

This lesson covered the foundational role and management of Data Definitions within SAP Ariba Procurement solutions, specifically focusing on integration via the SAP Integration Suite, managed gateway for spend management and SAP Business Network.

Key concepts covered include:

  • Define the Role of Data Definitions: Understand that Data Definitions act as the blueprint or schema for procurement documents, governing how fields are captured, displayed, and integrated with backend systems.
  • Manage Integration Updates: Identify how changes to standard SAP Ariba fields or the addition of custom fields require explicit review and acceptance to maintain integration stability and avoid breaking data imports or exports.
  • Execute the Acceptance Process: Follow the administrative steps to review Changed integration events, accept field updates (at either the event or individual field level), and publish these changes to the schema.
  • Implement Safeguards and Reversions: Utilize the Revert functionality to undo unintended or incompatible Data Definition changes, ensuring configuration governance and system stability.
  • Align with Backend Systems: Recognize the necessity of upgrading Managed Gateway for Spend&Network AddOn software components in the SAP ERP or SAP S/4HANA system to support and consume new fields introduced in the Data Definition.
  • Manage Technical Requirements and Granular Controls: Enable specific parameters in the Intelligent Configuration Manager to manage updates at a granular field level and ensure the Integration or Customer Administrators upgrade the required software components (such as ARBCI1, ARBCI2, and ARBCIGR) in the backend system.