Materiales

8.1 Message Flow

The syndication requires a correct setup of the SAP remote systems and PI. Refer to the IT Scenario Configuration Guide available on SAP Service Market Place, Tips and Tricks for MDM Vendor Distribution and chapter MDM Vendor PI Content of this document for details.

The (recommended) message flow between MDM and SAP ERP remote systems is realized with the CREMDM, CREMAS and ADRMAS IDoc types. MDM sends CREMDM XML messages to PI. The transfer from MDM to PI is either done via FTP or the MDM PI Adapter. PI is responsible for the transformation and splitting of the XML message into the ADRMAS and CREMAS IDocs (see Interface (XSLT) Mappings) and the correct routing to ERP. The IDocs are transferred via the IDoc Adapter from PI to ERP.

CAUTION

It is absolutely mandatory that you configure PI in a correct way. Ensure that the

message split has the correct sequence. Address IDocs must be sent always before the Vendor IDocs. Otherwise ERP will not be able to process the IDocs correctly.

8.2 Interface (XSLT) Mappings

As mentioned above the CREMDM message that is sent from MDM to PI is split into different IDoc messages. The resulting Vendor (CREMAS) IDocs carry one single record as the ALE inbound processing in R/3 or ERP is not mass capable. Furthermore the address information is sent to R/3 or ERP using a specific IDoc (ADRMAS).

Some fields of the Vendor (CREMAS) IDoc are available in the Address IDoc, too. As the Address IDoc is the first, leading IDoc the duplicate fields of the Vendor IDocs are marked with the No Data Sign that is a slash /. ALE inbound is using the already existing values of the address IDoc instead (refer to SAP Note 384462 for details).

CAUTION

It is absolutely mandatory that you configure PI in a correct way. Ensure that the

message split has the correct sequence. Address IDocs must be sent always before the Vendor IDocs. Otherwise ALE will not be able to process the IDocs correctly. MDM is using the message split to enable the Business Address Service (BAS) usage. BAS supports an additional amount of address fields as well as the possibility to define extended address checks. An additional bonus is that using the BAS ensures that all address fields have exactly the same Meta Data (field length, customizing data, and so on) through all SAP systems. It’s strongly recommended to do the message split and to use BAS.

Furthermore the Payment Method element <ZWELS> of the company code data segment

<E1LFB1M> is re-formatted. As the source of this field is a multi-valued hierarchy in MDM, the value of the field is a comma separated string. The XSLT mapping removes the delimiters from the string.

Example

The record in MDM has four payment methods 1, 7, A, and C. The output of Syndicator respectively MDSS for element <ZWELS> in the company code data segment

<E1LFB1M> is the value 1, 7, A, C. The XSLT mapping on PI transforms the <ZWELS>

value into the required format 17AC.

8.3 Field Mappings

Field mappings are generally listed in the attached Excel file Field Mapping and Check Tables

Vendor.xls. In a few cases the Vendor Syndication Map uses codes and/or cloned fields instead of the remote keys and/or mentioned field mappings:

Table / Tuple Field Destination Fields

Vendors Remote Key Value Clone: <E1LFBKM> LIFNR, <E1ADRMAS>

OBJID, <E1LFASM> LIFNR, <E1LFB1M>

LIFNR. <E1LFM1M> LIFNR, <E1LFB5M>

LIFNR

Language Remote Key Clone: <E1BPAD1VL> LANGU_CR,

<E1BPAD_REM> LANGU

Language ISO Code Clone: <E1BPAD1VL> LANGU_ISO,

<E1BPAD_REM> LANGU_ISO Regional Structure Additional City

Code

<E1BPAD1VL1> HOMECITYNO

Regional Structure City Code <E1BPAD1VL> CITY_NO Regional Structure District Code <E1BPAD1VL> DISTRICT_NO Regional Structure PO Box City

Code

<E1BPAD1VL> PBOXCIT_NO

Regional Structure Street Code <E1BPAD1VL> STREET_NO

Region Code <E1BPAD1VL> Region

Region for PO Box Code <E1BPAD1VL> PO_BOX_REG Transportation Zone Code <E1BPAD1VL> TRANSPZONE

Bank Details Region Code <E1LFBKM> PROV2

Company Code Data Accounting Clerk Code <E1LFB1M> BUSAB House Bank Code <E1LFB1M> HBKID Payment Methods Code <E1LFB1M> ZWELS Recipient Type Code <E1LFB1M> QSREC Reconciliation Account Code <E1LFB1M> AKONT Tolerance Group (BP/GL) Code <E1LFB1M> TOGRU Tolerance Group (Invoice) Code <E1LFB1M> TOGRR Withholding Tax Codes Code <E1LFB1M> QSSKZ Withholding Tax Country Code <E1LFB1M> QLAND Dunning Data Dunning Area Code <E1KNB5M> MABER

Dunning Clerk Code <E1KNB5M> BUSAB Purchasing

Organization Data

Mode of Transport for Foreign Trade

<E1LFM1M> EXPVZ

