IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

Similar Messages

PO Rejection - ORDSP Idoc Errors in ECC with different process codes

Hi All,
We were testing the Scenario where the Supplier rejects a PO line item as part of the PO Collaboration. On rejecting the PO in SNC, it trigerred an ROC XML with AcceptanceStatusCode == RE. The same was passed on from XML to Idoc in the IDoc segment E1EDP01, field ACTION = "003".
However, such ORDSP Idocs was failing on the ECC side during Inbound processing with the following errors:
1. Acknowledgment for PO item 4400000XXX 00010 contains quantity variance: Message no. ME794
2. Price unit 0 from IDoc differs from unit of purchase order 1: Message no. ME729
3. Order price unit differs from unit EA from purchase order: Message no. ME728
4. Order units differ : Message no. ME791
5. Material number differs from that of ordered material : Message no. ME790
Note : We dont get these errors for a normal confirmation. It happens only with Rejection.
The deletion indciator could not be set in the ECC PO line item even after manually correcting the above errors in the Idoc and posting it.
Then based on this SDN Post: [PO rejection in SNC does not update the items in MM with ORDRSP;, we changed the WE20 settings. i.e., for ORDSP Idoc changed the Process code from ORDR to ORDR_SUS. After this change, the the above errors were eliminated and the the rejection data was also updated on the ECC PO by setting a deletion indicator. But we are having the following issues:
1. Though both the confirmation & rejection data are getting transferred successfully, the Idocs remain in status 52 (Application document not fully posted).
2. The message in the status record is "Rejection of PO item 4400000XXX 00010 with reason: Message no. ME749
3. Came across these 2 related SAP Notes:
a. #1087422 : But this is not applicable as the note states that this error will occur only if we delete the PO line item before hand in ECC.
b. # 66192 : This note suggets a custom solution. But actually all the info from the ORDSP Idoc are getting processed successfully (Rejection & Confirmation send in the same Idoc). Only the status of the Idoc (Status = 52) is concerning us.
Looking forward for inputs / suggetions from those who have used the Rejection functionality in SNC without custom development.
Regards,
Bharath

Hi Bharath
Rejections is handled like that only, can you please check whether note 1529579 is helpful
It is standard behavior, as it expects other segments to fill, but never the less the PO will be updated properly, its only problem
with the status of the idoc....nothing wrong in the data updation. The above note should be handy.
Regards
Vinod

Vendor Master Replication Error from ECC to SUS : Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi,
Check
Re: Idoc Error Status "Entry in outbound table not found "
Looks like some issue with the partner profile set up for the sender or receiver of the EDI message in WE20.
Set up them again and When these have been set up try reprocessing your IDocs from BD87

File to idoc error

i am testing File to idoc scenario..
everything went smooth in XI...51 status error at ECC.
when i went into details..it says..Fill in all required entry fields
i tried checking those ..but its fine
what should be the error

Hey
When you execute the function module in foreground,you will see errors(if any) in red color along with the field which is giving this error(with explanation).fix that error and try to post IDOC's again.
to me it looks like the configuration is not in place to receive your IDOC,you might be passing some value which is not valid for proper configuration.
Like in my case i was giving wrong ship to party,this ship to party was not configured in R/3 hence IDOC was not posted correctly.
Thanx
Aamir

Inbound IDOC error :51 Passed with out Message Type to ALE Layer

Hi,
I am struct wtih the inbound IDOC scenario ..XI able to send IDOC but at ECC side it is in 51 red status and the error message is
"IDOC passed without Message type to ALE Layer"
Do I need to pass these segment values in Message Mapping? I didnt mapped any MESTYP,SNDPOR,SNDPRT and so on.. disabled these fields...
Could any one light on this issue?
Thanks
Rajeev

>
rajeev raj wrote:
> Hi,
>
> I am passing values in MM as below:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ZPORDCR01>
> <IDOC BEGIN="Constant">
> <EDI_DC40 SEMENT="Constant">
> <TABNAM>Constant</TABNAM>
> <DIRECT>Constant</DIRECT>
> <IDOCTYP>ZOrders</IDOCTYP>
> <CIMTYP>Constant</CIMTYP>
> <MESTYP>Z_Orders</MESTYP>
> <SNDPOR>B0009</SNDPOR>
> <SNDPRT>LS</SNDPRT>
> <SNDPFC>LS</SNDPFC>
> <SNDPRN>PD_100</SNDPRN>
> <RCVPOR>DEV</RCVPOR>
> <RCVPRT>LS</RCVPRT>
> <RCVPRN>Dev10</RCVPRN>
> <REFINT>GB</REFINT>
> <REFGRP>MTI</REFGRP>
> <REFMES></REFMES>
> <ARCKEY>20090909</ARCKEY>
> </EDI_DC40>
> <E1PORDCR SEGMENT="Constant">
>
> I am forwarding these values in MM... IDOC is successfully reaching in ECC but with 51 error in red... Logical system, post and message types are avaliable in Control record of the IDOC which received wiht errors in ECC.
>
> Thnaks
> Rajeev
Fill the TABNAME as EDI_DC40 and Direct as 2 (represents the inbound direction) and resend the idoc and check
Rajesh

IDOC Exceptions from ECC to email

Hi
I've been reading the SAP help on IDOC exception handling as I want all EDI IDOC errors in SAP ECC to be sent to a "user" as an email.    (I know this is not exacly an SAP PI question but thought I ask).
Any step by step guides out there ?

Hi
You can try the same by writing a function module.
The function module will reads the error message from ECC and then sends the email by calling another function module
the sample function module for email sending will look like this
CALL FUNCTION 'ZTEST_SEND_EMAIL'
      EXPORTING
        extcheck            = ''
        subject_long        = subject
        priority            = '5'
        bin_attachment_name = 'Failed error message'
        bin_attachment_type = 'BIN'
      TABLES
        it_content          = it_content
        it_bin_attachment   = it_attachx
        it_recipients       = it_recips.
The recipient needs to be crated using TCODE   SO23.

Sending IDOC from SAP ECC to SAP MII

Hello,
Issue while configuring.
I have configured the RFC Destination in the Netweaver message listener and when i check the connection in SM59 I got error as timeout during allocate of registered program and I have attached the screenshot of the error page.
I would request a reply asap.
Thanks,
Praveen

Hi Praveen,
First, I would suggest that you identify what version, and SP, of MII and ECC. Also the NW version and SP if applicable.
Second, use this custom Google search and terms MII, IDoc Listener, and perhaps SM59. There are many discussions on IDoc Listeners going back a number of years. Many of the issues with IDoc Listeners have not changed in most of that time, so look at the older ones as well. I presume that you found and are using my How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0) to set up your Listener? If not, you should review your configuration and setup procedure against it.
I have not looked at MII 14.0 or 15.0, but understand that the configuration of Listeners really has not changed since MII 12.1. So the document is still applicable.
Third, roughly 90% of the problems experienced with IDoc Listeners involve multiple uses of the self registering ProgID. Deleting it in one place, generally does not work. Use it in one place only. Create a new ProgID for each separate Listener (either type) on each separate MII instance for each ECC instance. Save yourself a lot of headaches. Never, ever reuse ProgIDs!!!
Fourth, most of the other issues involve a PI/XI system in the middle. Those are a bit more complicated since they rely on getting the connection configuration set up properly in PI. Since I am not that familiar with PI systems (most times it is not involved with the Listeners), I generally have to get other experts involved. Sometimes a CSS ticket is required.
Regards, Mike
SAP P&I Technology RIG

