MDM DEBMDM
Hi guys,
with the new SEPA Direct debit functionality, we are thinking of onboarding the bank details and the SEPA mandate for Customer Domain from MDM.
So that means the SEPA related details need to flow from SAP MDM 7.1 (SP08) to PI to ECC.
The notes etc. have been applied to the ECC to have this SEPA functionality, But my question is can this be supported by MDM (DEBMDM) or PI to pass this data on as part of the STANDARD IDOC??
thanks
-Adrivit
Hi Adrivit,
Please refer to SAP note - 1062489 for details and also refer the related information to it.
From what I read it seems once relevant notes have been implemented in ECC, SAP MDM only needs to provide valid Bank data e.g IBAN,BIC.These are part of standard DEBMAS idoc.
Also, Idoc PEXR2003 does not come in MDM's purview.
Going through this site would also give some background -
http://betaalvereniging.nl/en/european-transactions/
Thanks,
Ravi
Similar Messages
-
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
Janewe 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 -
How to send acknowledgement containing KUNNR from ECC to PI to MDM
Hello Experts,
I have a scenario of syndicating customer/vendor record from MDM system to ECC system using PI. File to IDOC. Since Customer and Vendor number ranges are internal to ECC system, after posting the customer and vendor record, we need to get the KUNNR or LIFNR back to MDM so that later updates using the key can be issued.
For Posting we have used DEBMDM in MDM output and mapped it to ADRMAS and DEBMAS for Customers and CREMDM for vendor outbound and mapped it to ADRMAS and CREMAS.
Now I want to understand what would be the best way to get the Customer or Vendor number back in MDM?
Using ALEAUD? Enhancing it?
or using some event mechanism which will post the DEBMAS/CREMAS back from ECC to PI?
Thanks in anticipation.
Regards,
AhmedHi,
check this ..
SOAP for IDOC demystified
http://wiki.sdn.sap.com/wiki/display/XI/UsingRequestResponseBeanModuleinFILE+Adapter
Cheers
Sunil. -
Map cannot be loaded in import manager | MDM
Hi ,
I am trying to upload some data in customer repository (I am on MDM 5.5 SP05) . I have a few XML files (IDOCS) from customer master in an ECC system ,which I am providing as a source for the import manager . In the source preview I can see the following tables
- DEBMAS06
- E1KNVIM
- E1KNVPM
Now when I try to open the import map 00_DEBMDM06_R3.map (standard map provided by SAP) it gives me an error message "the map cannot be loaded because table E1KNA1M is not a source" .
What do I need to get this file uploaded to the import manager ?
Regards
Deepak SinghHi Maheshwari/Harrison ,
I tried giving the type as XML schema as you guys suggested but now the the import manager won't open at all and I get the following error " The element DEBMAS06 is used but not declared in the DTD/Schema " .
In the console inside the customer repository > Admin > XML schemas i have made sure that the schema name DEBMDM06 points to DEBMDM.DEBMDM06.xsd that is provided in the business content with the customer repository . Infact for all the schemas( lookup tables , bank check tables , customer check tables ) i have made sure they point to the right XSD's provided in the business content for the customer repository .
Now what do you guys think is the problem ?
Regards
Deepak Singh -
MDM-XI-ECC for Master data like Vendor and customer
If there are some changes like addition or deletion of some fields in customer or vendor, then it is not possible to use the standard pre-delivered content which SAP has provided.
So in that case, how can we handle that in XI?
For example DEBMDM or CREMDM?
The predefined content splits this into two idocs CREMAS & ADRMAS and serialises and then sends to ECC.
So when there is customization of Idocs, how can we handle it?
Any clues please?
Thanks
KiranFor various reasons I would recommend not using the predefined content. Mainly for the exact scenario in which you describe. If you have to add custom fields, then you can't use the predelivered content, however you can copy the predelivered content and modify it. The MDM content for XI uses XSLT mappings, so if you are familiar with XLST then you can work with those, however I prefer to generate a graphical mapping, because it only takes a few seconds anyway. You simply have your source message be the CREMDM (or DEBMDM) format, and the target is CREMAS and ADRMAS. You simply select the top node of CREMDM and do a 1:1 mapping to CREMAS, then map the ADRC segment of CREMDM to the ADRMAS IDoc. If you use the graphical tool then you can modify your map easier if you need to add or remove fields. For example, if you want to do a IDoc reduction, then you can perform the IDoc reduction in ECC, and then swap that message type out with the one in your graphical map. Or if you want to add fields you can perform an IDoc extension in ECC, and then swap that message type out in XI. It's much easier to make these changes when you've built a graphical map.
-
Hi ,
I have few basic doubts, we have created a test port in R/3 in transaction WE21 called DEBMDM, and a port in XI in transaction IDX1 called SAPEIT.
I am using the business content for Customers, and am able to access the tables in MDM console. Whiel creating ports, the pre-defined ports appear one for BW, the default MDM and one called MDC_R3.
We have renamed MDC_R3 as EIT_900(R/3 sytem); Type as Inbound ; Code what is to be maintained here ?
According to the console reference documentation we are to maintain the folder where the inbound data appears ie the Ready folder.
So what value should we maintain here ?
Can all customer related data be uploaded using the same port ?
If not , how can different ports be created to upload data in MDM
Thanks in advance ,
Regards,
AnitaHi Anita,
an XSD is used to verify an XML. A XSD is kind of a definition on how your XML has to look like. You cannot import an XSD with Import Manager or MDIS. This doesn't make any sense.
so if you want to import an XML and you use the DEBMDM05.XSD for verfication, your XML must have the correct structure as defined by the XSD.
If you have a XSD definition like
<xsd:schema>
<xsl:element name="DEBMDM05 />
</xsd:schema>
your XML has to look like
<DEBMDM05>
</DEBMDM05>
Assuming that you use the SAP standard DEBMDM05.XSD, a valid XML file would look like this one:
<?xml version="1.0" encoding="UTF-8"?>
<DEBMDM05 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>Str</MANDT>
<DOCNUM>String</DOCNUM>
<DOCREL>Stri</DOCREL>
<STATUS>St</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>S</OUTMOD>
<EXPRSS>S</EXPRSS>
<TEST>S</TEST>
<IDOCTYP>DEBMDM05</IDOCTYP>
<CIMTYP>String</CIMTYP>
<MESTYP>DEBMDM</MESTYP>
<MESCOD>Str</MESCOD>
<MESFCT>Str</MESFCT>
<STD>S</STD>
<STDVRS>String</STDVRS>
<STDMES>String</STDMES>
<SNDPOR>String</SNDPOR>
<SNDPRT>St</SNDPRT>
<SNDPFC>St</SNDPFC>
<SNDPRN>String</SNDPRN>
<SNDSAD>String</SNDSAD>
<SNDLAD>String</SNDLAD>
<RCVPOR>String</RCVPOR>
<RCVPRT>St</RCVPRT>
<RCVPFC>St</RCVPFC>
<RCVPRN>String</RCVPRN>
<RCVSAD>String</RCVSAD>
<RCVLAD>String</RCVLAD>
<CREDAT>String</CREDAT>
<CRETIM>String</CRETIM>
<REFINT>String</REFINT>
<REFGRP>String</REFGRP>
<REFMES>String</REFMES>
<ARCKEY>String</ARCKEY>
<SERIAL>String</SERIAL>
</EDI_DC40>
<E1KNA1M SEGMENT="1">
<MSGFN>Str</MSGFN>
<KUNNR>String</KUNNR>
<ANRED>String</ANRED>
<AUFSD>St</AUFSD>
<BAHNE>String</BAHNE>
<BAHNS>String</BAHNS>
<BBBNR>String</BBBNR>
<BBSNR>Strin</BBSNR>
<BEGRU>Stri</BEGRU>
<BRSCH>CHEM</BRSCH>
<BUBKZ>S</BUBKZ>
<DATLT>String</DATLT>
<FAKSD>St</FAKSD>
<FISKN>String</FISKN>
<KNRZA>String</KNRZA>
<KONZS>String</KONZS>
<KTOKD>Stri</KTOKD>
<KUKLA>St</KUKLA>
<LAND1>DE</LAND1>
<LIFNR>String</LIFNR>
<LIFSD>St</LIFSD>
<LOCCO>String</LOCCO>
<LOEVM>S</LOEVM>
<NAME1>String</NAME1>
<NAME2>String</NAME2>
<NAME3>String</NAME3>
<NAME4>String</NAME4>
<NIELS>St</NIELS>
<ORT01>String</ORT01>
<ORT02>String</ORT02>
<PFACH>String</PFACH>
<PSTL2>String</PSTL2>
<PSTLZ>String</PSTLZ>
<REGIO>Str</REGIO>
<COUNC>Str</COUNC>
<CITYC>Stri</CITYC>
<RPMKR>Strin</RPMKR>
<SORTL>String</SORTL>
<SPERR>S</SPERR>
<SPRAS>S</SPRAS>
<STCD1>String</STCD1>
<STCD2>String</STCD2>
<STKZA>S</STKZA>
<STKZU>S</STKZU>
<STRAS>String</STRAS>
<TELBX>String</TELBX>
<TELF1>String</TELF1>
<TELF2>String</TELF2>
<TELFX>String</TELFX>
<TELTX>String</TELTX>
<TELX1>String</TELX1>
<LZONE>String</LZONE>
<XZEMP>S</XZEMP>
<VBUND>String</VBUND>
<STCEG>String</STCEG>
<GFORM>01</GFORM>
<BRAN1>String</BRAN1>
<BRAN2>String</BRAN2>
<BRAN3>String</BRAN3>
<BRAN4>String</BRAN4>
<BRAN5>String</BRAN5>
<UMJAH>Stri</UMJAH>
<UWAER>Strin</UWAER>
<JMZAH>String</JMZAH>
<JMJAH>Stri</JMJAH>
<KATR1>St</KATR1>
<KATR2>St</KATR2>
<KATR3>St</KATR3>
<KATR4>St</KATR4>
<KATR5>St</KATR5>
<KATR6>Str</KATR6>
<KATR7>Str</KATR7>
<KATR8>Str</KATR8>
<KATR9>Str</KATR9>
<KATR10>Str</KATR10>
<STKZN>X</STKZN>
<UMSA1>String</UMSA1>
<TXJCD>String</TXJCD>
<PERIV>St</PERIV>
<KTOCD>Stri</KTOCD>
<PFORT>String</PFORT>
<DTAMS>S</DTAMS>
<DTAWS>St</DTAWS>
<HZUOR>St</HZUOR>
<CIVVE>S</CIVVE>
<MILVE>S</MILVE>
<SPRAS_ISO>St</SPRAS_ISO>
<FITYP>St</FITYP>
<STCDT>St</STCDT>
<STCD3>String</STCD3>
<STCD4>String</STCD4>
<XICMS>S</XICMS>
<XXIPI>S</XXIPI>
<XSUBT>S</XSUBT>
<CFOPC>St</CFOPC>
<TXLW1>Str</TXLW1>
<TXLW2>Str</TXLW2>
<CCC01>S</CCC01>
<CCC02>S</CCC02>
<CCC03>S</CCC03>
<CCC04>S</CCC04>
<CASSD>St</CASSD>
<KDKG1>St</KDKG1>
<KDKG2>St</KDKG2>
<KDKG3>St</KDKG3>
<KDKG4>St</KDKG4>
<KDKG5>St</KDKG5>
<NODEL>S</NODEL>
<XSUB2>Str</XSUB2>
<WERKS>Stri</WERKS>
<E1KNA11 SEGMENT="1">
<KNURL>String</KNURL>
<J_1KFREPRE>String</J_1KFREPRE>
<J_1KFTBUS>String</J_1KFTBUS>
<J_1KFTIND>String</J_1KFTIND>
</E1KNA11>
<E1ADRMAS SEGMENT="1">
<OBJ_TYPE>String</OBJ_TYPE>
<OBJ_ID>String</OBJ_ID>
<OBJ_ID_EXT>String</OBJ_ID_EXT>
<CONTEXT>Stri</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<ADDR_VERS>S</ADDR_VERS>
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<TITLE>0001</TITLE>
<NAME>String</NAME>
<NAME_2>String</NAME_2>
<NAME_3>String</NAME_3>
<NAME_4>String</NAME_4>
<CONV_NAME>String</CONV_NAME>
<C_O_NAME>String</C_O_NAME>
<CITY>String</CITY>
<DISTRICT>String</DISTRICT>
<CITY_NO>String</CITY_NO>
<DISTRCT_NO>String</DISTRCT_NO>
<CHCKSTATUS>S</CHCKSTATUS>
<REGIOGROUP>String</REGIOGROUP>
<POSTL_COD1>String</POSTL_COD1>
<POSTL_COD2>String</POSTL_COD2>
<POSTL_COD3>String</POSTL_COD3>
<PCODE1_EXT>String</PCODE1_EXT>
<PCODE2_EXT>String</PCODE2_EXT>
<PCODE3_EXT>String</PCODE3_EXT>
<PO_BOX>String</PO_BOX>
<PO_W_O_NO>S</PO_W_O_NO>
<PO_BOX_CIT>String</PO_BOX_CIT>
<PBOXCIT_NO>String</PBOXCIT_NO>
<PO_BOX_REG>Str</PO_BOX_REG>
<POBOX_CTRY>DE</POBOX_CTRY>
<PO_CTRYISO>St</PO_CTRYISO>
<DELIV_DIS>String</DELIV_DIS>
<TRANSPZONE>String</TRANSPZONE>
<STREET>String</STREET>
<STREET_NO>String</STREET_NO>
<STR_ABBR>St</STR_ABBR>
<HOUSE_NO>String</HOUSE_NO>
<HOUSE_NO2>String</HOUSE_NO2>
<HOUSE_NO3>String</HOUSE_NO3>
<STR_SUPPL1>String</STR_SUPPL1>
<STR_SUPPL2>String</STR_SUPPL2>
<STR_SUPPL3>String</STR_SUPPL3>
<LOCATION>String</LOCATION>
<BUILDING>String</BUILDING>
<FLOOR>String</FLOOR>
<ROOM_NO>String</ROOM_NO>
<COUNTRY>DE</COUNTRY>
<COUNTRYISO>DE</COUNTRYISO>
<LANGU>D</LANGU>
<LANGU_ISO>DE</LANGU_ISO>
<REGION>01</REGION>
<SORT1>String</SORT1>
<SORT2>String</SORT2>
<EXTENS_1>String</EXTENS_1>
<EXTENS_2>String</EXTENS_2>
<TIME_ZONE>String</TIME_ZONE>
<TAXJURCODE>String</TAXJURCODE>
<E1BPAD1VL1 SEGMENT="1">
<ADDRESS_ID>String</ADDRESS_ID>
<LANGU_CR>S</LANGU_CR>
<LANGUCRISO>St</LANGUCRISO>
<COMM_TYPE>Str</COMM_TYPE>
<ADDR_GROUP>Stri</ADDR_GROUP>
<HOME_CITY>String</HOME_CITY>
<HOMECITYNO>String</HOMECITYNO>
</E1BPAD1VL1>
</E1BPAD1VL>
<E1BPADTEL SEGMENT="1">
<COUNTRY>DE</COUNTRY>
<COUNTRYISO>DE</COUNTRYISO>
<STD_NO>X</STD_NO>
<TELEPHONE>String</TELEPHONE>
<EXTENSION>String</EXTENSION>
<TEL_NO>String</TEL_NO>
<CALLER_NO>String</CALLER_NO>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>1</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADTEL>
<E1BPADFAX SEGMENT="1">
<COUNTRY>DE</COUNTRY>
<COUNTRYISO>DE</COUNTRYISO>
<STD_NO>X</STD_NO>
<FAX>String</FAX>
<EXTENSION>String</EXTENSION>
<FAX_NO>String</FAX_NO>
<SENDER_NO>String</SENDER_NO>
<FAX_GROUP>S</FAX_GROUP>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>1</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADFAX>
<E1BPADTTX SEGMENT="1">
<COUNTRY>DE</COUNTRY>
<COUNTRYISO>DE</COUNTRYISO>
<STD_NO>X</STD_NO>
<TELETEX>String</TELETEX>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>1</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADTTX>
<E1BPADTLX SEGMENT="1">
<COUNTRY>Str</COUNTRY>
<COUNTRYISO>St</COUNTRYISO>
<STD_NO>X</STD_NO>
<TELEX_NO>String</TELEX_NO>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>S</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADTLX>
<E1BPADSMTP SEGMENT="1">
<STD_NO>X</STD_NO>
<E_MAIL>String</E_MAIL>
<EMAIL_SRCH>String</EMAIL_SRCH>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>S</R_3_USER>
<ENCODE>S</ENCODE>
<TNEF>S</TNEF>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADSMTP>
<E1BPADRML SEGMENT="1">
<STD_NO>X</STD_NO>
<SYMB_DEST>String</SYMB_DEST>
<REC_TYPE>S</REC_TYPE>
<R_MAIL_CLT>Str</R_MAIL_CLT>
<R_MAIL>String</R_MAIL>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>S</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADRML>
<E1BPADX400 SEGMENT="1">
<STD_NO>X</STD_NO>
<COUNTRY>Str</COUNTRY>
<COUNTRYISO>St</COUNTRYISO>
<ADM_DOM>String</ADM_DOM>
<PRIV_DOM>String</PRIV_DOM>
<ORGANIZATN>String</ORGANIZATN>
<ORG_UNIT_1>String</ORG_UNIT_1>
<ORG_UNIT_2>String</ORG_UNIT_2>
<ORG_UNIT_3>String</ORG_UNIT_3>
<ORG_UNIT_4>String</ORG_UNIT_4>
<LASTNAME>String</LASTNAME>
<FIRSTNAME>String</FIRSTNAME>
<INITIALS>Strin</INITIALS>
<GENERATION>Str</GENERATION>
<X_121_ADDR>String</X_121_ADDR>
<TERM_ID>String</TERM_ID>
<TERM_TYPE>S</TERM_TYPE>
<UANID>String</UANID>
<DDA_TYPE1>String</DDA_TYPE1>
<DDA_VALUE1>String</DDA_VALUE1>
<DDA_TYPE2>String</DDA_TYPE2>
<DDA_VALUE2>String</DDA_VALUE2>
<DDA_TYPE3>String</DDA_TYPE3>
<DDA_VALUE3>String</DDA_VALUE3>
<DDA_TYPE4>String</DDA_TYPE4>
<DDA_VALUE4>String</DDA_VALUE4>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>S</R_3_USER>
<TXT_ENCODE>S</TXT_ENCODE>
<TNEF>S</TNEF>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADX400>
<E1BPADRFC SEGMENT="1">
<STD_NO>X</STD_NO>
<LOG_DEST>String</LOG_DEST>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>S</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADRFC>
<E1BPADPRT SEGMENT="1">
<STD_NO>X</STD_NO>
<PRINT_DEST>Stri</PRINT_DEST>
<STD_RECIP>S</STD_RECIP>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADPRT>
<E1BPADSSF SEGMENT="1">
<STD_NO>X</STD_NO>
<DUMMY>S</DUMMY>
<STD_RECIP>S</STD_RECIP>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<RFCDEST>String</RFCDEST>
<SSFIDSHORT>String</SSFIDSHORT>
<SSF_NS>String</SSF_NS>
<SSF_PROF>String</SSF_PROF>
<SSFIDPART1>String</SSFIDPART1>
<SSFIDPART2>String</SSFIDPART2>
<E1BPADSSF1 SEGMENT="1">
<SSFIDPART3>String</SSFIDPART3>
<SSFIDPART4>String</SSFIDPART4>
<SSFIDPART5>String</SSFIDPART5>
<SSFIDPART6>String</SSFIDPART6>
<E1BPADSSF2 SEGMENT="1">
<SSFIDPART7>String</SSFIDPART7>
<SSFIDPART8>String</SSFIDPART8>
<SSFIDPART9>String</SSFIDPART9>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADSSF2>
</E1BPADSSF1>
</E1BPADSSF>
<E1BPADURI SEGMENT="1">
<STD_NO>X</STD_NO>
<URI_TYPE>Str</URI_TYPE>
<URI>String</URI>
<STD_RECIP>S</STD_RECIP>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<URI_PART1>String</URI_PART1>
<URI_PART2>String</URI_PART2>
<URI_PART3>String</URI_PART3>
<E1BPADURI1 SEGMENT="1">
<URI_PART4>String</URI_PART4>
<URI_PART5>String</URI_PART5>
<URI_PART6>String</URI_PART6>
<URI_PART7>String</URI_PART7>
<E1BPADURI2 SEGMENT="1">
<URI_PART8>String</URI_PART8>
<URI_PART9>String</URI_PART9>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADURI2>
</E1BPADURI1>
</E1BPADURI>
<E1BPADPAG SEGMENT="1">
<COUNTRY>DE</COUNTRY>
<COUNTRYISO>DE</COUNTRYISO>
<STD_NO>X</STD_NO>
<PAGER_TYPE>Stri</PAGER_TYPE>
<PAGER>String</PAGER>
<PAGER_NO>String</PAGER_NO>
<CALLER_NO>String</CALLER_NO>
<STD_RECIP>S</STD_RECIP>
<R_3_USER>S</R_3_USER>
<HOME_FLAG>S</HOME_FLAG>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPADPAG>
<E1BPAD_REM SEGMENT="1">
<ADDR_VERS>S</ADDR_VERS>
<LANGU>S</LANGU>
<LANGU_ISO>St</LANGU_ISO>
<ADR_NOTES>String</ADR_NOTES>
</E1BPAD_REM>
<E1BPCOMREM SEGMENT="1">
<COMM_TYPE>Str</COMM_TYPE>
<LANGU>D</LANGU>
<LANGU_ISO>DE</LANGU_ISO>
<COMM_NOTES>String</COMM_NOTES>
<CONSNUMBER>Str</CONSNUMBER>
<ERRORFLAG>S</ERRORFLAG>
</E1BPCOMREM>
</E1ADRMAS>
<E1KNA1H SEGMENT="1">
<MSGFN>Str</MSGFN>
<TDOBJECT>String</TDOBJECT>
<TDNAME>String</TDNAME>
<TDID>Stri</TDID>
<TDSPRAS>S</TDSPRAS>
<TDTEXTTYPE>String</TDTEXTTYPE>
<TDSPRASISO>St</TDSPRASISO>
<E1KNA1L SEGMENT="1">
<MSGFN>Str</MSGFN>
<TDFORMAT>St</TDFORMAT>
<TDLINE>String</TDLINE>
</E1KNA1L>
</E1KNA1H>
<E1KNVVM SEGMENT="1">
<MSGFN>Str</MSGFN>
<VKORG>Stri</VKORG>
<VTWEG>St</VTWEG>
<SPART>St</SPART>
<BEGRU>Stri</BEGRU>
<LOEVM>S</LOEVM>
<VERSG>S</VERSG>
<AUFSD>St</AUFSD>
<KALKS>S</KALKS>
<KDGRP>St</KDGRP>
<BZIRK>String</BZIRK>
<KONDA>St</KONDA>
<PLTYP>St</PLTYP>
<AWAHR>Str</AWAHR>
<INCO1>Str</INCO1>
<INCO2>String</INCO2>
<LIFSD>St</LIFSD>
<AUTLF>S</AUTLF>
<ANTLF>St</ANTLF>
<KZTLF>S</KZTLF>
<KZAZU>S</KZAZU>
<CHSPL>S</CHSPL>
<LPRIO>St</LPRIO>
<EIKTO>String</EIKTO>
<VSBED>St</VSBED>
<FAKSD>St</FAKSD>
<MRNKZ>S</MRNKZ>
<PERFK>St</PERFK>
<PERRL>St</PERRL>
<WAERS>Strin</WAERS>
<KTGRD>St</KTGRD>
<ZTERM>Stri</ZTERM>
<VWERK>Stri</VWERK>
<VKGRP>Str</VKGRP>
<VKBUR>Stri</VKBUR>
<VSORT>String</VSORT>
<KVGR1>Str</KVGR1>
<KVGR2>Str</KVGR2>
<KVGR3>Str</KVGR3>
<KVGR4>Str</KVGR4>
<KVGR5>Str</KVGR5>
<BOKRE>S</BOKRE>
<KURST>Stri</KURST>
<PRFRE>S</PRFRE>
<KLABC>St</KLABC>
<KABSS>Stri</KABSS>
<KKBER>Stri</KKBER>
<CASSD>St</CASSD>
<RDOFF>S</RDOFF>
<AGREL>S</AGREL>
<MEGRU>Stri</MEGRU>
<UEBTO>Stri</UEBTO>
<UNTTO>Stri</UNTTO>
<UEBTK>S</UEBTK>
<PVKSM>St</PVKSM>
<PODKZ>S</PODKZ>
<PODTG>String</PODTG>
<E1KNVPM SEGMENT="1">
<MSGFN>Str</MSGFN>
<PARVW>St</PARVW>
<KUNN2>String</KUNN2>
<DEFPA>S</DEFPA>
<KNREF>String</KNREF>
<PARZA>Str</PARZA>
</E1KNVPM>
<E1KNVDM SEGMENT="1">
<MSGFN>Str</MSGFN>
<DOCTP>Stri</DOCTP>
<SPRAS>S</SPRAS>
<DOANZ>Str</DOANZ>
<DOVER>S</DOVER>
<NACHA>S</NACHA>
<SPRAS_ISO>St</SPRAS_ISO>
</E1KNVDM>
<E1KNVIM SEGMENT="1">
<MSGFN>Str</MSGFN>
<ALAND>Str</ALAND>
<TATYP>Stri</TATYP>
<TAXKD>S</TAXKD>
</E1KNVIM>
<E1KNVLM SEGMENT="1">
<MSGFN>Str</MSGFN>
<ALAND>Str</ALAND>
<TATYP>Stri</TATYP>
<LICNR>String</LICNR>
<DATAB>String</DATAB>
<DATBI>String</DATBI>
<BELIC>S</BELIC>
</E1KNVLM>
<E1KNVVH SEGMENT="1">
<MSGFN>Str</MSGFN>
<TDOBJECT>String</TDOBJECT>
<TDNAME>String</TDNAME>
<TDID>Stri</TDID>
<TDSPRAS>S</TDSPRAS>
<TDTEXTTYPE>String</TDTEXTTYPE>
<TDSPRASISO>St</TDSPRASISO>
<E1KNVVL SEGMENT="1">
<MSGFN>Str</MSGFN>
<TDFORMAT>St</TDFORMAT>
<TDLINE>String</TDLINE>
</E1KNVVL>
</E1KNVVH>
</E1KNVVM>
<E1KNB1M SEGMENT="1">
<MSGFN>Str</MSGFN>
<BUKRS>String</BUKRS>
<SPERR>S</SPERR>
<LOEVM>S</LOEVM>
<ZUAWA>Str</ZUAWA>
<BUSAB>St</BUSAB>
<AKONT>String</AKONT>
<BEGRU>Stri</BEGRU>
<KNRZE>String</KNRZE>
<KNRZB>String</KNRZB>
<ZAMIM>S</ZAMIM>
<ZAMIV>S</ZAMIV>
<ZAMIR>S</ZAMIR>
<ZAMIB>S</ZAMIB>
<ZAMIO>S</ZAMIO>
<ZWELS>String</ZWELS>
<XVERR>S</XVERR>
<ZAHLS>S</ZAHLS>
<ZTERM>Stri</ZTERM>
<WAKON>Stri</WAKON>
<VZSKZ>St</VZSKZ>
<ZINDT>String</ZINDT>
<ZINRT>St</ZINRT>
<EIKTO>String</EIKTO>
<ZSABE>String</ZSABE>
<KVERM>String</KVERM>
<FDGRV>String</FDGRV>
<VRBKZ>St</VRBKZ>
<VLIBB>String</VLIBB>
<VRSZL>Stri</VRSZL>
<VRSPR>Stri</VRSPR>
<VRSNR>String</VRSNR>
<VERDT>String</VERDT>
<PERKZ>S</PERKZ>
<XDEZV>S</XDEZV>
<XAUSZ>S</XAUSZ>
<WEBTR>String</WEBTR>
<REMIT>String</REMIT>
<DATLZ>String</DATLZ>
<XZVER>S</XZVER>
<TOGRU>Stri</TOGRU>
<KULTG>Stri</KULTG>
<HBKID>Strin</HBKID>
<XPORE>S</XPORE>
<BLNKZ>St</BLNKZ>
<ALTKN>String</ALTKN>
<ZGRUP>St</ZGRUP>
<URLID>Stri</URLID>
<MGRUP>St</MGRUP>
<LOCKB>String</LOCKB>
<UZAWE>St</UZAWE>
<EKVBD>String</EKVBD>
<SREGL>Str</SREGL>
<XEDIP>S</XEDIP>
<FRGRP>Stri</FRGRP>
<VRSDG>Str</VRSDG>
<TLFXS>String</TLFXS>
<PERNR>String</PERNR>
<INTAD>String</INTAD>
<GUZTE>Stri</GUZTE>
<GRICD>St</GRICD>
<GRIDT>St</GRIDT>
<WBRSL>St</WBRSL>
<NODEL>S</NODEL>
<TLFNS>String</TLFNS>
<CESSION_KZ>St</CESSION_KZ>
<E1KNB5M SEGMENT="1">
<MSGFN>Str</MSGFN>
<MABER>St</MABER>
<MAHNA>Stri</MAHNA>
<MANSP>S</MANSP>
<MADAT>String</MADAT>
<MAHNS>S</MAHNS>
<KNRMA>String</KNRMA>
<GMVDT>String</GMVDT>
<BUSAB>St</BUSAB>
</E1KNB5M>
<E1KNB1H SEGMENT="1">
<MSGFN>Str</MSGFN>
<TDOBJECT>String</TDOBJECT>
<TDNAME>String</TDNAME>
<TDID>Stri</TDID>
<TDSPRAS>S</TDSPRAS>
<TDTEXTTYPE>String</TDTEXTTYPE>
<TDSPRASISO>St</TDSPRASISO>
<E1KNB1L SEGMENT="1">
<MSGFN>Str</MSGFN>
<TDFORMAT>St</TDFORMAT>
<TDLINE>String</TDLINE>
</E1KNB1L>
</E1KNB1H>
</E1KNB1M>
<E1KNBKM SEGMENT="1">
<MSGFN>Str</MSGFN>
<BANKS>Str</BANKS>
<BANKL>String</BANKL>
<BANKN>String</BANKN>
<BKONT>St</BKONT>
<BVTYP>Stri</BVTYP>
<XEZER>S</XEZER>
<BKREF>String</BKREF>
<BANKA>String</BANKA>
<STRAS>String</STRAS>
<ORT01>String</ORT01>
<SWIFT>String</SWIFT>
<BGRUP>St</BGRUP>
<XPGRO>S</XPGRO>
<BNKLZ>String</BNKLZ>
<PSKTO>String</PSKTO>
<BRNCH>String</BRNCH>
<PROVZ>Str</PROVZ>
<KOINH>String</KOINH>
<KOINH_N>String</KOINH_N>
</E1KNBKM>
<E1KNVAM SEGMENT="1">
<MSGFN>Str</MSGFN>
<ABLAD>String</ABLAD>
<KNFAK>St</KNFAK>
<WANID>Str</WANID>
<MOAB1>String</MOAB1>
<MOBI1>String</MOBI1>
<MOAB2>String</MOAB2>
<MOBI2>String</MOBI2>
<DIAB1>String</DIAB1>
<DIBI1>String</DIBI1>
<DIAB2>String</DIAB2>
<DIBI2>String</DIBI2>
<MIAB1>String</MIAB1>
<MIBI1>String</MIBI1>
<MIAB2>String</MIAB2>
<MIBI2>String</MIBI2>
<DOAB1>String</DOAB1>
<DOBI1>String</DOBI1>
<DOAB2>String</DOAB2>
<DOBI2>String</DOBI2>
<FRAB1>String</FRAB1>
<FRBI1>String</FRBI1>
<FRAB2>String</FRAB2>
<FRBI2>String</FRBI2>
<SAAB1>String</SAAB1>
<SABI1>String</SABI1>
<SAAB2>String</SAAB2>
<SABI2>String</SABI2>
<SOAB1>String</SOAB1>
<SOBI1>String</SOBI1>
<SOAB2>String</SOAB2>
<SOBI2>String</SOBI2>
<DEFAB>S</DEFAB>
</E1KNVAM>
<E1WRF12 SEGMENT="1">
<MSGFN>Str</MSGFN>
<LOCNR>String</LOCNR>
<EMPST>String</EMPST>
<KUNN2>String</KUNN2>
<ABLAD>String</ABLAD>
</E1WRF12>
<E1WRF4M SEGMENT="1">
<MSGFN>Str</MSGFN>
<LOCNR>String</LOCNR>
<ABTNR>Stri</ABTNR>
<EMPST>String</EMPST>
<VERFL>String</VERFL>
<VERFE>Str</VERFE>
<LAYVR>String</LAYVR>
<FLVAR>Stri</FLVAR>
</E1WRF4M>
<E1KNVKM SEGMENT="1">
<MSGFN>Str</MSGFN>
<PARNR>String</PARNR>
<NAMEV>String</NAMEV>
<NAME1>String</NAME1>
<ABTPA>String</ABTPA>
<ABTNR>Stri</ABTNR>
<UEPAR>String</UEPAR>
<TELF1>String</TELF1>
<ANRED>String</ANRED>
<PAFKT>St</PAFKT>
<PARVO>S</PARVO>
<PAVIP>S</PAVIP>
<PARGE>S</PARGE>
<PARLA>S</PARLA>
<GBDAT>String</GBDAT>
<VRTNR>String</VRTNR>
<BRYTH>Stri</BRYTH>
<AKVER>St</AKVER>
<NMAIL>S</NMAIL>
<PARAU>String</PARAU>
<PARH1>St</PARH1>
<PARH2>St</PARH2>
<PARH3>St</PARH3>
<PARH4>St</PARH4>
<PARH5>St</PARH5>
<MOAB1>String</MOAB1>
<MOBI1>String</MOBI1>
<MOAB2>String</MOAB2>
<MOBI2>String</MOBI2>
<DIAB1>String</DIAB1>
<DIBI1>String</DIBI1>
<DIAB2>String</DIAB2>
<DIBI2>String</DIBI2>
<MIAB1>String</MIAB1>
<MIBI1>String</MIBI1>
<MIAB2>String</MIAB2>
<MIBI2>String</MIBI2>
<DOAB1>String</DOAB1>
<DOBI1>String</DOBI1>
<DOAB2>String</DOAB2>
<DOBI2>String</DOBI2>
<FRAB1>String</FRAB1>
<FRBI1>String</FRBI1>
<FRAB2>String</FRAB2>
<FRBI2>String</FRBI2>
<SAAB1>String</SAAB1>
<SABI1>String</SABI1>
<SAAB2>String</SAAB2>
<SABI2>String</SABI2>
<SOAB1>String</SOAB1>
<SOBI1>String</SOBI1>
<SOAB2>String</SOAB2>
<SOBI2>String</SOBI2>
<PAKN1>Str</PAKN1>
<PAKN2>Str</PAKN2>
<PAKN3>Str</PAKN3>
<PAKN4>Str</PAKN4>
<PAKN5>Str</PAKN5>
<SORTL>String</SORTL>
<FAMST>S</FAMST>
<SPNAM>String</SPNAM>
<TITEL_AP>String</TITEL_AP>
<E1ADR3MAS SEGMENT="1">
<OBJ_TYPE_P>String</OBJ_TYPE_P>
<OBJ_ID_P>String</OBJ_ID_P>
<OBJ_TYPE_C>String</OBJ_TYPE_C>
<OBJ_ID_C>String</OBJ_ID_C>
<OBJ_ID_EXT>String</OBJ_ID_EXT>
<CONTEXT>Stri</CONTEXT>
<E1BPAD3VL SEGMENT="1">
<ADDR_VERS>S</ADDR_VERS>
<FROM_DATE>String</FROM_DATE>
<TO_DATE>String</TO_DATE>
<TITLE_P>Stri</TITLE_P>
<FIRSTNAME>String</FIRSTNAME>
<LASTNAME>String</LASTNAME>
<BIRTH_NAME>String</BIRTH_NAME>
<MIDDLENAME>String</MIDDLENAME>
<SECONDNAME>String</SECONDNAME>
<FULLNAME>String</FULLNAME>
<FULLNAME_X>S</FULLNAME_X>
<TITLE_ACA1>Stri</TITLE_ACA1>
<TITLE_ACA2>Stri</TITLE_ACA2>
<PREFIX1>Stri</PREFIX1>
<PREFIX2>Stri</PREFIX2>
<TITLE_SPPL>Stri</TITLE_SPPL>
<NICKNAME>String</NICKNAME>
<INITIALS>String</INITIALS>
<NAMEFORMAT>St</NAMEFORMAT>
<NAMCOUNTRY>Str</NAMCOUNTRY>
<NAMCTRYISO>St</NAMCTRYISO>
<PROFESSION>String</PROFESSION>
<***>S</***>
<LANGU_P>S</LANGU_P>
<LANGUP_ISO>St</LANGUP_ISO>
<SORT1_P>String</SORT1_P>
<SORT2_P>String</SORT2_P>
<LANGU_CR_P>S</LANGU_CR_P>
<LANGUCPISO>St</LANGUCPISO>
<DEPARTMENT>String</DEPARTMENT>
<FUNCTION>String</FUNCTION>
<BUILDING_P>String</BUILDING_P>
<FLOOR_P>String</FLOOR_P>
<ROOM_NO_P>String</ROOM_NO_P>
<INITS_SIG>String</INITS_SIG>
<INHOUSE_ML>String</INHOUSE_ML>
<COMM_TYPE>Str</COMM_TYPE>
<PERS_GROUP>Stri</PERS_GROUP>
</E1BPAD3VL>
<E1BPADTEL3 SEGMENT="1">
<COUNTRY>Str</COUNTRY>
<COUNTRYISO>St</COUNTRYISO>
<STD_NO>S</STD_NO>
<TELEPHONE>String</TELEPHONE>
<EXTENSION>String</EXTENSION>
-
Hi All,
My team is trying to populate the customer data from MDM, back to R3.
In MDM syndicator mapping we mapped the fields with DEBMDM06. We are not able to use DEBMAS because the address details segmet E1ADRMAS is not present in DEBMAS. so we are using the DEBMDM which is a combination of both DEBMAS and ADRMAS.
I learned in the forums, that DEBMDM needs to be spilt into DEBMAS and ADRMAS in XI, and ADRMAS is going to process first and then DEBMAS. So can any one write me how would we will do the spilting in XI.
Can we have to use the BPM (Bussiness Process Management) technology for this. or there is any other way for spilting.
Your help will be appriciated.
Best Regards
SyamHi Syam,
there is some SAP delivered XI content that is doing the splitting on XI. In fact there are XSLTs doing the copy job (means extracting the address relevant data into ADRMAS and the customer data into DEBMAS) and additionally you've to configure the Interface Determination on XI in a way that it distributes ADRMAS and DEBMAS from your incomming DEBMDM.
Additional you can use BPM to ensure the correct order of the IDoc. But this is not a must.
BR Michael -
IDoc Inbound Processing for CREMDM & DEBMDM
Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh -
Dear Experts,
I have to do a sceario for R/3-XI-MDM for material idoc.Can we use MATMDM for material as we use CREMDM and DEBMDM for Vendor and Customer IDOC respectively. Wherever i searched, i found people using only MATMAS for Material.
If MATMDM can be used , then please provide with the useful links if you can.
Thanks,
Shweta.Hi,
Go throguh the weblog may be u get the idea.
XI Configuration for MDM Integration - Sample Scenario
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
R/3-XI-MDM (Outbound Scenario)
/people/balas.gorla/blog/2007/02/05/r3-xi-mdm-outbound-scenario
MDM-XI-R/3 Integration
/people/balas.gorla/blog/2006/09/27/mdm-xi-r3-integration
Testing and Monitoring an Interface Between MDM & XI
/people/harrison.holland5/blog/2007/01/22/testing-and-monitoring-an-interface-between-mdm-xi
MDM 5.5 data distribution using SAP XI
/people/sriram.vasudevan3/blog/2005/09/01/mdm-55-data-distribution-using-sap-xi
Advanced XI Mapping useful with MDM
/people/sap.user72/blog/2005/10/12/advanced-xi-mapping-useful-with-mdm
Re: whether i would write user-defined function convert euro into rupee or USD
Thanks,
Satya Kumar
Reward if it is usefull -
Hi Sap Gurus,
I am trying to integrate MDM,XI,R/3 as per the configuration guide for mdm5.5 sp02.But my problem is that in the document it is said that in transaction bd 64 specify the sender as R/3 System and Receiver as XI system but the message type as debmdm(customer) and cremdm(vendor) but i feel it should be debmas and cremas instead just because when i try to creeate idoc for customer by tansaction bd12 i get message type in the transaction as debmas.And when i try to release it i get 0 communication idocs created.Kindly let me know what has to be done.Tell me if at all i am missing any technical aspect.Hi Gurus,
I have a few questions regarding my XI and MDM installation ....
1: Can we have XI and MDM installtion done on the same box using same
hostname.??
2. Can you please let me know as to what should be the minimum or a good
server configuration for a MDM Installation.
3.Also if someone can please provide the configuration steps for a
successful MDM installation or can provide a helpful link where i can
find the confiuration steps.
4. Any realtime e.g of XI interfacing with MDM.
I hope i get to hear from the gurus very soon .
Thanks,
Sanjay. -
Hi,
We have an idoc DEBMDM coming out from MDM to R3. XI would map it to 2 idoc types in R3. First one by default is DEBMAS and for only specific values on field E2KNA1M-KUKLA, the second idoc CREMAS has to be created.
I have created separate message mapping for both these idocs. Should i create separate Interface mapping as well ? How can i mark my condition(for CREMAS) on the directory ? Is there other better way?
Thanks,
Ram.Hi,
This is Single XI Interface Scenario right ? In that in place, you get one message and need to send two idocs out of that ? if so ,it is normal message split.
Need to create one message mapping with the concept of 1:N Mapping [ Target structure will contain 2 structures here]
Then create One Interface Mappping i.e 1:N
Use this Interface mapping in the BPM with the help of Transformation Step so that you can send 2 idocs out of one message at the same time from XI.
Hope this helps, Rgds, Moorthy -
Is MDM a separate server or part of ECC
Hey guys
i have a small question regarding MDM,is it a separate module like SD,MM,FI and is part of R/3 or is it a stand alone server by itself like CRM,BI,XI etc?
also if i have a mainframe system which is sending a flat File and i need to integrate this with MDM using XI,which IDOC's i can use?
basically we have Customer data and sale data which we want to load onto MDM.
a list of available IDOC's on MDM will be awesome.
thanx
SaifHi .
For Customer Data , you can use DEBMDM or DEBMAS . However will recommend DEBMDM using MDM_CLNT_EXTR .
I am not sure abt sale ! which data it is ?
Hope this helps ,
- An -
Reduced matmas message type data transfer to mdm
Hello ,
I have scenario where I have reduced matmas message type (Zervicematmas) and it is linked to matmas05.I want to transfer this data using mdm_clnt_extr.
Uptill now my understanding is that mdm_clnt_extr can transfer data for standarad
message type as(DEBMDM,MATMAS).
if yes , pl suggest what config has to be done on ECC6.0.
thanks in advance,
SharadaThanks for the help,
As per your suggestion one can select sengment to be transfered at the time of creating a variant of Extraction.
My scenario is that I have to create a custome message type ZSERVICEMATMAS for transferring data to MDM and standard MATMAS will be used to trnasfer data to other third party system.
Now here MDM_CLNT_EXTR is able to give me idoc wrt MATMAS message type and MATMAS05 idoc type.
I want MDM_CLNT_EXTR should create idoc for ZSERVICEMATMAS meesage type and MATMAS05 is idoc type.
I have checked for exits is MATERIAL_extract FM where I can give this message type, but didnt got any clue.
Pl can you suggest on this.
thanks,
Sharada -
Error while opening MDM Data Manager
Hi,
We are getting the following error while trying to open Data manager on our repository.
"Error Initializing Attributes for table Taxonomy
Application will exit
Already exists"
mds Version 5.5.42.90
MDM DataManager Ver5.5.42.90
The repository loads without any errors. The server log file too doesnt show any errors.
Is there anyway to fix this?Go to your MDM console, Login to repository and Unload repository first.
Then load with Update Indices.
This problem comes when you change anything in schema in console and then load repository with immediate option.
So always prefer to use update indices as accelator files will get updated and data comes from actual database.
If the problem still persists then Go again to console and check your repository for any fatal error. if errors come then repair repository and if not come then also repair.
Then load with update indices.
Hope it will help you.
BR,
Alok
Edited by: Alok Sharma on Feb 14, 2008 9:20 AM -
What are the corresponding Data Types of some MDM Data Types
Hi Guys,
The MDM ABAP API involves creation of a DDIC structure in SRM. This structure should have the same fields with the MDM table fields. We would like to ask the corresponding ABAP Data Types for the following MDM Data Types.
MDM SRM
1. Look up (flat)
2. Look up (taxonomy)
3. Look up (heirarchy)
4. Look up (qualified flat look up)
Any significant inputs on this?
Thanks and regards,
REHi,
Refer the below link. This is from the MDM Reference guide and contains the sample source code as well for almost all the things like creating repository, creating tables and fields etc. It would be helpful to you.
http://help.sap.com/saphelp_mdm550/helpdata/en/47/5fd3f7cbd75518e10000000a421138/frameset.htm
Regards,
Jitesh Talreja
Maybe you are looking for
-
Transformation Issue for 2LIS_03_BF
Dear All. I am facing very strange issue for 0IC_C03 with the transformation of 2LiS_03_BF the cube was first got loaded from our Sandbox and every thing was fine, latter we connect BW development with R/3 development. i have transfer all the data so
-
I have a mac book air. Have had no issues with any virus before but today my safari page keeps directing me to a page which says " cyber crime" posing to be by Cheshire Police AUthority uk metropolitan police.Tells me that I have 24 hours to pay a 10
-
How do i convert a plain number into hh:mm:ss
Below is a part of my spreadsheet i am setting up for travelling. The driving time number is derived from a "IF" calculation that divides the "Distance" by a number depending upon the selection in the "Road" column (Data validation list) The calculat
-
How do you get the Touch to not shuffle a playlist?
I created a playlist for a class I teach, in a specific order. When I go to play it, it shuffles the playlist even though I did not hit the shuffle button. What am I missing? The shuffle is there to "shuffle" if I ask it to, so why is it doing it whe
-
Restore failed - iTunes: Restore error 40
When I run the restore by iTunes of the iPhone 3G I get the following error (Error 40): I-tunes generates the following log: 2012-05-21 11:21:55.834 [6656:1038]: restore library built Feb 6 2012 at 17:46:17 2012-05-21 11:21:55.834 [6656:1038]: iTune