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>

Similar Messages

  • 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

  • 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

  • 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

  • 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

  • Connecting of an external system by IDOC adapter

    Hello everybody,
    we want to connect an external (storage) system to XI by IDOC-Adapter.
    In a scenario without XI the R/3 backend triggers the external system by RFC-Call (TCPIP-conncetion) and an program on the external system is called. This program executes an RFC-call on the R/3 to get the IDOC-informations.
    IN the new scenario (with XI) the R/3 Backend sends the IDOC information to XI. The XI routes this to external system. An TCPIP-Connection is needed which calls the program from the external system.
    But how should this work? The program can not (or should not) call the R/3 Backend directly but the XI.
    What has to be done now? Has the program of the external system changed so that it can understand IDOC-structure directly?
    Or do I have to implement a business process scenario to guarantee that the external system reads the IDOC data in XI (similar to "old" scenario?
    Thanks a lot!

    HI everybody,
    thank you very much for your help. Now it es possible to send an IDOC from R/3 Backend and IDOC-Adapter via XI to an external system using the IDOC-Adapter.
    But now the external system wants to send IDOCs back. So the communication is realised by using the IDOC-Adapter again. In this case we do not get the messages in XI. The conncection is ok (we see this in the Gateway), but the system gets an error in IDOC adapter (sys-log):
    <b><b>Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )</b></b>LFS = external system (AS400).
    In the RFC-Trace we find following information:
    <b> **** Tra
    Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )ce file opened at 20060223 111414 W. Europe Stand, SAP-REL 640,0,109 RFC
    ======> Der Funktionsbaustein "EDI_FILL_SYIDOC01_FOR_RFC" ist nicht vorhanden
    ABAP Programm: SAPLIDX1 (Transaction: )
    Called function module: EDI_FILL_SYIDOC01_FOR_RFC
    User: RFC_USER (Client: 910)
    Destination: C01 (handle: 3, , {C322581B-EB47-43E7-87D7-4607C2873828})
    SERVER> RFC Server Session (handle: 1, 95896538, {43FD899F-8993-0202-E100-00000A
    SERVER> Caller host: LHMAS40A.INTRANET.SYS
    SERVER> Caller transaction code:  (Caller Program: SAPCPIC)
    SERVER> Called function module: ARFC_DEST_SHIP</b>
    Can anybody help us?
    Thanks a lot!
    Florian

  • JDBC - No 'action' attribute found in XML document - error

    Hi,
    I'm trying to write to SQL Server form File
    I successfully read from file, but fail to write.
    <b>My XML is :</b>
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:SD_NEZIGA_OUT_MT xmlns:ns0="ssss.co.il:SD:Office_core_Neziga"><statement2 action="INSERT"><table>Employees</table><access><ID>000009</ID><Name>&#1497;&#1493;&#1504;&#1505;&#1497; &#1512;&#1493;&#1514;&#1497;</Name><Phone>972528288840</Phone><Manager>001037</Manager><DistManager>001037</DistManager><Password>D</Password><UserType>0</UserType><miskalID>0000</miskalID></access></statement2></ns0:SD_NEZIGA_OUT_MT>
    <b>Error from JDBC adapter:</b>
    TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
    Help me please.
    Best regards, Natalia.

    Hey
    Ur XML is not correct,it must be something like this
    <root>
    <StatementName1>
    <dbTableName action=”UPDATE” | “UPDATE_INSERT”>
    <table>realDbTableName</table>.....
    </StatementName1>
    if u look at the receiver structure of /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 this blog,action is an attribute of TEST and not STATEMENTNAME,for ur structure its an attribute of Statement2
    can u send ur receiver structure?
    thanx
    ahmad
    Message was edited by:
            Ahmad

  • 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 Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

    Hi All,
    I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
    Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
    Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
    Error Detail :
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
    This error can have several reasons:
    The segment ZPROSEG is assigned to a group whose header segment does not occur.
    The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
    Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
    Below is the Details of the Steps which I have followed:
    1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
    2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
         Here when I run syntax check warning appears "No predecessors exist".  I am not sure if its okay!!
    3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
    4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
    5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
    DATA segnam(27).
    READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
    IF sy-subrc NE 0.
    LOOP AT dedidd WHERE segnam = 'E1EDP31'.
    CLEAR dedidd.
    dedidd-segnam = 'ZPROSEG'.
    zproseg-matnr = 'Mat1'.
    zproseg-lgort = '001'.
    zproseg-gernr = 'SNo1'.
    zproseg-labst = 2.
    dedidd-sdata = zproseg.
    APPEND dedidd.
    ENDLOOP.
    ENDIF.
    Finally ran  transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
    Looking forward for your reply.
    Many thanks in advance.

    Hello,
    Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
    So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
    LOOP AT dedidd WHERE segnam = 'E1EDP31'.
    lv_index = sy-tabix. " <<--
    ADD 1 TO lv_index. " <<--
    CLEAR dedidd.
    dedidd-segnam = 'ZPROSEG'.
    zproseg-matnr = 'Mat1'.
    zproseg-lgort = '001'.
    zproseg-gernr = 'SNo1'.
    zproseg-labst = 2.
    dedidd-sdata = zproseg.
    *APPEND dedidd.
    INSERT dedidd INDEX lv_index. " <<---
    ENDLOOP.
    Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
    So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

  • Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

    Hi all,
    I have extended the the standard IDOC MATMAS05  classification view with structure as below-
    E1MARAM                        Master material general data (MARA)--->Mandatory segment
         Z1KLART                        KLART --->Extended chaild to E1MARAM
             Z1CLASS                        segment for class --->Extended chaild to Z1KLART
             Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
         E1MARA1                        Additional Fields for E1MARAM
         E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to                                                                               
    E1MARAM )
    I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
    Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
    This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
    Please help to resolve the issue.
    Thank you.
    Edited by: sanu debu on Apr 30, 2009 11:25 AM
    Edited by: sanu debu on Apr 30, 2009 11:31 AM

    Hi,
       You cannot add an segment in the middle of other segments.
    YOu have to add any segment at the last.
    If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
    In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
    Regards,
    Ravi Kanth Talagana

  • 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

  • Error sending IDOC from external Java application to Sap ERP system

    Hi Experts!
    When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
    My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
    Please help. I read all threads about this error, but non of those can help me.
    My relevant java sourcecode:
                doc.setSenderPort("CLNTJAVA");
    The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
    Both case(third party business sytem and erp business system) I have configured the ID    i think correctly. I  made a business systems,I configured the adapter specific identifies,I  made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
    My configurations if it can help for you.
    Hostname:sapsp5
    System name: NE2
    Clients:
    000 ERP
    001 Integration Server
    <b>SLD configurations:</b>
    Third Party Technical system name: Java_sytem
    Business System:CLNTJAVA
    Logical system name: CLNTJAVA
    <b>ID configurations:</b>
    Business System:CLNTJAVA
    adapter-specific identifiers:logical system:CLNTJAVA, <u>the rest is initial</u>,because I cant change it.
    IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
    I think the IDX1 port and the adapter specific identifiers are wrong. is it?
    my java source if the sender is the JCO
    doc.setSenderPort("INTSERV");
    My configurations if the sender is the JCO.
    <b>SLD configurations:</b>
    Technical system name: NE2
    Business System:INTEGRATION_SERVER_NE2
    Logical system name: INTSERV
    <b>ID configurations:</b>
    Business System:INTEGRATION_SERVER_NE2
    adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
    IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
    Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
    Thank very much.

    Hi!
    My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
    Check this configuration please(posted here:
    No service for system ... in Integration Directory)
    doc.setMessageType("ACC_DOCUMENT");
    doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
    doc.setRecipientPartnerType("LS");
    doc.setRecipientPartnerNumber("SE1CLNT500");
    <b>doc.setSenderPort("SAP3MA");</b>
    doc.setSenderPartnerType("LS");
    <b>doc.setSenderPartnerNumber("TREMACLNT");</b>
    doc.setClient("100");
    Inside XI configuration integration builder
    <b>Business Service: Service: TREMACLNT</b>
    Under the menu Service - Adapter specific identifiers
    Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
    IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
    Client: 100
    In IDX1 trans
    <b>Port: SAP3MA</b> (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
    (a not so well documented feature)
    Client: 100
    RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
    I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
    My idx1 port is the same as my SNDPOR value in Java,but still came the error.

  • 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

  • EDI: Syntax error in IDoc (mandatory group/segment missing)

    hi EDI/IDoc experts,
    Need you help urgently. According to the requirement, i need populate a segement  E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
    E1IDT01  was populated,  but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
    EDI: Syntax error in IDoc (mandatory group missing)
    Message no. E0079
    Diagnosis
    The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
    Procedure
    Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

    Hi all,
    Thanks so much for your concern!
    Finally ,this problem has been figured out  .
    Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
    Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because  I didn't fill data correctly. I missed to keep SY-TABIX in momory .
    when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX  is changed .So we can't just use MODIFY EDIDD_TABLE INDEX  SY-TABIX  in the last . we should define a local variable to keep  SY-TABIX  in memory and then use it to modify EDIDD_TABLE. 
    Follow is the final code.
    IF SEGMENT_NAME = 'E1IDT01'.
    TABLES :STXL.
    * Define for long text getting
      DATA: LIT_TLINE  LIKE TLINE   OCCURS 0 WITH HEADER LINE.
      DATA: LV_STRING(2000)  TYPE C.                          
      DATA: LV_TDNAME TYPE THEAD-TDNAME,
            LV_ID     TYPE THEAD-TDID     VALUE '0001',
            LV_LANG   TYPE THEAD-TDSPRAS  VALUE 'E' ,
            LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
    data:   LV_LINE   TYPE I,                " long Text lines
            LV_LEN    TYPE I,                " long Text length   
            LV_TABIX  LIKE SY-TABIX.                              
    * Clear memory
      CLEAR:LV_TDNAME,
            LV_STRING,                                        
            LV_LINE,                                           
            LIT_TLINE, LIT_TLINE[],                          
            LV_LEN,                                            
            LV_TABIX.                                        
    * Keep sy-tabix memory using a variable--This is the key point
      LV_TABIX = SY-TABIX.
    * Combine TDNAME with company code + accounting doc + fiscal year + item number.
        CONCATENATE  REGUP_DATA-BUKRS REGUP_DATA-BELNR
                     REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO  LV_TDNAME.
    * When vendor item has long text , read long text into lv_string
        SELECT SINGLE *
          FROM STXL
          WHERE TDOBJECT = LV_OBJ
            AND TDNAME   = LV_TDNAME
            AND TDID     = LV_ID
            AND TDSPRAS  = 'E'.
        IF SY-SUBRC = 0.
          CALL FUNCTION 'READ_TEXT'
            EXPORTING
              CLIENT   = SY-MANDT
              ID       = LV_ID
              LANGUAGE = LV_LANG
              NAME     = LV_TDNAME
              OBJECT   = LV_OBJ
            TABLES
              LINES    = LIT_TLINE.
          IF NOT LIT_TLINE[] IS INITIAL.
            DESCRIBE  TABLE LIT_TLINE LINES LV_LINE.
            DO LV_LINE TIMES.
              READ TABLE LIT_TLINE INDEX SY-INDEX.
              CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
            ENDDO.
            LV_LEN = STRLEN( LV_STRING ).
    * Make sure we only need  less than 840 charicters
            IF LV_LEN > 840.
              LV_STRING = LV_STRING+0(840).
              LV_LEN    = 840.
            ENDIF.
    * Populate Vendor item long text with segment E1IDT01 start from
    * Fields TXT03 to TXT14.
             EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
            MODIFY EDIDD_TABLE INDEX LV_TABIX.
          ENDIF.
        ENDIF.
      ENDIF.

  • Reason for errors in IDOCS ? pls tell small scenarios

    hi pls tell practical scenarios reason for errors in idocs? all ale configuration are done.

    goto se16 and look at table EDIDS....in that look at field status text...you will see different reasons when something goes wrong in idoc generation...
    there should be a lot of practical scenario examples for you inside it...

Maybe you are looking for