Idoc status 62 - Passed to application

Hello All,
i am processing an inbound idoc purchase order. Got status 62 : Passed to application. But how to process it further to get status 53: Application document posted,
Thanks
Ricky

Ricky,
status 62 means that your application (the function configured for this IDoc type) started but did not do anything. It just does not work as expected. The application should come to a regular end with Posting and status 53 or 51/52 for failed posting.
There is no further processing for Status 62 because this status means the application is still processing it.
You can enter the IDoc number in WE19 test tool, select function module and process in debug mode. This may help you to find out what's wrong.
Regards,
Clemens

Similar Messages

IDOC status 62 - IDOC passed to application

Hello Experts,
Am posting a inbound sales order custom/extended IDOC into the system from WE19, but, when I saw it in WE02/05, its showing status 62 - IDOC passed to application, i checked ST22 run time error. there is no error and also checked triggering timings, its trigger IMMEDIATELY in WE20 fo rthat partner!!
Pls. let me kniow the reasona and fixing idea.
Thank you

I think you're going to want to debug through the process code (set a breakpoint in that function) and determine if you get a clean exit from there. If so, you should see a new status in your control record and in your status table as you exit the function call. It sounds like you've got an abnormal termination/exit from the process code, in which case the IDOC status is falling back to the last recorded status. If this is not the case, then perhaps you've got a commit handling issue where an explicit commit is expected to finish the process but never happens.

IDocStatus Application document not posted, No status record passed to ALE

Hi,
I am sending CREMAS04 IDOC to receiver system.The receiver system should create vendor entry in master table by using IDOC data.
IDOC is getting posted successfully in R/3,but while calling inbound function module i.e process code CRE1 I am getting following status records :
51 Application document not posted
No status record was passed to ALE by application.
62 IDOC passed to application
Direct call started.
64 IDOC ready to be transfered to application
No filters , No conversion , No version change .
50 IDoc added
Please help me to resolve this problem.

Shweta,
The IDOC has been posted by XI to the R3 system. It is the funtional module that is not able to handle the IDOC and only your Functional Team can tell you why the IDOC is not being processed properly by the R3 system.
It can be because of multiple reasons including invalid data, etc . For instance we once faced an issue once when the User ID used to post the IDOC did not have the authorizations to do financial manipulations and it was our functional team that was able to pin point the reason to us.
Regards,
Bhavesh

Inboun IDOC status 52--Application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

I am attaching how we documented the process in our troubleshooting guide. Graphics were not pasted.
21.3       Manually run IDOCs reported as 52.
It is possible that IDOCs are found in status 52 for the daily updates.   In principle IDOCs 52 can not be re-proceeed, but there is a way to push the appropriate data from a source system, e.g. ERP.    Following is the process.
21.3.1     You find IDOCs in status 52 in WE02.
21.3.1     Open table EDIDS.
Perform 2 searches for parameter STAPA2 and STAPA1 in status 52 and download the entries for each column to an MS Excel file.
21.3.2     Adjust the MS Excel file.
The strings STAPA2 and STAPA1 have to be truncated and separated into 3 different fields for processing: First 2 characters are the Plan Number, next 2 the Object Type, and next 8 the Object Number.
21.3.3     Manually process the entries via transaction PFAL from the source system, e.g. ERP.
The entries must be processed in the following order sorting by Object Name:
u2022     STAPA2s first, then STAPA1s.
u2022     Each organized by O, S, P, C, and CP.
21.3.3.1     Running individually for each entry.
By running PFAL with the individual entries: Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOC will be passed to target system for processing.
21.3.3.2     If there are many entries for processing.
If there are many STAPA2 and STAPA1 for processing.
u2022     Create a text file like the one below with the entries as mentioned above.
u2022     Logon into the source system and make sure CATTs are allowed..
u2022     Via SCAT, create a CATT that emulates the execution of PFAL entering Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOCs will be passed to the target system for processing.
. Create the text file with the entries.
. Execute the CATT ... the respective IDOCs will be passed to target system for processing.

IDoc: Status: Application document not posted

Hi Friends,
       I am New to ALE/IDOC. Based on the ALE_QUICKSTART documentation. I have tried to send material from one client to other client. (within system) To do that
