normal File to IDOC

[Former Member]

Hi Gurus ...

here i am working on a normal file to IDOC scenario. i am working on PI 7.0. here i am facing a problem .... i created a message type for the coming file. i created the message type and message interface even .... later i imported the idoc from the R/3 system.... after that as my file is having multiple records i gone for IDOC packaging.... for this i downloaded the IDOC and did the occurance change it to unbounded and imported into XI through External definitions ...later i went through the mapping program between the sender message and the receiver IDOC interface which we imported through External Definitions......later i went to interface mapping and did it between the sender message interface and the originally downloaded idoc type ....

i activated all the objects coming to Integration directory ... i created the service with my own name for the sender file system ...later for the receiver system i created the PARTY and SERVICE..and i configured the communication channels ...later i went through tthe creation of receiver determination ,,,..interface determination....sender agreement and receiver agreement ...

regarding the configuration i created the rfc destinations and parner profile and port ..... but finally when i try to test the scenario i am getting the error as ..

Receiver service XXXXXXXXXX cannot be converted into an ALE logical system.

for this i even check the business system in SLD also. the logical sysem name is there assingned to business system ....what else i can do to complete this scenario ....please help me out in this. \

[former_member189440]

Try to create the ALE settings one more time.

First create the logical system using transaction code bd54 .

and then create the rfc destination(sm59).

and create the Trfc port (we21).

and go to sale transaction to create the distribution model.

and assign the logial system name to the businness system in SLD or in Business syetm -

---

>Adapter specific Identifiers.

[Former Member]

take ur technical system as WEB AS ABAP .

and check in adapter spesific bussiness system

ther u need to fiend ur R3 system name and ip addres

clint details .

and check in communiacation channel u r given correct details or not .

like system name

port name

and sap release

[Former Member]

Hey,

yo need to create two logical system.

1 for SAP R3

2 for SAP XI.

Create them in SALE transaction of SAP R3.

The logical system that you have created for R3 assign a client to it.

Now use this logical system name in your technical system(WEB AS ABAP) in SLD.

Create a business system for the technical system.

Import the business system in ID.

open the business system.

In the service tab check the adapter specific Identifier.

the logical system name should be the same as mentioned in SLD.

Now if you have a Business service for your file sender.

Open the business service.

Goto the service tab

there wont be any logical system name in the adapter specific identifiers.

Assign the logical system that you have created for XI to this service.

Now your scenario should run properly.

regards,

Milan

Edited by: Milan Thaker on May 16, 2008 12:11 PM

[Former Member]

Hi Ramana,

You might be missed giving the logical system name in the below path:

ID>Business System>Adapter Specific Attributes.

Please make sure to give it.

Regards

Bhanu

Intelligroup.

[vijay_b4]

Hi Ramana,

have you tried: question 3 integration engine section

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

please check for the 'Adapter specific identifiers' entries in ID.

In Business System(R/3) 'Adapter specific identifiers' , do that 'Compare System Landscap Directory'

Reward points if this helps

Regards

Vani.

[Former Member]

In my opinion, you should be creating Business system of type WebAs ABAP in SLD. Make sure that port specified in the idoc comm channel is same as the one used in IDX2.

[former_member239282]

Hi,

go through the below weblog:

IDOC configuration

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Configurations required in R/3:

Maintain Logical System (SALE)

Define RFC Destination (SM59) which points to PI system

Maintain Port (WE21)

Maintain partner profile. (WE20):

Maintain Distribution Model (BD64):

bye

• if helpful reward points are appreciated

[Former Member]

Hi,

Clear SLD Cache........

Thanks,

Madhu

[GabrielSagaya]

make sure that your have assigned the logical systm name into your business system or the business service, whatever you are using. in case it is business system then it has to be maintained in SLD else in Integraion diectory.

and if you have maintained and it is still not appearing in integration directory, then from ID, do clear sld cache.

Double click the Business System/Business service

Goto--> Service menu select Adapter Specific and give the Logical system name.

This should solve the problem

[former_member556603]

Hello Ramana,

Go through the Micheal's Blog

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

Thanks,

Satya

Edited by: SATYA KUMAR AKKARABOYANA on May 15, 2008 4:56 PM