Ansicht
Dokumentation

UDM_INFO_MASTER_PI01 - Perform Configuration for Connection of UKMS to SAP NetWeaver PI

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

In this Customizing activity you can find the information you require if both of the following prerequisites apply:

• You want to connect several accounting systems (FI systems) to an SAP Financial Supply Chain Management system (FSCM system) in which SAP Collections Management or SAP Credit Management runs.

• You have not set up a central master data system, but create the customer master data decentrally in the FI systems and process it there.

This Customizing activity describes both scenarios: master data synchronization in the FI systems or the FSCM system.

You make these settings in the SAP NetWeaver Process Integration (SAP NetWeaver PI) system, referred to as "PI System" below. Note: The following link is intended for information only, and not with actually processing the Customizing activities: UKMS Connection to SAP NetWeaver Process Integration (SAP NetWeaver PI).

The PI system connected is based on one of the following releases:

• SAP NetWeaver 7.0 Enhancement Package 1 or higher

• SAP NetWeaver 7.11 or higher

To execute Customizing, in the PI system choose SAP NetWeaver -> Application Server -> Basis-Services -> Unified Key Mapping Service (UKMS) -> UKMS Connection to SAP NetWeaver Process Integration (SAP NetWeaver PI).

Depending on the synchronization scenario, you have to make the following settings:

Master Data Synchronization in the FI Systems

1. In the Customizing activity Define Number Range Object, create a number range object for the FSCM system business partner. If you want to enter a letter as a prefix when assigning the number in the FSCM system, you could for instance use NUMC09 as the domain for the number length. Indicate the number range as an internal number range.

Note that the number range object for the business partner in the FSCM system has to be created corresponding to the numbers created (optional prefix and numerical part).

1. In the Customizing activity Configure Key Mapping, define key mapping for the business partner:

• Under Message, assign a key and description to the key mapping for the business partner. Enter the message that you configured in the PI system (example: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03). The namespace is urn:sap-com:document:sap:idoc:messages.

• Under Mapping enter field BPARTNER as an element. Also enter the newly created number range, and the prefix if necessary. Enter the value BUS1006 as the main context.

• Under Path enter the following path in the message, so that the program can find the field to be exchanged quickly:

1	IDOC
	2	E101BUS_EI_EXTERN
	3	E101BUS_EI_HEADER
	4	E101BUS_EI_INSTANCE

1. Create key mapping for the business partner relationships:

• Under Message, assign a key and description to the key mapping for the business partner. Enter the message that you configured in the PI system (example: BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02). The namespace is urn:sap-com:document:sap:idoc:messages.

• Under Mapping, enter the same data as in the key mapping for the business partner.

• Under Path, enter the following path in the message:

1	IDOC
	2	E101BURS_EI_EXTERN
	3	E101BURS_EI_HEADER
	4	E101BURS_EI_INSTANCE

Master Data Synchronization in the FSCM System

1. In the Customizing activity Define Number Range Object, create a number range object for the customers and the contact persons in the FSCM system. If you want to place a letter as the prefix when assigning the numbers of the customers in the FSCM system, you can for instance use NUMC09 as the domain for the number length. Indicate the number range as an internal number range.

Note that the number range object for the customers in the FSCM system has to be created corresponding to the numbers created (optional prefix and numerical part).

Enter the value NUMC10 as the domain for the number length for the number range of the contact persons. Indicate the number range as an internal number range.

1. In the Customizing activity Configure Key Mapping, define key mapping for the customer:

• Under Message, assign a key and description to the key mapping for the customer. Enter the message that you configured in the PI system (example: DEBMAS.DEBMAS06). The namespace is urn:sap-com:document:sap:idoc:messages.

• Under Mapping, enter the field KUNNR as the element that is to be exchanged during mapping. Also enter the newly created number range for the customer, and the prefix if necessary. Enter the value KNA1 as the main context.
  Create entries for the following fields, in the same way as for field KUNNR:
  EKVBD, FISKN, KNKLI, KNRZA, KNRZB, KNRZE, KUNN2, LOCNR, REMIT

Enter element PARNR with the related number range for contact persons, without a prefix and with the main context BUS1006001.
Create an entry for field UEPAR in the same way as for PARNR.

• Under Path, enter the following path in the message:

1	IDOC
	2	E1KNA1M

1. Create key mapping for the address of the customer:

• Under Message, assign a key and description to the key mapping for the customer address. Enter the message that you configured in the PI system (example: ADRMAS.ADRMAS03). The namespace is urn:sap-com:document:sap:idoc:messages.

• Under Mapping enter field OBJ_ID as an element. Enter the number range for the customer, and the prefix if necessary. Enter the value KNA1 as the main context.

• Under Path, enter the following path in the message:

1	IDOC
	2	E1ADRMAS

• Under Conditions, specify which addresses are to be dealt with:
  Element OBJ_TYPE must be filled with KNA1.

• Create key mapping for the private address of the contact person:

• Under Message, assign a key and description to the key mapping for the private address of the contact person. Enter the message that you configured in the PI system (example: ADR2MAS.ADR2MAS03). The namespace is urn:sap-com:document:sap:idoc:messages.

• Under Mapping enter field OBJ_ID as an element. Specify the number range for the contact person in addition. Enter the value BUS1006001 as the main context.

• Under Path, enter the following path in the message:

1	IDOC
	2	E1ADR2MAS

• Under Conditions, specify which addresses are to be dealt with:
  Element OBJ_TYPE must be filled with BUS1006001.

1. Create key mapping for the contact person address:

• Under Message, assign a key and description to the key mapping for the contact person address. Enter the message that you configured in the PI system (example: ADR3MAS.ADR3MAS03). The namespace is urn:sap-com:document:sap:idoc:messages.

• Under Mapping enter field OBJ_ID_C as an element. Enter the number range for the customer, and the prefix if necessary. Enter the value KNA1 as the main context.
  Enter OBJ_ID_P as a second element with the related number range for contact persons and the main context BUS1006001.

• Under Path, enter the following path in the message:

1	IDOC
	2	E1ADR3MAS

• Under Conditions, specify which addresses are to be dealt with:
  Element OBJ_TYPE_C must be filled with KNA1.
  Element OBJ_TYPE_P must be filled with BUS1006001.

2

ROGBILLS - Synchronize billing plans   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 11801 Date: 20240606 Time: 123657     sap01-206 ( 130 ms )