Proxy to IDoc - IDoc error 51

Hi Experts,
I am working on the Proxy to Idoc interface . here message is successfully processed through SAP PI but giving an error on IDoc side.
Error : IDoc status record - 51
Enter date in the format __/__/____
I maintained the date format as shown above and mapping is also working fine, i can see the correct data in Sxmb_Moni (Receiver Payload). But some how when the data is send to HCM system, IDOC is generating this error.
Thanks in advance,
Kiran

Hi,
"personnel number(s) could not be locked" comes when the employee is already being access by some other process or report while your interface was trying to access it.
Have you used function module to like enque/dequeue to lock/unlock the employee? If yes then when the function module was trying to lock the pernr so that no one else can edit it simultaneously, it coulnt lock it and hence gave the error.
Also Make sure that you are not accessing the employee via transaction PA20/PA30 while triggerinf IDoc from WE19.
regards,
Deepak.
Edited by: Deepak Shah on Feb 17, 2011 10:31 AM

Similar Messages

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 Syntax Error E0072 with status 26 after upgrade to ECC6.0

Hi
We have upgraded SAP R/3 from 4.6C to ECC6.0. After upgrade, when we create PO and output EDI, we are seeing this IDOC syntax error E0072 for Mandatory Segment E1EDK01. In 4.6C it was working fine with no issues, only after upgrade this problem started. It says E1EDK01 is missing which is mandatory. We are using basic type ORDERS01 with no extensions. When we see WE30 it looks fine, WE20 settings looks fine.
Order of the segments got scrambled in upgraded version. First segment is E1EDP19001, this is supposed to be under E1EDP01 segment. There are two E1EDP19001 segments created but there were no sub segments to E1EDP01.
Any help in this regard is highly appreciated.
Thanks
Pandiri

User Exit activation and fixing the issue in user exit fixed this issue.

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 Receiver - IDoc with errors added

Hi All,
I am getting error in 56 - IDoc with errors added in receiver System.
I am new in Idoc - please tell me How to resolve this issue..
Thanks in advance..

Hi all thanks for reply .
All are the help full answer ,
I use T-code WE19 and change partner profile and execute now it is fine.
But i have checked all configuration regard partner profile from T-code WE20 it looking everything is fine but in Test tool for Idoc Processing by t-code WE19 i have checked it will taken wrong partner profile detail after giving correct manually now it is working fine.

IDOC AAE error:IDOC_ERROR_PARSE_FAILURE

Hello Gurus,
I am facing following error in IDOC AAE channel scenario is SOAP to IDOC we are using Integrated configuration.I have mapped all the attributes in the IDOC to 1 and date formats are fine.On Analsys i found for the IDOC Field MENGE is not accepting Decimal values when the value 868.000 is passed IDOC AAE is failing with following error.
When i pass with out decimal like 868 Idoc is posting successfully.
using connection
File_http://sap.com/xi/XI/System failed, due to:
com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to
idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException
occurred while parsing IDocXML for type :state=READING_FIELD_VALUE_TAG,
charPosition=441, lineNumber=1, columnNumber=442" tabIndex=0
ti="0" lsdata="{0:'Transmitting the message to endpoint using
connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:
An IDocConversionException occurred while parsing IDocXML for type
:\nstate=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1,
columnNumber=442',7:true}" ct="TV"
bMarkedAsFocussed="true" bResetTabIndex="true"Transmitting
the message to endpoint <local> using connection
File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:
An IDocConversionException occurred while parsing IDocXML for type
<Z2MAK075IDOC>:
state=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1, columnNumber=442
I have explored through forum but i didnt find exact solution how decimal values can be handled in IDOC AAE .Please through some light on the issue any help is higly apprecaited.
Regards
Praveen Maareddy

Hi Praveen
Looks like it will not allow dot(.) or comma(,) .
Check this
A numc field will not allow you to post values like '.' or ',' to it. You need to get rid of the decimal point/comma. You can do that by multiplying the value by 100 or 1000... depending on your decimal places. Then it is possible to post that values to a numc field. A numc does allow only the numeric characters from 0 to 9. If this is not what you want (because you are dealing with an characteristic) you need to use a char infoobject or you need to use a keyfigure.
Problem with conversion char to numc in transference rules
You can change the data type of MENGE like below
result TYPE p LENGTH 8 DECIMALS 3.

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