Table / Tuple Field Destination Fields Office of Exit or Entry for Foreign

Trade

<E1LFM1M> ZOLLA

Planning Calendar <E1LFM1M> MRPPP Planning Cycle <E1LFM1M> LFHRY Rounding Profile <E1LFM1M> RDPRF

8.3.1 Bank Details & Bank Master

The syndication of Bank Details and Bank Master records differs from the import. The reason is that the SAP ERP remote system requires a full set of the data within the IDoc segment <E1LFBKM>.

Missing and/or empty elements are interpreted as value deletions. The Syndication Map uses both fields of the Bank Details tuple and its Bank lookup main field to create a complete segment.

8.4 Predefined Field Values for CREMDM04

Some fields of the Syndication Map carry predefined values. The values are set in MDM Syndicator as Static Text for the following Destination Items (IDoc fields or attributes).

CAUTION

If you change the existing Vendor Syndication Map or create one of your own, you must keep in mind that the SAP ERP remote system always expects a complete segment for IDoc inbound processing. Any missing and/or empty field is handled as a value deletion in SAP ERP.

8.4.1 Begin & Segment Attributes

Both the BEGIN and the SEGMENT attributes are mandatory within the CREMDM IDoc. The BEGIN attribute belongs to the <IDOC> segment whereas the SEGMENT attribute is part of each data carrying segment like <E1LFA1M>, <E1LFBKM>, and so on. It is mandatory that the BEGIN attribute and all SEGMENT attributes of used IDoc segments contain the value 1. Otherwise the IDoc inbound processing in the SAP ERP remote system might fail.

8.4.2 Message Function Element

The Message Function Element <MSGFN> is usually a part of data carrying segments like

<E1LFA1M>, <E1LFBKM>, and so on (exception: <E1ADRMAS> and all of its children do not use the message function). The message function defines the inbound processing action of the SAP ERP remote system. The Vendor Syndication Map is always using value 005 that triggers a replacement of previous information. Other valid values and their related actions are:

003 Delete: Message contains objects to be deleted 004 Change: Message contains changes

005 Replace: This message replaces previous messages 009 Original: First message for process

023 Wait/Adjust: Data should not be imported 018 Resend

8.4.3 Specific Address Values

To ensure the correct inbound processing of Vendor (CREMAS) and Address (ADRMAS) IDocs in SAP ERP remote systems, the CREMDM IDoc created by the Vendor Syndication Map must contain some specific information.

Specific Values

Fields in segment <E1ADRMAS> must have the following values:

OBJ_TYPE = LFA1 CONTEXT = 0001

Fields in segment <E1BPAD1VL1> must have the following values:

ADDR_GROUP = BP No Data Sign

Some fields of the Vendor IDoc are available in the Address IDoc, too. As the Address IDoc is the first, leading IDoc the duplicate fields of the Vendor IDocs are marked with the “No Data Sign” that is a slash “/”. ALE inbound is using the already existing values of the address IDoc instead (refer to SAP Note 384462 for details).

The fields in segment <E1LFA1M> are:

ANRED, DATLT, LAND1, NAME1, NAME2, NAME3, NAME4, ORT01, ORT02 PFACH, PSTL2, PSTLZ, REGIO, SORTL, SPRAS, STRAS, TELBX, TELF1 TELF2, TELFX, TELTX, TELX1, ADRNR, PFORT, TXJCD, LZONE, The field in segment <E1LFA1A> is:

LFURL

8.5 Predefined Field Values for GenericVendor

If you distribute data to a new BI system that uses a web service base data source for inbound processing, the XML file requires the correct by namespace. The namespace is defined in the syndication map (see screenshot below).

Figure: Generic Vendor Map Properties

8.6 Completion of the delivered Map Templates

All delivered syndication maps are templates. You have to add some specific settings before you can use them in a productive environment. Therefore open a syndication map with MDM Syndicator.

Switch to tab Map Properties.

Check that property Remote Key Override is set to your remote system. This setting ensures that MDM Syndicator respectively MDSS use the correct key mapping information when creating the XML message. Using this property you can control which keys shall be distributed to your BI system.

Check that property Suppress Records without Key is marked. This ensures that only those records are distributed back to the remote systems that were previously imported from the same system.

Use properties XML File Output and Max Records Per Output File to control the amount of records to be distributed in one single XML message.

Use property Suppress Unchanged Records to control if you want to send always all records or changed records (delta distribution) only.

The screenshot below shows the default properties of map _CREMDM04.

Figure: Syndication Map _CREMDM04 default Properties

Completing the map is a mandatory step to use the automatic syndication!

8.7 MDSS usage

Currently the outbound ports for distributing MDM Vendor XML messages are defined as manual ports. This configuration setting has been made for some reasons. The delivered Syndication Maps are not yet complete. You have to complete the maps according to your distribution scenario and furthermore to add some system landscape specific information in the maps. As SAP neither knows your distribution scenario nor your system landscape, these values cannot be predefined. Use MDM Syndicator once to finish the maps. Then you can use MDM Console to configure the outbound ports for automatic processing.