SAP Customer/Vendor Integration (CVI)

Customer Vendor Integration

      CVI is separated into 2 part.


1. CVI Configuration in S4/HANA system
2. CVI Synchronization

CVI Configuration

In S4/HANA, If we want to make it Business Partner as a Leading Object to maintain Customer or Vendor then we must do CVI Configuration.

Limitation of Customer/Vendor objects without CVI

-> Only single address we can maintain for each customer or vendor.

      -> No relation supports between customer and vendor

      -> No time dependency data we can have

      -> In S4/HANA we have single business objects as ‘BP’.

      -> BP is capable of centrally managing master data of BP, Customer, Vendor

Customer

·       Customer is a BP to which we sell our Goods or Services.

·       Some customer information is specific to a company (Company code data) or sales unit (Sales area data).

Vendor

·       Vendor is a BP from which we buy goods or services.

·       Some vendor information is specific to a company (Company code data) or purchasing unit (Purchase area data).

CVI Complex Interface:

                            


Steps to Configure CVI:

Account Group:

·      👉Account group defines what kind of customer or vendor it is.
  👉It can be ship to party or it can be sold to party.
  👉So, depend on the account grouping it can be classified.

·  

Number Ranges:

2 Types of Number Ranges:

·       👉External Number Ranges: Externally giving number to objects or coming from external          system.

·       👉Internal Number Ranges: System will generate numbers.

 

Configuration of CVI

Creation of Account group:

For Customer: -

SPRO -> Financial Accounting -> Account Receivable and Account Payable -> Customer Accounts -> Master Data -> Preparation of Creating Customer Master Data -> Define Account Groups with Screen Layout.

For Supplier: -

SPRO -> Financial Accounting -> Account Receivable and Account Payable -> Supplier Accounts -> Master Data -> Preparation of Creating Supplier Master Data -> Define Account Groups with Screen Layout.

Creating Number Ranges for Customer Account Group:

SPRO -> Financial Accounting -> Account Receivable and Account Payable -> Supplier Accounts -> Master Data -> Preparation of Creating Supplier Master Data -> Create Number Ranges for Customer Accounts

Assign Number Range to Account Group

SPRO -> Financial Accounting -> Account Receivable and Account Payable -> Supplier Accounts -> Master Data -> Preparation of Creating Supplier Master Data -> Assign Number Ranges to Customer Account Groups

Creating Number Range for Business Partner

SPRO -> Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Number Ranges and Groupings -> Define Number Ranges

Assigning Number Range to Business Grouping

SPRO -> Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Number Ranges and Groupings -> Define Groupings and Assign Number Ranges

Define Number Assignment for Direction BP to Customer

SPRO -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Partner Settings -> Settings for Customer Integration -> Field Assignment for Customer Integration -> Assign Keys -> Define Number Assignment for Direction BP to Customer


In next blog, will perform this operations in real system. 

Comments

Post a Comment

Popular posts from this blog

Extend the MDG Business Partner – Node Extension (Reuse Option)

Image
So, here we are going to add a new entity to the company code data level, as shown in the above figure. Steps:- Extension of S4 API Structures To get the API structures, we need to go to the standard BP handler class. In Below structure, we need to add our own API structure. Class ‘ CL_MDG_BS_ECC_HANDLER ’. Table Type ‘ MDG_BS_BP_TT_ECC_EXTERN ’. Data Dictionary Object Creation Structures For Genil model extensions: Creation of Table to store this Secret number data in backend active table Extension of BP data model with new Entity Generate Data Model specific structures Create and Implement BP Handler Class Below methods we need to re-define GET_OBJECT_DATA_BY_ENTITY SORT_ENTITIES MAP_DATA_2API MAP_DATA_2STA PREPARE_EI_HEADER_MAP_2API READ_OBJECT_DATA SAVE_ADDITIONAL_OBJECT_DATA CONSTRUCTOR Below methods we have created newly READ_VENDOR_BY_LIFNR READ_VENDOR MAP_BP_ZSECRET_N_2API MAP_BP_ZSECRET_N_2STA CONSTRUCTOR METHOD  constructor .    ...
Read more

SAP MDG Data Modelling

Image
·        Data model is to define the structure of the data storage. ·        During Master data processing, a change request is used to store the data which is in process of changing in staging area. ·        The data model can define reuse area that is used for data storage after completion of change request. ·        In this case the system moves the data from staging area to a storage location using access class of the reuse area. This storage location is called active area. ·        In case no reuse area is defined, the same database table which is used for staging area, are also used to store active data. ·        Then no access class is involved, the system does not move the data to other system or any other table then MDG generated tables which is used as active area. In simple term, Data Mode...
Read more