Idoc in sm 58 error in idoc to file

hai friends
iam doing file to idoc (matmas) secinario in that
while sending idocs from sap system to xi system iam getting this error
Transaction IDX1: Port SAPD40, client 151
destination  contain error
in xi system alredy one more  matmas secinario is running
it is defferent one .
fisrt one source and targer systems are sefferent
this one is defferent but the idoc is look into the SAPD40.
SAPD40 is first secinario port in idx1.
iam created saparete port for this scenario as SAPQ10.
why its not look into SAPQ10.
can any body help me
with regards
srikanth vipparla

hi Shrikant,
Kindly follow these steps to configure or check your ALE settings...
Reward points if helpful..
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)

Similar Messages

  • Getting error 51 saying 'IDoc included in IDoc packet containing an error'

    When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.
    Can any one tell me how to resolve this.

    Hi,
        Change the packet size to 1 then process again.

  • Getting error saying 'IDoc included in IDoc packet containing an error'.

    hi experts
    When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.I changed the packet size also but it was not resolved.
    Can any one tell me how to resolve this.

    Hi,
        Check below link......
    Getting error 51 saying 'IDoc included in IDoc packet containing an error'
    even this link is not solving problem then check the aplication log to get exact error text.
    Thanks,
    Asit Purbey.

  • Status Code 56; Idoc is added with errors

    file 2 idoc :
    i am getting error 56(idoc is added with errors).
    data was picked successfully from legacy system and sent to xi.. sxmb_moni shows success but in target r/3 weo5 shows error 56......plz anyone give me answer//

    answered

  • Error in Idoc-XI-File scenario

    dear all,
    i am doing one Idoc to Xi and then to a flat file scenario. i have created one BS of type 3rd party for receiver and ont BS of type Web as ABAP. Then I created one namespace and import the Idoc type there. I have not created any DT, MT, MI, MM. I have created one interface Mapping where both sender & receiver has same structure & I have selected there mapping type of ABAP-Class with one Z program name.
    Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type.
    Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?
    Warm Rgards,
    N.Jain

    <i>Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type. </i>
    >>
    you dont need a Sender IDoc channel to be configured.
    <i>Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?</i>
    >>>
    1. what does it say in SXMB_MONI ? Has the IDoc come into XI ?
    2. In communication channel monitoring what is the error for the recv. file adapter

  • Error in IDOC-XI-IDOC scenario

    Hi folks,
    Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPM’s involved. SAX parsing used to parse the IDOCs.
    We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as <b>‘Problems found during the EXPORT to specified keyin table’</b>.
    When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying <b>‘Function module does not exist or EXCEPTION raised’</b>.
    I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is<b> ‘EXPORT_TABLE_UPDATE_CONFLICT’</b>.
    In the ‘what happened?’ part of the dump, it says ‘Error in ABAP application program. The current ABAP program <b>“CL_XMS_PERSIST=============CP”</b> had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.’
    Even SXMB_MONI is not opening (for yesterday’s date). When I try to open it, it hangs for a long time, and finally opens an ‘ABAP Runtime Errors’ page with the runtime error titled as<b> ‘SNAP_NO_NEW_ENTRY’</b> and the error short text as ‘ Runtime error: Unable to write short dump’
    Please advise.Thanks a ton!
    cheers,
    Prashanth

    Hello Prashanth,
    First of all this is an XI issue and belongs in that forum.
    The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
    ‘Function module does not exist or EXCEPTION raised’- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
    Good Luck (don't forget to award points)
    Ofer

  • Error in IDoc AAE (Receiver) PI 7.3

    Dear Experts,
    I have a SOAP - IDoc scenario where I am using IDoc AAE reciver adapter for posting IDoc to SAP ECC system.
    Message is successful in SXMB_MONI,however getting an error as below in receiver IDoc adapter.
    Message processing failed. Cause: com.sap.aii.af.idoc.exception.IDOCAdapterException: com.sap.sql.log.OpenSQLException: Failed to set the parameter 9 of the statement >>INSERT INTO XI_IDOC_OUT_MSG ( IDOC_NUMBER , XI_MSG_NO , REF_NUMBER , ORIGINAL_IDOC_NO , IN_TIME , MESSAGING_TYPE , IDOC_TYPE , CIM_TYPE , SEND_PORT , SEND_PRTNR_NO , SEND_PRTNR_TYPE , CLIENT , STATUS , CONTROL_RECORD , CHANNEL_ID , ACK_NEEDED , ACK_RECEIVED , ARCHIVE ) values ( ?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,? ) <<: Cannot assign an empty string to a parameter with JDBC type >>VARCHAR<<.
    My payload for this message is --
    <HU_CREATE01>
                   <IDOC BEGIN='1'>
                        <EDI_DC40 SEGMENT='1'>
                             <TABNAM>EDI_DC40</TABNAM>
                             <MANDT>120</MANDT>
                             <IDOCTYP>HU_CREATE01</IDOCTYP>
                             <MESTYP>HU_CREATE</MESTYP>
                             <SNDPOR>SAPPID</SNDPOR>
                             <SNDPRT>LS</SNDPRT>
                             <SNDPRN>BS_ORIWIN</SNDPRN>
                             <RCVPOR>SAPD3S</RCVPOR>
                             <RCVPRT>LS</RCVPRT>
                             <RCVPRN>D3SCLNT300</RCVPRN>
                        </EDI_DC40>
                        <E1BPHUHDRPROPOSAL SEGMENT='1'>
                             <HU_STATUS_INIT>A</HU_STATUS_INIT>
                             <PACK_MAT>000000000002001755</PACK_MAT>
                             <HU_EXID>00340042312419076037</HU_EXID>
                             <TOTAL_WGHT>11.123</TOTAL_WGHT>
                             <UNIT_OF_WT_ISO>KGM</UNIT_OF_WT_ISO>
                             <CONTENT>00002059911110071031</CONTENT>
                             <PLANT>9610</PLANT>
                             <STGE_LOC>2000</STGE_LOC>
                        </E1BPHUHDRPROPOSAL>
                        <E1BPHUITMPROPOSAL SEGMENT='1'>
                             <HU_ITEM_TYPE>1</HU_ITEM_TYPE>
                             <LOWER_LEVEL_EXID>00000000000000000000_Test</LOWER_LEVEL_EXID>
                             <PACK_QTY>12</PACK_QTY>
                             <BASE_UNIT_QTY_ISO>ZCP</BASE_UNIT_QTY_ISO>
                             <BASE_UNIT_QTY>ZCP</BASE_UNIT_QTY>
                             <MATERIAL>000000000000205991</MATERIAL>
                        </E1BPHUITMPROPOSAL>
                   </IDOC>
              </HU_CREATE01>
    Could you please give me your valuable input for the same.
    Waiting for a reply.
    Thanks in advance.
    Best Regards,
    Sugeet.

    Hello
    Note #1688780 IDoc AAE Adapter fails to insert empty strings in database, has been created to resolve this error. The fix is still being tested, so the note is not available for download just yet. Once the fix is released, the note will be available for download.
    Here are some further details on the cause of the error:
    The issue occurs if the persistency of the IDoc_AAE adapter is enabled
    via the 'Persistance' property for the 'JavaIdocAdapter' resource
    adapter and one or more of the IDoc relevant properties (for example
    sender/receiver port, partner number or type) of the XI message is/are
    empty strings. As empty string insertion into database is not supported
    by the persictency framework the above OpenSQLException exception is
    thrown and the XI message processing fails.
    Regards
    Mark

  • Error in Idoc with status 26

    Hi,
    IDOC  showing an error messge when syntex check.
    EDI: Syntax error in IDoc (segment cannot be identified)
    Diagnosis:
    The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
    This error can have several reasons:
    The segment E1EDP19 is assigned to a group whose header segment does not occur.
    The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (extension ).
    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.
    Please help me....
    Regards,
    Sudha

    Hi,
    I have pasted a portion of my code:
    DATA: BEGIN OF GT_EDIDC OCCURS 0.
            INCLUDE STRUCTURE EDIDC.
    DATA :END OF GT_EDIDC.
    DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
            INCLUDE STRUCTURE EDIDC.
    DATA :END OF GT_EDIDC1.
    DATA: BEGIN OF GT_EDIDD OCCURS 0.
            INCLUDE STRUCTURE EDIDD.
    DATA :END OF GT_EDIDD.
    DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
            INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
    DATA : END OF GT_Z1ZPSOBJLOC.
    * Control Record
    FORM BUILD_CONTROL_RECORD .
      GT_EDIDC-MESTYP = C_MESTYP.
      GT_EDIDC-IDOCTP = C_IDOCTP.
      GT_EDIDC-DIRECT = C_1.
      APPEND GT_EDIDC.
    ENDFORM.                    " built_control_record
    *&      Form  built_data_record
    * Data record
    FORM BUILD_DATA_RECORD .
      LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
        GT_EDIDD-MANDT = SY-MANDT.
        GT_EDIDD-SEGNAM = C_SEG.
        GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
        APPEND GT_EDIDD .
      PERFORM DISTRIBUTE_DATA.
      ENDLOOP.
    ENDFORM.                    " built_data_record
    *&      Form  distribute_data
    * Distribute Data
    FORM DISTRIBUTE_DATA .
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          MASTER_IDOC_CONTROL            = GT_EDIDC
        TABLES
          COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
          MASTER_IDOC_DATA               = GT_EDIDD
        EXCEPTIONS
          ERROR_IN_IDOC_CONTROL          = 1
          ERROR_WRITING_IDOC_STATUS      = 2
          ERROR_IN_IDOC_DATA             = 3
          SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
          OTHERS                         = 5.
      CASE SY-SUBRC.
          WHEN 1.
          MESSAGE E004.
        WHEN 2.
          MESSAGE E005.
        WHEN 3.
          MESSAGE E006.
        WHEN 4.
          MESSAGE E007.
        WHEN 5.
          MESSAGE E008.
        WHEN OTHERS.
    * Do Nothing
      ENDCASE.
      COMMIT WORK.
    * Clear IDOC data internal table after use
      CLEAR GT_EDIDD.
      REFRESH GT_EDIDD.
    ENDFORM.                    " distribute_data
    Hope it proves useful.
    Regards,
    Gayathri

  • Error in IDOC creation of Inbound Delivery (VL31N) with  Error Message Number VL561

    H,
      I'm getting an error message when generating a test IDOC of Message type DESADV and IDOC type DELVRY03 to create Inbound delivery with reference to a standard purchase order.
    Essential transfer parameters are missing in record: PO Number and Item
    Could you one help me out in solving this.
    Thanks,
    Raj

    Hi ,
    Goto SM13 .
    Find the terminations based on user and creation date.
    Get the same analysed by ur ABAP team.
    Also check the confirmations in PO at Item level.
    Regards
    Ramesh Ch

  • IDoc failed with the error massaeg "Instance of object type could not be ch

    Hi All
    I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
    Message type :PORDCR
    Basic type : PORDCR05
    Message no. BAPI003
    Status : 51
    All POs are get uploaded in SAP during Cut over activities only.
    Please suggest on this.It will be a great help.
    Thanks
    Ajit

    Hi
    After uploading POs into SAP we are changing quantity and value in PO in Legacy system, and for this all IDocs are failed, subsequently these changes are not triggering to ECC.
    Please help
    Thanks
    Ajit

  • IDoc included in IDoc packet containing an error: transfer it separately

    Hi Gurus,
    I'm having this problem in our ECC side. I already did what Michal said in his blog:
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    I have bundled the multiple IDOCs into 1 MATMAS.
    But I'm still having the error IDoc included in IDoc packet containing an error: transfer it separately.
    I've searched in the forums and none of them worked for me.
    Thanks in advance!

    Disable packaging or change the Partner Profile on WE02 transaction to "process immediately" the IDOCS.
    When you process the IDOCS in background mode, it will create packages (it is enabled by default), and in case any of them fail you won't be able to see the root cause, but will have to go to BD97 transaction to process them again. Therefore, please use the "process immediately" or disable packaging and then you will be able to either see the error or process it because it won't fail because of another IDOC.

  • AckRequestNotSupported error in IDoc to file scenario

    Hi,
    I have a scenario from IDoc to file adatper, when i try to run this scenario, every thing is ok except there is a error in message monitor.
    This error is regarding the Acknowledgment("Acknowledgment not possible"), But the ALEAUD IDoc have been sent to the orignal sender (IDoc side) with the empty content except the Header segment such as sender name, receiver name etc.
    And when i tracted the detail information in message monitor, i got the following error information.
      *<SAP:Status>AckRequestNotSupported</SAP:Status>*
      *<SAP:Category>permanent</SAP:Category>*
    I also went through some weblog and artical, i didn't got the solution.
    If some body also have this error?
    thanks & Best regards
    Rocky
    Following is My acknowledgment error information: FYI
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Response*
      -->
    - <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
      <SAP:Status>AckRequestNotSupported</SAP:Status>
      <SAP:Category>permanent</SAP:Category>
      </SAP:Ack>
    Outbound Acknowledgment content:
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>030</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000036022</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ALEAUD</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPO01</SAP:SNDPOR>
      <SAP:SNDPRN>A01CLNT030</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPO05</SAP:RCVPOR>
      <SAP:RCVPRN>A05CLNT231</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS>03</SAP:STATUS>
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY />
      </SAP:IDocOutbound>

    Hi Rocky,
    Check the below links of setting up of ALEAUDUT RESPONSE:
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Check this document on handling IDOC acknowledgements. This might give you some idea.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    Please check the above two links if u have missed anything in setting up the acknowledgement.Let me know if u need furthur information
    Thanks,
    Bhargav.
    Note:Award points if found useful.

  • SM58 Error For IDOC to IDOC Scenario

    Folks,
    I am getting an error in SM58 from Sender system ( IDOC-XI-IDOC Scenario ) <u><b>IDoc adapter inbound channel: Error Error when reading</b></u>. The Issue is XI is not receiving any IDOCS. Does anybody know what is the problem
    Thanks
    Manish

    Hi Renjith,
    I'm facing the same problem the flow is basically form BW to BO.
    When they load the data at sender side the idocs are stucked with error status 2:
    "Could not find code page for receiving system" in transaction BD87.
    Also when I reprocess it is successful. But its is getting stucked in SM58 with errors like:
    1)Error in RFC connnection
    2)ERROR REQU_D38IW3WD0XGK1DA48DM96N12J PG# 8 in BW
    When I execute it throes an error saying "Function Module does not existsor EXCEPTION raised".
    Also are many queues stucked in SMQ1 Outbound.
    Please help. Many Thanks.

  • Error sending Idoc's to SAP

    Hi,
    I'm getting error in file-XI-SAP scenario. File is read and transformed to Idoc ok, but then I get this kind of error message in SXMB_MONI:
    <SAP:Stack>Error: Basic type 'HRMD_A01' is unknown</SAP:Stack>
    What I'm I missing in the scenario?

    Hi Tapio,
    Take a look at this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    Error: No IDocs could be sent to the SAP BW using RFC.
    Hope it helps you.
    Cheers,
    Chandra

  • IDOC is posting with Errors in File to IDOC scenario

    Hi,
       I did the File  to IDOC scenario for CREMAS  . IDOC is posting with Errors .. i.e. in the status record it was showing  56- EDI: Partner profile inbound not available  ..
    If I manually process that IDOC in WE19 , then it was processing successfully..    and in the  we19 it was showing Inbound Processing : Port Not Maintained    but even though manually it was posting fine...
    any ideas regarding this will be appriciated..... 
    Regards
    Babu

    Please check whether you had done the following assuming your doing File to Idoc
    Settings in your Business service for the receiving system
    Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
    Settings in R/3
    WE20 - Add the partner profile for the particular message type cremas and process code.
    Your statement
    " and that same logical system name  had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
    Please do mention R/3 Details in the receiver business service or system.
    Thnz