File to Idoc error:"Lock table overflow"

When I post 3000 records I see 3000 idocs generated in ECC successfully, when I try to post 4000 idocs I get an error in PI "Lock table overflow" in SM58, please help
Thanks

Hi.
The error could be due to following:
1. small size of lock table
2. a particular program sets a large no of locks
3. an update process hangs hence setting a large number of locks
please check below thread.
Lock table overflow
Also check below link frm help.sap.
http://help.sap.com/saphelp_nw70/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/frameset.htm
Hope this helps.
Regards,
Deepak.
Edited by: Deepak Shah on Feb 8, 2011 4:48 AM

"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

Hi all,
While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
Only a particular Idoc type is having this issue.
Below are the checks done before posting this query:
1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
2. Reloaded the meta data in PI for the particular Idoc type in issue.
3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
5. Restarted the inboundRA service in PI AEX.
Is there anything still missing. What could be root cause of this issue.
If anyone has encountered it before, pleases share the resolution.
Thank you
Younus

Hi Amit,
Thanks for the reply. Log viewer doesn't provide much help on the error.
The error desc says
"JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
regards,
Younus

** Not able to import IDoc from SAP ECC system

Hi Friends,
I am not able to import the IDoc from SAP ECC system in IR. I have checked that, hostname, client, server no. everthing is correct. I checked in SLD also. Host Name is correct.
While import (after giving the user name and password), I am getting the following error.
Problems to reach R3 System
What could be the probelm ?
Kindly help me friends.
Thanking you.
Kind regards,
Jegathees P.

