Design approach help: SAP ALE config for 2 differrnt systems

[Former Member]

Hi,

Need inputs on the below Outbound scenario:

1. Can we send the same IDoc information to multiple applications (ex: Seebeyond middleware, SAP PI,etc.)

2. Currently there is an existing (ALE) flow which have been defined (SAP R/3 -> Seebeyond -> other application).

Can we have a parallel flow as shown for NW PI?

SAP R/3-----> SeeBeyond ---> other application

\ /

\ /

\ /

Netweaver PI

3. How do we create/maintain partner profiles in SAP R/3 system for two different applications? (Outbound parameters)

Thanks in advance,

Ravindra

[Former Member]

answered

[Former Member]

1. Can we send the same IDoc information to multiple applications (ex: Seebeyond middleware, SAP PI,etc.)

Yes.

2. Currently there is an existing (ALE) flow which have been defined (SAP R/3 -> Seebeyond -> other application). 
Can we have a parallel flow as shown for NW PI?

Yes.

3. How do we create/maintain partner profiles in SAP R/3 system for two different applications? (Outbound parameters)

Search on SAP Help / SDN.

[Former Member]

Hi,

The R/3 -> Seebeyond -> other application is an existing flow in Production which we do not want to disturb and it includes corrseponding ALE configuration steps like :

- RFC Destination (Type -T)

- tRFC Port

- Partner profiles (TA: WE20) : Includes outbound Idoc along with the tRFC port for the type Vendor(LI). I beleive we can assign only one port for a vendor at any given point of time?

- ...

- ....

Now,we intend to create a parallel flow, without distrubing the existing workflow, for PI with the ALE configuration (R/3 -> NWPI -> other application). In other words whenever a IDoc is triggered within R/3 system then the IDOC needs to be sent to two different middleware systems (Seebeyond and PI).

Is there any way to send the IDoc to two Different applications? If so within partner profiles, how we can assign the tRFC port of PI for the existing vendor.

I hope the requirement is clear. Any inputs would be appreciated.

Thanks

[Former Member]

Any Suggestions??

[Former Member]

Hi Ravi,

The partner profile is based on the parter type. It would be of type LS in your case for PI.

Now you need to create another LS as partner type for seebeyond. Assign the outbound IDOCs to this in we20.

then in we21 create a new port and specify this port for the above partner profile.

in the new port a new RFC connection could be mentioned.

Thanks,

Francis

[Former Member]

Hi Francis,

Within R/3 system we will define a LS for PI, will create a tRFC port in WE21, will create RFC Destination in SM59 (R/3 pointing towards PI)... (remaining ALE configuration..)

For defining the partner profiles having the doubt:

For the Vendor (ex:123456) of type LI within the outbound parameters the IDoc type (ex: INVOC) is assigned and if i double click on the IDoc type and check further outbound processing parameters.. there is already a tRFC port (ex: A00000032) assigned to it. The tRFC port refers to RFC destination (Type: T) for Seebeyond middleware.

Now the Question is how can i specify two ports within the partner profiles(we20) for that vendor and for the same IDoc?

Is there any other approach/alternative to handle the requirement?

Thanks,

Ravi

[Former Member]

try to use message variant option in we20.

[Former Member]

Hi Suresh,

Can we acheive this requirement with message variant functionality in we20? Could you please eloborate more..

Thanks in advance

Ravi

[Former Member]

Any suggestions ??

[former_member241146]

Hello Ravindra.

You can use the follow scenarios:

SAP R3 -> NW PI -> SeeBeyond

-> Other application 1

-> Other application 2

-> ....

The NW PI will be the middleware that exchange messages to other applications.

You will change the Receiver Determination so that the NW PI can exchange messages with every application.

Regards.

Bruno.