Ansicht
Dokumentation

CVPEOP_GEN_INFO - General Information

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

In addition to the subnode Registration of System Landscape, this set of Customizing activities provides advanced configuration options to set up the end of purpose (EoP) check for customer and supplier data master data (C/V master data). You can use these additional configuration options to meet the requirements of a more complex system landscape with dedicated leading and dependent systems for the data.

The Customizing activities listed under this node are used to set up your system landscape for the following EoP check scenarios:

Scenario 1: One Leading System with Multiple Dependent Systems

In this scenario, you manage all your customer/ supplier master data in a single leading system and replicate it to a group of dependent systems.

To configure your system landscape for this scenario, you can use both the regular system landscape registration provided with the Customizing structure Registration of System Landscape as well as the advanced configuration options described here. When using the advanced system registration though, you can define the order in which dependent systems are called by the leading system (regardless of the connection type defined for that system).

Scenario 2: Multiple Leading Systems

In this scenario, you have multiple leading systems. One of these systems is both leading system and dependent system at the same time.

Example: Your landscape consists of three ERP systems (ERP1, ERP2, ERP3). ERP1 is the leading system for customer master data Cus.A which is replicated to systems ERP2 and ERP3. Therefore, ERP2 and ERP3 are dependent systems for Cus.A. At the same time, ERP2 is the leading system for master data Cus.Band it is thus both leading system and dependent system. ERP2 has no dependent systems.

Sample configuration: Two system groups A and B are created using criterion account group (Cus.Aassigned to account group A, Cus.Bassigned to account group B).

• For system group A, the EoP check starts in ERP1 and checks all data belonging to system group A in ERP1 and remotely in ERP2 and ERP3.

• For system group B, the EoP check starts in ERP2 and checks all data belonging to system group B in ERP2 only.

Scenario 3: Multiple Leading Systems and Multiple Dependent Systems

In this scenario, a system that is both leading and dependent system has in turn one or more dependent systems.

Example: Your landscape consists of four ERP systems (ERP1, ERP2, ERP3, ERP4). ERP1 is the leading system for customer master data Cus.A, which is replicated to systems ERP2 and ERP3. Therefore, ERP2 and ERP3 are dependent systems for Cus.A. At the same time, ERP2 is the leading system for master data Cus.B, which is replicated to dependent system ERP4.

Sample Configuration: Two system groups A and B are created using criterion account group (Cus.A assigned to account group A, Cus.Bassigned to account group B).

• For system group A, the EoP check starts in ERP1 and checks all data belonging to system group A in ERP1 and remotely in ERP2 and ERP3.

• For system group B, the EoP check starts in ERP2 and checks all data belonging to system group B in ERP2 and remotely in ERP4.

Scenario 4: One Leading System with Multiple System Groups

In this scenario, the EoP check is only carried out in those dependent systems that are relevant for a set of data, according to the system groups you defined.

Example: Your landscape consists of three ERP systems (ERP1, ERP2, ERP3). ERP1 is the leading system for customer master data Cus.Aand Cus.C. Cus.Ais replicated to systems ERP2 and ERP3, whereas Cus.Cis replicated to system ERP3 only.

Sample Configuration: Two system groups A and C are created using criterion account group (Cus.Aassigned to account group A , Cus.Cassigned to account group C). For both groups, the EoP check starts in system ERP1 as the leading system:

• The EoP check for system group A calls systems ERP2 and ERP3 to check the data.

• The EoP check for system group C, however, only calls ERP3 as this is the only dependent system for Cus.Cdata.

Scenario 5: One Dependent System with Multiple Leading Systems - Enhanced Interim Check

In this scenario, a dependent system has more than one leading system. When the EoP check is carried out locally in that system, the interim check results are sent back to their respective leading systems, according to the system groups you defined.

Example: Your system landscape consists of three ERP systems (ERP1, ERP2, ERP4). ERP1 is the leading system for master data Cus.A which is replicated to dependent system ERP2. ERP4 is the leading system for master data Cus.Dwhich is replicated to dependent system ERP2.

Sample Configuration: Two system groups A and D are created using criteria account group (Cus.Aassigned to account group A , Cus.Dassigned to account group D). When the remote EoP check in dependent system ERP2 is executed, the interim check results are sent back to their respective leading systems ERP1 and ERP4:

•,,Interim check results of system group A are sent to leading system ERP1 only.

•,,Interim check results of system group D are sent to leading system ERP4 only.

To meet the requirements of above-mentioned scenarios, you can create system groups with specified leading and dependent systems. The EoP check can then be performed according to the system groups you defined to achieve comprehensive check results.

To use the advanced configuration options for your system landscape, you must make the following Customizing settings:

• Register systems that you want to assign to system groups in Customizing activity Define Systems.

• Determine the communication type for each system (RFC or via SOA service) in Customizing activities Make Technical System Settings and Make SOA Settings.

• Define system groups, specify leading system dependent systems using Customizing activity Define System Groups.

• Maintain BRFplus business rules to assign your customer/ supplier master data to system groups according to predefined criteria, for example ID, ID type or account group. Go to Customizing activity Configure BRFplus Decision Table to make the necessary settings.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 8130 Date: 20240523 Time: 171445     sap01-206 ( 150 ms )