IDocs in WEOUTQUEUE not processed

Hi all,
I have a problem with IDocs' serialization. I want to send IDocs of specific message types via IDoc outbound queue (trans. WEOUTQUEUE) .At sender system side in outbound partner profile (WE20) I configured IDoc to be send by Queue Processing with rule "constant:ediqueue". IDocs arrive to queue in WEOUTQUEUE, and here the problems begin:
1. Processed messages stay in queue - why?
2. If I send 1 IDoc it's not sended automatically, I have to activate queue in order to process it. It ried to use report RSEOUT00,but it only shows how many IDocs ready for processing and doesn't send them - how can I configure automatic processing of Idocs in queue?
3. If I send (with WE19) more then 1 IDoc at once, thay are automatically processed, but in XI in SXMB_MONI i see that they are processed by random QRFCs and are not serialized.
Can anyone please help me to work it out?
Thanks!
Anna.

We are having a similair issue.  I have IDocs outbound from R/3 to XI.  The Idocs are setup as "Queue Processing" with "Transfer IDoc Immed" option in the WE20 partner profile for EOIO processing.  I usually have no problem all day long but every night right after midnight all the Idocs remain in a status 30.  I have to use WEOUTQUEUE to activate the que or BD87 to release them.  Once I do this, all IDocs moved along successfuly except every once in awhile during the middle of the day they go into a status 30 and remain there.  I did notice the difference between the Idocs that work and the others that get stuck is the there are 2 entries for status 30 when viewing the IDocs in WE02.  Here is what they look like.  IS this simialiar to your issue?
03 - qRFC used to send IDoc to SAP system  (I get this once I releaqse them manualy)
30 - blank
30 - Receiver exists , No filters , No conversion , No version change
01 - blank

