IDocs with incorrect status

Hi !
When i tried to upload data from R3 to BW based on generic DataSource
( function module ) , in the monitor i get the following error :
Status code : 56. Description: "Idoc with error added" .
How can i get more details about the error? How To correct the Error ?
Thanks
Moshe

Hi,
it's IDoc with errors added
check if you have any errors in other stauses
and display 56 (double click) in WE02
you should see some more descriptions .
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4344391&messageID=3662902
Foe more information, please check this links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
rEGARDS

Similar Messages

There are IDocs with incorrect status.How to rectify it?

Hi All,
I was trying to do full load for 0vendor_attr.
The error message is getting displayed as mentioned below:
" Error when updating Idocs in Source System*
Diagnosis
Errors have been reported in Source System during IDoc update:
Incomplete control parameter for commmunication wi
System response
There are IDocs with incorrect status.
Procedure
Check the IDocs in Source System . You can get here using the BW Monitor.
Removing errors:
*How you remove the errors depends on the error message you receive." *
Please revert.

The Error messages in detail:
Incomplete control parameter for commmunication with the BW system
                                                                                Diagnosis
                                                                                The control parameters for communication with the BW server are not
     complete. A BW PlugIn upgrade could be the cause of the problem.
                                                                                System response
                                                                                Procedure
                                                                                Depending on the Release of the BW server, proceed as follows:
     BW Server Release 1.2B: Source system: Update InfoSource metadata
     BW Server Release >= 2.0A: Source system: Activate
Please revert at the earliest what needs to be done int his case.

Idocs with error status

Hi Everyone,
How to find all idocs with error status for a given date range?

Hi,
Please refer EDIDS for Status and EDIDC for control records.
Also refer the below wiki page for details.
http://wiki.scn.sap.com/wiki/display/ABAPConn/IDoc+Overview
Thanks,
Karthik

Creating Idocs With 64 Status.

Hai Friends,
My requirement is like this...
Scenario:- my client says...They Get some idocs from a external system and then a program runs in the background to read these idocs and post Inbound delivery and IR documents.
And Now As These IDOCs are not coming ...We have to read this data from a excel sheet and Create exactly the same type of IDOCs so that They can RUN the same Program to post Documents.....
Now my doubt is ...How do i create IDOCs with status 64 and that too in the same same..as here there wont be any target system..
Please help me with ur solution....How should i Approach...I know how to fetch data from excel and all..I need Help specially in
Creating IDOCs with 64 status and what should be in the Control Records..
Waiting for your insight.
Thanks,
Jeevan...

Hi,
You can use below FM for your requirement.
CALL FUNCTION 'IDOC_INBOUND_SINGLE'
 EXPORTING
 pi_idoc_control_rec_40 = w_control_rec
 IMPORTING
 pe_idoc_number = g_idoc_number
 TABLES
 pt_idoc_data_records_40 = i_idoc_recposting
 EXCEPTIONS
 idoc_not_saved = 1
 OTHERS = 2.
IF sy-subrc = 0.
Idoc created if sy-subrc = 0
Endif.
The Control records should be like this ( You need to check the partner profile)
w_control_rec-mandt = sy-mandt.
w_control_rec-docrel = <sap_release>
w_control_rec-direct = '2'.
w_control_rec-idoctyp = < Idoc type >.
w_control_rec-mestyp = < message type>.
w_control_rec-sndpor = <sender port>
w_control_rec-sndprt = < Sender partner type>
w_control_rec-sndprn = < sender partner>.
w_control_rec-rcvpor = < recv port>
w_control_rec-rcvprt = < recv partnertype >
w_control_rec-rcvprn = < recv partner>
Let us know if it helps you. Thanks.
Edited by: Atul Mohanty on Jun 23, 2011 10:59 PM

Inbound idoc with error status 52 messege type hrmd_a07

i have an inbound idoc with status 52
error messege : Object 01 ,P ,00056786 does not exist: infotype 0302 cannot be created
Object 01 ,P ,00056786 does not exist: infotype 0006 cannot be created
i debugged but i haven't find out the reason
am updating 0000,0001,0002,0003,0006 infotypes

Hi rahul,
Need to check the address filed (0006) for BP mapped to postion (00056786)
Infotype 0302 (Additional Actions) :
Infotype 0302 is not maintained directly and is automatically updated by Infotype 0000 .
The additional actions Infotype (0302) is of time constraint 3 (gaps and overlaps).
Specifically in some cases if we want to have a non status-changing Action on the same day where already a personnel action is existing at that time we can activate the Infotype 302 by executing Report RPUEVSUP.
please check and let me know . I think it will be helpfull
Thanks and Regards,
Krishna

IDoc with incorrect data is expected to fail but it does not

Hi All,
The Job CQM_CR_O_IF103_IN_INOVIS_ORDER3 got cancelled as result of a short dump. In the initial investigation we found that the IDoc 0000000012089824 had an incorrect information i.e. it had a material which did not
exist. The IDoc is expected to fail and give an error message but has not done so.
We also observed the IDoc does not fail when the incorrect materialhappens to be the last material in the IDoc.
The workaround was to fail the IDoc manually and then the subsequent jobs runs successfully.
Would like to know why the IDoc is not failing when it has incorrect
data.
Thanks & Regards,

Hello,
the idoc fails only if there is a hard error in the segment, means i.e. if there is a wrong transaction type or missing ... But I think that the system behavior is correct, because the idoc cannot fail because a product is "just" wrong. This is no hard error, you should then get an error in the transaction that i.e. the product does not exists. You can try to use badi CRMXIF_ORDER_MAP to check the products, but then please make sure that note 1644057 is implemented.
BR
Rene

