IDOC ADAPTER , ATTRIBUTE_IDOC_METADATA Error

Hi everyone!
XI have sent Idoc to SAP A5P.
But there is an error log,
"IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA
> Metadata EDISDEF for port SAPA5P, IDoc type ORDERS02 and CIM type ZORDERS2 not maintained
Kindly advise what is wrong with our configurations.
Thank you very much!
Fred

hi,
Your error is IDOC metadata related
(probably incorrect entry in IDX1 - or RFC to R3 is ont working)
download your idoc in IDX2 to check it
Also check if you are using the right port in IDX1.
else,
Goto ID and open the relevant Business system.
Goto --->Menu tab "Service" --->Adapter Specific Identifiers.
Check if the proper logical system details have provided.
Refer
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
SAP Network Blog: Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thanks
Swarup

Similar Messages

  • IDoc Adapter and Error Management

    Hi Experts,
    I don't understand tha management of business logic error.
    My External System communicate with SAP ERP via SAP PI IDOC Adapter (HTTP protocol, asynchronous mode).
    SAP ERP sends an IDOC via PI to my system, my system receives IDoc, an error occurs during business operation in my system.
    What should I do?
    In my scenario there are not message of error or IDOC to communicate a problem.
    Thanks,
    Marco Genova
    Edited by: m.genova on May 21, 2009 6:41 PM

    Hi,
    For the same wrong rfc destination i've got
    in sxmb_moni : <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
    <SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with ARS Name or password is incorrect. Please re-enter FM NLS_GET_LANGU_CP_TAB</SAP:P1>
    OR
    in sm58 : XIAFUSER     IDOC_INBOUND_ASYNCHRONOUS     ARS           17.02.2006 15:57:33 Name or password is incorrect. Please re-enter
    It's so strange ?
    Regards,
    Vincent

  • Reciever idoc adapter Determination error

    Hi,
    I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
    I am getting Reciever determination error.I have done all the steps according to the below weblog.
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
    Below is error description.
    <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Plz help me out if any one has some idea abt it.
    Thanx
    Rekha

    Hi Rekha,
    The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
    The most common reason for this error is:
    1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
    2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
    Hope this helps.
    Regards
    Suraj

  • IDoc Adapter throws error

    We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
    the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
    All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
    But we are getting the following error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
      <SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
      <SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>S70_812</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
      </SAP:Sender>
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    We are not sure where from this synchronous is being picked?
    Please advise.
    Thanks,
    Bhaskar and Anil

    In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

  • XI Business content for MDM - Syntax error in IDOC adapter

    Hi mates,
    I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
    <i><SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
      <SAP:Retry>M</SAP:Retry></i>
    Generated ADRMAS IDOC is
    <i>  <?xml version="1.0" encoding="utf 8" ?>
      <ADRMAS02>
      <IDOC BEGIN="1">
      <EDI_DC40 SEGMENT="1" />
      <E1ADRMAS>
      <OBJ_TYPE>LFA1</OBJ_TYPE>
      <OBJ_ID>0000500140</OBJ_ID>
      <CONTEXT>0001</CONTEXT>
      <E1BPAD1VL SEGMENT="1">
      <FROM_DATE>00010101</FROM_DATE>
      <TO_DATE>99991231</TO_DATE>
      <NAME>Swift Transportation</NAME>
      <COUNTRY>US</COUNTRY>
      <COUNTRYISO>US</COUNTRYISO>
      <LANGU>E</LANGU>
      <LANGU_ISO>EN</LANGU_ISO>
      <SORT1>SWIFT TRANSPORTATION</SORT1>
      <TIME_ZONE>CST</TIME_ZONE>
      <E1BPAD1VL1 SEGMENT="1">
      <LANGU_CR>E</LANGU_CR>
      <LANGUCRISO>EN</LANGUCRISO>
      <ADDR_GROUP>BP</ADDR_GROUP>
      </E1BPAD1VL1>
      </E1BPAD1VL>
      </E1ADRMAS>
      </IDOC>
      </ADRMAS02></i>
    Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
    Look at the code sample from XSLT mapping program
      <xsl:for-each select="IDOC/*/E1ADRMAS">
           <IDOC BEGIN="1">
           <!-- The header data of each single ADRMAS-IDoc needs to be there but does not require specific data -->
                <EDI_DC40 SEGMENT="1"/>
                <xsl:apply-templates select="."/>
           </IDOC> 
      </xsl:for-each>
    How can an IDOC w/o control record be posted?
    Did anyone come across this error? Whats wrong/missing?
    I appreciate ur inputs.
    thx in adv
    praveen

    Moorthy,
    I tried reloading the IDOC metadata from IDX2. Still I get the same error.
    Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
    Thanks
    Praveen

  • Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

    Scenario:
    EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
    I'm getting an error (below) at the Call Adapter stage:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
    I::000
    and thus the IDOC can't get recreated.
    Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
    Can someone please shed some light?

    Hi,
    Addition to the above
    Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
    it should be only SAPSID..(SID is your system name..)
    HTH
    Rajesh

  • Error in Idoc adapter

    Hi I am trying todo the from file to Idoc. I am getting the payload exactly but i am getting the error pls check the below code
    Thanks
    Gowri
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi All!
    I've encountered the same error as stated above,
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The RFC Destination is SAPA5A.
    We're now on Acceptance box.
    But, as of this moment, A5A was down (due to maintenance activity).
    Is this the reason for this error?
    Because A5A was down, there is no automatic refresh of metadata in Acceptance box ?
    Kindly advise.
    Thank you!
    Fred

  • SP14 Multi-mapping - error in receiver idoc adapter

    Hi,
    I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
    I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
    In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
    It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
    When testing the setup 'real life' the message fails. The error message in the monitor says:
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>InterfaceCollection</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
    If trying to send multiple XML records, i get the following error:
    - <!--  Technical Routing
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
    Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
    It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
    Also the Idoc is also being used as Inbound interface - so no mistakes here either.
    I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
    Best regards,
    Daniel

    Hi Daniel,
    I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
    I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
    <i>CO_TXT_MMF_ENGINETYPE
    Messages in multi message format can be sent to one adapter engine only</i>
    However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
    Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
    the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
    I hope that helped you a little further - if you find out more I'd be happy to learn about it.
    regards,
    Peter

  • Error using IDOC adapter

    Hi All,
    I'am trying to run the following scenario:
    FILE --> XI --> IDOC (r/3).
    Data is read and mapped towards an internal format. Then a mapping from the internal format to MATMAS_BAPI01 is done.
    I disabled EDI_DC40 and did the needed mappings.
    When I execute the scenario I get the following error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I expected that the XI system would automaticly fill in the needed info in EDI_DC40.
    Does anyone has an idea what is going wrong?
    Kind regards
    Message was edited by: Geert Wouters

    hi,
    most probably your idoc message
    has a wrong format
    when you import your new idoc to integration repository
    does it have EDI_DC40 at the beggining?
    BTW
    try without disabling the edi_dc40
    you cna also have a look at my weblog:
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • Basic Idoc Adapter Error - XI 3.0

    Hi,
    I am new to XI so excuse me if this is a basic question.
    The scenario we have is File -> XI -> IDOC
    When the message is processed into the IDOC Adapter I am getting the following error :
    Control record must start with tag EDI_DC40 not E1LFA1M
    Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
    Is there something I need to change in the Idoc Adapter to get this to happen ?
    Kind regards
    colin.

    It is not a basic question, but it seems to be a common problem.
    Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
    Regards
    Stefan

  • REG: Error in IDoc adapter outbound processing

    Hi All,
          I had a couple of doubts regarding these IDoc's.
    1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
    "IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
    Can any one help me to Solve my Problem
    2) How to find out whether the IDoc is of synchronous or Asynchronous mode
        and how to  handle the synchronous type of IDoc's
    Thanks in advance.
    with Regards,
    Kalyan Dannapaneni.

    Hi Kalyan,
    IDOCs are only Aynchronous (EO or EOIO).
    If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
    Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
    Best regards,
    Silvia

  • IDOC Adapter Error

    Hi All,
    My scenario is JDBC to IDOC, where I am fetching data from Database and posting an IDOC in SAP. My ALE Configuration is correct. I have done the following steps:
    In XI:
    1. Created RFC destination to connect to ECC system
    2. Created Port in IDX1
    3. Imported Meta-data in IDX2
    In ECC:
    1. Defined Logical system
    2. Partner Profile settings.
    Still, I am getting the below error, not sure why is this occuring...
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can anyone help me out with what could be the cause of the error.
    Thanks in advance.
    Regards,
    Amit

    Hi Amit,
    check this link
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    OR Check the receiver IDOC setting in my posting on Wiki
    for File to IDOC scenario are u missing something
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    copy and paste complete link in URL or click here
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&         then Part3
    Sachin
    Message was edited by:
            Sachin Dhingra

  • ATTRIBUTE _ WRONG _ INTF error in idoc adapter

    hai
    iam creating file to idoc scenario in that
    iam copying the CREMAS in to XSD file
    and chenge the occurence of name1
    filed.
    and this xsd file iam using at reciving side interface
    my reciver adapter is idoc adapter
    sender adapter is file adapter
    when i configure this
    iam getting this error
    <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>CRMAS_IF</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface CRMAS_IF</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    so pls any body can help me
    what is this error

    hai
    THANKS FOR UR HELP
    NOW IAM GETTING THIS KID OF ERROR
    WHAT IS THIS IAM NOT UNDER SANDING
    During the application mapping com/sap/xi/tf/_cr_mp_03_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformation
    iam trying to vreate multi ple segments at reciver side for one field .at that time iam getting this error
    i changed the occurs of that filed to unbouned .
    is it need to change the idoc structure at r3  system also ?
    can any body help me pls
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_cr_mp_03_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>During the application mapping com/sap/xi/tf/_cr_mp_03_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • Metadata EDISDEF not maintained  - Idoc adapter error

    hi,
    In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
    Any ideas or suggestions.
    Thanks
    Pandari

    One LAST suggestion.  Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS).  Try authorization group 'SS' (without quotes).  So:
    Object: S_TABU_DIS
    Activity: 03
    Auth. Group: SS
    I recall now that a customer recently had this issue and (for them), this helped.
    Jin

  • IDoc adapter inbound channel: Error Fehler beim Le

    Hello,
    I have a BIG problem. I want to use IDOC - XI - IDOC. I have configured the connections. But when I send the Idoc to the XI. it returns a code in the SM58 "IDoc adapter inbound channel: Error Fehler beim Le" The Message comes cut, it doesn't return all the message. In the XI doesn't give me any error, nothing. The IDOC says thta it has been sent correctly (Code 3). How can I trace the IDOC from de sender to the XI?
    I wanted to use the IDOC HRMD_A06 but now i'm trying with SYIDOC to see if it passes.
    Can Someone help me?
    Caller       Function module               Target system Date       Time     Status text
    SRGEN13      IDOC_INBOUND_ASYNCHRONOUS     RHXCLNT013    07.04.2006 10:06:46 IDoc adapter inbound channel: Error Fehler beim Le
    Thank you
    PM

    I want to know if the Connections have to have SNC?
    I have read this in the note http://help.sap.com/saphelp_nw04/helpdata/en/ca/fafaf6dbc8b240b1cf4a88c40379b2/frameset.htm
    Inbound and outbound connections should be secured by Secure Network Communication (SNC).
    Is that correct? maybe that's why it says the that error
    PM

