Explaining the Integrated Object Model for the Business Partner

Objective

After completing this lesson, you will be able to explain the Integrated Object Model for business partner.

SAP Master Data Governance Integrated Object Model for Business Partner

Integrated Object Model: Business Partner

Master data governance provides a directory of Business Partners (organizations, persons, groups of persons). This directory contains data primarily used for identification (for example, name, address, ID numbers, and so on). The master data governance objects like Customer and Supplier will be based on this directory and offer seamless integration with customer-specific data and supplier-specific data.

A Business Partner could be a Customer, Supplier, Prospect, Bidder, Contact Person, and so on.

Integrated Object Model: SAP Business Partner

The entity type Business Partner is a generic application for business partner management (maintaining organizations, persons, and groups of persons).

The slide explains the SAP Business Partner. First maintain the general data of the business partner. Depending on the role (customer, supplier, prospect, and so on), maintain the relevant attributes for your business partner. Once you have created your business partner, connect the different business partner using relationships. Last, use the business partner in different solutions.

Integrated Object Model: Solutions for Customers, Suppliers, and Business Partner Fundamentals

A business partner typically consists of attributes (general data), which are relevant for all roles. But the business partner also has role-dependent attributes, which you maintain in customer governance or supplier governance.

A business partner typically consists of attributes (general data), which are relevant for all roles. But the business partner also has role-dependent attributes, which you maintain in customer governance or supplier governance.

All solutions use the SAP BP as the central anchor for identifying data:

Business Partners that are both a customer and supplier are represented by one Business Partner (BP) only.

Business Partner governance as the basis for:

  • Customers limiting their governance scope to BP data only
  • Solutions only being based on SAP BP (for example, service industries)

Transition from Business Partner Governance to Supplier Governance / Customer Governance without disruption.

The BP Governance Data Model

The following figure illustrates the data model of the Business Partner Governance.

The image shows that the business partner governance data model consists of the business partner roles: organization, person, or group. The address has the attributes phone, fax, email, URL, and address versions. The business partner data consist of the central data, roles, bank accounts, payment cards, identification numbers, and so on.

The Customer Governance Data Model

The following figure illustrates the Customer Governance data model.

The customer governance data model extends the business partner data model by ERP customer-specific data like: general data, documents, classification, unloading points, sales area data, or tax indicators.

The Supplier Governance Data Model

The following figure illustrates the Supplier Governance data model.

The supplier governance data model extends the business partner data model by ERP vendor-specific data like: general data, documents, classification, company code data, and purchasing organization data.

Customer/Vendor Integration

CVI complex partner data contains:

  • Business partner data
  • Customer data
  • Vendor data

Business Partner/Customer/Vendor data are partly redundant (name and address data). The customer and vendor data are synchronized with central business partner data using CVI - Customer/Vendor Integration. When you save your created or changed Business Partner, the corresponding customer and vendor data are updated automatically.

The Customer/Vendor Integration (CVI), as shown in the figure, is a complex interface which contains business-partner-specific data as well as customer- and vendor-specific data. CVI synchronizes and distributes all data into general tables and application-specific tables

When you create a customer or supplier, SAP Master Data Governance always creates a Business Partner.

The complex interface of the CVI (Customer/Vendor Integration) contains Business Partner specific data as well as Customer and Vendor specific data. Partially, the data of the Business Partner and Customer/Vendor are redundant (BUT000 against KNA1 & LFA1 data). For instance, Name and Address specific attributes are available in both persistencies. Customer- or Vendor-specific data is routed through the Customer/Vendor- specific interface and combined with the Business Partner central data. On commit, the Business Partner and corresponding Customer and/or Vendor is maintained or created.

General data is stored in business partner tables (BUT000, BUT100, BUT020).

Application data is stored in already used customer/vendor tables (KNA1, KNVV, LFA1).

CVI synchronizes and distributes all data into general tables and application-specific tables.

The following figure shows some related tables of the vendor master record explaining what their purposes are as a simplified data model.

The diagram shows the Vendor block the Vendor General Data like Company Code Data, Bank Data and also Address Data Link, which points to the Central Address Data tables.

Update Supplier Master Data

Business Example

You are acting as a business user of the purchasing department. You are supposed to maintain supplier master data to change some relevant data of an existing supplier master record using the SAP Master Data Governance system.

At the end of this exercise, you will be able to complete the following tasks:

  • Use the search capabilities of SAP Master Data Governance for Business Partner.

  • View and update an existing supplier master data record with SAP Master Data Governance.

  • View the change history of the supplier master data record in the SAP S/4HANA system.