Creating Ports in MDM

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,
Anita

Hi 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>

Similar Messages

Unable to select the created Ports(greyed out) in the import manager

Hi ,
We have created some ports with specific Remote system and XML schema's and also assigned the map to it.
The processing type is manual for now,since we want to load data manually using import manager from the Ready folder of the port since PI is dropping the files there.But when I load import manager and select the file type as "Port" and also the relevant remote system ,I cannot select any of the list of ports created ,All are greyed out.
All I need is to select "Port" option ,remote system and use the created port from the dropdown list of import manager " connect to source" step,which i am unable to select as all the port s are greyed out and unable to select.
Any help greatly appreciated...

Hello Arvind,
There is no need to start the MDIS (Import server) if you are importing the data manually.you just open the import manager, login into the repository and select type as XML as per your case and select the remote system (it depends on your requirement) and select the port on which your xml files resides.and enter in the import manager then map you data accordingly and you can import into the repository.
when you want to automate the process for importing the data in repository then you will need to Start the import Server. In that case import server automatically pick the file from the ready port folder and also set the property in console as the processing type is Automatic.
Hope this will help you and clear your doubt.
TNR,
Saurabh...
Reward if found helpful.

Error occurs while the user creates an vendor(MDM)

Hi,
The following error occurs when the user creates an vendor(MDM) and submits the form for validation on Enterprise portal.
" Could not create JCOClientConnection for logical System: MDM_WD_MODELDATA_DEST - Model: class com.xxxx.ven.crt.MDMBAPIValidateModel. Please assure that you have configured the RFC connections and/or logical system name properly for this model"
Can any one help me out how to rectify this error?
Regards,
KN

Hello,
test MDM_WD_MODELDATA_DEST with webdynpro content admin rights . check sso or uid/pw given and system details as error message showing that JCO Destination configuration is wrong.
Regards,
Koti Reddy

Create port channel between UCS-FI and MDS 9124 (F Mode)