I have created two logical systems and assigned them to corresponding clients.
Created a RFC destination and assigned logical systems.
Created Distribution model in sending client.
Created partner profile in both clients.
Created Material and send to receiving system using BD10 tcode.
I checked Idoc status in Sending system, Idoc status is 03-Data is passed to port OK, status 30-Idoc ready for dispatch and status 01- Idoc generated.
But in receving system (Inbound Idoc)- I got status- 51-Application document not posted and Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
I also checked partner profiles in both systmes- both r same.
Kindly tell me what went wrong and what should i do.
Pl.provide answers pertain to this problem only.
Thanks in advance,
S.Senthil

Hi Chris,
        Thanks for ur reply. I am not using is-retail and I have Generated MATMAS idoc in sending system.
      Kindly provide me answer.
Thanks in advance,
s.senthil kumar

Idoc status 53.Yet application data is not posted.

IDOC status is 53. But application data is not partially posted.iam generating 2 idocs, one for type INFREC01 and other for COND_A01. iam Generating IDOC using a fm IDOC_INBOUND_ASYNCHRONOUS. purchase info record is posted succesfully. but condition info record is not posted.
for both the idoc its shows green status-53. moreover data in EINA EINE KONH KONP is updating, but its not displayed in transaction ME13.
Kindly help me.

Hi,
Check the config stuff if you are usng the right IDoc...See partner profiles and the message types.
thanks

BI extraction error -- Application document not posted - IDOC Status 51

Hi,
I am getting the following error while extracting data from ECC to BI.
'Application Document not posted'
I went to BD87 in ECC and found that the Idoc Status is 51 and the message is
'Request REQU_4C65QV...V9QRNZ2X9TV9QRNZ does not exist in target system N05CLNT100'.
I have already checked partner profile parameters with Basis and they claim everything is okay.
Do you have any ideas what might be the issue?
Thanks,

Hello Rajendra,
You can review the note 417307 which contain information about the MAXSIZE of a package size. This is a collective note which contain more notes to other extractors.
417307 - Extractor package size: Collective note for applications
549184 - FAQ: What is important for extraction
157652 - Main memory requirement for extraction from R/3
You can review the table ROIDOCPRMS and check if the parameter StatFrqu contains a 'X' or a number? You can set this option to 99.
You can also review the correction note 1147326.
Check as well if the user ALEREMOTE have the proper profiles configured in both source and target system, sometimes the user is missing the profiles, to check this, read the note 150315.
I hope that the information can help you.
Regards,
Daniel

IDoc Status Messages

Hi All, Is there any Function Module or standard report which will list out all the Status messages of an IDoc...Basically i need to capture all the segments which are in error state... In EDIDS table i am not able to link to a particular segment.
Please help me out
Thank You,
Regards,
Swaroop Patri...

HI,
ALE/IDOC Status Codes/Messages----
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
Regards
Sudheer

What is the Successfull processed IDOC status number?

Hi Experts
What is the Successfull processed IDOC status number?
arjent Please.
Thanks in advance
Sekhar

Hi Chandra,
Below are IDoc Process Codes
For outboud Idocs:
1 IDoc created
2 Error passing data to port
3 Data passed to port OK
4 Error within control information of EDI subsystem
5 Error during translation
6 Translation OK
7 Error during syntax check
8 Syntax check OK
9 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the receiving system (ALE service)
40 Application document not created in receiving system
41 Application document created in receiving system
42 IDoc was created by test transaction
50 IDoc added
For Inound Idocs
51 Error: Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc-Copy from an R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
Regards,
Satish

IDOC Status 50 / Idoc added

Hello Guru's
I can only find a description 'Idoc added'. What does IDOC status 50 mean?
Best regards

Hi,
If the inbound idoc is posted successfully, then you will see this kind of sequence.
50 IDoc added
64 IDoc ready to be transferred to application
62 IDoc passed to application
53 Application document posted
status codes
50 IDoc added
51 Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc copy from R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
75 IDoc is in inbound queu
regards
srinivas

IDOC STATUS 62