IDoc with incorrect data is expected to fail but does not

Hi All,
The Job CQM_CR_O_IF103_IN_INOVIS_ORDER3 got cancelled as result of a short dump. In the initial investigation we found that the IDoc 0000000012089824 had an incorrect information i.e. it had a material which did not
exist. The IDoc is expected to fail and give an error message but has not done so.
We also observed the IDoc does not fail when the incorrect materialhappens to be the last material in the IDoc.
The workaround was to fail the IDoc manually and then the subsequent jobs runs successfully.
Would like to know why the IDoc is not failing when it has incorrect
data.
Thanks & Regards,

Hello,
the idoc fails only if there is a hard error in the segment, means i.e. if there is a wrong transaction type or missing ... But I think that the system behavior is correct, because the idoc cannot fail because a product is "just" wrong. This is no hard error, you should then get an error in the transaction that i.e. the product does not exists. You can try to use badi CRMXIF_ORDER_MAP to check the products, but then please make sure that note 1644057 is implemented.
BR
Rene

How can i delete or archive idoc with status 30,02,51

I try to delete idoc with Sara and also running program RSEXARCA with.
When create variant and i want to choose the status i can't find the status 30, 02, 51.
How can I delete thus idocs with this status?
Thanks
Menashe.

Yes. WE11 Would do.
But, one request.
Next time when you post a query related to Idocs, post it in Data Transfers section. If you do so you will get very quick reply compared to the response you get in ABAP General Section.
Thanks,
Babu Kilari

PAYEXT IDOC has recurring statuses

Hi
We are using the standard message type PAYEXT to send IDOCs to banks for payments to vendors. The IDOCs are set to be created via F110 payment run. Then a periodically scheduled job for RSEOUT00 sends the IDOCs out. When the IDOCs are created via the payment run, they are set to status 30 (Receiver exists , No filters , No conversion , No version change), which has the user's username. When BD87 runs the IDOC status changes to 03 (IDoc written to file), which has the SAP_BATCH username (the username with which the BD87 was scheduled with).
This system has been working fawlessly for over 6 yrs.
Just one day this month, all the IDOCs that were created for PAYEXT message type, began with had the correct status of 30 & then 03 with the correct user-ids and statuses as above & for some strange reason again a status 30 (with SAP_BATCH username and error status: Could not write IDoc to file) and 03 (SAP_BATCH username and success status: *IDoc written to file*) and then continued as usual. The difference in the first & second status 30 is 3 secs. This has caused duplicate payments to the Vendor.
This whole situation was reset when 1 IDOC failed and everything was back to ususal.
We do not have any custom code to set any statuses. We have posted this to SAP & have been waiting for 2 days to respond.
Any help will be greatly appreciated.
Thanks
Ashwini

Hello,
In my case Inbound - IDOC was generated & process in one thread. there was bug in code which was creating another thread to proces same IDOC.
One thread was processing IDOC with correct status of 53, another was trying to process IDOC it was putting status of 51 on same idoc
Both statuses were on same IDOC.
The possibility of creating new idoc hapens when system try to create IDOC.
In your case, It's just processing of IDOC which happens two times. so new IDOC will not be created.
Regards,
Sameer Desai

Idoc with recurring Object ids(CP) in E1PLOGI.

Hi,
When Idocs for object type 'CP' is getting created the E1PLOGI are getting created with recurring object ids.
In a single IDoc, if multiple E1PLOGI are there, the the 1st E1plogi contains one object id (CP), 2nd one contains 1st and 2nd both , 3rd E1PLOGI contains 1st,2nd and 3rd, all the object ids(CP).
Please explain what's the cause of this kind of recurring insertion of objects in the succeding E1plogis.
Thanks.

Hello,
In my case Inbound - IDOC was generated & process in one thread. there was bug in code which was creating another thread to proces same IDOC.
One thread was processing IDOC with correct status of 53, another was trying to process IDOC it was putting status of 51 on same idoc
Both statuses were on same IDOC.
The possibility of creating new idoc hapens when system try to create IDOC.
In your case, It's just processing of IDOC which happens two times. so new IDOC will not be created.
Regards,
Sameer Desai

Reprocessing IDOCS with status 52

Hi all,
I facing a problem with IDOC status 52.
After correcting the error it had given, I want to reprocess it again.
Kindly tell me any report or transaction name for reprocessing IDOC with status 52.
Regards,
Rahul

Hi Rahul,
You can use the below Programs for IDocs Reprocessing:
RBDMANI2 : Reprocess Idocs manually
RBDMANIN : Posting of IDocs with Status 51
RBDMOIND : Outbound Idocs status 03->12
RSEOUT00 : For Processing 30 Status IDocs
RBDAPP01 : For Processing 64 Status IDocs
RBDAGAIN : Reprocess Incorrect Outbound IDocs
RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
Regards
Aneesh.

Idoc with status 68

Hi,
Can any one tell me the reason for idoc status as 68.......in which case the system will show me the idoc status as 68
Thanks,
Shilpa

IDoc status Description
Outbound values :-->
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
Inbound Values::-->
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

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

Error in idoc with status 20 "Error triggering EDI Subsystem"

Dear All,
I have query related to IDOC Status 20.
I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )
Keeping the above fatcs in mind could you please tell me how to remove the error with status 20 "Error triggering EDI Subsystem".

Hi prabhat,
You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
Go to WE21 and do the access test for the file port.
Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
other reason could be the logical system assigned to the client should be having production client's name.
Check these.
I am sure you should be able to solve this issue.
Thank you.
regards,
karun.M

5 IDOC with status 29 Error in ALE service

hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
raju

Hi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards.

IDocs with incorrect status

Similar Messages

Maybe you are looking for