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

Similar Messages

Status 56 - IDOC with errors added

Hi everyone,
 I was configuring File to IDOC Scenario, in the receiving R/3 system, i am getting error as Status 56 - IDOC with errors added "EDI: Partner Profile not available".
 but i had already created Partner profile in WE20.
Regards,
Varun Reddy.K

Hi Varun,
 The below link will help u in solving u r problem
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Just try follow the steps followed in above mentioned link
And also check u r RFC connection in TC "SM59".
Reward with ponits if helpful
Regards
Sai Ganesh

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Idoc status 03 in SAP but in XI idoc not showing

Hi Experts,
in my SAP to file scenario, idoc is created successfully with status 03, but idoc is not coming to PI.
It is not happening always. some times, idocs are missing. But not able to find any error in PI.
Please guide me how to get the missed idoc.
Thanks,
Swapnashree

this is old interface and it only gave issue this time. In ECC side, when I checked, out of 4 idocs one idoc is with 03 status and other three were with 39 status.
But all in green status. No error.
RFC destination and all are correct.
Actually I am not able to see the complete error text in TRFC . that message class is not maintained. Our functional team informed that they added XX text and re import idoc and it worked. Please suggest.

File to IDoc Scenario: Idoc Status 50

Hello,
I have a problem in doing a File to IDoc Scenario with a simple XML file mapped to IDoc "CREMAS.CREMAS03". In the beginning, I got a status 56:"IDoc with errors added". Then I added a logical system (LS name of my sender)manually in "Display IMG";however, it didn't work. So I simply changed the logical system name of my sender to XI_00_800 which already exists in R/3. I tried the scenario again, then I got the status 50:"IDoc added". Looked like the IDoc still hadn't been correctly inserted as a record. May I ask what other steps or configurations do I need to do to get this scenario to work? Thank you.

Steve,
Moreover, I didn't create any partner profile. The "XI_00_800" partner profile is in the system all along. Should I create a whole new partner profile and point that to my sender business system?
You need not create it once again as it already exists. Normally , ALE configurations on an R3 system are the responsibiltis of the Functional Team. For instance , on our projects we are never given access to the End r3 systems and the Partner profile are created by the F'nal team itself.
Like I mentioned, ask your F'nal team why you are getting this issue. From XI side , there is nothing more you need to do.
Regards,
Bhavesh

File to IDOC- Status 51:Application document not posted

Hi Experts,
I'm doing a File to IDOC scenario. The Idoc is getting added and then it is trying to post it to the application but i get the error saying that "Fill all required fields SAPMF02D 0111 ADDR1_DATA-COUNTRY".
The idoc type i'm using here is debmas06. The source file doesn't provide all the data and the idoc type doesn't really contain the field addr1_data in it. What is wrong?
Plese help.
Thanks ,
Merrilly

Hi
For Idoc type debmas06 there are few mandatory fields such as ADDR1_DATA-COUNTRY.
Check if the ADDR1_data is segment in IDOC not field.
While passing the data from file to xi to IDOC these mandatory fields are not filled up.
Probably you need to identify these fields and have to pass the default values if incase the inputs are not in file.
In We30/we31 you can check with the segment editor for the mandatory status of the fields.
Thanks
Swarup

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

File to idoc status 56

Hi,
I have already defined the partner profile in we20, but still i am receiving this error for inbound idoc.
In PI the message is successful in sxmb_moni.
I have carried the following steps in PI:
1 RFC destin in PI i.e. ERD250100 sm59
2 Port in idx1 SAPERD250
3 load metadata of ISM_MATMAS03
The following steps in ERP
1. bd54 added source file system logical name BIBLIO01
2. we20 part no. : BIBLIO01 and added the inbound parameters as ISM_MATMAS
Also in receiver idoc CC i added SAPERD250 as port and ERD250100 as the rfc destination
Now I am not able to receive idocs and before i received it with status 56
Please Help

Hi
Check this blog also
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Check this also :
the port maintained must be of naming convention
SAP<SID>
Check this also:
Solution:-Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.
If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process
TA. BD87.
1. Execute transaction BD87.
2. From the screen displayed, fill in the selection criteria.
3. On the next screen, select a summary line click the process button to reprocess all IDocs represented by the line. By clicking the Restrict and process button, you will be shown another selection screen to further restrict the number of IDocs to be processed.
Check this also:
Delete the Entries under that inbound Parameters.and Add again.
Check this also:
In XI Mapping, Fill the Control Record values manually
And in the Receiver Idoc Adapter, Check the boxes
Take Sender from Payload
Take Receiver from Payload
apply control record values from payload
trigger this time and check
Hope any one of the above solution will help you.
Regards
Dheeraj Kumar

