Inbound IDOC status is strucked at 64

Hi,
My rerequirement is as follws.
Inbound IDOC process:
Through inbound IDOC i have to create the new sales orders and need to change some information to existing sales orders means 2 cases.
1) Create new sales order
2) Change existing order.
Iu2019ve generated two example IDOCs from order interface
one for an u2018order addu2019 and one for an u2018order changeu2019.
The times each IDOC reached each status are shown below:
IDOC 1677672 u2013 Order ADD
Status: 50 Started         Time:    09:54
            64 IDOC ready               09:54
            62 Direct Call                 10:39
            53 Order Created           10:39
IDOC 1677684 u2013 Order CHANGE
Status: 50 Started         Time:    12:50
            64 IDOC ready               12:50
            62 Direct Call                 12:50
            53 Changes on Y-table   12:50
Can anybody explain why the first IDOC had to wait for the scheduled
u2018IDOC PROCESSINGu2019 job to run, before it moved from status 64 to 62. But
the second IDOC appears to have been processed automatically without
waiting for the next run of the scheduled job?
Obviously, the u2018automaticu2019 processing of the change IDOC is the way we
would prefer it to work all the time).
Can any body explain in first case why it's taking time and in second case it's processed immidiately.
Regards,
Janardhan

Hi,
I believe you are using two different message types for this purpose. One to create order and one to change order. Did you check the partner profiles for these? May be partner profile(WE20) for creating order is set as "Collect Idocs" whereas the partner profile for the message type to change order is se as "Trigger immediately".
Hope it helps.
Regds,
Rudra

Similar Messages

Error Inbound IDoc - Status 51

Hi,
i am new in working with SAP and I am trying to integrate an inbound IDoc type WPUBON via WE19 transaction, l solved all the issues related with ports and partner profiles(they were the first errors). But when I want to check if the process has been done well with the WE05 transaction I get two error messages, both of them with status 51:
The transactions for intermediate document 0000000000052247 could not be written
Message no. /POSDW/INPUT004
Document flow: Error reading model data of object relationship se
Message no. /POSDW/CORE028
Diagnosis
Error reading model data of object relationship se
System Response
The document links could not be updated.
Procedure
Contact your system administrator.
Procedure for System Administration
Check the format of the document links transferred to the POS Workbench.
Thank you very much in advance!!
Best regards,
Ander
Edited by: AAnder on Nov 3, 2010 11:46 AM

General process for a correct IDOC infrastructure is:
Create RFC destination --> SM59 (You can point to local machine for tests)
Create RFC port to process IDOC --> WE21 with the RFC create before
Create FILE port to process IDOC --> WE21
Create LOGICAL SYSTEM (BD54) --> IDOC2FILE
Define partner in WE20 with partner type "LS" --> WE20 ... add message
RECEIVER port ( created in WE21 )
FROM WE19 GENERAte IDOC with LOCAL SYSTEM as sender And FILE PORT as receiver
WE19 is FOR TEST...
tell me if you can understand, sorry for my english ....

Inbound Idoc Status

Hi Gurus,
I have Inbound Idoc which is working fine ,
but it's status is showing
51 Error: Application document not posted.
What does this mean, My Idoc FM is doing all it's part which required.
Can any please suggest me .
Thanks ,
Raj

Hello,
         What you've coded looks good. Another way of error Handling can be found as below. In the below Example, I am validating the Handling Unit Number got from the IDoc.
Validation for Handling Unit ID (EXIDV2 From IDOC) - Begin
CLEAR: i_vekp.
SELECT venum
         exidv
         exidv2
         FROM vekp INTO CORRESPONDING FIELDS OF
         TABLE i_vekp
         WHERE venum NE space AND
               exidv NE space AND
               exidv2 = wa_z1ctrlmm-exidv2.
IF sy-subrc EQ 0.
    DESCRIBE TABLE i_vekp.
    IF sy-tfill GT 1.
      CLEAR: wa_idoc_status.
      CLEAR: wa_vendor.
      READ TABLE i_vendor INTO wa_vendor INDEX 1.
      ws_c_flag             = c_x.
      wa_idoc_status-docnum = wa_idoc_control-docnum.
      wa_idoc_status-status = c_51.
      wa_idoc_status-msgty = c_e.
      wa_idoc_status-msgid = c_msgclas.
      wa_idoc_status-msgno = '004'.
      wa_idoc_status-msgv1 = wa_vendor-v_batch.
      APPEND wa_idoc_status TO i_idoc_status.
      CLEAR: wa_idoc_status.
      Here, I am not updating the IDOC_STATUS directly. Instead, I've taken one Temporary Table I_IDOC_STATUS and finally, after all the Validations are done & all the Statuses are updated in the I_IDOC_STATUS, I am updating the IDOC_STATUS Table at the end of the Function module as below.
