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!

Similar Messages

IDOC Status code 56 !!

Hi Friends,
 I am getting status code 56 for an Inbound IDOC. I have defined the partner profile for the Legacy system. Still I am getting status 56 with the following description.
Text
 EDI: Partner profile inbound not available
 Diagnosis
 An inbound partner profile could not be found with the following key:
 /DEVCLNT900/LS//FKK_EBS_TOI_COPA////
 This involves the key fields of table EDP21:
 -SNDPRN partner number of sender
 -SNDPRT partner type of sender
 -SNDPFC partner function of sender
 -MESTYP logical message type
 -MESCOD logical message code
 -MESFCT logical message function
 -TEST test flag
 Procedure
 Please check the inbound partner profiles.
Thank U for Ur time.
Senthil

Hi Senthil,
Here is the procedure to test.
Create segments WE31
Create IDOC types using segments in: WE30 (BASIC type)
Create Message type: WE81
now link between message type and basic type: WE82
create process codes: WE42
now link process codes to direction of delivery inbox or outbox with messege type: WE64.
make an entry of your FM in: BD51
now link between FM, Basic TYpe, Messg.Type: WE57.
create port: WE21
create partner profile: WE20
 partner no.: SAP_DEV
 partn.type: LS
 Under Post processing:
 type: US
 agent: name of agent
 lang.: EN
 outbound partrs.
 message type:---
 Inbound partnrs.
 message type:ZLOCAL_STAFF / HRMD_A
 under Classification:
 partner class: ALE
 partn.status: A
 Message type: ZLOCAL_STAFF
Hope this helps.
Regards,
Vivek
<<removed_by_moderator>>
Edited by: Vijay Babu Dudla on May 19, 2009 7:09 AM

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 code

Hi
could you plz somebody explain what does this mean ??
Status 30
Status Message for Selected IDoc
IDoc: 0000000000546089 Status: IDoc ready for dispatch (ALE service)
Receiver found , No filters , No conversion , Version conversion
thanks
kumar

status 30 means idoc ready for dispatch from ALE Service Layer to Communication Layer.
Once the idoc has reached the Communication Layer it will get the status 03.
Cheers,
Hakim

Idoc inbound error status code 56

Hi,
   when i am sending custom idoc from source system to destination , idoc sent successfully from source system .But in the receiver system idoc status code is 56 ( idoc with errors added) .
partner profile also available in the receiver system. How to solve the error.can any one pls give me the solution.
                                                                                Regards,
                                                                                Suhash.

Hi,
Check this link..[IDOC Status code 56 !!   |IDOC Status code 56 !!]
[Re: Status 56 - IDOC with errors added   |Status 56 - IDOC with errors added]
Edited by: Avinash Kodarapu on Mar 19, 2009 4:55 PM

IDoc status error 51 : A company code cannot be determined for LS

Hi,
We are trying to post an Idoc into R/3 but getting the IDoc status code 51 : A company code cannot be determined for LS
What could be the possible reason?
Should we use Party in Receiver IDoc scenarios?

Hi,
I have quite the same problem. I built an IDOC with WE19 and I have the message "A company code cannot be determined for LI 0000031004".
As explained in note OSS 117808, the partner number (31004) and partner type (LI) are read from the control record of the IDOC. I enter this values in OBCA and OBCE customizing points, to determine the company code 'LC'. It doesn't work.
PT Rao, what do you call "activate partner profile" ?
Thanks in advance.
Regards,
Arnaud

Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

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

Regarding idoc status 26 Error

In ABAP(Selection program)
can anyone give the solution for the idoc status code below
26 Error during syntax check of IDoc (outbound)
what could be wrong in the idoc creation
Edited by: vijay on Jan 7, 2008 3:39 PM

hi vijay,
It depends on the type of program.if it is custom written program check with your program logic and compare it with idoc structure.
Reward if it usful,
Thanks,
Srikanth.A

A new IDOC status - ex. 80

Is it possible to create a new IDOC status code? we want to capture some of the intermediate processing messages in the IDOC status log. ex. "status 80 - BDC x done" -> "Status 80 order created" -> "Status 53 order has been imported".
I couldn't find anything under SALE but did saw couple of tables that list out status numbers and associated texts w/ it. I thought I would be able to add in a new status number - code, but 'new entries' is not an option.
Thanks in advance.

Yes, you have an option to create new status messages. I have done this before.
Please try running the area menu WEDI from your SAP easy acess screen.
You will find an option to create new status.
Let me know if you need more details.
Regards
Sabu

Changing idoc status by programs

when we will go for changing the idoc status code ?? Actually what is the use behind that ?? why we are forcing the system to chagne the status using some program ?? In which situations normally we will do that ?? Is it a valid procedure to do that ?? suppose idoc status is change from 51 to 68 using Program RC1_IDOC_SET_STATUS.
thanks
kumar

Hi pavan! thanks for your reply !
>>so the users will manually change the idoc instead of changing the legacy file. and chagne the status.
manually change the idoc means the data of idoc or sth else ?? could you please calrify the same ?? once if you change the status of idoc ...suppose 51 to 68 again you got to run the exteranal program to proces the idoc ??
>>then we've schduled a job which will process the edited idocs, so that all idocs will post again with correct data
Could you please tell me what do you mean by (actually what it is ??) scheduling of a job ?? Is it like that any executable program ?? or you are going to send the new idoc ??
thanks
kumar

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.

37 Status code in IDoc to File Scenario

Hi Experts,
I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
while I am testing from SAP backend system (All required configuration steps are also good).
I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
please help me.
Thanks in advance,
Regards,
Sudeepth.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

Idoc Monitoring (Inbound & Outbound Status codes)

Hi ,
In a scenario...whr IDOC has to be send to XI to file.....
and idoc is sent to XI ...if an error occurs ...wht is the process to troubleshoot...wht r the various reasons codes ? in a reverse way ..an IDOC needs to send to R/3 and an error occurs..wht is the process to trouble shoot....pls give a brief note on various idoc status ???
Best Regards,
Kir@n ; )

Main Tools
XI Runtime Workbench
Transactions:
●     IDX1
●     IDX5
●     SXMB_MONI
●     SM58
●     SM21
Analysis
For an overview of analysis steps see a very good link to troubleshoot
[http://help.sap.com/saphelp_nw04/helpdata/en/05/d5fc3f8fc2c542e10000000a1550b0/frameset.htm]

Idoc status codes

Similar Messages

Maybe you are looking for