Dear Team,
We were trying to create port channel between UCS FI and MDS 9124
But the port channel not getting active in F mode on MDS 9124
FI is in FC End Host Mode
We have enabled FC uplink trunking on FI
We have enabled NPIV on MDS
We have enabled trunk on MDS
FI and MDS in default VSAN
To check we changed the FI mode to FC Switching mode and port channels became active but in E mode
when we enabled FC uplink trunking on FI and FC Switching mode port channels became active in TE mode
but in both the above cases showflogi database shows WWPN of SAN alone not showing any from FI.
How to achive this?
Have read that no need to change the swicthing mode to FC Switching mode and keep as FC Endhost mode
SO how to achieve Port channel with F mode in MDS and FI ( Mode showing as NProxy)
Does it has to do anything with MDS NX-OS version? (https://supportforums.cisco.com/thread/2179129)
If yes how to upgrade as license for ports came along with Device and we do not have any PAC/PAK or license file as it came
with license
Also we have seen 2 files availabe for download (m9100-s2ek9-kickstart-mz.5.2.8b.bin and m9100-s2ek9-mz.5.2.8b.bin) which to use
Thanks and Regards
Jose

Hi Jo Bo,
what version of software if your MDS running?
On your UCS do connect nxos and show inteface brieft and look at the mac address.
it is possible that you might be hitting the bug below. if this is the case you might need to upgrade the firmware on your MDS.
Add MAC OUI "002a6a", "8c604f", "00defb" for 5k/UCS-FI
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCty04686
Symptom:
Nexus switch unable to connect any other Nexus or other Cisco Switch in NPV mode with a F port-channel. Issue might be seen in earlier 5.1 releases like
5.1.3.N1.1a
but not the latest
5.1.3.N2.1c
release. Issue is also seen in
5.2(1)N1(1)
and
6.0(2)N1(1)
and later releases.
Conditions:
Nexus configured for SAN PortChannels or NPIV trunking mode Nexus connected to UCS via regular F port channel where UCS in NPV mode NPV edge switch: Port WWN OUI from UCS FI or other Cisco manufactured switch: xx:xx:00:2a:6a:xx:xx:xx OR xx:xx:8c:60:4f:xx:xx:xx
Workaround:
Turn-off trunking mode on Nexus 5k TF-port Issue does not happen with standard F-PORT Remove SAN Portchannel config
Further Problem Description:
To verify the issue please collect show flogi internal event-history errors Each time the port is attempted OLS, NOS, LRR counters will increment. This can be determined via the following output, show port internal info all show port internal event-history errors

RSA1 automatically creating port definitions

When setting up BW connection to ECC and SCM systems, RSA1 auto creates port definitions using the generated A000000X format. I want to use a predinfed port like BIQ100 or BIP100 (source client format).
Is there a way to use predinfed versus generated port defintion.
Thanks
Jexun

Go to transaction WE20 and maintain the port in the outbound parameter in the correct logical system under partner type LS.

Creating Port,RFC desitination in R3 for XI

Can somebody send a link for creating Port/RFC destination in R3 system WITH SCREENSHOTS.. I need step-by-step process.. pls
Thanks-GS

Hi Gopal,
To create RFC destination in R/3 TCODE is SM59.
Go to SM59->R/3 Connections->Create new->Give RFC destination name,type is 3 in this case,then give target host as the host name of ur R/3 system to which u want to connect then give system no.(most of the time it is 00) then select as a host name or ip address then go to logon security tab give language,client of ur target system and enter username and password which should be used to logon in target system.Then save this connection click on test Connection if it is successful click on remote Logon.
To create ports TCODE is WE21->Transactional RFC->create new
Then give port name then select RFC destination( the one u created in previous step).
Thanks.

Shopping cart created for a MDM material uploaded from MARA

Hello,
I need to create an interfase from ECC6 material master (MARA) to MDM1.0
I can not test the creation of a shopping cart for a catalogue material at the moment.
My question is.
Someone know can confirm me if is possible
. to upload to MDM the "MARA" table
. and the SRM shopping cart will be created for a catalogue material (uploaded from MARA, ECC6.0.
AND the purchase requisition created in the back-end (ECC6) will take the MARA material number not a free text.
I think that this is possible, but what do I have to define in MDM? How MDM will reconize the material number to transfer that information from the shopping cart to the purchase requisition?
Thank for your help.
Cheers,
Marta
Message was edited by:
Marta Canabal Mazorra

Hi Marta,
Check for details under "Loading Master Data"
http://help.sap.com/saphelp_mdmgds55/helpdata/en/ae/82b24265e8b211e10000000a155106/frameset.htm
Regards
Rehman

I am not able to create repository in MDM 7.1

Hi SDNers,
I am not able to connect to database from my Comsole.
When I tried to unarchieve or create a new repository it will ask Database name, User id and password then only I can enter repository name. When I enter Database name, user id and Password I am getting an error like "Unable to connect to Database Server".
Already I checked these from my end.
1) I checked Database is up or not. Database is up and Running.
2) I tried to logon into database with the user id I am trying in Console. At Database level I am able to login. But when I tried in Console to connect to database I am not able to connect to Database server from concole.
3) I tried changing the password at mds.ini file and restarted the MDM Server also. But still error remain same.
Can anyone help me out why I am getitng that error "Unable to connect to Database Server". I need to add any parameters in mds.ini file. or I am missing any connections parameters
Thanks
Kiran
Edited by: Kiran on Mar 1, 2011 9:29 AM

Hi SDNers,
I tried all above options.
And I raised to SAP. They told like you are in Old Version update to latest Patch MDM 7.1 SP06.
But I dont think If I update Patches to MDM 7.1 SP06 it will solve this problem. But I trying to do that.
Mean while If I see logs at Server level I am able this this error.
Error Message "SQL_ERROR SQLSTATE= 08001, ErrorCode= -1013, Msg=[IBM][CLI Driver] SQL1013N The database alias name or database name "M7P" could not be found. SQLSTATE=42705 GetDiagRec/Connect: 08001(0), ErrorCode= -1013,"
Can you please suggest as I am missing any parameters in MDS.ini file or MDS_List.ini files or any entries at Database level files. Or after Installing Database I need to set any parameter at Database level or MDM level . Just I am wondering where I missed???
Any Help!!!
Thanks
Kiran

Unable to receive Queue Message Unable to create Queue in MDM 2.0.1

Hi All,
I am getting below exception when i am trying to read JMSQueue from weblogic server to MDM 2.0.1
Steps i configured as below:
Created XAI JNDI server : XAI JNDI Server(Demo), Provider URL(http://localhost:7001), Initial Connection Factory(weblogic.jndi.WLInitialContextFactory)
created XAI JMS Connection:XAI JMS Connection(DemoConn), XAI JNDI Server(Demo), JNDI Connection Factory(weblogic.jms.XAConnectionFactory)
created XAI JMS Queue: XAI Queue Name(DemoQueue), Queue Name(TestQueue), XAI JNDI Server(Demo)
created XAI Receiver DemoRx mapped with XAI Class JMSRCVR and with above configurations
MPL is creating intial context factory for jndi server properly and intializing queues properly.
But getting namenotfound exception at Receiver DemoRx
[Thu May 26 15:01:46 IST 2011] Receiver DemoRx - Read interval is 10 seconds.
[Thu May 26 15:01:47 IST 2011] Receiver "DemoRx" initialization failed:Unable to receive Queue MessageUnable to create Queue: javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '']; remaining name 'TestQueue'
com.splwg.mpl.receiving.ReceiverInitException: Unable to receive Queue MessageUnable to create Queue: javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '']; remaining name 'TestQueue'
     at com.splwg.mpl.jms.queue.JMSReceiver.prepareConnection(JMSReceiver.java:394)
     at com.splwg.mpl.jms.queue.JMSReceiver.init(JMSReceiver.java:266)
     at com.splwg.mpl.receiving.AsyncReceiverManager$1.call(AsyncReceiverManager.java:232)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Please help me in this regard
Thanks in advance,
sukumar

Hi Suraj,
I would prefer to discuss the problems in the forum. There are maybe other that have the same problem and they could then participate from the discussion.
No back to your problem:
As fare as I know there is no build in function to read directly from file system.
MPL is no longer supported in this product and this was the only module for reading the file system.
You have to develop an application to fetch the files form the file system or you must use an Enterprise Service Bus
like OSB or ServiceMix.
To enable the system for the IMD import you have to publish a Business Object or Script via XAI Inbound service.
The recommended way is to use the D1-IMDSeeder BO.
There is a chapter in the MDM Configuration Guide, explaining how to setup the XAI Inbound service.
There is also a service script available. The advantage of the service script is, that you can import IMDs for more than on device (D1-IMDEvtUpl and DM-IMDEvtUpl). The DM-IMDEvtUpl is eventually only in the demo database available.
The disadvantage of the IMDSeeder is, that you have to setup a lot of configurations in the system. There is another thread in the forum explaining the setup.
My preferred way is to use the D1-InitialLoadIMDScalar or D1-InitialLoadIMDInterval BO but you have to do a lot of things by your own.
/Markus

Generic error while using create operation on MDM WebService

Hello
I´m trying to create a record on MDM using a standard MDM WebService operation createProducts
When I create a record with everything blank (but not the repository info), it creates perfectly:
 <urn:createProducts>
 <urn:products>
 <urn1:ProductsCreate></urn1:ProductsCreate>
 </urn:products>
 <urn:reposInfo>
 <urn2:dataLang>English </urn2:dataLang>
 <urn2:repositoryName>MY_REPOSITORY</urn2:repositoryName>
 <urn2:serverName>mdmserver</urn2:serverName>
 </urn:reposInfo>
 </urn:createProducts>
However, when I try to add the following code, it doesn´t work:
 <urn:createProducts>
 <urn:products>
 <urn1:ProductsCreate>
 <urn1:eClassClassification>
 <urn1:displayValue>PDM TEST</urn1:displayValue>
 <urn1:attributes>
 <urn1:attribute>
 <urn1:name>TEST1 TEST123</urn1:name>
 </urn1:attribute>
 <urn1:attributeValue>
 <urn1:value>
 <urn1:value>220,00 MM</urn1:value>
 </urn1:value>
 </urn1:attributeValue>
 </urn1:attributes>
 </urn1:eClassClassification>
 </urn1:ProductsCreate>
 </urn:products>
 <urn:reposInfo>
 <urn2:dataLang>English </urn2:dataLang>
 <urn2:repositoryName>MY_REPOSITORY</urn2:repositoryName>
 <urn2:serverName>mdmserver</urn2:serverName>
 </urn:reposInfo>
 </urn:createProducts>
