IDoc Status 02 error

Hi All,
Whenever we create the PO the outbound IDoc gets triggered but when we see the Idoc status it goes to 02 every time. Then when we manually re trigger the PO the status goes 12 which is ok.
we want that whenver PO is created Idoc should succesfully posted to status 12.
we are using the standard pgm for outbound idoc (RSNASTED).
Let me know how to resolve the issue.
Thnx
AC

Hi,
I have checked in WE20 transactiona and everything is ok as per your input, but still proble persist.
In partner profile in output mode "Transfer Idoc imm has been activated already.
Let me know what are other things i need to check to resolve this issue.
Thnx
AC

Similar Messages

IDOC: Status (Error/Success/information)report to Sender system

How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

Hi Baumann,
you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
Setting Up Audit Reporting
In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
Two programs enable cross-system reporting.
1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
The RBDSTATE program returns the following statuses, from the receiving to the sending system.
RBDSTATE Is Run on the Receiving System
Status of IDoc in receiving system     Status reported to sending system via ALEAUD
53 (Application document posted.)     41 (Application document created in receiving system.)
51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)     40 (Application document not created in receiving system.)
reward points if helpful,

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

Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
Could you please tell me , what is the issue with the partner type configuration .

Hi,
Error 29 occurs when there is an incomplete or no partner profile maintained.
Check whether you have done the correct partner profile settings in WE20 outbound parameters.
For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
with correct message type WMMBXY and Idoc type WMMBID02. Also check for message function code.
Regards,
Savitha

Idoc status error 37 in sender and 51 in recieving system

i m new to ale idoc n created 2 clients 910(sender system) and 800(reciever system)
all connections are well i got status message 03 and 30 and 01 but along with it i m getting one more idoc genersted and status as 37 . idoc no. 50 as 03 30 and 01 and idoc 51 as 37 . in sender system n inreciever system i m not getting idoc.after sumtim i m getting them n error status as 51 .two idocs are generated simultanously.
does the port name we21 should be same i m using same port name currently .
clnt910 --rfc800 destination client 800 (sender system).
clnt800 --rfc800 destination client 910 (reciever system).
when i m changing the port name i m getting error status as 29 .
we20 both the partner profile are active

Hi,
You Outbound IDOC is not correctly formatted I think, check the segments whether they are correctly added or not.
Thanks,
Mahesh.

Idoc status error 66 - IDoc must be processed later; 000006 , IDoc no. 0000

Hi,
The following error appears when a particular Idoc is trying to get posted
Status 66 - IDoc is waiting for predecessor IDoc (serialization)
Message - "IDoc must be processed later; 000006 , IDoc no. 000002 required."
What is this error all about? How do I find out which is the predecessor Idoc which has to be posted first. I can not find any other idoc numbers mentioned here.
Thanks in advance

Rhea,
What you have mentioned is clear for me too. But the question is how do I trace the predecessor idoc? 0002 or 0006 are not Idoc numbers. They are Idoc types.
Any way in which I can trace out the predecessor idoc?
Regards

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

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 "<b>EDI: Partner Profile not available</b>".
        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

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.

No authorization for changing Customer Centrally- Idoc in Error Status 51

Hi Experts,
We are implementing MDM for one of the client.
The client runs a modification scenario in MDM for Customer Master.
He modifies a customer record in MDM and this record is transfered from MDM to ECC via PI through Idocs.
We are using standard Idocs for Customer Master which is DEBMDM
There are 2 Idoc's generated in ECC by PI from DEBMDM as DEBMAS and ADRMAS.
ADRMAS Idoc is succesfull in ECC and the corresponding record is modified.
Now the issue is that the corresponding DEBMAS Idoc goes into Error 51.
The Error details is as below:
                                                                                No authorization for changing vendor Centrally
Message no. F2326
System Response
You cannot access the requested data.
Procedure for System Administration
If necessary, include an entry in the user's authorization profile for
    the authorization object and parameters specified below.
Authorization object:
o   F_KNA1_APP
Parameters:
o   Activity: 02
    o   Application authorization : *
We gave the respective authorization object to the RFC User ID used in PI RFC created to connect to ECC.
Also we have given the user id Tcode authorization like XD01/02/03.
But this error still persists.
Request to throw some light on this.
Cheers
Dhwani

Check these threads
[Re: IDOC STATUS - 51 " IDOC HAS TEST STATUS|IDOC STATUS - 51 " IDOC HAS TEST STATUS";
[Error Inbound IDoc - Status 51|Error Inbound IDoc - Status 51;
thanks
G. Lakshmipathi

HRMD_A IDocs in Error Status 02

Dear SAP Peeps,
Upon generation of outbound HRMD_A idocs, an error occurs. Error status is "02 - Could not find code page for receiving system".
Can you guys assist me here? What does code page mean? How the error will be solve? The error occurs in every two weeks upon sending the idocs. Sending system is a unicode system while the receiving system is a non-unicode system.
Thanks!

i Think u have run some personnel acitons
than u need to check the table T529A and check have u assigned the feature which standrad in sap for certain acions
for Ex MSN20 MSN10 check these thr PE03
in IMg
check SEt up personnel Acitons

SBWP full of status error 56 IDoc ?

Hi SAP Experts,
In my SAP ECC 6, thousand of inbound IDocs have been in error with status error 56 (partner profile not available with WE20).
Now, all users can see in their Business Workplace...thousand of error notifications !.
=> How can I deactivate this ?
Thanks a lot
Best regards
Etienne

Hi Imthiaz,
Thanks for yur response. We're looking around this task....
But we can't use a partner profil setting since we don't have any anyone (and don't want anyone).
Best regards
Etienne

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

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

Error handling problem with outbound idoc status 02 and XML HTTP Port

I set up an ALE scenario to send master data out of SAP via an XML HTTP port. All goes well until the idoc receives error 02.
It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques. Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
Is there any solution to still use the standard ALE error handling ?

Hi Karin,
Looks like based on note 701597, you can only reprocess these idocs manually via a workitem. I qouted the relevant text below:
3. Error handling with status '02':
An HTTP IDoc in status '02' should not automatically be sent once again.
Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
However, this report was adjusted and now deletes all IDocs in status 02
to be routed to a HTTP port from the list of selected IDocs. IDocs to a
HTTP port in status '02' should only be sent manually via a work item.
Regards:
Rex

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 02 error

Similar Messages

Maybe you are looking for