Idoc INVOIC - error Tax entry not possible in this item - Message no. FF724

Hello,
I have an idoc in error with the following error message.
In the idoc type INVOIC
Segment E1EDK04:
MWSKZ     N1     VAT indicator
MSATZ     19.000     VAT rate
MWSBT     20.52     Value added tax amount
In OBCD
Partn.Type PartnerNo Tax type Tax rate Cty Tx
LI         FNISL     N1       19.000       V2
Input tax N6 is defined in the system with rate 19.000%
Direction         2     Inbox
Current status    51
Basic type        INVOIC01
Extension
Message type      INVOIC
Partner No.       FNISL
Partn.Type        LI
Tax entry not possible in this item
Message no. FF724
Diagnosis
You can not enter a tax amount in this item since, due to the posting amount entered and the tax code, a total tax amount of zero has been calculated.
This could either be due to the fact that the tax code has been defined with a value of 0%, or because the posting amount entered (that is, the tax base) is too small.
Example:
With a tax rate of 15%, a tax amount greater than zero will only be achieved with a base amount greater than 0.04. With values of 0.03 and less, it is therefore not possible to enter a tax amount.
Procedure
Only enter tax amounts in conjunction with tax codes for which a percentage rate not equal to zero has been defined. Make sure that in documents with several G/L account items you enter the total tax amount in an item with a sufficiently high posting amount.
do you have an idea to solve it?
Regards
Arnaud

Message no. FF724
Check note 681538
thanks
G. Lakshmipathi

HRMD_A IDoc in error not raising an event

I have workflows enabled for IDocs in error.
If an inbound order IDoc (ORDERS) arrives in status 51, it triggers a workflow.
If an HR master data IDoc (message type HRMD_A) arrives in status 51, no workflow is triggered.
Here is what I have checked:
Partner profile has me as responsible agent in both cases.
Both type linkages are active for IDOCHRMD and IDOCORDERS event InputErrorOccurred.
Both IDocs types are posted in with the test tool and end up in status 51.
When I investigate the event trace, I can see that an event is raised for the ORDERS IDoc but not for the HRMD_A IDoc.
There are no errors in the type linkage status column.
So why would it be that the event is not being raised for the HRMD_A IDoc?
How can I find out what should be raising the event? I guess that there is a function module call to SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT.
Kind Regards,
Tony.

Hi Tony,
I am a complete novice to workflow but I have a requirement liek yours to trigger workflow for idocs in error, so I was hoping you could point me in the direction of some documentation/steps on how to do this?

RBDMANI2 for IDOCs in error not working in Background..

Dear All,
 We have an ALE-IDOC scenario in which our IDOC gets posted in the destination system with status 51 as per business reqt. We schedule a job in the background using program RBDMANI2 which is used to manually reprocess IDOCS in error.
 This background job was working fine in the 4,7 R/3 Server, but we have upgarded the receiving system to ECC 6.0. Now the problem is dat when we try to reprocess the IDOC using this job, the IDOC are not processing further.. It ideally is supposed to do further processing as per the code writen.
We tried debugging the code(RBDMANI2) in background. But, its not helping.
Kindly advise.
Regards,
Santosh Reddy.

On primary research I found that there is a call to this FM 'SAPGUI_PROGRESS_INDICATOR' .
In that FM see line 12.
IF SY-BATCH <> SPACE.
 EXIT. "do nothing in batch
 ENDIF.
May be this is the cause of your error.
Rhea.

Vendor Confirmation workflow ( TS00008075 ) issue for IDOCs in Error ( 51 )

Hi All,
          When IDOCs (Basic type: ORDERS02, Message type : ORDRSP ) goes in error with status 51 & comes to SAP system it calls event u2018INPUTERROROCCURREDu2019 which is correct but it creates problem when it get re processed as it triggers event u2018INPUTSUCCESSu2019 resulting in firing vendor confirmation workflows to respective user ( this batch job re process each ORDRSP IDOC twice a day & hence 2 workflows per IDOC in error to clientu2019s inbox by triggering event u2018INPUTSUCCESSu2019).
