IDoc missing in IDoc - XI - IDoc scenario

Hello!
The integration scenario is R/3 4.6C (IDoc) -> XI -> (IDoc) R/3 4.6C for DELFOR, ORDERS, ORDCHG, DESADV and ORDRSP.
Now we switched to a new XI development system and the flow is working for all message types besides DELFOR.
WE20 -> New XI Logical System Name -> DELFOR points to the new receiver port which referenced to the correct SM59 destination that is used by all other message types as well.
There is also no error in SM58 in the sending R/3 system and the DELFOR IDocs are in status 12 in WE02 but when I search the IDoc number in IDX5 on XI the IDocs are not there.
Does anybody have an idea where to find the DELFOR IDocs?
Regards, Tanja

Hello!
> IDOC staus if it is sent out from R/3 should be 03 or
> 12?
First it was 03 but as I was not able to find it anywhere I ran a report and the status changed to 12 afterwards.
> if IDOC is coming out of R/3 without any errors( sm58
> no errors) then it should come in the SXMB_MONI in XI
> as it usess th TRFC Port........
Yes, this is also my understanding but it is not in SXMB_MONI nor in IDX5.
> if it is not check the SMQ2 and SMQ! in both XI and
> R/3...it cannot go anywere else (-:
I have checked SMQ2 and SMQ1, the queues are empty in XI and R/3.
Regards, Tanja

Similar Messages

  • Missing items in the IDoc for the delivery

    Hi to all,
    Sorry if not posting in the right forum.
    In my customer's scenario, an IDoc is created against a delivery (via the delivery output), and sent via ALE to a distant warehouse system, for picking and GI posting (basic type SHPMNT03).
    For some times, the IDoc created against deliveries including BOMs is missing the main item of the BOM (though the BOM main item is in the delivery).
    Consequently, the integration in the distant system is failing, because the higher-level item referenced in the BOM sub-items is missing.
    Surprisingly, re-triggering the delivery output does re-generate a complete IDoc, where the segment for the main item is back.
    I looked almost everywhere, did many searches in OSS (on SHPMNT03, on HIPOS, on E1ELD24 - segment name in the IDoc -, on "Missing items in the IDoc for the delivery", etc...), I even simply googled the web, but I can't even figure out what is the cause for this (I imagined it could be caused by a missing commit in the program generating the IDoc, but don't know whether this make sense).
    Any help would be highly appreciated.
    Thanks in advance and best regards
    Yan
    Edited by: Yan Loiseau on Jul 8, 2010 12:52 PM
    Edited by: Yan Loiseau on Jul 8, 2010 12:56 PM

    Hello Yan
    Jelena is right, you are better off taking it up with SAP. I also did not find any relevant OSS notes.
    However the issue, according to my reading, is in the following areas:
    1) LV56KF05: INCLUDE LV56KF62 .  " FILL_E1EDL24"
    This fills the EIEDL24 segment, may be the main item is filled  initially and overwritten later.
    2) Function Module: IDOC_OUTPUT_DELVRY
    You can look at the following OSS notes (though not fully relevant)  for some clues:
    810981 - Reference data missing in DESADV IDoc from decentralized WMS
    537470 - BOM + batch split in decentralized WMS, confirmation fails
    752921 - VL563: Higher-level item does not exist
    705086 - Higher-level item does not refer to existing item
    Hope this helps. Good luck.

  • How to get Idoc acknowledgment in File to Idoc scenario

    Hi All,
    Please give suggestions about the below mentioned scenario:
    Scenario: File–XI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
    Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, ‘n’ were posted successfully and rest failed along with the error description. How can this be achieved?
    Regards,
    XIer

    Pls go thruough these links also
    Please see the below links
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    unable to import from SLD
    /people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    <b>IDOC Acknowledgements</b>
    R/3 IDOC ->XI-> ORACLE Error Handling
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    /people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    Regards
    Abhishek Agrahari

  • How to use IDOC and RFC adapter in 1 scenario?

    We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and  what are the design and configuration objects we require to create?

    To achieve this you have to use
    Two Interface Determinations
    Two Communication Channels (IDOC & RFC)
    & Two Receiver Aggrements.
    Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

  • Query realted to IDOC packaging in case of  IDOC-SAPPI- FILE scenario

    Hi,
    I have requirement related to IDOC packaging, i.e. SAP ECC -SAP PI - FTP server.
    I have done the following settings:
    1) In WE20, I put the partner profile settings to collect mode.
    2) I am using RSEOUT00 to trigger the collected IDOCs for example 2 idocs together.
    3) In SAP PI, I have done the following settings
    a) I added the the parameter in sxmb-adm, RUNTIME , PACKAGING & Value 1
    b) I have used IDXPW t-code to activate the message packages for IDOC
    c) I run the job through sxmb_adm t-code, configure event driven message filtering
    d) I exported the xsd of ORDERS05 and changed occurence of source structure to 0 to Unbounded and imported it in Integration Repository.
    e) I am not using mapping & interface mapping as I just want to post the IDOC structure as it to the receiving FTP server. Therefore when I changed the occurence of ORDERS05 xsd to 0 to unbounded my idea was that in the outbound message interface it will be reflected which will be ultimately reflected in Integration directory.
    Problem Details:
    When I test for the 2 PO idoc from SAP ECC, it generates 2 messages in SAP PI and also 2 files in FTP server but actually it should generate one output file containing both the IDOC details.
    Note: I am just trying to merge 2 idocs of PO as IDOC package into one output message.
    Can anybody what configuration settings I am missing for the packaging.
    Thanks & Regards
    Prabhat

    Hi Prabhat,
    If you are using PI 7.0 EHp1 or PI 7.1 Ehp1, you can configure packaging parameter and create single file for multiple idocs without using BPM.
    In other case, you have to use BPM.
    But recommended approach would be to create XML file port on SAP ECC and create IDOC XML file.
    You must have set collect IDOCs option in partner profile.
    Now you can execute RSEOUT00 report program and specify IDOC type and number IDOCs to be collected.
    This configuration will generate IDOC XML file for number IDOCs you specified in RSEOUT00 report program.
    In PI you can use File adapter to pick the file.
    Here is the nice blog explaining entire process:
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    Best Regards,
    Divyesh

  • Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

    Hello,
    the above segment is missing in the inbound idoc - basic type pexr2002.
    I have checked in TC-we30 and its available there.
    but still the idoc is getting generated without this segment.
    can someone suggest.
    thanks
    Arun

    Hi All,
    I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
    I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002  and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
    We have done the following steps:
    - BTE 2441 is available on our release
    - house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
    - entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
    - code maintained in ZXF08U04
    The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
    Can you advise what we might be missing please?
    Thanks and regards
    Mike

  • Error message : Info Idoc missing ;database system

    I am  trying to load the data from database system  oracle ,the data was successfully loaded into psa , but can’t able to load the data into ods from psa .
    Data in psa is all green without any errors , as  info idocs are missing its not letting  to load data manually from psa to ods ,
    I try to reload  but coming up with same error
    Next day problem was fixed automatically, I want to know what is the exact reason for this problem  and  how can  next day  it fixed automatically

    Error message : Info Idoc missing ;database system
    I need the solution urgently, please help

  • Why IDoc Sender Channel Used in Outbound Scenario's

    Hi Team,
    In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
    Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
    Can you give me clear idea on it / suggect any blogs.
    Thanks.
    Drumi

    HI,
    In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
    Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
    we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
    The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
    This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
    Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
    be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
    one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
    thanks,
    Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

  • Idocs missing from source system

    Hello,
    I am trying to extract data from R3 to BW. I am getting an error message in BI, No idocs arrived from the source system.
    In SM58 system showing the message 'No service for system SAPECC, CLIENT 800 IN INTEGRATION DIRECTORY'. Please help on this issue
    Regards,
    Ramesh

    Hi Ramesh,
    Check whether the connection is proper between BW & R/3. 
    Goto your Source system> Right clcik> Check.
    You can also check the following :
    No Idocs arrived from the source system.
    Idocs missing: No selection information arrived from the source system
    Error when updating Idocs in Source System
    Hope it helps!
    Regards,
    Pavan

  • Idocs miss match.

    Hi,
    I am changing a Customer Details using XD02 Tx.
    In BD50,The Message type'OILDEB' is Active.
    But when I run Program 'RBDMIDOC' to create an Idoc to send this change to other system,I am (At Times,not always)getting Idocs created in wrong order.
    Like for example >> Idoc 12 with creation time 5.00pm and Idoc 13 with creation time 3.00pm (Both were created on same day).
    Can there be a possiblity that Idoc 13 be created before Idoc 12 or is this an exceptional case?
    I was under the impression that Idocs get created in a sequence.
    Its Urgent.Kindly let me know.
    Regards,
    Shashank.

    yes, it is possible in idocs that they may be sent in that way because
    some idocs may be in queue which will send them later.
    SHASHANK AMIN wrote :
    Its Urgent.Kindly let me know.
      Follow the rules of engagement and dont use these kind of words.

  • Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

    Hi Experts,
    I am doing idoc to file scenario.
    I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
    In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
    I heard that, i can do in 3 ways. those are
    1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
    2. Without message type: create a message interface whose message type would be idoc itself
    3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
    If i  go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
    MY ASSUPTION:
       step1: I will import the IDOC into IR.
       step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
      Is my assuption or correct or not?, please tell me.
    So please tell me the entire scenario how to achieve this.
    Please help in this issue.

    Hi Laxmi
    1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
    -- Not Possible
    2. Without message type: create a message interface whose message type would be idoc itself
    -- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
    3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
    -- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
    Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
    While doing an IDOC -> XI -> File scenario, The Points to noted are:
    1. You don’t need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
    2. You import the IDOC and use the same in your mapping.
    3. In this configuration note that you don’t have a sender agreement as you don’t have a sender IDOC adapter.
    If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
    points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
    IDOC -> File scenario ref:
    IDoc-XI-File scenario
    File -> IDOC ref:
    File to IDOC
    To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
    You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
    Also, I would suggest that you go through this blog by michal if any issue arises,
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    I hope this answers your query.
    Award the POINTS if it is useful **
    Cheers
    Vasu

  • IDOC -- File:(R/3-- XI) : Idocs not reaching XI. Where to check for error

    Hi,
    I have completed the config for IDOC to XI (R/3-->XI) scenario based on various weblogs available on Sdn.
    For testing, I am using we19 to trigger the outbound idoc from R/3. But when I look in IDX5 in XI or message monitor, I do not see any message or IDOC there. Even SXMB_MONI in XI does not have any message.
    What could be the potential issue for this behaviour. Is there a way where I could debug or any steps that could tell me where to look for the error.
    So far only odd behaviour I have observed is:
    When in WE19 I trigger the IDOC for outbound processing, XI login screen pops up, where I need to enter password. Once I click enter the screen disappears and the message, IDOC sucessfully sent to external system/Port appears.
    Appreciate your help.
    Thanks
    Shirin

    Hi,
    I checked SM58 and teher indeed are errors saying
    "Name or Password is incorrect (repeat logon) "
    So which connection is having incorrect password in SM59?
    I checked and I have a working RFC connection  (TYpe 3) in SM59 for XI.
    Just to add TCP/IP connection(Type T) has 2 connections not working. They are LCRSAPRFC and SAPSLDAPI.
    So what should be my next step in correcting this error as I am not sure which RFC connection user-id is responsible for SM58 errors.
    Any feedback is welcome.
    Thanks
    Shirin

  • IDoc to XI u0096 Outbound IDoc

    hi Experts,
    Please let me know how to post IDOC to XI in R/3 Sender System?
    Please help
    Sourabh

    Hi,
    WE19 is the testing tool for the INBOUND and OUTBOUND Idocs,it will not post the data into XI.
    What type of idoc ur using,To post the data into XI u have to trigger the IDOC in the transaction.
    Suppoce u have to post the production order details then u have to go to  CO02 TC code there u have to give the production order details and release the IDOC .
    Before  release the IDOC make sure u have done the ALE settings then the Data will be posted into XI.
    Chech the ALE settings.
    IDOC
    http://msdn2.microsoft.com/en-us/library/ms942196.aspx
    Idoc configuration Required~
    in R/3
    1) RFC destination pointing to XI
    2) WE20 Partner Profile entries
    in XI
    1) RFC destination pointing to R/3
    Go thru this -
    configuration steps for receiving idoc in xi from r/3
    Go thru these for Idoc to XI scenarios-
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    These will be the Configurations needed in your R3,
    1. SM 59 - Create an RFC destination for your XI .
    2. We21 -- Create a port for XI
    3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
    Configuration on XI
    1. IDX2 - Import IDOC metadata.
    For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
    In XI :
    Step 1 : In SALE Tcode :
    a)Create Logical systems for R/3 and XI.
    EG : (QZACLNT100) and (X7ACLNT100).
    b) Assign the logical system of XI to Client.(X7ACLNT100)
    Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
    Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
    Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
    In R/3 :
    Step 1:
    In SALE Tcode :
    a) Create Logical systems for R/3 and XI for
    b) Assign the logical system of R/3 to Client.(QZACLNT100)
    Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
    Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
    a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
    b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
    c)In Menu Bar EDIT->Generate Partner Profile.
    Click on that and press Execute .
    This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
    d) Click EDIT->MODEL VIEW->Distribute.
    This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
    This configuration shall surely help u out as it worked out for me.
    Configurations required for IDocs in R/3
    In your XI system, you need to do the following.
    1. Create a RFC destination to your R/3 system
    2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
    3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
    4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
    5. Import the business system and you can use it in your configuration scenario.
    Please also refer below links for details.
    Go thru this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    SAP R3 ->Legacy system including master data using XI
    Regards,
    Phani

  • Outbound idoc has data from previous idoc as well

    Hi Experts
    I am doing the goods receipt against a scheduling agreement using idocs. If this goods receipt is succesful, I am triggering an outbound idoc informing the WMS of the goods receipt. For example, if idoc number 1 comes in for GR , code has been mentioned in the inbound function module for trigger of an outbound idoc A. Please note that the difference that this isnt the case of an output type.
    Now the problem that arises is , the idoc data for outbound idocs is being accumulated and sent. For example, if 1 is the GR idoc, A is the outbound idoc, then 2 is the 2nd GR idoc, then AB is the data coming  2nd outbound idoc (instead of just B), then 3 is the 3rd GR idoc, then ABC is the data coming  for 3rd outbound idoc(instead of just C)
    I am a little confused about the same as to which area this pertains to and would really appreciate quick help on the same.
    Regards
    Shubhankar

    Hi,
    How are you testing this functionality ? Is it using WE19 test transaction or ??
    If that is the case then please come out of transaction everytime you process the idoc.
    Also, clarify your scenario in more detail.
    Processing of your single inbound idoc creates more than one outbound idocs or
    for every inbound idoc which is processed you are creating one outbound idoc in user exit.
    Also check if the idocdata internal table is refreshed once an outbound idoc is created.
    If possible please send your code.
    KR Jaideep,

  • FM to get IDOC number of the created IDOC

    I am creating the idoc using FM -- >MASTER_IDOC_DISTRIBUTE
    If Idoc is created successfully I get sy-subrc = 0.
    If sy-subrc is 0 .... I need to fetch the Idoc number...
    I need a FM that will return the appropriate idoc number...
    thanks
    Warm regards,
    Karen

    Hello,
    try this FM "IDOC_INBOUND_SINGLE", this returns the IDoc number.
    Regards,
    Sachinkumar Mehta

Maybe you are looking for