IDOC status 64 not getting processed.

Hi Gurus,
      I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
17.09.2009 19:05:23 Job started                                                                   00           516          S
17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT)      00           550          S
17.09.2009 19:05:25 No data could be selected.                                                    B1           083          I
17.09.2009 19:05:25 Job finished                                                                  00           517          S
Kindly advise on this.
Regards,
Riaz.

When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
1) 18.09.2009 02:00:06 Job started                                             00           516          S
18.09.2009 02:00:06 Logon not possible (error in license check)             00           179          E
18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE      00           564          A
2) 18.09.2009 00:55:27 Job started                                                          00           516          S
18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO)      00           550          S
18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV                                   DB6PM         000          S
18.09.2009 00:55:29 Clean_Plan:beendet                                                  DB6PM         000          S
18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR                                00           671          A
18.09.2009 01:00:52 Job cancelled                                                        00           518          A
This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.

Similar Messages

  • IDOCS Error - Not getting processed automatically

    Hi All,
    We are loading hierarchy for a Product from R/3 system using the standard datasource.
    When we execute the info package, IDOCs are not getting processed automatically.
    We are facing the below error message.
    Error when updating Idocs in Business Information Warehouse
    Diagnosis
    Errors have been reported in Business Information Warehouse during IDoc update:
    No status record was passed to ALE by the applicat
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
    Error handling:
    How you resolve the errors depends on the error message you get.
    But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
    Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
    Thanks in Advance
    Regards,
    Sachin

    Hi,
    This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
    Hope it helps a lot.
    Thanks and Regards,
    Kamesham

  • RSEOUT00 - Idoc not getting processed

    Hi All,
    I have few idocs in prod.system with status 30 and they are not getting processed using RSEOUT00.
    I tried using back ground job / forgrond / BD87 also but they are not getting converted to 03 status.
    receiver port is xmlgen.
    Any thing like idoc lock ? or something other that is preventing it process ?
    Please let me know if anything.

    check out the multiple threads in SDN regarding this issue
    idoc remains random in status 30
    some of the common pointers looks to be locked IDOC (check in SM12), SM58 to see if anything is in the RFC queue (though I doubt that would be the case)..
    How are you generating your idoc? standard FM or MASTER_IDOC_DISTRIBUTE?

  • Idoc in 64 status not getting released

    HI experts,
    I have inbound idocs in 64 status they ar getting processed in a slower speed but i saw that there are few idocs of some previous date whihch are still in 64 status.
    Any idea why they are not getting processed??
    is there any logic which say give priority to current date idocs first????
    all the configuration are in place to make it processe it immediatly.
    i am not able to understand ahy they are not getting processed.
    please guide me.
    thanks in advance

    Hello,
    I have seen these situations in some occasions. These inbound IDOCs are set to process immediately to the application; but at that very moment there are no free processors to handle them.  So they stay in status 64. The work-around is to schedule BD64 to take care of these rare situations.
    Thanks,
    Venu

  • Article IDoc not getting processed in PI for particle article type

    Hello All,
         I have an strange behaviour in my system.
    i.e 1, we are creating an article IDOC by using BD10 for particulat article type.
    2, IDOC created succesfully , then
    3, Process the IDOC in BD87 to push the IDOC to PI system .
    4, But i could not see the message in PI that too only for one article type.
    I'm wondering why this is not getting processed only for one article type and not for others.
    we also checked the basic filter for the message type in dist model and even i could not see any condition in PI also,
      Is there any thing else i should check? can you please help us on this.
    Regards , Sethu.

    Hi,
    Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.
    EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
    IDoc 0000000000181226 was saved but cannot or should not be sent
    Regards,
    Priyanka

  • Automatic update of number ranges in FBN1 is not getting processed

    Automatic update of number ranges in FBN1 (current status) level is not getting processed.
    Tried posting a customer payment document in the system though number ranges are maintained for the year 2015 the number ranges are not overlapped last year all documents are closed but still the numbers are not been picked automatically in FBN1 kindly help in this issue

    Hello Rajesh
    Please verify if number ranges are maintained correctly, verify same using transaction OBA7. Also ensure that external assignment is unchecked in FBN1. Share screenshots if possible.
    Regards
    Aniket

  • FI - Interface triggerring multiple idoc is not getting posted

    Hi all,
    I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
    now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
    But the same idoc, when i proccess indivisually get's process gets posted successfully.
    I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
    As an abaper, I am not able to understand problem to take corrective steps.
    Thanks & Regards
    shashikant

    hi,
    if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
    please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
    let us know.
    Rodrigo P-.

  • For the new delivery type created the Idoc is not getting triggered

    Hi All,
    I am facing the following problem:
    For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
    Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
    The Idoc being used is:   DESADV01
    Message type :DESADV
    Thanks,
    Geeta

    I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

  • Savings Plan Contribution is not getting processed in Payroll

    Hello Friends,
    We are in the process of upgrading our system from 4.0 to 4.7, After correcting the schema as per the release/OSS notes, we are getting Savings Plan Contribution as blank (Retirement Savings).
    Cumulation values are coming thru right but current period contribution is missing.
    Earlier we had P0169 with P61, now we do not see processing class(PCLS)61 in the PCLS list. Our earlier wage types were referring to PCLS 61, I am not sure if this is causing an issue.
    Please let me know if you have any faced similar situation and have an answer.
    Thanks & Best Regards
    ravi

    Ravi,
    Appriciate if you could share the solution for your problem in savings plan contribution is not getting processed in the payroll. As I am facing the same kind od problem for my new configured benefit plan ROTH 401k plan.
    Please let me know the solution.
    Thanks & Regards,
    Sunita

  • Bulky Message are not getting processed

    Hi All,
    Recently we have upgraded our XI systems to EHP4.
    After upgrade Bulky files are not getting processed into XI system. Small files are getting processed successfully.
    Earlier we had faced same issue at that time we have maintained some parameters in transaction RZ10, RZ11, SXMB_ADM-->
    Integration Configuration--> HTTP time out parameter.
    Same parameters are still there. But now the message is not getting processed in XI when we check into sxi_monitor. Message mapping is also not seems to be a problem as we havnt put any bulky logic over there.
    The message is not getting processed ahead of  Receiver Grouping .  Please find attached log from Performanceheader
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Grouping
      -->
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134229.930472</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="evoxicqab">20091210134232.052577</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134232.059576</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="evoxicqab">20091210134232.07151</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134232.071518</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="evoxicqab">20091210134237.239947</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134237.241179</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="evoxicqab">20091210134237.250385</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134239.999045</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="evoxicqab">20091210134240.001292</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134240.001413</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="evoxicqab">20091210134240.026156</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="evoxicqab">20091210134240.026164</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>

    Hi
    Have you checked this thread, same discussion here
    Performance of XI Interfaces
    Also check this blog
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Regards
    Ramesh

  • Entry not getting processed

    I have an Non recurrening Multiple Entries allowed element to an assignment which is not getting processed when i run payroll.
    Please help
    Thanks

    This is to ensure that results generated by the future payroll runs are correct. Lets take a simple eg.
    You have a pension element which would be 10% of Gross Pay_YTD.
    Run Payroll for Jan (Gross Pay) = 1000 -> Pension = 100 (10% of 1000).
    Run Payroll for Mar (Gross Pay) = 1000 -> Pension = 200 (10% of 2000).
    Run Payroll for Feb (Gross Pay) = 1000 -> Pension = 200 (10% of 2000 as _YTD of Feb does not account  March figures).
    In the above case the Payroll Run results generated by March would be incorrect.
    So once you run Payroll for March, you can not run payroll for Feb. If you require any additional payments to be made in Feb (after Payroll for Feb and March are processed), you can run Retropay to bring forward the entries to next Open pay period.

  • System status not get updated.

    hai any one can help me in this pls
    my client created sevice orders in crm system and in these some details are reflected in to mobile client.There is integration between in CRM & Mobile clients.
    present requirement is system status is not get updated.
    user status is released.but in system status showing like 1) open  2) contains error. This is occure for some sevice orders  which are created in perticular transaction type  for suppose if my client created 1000 service orders in that 200 or 250 orders status not get updated.
    Because of  this the followup document is not created.
    For temparary pupose to overcome this issue we are doing like this. There are two mandatory fields are there in that any one delete and reenter the same value then automatically the system status get updated in to release status.
    where the problem whether  is in configuration or it is in system
    or it is some technical. Before its worked properly recently they got this issue. How can i overcome this issue permanently.

    Hi
    The status of a sales transaction, saved in CRM Enterprise must be without errors so that it can be transferred to the mobile client
    Sales transactions with errors can be transferred from the mobile client to CRM Enterprise.
    Check the table CDBD_STATUS
    Reward with points if helpful
    Regards
    Manohar

  • Data packet not getting processed

    Hi SDN's
    I m loading data from one ODS to 4 regions , the source ODS is successfully loaded from der to the data targets the load is getting failed or taking loang time .
    upto transfer rules the data is successful, in update rules data packets are not getting processed
    kindly suggest solution, points will be assigned
    thx in advance

    Hi Katam,
    In the target ODSs go to the monitor screen for a particular request -> in the menu bar go to environment -> transactRFC-> in the datawarehouse -> give the ID and date -> execute.
    Check if there are entries in that. Usually this queue will be stuck and you need to execute the LUWs in the queue manually.
    if it says transaction recorded u need to execute it manually
    Please revert if any issues
    Edited by: Pramod Manjunath on Dec 19, 2007 4:48 PM

  • ALE - Idoc not getting processed automatically, instead going fine in Debug

    Hello All,
    I have a problem with Inbound idoc processing.
    IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
    The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
    Can some body help me with correction step or sequence of steps  for this ALE process.
    Thanks & Regards, Jilan

    Hi Jilan,
    Plz follow the steps:
    ALE Configuration:
    •     WE30 - IDOC type creation
    •     WE31 - Create segment
    •     WE81 - Message type creation
    •     WE82 - Link IDOC type to Message type
    •     SE37   - Create Inbound Function Module
    •     BD51  - Maintain entry for Function Module
    •     WE57 - Maintain
    •     BD57  - Link Function Module, IDOC type and Message type
    •     WE42 – Create Inbound Process Code
    •     BD67  - Link Process code to Function Module
    •     WE20 - Create Partner Profile
    •     BD64  -  Display Distribution Model
    •     WE02 -  IDoc List, Display all Inbound/Outbound IDocs
    •     WE14 -  Outbound Processing of IDoc’s
    •     BD20 -  Inbound Processing of IDoc’s
    1st Step:   Create  a Segment  ( WE31)
             Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it.  But, to actually use this Segment, you have to Release the Segment, otherwise u can’t use the Segment, by menu, EDIT--> Set Release.
             Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
    2nd Step:   Create IDOC Type  ( WE30 )
            After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
           Basic IDoc Type:  Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
           Extension IDOC Type:  When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
    3rd Step:   Create Message Type (WE81)
         Message Type is like the Postman for sending the Letter.
      4th Step:   Attach Message Type to the IDOC Type (WE82)
    5th Step:   Create a Function Module (SE37)
           Write the Processing logic in a Function Module.
    6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
    7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
    8th Step:   Create a Custom Process Code (WE42)
    9th Step:   Attach the Function Module to the Process Code (BD67)
    10th Step: Execute Inbound IDOC’ s (WE19)
    Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
    reward is useful,
    regards,
    Tanmay

  • Asset - worklist processing status not getting changed

    Hi,
    I created a worklist through Tcode- 'AR01' for processing mass
    retirement of assets.
    I executed the worklist through Tcode- 'AR31', and released the
    worklist.
    The status is in 'In process' is not changing even when I keep on refreshing it.
    The system speed is normal.
    rgds

    Hi,
    The session is not getting displayed in 'SM12' for the basis person to break the session.
    Also the worklist status shows 'IN PROCESS'
    How should I delete a worklist?
    rgds

Maybe you are looking for