Explaining Suite Integration


After completing this lesson, you will be able to Summarize key concepts related to suite integration.

Understanding the Key concept of suite integration

We are implementing our SAP Ariba Strategic Sourcing solutions before deploying SAP Ariba Buying and Invoicing. I was advised we will need to be cautious of our company's master data due to the site being Suite Integrated. What does that mean, and what do we need to be mindful of?

Suite Integration is a term that is used when SAP Ariba Sourcing and Procurement modules are used within the same realm and function as a collaborative system.

Benefits of Suite Integration

  • Single log-in location for individuals who are users of both systems
  • Simplified master data management
  • Unified view of all relevant content, aggregated across SAP Ariba applications
  • Truly seamless cross-application workflows (examples: contracts visibility, reporting)

Master Data Synchronization and Administration

The master data that is used between the two modules within one site will overlap. In short, data elements will mostly be managed on procurement'sCore Administration menu, with exceptions such as regions and departments. We will want to consult with the Buying and Invoicing deployment team for administering shared master data items like commodity codes, units of measure, currencies, common supplier data, etc.

Site administration within a Suite Integrated realm is managed within two separate areas, based upon where the information ultimately resides.

Manage ﹥ Administration:

Administration includes SAP Ariba Strategic Sourcing controlled data and configurations, mainly: reporting settings, departments, regions, event messaging templates, Sourcing parameters, and branding settings.

Manage ﹥ Core Administration:

Core Administration allows you to manage SAP Ariba Procurement controlled data and configurations. Most shared master data will need to be imported under Core Administration within Suite Integrated realms.

Customer Administrators will need to make sure that they are in the correct administrative area while completing administrative tasks. If a Customer Administrator does not see a feature in the Administration section, they are likely under the wrong area.

Strategic Sourcing and Procurement

The following master data will be shared between Strategic Sourcing and Procurement:

  • Users: All users have data that will be shared, but Procurement users will need to have their partitioned data added.
  • Common Suppliers: Suppliers need to have partitioned data added in order to transaction with them in Procurement.
  • Groups: Group assignments not only grant permissions in the site, but have user licensing implications within Strategic Sourcing.
  • Commodity Codes: The same domains have to be used; no custom and UNSPSC in the same realm. It is suggested to use UNSPSC, which is used on the SAP Business Network.
  • Units of Measure: It is recommended to use the default list of Units of Measure (UoM) to enable transactions with network suppliers.
  • Currency Conversion Rates: Rates will need to be updated frequently with the market. Administrators should have a plan on refreshing exchange rates within the site.
  • Locales: A standard list of locale values is shared.

Log in to track your progress & complete quizzes