HI Experts,
I am processing an inbound idoc for material transfer request,
In WE19 once i click on "Inbound Function module " button to process idoc.
It process it successfully and also creates the Transfer request.
In FM in which i am processing the IDOC , after successfull creation i am updating the status to 53.
But it is not getting reflected,Its showing Status 62 all the time.
Please tell me the solution.
Thanks
Nikhil

Hi Nikil,
62 IDoc passed to application ..
that means there is a Problem with Process code or the Partner profile inbound message type..
check the Process code and message type are correctly maintined in WE20 for he Partner which the idoc is triggering..
the problem might be Process code for the Partner is not properly configured..
see the below sap notes for the possible solution
» 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
Regards,
Prabhudas

Ale Idocs Status code 64

Hi,
While processing inbound idocs, I am encountering status code 64 (IDoc ready to be transferred to application) . Can any one help in avoiding this status code.
Helpful answers will be rewarded.

64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Although the partner profile is defined and the IDoc has been received, the IDoc cannot be transferred to the application.
You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this report.
Check the processing mode for the IDoc in the partner profile:
Processing mode 1: The system transmits the IDoc immediately after receipt in the application.
Output mode 3: The system collects received IDocs.
IDocs are not intended to be transmitted directly to the application.
Status 64 in the IDoc can normally only occur in conjunction with processing mode 3 and output mode 2.

Idoc status codes

Hi,
I want to know the meaning of each staus code in Idoc ...
For example...
03 : -Data passed to port OK.
Points will be rewarded.

Hi there,
These are the codes that you are looking for! hope it helps!
Status Description
00    Not used, only R/2
01    IDoc generated
02    Error passing data to port
03    Data passed to port OK
04    Error within control information of EDI subsystem
05    Error during translation
06    Translation OK
07    Error during syntax check
08    Syntax check OK
09    Error during interchange handling
10    Interchange handling OK
11    Error during dispatch
12    Dispatch OK
13    Retransmission OK
14    Interchange Acknowledgement positive
15    Interchange Acknowledgement negative
16    Functional Acknowledgement positive
17    Functional Acknowledgement negative
18    Triggering EDI subsystem OK
19    Data transfer for test OK
20    Error triggering EDI subsystem
21    Error passing data for test
22    Dispatch OK, acknowledgement still due
23    Error during retransmission
24    Control information of EDI subsystem OK
25    Processing despite syntax error (outbound)
26    Error during syntax check of IDoc (outbound)
27    Error in dispatch level (ALE service)
28    Not used
29    Error in ALE service
30    IDoc ready for dispatch (ALE service)
31    Error - no further processing
32    IDoc was edited
33    Original of an IDoc which was edited
34    Error in control record of IDoc
35    IDoc reloaded from archive
36    Electronic signature not performed (timeout)
37    IDoc added incorrectly
38    IDoc archived
39    IDoc is in the target system (ALE service)
40    Application document not created in target system
41    Application document created in target system
42    IDoc was created by test transaction
50    IDoc added
51    Application document not posted
52    Application document not fully posted
53    Application document posted
54    Error during formal application check
55    Formal application check OK
56    IDoc with errors added
57    Test IDoc: Error during application check
58    IDoc copy from R/2 connection
59    Not used
60    Error during syntax check of IDoc (inbound)
61    Processing despite syntax error (inbound)
62    IDoc passed to application
63    Error passing IDoc to application
64    IDoc ready to be transferred to application
65    Error in ALE service
66    IDoc is waiting for predecessor IDoc (serialization)
67    Not used
68    Error - no further processing
69    IDoc was edited
70    Original of an IDoc which was edited
71    IDoc reloaded from archive
72    Not used, only R/2
73    IDoc archived
74    IDoc was created by test transaction
Rewards would be appreciated!

Idoc Status doubt...

Hello,
If an Idoc(Inbound) is in status 64 (Idoc ready to be passed to application) is there any way to force it to any other status so that it will not be processed by the backgroung job(running for RBDAPP01)...?
Is it possible to force an inbound idoc to other status...?
We need to stop the idoc before its been processed by Scheduled background job...
Thanks,
Larry

Use this:
<code>
REPORT z_idoc_status.
TYPE-POOLS:
slis.
TABLES:
edidc.
TYPES:
BEGIN OF out_type,
 docnum LIKE edidc-docnum,
 mestyp LIKE edidc-mestyp,
 status_old LIKE edidc-status,
 status_new LIKE edidc-status,
