Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Confused between inbound and outbound IDocs...

aris_hidalgo
Contributor
0 Kudos

Hello Experts,

Sometime I'm confused as to IDocs that we send to XI/PI system are still inbound and some are outbound. What is

the main difference between these 2?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

basically you need to differentiate inbound and outbound for each system. Sending an IDoc from Sys1 to Sys2 this IDoc is outbound for Sys1 and inbound for Sys2. The IDoc sent from Sys2 to Sys1 is outbound for Sys2 and inbound for Sys1.

XI / PI also differentiates between receiver and sender channels that are used to communicate with partner systems. A sender channel gets data from a system to XI / PI, while a receiver channel gives data to a other system. This can sometimes be confusing but you need to see it always from the (3rd) party's point of view, not from XI / PI.

Hope this throws some light in.

Kai

7 REPLIES 7

Former Member
0 Kudos

hi,

An IDoc is referred as a Outbound or Inbound with respect to the system you are referring,

Referred as Outbound Idoc from the source/ transmitting system &

as In bound Idoc at the target/receiver system..

Regards

Sharath

Former Member
0 Kudos

Hi,

basically you need to differentiate inbound and outbound for each system. Sending an IDoc from Sys1 to Sys2 this IDoc is outbound for Sys1 and inbound for Sys2. The IDoc sent from Sys2 to Sys1 is outbound for Sys2 and inbound for Sys1.

XI / PI also differentiates between receiver and sender channels that are used to communicate with partner systems. A sender channel gets data from a system to XI / PI, while a receiver channel gives data to a other system. This can sometimes be confusing but you need to see it always from the (3rd) party's point of view, not from XI / PI.

Hope this throws some light in.

Kai

0 Kudos

For example, Idocs DEBMAS and CREMAS is treated as inbound the idoc will be 'fetched' by PI.

0 Kudos

>

> For example, Idocs DEBMAS and CREMAS is treated as inbound the idoc will be 'fetched' by PI.

It's not based on the type of IDOC that it will be treated as inbound or outbound. Here is a simple explanantion:

Outbound(General):- That is going out of one system

Inbound(General):- That is coming In the System

Now, if we talk about XI/PI it is a miidleware whose job is to just make two systems communicate. so to avoid any confustion it consider the reverse terminlogy for itself. (As it is nothing to do with IDOC)

Outbound(XI) : So, a message coming into XI should be Inbound (If we talk about General meaning) But, XI being a middleware consider it as Outbound Only.

Inbound(XI) : A message going out of XI should be outbound (If we talk about General meaning) But, XI being a middleware consider it as Outbound Only.

Hope it's clear, ask for further clarification.

Sachin

abdul_hakim
Active Contributor
0 Kudos

Hi

Consider the below scenario:

You are sending an DEBMAS IDoc from SYSA to SYSB via XI/PI System.

This is graphically represented as SYSA->XI/PI->SYSB.

SYSA will generate an outbound idoc and send it to XI/PI System. This Idoc becomes the inbound idoc for XI/PI System.

XI/PI System inturn generate Outbound idoc and send it to SYSB. This Idoc becomes the inbound idoc for SYSB.

Hope this clarifies.

Regards,

Hakim

0 Kudos

Absolutely correct ;o)

Former Member
0 Kudos

hi,

Consider the case of basic type ORDERS which is used for both PURCHASE and SALES.

But the particular name is referred based on the system type.

i.e.

If its a sender system it will be a OUTBOUND and called as PURCHASE ORDER

and if its a receiver end it will be a INBOUND and called as SALES ORDER.

Regards

Sharath