I get the return:
 <rpl:createProductsResponse xmlns:rpl="urn:MDMMateriaisVi">
 <rpl:Response xmlns:pns="urn:com.sap.mdm.ws.beans">
 <pns:ExecutionStatus>
 <pns:status>Fault</pns:status>
 <pns:description>Record creation unsuccessful, see the faults list</pns:description>
 <pns:fault>
 <pns:severity>Error</pns:severity>
 <pns:id>repository_3001</pns:id>
 <pns:text>Error executing Records Creation on repository MY_REPOSITORY, error code -5627883, caused by Server error (0xffaa2015)</pns:text>
 </pns:fault>
 </pns:ExecutionStatus>
 </rpl:Response>
 </rpl:createProductsResponse>
All atributes exists on MDM but I still get the error.
Any ideas ?
Thanks

Hello,
did you got the solution to this issue, as we are also getting the same error,

Create users in MDM console

HI,
I want to create some hundreds of users in console.Hence i dont want to create it manually.
Is there any procedure to load the users into console list.
Thanks
Sree

Hi Sreenath,
There are couple of ways to accomplish this .
1) If you have IDM then you can push all the user ID's into the MDM system .
2) if you have direct DB access you can run some queries import the user roles and mapping directly .
Regards, Vag Vignesh Shenoy

Creating Hierarchy in MDM

My source file is in the format -
Parent Child
Valve Belt
Belt Conveyor
The expected hierarchy in MDM is -
Valve
 |_______Belt
 |________Conveyor
How do we create this hierarchy from the flat source file?

Hi Tejas,
The Taxonomy table is created in Console, however, creation of hierarchy within the Taxonomy is done through Import Manager. There is no need to create/select two columns in Console.
You might be having a soure file containing the hiearachy and a destination Taxonomy in table in MDM with atleast one filed. (Created by default)
Follow following steps:
1. Open Import Manager by specifying the location of Source File. Your cource file should be a updatable data source (e.g. XML, Excel file is not a updatable souce - for more info on this see the Data Manager Reference Documentation).
2. Select appropriate Source and Deatination from drop down box.
3. In Source Hierarchy, Select both the columns(parent and child) > right click > select 'Create Hierarchy filed' and select the parent and child fields.
4. Click on create. This will generate 2 new fields in the Field Mapping Source Fields containing the Hierarchy.
5. Map the Source to Destination and complete other usual steps.
Hope this helps. If you have any further difficulties, give the details of source file format.
Regards,
Anoop
PS: Do give point if found helpful.

I have plex app on my mac computer and on my i pad while on the apple air port i am able to use the plex app on my i pad when i get on 3 g i am not able to connect to my plex app on my mac to use the remote app i have tried to creat port fowarding on the

i am trying to use my plex app while on 3G i have tried to set up port forwarding on my airport router and cant see to get the app to work i also have a myplex account. how can i get it to work. i followed the direction on the apple port forwardering but still no positive results. i can use the app while at home.
thank

If you don't get any answers here, I'd suggest you post over at the Plex forum.

While creating connection to MDM repository using MDM JAVA API

I am getting the following error message:
Unexpected field type 28
I am able to debug that this error message is being displayed after executing the following line of code:
/** Get the Repository schema */
GetRepositorySchemaCommand repositroySchemaCommand =
new GetRepositorySchemaCommand(simpleConnection);
repositroySchemaCommand.setSession(repositorySession);
repositroySchemaCommand.execute();
Now can anyone please explain how to resolve this error?
Thanks in Advance.
Rajat

