Managing Partitioned Supplier Data in SM Administration

Objective

After completing this lesson, you will be able to explain the differences between common and partitioned supplier data and describes the partitioned supplier feature.

Common vs. Partitioned Supplier Data

Common Supplier

  • General information about the supplier, such as name and headquarters address.
  • Used for strategic sourcing and supplier management activities.

Partitioned Supplier

  • Additional information about the supplier, such as payment terms and carrier method.
  • Used for procurement activities, such as requisitioning.
  • Each partitioned supplier can have multiple supplier locations (ordering addresses) and remittance locations.
  • The partitioned supplier and all of its supplier and remittance locations roll up to the common supplier.

Note

By default, the unified vendor model stores common supplier data only.

Support for Managing Partitioned Supplier Data in SM Administration

If the Support for partitioned supplier data for SAP Ariba Procurement solutions feature is enabled in your site, you can manage partitioned supplier data as well as common suppliers in SM Administration.

To use the partitioned supplier feature, your SAP Ariba site must be:

  • A new deployment, with no supplier data (including partitioned supplier data) loaded
  • Either a single-variant configuration or a multi-ERP configuration with only one child site
    • If your site uses a multi-ERP configuration, it must fully synchronize supplier data between parent and child sites and both sites must use the SAP variant
  • Suite integrated
  • Integrated with SAP S/4HANA Cloud using SAP Master Data Integration (MDI)

Restrictions for the Partitioned Supplier Feature

Currently, the Support for partitioned supplier data for SAP Ariba Procurement solutions feature has the following restrictions:

  • The feature supports guided buying requisitioning as defined in the Guided Buying Capability with SAP Ariba Buying (2NV) scope item. It does not support procurement transactions outside this scope. For details on the scope, refer to this description in the SAP S/4HANA Cloud Sourcing and Procurement documentation.
  • Currently, the best practice is to create suppliers in SAP Ariba through replication from SAP S/4HANA Cloud. Creating or updating suppliers in SAP Ariba solutions is not recommended.
  • Additional supplier types unspecified suppliers and one-time vendors are not supported.
  • Alternate payees and permitted payees are not supported.
  • Sites with the PeopleSoft and simple generic variant are not supported. Only the SAP variant is supported.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn