WM interface to external system

[Former Member]

Have anybody ever configured WM interface to external system (t-code OMKY)?

I have a question here and hope you can help:

What's the naming rule when define Logical System, RFC destination, Port and Partner Profile? Should all be defined under one name? In my test, if I only define logical system and partner profile under same name (for example "ABC"), and maintain Port and RFC destination under another name say "XYZ", then I can only sent IDOC but I can't receive the IDOC sent from external system (for example, confirmation of transfer order).

Can anybody shed some light on this question? Your input is highly appreciated.

[Former Member]

Have anybody ever configured WM interface to external system (t-code OMKY)?

I have a question here and hope you can help:

What's the naming rule when define Logical System, RFC destination, Port and Partner Profile? Should all be defined under one name? In my test, if I only define logical system and partner profile under same name (for example "ABC"), and maintain Port and RFC destination under another name say "XYZ", then I can only sent IDOC but I can't receive the IDOC sent from external system (for example, confirmation of transfer order).

Can anybody shed some light on this question? Your input is highly appreciated.

[Former Member]

Hi,

You can define logical system, RFC destination, Port and Partner Profile with same name (i.e ABC).

For port you can define two directions for inbound and outbound with same name.

This also apply for setting partner profile (inbound and outbound) as well.

Regards,

Ferry Lianto

[Former Member]

Hello Ferry Lianto,

First thanks very much for your reply.

Must the four be maintained under same name? Before I thought that it’s enough to maintain logical system and partner profile under same name. Why should the port and RFC destination also use same name as logical system and partner profile? Would you please kindly show me the rule? I’ve checked online help and searched extensively on websites without any clear instruction.

In case of different name between logical system and port, would you please tell me why we can’t receive IDOC sent back by external system? Can’t they find the correct partner and port then send IDOC anymore?

[Former Member]

Hi,

Why should the port and RFC destination also use same name as logical system and partner profile? Would you please kindly show me the rule? I’ve checked online help and searched extensively on websites without any clear instruction.

In my experinces, usually I setup using the names and make easy for other developer to identfy the interface problems in production as well as for enhancement in the future. Just imagine if you are dealing with hundred interfaces (inbound and outbound) and you have different names for same interface.

Again, you could setup with different names for logical system, RFC and so on.

In case of different name between logical system and port, would you please tell me why we can’t receive IDOC sent back by external system? Can’t they find the correct partner and port then send IDOC anymore?

Well ... you need to tell the external system what names to use for partner profile and port as part of EDIDC data.

Regards,

Ferry Lianto

[Former Member]

Hi Ferry Lianto,

Again thanks for your reply. Now I am a little lost. In our test system, once I create logical system and partner under same name as the RFC destination, we can receive inbound IDOC from external system. But if I use name between logical system and RFC destination, we just can’t receive any inbound IDOC. Maybe I should ask the client to test one more time. We can get the result tomorrow.

Points rewarded. Thanks very much for your kind help.

[Former Member]

Hello guys,

I'm a funtional person and looking for the Idocs related to interface with WM. Could you please share it with me.

Thanks,

Anju.