IF Err_Flag = space.
    wa_idoc_status-docnum = wa_idoc_control-docnum.
     wa_idoc_status-status = c_53.
     wa_idoc_status-msgty = c_s.
     wa_idoc_status-msgid = c_msgclas.
     wa_idoc_status-msgno = '007'.
     append wa_idoc_status to I_IDoc_status.
else.
     wa_idoc_status-docnum = wa_idoc_control-docnum.
     wa_idoc_status-status = c_51.
     wa_idoc_status-msgty = c_e.
     wa_idoc_status-msgid = c_msgclas.
     wa_idoc_status-msgno = '004'.
     append wa_idoc_status to I_IDoc_status.
endif.
IDOC_STATUS[] = I_IDOC_STATUS[].
ENDFUNCTION.
This is how a typical Error Handling technique should be while processing a Custom Inbound Function Module. At any point in time during the Function Module, catching the Message, either Success or Failure is important otherwise, you may end up posting the IDoc with Status 51 or 62 or 64 Status which doesn't make any sense.
Thanks and Regards,
Venkat Phani Prasad Konduri

Inbound idoc status 62

hi,
am getting the sales order as inbound with status 62.
can anybody reply how to rectify this problem.
but in we19 i have executed privious idocs it will give the status 53,

Hi Sathish,
Please check the following links given below:
IDOC:
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
Status codes:
http://publib.boulder.ibm.com/tividd/td/ITMAN/SC23-4812-00/en_US/HTML/sa51mst256.htm
Regards
Satish

Hii Inbound idoc status

Hii
i have a requirement where when an Zidoc is being process if a certain condition is met we should insert in a custom table and not process the IDOC
What status should i put the IDOC in a sort of stand by process so that the user can process it later on with either BD87 or a FM IDOC_INPUT??
I have try putting in a sort of warning message but neither BD87 or the FM can process idoc with status 52
i have put it status 64 but client won't accept it since he recognise idoc comming from external system as 64.

Hi,
use my form for finishing IDOC processing from the time I did not uses OO...
*&      Form append_idoc_status
*       Create IDOC status record from system message fields
*       This is always the last action for processing one single
*       IDOC
FORM append_idoc_status
USING    ps_edidc        TYPE edidc
CHANGING pt_idoc_status TYPE ty_t_bdidocstat.
DATA:
    ls_bdidocstat TYPE bdidocstat.
* this Routine must be called only once per IDOC
MOVE-CORRESPONDING ps_edidc TO ls_bdidocstat.
* transfer message data
ls_bdidocstat-msgty    = sy-msgty.
ls_bdidocstat-msgid    = sy-msgid.
ls_bdidocstat-msgno    = sy-msgno.
ls_bdidocstat-msgv1    = sy-msgv1.
ls_bdidocstat-msgv2    = sy-msgv2.
ls_bdidocstat-msgv3    = sy-msgv3.
ls_bdidocstat-msgv4    = sy-msgv4.
ls_bdidocstat-repid    = sy-repid.
* update IDOC status
CASE ls_bdidocstat-msgty.
    WHEN 'S' OR 'I'.
      ls_bdidocstat-status = c_idoc_posted_ok.
    WHEN 'W'.
      ls_bdidocstat-status = c_idoc_not_fully_posted.
    WHEN 'E' OR 'A'.
      ls_bdidocstat-status = c_idoc_not_posted .
ENDCASE." ls_bdidocstat-msgty.
APPEND ls_bdidocstat TO pt_idoc_status.
ENDFORM.                    " append_idoc_status
A precondition is that your processing issues a MESSAGE ... INTO lv_dummy with lv_dummy of TYPE STRING.
Regards,
Clemens

Inbound idoc status 53 but nothing is updated in transaction level

Hi All
I am using we19 test tool to process routing idoc LOIROU02 (inbound processing)with some test values. After executing using standard inbound function module in R/3 4.7, I am getting a status 53 ( application document posted). This idoc is used for changing routings in PP module to allocate operations for BOM components in a master BOM material and Group. After processing, I went to routing transaction and checked but nothing is updated for operations. Do anyone knows why then the application document is successfully posted and giving status 53.
Any response is appreciated
Thanks

Hi All,
I am using inbound process code ED00 ( Display using workitem) , Identification TS30200088, with/o Ale service, Processing by task. I get the idoc in my business work place when I execute it through we19. From the business work place inbox, I got to edit idoc and End process for gettign the status 53. I am not sure why it is not updating the DB?
Thanks
Ricky

