Error oocuring after posting the IDOC

i am getting a error in a scenario

the scenario is Idoc to file. when we post the IDoc, its getting posted successfully. but the pipiline is getting failed at the inbound message when monitoring in SXMB_MONI.

i am getting the following 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>

all the experts help me out in solving this issue

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (5)

Hi Deepika,

their might be some problems with ur ALE settings.

Here is a detail of the steps to be followed.

Do verify whether u have done the steps or repeat the steps as stated:

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)

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

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.

Step 7)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

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)

IDx5(Idoc check)

SU53(authorization check)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi ..

i have checked the idoc status in SAP system using the transaction we20. its green.

but when we check the same idoc status using transaction idx5 in XI we r getting the error.

can any one help me out to sort this issue.

Thanks in advance

Deepika

Hi,

You are doing the idoc to file scenario.

the idoc sucessfully trigred from R/3 system, then status code of idoc should be 03.

here u are configuring for acknowlegemnt , for that you use the ALUEID idoc also.

please once again check the partner profiles of idoc

with t.code we20

regards

mahesh.

The Idoc is not reaching the XI system. We get the error when the Idoc is being checked with the transaction IDX5(X10 System).

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

When we post the IDOC in Run time workbench( used to test within XI), the message is successfully posted and received.

But when the same IDOC is being posted from SAP system, we are facing the issue.

With the transactions WE02 and WE05 (E10 System) the status of the IDOC posted in not 39

note: nice reward points will be awarded

Thanks

Deepika

Hi,

From error log, we can observe that

"attribute_no_request"- no request from idoc adapter

because of that it is showing an error as

"ALEAUDIT IDoc cannot find request IDoc in Integration Server".

please check once again inbound partner profile.

regards

mahesh.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

hi deepika,

I think u r working on synchronous scenario for IDOC to file .

for the IDOC the synchronous scenario is not just simillar to other scenario .responce message in IDOC is handeled by ALEAUDIT.

please go througt the following link how to handle respnce message in IDOC.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50...

some tome after doing so Errro may come please check the link below to handle some of the Error.

/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

rewards point if helpful

regards,

navneet

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Navneet,

its asyncronous scenario.after the Idoc is posted, when i check in SXMB_MONI, i am getting this error.dont know exactly if ita a problem with IDOC configuration or with XI.

Have you specify logical system in Integration directory for the Business service for the IDOC??

/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi ..

i am using a business system and not business service. is it necessary to include the logical system in Integration Directory?

Hi,

Have you loaded the Idoc Meta data in IDX2

Try with that

Regards

Seshagiri

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Seshagiri..

i have loaded the Idoc Meta data using IDX2. also the Cache is updated. still the problem exists

Have you checked wether you have recieved the file in the target system?

Hi..

The IDOC is failing to reach the inbound message in the pipeline.

none of the pipeline steps are executed. so their is no way possible for the file to be created in the target system

Ask a Question

Top Q&A Solution Author

User

Count