cancel
Showing results for 
Search instead for 
Did you mean: 

File-XI-Idoc Scenario

Former Member
0 Kudos

Hi All,

I created one scenario i.e file-XI-idoc Scenario. All IR & ID part over and when i am trying to execute this, the file is picking from the source directory. And i got the error in SXMB_MONI

i.e. "Receiver service cannot be converted into an ALE logical system"

under Call Adapter of Pipe line services.

Anybody came across this situation, please get back to me ASAP with the solution.

I am very thankful to you in advance.

Thanks & Regards,

Nagarjuna.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

IF u r using Business Service then only u can add it in ID.

if ur using Business System then u hv to add it in SDL.

For Business Sercive, before going to Adapter specific identifier, keep ur BS in Edit mode & then

click on service -> Adapter specific Identifires.

Hope its clear.

Thanks,

Maheshwari.

Former Member
0 Kudos

Hi Maheshwari,

It's Business System not a business service. O.K. it's clear.

But the actual problem is, the file is picking from source directory and deleted after 60 secs. And i got the error in SXMB_IFR i.e."Receiver service cannot be converted into an ALE logical system" in call Adapter fo Pipe Line services.

How i can solve this issue. Please let me know the solution ASAP.

I am very thankful to you.

Regards,

Nagarjuna.

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi,

Even i came across this situation once.Do one thing check whether u have assign the logical system name to business system in SLD.to check whether its define or not ,in configuration u can double click on business system GOTO

->SERVICE->ADAPTER SPECIFIC IDENTIFIERS.There u can see whether its there or not.Also at r/3 side while during ALE Settings give this same logical name and dont forget to assign to r/3 client .Also check partner profile is properly configured.

PLZ REWARDS POINTS

VIKAS JAIN

Former Member
0 Kudos

Hi Vikas,

The Business system is created in SLD and logical system is also assigned for the BS in SLD. the same LS created in R/3.

But, in ID, there is no entry for this LS in service-->Adapter specific Identifiers. i am trying to add LS here, but it's not editable and inactive state. How can i add this here, please let me know asap.

Thanks,

Nagarjuna.

Former Member
0 Kudos

HI,

manual entry is not possible in adapter specific identifiers,

u can delete business system and add necessary logical system in sld and import it manually.

regards,

pradeep.

Former Member
0 Kudos

Hi ,

Just check out these steps ..... this will definitely help u out

*************************************************************************************************************************

To Configure the FILE TO IDOC SCENARIO,PROCEED AS FOLLOWS

***********************************************************************************************************************

STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3

We need to do the following settings in XI

1) Create an RFC Destination to the Receiving System in transaction code (SM59)

a) Choose create

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#

e) Enter the Gateway host as same details above SID/URL

f) Gateway service is 3300+system number#

g) In the Logon /Security tab, enter the client, user & Password details of Destination system

h) Test the connection and remote logon.Both should be succesful

****************************************************************

2) Create Port Using Transaction Code IDX1

**************************************************************

a) Select Create New button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client

d) Enter the RFC Destination created in XI towards R/3

e) Save

*********************************************************************

3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)

**********************************************************************

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1

**********************************************************************************************************************

SETTINGS IN SAP R/3

***********************************************************************************************************************

We need to do the following settings in R/3

Logon to Sap R/3 System

**********************************************************************

1) Create an RFC Destination to XI in transaction code (SM59)

***********************************************************************

a) Choose create

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#

e) Enter the Gateway host as same details above SID/URL

f) Gateway service is 3300+system number#

g) In the Logon /Security tab, enter the client, user & Password details of Destination system

h) Test the connection and remote logon.Both must be succesful

***********************************************************************

2) Create communication Port for Idoc processing Using Transaction(We21)

***********************************************************************

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

***********************************************************************

3) Create Partner Profile with Inbound Parameters (WE20)

***********************************************************************

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang

Then Save

e) Select Partner no. and LS which were create above

f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter

g) Select Message type

h) Double click on Message Type and Then Enter the details for Message Type and Process Code.

I) save

*******************************************

4) In Transaction SALE, Create Logical System

*******************************************

a). Go to Basic Settings-> First Define logical systems

and then assign logical systems

b) Double click on Define the logical systems

c) Give data for your Logicaal System and Name

d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready

e) Assign the logical system name to the client

Jitendra_Jeswan
Contributor
0 Kudos

This is because You have Business Service at one side and Business System at other side

You need to use either a Business System both the sides or Business Service Both the sides. To do this you can use header mapping at the communication channel level.

Regards.

Jeet.

former_member859847
Active Contributor
0 Kudos

Hi Nagarjuna,

You have two business systems one for the FILE and second one for IDOC.

please assign the logical system name to reciver business sytem.

if already assighned please check it in ID.

in ID select the business system and display it .

check Service->adapter specific attributes.

where you can find the name of logical system .

if it is not there, u got the following error

"Receiver service cannot be converted into an ALE logical system"

reward points;), if your problem resolved.

regards

mahesh.

Former Member
0 Kudos

Hi Mahesh,

What you said exactly correct? i checked in ID for logical system in service-->adapters specific identifiers and there is no logical system name assigned.

I am trying to add the logical system, but it's not in editing mode, how can i add the logical system there.

Please let me know ASAP. I am waitng for your response.

Thanks,

Nagarjuna.

former_member208856
Active Contributor
0 Kudos

please create entry of your idoc in

T-code : IDX2 in XI

for idoc matadata,

Sandeep