Inbound idoc status 51.

hi,
   i am using asn 856, inbound delivery,
in segment E1EDT13.
   if the qualifier is 007 , its working fyn.
    if the qualifier is 006, it gives an error msg:
       status code 51(please enter the delivery date or goods issue date).
how should i proceed.

Hi,
Why do you need to populate the value in itab T_DLGN?
This internal table is used in FM GN_DELIVERY_CREATE to create delivery as I mentioned earlier. Please go to an include program LV50SF13 and check the following logic which gives you the error message VL 562.
IF xkomdlgn-lfdat IS INITIAL AND
     xkomdlgn-wadat IS INITIAL.
    PERFORM message_handling(sapmv50a) USING cvbap-posnr
                                              '562'
                                              'E'
                                              'VL'
                                              cvbak-vbeln
                                              cvbap-posnr
                                              space
                                              space.
    gmp_subrc = 4.
Regards,
Ferry Lianto
Please reward points if helpful.

Error in re-processing inbound idocs of status 51

Hi
We are facing problems in reprocessing inbound idoc from BD87 transaction
We have an inbound process code 'STA1' which is pointing to a standard task 'TS30000206'. we have an errored inbound idoc(status 51) of message type 'STATUS' ( standard status change idoc pointing to process code STA1 for a valid port. Whenever we try to process it using BD87 transaction, we are getting errors B1033-'No function module for input process code STA1'.
We dont understand what we were missing. When we try the same for a process code which points to a function module, BD87 reprocesses it correctly.
We tried adding an entry in BD67 with an inbound function module 'APPL_IDOC_INPUT1'. Note that we still had the process code pointing to the same task. This time BD87 reprocessed idoc, but gave 51 again saying that 'Function module not allowed: APPL_IDOC_INPUT1'.
Any pointers or help in this regard will be highly appreciated.

Hi,
Please check IDOC TYPE, MESSAGE TYPE & PROCESS CODE and also check the we30, we42. & try BD87 reprocess of an IDOC.

Transaction to see result of inbound idoc ( XI to SAP R3) ?

Hi,
may i know the transaction to see whether the inbound idoc has created the record ?
i'm sending idoc from XI to ECC.
Farah

Hello Farah ,
You can check the inbound idoc status in R3 using WE02/We05. In case want to do a search on idoc based on the timings , message type , target system etc use WE09 . Do remember to mention the search field like MATNR for material idoc , KUNNR for customer idoc or LFA1 for vendor idoc etc.
Idoc in status 53 means success and staus 51 failure.
Hope that helps!
Cheers
Binoy
Edited by: Binoy Thomas on Apr 24, 2008 7:33 PM
Edited by: Binoy Thomas on Apr 24, 2008 7:34 PM

How to block the status mail for an inbound Idoc to a specific user

Hi,
I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
Thanks,
Santosh

Hi,
I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
Thanks,
Santosh

Inbound IDoc used for updating Sales order status

I have a requirements to set use standard IDoc to send out the Sales order to a non-SAP software as well as receiving Inbound IDoc to update the status of sales order in SAP. Could someone comment on my questions below:
1. What are the difference between all the ORDERSxx Idoc types?
2. What IDoc should be used for Inbound IDoc to update the sales order stataus in SAP?
3. Can the same IDoc type be used for both Inbound and Outbound with only the difference in the segment of Direction?
Thank you. Points will be awarded appropriately for helpful comments.

Hi,
1.Intially standard IDOC types "ORDERS01" is having limited
      segments. After few months the requirement got increased to
      add more fields to "ORDERS01".So,once you release the IDOC
      type you can not add any more fields .So SAP come up
      with "ORDERS02" with new fields.Like that all IDocs types have
      some more new seg ments.
2.You can use ORDER05
3. Yes you can use same IDOC type

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Inbound idoc error in 51 Status of at least one serial number of item

Dear Experts,
There is one inbound IDOC which is in error with status 51 showing error Status of at least one serial number of item is not allowed.
Can you please advice why this error is coming.
Thanks & Regards,
Nikhil Kanegaonkar.

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

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

How to process inbound idoc in R/3 with status 75 - idoc received via qRFC?

Hi gurus,
we are using EOIO for source to R/3, and all the idocs a received in r/3 with this status. But they can't be processed from BD87. How to process these?
Thanks,
Olian
Edited by: Olian Saludew on Sep 11, 2008 11:44 AM

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

Inbound IDOC status is strucked at 64

Similar Messages

Maybe you are looking for