public void getRepositoryConnection(
          java.lang.String hostName,
          java.lang.String repositoryName,
          java.lang.String userId,
          java.lang.String passWord) {
          //@@begin getRepositoryConnection()
          try {
               if (simpleConnection == null) {
                    simpleConnection =
                         SimpleConnectionFactory.getInstance(hostName);
                    // Establish TCP Connection to the server
                    if (simpleConnection != null) {
                         //                              wdComponentAPI.getMessageManager().reportSuccess("Got Connected");
                         /** Establish a repository session with the respository */
                         //Set the region properties
                         RegionProperties dataRegion = new RegionProperties();
                         /** Set region code for the session */
                         dataRegion.setRegionCode("engUSA");
                         /** Set the locale on data region */
                         dataRegion.setLocale(new Locale("en", "US"));
                         /** Set the name of data region */
                         dataRegion.setName("US");
                         // Createa repository identifier
                         RepositoryIdentifier repositoryID =
                              new RepositoryIdentifier(
                                   repositoryName,
                                   hostName,
                                   DBMSType.MS_SQL);
                         /** Create the User Session */
                         CreateUserSessionCommand createUserSessionCommand =
                              new CreateUserSessionCommand(simpleConnection);
                         /** Set the repository identifier (mandatory)*/
                         createUserSessionCommand.setRepositoryIdentifier(
                              repositoryID);
                         /** Set the region properties for the session (mandatory) */
                         createUserSessionCommand.setDataRegion(dataRegion);
                         createUserSessionCommand.execute();
                         /** Get the session identifier */
                         this.userSession =
                              createUserSessionCommand.getUserSession();
                         AuthenticateUserSessionCommand authenticateUserSessionCommand =
                              new AuthenticateUserSessionCommand(simpleConnection);
                         /** Set session identifier (mandatory)*/
                         authenticateUserSessionCommand.setSession(userSession);
                         /** Set id of repository user(mandatory) */
                         authenticateUserSessionCommand.setUserName(userId);
                         /** Set password (mandatory)*/
                         authenticateUserSessionCommand.setUserPassword(passWord);
                         /** Establish the session */
                         authenticateUserSessionCommand.execute();
                         SetUnicodeNormalizationCommand unicodeNormalizationCommand =
                              new SetUnicodeNormalizationCommand(simpleConnection);
                         unicodeNormalizationCommand.setSession(userSession);
                         unicodeNormalizationCommand.setNormalizationType(
                              SetUnicodeNormalizationCommand.NORMALIZATION_COMPOSED);
                         unicodeNormalizationCommand.execute();
                         CreateRepositorySessionCommand repositorySessionCommand =
                              new CreateRepositorySessionCommand(simpleConnection);
                         /** Set the repository identifier */
                         repositorySessionCommand.setRepositoryIdentifier(
                              repositoryID);
                         /** Obtain repository session */
                         repositorySessionCommand.execute();
                         /** Store the session id into the variable repositorySession */
                         this.repositorySession =
                              repositorySessionCommand.getRepositorySession();
                         /** Authenticate the users session */
                         AuthenticateRepositorySessionCommand authenticatedRepositorySession =
                              new AuthenticateRepositorySessionCommand(simpleConnection);
                         /** set the session id */
                         authenticatedRepositorySession.setSession(
                              repositorySession);
                         /** set id of the repository user */
                         authenticatedRepositorySession.setUserName(userId);
                         /** set password */
                         authenticatedRepositorySession.setUserPassword(passWord);
                         authenticatedRepositorySession.execute();
                         /** Get the Repository schema */
                         GetRepositorySchemaCommand repositroySchemaCommand =
                              new GetRepositorySchemaCommand(simpleConnection);
                         repositroySchemaCommand.setSession(repositorySession);
                         repositroySchemaCommand.execute();
                         this.schema = repositroySchemaCommand.getRepositorySchema();
          } catch (Exception e) {
               wdComponentAPI.getMessageManager().reportException(
                    e.getMessage(),
                    true);
          //@@end

MDM Syndication - IDOC mapping ?

Hi Gurus,
I was going thru the following blog.
MDM Syndication
/people/harrison.holland5/blog/2006/11/27/mdm-syndication
What is the purpose of remote system(ECC) in MDM ? Is it required to get IDOC structure from ECC into MDM repository ?
If so, what are the pre requisites/configurations required for connection to ECC from MDM. Is it enough to mention technical/Logical name of ECC server (as in SLD) for creating remote system in MDM ?
Appreciate your help

Ports(Outbound) is for automating the Syndication.
You create Ports in MDM Console.
You do NOT have to import the IDoc structure into MDM.
MDM is not like Integration Repository of XI. You do not have to import the Idoc structure at all.
SAP provides business content (out of the box) for the XI - MDM mapping.
File Adapter of XI(Inbound to XI) picks up the created xml file.
In the outbound side of XI, Idoc Adapters are used.
In the port definition of MDM, you specify the map to be used to syndicate the data.
SAP delivers the map and XSD for predefined Repository like Material, Customer, Vendor, Business Partner etc..

Creating Ports in MDM

Similar Messages

Maybe you are looking for