Maybe you are looking for

  • Material inventory being posted in multiple SLOC at the same time

    When the same material is stored in multiple SLOCs and physical inventory counters are trying to enter the count at the same time the system stops them  with error- "material is blicked by user xxxx" etc. Please note at this client they do not block

  • F110 - Posting details

    Hello, In the transaction OBVCS, there is a section related to the POSTING DETAILS. There are the following fields: - Document type for payment - Clearing document type I'd like to understand when the posting happen with the CLEARING DOCUMENT TYPE. I

  • Dam:asset scripts location

    Hello, I dont find the location of the dam:assets scripts. For example the assetthumbnail script which is launched when you update one asset's thumbnail via this url /assetname.jpg.assetthumbnail.html . Where these scripts are located ?

  • SOME MOST PROBALE ERROR IN MOST JAVA CODE

    hi... Otn team.. i want to know while i am running some program in netBeans it shows some error ... 1)class interface or enum expected. 2)illegal Start of type. 3)if i use super keyword to add some argument within it than it shows an error that "Keyw

  • How to create cross tab reports using RAS SDK api with Crystal Reports XI

    Hi Everybody, Iam generating reports in a web-based application with Crystal Reports XI using Report Application Server(RAS) SDK API. The columns in my report exceed that of an A4 sized page. So, when I export that report to pdf, only those columns t