Problem with File to IDOC scenario

[Former Member]

Hello,

I try to implement our first scenario to IDOC.

In TOC SXMB_MONI I have to errors

1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>

2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>

Any idea how I can solve this problems?

Elad

[Former Member · Accepted solution]

Hi Elad,

In addition to the above, you could also do the following:

1. Click on the service tab of your sender service and go to the adapter specific parameters.Fill in the logical system name there.

2. Or in the Header Mapping of the Receiver Agreement, you could specify the Sender service name.

Please reward points if helpful.

Regards,

Jyotika.

[Former Member · Accepted solution]

Hello,

I try all the steps in the answers that you sent and the errors is the same.

Maybe is mapping problems?

any new ideas to investigate?

Elad

[Former Member · Accepted solution]

HI,

Just now the same problem was got resolved just go through the below thread.

Thnx

Chirag

[Former Member · Accepted solution]

Hello,

When I try to update the LS name for Business Service in ID in the sender business service I received this message:

Check Result for Object aaa_Sender_Service Logical system DEV already exists in service | DEV400 SAP system ID DEV and client 400 already exist in service | DEV400

Elad

[Former Member · Accepted solution]

This logical system "DEV" is already used by another BS..Logical system name should be unique...

Give a unique name..

[Former Member · Accepted solution]

Hi Elad,

your logical system name has to be unique across all the Business Service/Business System.

That is the reason you are getting the errror.

Give a unique LS name for your business service.

Regards,

Sumit

[Former Member · Accepted solution]

Hello,

Thank you very much for all your help.

In Adapter specific identifier in need to fill 3 parameters:

IDOC adapter logical system:

R/3 system ID:

Client:

From where I need to take this 3 parameters

Elad

[Former Member · Accepted solution]

Hi,

If you are updating for Business Service you only need to enter details for Logical System.

Leave the others as blank.

Regards,

Sumit Khetawat

[Former Member · Accepted solution]

HI,

U can get the information: Go to SALE transaction u will get the information of IDOC adapter logical system and client from Define logical system and assign logical system to client tab.

U can alos get the information about the client information from system-> status

System ID information from -> SAP logon pad click on change item button.

Thnx

Chirag

[Former Member · Accepted solution]

Hello Chirag,

I think I close to the point.

If I'm not found the necessary data in TOC sale how can I add the information>

Do you have any information how I need to configure the sale?

Elad

[Former Member · Accepted solution]

HI,

I think u have not done the configuration at the R3 end....

Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....

File To IDOC - Part1 (SLD and Design):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

File To IDOC - Part2 (Configuration):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&

File To IDOC - Part3 (Steps required in XI and R3):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&

Thnx

Chirag

[Former Member · Accepted solution]

Hello Charig,

I start from the begin.

In first part what is:

Create the actions to send and receive vendor as follows:

Elad

[Former Member · Accepted solution]

HI,

Action is the part of Integration scenario in IR. if u design a IS in IR then u do not need to follow the configuration steps in ID. In the ID u just have to select Transport IS for IR and ur configuration is done.

In Action we specify the INbound and Outbound message types and assigned the action to the IS.

Hope I clear ur questions.

What I suggest is u just go through the link and check the configuration which is required at R3 end.

Thnx

Chirag

[Former Member · Accepted solution]

Hello,

We still looking for way to make our scenario without success.

If is this first time that we make scenario file to IDOC may we need to implement something new in our SLD?

Elad

[Former Member · Accepted solution]

I found the problem,

If I configure the same LS in xi and in the R/3 system is work.

Other way to solve this problem is to use with header mapping in receiver agreement.

Thank you for all your help

Elad

[Former Member]

Hi Elad,

check to see the adapter configuration for the Business System/Service you are using as Sender.

in the integration directory Service->Adapter configuration, there should be the Logical system name entered. ( hope you are connecting to Logical system)

this might be the problem that the Logical system entry is missing there.

tell me the status.

regards,

vinod

[Former Member]

Hello Vinod,

I solved the problem.

You can see my last post.

Thank you for your answer

Elad

[Former Member]

Hi Elad,

Go to SLD and check wheather ur rcvr business system has assigned any logical system name or not.Actually integration server is unable to find the rcvr BS in ur case.And this is due to the logical system name of the BS.

Check this blog for details.

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

Regards

Biplab

[Former Member]

Hi,

Please go through below weblog and thread I think it will solve ur problem

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

Thnx

Chirag