Wrong idoc

i m new to ale idoc
i have configured client 800 (sender) and client 910(reciever)
idoc gets triggered from sender status 03 12 30 01 is fired . with idoc no.
but in recieving client im not getting the idoc instead i m getting wrong idoc. n status 51.
i have generated port name as rfc800(client 910) and rfc910(client 800).
is the port(sending and reieving) should be same in idoc.

Hi,
idoc status 51 means idoc is in queue..
so ru the below program to turn to 53 success status by entering the idoc number which is in 51.
Program RBDMANI2 for status 51...
Regards,
Prabhudas

Similar Messages

  • Urgent problem, wrong IDOC relating wiht PO.

    Hello experts:
           Thank you in advance for all your replies.
           There is something wrong with   An IDOC associate with a PO,  its status is 51saying that " no PO items were found for IDOC 11939458 item REP 621104 /15 ",   anybody know how to modify it manually.    couldn't thank you more.
    Best regards.
    Frank

    Hi
    If you want to change the IDoc Manually, goto we02, enter the Idoc number,
    Click on the Segment icon Click on Data record -> Diplay/ Change. Change the Idoc & click on save.
    Now go to BD87, enter the idoc number, select the idoc last node & Click on restrict & process.
    the idoc will be reprocessed & the PO will be created.
    Thanks & Regards
    Kishore
    Edited by: Kishore Kumar Chiluka on Apr 17, 2008 12:47 PM

  • Trouble shooting File to Idoc scenario: wrong Idoc structure in target

    Hi All,
                 I am working in an file to idoc scenario. Now the scenario is running but the idoc I am sending from SAP XI is not matching with one received in SAP R/3 system. This is not a new scenario. The  scenario was already existing. I have done structural changes in Idoc structure and re-imported it in SAP XI. When the iodoc reaches SAP R/3 system I check its structure and data content. 4 of its fields are missing all 4 were newly added fields. Data from some fields are getting merged into one field within Idoc. data from one field is moving onto other fields in target. I have refreshed the metadata using IDX2 transcation within SAP XI but still getting same result.

    Hi All,
    I am able to see the changed idoc structure in IR. I have also tried cache refresh. I am trying to explain my problem once again with example.
    Source Idoc in XI
          fieldname                            data
           f1                                       d1
           f2                                       d2
           f3                                       d33
           f4                                       d4
           f5                                       d5
    Idoc structure received in SAP R/3 system. I am seeing through we02 transcation, inbound idoc
          fieldname                            data
           f1                                       d1
           f2                                       d2
           f4                                       d33d4
    I have tried cache refresh, IDx2 metadata refresh, but no improvement of the situation.

  • Get wrong IDoc control data

    Hi, experts, I create a extension base on baisc type SISDEL01 for delivery.  And I have add the control data in WE82. But now i found when i get idoc control data, the field of extension has no value. Could somebody give me some advices? Thanks.

    Hi Rick
    After released the IDOC did you re imported?. Are you able to use the extended structure in PI?.
    Check this as well
    XI IDoc  control record data source?
    Thanks
    Gaurav

  • Wrong idoc fetched

    Dear Friends,
    I am trying to send an extension idoc from one client to another client . I made changes to the partner profile and put my basic idoc type and extension idoc . I also defined the message type for my idoc .Whenever I try to save a billing doc and try to go to the we02 and check for outbound idocs. I see that it sends some other idoc. I eman my idoc is not  sent. It sends some other idoc which was sent earlier. I am wondering why it is not fetching my new idoc and sending it ?
    Thank you
    Alisha

    When you’re saving the billing document, are you populating the segment of the ext.idoc in your program?
    This could be the problem...
    Bye

  • BPM: Idoc Monitoring

    Hi Colleagues,
    I'm configuring IDoc Monitoring in BPM and have an unexpected result.
    System generate error alert "0 IDocs have been found since the last collector run at 01:56:56 on 18.11.2009"
    I expected this message to be green since system didn't find any IDoc error, or with proper number when it has errores.
    Mi configuration for IDoc Delta Monitoring is:
    Direction Outbound
    Partner Port ZPTA_PI
    Basic Type ORDERS05
    IDoc age (in hours) 336
    Status Number(s): All technical for outbound:
    - 29 Error in ALE service (for example, errors with field conversion, and so on)
    - 26 Syntax error (for example, too many segments, wrong IDoc structure, and so on)
    - 37 IDoc added incorrectly
    - 02 Error passing data to port (for example, port not available, file system not available, and so on)
    - 20 Error triggering EDI subsystem (for example, error during OS script processing)
    Any ideas?
    Regards,
    Renato Petrulis

    Hi Renato
    I think you work with IDoc monitoring based on application monitor.
    So in this case, I guess setup based on the meanining is correct way.
    (You do not have to setup like IDoc Monitoring of CCMS base).
    *Also at the moment IDoc monitoring based on application monitor is recommended.
    Now you focus on technical error.
    So it should not be occur. So I think using just "more than"
    is ok. If you use less than, in case of zero "0" value,
    you get some alert. So I think in that case, less than is not
    necessary.
    It is worth using less than alert when you monitor through put.
    How many number of documents are created, then checking data
    using more than (due to some error, less data created than expected)
    and less than (due to some error like incorrect master data setting,
    less data created than expected)
    best regards
    Keiji

  • Idoc error mapping error for segment "E1EDT13 006" in DESADV idoc

    Hi SAP Gurus,
    DESADV IDOC for few articles is not getting passed from SAP to legacy system. It is missing one segment"E1EDT13 006" for goods issue.
    Why is this mapping error happening. How can this be resolved.
    Regards.
    Sumi

    Hi Nsangle/SAP gurus,
    Thanks for  that. But, I have already compared the failing idoc with the successful one. It's the segment E1EDT13 006 missing in the wrong idoc. I have already added that idoc and reprocessed it.
    But, I wanted to know why such kind of idoc segment missing/ mapping error happens.
    Regards.
    Sumi

  • Inbound Idocs: Queue Processing (non-stop queue?)

    Hi everyone!
    I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
    There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
    I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
    I'm using PI 7.0 SP30.
    Thank you in advance!

    First, this is not serialization, it's the queuing design EOIO... they are not the same.
    So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
    Basically the serialization is not a good fit for these requirements.
    Here is one solution:
    1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
    2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
    3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
    4- There is  standard report that you have to schedule and restart the queues
    5- Reprocess the IDOCs from steps 2
    The enemy of EOIO design is the user locks in the target system...
    Cheers,
    Fouad

  • Inbound processing of segment E1EDT13 - QUALF 499 in SHPMNT idoc

    Dear all,
    we are currently facing the problem, that we want to send customized deadline dates in a SHPMNT idoc into our system.
    I set up the customizing accordingly, maintained the data in a outbound delivery and created an idoc out of it. I saw, that the segment E1EDT13 is filled using QUALF 499.
    I took this idoc modified a few fields and sent it back as an inbound delivery.
    This works, but E1EDT13 with qualifier 499 doesn't appear in the created inbound delivery.
    I checked the coding of the inbound function modules concerning qualifier 499 and detected, that this qualifier is never considered in the coding.
    Does SAP support the inbound posting of qualifier 499? If yes, how? Which function module will be used?
    If no, does anyone have an idea/experience concerning inbound SHPMNT using qualifier 499 in segment E1EDT13?
    Kind regards
    Harry
    PS: We are using a ECC 6.0 release.
    PPS: I posted the wrong idoc type in a previous message.

    Posted the wrong idoc type. Sorry
    Moderator Message: I will lock this thread, just in case someone feels tempted to answer it :-). Next time please use the EDIT option to edit your post.
    Edited by: kishan P on Nov 4, 2010 5:53 PM

  • Inbound processing of segment E1EDT13 - QUALF 499 in DESADV idoc

    Dear all,
    we are currently facing the problem, that we want to send customized deadline dates in a DESADV idoc into our system.
    I set up the customizing accordingly, maintained the data in a outbound delivery and created an idoc out of it. I saw, that the segment E1EDT13 is filled using QUALF 499.
    I took this idoc modified a few fields and sent it back as an inbound delivery.
    This works, but E1EDT13 with qualifier 499 doesn't appear in the created inbound delivery.
    I checked the coding of the inbound function modules concerning qualifier 499 and detected, that this qualifier is never considered in the coding.
    Does SAP support the inbound posting of qualifier 499? If yes, how? Which function module will be used?
    If no, does anyone have an idea/experience concerning inbound DESADV using qualifier 499 in segment E1EDT13?
    Kind regards
    Harry
    PS: We are using a ECC 6.0 release.

    Posted the wrong idoc type. Sorry
    Moderator Message: I will lock this thread, just in case someone feels tempted to answer it :-). Next time please use the EDIT option to edit your post.
    Edited by: kishan P on Nov 4, 2010 5:53 PM

  • Idoc Error    Empty Schedule Agreement  Purchasing Group Assnmt.

    Dear Experts,
      We have a job running, automatic sending Schedule Agreements' Line Items out through EDI
      But some Schedule Agreements' field Purchasing Group is empty, Idocs created on these SAs are wrong
      Idoc have wrong data filled in the Control Records, and segements are empy, status is set 26 in outbound process
      because Idocs have wrong data, it is also very hard to trace
      why ...
      pls help ..

    Using SU53 Immediately after Error will tell you what authorization is exactly missing. Send the screen shot to your BASIS team who normally incharge of giving authorization.
    If you have authorization for SU22, check what authorization objects SAP check within that Tcode and check whether those object and appropriate authorization for them is maintained in any one role / profile assinged.
    - Sunil Kolambkar

  • Read data from IDOC

    Hello Expert
    do you know where i can find (tables) data contained in wrong idoc?
    I have 2000 MATMAS idoc in wrong status and i need to create for all these materials new idoc , therefore i need a list of all materials memorized in these idocs.
    Do you have any idea?
    please let me know
    thanks
    Boris

    Hi
    Tcode WE05 - We can display all the IDOCs based on selection criteria.
    Tcode  : BD87 idoc Status Monitor and Reprocessing.
    These tcodes may help u.
    <b>Reward if Helpful.</b>

  • No master data transmitted from ERP to GTS

    We are using ERP 4.70 with the following settings:
    SAP_APPL 470 SP-Level 0031
    PI 2004_1_470 SP-Level 0016
    PI_BASIS 2005_1_620 SP-Level 0017
    SLL_PI 720_470 SP-Level 0007
    together with SAP GTS 7.2 SP-Level 09
    I created the message types /SAPSLL/DEBMAS_SLL and /SAPSLL/MATMAS_SLL manually and activated them.
    I try to send an customer master data to GTS but the partner will not transmitted. In the log protocoll in GTS the error message appears that there was no data collected from table SAPSLL/TCOGVA
    If I try to send a material master from ERP to GTS the RFC connection gets broken with error message:
    RFC error (The transaction has dumped the connection). What I had found out is, that the error appears in the function /SAPSLL/API_1006_SYNCH_MASS.
    Has this something to do maybe with a wrong IDOC type? Does I have to to something in some tables. Do I use the wrong programme? I use /SAPSLL/MATMAS_DISTRIBUTE_R3 and /SAPSLL/DEBMAS_DISTRIBUTE_R3.
    I made absolutely the same customizing settings in another system at a customer and it worked fine there.
    Does anybody has an idea? Thanks to all for the possible help.
    Thanks very much in advance

    Hi Andreas,
    there are several possibilities why this is not working.
    First of all you should check, if your RFC settings are correctly maintained.
    Please bear in mind that the logical systems have to be assigned to logical system groups and that GTS and R/ shall not be in teh same group.
    Please also ensure that the logical system name is the same in both systems, R/3 and GTS.
    Secondly there is also the possibilites that necessary tables are not filled correctly.
    Please run report /SAPSLL/PLUGIN_CHECK_R3
    It could be thate.g. the tables TBD24 and TBD62 are not filled 
    for the relevant message type (in your case /SAPSLL/DEBMAS_SLL and /SAPSLL/MATMAS_SL)
    To update this tables corretly pls. do the following:                                                                               
    - BD53                                                                
    - select message type (/SAPSLL/MATMAS_SLL)and edit it                 
    - select a segment                                                    
    - save                                                                
    - deselect segment again                                              
    - activate                                                            
    - set in trx BD60 the FM to the correct value                         
      (/SAPSLL/MATMAS_DISTRIBUTE_R3)                                                                               
    You can than check with the programm: '/SAPSLL/PLUGIN_CHECK_R3' if    
    all 4 required tables (TBD24, TBD62, TBDA2, TBDME) are filled, or not.
    I hope this helps with the issue.

  • IDOCXMLtoFileConvertor Exception

    Hi,
    Can someone please let me know the reason for below exception for IDOC XML converter.
    Message processing failed. Cause: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not available. See cause exception for details. : state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0
    Thanks
    -Kulwant

    Hi Kulwant Bhatia,
    I understand you are getting error message in IDOC sender channel (using IDOCFlatToXmlConvertor) in PI7.11. Hope you have followed steps mentioned in SAP Help [Link1|http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm]
    It seems, error is due to wrong IDOC format triggered from sender SAP system (R/3). You may take out IDOCFlatToXmlConvertor module from communication channel and test interface again, to see how messages looks (in SXI_MONITOR or RWB).
    Regards,
    Raghu_Vamsee

  • Status Errors In RBDMANI2

    I am currently experiencing a problem in using program RBDMANI2 to reprocess some failed IDOCs whereby the status message is being appended to the wrong IDOC. 
    For example, IDOC no 1234 fails, as does IDOC 1235.  Periodically, RBDMANI2 is run in batch mode to reprocess all failed IDOCs.  IDOC 1234 and 1235 are set to status successful, even though the data contained in IDOC 1234 has not been successfully processed, and the success message contains the document number relating to IDOC 1235.
    I have checked for the obvious, such as message and BDC data tables not being refreshed, but this appears to be OK.
    Does anyone have any suggestions as to where the problem may lie?
    Thanks
    Colin

    Why don't you put a break-point in your processing function module and execute RBDMANI2 to see what's wrong inside?

Maybe you are looking for