Error in ALEAUD Idoc

Hi All,
When i send the MATMAS Idoc from ECC to XI, it is giving success and iam expecting the ALEAUD back to SAP.
If the ALEAUD idoc is posted successfully to ECC means ,the outbound idoc status will be turned into 39 status.Else it is in 03 only
when i check the status of ALEAUD, few of the Status is in 51 and saying the error as
Error when locking the audit statistics for DR2CLNT200 DWMS ZATEMATMAS
Please let me know the solution for this.
Regards

HI Vamshi,
This is a lock issue. When one idoc is trying to update a table and at the same time another idocs come to update it, then it will be locked.
In your case i believe the first ALEAUD got updated with success but when the second ALEAUD is upadting ECC, the third might have also reached thus locking it. If you can add some time delay in getting the response back then it might help with the lock issue.
Hope this helps.
Thanks,
Sudhir

Similar Messages

"ALEAUDIT IDoc cannot find request IDoc in Integration Server" error in PI

Hi Experts,
i am getting error "ALEAUDIT IDoc cannot find request IDoc in Integration Server" and
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code> in PI .
i am using ALEAUD.ALEAUD01 IDoc in my scenario.
i found two threads in SCN (scn.sap.com/thread/1370194,scn.sap.com/thread/1132815)but still i did not understand clearly for this issue .
Please clearly expline the solution for this issue in this thread ,i will give you points who post the correct solution.
Please send me solution for this issue clearly.
see the below payload also.
Thanks,
Aadi

the same problem
"ALEAUDIT IDoc cannot find request IDoc in Integration Server"
Could someone help with it?

Problem with ALEAUD IDOC

Helo everybody
We have this scenario:
JDBC>PI-(IDOC)---->SAP
SAP(ALEAUD IDOC)>PI----->JDBC
But we cant recive the Aleaud Idoc in PI. We get this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Anybodoy knows what´s happenning and how to solve it????
Thanks a lot

Christian Abad Chico wrote:
> Helo everybody
>
> We have this scenario:
> JDBC>PI-(IDOC)---->SAP
> SAP(ALEAUD IDOC)>PI----->JDBC
>
> But we cant recive the Aleaud Idoc in PI. We get this error:
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
> - 
> - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
> <SAP:Category>XIAdapter</SAP:Category>
> <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
> <SAP:P1 />
> <SAP:P2 />
> <SAP:P3 />
> <SAP:P4 />
> <SAP:AdditionalText />
> <SAP:ApplicationFaultMessage namespace="" />
> <SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
This IDoc is received by PI as acknowledgement. Hence it tries to correlate this to the request IDoc and is not able to find the request IDoc. The correlation used is the idoc number DOCNUM under E1STATE
So, If you are manually generating the ALEAUD Idoc through we19 make sure that you fill in proper Idoc number in the above field to get rid of this error.
> <SAP:Retry>N</SAP:Retry>
> </SAP:Error>
>
> Anybodoy knows what´s happenning and how to solve it????
>
> Thanks a lot
From the description of your scenario, You need to get the ALEAUD message as a request message as against acknowledgement. For that you need to use the program IDX_ALEREQUEST program in PI as suggested by others in your other threads. If this issue is already solved, Please close the same.
Best Regards,
Nageshwar

ALEAUDIT IDoc cannot find request IDoc in Integration Server

Hi,
i m working with a scenario SAP ECC 7.0 -> IDoc -> PI -> IDoc -> R/3 4.6c
I m sending a purchase order (ORDERS.ORDERS05) from SAP ECC and i want to receive an acknowledgment from R/3. Unfortunately there are only zeros in the field E1ADHDR / E1STATE / DOCNUM, this leads to the error "ALEAUDIT IDoc cannot find request IDoc in Integration Server" on PI.
Does anybody know what to do in the R/3 system to send the original IDoc number in E1STATE / DOCNUM?
XML Source of the ALEAUD received at PI:
<?xml version="1.0" encoding="UTF-8" ?>
<ALEAUD01>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>0000000004307392</DOCNUM>
<DOCREL>46C</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>ALEAUD01</IDOCTYP>
<MESTYP>ALEAUD</MESTYP>
<SNDPOR>SAPQV1</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>QV1CLT100</SNDPRN>
<RCVPOR>A000000022</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>QXC100</RCVPRN>
<CREDAT>20090605</CREDAT>
<CRETIM>111523</CRETIM>
<SERIAL>20090605111521</SERIAL>
</EDI_DC40>
<E1ADHDR SEGMENT="1">
<MESTYP>ORDERS</MESTYP>
<MESTYP_LNG>ORDERS</MESTYP_LNG>
<E1STATE SEGMENT="1">
<DOCNUM>0000000000000000</DOCNUM>
<STATUS>53</STATUS>
<STACOD>SAPV1311</STACOD>
<STATXT>&1 &2 wurde gesichert</STATXT>
<STAPA1>Terminauftrag EX</STAPA1>
<STAPA2>2510016042</STAPA2>
<STATYP>I</STATYP>
<STAMQU>SAP</STAMQU>
<STAMID>V1</STAMID>
<STAMNO>311</STAMNO>
<STAPA1_LNG>Terminauftrag EX</STAPA1_LNG>
<STAPA2_LNG>2510016042</STAPA2_LNG>
<E1PRTOB SEGMENT="1">
<DOCNUM>0000000004307353</DOCNUM>
<OBJTYPE>BUS2032</OBJTYPE>
<OBJKEY>2510016042</OBJKEY>
</E1PRTOB>
</E1STATE>
</E1ADHDR>
</IDOC>
</ALEAUD01>
Regards,
Udo