Similar Messages

  • Inbound Idocs are not Processing

    Hi,
    Inbound IDOCS queue is not processing if any one IDOC is showing amber(error) . Please let me know the resolution to avoid this issue or let me know the BASIS setting to avoid it.
    Regards,
    PVK.

    Hello,
    Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
    For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
    For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
    It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
    Help on RBDAPP01
    Regards,
    Sameer

  • IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

    Dear Folks,
    Here we are implementing MIRROR sytem for data extraction in to BIW.
    I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
    These are following steps I had performed in BW production
    1. Using RSADMIN transcation- Assigned one user as a Debugging user.
    2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
        In data selection tab, I given date as from 2002 to 2003
        In Update tab, I selected update mode as Initialize Delta process-               without data transfer and Uncheck Update Data in master   system immediately
       In schedule tab I selected option Start Data load immediately then Start extraction.
    3.Data was requested and It was intialized properly with green status 1 from 1 Records.
    4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
    5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
    Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option <b>IDOC list in Source sytem</b>, here also it is not showing any IDOCs.
    Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
    Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
    Points is Assured for all replies.

    Hi,
    - check you RFC destination (normal test + authorization test)
    - Check you partner profiles in WE20 and its ports WE21
    - from the source system tree (RSA13) right click your source system and perform a check
    - the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
    hope this helps,
    Olivier.

  • Idoc in 53 status but not processed completely. Missing authorisation error

    Hi ,
    Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
    They got below warning message when I checked in WPER transaction code.
    " Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
    This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
    These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
    Thanks
    Deepthi.

    done.

  • Idocs neding in 64 status and not processed further

    Hi
    We have inbound idocs of FIDCC2 message type, which are set to be triggered immediately. However we have noticed that sometimes (not always) these idocs are in 64 status and are not processed further. We have to manually reprocess them.
    What could be the problem? Where should we start investigating?
    Any help would be appreciated.
    Thanks
    Mick

    I think the comment by Gautham Vangaveti  is probably correct.
    We hit the same issue occassionally.  We have IDOCS as trigger immediately, but at the time they try to process, there are no available work processes which can handle the IDOC and they sit at status 64.
    There is an oss note 1333417 which describes the situation
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1333417
    And unhelpfully suggests changing over to processing by batch job, which is not always appropriate.
    It may be worth enlisting help from you Basis team to try and indentify if those going to status 64 are occuring at the same time each day, and maybe looking to see what other processes are running at that time.  If the load on the system can be managed then the problem may go away, it did for us.
    Otherwise, Basis may be able to increase the number of work process which may also resolve the issue.

  • Idocs are not processed in the right order.

    Hi,
    I face a problem that when there are a large number of IDocs (Inbound) posted the Idocs are not processed in the right order.
    Msg type: MBGMCR
    any idea how this can happen?
    what is the solution?
    br
    Karen

    No answer

  • Report RBDAPP01 not processing IDocs in status 51

    Hello guys,
    I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
    Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
    In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
    There is no parallel processo to avoid the locks.
    Do you know how we can solve it?
    Many thans in advance.
    Regards,
    Xavi.

    i do have the same problem. is there an solution to this?

  • Idoc in 53 status but not processed completely.

    Hi ,
    Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
    They got below warning message when I checked in WPER transaction code.
    " Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
    This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
    Any idea what might be the reason? 
    Thanks
    Deepthi.

    Hello,
    This seems to be an Authorisation issue, Kindly check for Purchasing Group 110, who are all assigned Buyers...
    Then for those Buyers.. you can check what authorization is missing from Su53..
    Compare with those who has authorisation to create PO Vs who does not have ..
    you will have to provide the same authorisation to those users
    Thanks and regards
    PJ

  • IdocReceiver not processing all the idocs produced from PFAL in OrgModeler

    Dear experts,
    We are on below Nakisa version.
    Name Nakisa OrgModeler
    Version 4.0 SP1
    Build 0910021700
    I ran the initial load for the OrgModeler and it produced around 500 idocs. When I followed the command line interface, it processed around 56 idocs. The idoc status becomes 03 (Data Processed to Port OK) at the R/3 end for all the idocs. However idocreceiver is skipping many idocs in between and processing only few. I checked the database for HRP1000 and HRP1001 and the records loaded are not even 20% of the records in R/3 for the objects and relationships(HRP1000 obj types C, O, Q,S and HRP1001 002/003/007/008/011/012 etc) we filter at the distribution model.
    I think  the issue might not be an authorzation problem as its fetching the records from SAP R/3 and loading few records in the database.
    I checked with my Basis consultant about another reciever running and grabing the missing records. He confirmed that only one idocreceiver running at nakisa end. I even happened to check the SAP gateway server(SMGW) and with TP Name NAKIDOC and symbollic destination NAK_RFC_DEST I can see only one record which is appearing on and off. When the record appear on the gatway server, the corresponding idoc being processed at command line interface. Till the other record appears on the sap gateway server, the idocs are missing at the command line interface.
    Below is the screen shot from idocreceiver. (After the idoc 1695358 it processed 1695366 then 1695372 etc)
    Any suggestions would be a great help.

    Dear All,
    My Basis guy finally realised that he started a Jco provider at the netweaver end and causing the issue. He stopped it and all the idocs processed successfully.
    I learned the below points and might useful for few folks.
    1.No idoc being processed and all the idocs failing with 'Bean IDOC_INBOUND_ASYNCHRONOUS not found on host'. It should be an authorization error and assigning the Authorization Object: S_IDOCDEFT (EDI_TCD = "WE30"; ACTVT = "03") will resolve the issue.
    2. Few idocs are being processed at idoc receiver end.
    i. Check for multiple idoc receivers which might be active and running.
    ii. Check the number of connections and timeout parameters and set them to the maximum.
    Thanks,
    Manohar

  • RBDAPP01 is not processing Idoc's

    Hi,
    We are facing an issue that the RBDAPP01 program scheduled to process inbound Idoc's is not picking Idoc's for posting and running for ever with out processing Idoc's.
    Please let me know what could be the reason for this kind of behavior.
    Regards,
    Cheritha

    Hi ,
         Check your idoc is in 64 status ? If it in 64 process then process with RBDAPP01 in background or Put that idoc in BD87 and process in foreground.
    Thanks,
    Asit Purbey

  • IDOC number is not in the list

    Hi,
    I am creating an inbound delivery using IDOC. The message type is DESADV and basic type is DELVRY01. After I have populated the control and data tables, I processed them using IDOC_WRITE_AND_START_INBOUND. I have generated the IDOC number after executing the program. The problem is, when I go to WE02, the idoc number is not the list. I am not sure if the IDOC I generated is successful or not. Does it have something to do with the FM that I used. I set a custom process code that will call the FM IDOC_INPUT_DESADV1. Please advise. Thanks in advance.
    Lalyn

    Hi Arun,
    Thanks for the reply. But the IDOC number is not in the list and I can't access it WE19. Do you have any other Function module that I can use to process the IDOC in ABAP? The Function module should be the one to call the FM IDOC_INPUT_DESADV1 to create an inbound delivery. That's what I think causes the error. Thanks.
    Lalyn

  • IDoc type could not be determined for the IDoc in F110

    Dear All,
    The below mentioned error is encountered by us in F110.We have check all the setiing  and not able to find the solution for this error.
    Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
    The system is not creating the IDOC file.....
    IDoc type could not be determined for the IDoc
    Message no. B1090
    Diagnosis
    The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
    The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
    The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type  from field DOCTYP.
    Procedure
    Possible error sources:
    - The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
    - The IDoc type  is not known in your system and must be maintained.
    Kindly do the needful.
    Regards

    If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
    see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

  • IDocs sent to XI, processed only some, others in status Scheduled for o/b..

    Hi guys!
    We have a scenario, where Idoc is sent from r/3 into XI, here enters integration process, where the idoc is mapped to soap req, sent sync to web service, ws response is mapped to other idoc type and integration process sends data to r/3.
    The problem is, when more idocs are sent into xi from r/3 in short time. Some idocs are processed correctly, but some remain in status - Scheduled for outbound processing. When the same idoc (same data etc) is sent later, separately, the data (process) is processed succesfully.
    Any ideas, what could be wrong?
    Thanx a lot! Olian

    Hi Olian,
    This problem occurs when XI has not received the response from the webservice and it gets timed out.  You can monitor this in RWB - Message Monitoring.
    Have a look at this weblog
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Hope this will help you in resolving the issue.
    Regards
    Sreenivas

  • File to idoc scenario error - not working yet :(

    Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01
    I have an error 56 EDI: Partner profile not available.
    In Control record in we02 transaction, I have right Partner number for Recipient information - logical system name like CRM has in SLD.  But there is no Port.
    In Sender information I have right Partner number, like my filesystem business system has in SLD and have a port SAPP1D - but  I have nowhere entered it!
    And one more little question. In we20 transaction am entering inbound parameters for partner:
    CRMXIF_PARTNER_SAVE
    CRMXIF_PARTNER_SAVE_M
    1) Is this right inbound parameters for my idoc?
    2) What Process code should I use ?

    Hi,
    in XI in IDX1 transaction, maintain a port for CRM system specifying the CRM port and the client and the RFC destination from XI to CRM system.......moreover if you are using apply control record values from payload option in reciver IDOC comm channel, then in the IDOC control record in msg mapping map the sender port to CRM port, partner number as logical system of CRM ie C2DCLNT100 and partner type as LS..........then when you will re-run your scenario, your IDOC will have CRM port also in the control record..........
    in CRM system your WE20 for LS for XI should have as an inbound parameter your IDOC - which i think you have already done.........
    One more thing - put everything in uppercase letters everywhere in msg mapping in control record data, in we20 setting etc.
    Regards,
    Rajeev Gupta

  • Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

    Hi All,
    We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP  Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

    Hi,
    Both the sender and receiver IDoc transmission is done by the RFC communication channel.
    In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
    However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
    Hope this helps...!!!!
    ~SaNv...

Maybe you are looking for