Hi,
Just counter check following step
1. Go to SWCV definition tab select radio button for Import of RFC....
2. In Connection Data for Import from SAP System maintain correct System and correct Client.
3. Make sure you maitain ECC system in Central SLD.
4. In Import Screen check at the top of the screen have SAP System, is that system from where you want to import the IDOC.
With Regards
Sunil

SAP Inbox - IDOC Error

Hello All,
1. I am getting mail alert when ever any IDOC failed in ECC system. Is there any solution available to stop this type of messages coming to SAP Inbox? These notification messages are passing to SAP most of users.
2. Due to that their Inbox is getting full. And not able to delete all messages at a time. Is there any solution available to delete all messages once?
Lots of lots of error messags are coming in SAP Inbox for IDOC errror like: Partner profile not defined, IDOC not processed until Final stage, etc.,
regards,
Ansar.

Check the appropriate "Partner Profile" in WE20 and see if any agent is maintained for the
Post Processing - Permitted Agent.
Check the inbound and outbound parameters message types as well and seee if any agents are assigned or not...
try assigning a userid in test system and ensure the message goes to only the user mentioned..
Regards,
PR.

IDOC error:IDOC_ERROR_METADATA_UNAVAILABLE

I had followed the "How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener" atricle to setup IDOC Listenser completely.
When SAP ERP sent MATMAS message IDOC to SAP MII,I found error message in Netweaver as below:
com.sap.conn.idoc.IDocRuntimeException: IDocException occurred?
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:111)?
at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6643)?
at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6605)?
at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6763)?
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:959)?
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:937)?
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)?
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2630)?
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2307)?
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2139)?
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2021)?
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1912)?
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)?
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:321)?
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)?
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7233)?
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)?
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)?
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)?
Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.?
at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)?
at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)?
at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)?
at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)?
at com.sap.mw.jco.jra.idoc.JRAIDocRuntime.createIDocDocumentList(JRAIDocRuntime.java:104)?
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:69
Please give me any solution to resolve this problem.
Thanks

Hello Vincent,
Just make sure that you have hit the update button in MII Message Listeners after configuring IDOC listener in NWA.
Any changes made to listener in nwa will not get reflected unless you do update in message listeners.
Hope this helps!!
Regards,
Adarsh

Timeout error in ECC "INTERNAL.CLIENT_RECEIVE_FAILED Error while receiving by HTTP (error code: 402 , error text: ICM_HTTP_TIMEOUT)"

Dear Experts,
I am very critical situation due to this timeout error in ECC, please help me as much as you can. Go-live date is very near, but I am not getting any clue why this error is occurring. our ECC system is EHP 4, and PI is dual stack 7.4
My scenario is synchronous ABAP proxy to HTTP_AAE. request is triggering from ECC via proxy and reaching to third party (bank) through PI, I am reviving the response back in PI from bank. But from PI to ECC the response is not reaching. So in ECC after the defined Timeout limit its getting timed out.
I have tried everything by increasing the timeout in ECC more than 15 minutes in HTTP_TIMEOUT under SXMB_adm in ECC, but nothing worked, even if I am increasing for half an hour then also its getting timeout after half an hour.
response from bank to PI is coming within 30 to 40 seconds, but PI is not sending the response back to ECC.
This is classical scenario, and I have checked the trace via SXMB_Moni in PI as well as in ECC, in ECC its showing the timeout error, but in PI i did not see any trace for this error.
I have read many thread on SCN for the same error, and everywhere it has been suggested to increase the timeout, and I have tired that, it didn't help me.
All ABAP proxy configuration has been done as follows.
RFC destinations in ECC
LCRSAPRFC(TCP/IP)
SAPSLDAPI ((TCP/IP))
G type destination to path "/sap/xi/engine?type=entry"
G type destination SAP_PROXY_ESR to path "/rep"
All the destination connection test is working fine.
but i have a doubt on G type destination(AAE_XDJ) to path "/sap/xi/engine?type=entry" which is returns the status code 500 with message "Empty HTTP request received", is it ok with 500 ?
Configuration in ECC Integration Engine configuration is as follows
Questions
How the message gets pushed to ECC from PI, once the message received in PI, I believe by G type RFC destination on path "/sap/xi/engine?type=entry" , please clarify.
How to trace this, if message is not getting pushed to ECC, I mean I have checked the trace in PI XSMB_MONI, but didn't get anything for this error. In ECC SXMB_moni only I am able to the timeout error.
Please expert help me as soon as you can, this error really effecting me badly in front of management
Thanks,
Farhan