Hi Volker,
yes, that was the right hint
I needed to change the RCVPRT field to LS to force the receiving system to send the ALEAUD with original number at the right place. Strange reaction, but it is SAP software, he, he.
Regards,
Udo

ALEAUD idoc

Hi all.
I am following the How ToHandle Acknowledgments for IDoc guide.
I have posted 3 idocs into a BW system. The three idocs are similar but errors are produced in the system.
I made use of the program RBDSTATE and the variant SAP_AUDIT_SEND to send acknowledgements back to the XI server. However there is only one ALEAUD idoc sent back to the XI server and the ALEAUD only corresponds to the first idoc received in the BW system.
How can i send three separate ALEAUD for the three similiar idocs received in the BW system?
Appreciate any advice.

Check if the first ALEAUD idoc has the information of the remaining idocs too. And make sure that the packect size in partner profile is 1.
Regards,
Prateek

Aleaud idoc in status 56

hi i work in production support and new to idocs this is the problem given to me i have to solve it asap. when i check the idocs in we02 transaction it shows idocs in status 56 with a message ipartner profile inbound not available.
DETAILED DESCRIPTION OF PROBLEM.
inbound ALEAUD idocs that error with status 56.   These clog up & slow down
workflow- as we are getting over 10,000 of these per month.     For example:
when we work on inbound invoices that error, it's slower. (using transaction
SBWP)    I'm NOT saying ALEAUD idocs are related to inbound invoices, just
saying that SBWP gives us access to variety of idocs and it's been running
slower due to large amount of ALEAUD idocs erroring into workflow every day.
Best I can tell- looks like for every PO & PO Change idoc we send to
SupplySync, we get ALEAUD in response a few seconds/or a minute later.
**See examples on attached Word document, for date of 9/27/05.
Also I checked several different dates and the count/total number of:
PO documents sent    VS   the inbound ALEAUD idocs recvd- always matches
within a count of 1 or 2.
Ex: on 9/27/05     PO docs sent = 663       ALEAUD recvd = 664
Would like to have:
A) ALEAUD idoc creation stopped- if not serving a purpose
B) OR?- have them post successfully instead of erroring in workflow
Or- have workflow purged periodically, if can't do A or B above.
Regardless of how this is resolved- need backlog of ALEAUD purged from
workflow.
any kind of help in solving this problem would be great
thanks
noor.

Hi thanks for reply its very helpful if possible could you plz give more details about the oss notes 153205 it had a look at it talks about report RSWWCIDE to delete type c work items i also saw its selection screen
The selection parameters of the report have the following meaning:
id - ID of the work item -> please always restrict here !!!
cd - creation date of the work item
ct - creation time of the work item
commitc - number of the ContainerItems to be deleted for each LUW
del_log - also delete the history of the ContainerItems
disp - only list selected ContainerItems
does this report deletes the idocs does mean on id of work item i have to enter the idoc numbers which i want to delete and then all idocs nos i enter gets deleted is it so? can youplease give more details.
thanks

Missing ALEAUD idocs

Dear Experts,
For one of our existing interfaces for Delivery Idocs from R3>PI>third party; we have an issue with the ALEAUD messages. This configuration is in place since a long time. Some of the Delivery Idocs are in status 12 in R3 system and they do not have the corresponding ALEAUD Idocs- hence the staus remains 12 and does not get changed to 39. The third party application has been receiving these delivery Idocs; hence I am not sure why we do not have ALEAUD messages getting created for these. I have checked the below:
In R3 WE09 I have searched ALEAUD messages for the Idocs in status 12 with filter: Segment:E1STATE and Field DOCNUM and heValue <Original Delivery Idoc Number>. For the 39 status idocs I do find ALEAUD Idocs corresponding to th original delivery Idoc. But for the Idocs in status 12; as suspected; I do not find ALEAUD messages.
In PI SXI_Monitor; I do not know how to corelate/find the ALEAUD message for a specific Delivery Idoc message. But I checked with approximate timestamp randomly and could not find the ALEAUD message for my delivery. Is there any other way to find if an ALEAUD message is created for an Original message?Checked in Trace and reliable messaging in SOAP header, response header; but no luck. For 1 hr I could find 2000 messages and going through each of them individually is not an option. I do not have time/aprovals to implement content based search on my production box within a short duration to apply any filter to find these messages.
Can you please help and tell me
1. How can I find/correlate ALEAUD messages for an original message in PI?
2. What could be the reason that ALEAUD messages are not getting generated; only for some messages; eventhough the same has been received at the Destination?