Maybe you are looking for

  • Save generated jsp in specific location

    Hi everyone! I have an editor to write formatted text and then to preview it in a jsp page. I need to save the generated page in a word document. Can you help me on this? How can I save it in a certain location (as jsp or html)? After that, I can tra

  • Font Minor Problem

    I was in Font Book, verified all font and have 35 minor issues, yellow question mark. How do I fix them. It appears all my fonts are in \Library\Fonts \System\Library\Fonts I have no fonts in \User\Name\Fonts but have collections in FontCollection 1.

  • Looking for the most econmical way of tying domain name to mobileme iweb

    Hi all, I currently have a few sites that are hosted on mobileme, and I used the DynDNS services to 1) register a domain name (15$) and 2) create a webhop (CNAME) from the domain to the mobileme site (30$). So that's 45$ per year per site. Is there a

  • Insert Based on the Condition

    Hi, I have a select list which contains a list of items in it like QCR, SUS, NAC i have table which contains columns like this table name = "watchlist" id , project_name, type -- > here type is wht i have included above i need to give a plsql conditi

  • Missing 1 pixel on Export

    I'm doing some HDR. Everything is shot raw (CR2, Canon) and processed in LR5. I sync all settings (WB, Lens Correction, etc.) needed. I export full size jpg (I've tried both exporting jpg and tiff) and everytime I do, the first shot of the series has