ALE/IDOC configuration problem

[iamhe7806]

Hi Gurus,

It will be nice if you please help me finding the flaws in my configuration that is not allowing me to get a desired output.

Let me make it step by step:-

1. My desired output:- To see destination partner type as "LI/LF/ vendor name" for the Inbound IDOCs when an IDOC is starts it journey from "KU/WE/customer name" or vice versa

2. Present output:- Inbound IDOC always comes to "LS/ /TS90CLNT800". It means in my case inbound IDOC always comes to Logical System LS instead of LI or KU

How to configure it properly so that I can pass the Inbound IDOCS to other partner type except LS.

Please help.

Here what I have done so far as setting:-

1. Created a Logical System TS90CLNT800 using transaction SALE

2. Assigned it with client 8003. Created one RFC named tZRFC with connection Type "3"

(R/3 connection) using trxn SM59

4. Created a port ZEDI and assiged tZRFC using trxn WE21

5. Created partner profile for Vendors in partner type LI and for Customer in partner type KU

6. Because of getting error " no partner profile for ZEDI LS found" therefore created inbound parameters in parter profile LS for each Message Type.

I am processing IDOC within same client 800 ( both inbound and Outbound)

But I want the Inbound Idocs should come into partner type LI if the the Outbound IDOC is sent from KU and vice versa.

Please help me what config I need to do.

Amit

[Former Member]

All you need to do is the set the partners correctly.

Simply you must be knowing that even though if you are sending the idoc to some other system you will have to create a logical system for that and that would be treated as partner as well in your system.

Now, In WE20, if you select the destination partner. In the right side window you will have two options.

1) Outbound

2) Inbound.

If you are sending an Idoc to the partner which you have selected, then mention it in the outbound parameters.

If you are recieving an Idoc from the partner which you have selected, then mention it in the inbound paramters.

Hope this configuration is clear.

Thanks,

Babu Kilari

[Former Member]

From WE20 Check the processing code for both KU and LI,Is this different in both cases?

[soumya_jose3]

Hi Amit,

Try the below steps:

1) Define Logical System through SALE

2) Assign client to the logical system created.

3) Create RFC destination (say, ZTEST) through SM59.

Note that if the RFC destination name is the same as the logical system name of the receiver system, then ports will be created automatically while generating partner profile(step 5)

4) Maintain the distribution model through BD64

5) Generate the partner profile using BD82 for the distribution model created above.

6) Distribute the model using BD82.

Try the above steps and check if you still have any problem.

Regards,

Soumya.

[iamhe7806]

Hi Soumya,

Thank you for your suggestion.

I am facing problem on BD64 as per your suggestion. This is as below:-

I am using same system to process IDOC. I mean I want to create say Sales Order from a Purchase Order using IDOC message type ORDERS in the same system 4.6C.

Now I have created one Logical System ZEDI and assigned it to client. I created one RFC connection named tZRFC and one Port named ZEDI ( same name as logical system).

However, using BD64 when I want to map distribution model system asks for two different logical system.

What to do in this case?

Amit

[Former Member]

Amit,

In that case, while creating the RFC Conneciotn in SM59 give the target system as NONE. So, this way it points out to the same system.

Hope this would solve your problem

Thanks,

Babu Kilari

[iamhe7806]

Hi Babu,

Thank you very much for your post.

Can you please guide me on the question I have thrown while replying Sruthi

Regards,

Amit

[iamhe7806]

Hi all,

This problem is solved when I used message code FI for message type INVOIC for both Inbound and outbound parameter in Partner Profile.

Now Sender is LI/ /IN02_IN01( Vendor)

Previously it was LS/ /ZEDI ( Logical system)

and this is what I wanted.

Thank you all for your help.

Regards,

Amit

[Former Member]

Do the ALE settings like this.

Logical system : ZEDI (sender assigned to client)

create another Logical system - ZEDITEST. (dummy system. do not assign it to any client)

create partner profile. ZEDI with inbound configuration.

Give (SO) Message type,

Process code.

create partner profile ZEDITEST with outbound configuration.

Give (PO) Message type,

Basic type,

Port (with RFC destination pointing to the same system).

now in BD64. Sender ZEDI

Receiver ZEDITEST.

Thanks

Sruthi

[iamhe7806]

Hi Sruthi,

Thank you very much for your time that you have spent for my problem.

So far I created these type of partner profiles and they were working in the following fashion.

Partner Profile created in WE20:

Partner Type = LI, Partner Number V001 ( Vendor Number)

Partner Type = KU, Partner Number K001( Customer Number)

Partner Type = LS, Partner Number ZEDI ( Logical System)

I created one Logical System ZEDI and assigned it to Client

tRFC created in SM59:-

Connection Type = R/3 Connection, Name tZRFC

Port created in WE21:-

Port Name ZEDI (again) and assigned with tZRFC.

BD64 not used so far

Now If I add Message type ORDERS in Inbound Parameters of Partner Type KU and Outbound Parameters on Partner type LI system fails.

If I add message type ORDERS in Inbound Parameters of Partner Type LS and Outbound Parameters on Partner type LI system works fine.

Whenever IDOCs are being processed partner profile are being shown as follows:-

Outbound IDOC : LI/LF/V001 ( Receiver)

Inbound IDOC : LS/ /ZEDI ( Sender)

My question is that can I make any setting so that I get the following:-

Sender ( LI/LF/V001)

Receiver ( KU/WE/K001)

• LF and WE are respective partner functions

Regards,

Amit

[iamhe7806]

This session is closed