topic Re: Regarding inbound issue in Application Development and Automation Discussions

Regarding inbound issue

Former Member — Wed, 15 Apr 2009 17:03:19 GMT

Hi all,

Like, for outbound we use the port in the partner profile as a receiver port.

but for inbound idoc where, we use the defined port.

Regards

krishna

Re: Regarding inbound issue

Former Member — Wed, 15 Apr 2009 17:10:03 GMT


> Hi all,
> Like, for outbound we use the port in the partner profile as a receiver port.
> but for inbound idoc where, we use the defined port.
> 
> Regards
> krishna

Hi Krishna,


Define segments: WE31 
Create new basic idoc type: WE30 
Create message type: WE81 
Link message type to IDOC basis type: WE82 
Create RDC destination: SM59 
Create logical system: SALE 
Create port: WE21                                 "Declare Port
Create partner profile: WE20                  "Add port to Partner profile
Set up distribution model (If necessary): BD64


for indound and outbound we define port at same areas in we21 but we will mention the whether it is outbound or indound...

regards,

Prabhudas

Re: Regarding inbound issue

Former Member — Thu, 16 Apr 2009 03:37:02 GMT

Hi,

Port is the medium which carries the data from sender system to receiver system. Suppose you want to transfer data from system A to system B, then you need to define port at system A in transaction WE21, at system B port definition is not required.

Again if you want to transfer data from system B to system A, in this scenario system B will act as sender system then you need to define port here in WE21 otherwise not required.

Thanks,

Asit Purbey.

Re: Regarding inbound issue

Former Member — Thu, 16 Apr 2009 03:58:00 GMT

Hello,

You only need to create and assign port in Sender system, not in Receiver system for a messege type.

In the receiver partner profile in inbound parameter you have to assign the process code for the corresponding messege type.

Regards

Arindam

Re: Regarding inbound issue

Former Member — Thu, 16 Apr 2009 06:50:02 GMT

hi,

there is no port in recieving system .. u need to define the process code for the message type .

use think .

~linganna

Re: Regarding inbound issue

Former Member — Thu, 14 May 2009 06:23:24 GMT

Hi,

You will have to fill in the parameter "Port" only for any outbound messages (when you configure in WE20), which makes it clear that any partner sending messages from itself will have to have a port assigned to the outgoing message. If there is a necessacity to send any acknowledgement message from the receiver back to the sender, the acknowledgement message will be an outgoing message from the receiver's perspective, which will have a port attached to it.

~ Bineah.

Re: Regarding inbound issue

Former Member — Fri, 15 May 2009 03:38:57 GMT

Hi,

It depends on the Porttype we have to use.

eg: if it is a tRFC Porttype, defining port in the inbound system is not neessary.

if it is FILE porttype , we have to define port in the inbound system( in this case the inbound IDOCs are first transferred to a file and then sent for processing).

Thanks Sruthi .

Re: Regarding inbound issue

Former Member — Wed, 20 May 2009 11:04:31 GMT

For Outbound : Definition of port, partner profile and message control ( this is done in partner profile ) is required.

For Inbound : Definition of partner profile and process code ( this is done in partner profile ) is required.

If both are SAP systems then the port in the sender system is TRFC and idoc' s are transferred immediately to the receiving system . The process code is linked to function module which process the inbound idoc's( in the receiving system).

If the receiving system is Non SAP system then the idocs are collected in a file format and sent to receiving system. In the receiving system Background Jobs will be scheduled with program steps ( which will call the function module linked to the process code) which will process the file and application data posted.