Could you please tell me why these IDOCs are triggering event u2018INPUTSUCCESSu2019 in case of error ( status 51 ) when they get RE PROCESSED. These kind of Idocs must only trigger u2018INPUTERROROCCURREDu2019 once and should not create anything when these get reprocessed. Please note that these issues arise after EHP4 upgrade. Please let me know if any setting is there for triggering Vendor COnfirmation workflow ( TS00008075 ) when IDOCs in error get re processed.
Please help us , thanks.
Regards,
Kartikey Rawat.

Hello Kartikey Rawat !
                    INPUTSUCCESS event gets fired just because it is configured as terminating event in the task.
                    If you don't want this event to get fired, either you can deactivate it or delete the bindings related to the event INPUTSUCCESS(doing so should not affect other two terminating events that may be required for you scenario) .
                    If you want know why it is fired, you can get to know in debug mode or check whether the event is defined through related function modules configured in WE57,BD51,WE42 AND WE20 transaction codes.
                    In WE05 or WE02 transactions, you will get error description.Based on it too, you can figure out the reason.
Regards,
S.Suresh

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

Idoc receving errors

Hi,
This is my program. When i executed this program iam getting these errors . If any one knows pls help.
Exception in thread "main" java.lang.ExceptionInInitializerError
 at JcoIdocSample1.main(JcoIdocSample1.java:36)
Caused by: com.sap.mw.idoc.IDoc$Exception: (8) IDOC_ERROR_INITIALIZATION: Could
not initialize SAP Java Connector IDoc Class Library. Found SAP Java Connector v
ersion 2.0.12 but version 2.1.8 or a higher patch level is required.
 at com.sap.mw.idoc.jco.JCoIDoc.<clinit>(JCoIDoc.java:128)
