IDoc Delays: 64 to 62 status

Hello - We have been seeing some intermittent delays on some of our ORDERS idocs. They are configured to process immeadiately, but we have been seeing some delays when they are going from status 64 (Ready to be Transferred) to status 62 (IDoc passed to application). These delays are sporatic and ranging from 2 minutes to 20 minutes.
Any thoughts?
Thanks - Kyle Winters

Hi,
Are these idocs processed using workflows or ??
Please have a look at following SAP notes.
» SAP Note Number: 160670 Idocs remain in inbound with status 62
» SAP Note Number: 836022 ALE: Link to application log in status 62
» SAP Note Number: 92552 IDocs-Status 62 cannot be processed
» SAP Note Number: 631039 IDoc: Problems with inbound processing using workflow
» SAP Note Number: 194640 IDoc: Workflow is not started in RSEINB00
» SAP Note Number: 181729 ALE: IDocs remain in status 64 / 3.X inbound
» SAP Note Number: 168276 IDocs remain in status 64
KR Jaideep,

Similar Messages

  • RBDAPP01 going into SLEEP Mode and Idocs still in 64 status

    Hey all,
          I have a Inbound Idoc interface which is being processed using RBDAPP01 Program. The Issue I am facing is that the job running the rbdapp01 program goes into sleep mode even though there are idocs present in 64 status. I tried to debug the work process using SM66 but it does not open any debugging window although it says debugging started. If I cancel the Job and run it again it processes those Idocs Any input on how one can resolve this issue?
    Thanks.

    Hi Aparna,
    Here is extract from SAP material on running RBDAPP01 transaction and possible reasons for delay in processing. HOpe this can help you.
    To automate the treatment of IDocs, you must run the ABAP program RBDAPP01 (transaction BD20) in job. This program has a very good option for parallel processing which can reduce a lot the time required for treatment. However use it carefully and make sure you set a packetsize high enough to avoid that your SAP system be overwhelm by demands for available dialog tasks (don't forget one dialog task is monopolized per IDocs packed to treat).
    Best Regards,
    Krishna

  • IDoc Acknowledgement to JDBC status update

    Hi,
    JDBC --> XI --> SAP R/3 (IDoc ACC_DOCUMENT02)
    JDBC <-- XI <-- SAP R/3 (IDoc ALEAUD01)
    I have the following scenario... I am reading data from a database using the JDBC Adapter. The data is in the following format at source. Using the JDBC adapter I read the database for rows for which the status is blank, this is multiple documents.
    Invoice 1 Status 53
    Invoice 1 Status 53
    Invoice 1 Status 53
    Invoice 1 Status 53
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 3 Status <blank>
    Invoice 3 Status <blank>
    Using a BPM process I split the source data into multiple messages and map them to the IDoc structure. In the above example Invoice 2 & 3 would be read from the database and split into 2 individual IDocs to be posted separately into SAP.
    IDoc 1
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    Invoice 2 Status <blank>
    IDoc 2
    Invoice 3 Status <blank>
    Invoice 3 Status <blank>
    I now want to extend this scenario to include acknowledgement messages which I can use to update the status in the source system.
    I have configured the ALEAUD01 message in the destination system and scheduled the RBDSTATE program to run periodically. I can see in the XI message monitor that my messages now have aknowledgement status.
    What I would now like to do and hopefully someone can help is to use the status information being fed back from SAP in the ALEAUD01 message to update the status field for individual lines in the source table. Can anyone help with this step???
    Regards,
    Pete

    I can see the limitation of ALEAUDIT as it is handled internally in XI. Using the bespoke route I can create a copy of ALEAUDIT and a bespoke IDoc ZALEAUD01 for example, which will send the status idoc to XI.
    In BPM I can configure a receive step to receive the IDoc... But, how do I then relate the IDoc I created to the particular segment in my ALEAUD01 IDoc.
    Regards,
    Pete

  • IDOC is created with status 51( application document not posted)

    Hi experts
    iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
    but the IDOC is created with status 51( application document not posted)
    the details error shows:
    An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
    during a synchronous update.
    The error was caused by the transaction VA01.
    previously i used same test data that time it was working fine,
    please tell me how can i fix the issue.
    regards
    vasavi

    Key in your Idoc number in BD87, execute
    select the error message and then follow the menu path :
    EDIT --> restrict and process  (Select)
    In the next screen UNCHECK the Bkgd Processing and execute
    Now EDIT --> Process --> foreground from error or in foreground mode.
    This will lead you the screen where it errored out.
    Thx
    PSR

  • Inbound IDOC Mass processing - No status message

    Hi Friends,
    I am updating a database table using inbound IDOC. But in batch job when XI passes multiple IDOCS,
    for some IDOCs there is no status message even though i coded for status message.
    If i rerun IDOC in BD87 then it work fine.
    please help.
    regards,
    madan

    Hi Madan,
    Since you are loading multiple idoc to the system due to high load in the production system data is not commiting properly. So use external commit work statement in you code. this will reduce the performance but logic will work.
    COMMIT WORK [AND WAIT].
    Effect
    The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
    It executes all subroutines registered using PERFORM ON COMMIT.
    The sequence is based on the order of registration or according to the priority specified using the LEVEL addition. Execution of the following statements is not permitted in a subroutine of this type:
    PERFORM ... ON COMMIT|ROLLBACK
    COMMIT WORK
    ROLLBACK WORK
    The statement CALL FUNCTION ... IN UPDATE TASK can be executed.
    Triggering an internal event for the Persistence Service of the Object Services.
    If event handlers are registered by the Persistence Service, these collect the changes to the objects managed by the Persistence Service and transfer them via CALL FUNCTION ... IN UPDATE TASK to a specific update function module that is registered as the last update module.
    This executes all high-priority (VB1) update function modules in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
    When all high-priority update function modules are completed successfully, the statement executes the low-priority (VB2) update function modules in the order of registration together in a common database LUW.
    After the execution of high-priority update function modules, the individual function modules registered using CALL FUNCTION ...IN BACKGROUND TASK|UNIT are executed in a separate database LUW for each destination.
    Within an update function module started using COMMIT WORK, the execution of statements that lead to a database commit is not permitted. In particular, the following are forbidden:
    Thanks,
    Raghav

  • IDOC adapter message limitation Status 64

    Hello,
    we have implemented an IDOC R/3->XI->R3 scenario.
    Sometimes it happens, that the sending system generates a hugh number of idocs.
    In this case, the IDOCs are posted to the receiving R/3 system, but stay on status 64 which says,
    "...to few dialog processes...."
    So the receiving SAP system has to few processes to start the processing of the idocs.
    But we can no enhance the amount of the processes.
    Is it possible, to limit the calls of the IDOC adapter
    or to schedule the idocs, or to make a package?
    This should be done on XI!!!!
    I have read the QUEUE option, but we are working on 4.6BASIS, so this did not solve the problem.
    best regards
    Werner

    Werner-
    This situation can be handled using some variations to your suggestion of handling it in XI.
    1) In the Partner profile of the target R3 system, use the option 'trigger by background program' in the inbound parameters. This way, the IDOCs will be created in the database, syntax checked and will be set to status '64' but with a different message (mostly No filters....). At this point, we are not even trying to post the IDOC to the application, which takes the most processing time.
    2) Then in your traget SAP system, schedule program RBDAPP01. There are various options available to restrict your selections. By scheduling this program to run in regular intervals, you can process IDOCs which are in status 64, there by re-processing them if some failed during the last run because of lack of processes.
    Some additional information on performance improvment:
    RBDAPP01 is an interesting program, because it allows you to parallel process the IDOCs plus process them in packets. That is, instead of processing IDOCs one by one, you can make the program to use all the available free processes to process the IDOCs in parallel. This will greatly reduce your processing time.
    If you see, this program has a tab called 'Parallel Proc' (assuming you are logged on in English). You can activate the check box 'Parallel Proc. Active' and choose a 'Server Group'.
    Now, before using this option, you need to understand that this program will occupy all free DIALOG processes. Which means no process will be available for users to log on (even admins) while the program is busy posting IDOCS. However, this limitation can be overcome by fixing a system parameter on the server group which will limit the number of processes to be used by this program. For e.g., in one of my implementations, we set up the profile parameter in such a way that out of 13 dialog processes available, the program will always leave 5 processes free thereby occupying only seven free processes max.
    This setting was done by the basis team and probably you or your basis team already know about it. If not, let me know, I will try to find it out from our guys here.
    Hope the above explaination help. For more information check note 399271 and other related notes for RBDAPP01 PARALLEL PROCESSING.
    KK

  • 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.

  • Batch job for IDOC processing in 64 status

    Hi experts ,
    i want to know the name of Batch job for IDOC processing in 64 status.
    I have configured the partner profiles as 'process immediatly'.
    So with this configuration whenever an idoc comes in production it gets processed immediatly and automatically.
    i want to know how they are getting processed automatically.
    is there any job which looks for these idocs(in 64 status and process immediatly flag) and process it.
    What is the trigger for thiese idocs processing???
    Please guide me
    thanks in advance
    Anit gautam

    Hi Thanks for ur reply.
    =====Upon arrival, "process immediately" should fire that process =====
    how it is getting fire?
    means is there any batch job running which looks for idoc in 64 status or is there any event which get triggered when an idoc
    comes in 64 status.
    why we use OYEB transaction???
    Regards

  • Urgent --- How to resend an outbound IDoc which is in status 03

    Hi Experts,
    I've a rquirement to resend an outbound IDoc which is in status 03. I don't want to use BD87  or WE19 to reprocess.
    Please provide me some FM or some technique by which I may use in a Z-program to accomplish the above requirement.
    Even if IDoc no is changed....that won't cause any problem....i just need to resend the IDoc.
    Thnx in advance
    Rudresh
    Mumbai

    Test: Outbound Processing from IDoc
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated, to allow the test program to intervene. You can make sure that this is the case by setting the output mode to "Collect IDocs" in the partner profile for the IDoc interface. If you now generate an outbound IDoc for the partner (for example, via the application or the test tool), the IDoc is only generated in the R/3 System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report
    RSEOUT00, which is also generally scheduled with the output mode "Collect IDocs" in live operation. 
    Activities
    Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
    You can decide whether the output mode is set to "Start subsystem" or "Do not start subsystem" in the partner profile. This defines whether the external (sub) system processes the IDocs further.

  • RSEOUT00 - ECC 6.0 IDOC Dispatch Error.  Status 30 goes to status 02

    After our Unicode conversion to ECC 6.0, we started to get some IDOC processing going from status 30 to 02 and not dispatching to our EDI provider.  We noticed it is on the PO Long Text or any of the Text fields for that matter where somebody has Cut/Paste Text from Word/Excel/Outlook document and they are using colors/fonts/bold, etc.  We've also noticed it on our MAKT table on the description.  You click on the Text and can see it outlines extra characters beyond the end of the visible text.  When RSEOUT00 gets a hold of these PO's, it won't dispatch them.  If we go back and erase the text and type it all in by had and save and close our PO Version change, it dispatches, pulls and loads now to our EDI provider.  Looking for some setting that allows us to maybe turn this feature off?  maybe it has to do with CodePage defaults, etc.  I saw once were you could tell SAP to save documents in Office 2007/2010 version instead of Office 2003 but don't remember which OSS note that was.

    Try to use "Line Editor' or 'Sapscript Editor' instead of  "Continous Text Editor". You will find these editor options below to the text fields in text maintenace tabs. Hope this helps.
    Regards,
    Gokul

  • Error in Idoc...(status 26)

    Hi All
    when  i see the idoc in WE02 t-code ,the error occured.
    Error during syntax check of IDoc (outbound)
    Status : 26
    Internal error occurred reading structure of segment .
    I am using ztable for data reading..
    Regards
    lakhan

    hi lakhan,
    Go through the following Steps for Creating IDoc Via ALE
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    <b>Regards,
    Azhar</b>

  • How to trigger an Outbound IDOC with a default status 68

    Hi,
    How an Outbound IDOC can be created/triggered with a default status 68??
    I have a requirement where the outbound IDOC should always get created with status 68. Once an Outbound IDOC is created, I should not be changing its status manually or using a program.
    Basically we don't want any IDOCs created in other status and changing to 68 once an IDOC is created with a different status.
    Currently i'm using fm 'IDOC_OUTPUT_DELVRY' to trigger an outbound idoc, and the idocs are triggered with different status 30, 2, 3 etc... By using a program i can change the status of the IDOC. But what we need is "Whenever an outbound idoc is triggered, it should always have status 68".
    Please let me know the ways to achieve this functionality.
    Thanks!

    Hi,
    We need to display all the IDOC data on a Smartform layout. But we dont need the IDOC to be used for our requirement. So we want to make sure that IDOC is triggered but will not stay in 02 or other status.
    We have a process to monitor the failed idocs (02 status) and we do not want our idoc to have failed status. So we need the idocs to be tirggered directly with status 31 (thanks for letting me know that i cant use status 68 for outbound idocs).
    Thanks!

  • Unable to post the Purchase Order inbound idocs which are in status 64

    Hi
    While Processing the inbound idocs which are in status 64 for message type: PORDCR i am getting the
    idoc into error status 51 saying the error as "Missing authorization: Purchase Order Create Purchasing Grou V10"
    We are getting the inbound idocs from third party and we need to post these idocs in production.
    Can any one help me out how to proceed further on this.
    Thanks in Advance
    Regards,
    Phani Miriyala.

    Hi
    Thank you very much for your quick response.
    As the same user is able to process the idocs of message type PORDCR which are in status 64 successfully previously.
    Regards,
    Phani Miriyala.

  • IDOC not coming in status 30 for collecting idocs

    Hi All,
    We have a requirement in which we need to collect idocs and send together.
    To achieve I am making Collect idocs in Partner profiles so that it goes in status 30 and hence I can run program RSEOUT00 to make it status 03 and hence write in file as a group of idocs.
    Now inspite of making collect idocs in partner profile, its not coming in status 30 but directly coming in status 03.
    Please let me know what may be the reason for the same.
    Thanks,
    Vivek

    Hi vivek,
    If you have set the Collect Idoc option in partner profile then the IDOC's will be collected , irrespective of kind of port you are using and the packet size doesn't matter in this case.
    It seems to me that the program RSEOUT00 is already scheduled in your system.
    Can you check in SM37 , by putting the program RSEOUT00 and check if any user has scheduled the program.
    Hope this helps.
    Harry

  • IDOC  Delayed in SAP to XI

    Hi Gurus ,
    An IDOC is resent and there is a delay from SAP to XI changing sales order .
    Pls tell me a valid reason for this .
    Thanks in advance

    Hi,
    It might be possible that due to the large generation of the IDoc, the standard jobs might not picking up the IDocs within the scheduled time due to which  their might be a delay.
    Thanks
    Krithika

Maybe you are looking for