Hi Hareesh,
I configured the scenario based on ICO, and again I received the same timeout error in ECC.
I am really sick with this error, and I have raised the OSS message to SAP. Meanwhile I just want to double check my entire configuration with you. Please see the below configuration (for classical) for ABAP proxy to HTTP_AAE, and let me know if anything is wrong.
Request structure (ECC->PI->Bank)
<?xml version='1.0' ?>
<PaymentInfoMessage>
<PaymentInfoRequest>
<CompanyCode>Partner01</CompanyCode>
<BankCode>BSFRSARI</BankCode>
<StartDate>2006-07-09T00:00:00</StartDate>
<EndDate>2006-07-09T00:00:00</EndDate>
<TransactionType>940</TransactionType>
</PaymentInfoRequest>
</PaymentInfoMessage>
Response Structure (Bank->PI->ECC)
<?xml version="1.0"?>
<PaymentInfoMessageResponse>
<PaymentInfoResponse>
 <TransactionType>940</TransactionType>
 <SequenceNum>1</SequenceNum>
 <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
 <ProcessStatus>1</ProcessStatus>
 <Comment>No Comment</Comment>
 <TransactionData>:20:MT940-1007200601
:25:3210000079901
:28C:190/0001
</TransactionData>
 <CompanyCode>PARTNER01</CompanyCode>
</PaymentInfoResponse>
<StatusCode>OK</StatusCode>
<StatusDetail>OK</StatusDetail>
<ResponseItemCount>2</ResponseItemCount>
</PaymentInfoMessageResponse>
ESR Configuration
Please see the below screenshot for ESR config. I have created 4 data types, 4 message types, 2 Service interface (synchronous), 2 mapping and one operation mapping.
I just want to clarify about selecting the Request and response message type in inbound and outbound service interface.
<?xml version='1.0' ?>
<PaymentInfoMessage>
<PaymentInfoRequest>
<CompanyCode>Partner01</CompanyCode>
<BankCode>BSFRSARI</BankCode>
<StartDate>2006-07-09T00:00:00</StartDate>
<EndDate>2006-07-09T00:00:00</EndDate>
<TransactionType>940</TransactionType>
</PaymentInfoRequest>
</PaymentInfoMessage>
Response Structure (Bank->PI->ECC)
<?xml version="1.0"?>
<PaymentInfoMessageResponse>
<PaymentInfoResponse>
 <TransactionType>940</TransactionType>
 <SequenceNum>1</SequenceNum>
 <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
 <ProcessStatus>1</ProcessStatus>
 <Comment>No Comment</Comment>
 <TransactionData>:20:MT940-1007200601
:25:3210000079901
:28C:190/0001
</TransactionData>
 <CompanyCode>PARTNER01</CompanyCode>
</PaymentInfoResponse>
<StatusCode>OK</StatusCode>
<StatusDetail>OK</StatusDetail>
<ResponseItemCount>2</ResponseItemCount>
</PaymentInfoMessageResponse>
ESR Configuration
I have simply created 2 data types for requests(ECC->PI->Bank) and did one to one mapping. Similarly for response(Bank->PI->ECC) 2 data types, one to one mapping for this as well.
But I just want to clarify about selecting the Request and response message type in inbound and outbound service interface. please explain me this for synchronous interface.
Please see the below structure from ESR and inbound and Outbound service and let me know if the selection of Request and response message types is correct or not.
OutBound service interface
Inbound service interface
Thanks,
Farhan

IDoc error In case of ERS procedure, please enter terms of payment

Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
Thanks

Check
BAPI_PO_CREATE1 - E 06 436 In case of account assignment

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

IDoc Errors in ECC

Similar Messages

Maybe you are looking for