END OF out_type.
DATA:
wa_out TYPE out_type,
out TYPE STANDARD TABLE OF out_type.
DATA for ALV GRID VIEW
DATA: fcat TYPE slis_t_fieldcat_alv,
 wa_fcat TYPE slis_fieldcat_alv,
 alv_layout TYPE slis_layout_alv,
 alv_variant TYPE disvariant,
 alv_grid_title TYPE lvc_title,
 alv_sort TYPE slis_t_sortinfo_alv,
 wa_alv_sort TYPE slis_sortinfo_alv,
 alv_report_id LIKE sy-repid.
SELECTION-SCREEN BEGIN OF BLOCK idoc WITH FRAME TITLE text-001.
SELECT-OPTIONS s_docnum FOR edidc-docnum.
SELECT-OPTIONS s_mestyp FOR edidc-mestyp.
SELECT-OPTIONS s_staold FOR edidc-status.
PARAMETER p_stanew TYPE edidc-status.
PARAMETER p_update AS CHECKBOX.
SELECTION-SCREEN END OF BLOCK idoc.
START-OF-SELECTION.
SELECT
 docnum
 mestyp
 status
INTO (wa_out-docnum
 ,wa_out-mestyp
 ,wa_out-status_old
FROM edidc
WHERE docnum IN s_docnum
 AND mestyp IN s_mestyp
 AND status IN s_staold.
 wa_out-status_new = p_stanew.
 APPEND wa_out TO out.
ENDSELECT.
IF p_update = 'X'.
 LOOP AT out INTO wa_out.
 UPDATE edidc
 SET status = p_stanew
 WHERE docnum = wa_out-docnum.
 ENDLOOP.
ENDIF.
CLEAR wa_fcat.
wa_fcat-fieldname = 'DOCNUM'.
wa_fcat-ref_tabname = 'EDIDC'.
wa_fcat-ref_fieldname = 'DOCNUM'.
wa_fcat-key = 'X'.
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
wa_fcat-fieldname = 'MESTYP'.
wa_fcat-ref_tabname = 'EDIDC'.
wa_fcat-ref_fieldname = 'MESTYP'.
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
wa_fcat-fieldname = 'STATUS_OLD'.
wa_fcat-seltext_l = 'Status alt'(002).
wa_fcat-seltext_m = 'Status alt'(002).
wa_fcat-seltext_s = 'Status alt'(002).
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
wa_fcat-fieldname = 'STATUS_NEW'.
wa_fcat-seltext_l = 'Status neu'(003).
wa_fcat-seltext_m = 'Status neu'(003).
wa_fcat-seltext_s = 'Status neu'(003).
APPEND wa_fcat TO fcat.
alv sortierung
CLEAR wa_alv_sort.
wa_alv_sort-spos = 1.
wa_alv_sort-fieldname = 'DOCNUM'.
wa_alv_sort-up = 'X'.
APPEND wa_alv_sort TO alv_sort.
alv Ausgabe
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = alv_report_id
 i_grid_title = alv_grid_title
 is_layout = alv_layout
 it_fieldcat = fcat
 i_save = 'A'
 it_sort = alv_sort
 is_variant = alv_variant
 TABLES
 t_outtab = out
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
</code>
You can manipulate the status of each idoc.

IDoc Status 02 ( Could not find code page for receiving system )

Hi All,
I am getting Idoc status 02 when I am trying to send IDocs from ECC to PI system ( Production ).
Error description.
Could not find code page for receiving system
Message no. E0266
Diagnosis
For the logical destination PIP001, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
Procedure for System Administration
Possible causes are:
1. The entry no longer exists in the table of logical destinations.
2. The target system could not be accessed at runtime.
3. The logon language is not installed in the target system.
4. In the destination system, no logon language is maintained
Please help.
Thanks - Vinay.

Hi Vinay,
Status 02 occurs when data is not passed to port suceessfully. Check the RFC desination is working fine and your able to connect to target system and also check correct port is assigned.
Regards,
Vinod.

Idoc status 62 - Passed to application

Similar Messages

Maybe you are looking for