Kontakt

Ansicht
Dokumentation

UDM_INFO_MASTER_PI - Perform Configuration in SAP NetWeaver PI

UDM_INFO_MASTER_PI - Perform Configuration in SAP NetWeaver PI

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

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.

Following this Customizing activity, you have to execute the following Customizing activity Configuration for the UKMS Connection to SAP NetWeaver Process Integration.

  • You have carried out the previous Customizing activity ALE Master Data Distribution for Several FI Systems.
  • The connected system for SAP NetWeaver Process Integration (SAP NetWeaver PI), referred to as "PI System" below, is based on one of the following releases:
  • SAP NetWeaver 7.0 Enhancement Package 1 or higher

  • SAP NetWeaver 7.11 or higher

  • The FI systems connected must be connected to the PI System in the System Landscape Directory (transaction SLDAPIC).
  • To be able to use ABAP Mapping in this PI System, you have to enable this with the following parameter in the exchange profile:
com.sap.aii.repository.mapping.additionaltypes=R3_ABAP|Abap-Klasse;R3_XSLT|XSL (ABAP Engine)

The settings in SAP NetWeaver PI are described for each master data synchronization scenario (FI systems, FSCM system) for design and configuration. You make the settings using the Integration Browser (transaction XSMB_IFR in the PI System).

Landscape Directory
  1. Define a product and a software component with which the design and configuration objects are to be created.
  2. Create the technical systems for the FI systems and for the FSCM system. Enter the clients there, and the related logical systems. Select the software component that you are using for design and configuration as the Installed Product.
  3. Create the business systems for the clients that have been entered in the technical systems.

Master Data Synchronization in the FI Systems

Integration Builder: Design (Integration Repository)
  1. Import the software component created from the System Landscape Directory, and create a namespace for it.
  2. Import the IDoc interfaces under Imported Objects of the versions used for IDocs
    BUPA_INBOUND_MAIN_SAVE_M and BUPA_INBOUND_REL_SAVE_M
    Namespace urn:sap-com:document:sap:idoc:messages.
  3. Create the interface mappings for the messages from the FI systems to the FSCM system, and when doing so use ABAP class CL_UKMPI_MAPPING as the mapping program.
Example:
  • FI_2_FSCM_BP:
    Outbound interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Target interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Mapping program: Type ABAP class, name CL_UKMPI_MAPPING

  • FI_2_FSCM_BP_REL:
    Proceed in the same was as for interface BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02.

  1. Create similar interface mapping with ABAP class CL_UKMPI_MAPPING as the mapping program for the other direction.
Example:
  • FSCM_2_FI_BP

  • FSCM_2_FI_BP_REL

  1. Create interface mappings for determining the FI system as receiver dynamically.
Example:
  • FSCM_2_REC_BP:
    Outbound interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Target interface: ReceiverDetermination
    Namespace: http://sap.com/xi/XI/System
    Software component: SAP BASIS
    Mapping program: Type ABAP class, name CL_UKMPI_ROUTING

  • FSCM_2_REC_BP_REL
    Proceed in the same was as for outbound interface BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02.

Integration Builder: Configuration (Integration Directory)
  1. Create a configuration scenario.
  2. Import the business systems for the FI systems and FSCM system concerned from the System Landscape Directory.
  3. Complete the generated communication channels.
  4. Create a standard receiver determination for every business system of the FI systems involved.
Example:
  • Sender service: Business system of the FI system
    Interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Type of receiver agreement: Standard
    Configured receiver: Business system of the FSCM system

  • Proceed in the same was as for interface BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02.

  1. Create an enhanced receiver determination for the business system for the FSCM system.
Example:
  • Sender service: Business system of the FSCM system
    Interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Type of receiver agreement: Enhanced
    Interface mapping: FSCM_2_REC_BP

  • Proceed in a similar way as for interface BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02 with interface mapping FSCM_2_REC_BP_REL.

  1. For each business system of the FI systems involved, create an interface determination for the business system of the FSCM system.
Example:
  • Sender service: Business system of the FI system
    Interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Receiver service: Business system of the FSCM system
    Inbound interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Interface mapping: FI_2_FSCM_BP

  • Proceed in a similar way as for interface BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02 with interface mapping FI_2_FSCM_BP_REL.

  1. For each business system of the FSCM system involved, create an interface determination for the business systems of the FI systems.
Example:
  • Sender service: Business system of the FSCM system
    Interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Receiver service: Business system of the FI system
    Inbound interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    Interface mapping: FSCM_2_FI_BP

  • Proceed in a similar way as for interface BUPA_INBOUND_REL_SAVE_M.BUPA_INBOUND_REL_SAVE_M02 with interface mapping FSCM_2_FI_BP_REL.

  1. Create the receiver agreements for the two interfaces for all of the business systems in both directions.
Example:
  • Sender service: Business system of the FI system
    Receiver service: Business system of the FSCM system
    Inbound interface: BUPA_INBOUND_MAIN_SAVE_M.BUPA_INBOUND_MAIN_SAVE_M03
    Namespace: urn:sap-com:document:sap:idoc:messages
    IDoc communication channel of the receiver service

Master Data Synchronization in the FSCM System