I/B Idoc Status 56 - Reason Required

Hi,
We have a PI system and R/3 System. PI sending some idoc to R/3. In this case Idoc is failing and giving status message as 56. Can any one tell me reason why it is giving error like.
Error messages are like this:
Status Text:- IDoc: 0000000001230201 Status: IDoc with errors added
T001 Text :- EDI: Partner profile not active
Please let me know in which system do i need to the changes and how can i do these changes.
I am new to this concept.
Thanks,
Sekhar.J

Hi Sekhar,
From PI perspective everything is fine, you were able to create an IDOC structure and push it to R/3 system and there is also successfully created but it has failed with the error 56. It is due to invalid partner profile, check the transaction WE20 whether a partner profile has been created for that partner or not, if it is created then whether the message type is configured for that partner or not.
The error is basically due to invalid partner profile and you need to correct that in WE20 transaction, once you correct that then you can reprocess the idoc through BD87 transaction.
Thanks,
Mahesh.

Post system refresh, "Request IDoc : IDoc with errors added"

Hello All,
Post system refresh, we are not able to execute the data loads.
While loading the Infopackage, the overall status is still showing in YELLOW status. but in the Transfer (IDOCs & TRFC), it shows an Error message as "Request IDoc : IDoc with errors added"
Yesterday immediately after the refresh, we were able to execute the master data loads (full loads)...
However, transaction loads (delta) is facing issues.
Today, we are facing the problem in both master and transaction data.
Please help!!!! Its a very critical issue!!!
Edited by: Siegfried Szameitat on Aug 9, 2011 10:17 AM

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

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

Add message to iDoc status

I created Z_ functional module for inbound Sales Order iDoc processing.
I want to add my own warning message to iDoc status:
    CLEAR idoc_status.
    idoc_status-docnum = idoc_contrl-docnum.
    idoc_status-status = '64'.
    idoc_status-msgty = 'W'.
    idoc_status-msgid = 'ZMSERIES'.
    idoc_status-msgno = '005'.
    APPEND idoc_status.
When i test in Test Tool WE19 using button "Inbound functional module" message successfully added to iDoc (WE02).
When i click "Standard inbound" - there is no my message in iDoc status.
Maybe i should use another status number? Instead of '64'?

I dont think you should change status number, but i ask you to check it once with proper configuration settings

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!

Set idoc status

Dear experts,
i have an idoc which i work with. My Problem is:
how can i set the idoc status to 51 and mark it as corrupted ?
or how can i let the system mark it like this if it is not possible to do it myself ?
Thanks a lot and best regards
René

Presumably, the 51 status has been triggered by some error condition in your process code. That error condition should have a message associated with it. You should have a table or structure that stores these messages and then at the end of your processing, add those messages to the IDOC_STATUS table. You can also add messages for status 53 (such as the document numbers that you have created), status 68, or any other status value. Look at examples of standard process code and you'll see what I mean but here are a few code snippets:
Conditional error message:
    GV_IDOC_ERROR_FLAG = 'X'.
    GV_STATUS          = C_IDOC_STATUS_51.
    MESSAGE E199(ZCORP) WITH GS_DEL-VBELN INTO GV_MESSAGE.
    PERFORM F9999_ADD_MESSAGE.
Setting the status, adding the messages to the IDOC in a subroutine at the end of processing:
CLEAR IDOC_STATUS.
LOOP AT GT_MESSAGES INTO GS_MESSAGES.
    IDOC_STATUS-DOCNUM = P_DOCNUM.
    IDOC_STATUS-STATUS = GV_STATUS.
    IDOC_STATUS-MSGTY = GS_MESSAGES-MSGTY.
    IDOC_STATUS-MSGID = GS_MESSAGES-MSGID.
    IDOC_STATUS-MSGNO = GS_MESSAGES-MSGNO.
    IDOC_STATUS-MSGV1 = GS_MESSAGES-MSGV1.
    IDOC_STATUS-MSGV2 = GS_MESSAGES-MSGV2.
    IDOC_STATUS-MSGV3 = GS_MESSAGES-MSGV3.
    IDOC_STATUS-MSGV4 = GS_MESSAGES-MSGV4.
    APPEND IDOC_STATUS.
    CLEAR IDOC_STATUS.
ENDLOOP.
IF SY-SUBRC NE 0.
    IDOC_STATUS-DOCNUM = P_DOCNUM.
    IDOC_STATUS-STATUS = GV_STATUS.
    APPEND IDOC_STATUS.
    CLEAR IDOC_STATUS.
ENDIF.

IDOC Status 50 / Idoc added

Similar Messages

Maybe you are looking for