CREMDM04

Hi,
I'm working with the SAP vendor master content. In syndicator I use the provided map CREMDM04 for syndication to ERP systems. However the IDOC segment EDIDC40 is not mapped and it is not possible for me to map it as the MAP key is grey.
I need to map the remote system into the field RCVPRN.
Can someone explain how the mapping of EDI_DC40 segment is supposed to work?
Kind regards
Jonna

Got an answer on my OSS note

Similar Messages

Standard Vendor IDoc CREMDM04 needs to be triggered from the transactions

The Standard Vendor IDoc CREMDM04 needs to be triggered from the following transactions:
u2022XK01 (Create Vendor)
u2022XK02 (Modify Vendor)
u2022User Exit EXIT_SAPOTM_VEND01 .
The following are some more details:
u2022Receiving System: SAP PI
u2022Sending System: SAP ECC
u2022Direction: Outbound from SAP ECC.
How do we achieve it ??
BR.
Tan
Moderator message: please do more research before asking, show what you have done when posting.
Edited by: Thomas Zloch on Feb 20, 2012

Hi,
In Tx. WE42, Select the process code for the corresponding partner and bind your workflow / task inplace of the function module with the process code. Now, this will enable the idoc to get placed in the agents(identified by that workflow)inbox.
But to design the workflow, you`ll have to use tx. swdd and prior to that get some basic understanding of Business Workflow from SAP Library.
Hope the info. is helpful and reward points if so.
Regards

Single CREMDM04 XML is mapped to ADRMAS03 and CREMAS05 to 3 ECC Systems

Hi All,
What is the best possible approach to follow in a scenario when 1 single CREMDM XML is to be mapped to ADRMAS03 and CREMAS05 to be sent to 3 ECC Systems with ADRMAS03 to be posted first and then CREMAS05. The indicators in the CREMDM XML for splitting are two fields indicating the Business Unit to which each ECC System belongs to and the corresponding Business System names of these 3 ECC Systems.
Note: We have E1LFA1M segment occuring multiple times in CREMDM04.

you can do this with BPM.
In your case its - http://help.sap.com/saphelp_nw2004s/helpdata/en/11/13283fd0ca8443e10000000a114084/frameset.htm
refer to the link for deciding amongst various BPM pattern - http://help.sap.com/saphelp_nw2004s/helpdata/en/11/13283fd0ca8443e10000000a114084/frameset.htm

Difference between CREMDM04 Idoc and CREMAS04 Idoc

Hi all,
I am creating a vendor using an idoc CREMAS04.
But there are some fields which are not there in that IDOC (fields like Email address , POBOX number for other country) so i want to know that is there any other IDOC which contains all the fields for the vendor creation.
I have found the IDOC CREMDM04 which contains those fields but i want to know the difference between the CREMDM04 and CREMAS04.
I also want to know that will it make any difference is i use CREMDM04 instead of CREMAS04(like is it that all the fields of CREMAS04 is there in CREMDM04 or no).
If anybody knows ,then please let me know.
Thanks in advance.
Shruti.

to name a few:
CREMAS01 Vendor master data distribution ALE
CREMAS02 Vendor master data distribution ALE
CREMAS03 Vendor master data distribution
CREMAS04 Vendor master data distribution
CREMDM01 MDM: Mass Processing CREMAS (Vendor Master)
CREMDM02 MDM: Mass Processing CREMAS (Vendor Master + Addresses)
CREMDM03 MDM: Mass Processing CREMAS (Vendor Master + Addresses)
CREMDM04 MDM: Mass Processing CREMAS (Vendor Master + Addresses)

Import Manager 'Error 5611520 - Error Saving Key Mapping'

I am using CREDITOR_EXTRACT in R/3 to send Vendor IDoc to XI and use CREMDM04 type. XI generates an XML file that I load into MDM using a client that is set up for Inbound/Outbound. The key mappings have been turned on for the Vendor repository.
In IM, I use the standard map CREMDM04 and the system maps the incoming XML file to the vendor main table. There are few values that I have to map manually - fine. Next, when I click Import, I get a error pop-up message 'Error Saving Key Mapping - Errno 5611520'.
Has anybody experienced this when using all standard content (schemas and maps) for Vendor?
Thanks in advance.

Subbu,
Found another system that has the same versions as you do. This particular error did not appear, but we got some internal IM error. Also, the SAP training demos are on the same versions as mine.
I am using MDC R/3 as the client and the CREMDM04 schema map. Not using MDM inbound ports for now. Just loading XML file generated by XI based on CREMDM04. Do you think that I need to define a Qualified Range for this client in the Console or can it be left blank?
Thanks.

MDM interfaces does not exist in XI repository

we just installed MDM 5.5 SP3 and imported the XI MDM content into the XI repository. but when we try to create business system for R/3 and choose the interfaces, there are no MDM interface for us to choose from. example: CREMDM.CREMDM04, DEBMDM.DEBMDM06, etc. we can see interface mapping in XI repository under MDM 5.5 business content, but no interfaces with names above. what did we miss? anybody has the same problem?
Thanks
Jane

we are on ECC 5.0, system.
it's in the XI system that the interfaces are missing. we tried to create 'external destination', but we got a message says software component can not be changed. we wouldn't think we have to create an external destination for pre-delivered content, or is it so?
Thanks
Jane

Issue with the CREMDM IDoc

Hi,
I am sending the Vendor data from ECC to the external system through XI. I am using the change pointers and the IDocs are generated through BD21. IDocs are generated with no errors and the status '3', but the IDocs are not sent to XI. I checked the SM58 transaction and found the errors. Error Message is "EDISDEF: Port SAPXXX segment defn YSTP1EDY_MDMNR001 in IDoc type CREMDM04". I have created an extension for CREMDM04 and in the outbound Partner Functions I have given both Basic and extension types.
As part of our new requirement I have added couple of fields to the custom segment which was already released and in use. After changing and released the segment, a new segment defnition YSTP1EDY_MDMNR001 is generated.
I googled to find the solution for this issue, everywhere I found that the metadata in XI side should be deleted and reimported it manually in transaction IDX2. We have done this couple of times and are of no luck.
Could anyone please tell is this due to someother issue other than the metadata in XI.
Thanks,
Murali.

SAP ERP
1. do you have "set release" at the new segment and idoctype ?
2. do you have provided the new extension in the partnerprofile we20 ?
SAP XI
1. delete the imported IDoc Object in the integration repository/Service Repository
2. reimport the new IDoc (with extension).
3. check your interface objects (message interface/mappings) that the new extension name is used
4. clear metadata and reimport via idx2
maybe you have to clear the cache.
Regards,
Gordon

Getting Receiver Agreement issue in IDOC to File scenario

Hi Gurus,
            Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
      Interface : VEND_IDOC_OUT_MI
      Message Type : CREMDM.CREMDM04
Receiver:
      Interface : VEND_FILE_IN_MI
     Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
                                              Service ---> SAPERP
                                             Interface--> VEND_IDOC_OUT_MI
                                             Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
                                           Service       --> IDOC2FileReceiver
                                           Interface    ---> VEND_FILE_IN_MI
                                           Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
                                     VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
Subhadip

Hi Babu,
           In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
     <xsd:complexType name="VEND_FILE_DT">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               8f584d80456311dccd680018fe79f69b
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb0390c11dc843000188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Code
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb4390c11dc84e800188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor name4
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb5390c11dcbe3400188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor City
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb6390c11dc896100188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor PO Box
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0335fd11dc9e9600188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor House No & Street
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0435fd11dc98b000188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Postal Code
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0535fd11dc870500188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Country
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7ca8d600403b11dcc9bd00188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Tax Number 1
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7040e611dcce4300188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Telephone number
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7140e611dc8f3900188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         VAT Registration Number
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7240e611dccef700188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Account Number of Vendor or Creditor
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7340e611dcb3bc00188bd09370
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Import Bank Details qualifier table not getting mapped in vendor scenario

Hi All,
I am using MDM5.5 SP5.
Trying to import the IDoc CREMDM04 from ECC 5.0 to MDM.
Using the note 830864 i have copied all the reference data to MDM using the xml that was generated by the program referred in the note..
But Bank details is missing in this reference data. If i try to use the map 99 for bank details i get the error msg "The map cannot be loaded because the table "Bank details" is not a source".
How do I get the bank reference data into MDM .
If I skip this step and i try to import the xml file of CREMDM04 (generated through XI). And then if i use the map 99 i get the same error.
If i use the map CREMDM04 I get the error "The map cannot be loaded because the table "E1LFA1M" is not a source".
Please help!
Thanks a lot!
Jyotika

HI Jyotika,
This usually happens when you have a lookup table which has more than one display field. You get this error because you have to create an Compound field, which might not be set in the map. In order to create a Compound filed just check wether all the individual fields in the destinations field BankDetails<X,Y,Z>(X,Y,Z are individually mapped) then just right click in any portion on the source fields and select compound filed's, it creates a Bank details field and automatically maps it to the destination fields. Some times it also maps the values; if not you got to manually map it.
I you have any problem please let me know.
Regards,
CHARAN

Vendor Master Data - General and Company Code Data

Hi,
We are collecting vendor master data requirements. The requirements that I have are for Vendor General Data, Company Code Data (Accounting Info, Payment Transactions, Correspondence etc.) and Purchasing Org Data. Out of these 3 groups I can only see Vendor General Data that is mapped to CREMDM04 in SAP supplied syndication maps. I am wondering if someone could tell me how much effort is involved to first create the structure in MDM for Company Code data and Purchasing Data and then map these additional fields to CREMDM04 fields?
Why is it that Company Code data and Purchasing Data is not mapped in pre-delivered syndication maps?
Thanks in advance,
M

Thanks Shruti for your reply.
I agree with you. However, our client is really pushing for Company Code Data and Purchasing Org data along with Vendor General Data. Now, this is something that is new to me to do. I have never done this kind of customization before.
I would really appreciate if someone from SAP could give me their recommendation and also help me answer the following questions
1. Is this doable to map and syndicate Company Code data and Purchasing Org data along with Vendor General Data
2. Is it possible to then extract the tables that hold Company Code data and Purchasing Org data from ECC and bring it back in MDM to update MDM tables (that we are going to create for this data)?
3. What's the effort involved in this customization (Considering that we will be extending our repository structure, extend the syndication map, extract new tables from ECC for MDM, create import maps for these tables to import Company Code and Purchasing Org data into MDM)
Regards,
M

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

XI Configuration Design questions with multi-mapping message mapping object

Hello,
I'm having trouble designing a particular scenario for multi-mapping. Currently i'm working with a Vendor create and change. BPM is not being used.
This is what i need:
I need a CREMDM04 to turn into one or multiple ADRMAS/CREMAS IDocs and potentially a CLFMAS IDoc based on the values in the inbound CREMDM04 IDoc.
This is what i currently have:
A CREMDM04 inbound idoc is multi-mapped to a CREMDM03 (1...9999), another CREMDM03 (0...9999), and a CLFMAS01 (0...9999). At a minimum only the first CREMDM03 IDoc will be created and at a maximum all three will be created. The parameters on creating the second CREMDM03 IDoc and the CLFMAS01 IDoc are based on the values in the inbound CREMDM04 IDoc, whereas the first CREMDM03 IDoc will always be created and the values will just be converted/mapped from the inbound CREMDM04 IDoc. This multi-mapping is currently set-up via a graphical message map and works successfully in the test-tab of the mapping object. It has a main message and has sub-messages which are the IDocs. Im mapping the CREMDM04 to a CREMDM03 to then map it through an ABAP-Class and then to an XSL where the CREMDM03 inbound structure is expected to split into ADRMAS and CREMAS Outbound IDocs for Vendor Create/Change in the remote R/3 systems.
After the graphical map we have a necessary ABAP Class call that calls a BAPI to the remote system. This ABAP Class must come after the graphical map since the parameter for the BAPI is based on a converted value from the graphical multi-map.
After the ABAP Class call there is finally an XSL message split the CREMDM IDoc into an ADRMAS and CREMAS IDoc. There need to be two interface mappings (one per ADRMAS and CREMAS) since the ABAP classes and XSLs are specific to the ADRMAS and CREMAS.
The CLFMAS IDoc can go directly to the remote system, but since its within this one multi-map, Im not sure if is possible? Im not sure if it will fail once it tries entering the XSL mapping (this is the standard CREMDM message split offered from SAP).
There are three interface mapping scenarios I can think of, but cannot get to work:
CREMDM04 to ADRMAS02
CREMDM04 to CREMAS03
CREMDM04 to CLFMAS01
Currently I have the Interface Mapping structured as follows: (I cannot get this to activate as it appears it does not work)
Multi-Mapping ==> ABAP Class Call ==> Standard XSL Message Split
How should i design the interface mapping objects and the configuration objects for this scenario?
Any help is appreciated and I definitely will reward points (no need to include it in your response).

Hi,
I suggest you may use multiple steps interface mapping. It's composited with 3 message mappings as step by step.
Mapping 1: One to one mapping. For the output schema, use a composition schema which includes those 3 IDOCs you want.
Mappign 2: ABAP Mapping. I am not sure the ABAP class you mentioned is an ABAP mapping or not. If it does, That's ok. If not,
call that ABAP class in your ABAP mapping and do corresponding change for your message. Return back the same structure as output.
Mapping 3: One to multiple mapping to split the message.
So basically as interface mapping, it's one to multiple mapping. And internally, you have 3 steps to realize the mapping.
And as my experience, for both one to multiple message mapping & multiple steps interface mapping, it works well in my project. And
in ID, you have to configure it via "advance" function in receiver determination or interface determination.
Let me know if any confusion.
Thanks
Nick

MDM Import Manager Batch

Hi everyone,
We are using the MDM Import Manager Batch to import data automatically. Can we write in our ImportBatch.ini the file name with * at the end : CREMDM.CREMDM04*.xml
because the file name comes with time stamp (CREMDM.CREMDM0420061129-103959-602.xml)
[Source]
Type=XML Schema
XML Schema=CREMDM04
File name= \...\... CREMDM.CREMDM04*.xml
DSN=
DBMS Server=
Database=
User=admin
In advance thanks,
Aklilu

Hi Aklilu,
the names of the XML files don't matter. MDIS tries to process everthing that is put into the ready folder. The ready folder is processed in a "first comes, first served" way. So there's no need to change the names. Is the time stamp in the file name really a problem? If yes, why?
> We are trying to parameter the mdis.ini and until now it does not work.
Could you specify this? In addition, I've got a few hints:
MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
Here's a sample for the MDIS.ini:
[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF:     0x0000
-- Verbose ON:      0xFFFF
-- FI Verbose:     0x0001
-- XML Verbose:     0x0002
-- MAP Verbose:     0x0004
-- THRD Verbose:    0x0008
-- PARSER Verbose: 0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose: 0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
Kind regards
Michael

IDOC Overrides the data in SAP

Hi Experts,
I am working on MDM 7.1 SP5 Vendor Master Implementation. We are maintaining all the SAP data in MDM and there is no manual intervenation at SAP ECC
So we have used standard repository , CREMDM04 as XSD and the standard process code for IDOC
Later Business has decided to maintain only one field Search Term 2 directly in SAP ECC and not part of MDM
So i have unmapped that field in the Syndication map, and also in the PI mapping .
When we syndicate the data from MDM to SAP, the IDOC overrides the search term 2 directly maintained in SAP ECC
When i checked in the IDOC posted to ECC, this field SORT2 is not part of it.
As a workaround, though SORT2 is part of only ADRMAS, still i have passed / though it is not mapped. But no luck
Could you kindly help me to resolve this
Regards,
Antony

Hi Rajesh,
I have mapped the SORT2 in MDM & as well as PI with the value /
In IDOC the sort2 value is going as / and over rides the value in SAP
I believe the / concept will work only for CREMAS so that it will not over ride the ADRMAS data which is posted to SAP
Please advice is there any work around as this issue hampers our go live
Regards,
Antony

IDOCs missing in XI

Dear MDM Gurus,
I've imported the MDM business 5.5 content to the XI, create the mapping and ALE settings, and I like to send MATMAS IDOC from ECC 6.0 to MDM with mdm_clnt_extr. But on XI side the standard logistic idocs is missing like BOMMAT04, ECMMAS02, CREMDM04, DEBMDM06, DOCMAS04, MATMAS05, etc. The ECC system cant' send the idoc because the other side the idoc schema is missing. Perhaps I have forgot to install some add-on or other component?
Regards
Almos Paksi

Hi Almos,
When you import MDM business 5.5 contents in IR, it comes without Imported Objects.
If you want to use standard XSLT mappings, u can copy it to ur namespace & use it.
What u need to do is:
Copy proper Imported Archive from MDM BUSINESS CONTENT 5.5 to ur namespace.
Import Required IDOC from ECC 6.0 system to ur namespace.
& then apply this copied XSLT mapping.
Hope this is clear to u.
If u want some help u can ask.
Thanks,
Maheshwari.

CREMDM04

Similar Messages

Maybe you are looking for