My issue was solved.
After further analysis it was found that the ALEAUD messages are created from the response messages sent by the receiving 3rd part system. Eventhough the 3rd party system was receiving all our outgoing messages; they failed to process the acknowledgement or confirmation for some of the messages. Inturn we received no confirmation responses from the third party and hence the ALEAUD messages were not created for the same. After finding this, the same was informed to the thrid party system and they are fixing the message confirmation/acknowldgement processing from their side. So the issue was closed.
I had also raised an OSS message for this where the analyst had asked me to check the below.. Please go through the same for your issue. Maybe it will help you...
"I looked at the example IDoc messages and i found no request message
created by the external system. Please give us the message id that
for the request message id that should create and ALEAUD-IDoc
for IDoc xxxxxx. If this is missing in the system please contact
the administrator of the external system why this request messages
was not created.
I found 126890 messages in the system with system error, possible
one of these messages contain the information for your idocs.
transaction SM58 i found many errors with function module
IDOC_INBOUND_ASYNCHRONOUS, this function module transports IDocs
and these IDocs are possible missing in the receiving system ?
Please check the errors and try to correct them."
Thank you

Multiple ALEAUD Idocs are being generated per original Idoc

We have the following scenario in PI:
ERP (IDOC)> PI (JDBC)> 3rd Party
PI sends ALEAUD idocs back to ERP when the process is successful. Program RBDAPP01 is then ran on a schedule to update the ALEAUD idoc status, which in turn, updates the idoc status of the orignal idoc sent from ERP (03 to 12).
We just upgraded our PI from 7.0 to 7.1. Now, it seems multiple ALEAUD idocs are being created for each ERP outbound idoc. It used to be 1-to-1. From what I can tell, it look like an ALEAUD it created for every receiver. For example, if we sent one idoc and the data goes to 3 receivers, 3 ALEAUD idocs are created. This causes an issue because the first ALEAUD idoc will update the original outbound idoc to status 12, but any other ones will take it from status 12 to status 09. We want it to stay in status 12.
Any ideas why 7.1 would be any different?

This seems to be the standard behavior. I will explain it.
If an idoc comes and message is sent to say three receivers, all the three message should generate the ack unless they are not disabled. And in this case you will find multiple ALEAUD message at sender. In case the receiver adapters are like File, JDBC which do not support application ack, then ALEAUD won't be sent and you will receiver "Applicaition Ack Not Supported". With this error, if multiple ack are seen in sender then I guess they won't actually perform any update.
Regards,
Prateek

Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

Hi,
I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
Has anyone come accross this error before and if so, what is the resolution???
Thanks, in advance,
Pete

Hi Peter,
did you fixed it?
How did you?
got the same problem
Kind regards,
Michael

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
<i>CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only</i>
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
MenoN

Error when posting IDoc *** in system ERP100

Hi Experts!
Can you pls help me with a goods receipt issue?
When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
The same msg is getting displayed in RZ20.
On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
What can be the reason for this problem please?
What is in general the way to analyse and solve this kind of issue?
Thanks a lot !!
imre

Hi,
First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of BBP_DOCUMENT_TAB.
Hope this helps.
Regards,
Kalyan

Error Loading Hierarchy Error when updating Idocs in Source System

Hello Friends,
I am loading hierarchy data using Info pac into 0FUNDS_CTR . I have selected a hierarchy under hierarchy selections tab in the Info pac .
All Partner profiles in WE20 seems OK . But When I loaded data , throwing errrr message as below
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
When I checked in TC WE05 says that IDoc: 0000000000355113 Status: Error during syntax check of IDoc (outbound) with status 26 .
Please advice .
Many thanks

Hi Krishna4bi,
Actually we will monitor idoc status in BD87 in SAP BI As well ECC , while extracting the data from source sytem if any idoc struck we will manually process in BD87 , But you are telling that while loading the datasource the error occurred , so please check once in ECC side . Otherwise see how many packets are still process, make it red that infopackage and do manually update.
Hope it helps,
By,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://bluemarlinsys.com/bi.

Error when updating Idocs in Source System - Urgent

Hi Team,
When i was loading the data from SAP R/3 to BW, i was facing the error "Error when updating Idocs in Source System" (0 From 0 Records).
When i check in the Environment>Transaction RFC->In the Source System, it was displaying the error--
<b>" Import container contains errors (are any obligato) in the Function Module: IDOC_ERROR_WORKFLOW_START_R".</b>
Can any one please help me to solve this error.
This is am Urgent requirement for me to deliver.
Thanks & Best Regards,
Venkata.

Hello VenkaTa,
How r u ?
The workflow settings are not proper it seems. Ask the BASIS people to correct the Work Flow Settings. Then try Updating the IDOCs manually.
Also check the Inbound and outbound IDOCs in the Source system. The outbound should contain some warnings or errors.
Best Regards....
Sankar Kumar
+91 98403 47141

Error in ALEAUD Idoc

Similar Messages

Maybe you are looking for