Integration Builder: Design (Integration Repository)
  1. Import the software component created from the System Landscape Directory, and create a namespace for it.
  2. Import the IDoc interfaces under Imported Objects of the versions used of the IDocs
    DEBMAS, ADRMAS, ADR2MAS, ADR3MAS,
    Namespace urn:sap-com:document:sap:idoc:messages.
  3. Create the interface mappings for the messages from the FI systems to the FSCM system, and when doing so use ABAP class CL_UKMPI_MAPPING as the mapping program.
Example:
  • FI_2_FSCM_DEB:
    Outbound interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Target interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Mapping program: Type ABAP class, name CL_UKMPI_MAPPING

  • FI_2_FSCM_ADR:
    Proceed in the same was as for interface ADRMAS.ADRMAS03.

  • FI_2_FSCM_ADR2:
    Proceed in the same was as for interface ADR2MAS.ADRMAS03.

  • FI_2_FSCM_ADR3:
    Proceed in the same was as for interface ADR3MAS.ADRMAS03.

  1. Create similar interface mapping with ABAP class CL_UKMPI_MAPPING as the mapping program for the other direction.
Example:
  • FSCM_2_FI_DEB

  • FSCM_2_FI_ADR

  • FSCM_2_FI_ADR2

  • FSCM_2_FI_ADR3

  1. Create interface mappings for determining the FI system as receiver dynamically.
Example:
  • FSCM_2_REC_DEB
    Outbound interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Target interface: ReceiverDetermination
    Namespace: http://sap.com/xi/XI/System
    Software component: SAP BASIS
    Mapping program: Type ABAP class, name CL_UKMPI_ROUTING

  • FSCM_2_REC_ADR
    Proceed in the same was as for outbound interface ADRMAS.ADRMAS03.

  • FSCM_2_REC_ADR2
    Proceed in the same was as for outbound interface ADR2MAS.ADRMAS03.

  • FSCM_2_REC_ADR3
    Proceed in the same was as for outbound interface ADR3MAS.ADRMAS03.

Integration Builder: Configuration (Integration Directory)
  1. Create a configuration scenario.
  2. Import the business systems for the FI systems and FSCM system concerned from the System Landscape Directory.
  3. Complete the generated communication channels.
  4. Create a standard receiver determination for every business system of the FI systems involved.
Example:
  • Sender service: Business system of the FI system
    Interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Type of receiver agreement: Standard
    Configured receiver: Business system of the FSCM system

  • Proceed in the same way as for interfaces ADRMAS.ADRMAS03, ADR2MAS.ADRMAS03, ADR3MAS.ADRMAS03.

  1. Create an enhanced receiver determination for the business system for the FSCM system.
Example:
  • Sender service: Business system of the FSCM system
    Interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Type of receiver agreement: Enhanced
    Interface mapping: FSCM_2_REC_DEB

  • Proceed in a similar way as for interface ADRMAS.ADRMAS03 with interface mapping FSCM_2_REC_ADR.

  • Proceed in a similar way as for interface ADR2MAS.ADRMAS03 with interface mapping FSCM_2_REC_ADR2.

  • Proceed in a similar way as for interface ADR3MAS.ADRMAS03 with interface mapping FSCM_2_REC_ADR3.

  1. For each business system of the FI systems involved, create an interface determination for the business system of the FSCM system.
Example:
  • Sender service: Business system of the FI system
    Interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Receiver service: Business system of the FSCM system
    Inbound interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Interface mapping: FI_2_FSCM_DEB

  • Proceed in a similar way as for interface ADRMAS.ADRMAS03 with interface mapping FI_2_FSCM_ADR.

  • Proceed in a similar way as for interface ADR2MAS.ADRMAS03 with interface mapping FI_2_FSCM_ADR2.

  • Proceed in a similar way as for interface ADR3MAS.ADRMAS03 with interface mapping FI_2_FSCM_ADR3.

  1. For each business system of the FSCM system involved, create an interface determination for the business systems of the FI systems.
Example:
  • Sender service: Business system of the FSCM system
    Interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Receiver service: Business system of the FI system
    Inbound interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    Interface mapping: FSCM_2_FI_DEB

  • Proceed in a similar way as for interface ADRMAS.ADRMAS03 with interface mapping FSCM_2_FI_ADR.

  • Proceed in a similar way as for interface ADR2MAS.ADRMAS03 with interface mapping FSCM_2_FI_ADR2.

  • Proceed in a similar way as for interface ADR3MAS.ADRMAS03 with interface mapping FSCM_2_FI_ADR3.

  1. Create the receiver agreements for the four interfaces for all of the business systems in both directions.
Example:
  • Sender service: Business system of the FI system
    Receiver service: Business system of the FSCM system
    Inbound interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    IDoc communication channel of the receiver service

  • Sender service: Business system of the FSCM system
    Receiver service: Business system of the FI system
    Inbound interface: DEBMAS.DEBMAS06
    Namespace: urn:sap-com:document:sap:idoc:messages
    IDoc communication channel of the receiver service

  • Proceed in the same way as for interfaces ADRMAS.ADRMAS03, ADR2MAS.ADRMAS03, ADR3MAS.ADRMAS03.






Fill RESBD Structure from EBP Component Structure   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 17244 Date: 20240523 Time: 163242     sap01-206 ( 141 ms )