This is the program
import com.sap.mw.idoc.*;
import com.sap.mw.idoc.jco.*;
import com.sap.mw.jco.*;
This sample program demonstrates how to create a simple Material Master IDoc
(MATMAS02) from scratch, fill it with sample data and send it to an SAP
system.
@version 1.0
@author SAP AG, Walldorf
public class JcoIdocSample1
 public static void main(String[] args)
 try {
 //create a JCo client pool
 JCO.addClientPool( "MyPool", //pool name
 3, //maximum pool connections
 "800", //SAP client
 "INTFACE_USER", //user ID
 "**********", //password
 "EN", //language
 "5.137.151.198", //app server host name
 "00" ); //system number
 //create an IDoc repository
 IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
 //create a new and empty MATMAS02 document
 System.out.print("Creating IDoc...");
 IDoc.Document doc = JCoIDoc.createDocument(idocRep, "MATMAS02");
 //get the root segment from the document
 //The root segment does not contain any fields or data. It is only
 //used as the standard parent segment and won't be transmitted when
 //the document is sent to an SAP system.
 IDoc.Segment segment = doc.getRootSegment();
 //create and add a new and empty child segment of type E1MARAM
 //and fill the segment data
 segment = segment.addChild("E1MARAM");
 segment.setField("MSGFN", "005");
 segment.setField("MATNR", "BOXCOOKIES");
 segment.setField("ERSDA", "20020801");
 segment.setField("ERNAM", "TIGGER");
 segment.setField("PSTAT", "KBG");
 segment.setField("MTART", "FERT");
 segment.setField("MBRSH", "L");
 segment.setField("MATKL", "G1113");
 segment.setField("MEINS", "PCE");
 segment.setField("BLANZ", "000");
 segment.setField("BRGEW", "0.550");
 segment.setField("NTGEW", "0.000");
 segment.setField("GEWEI", "KGM");
 segment.setField("VPSTA", "KBG");
 //create and add a new and empty child segment of type E1MAKTM
 //and fill the segment data
 segment = segment.addChild("E1MAKTM");
 segment.setField("MSGFN", "005");
 segment.setField("SPRAS", "D");
 segment.setField("MAKTX", "Schachtel mit Keksen");
 segment.setField("SPRAS_ISO", "DE");
 //create and add a new and empty sibling segment of type E1MAKTM (same type)
 //and fill the segment data
 segment = segment.addSibling();
 segment.setField("MSGFN", "005");
 segment.setField("SPRAS", "E");
 segment.setField("MAKTX", "Box of cookies");
 segment.setField("SPRAS_ISO", "EN");
 //create and add a new and empty sibling segment of type E1MARCM
 //and fill the segment data
 segment = segment.addSibling("E1MARCM");
 segment.setField("MSGFN", "005");
 segment.setField("WERKS", "0001");
 segment.setField("PSTAT", "BG");
 segment.setField("PLIFZ", "0");
 segment.setField("WEBAZ", "0");
 segment.setField("PERKZ", "M");
 segment.setField("AUSSS", "0.00");
 segment.setField("BESKZ", "E");
 segment.setField("AUTRU", "X");
 //create and add a new and empty sibling segment of type E1MBEWM
 //and fill the segment data
 segment = segment.addSibling("E1MBEWM");
 segment.setField("MSGFN", "005");
 segment.setField("BWKEY", "0001");
 segment.setField("VPRSV", "S");
 segment.setField("VERPR", "0.00");
 segment.setField("STPRS", "15.50");
 segment.setField("PEINH", "1");
 segment.setField("BKLAS", "7920");
 segment.setField("VJVPR", "S");
 segment.setField("VJVER", "0.00");
 segment.setField("VJSTP", "15.50");
 segment.setField("LFGJA", "2002");
 segment.setField("LFMON", "08");
 segment.setField("PSTAT", "BG");
 segment.setField("KALN1", "000100126602");
 segment.setField("KALNR", "000100126603");
 segment.setField("EKALR", "X");
 segment.setField("VPLPR", "0.00");
 segment.setField("VJBKL", "7920");
 segment.setField("VJPEI", "1");
 segment.setField("BWPEI", "0");
 //prepare document for sending and set the appropriate control data
 doc.setMessageType("MATMAS");
 doc.setRecipientPartnerType("LS");
 doc.setRecipientPartnerNumber("TSTCLNT000");
 doc.setSenderPort("SAPJCOIDOC");
 doc.setSenderPartnerType("LS");
 doc.setSenderPartnerNumber("JCOCLNT000");
 System.out.println(" done.");
 //check the whole document's syntax
 try {
 System.out.print("Checking IDoc syntax...");
 doc.checkSyntax();
 System.out.println(" done.");
 catch ( IDoc.Exception ex ) {
 System.out.println(" Syntax error: " + ex);
 System.exit(0);
 //get a JCo client from previously created client pool
 JCO.Client client = JCO.getClient("MyPool");
 //create a new transaction ID
 String tid = client.createTID();
 //send the document to the SAP system asynchronously
 System.out.print("Sending IDoc...");
 client.send(doc, tid);
 //confirm the transaction ID
 client.confirmTID(tid);
 System.out.println(" done.");
 //release the JCo client and return it back to the pool
 JCO.releaseClient(client);
 catch ( java.lang.Exception ex ) {
 System.out.println("Application error: " + ex);
 }//method main
}//class JCoIDocSample1

You can see the problem in the error message that you get: Could not initialize SAP Java Connector IDoc Class Library. Found SAP Java Connector v ersion 2.0.12 but version 2.1.8 or a higher patch level is required at com.sap.mw.idoc.jco.JCoIDoc.
Below is the comment from SAP for JCo IDoc class library 1.0.8, which you are utilizing:
The "IDoc Class Library 1.x" consists of two parts: a "Base IDoc Class Library" and a "Connector IDoc Class Library". Both parts are required. The SAP Java Connector IDoc Class Library 1.0.8 needs SAP JCo 2.1.x, where x is at least 8, and a JRE/JDK 1.3 or 1.4.
So it's clear that you'll have to upgrade your JCo library and download version 2.1.8 (instead of your used version 2.0.12).
Best wishes, harald

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

Proxy to IDoc - IDoc error 51

Similar Messages

Maybe you are looking for