User Details In RFC Type T Conn. for IDOC_AAE Sender

[former_member216579]

Hi All,

There is one doubt related to flow of IDOC in single stack .

We are using IDOC_AAE sender channel in Default mode , following are the configuration done :

In ECC :

RFC Destination Type T with Program ID and Gateway host and Service , here host annd service are of PO .

In NWA :

Resource adapter : inboundRA : here default destination name was maintained and the Same Program ID , Destination maintained here is of ECC .

My Question is :

Here we are not maintaining User details of PO server  any where not even in RFC destination Type T and neither in the Resource adapter but our data is flowing from our Application Server(ECC) to Integration Server(PO) , So where is the authentication done of the data flow between two server .

As per my understanding the while communication between two server the authentication is must .

Thanks

[former_member186851]

Hello Ankit,

Authentication is not mandatory all the time.

And as Bhargav mentioned and as per my knowledge the Program ID will act as layer for communication.

Lets wait for other experts comments as well.

[Bhargavakrishna]

Hi Ankit,

With IDOC_AAE sender  communication channel we can able  establish technical connection from SAP R/3 system to SAP PI system using RFC.

If you are using default option, a single resource adapter is shared between all the sender channels.

--> The PI system receiving the IDOC needs to query the sending R/3 system to understand the

structure of the received IDOC. An RFC connection is created for this purpose on the PI system.

--> A RFC destination is maintained in the PI system with details of the R/3 system to query the

IDOC structure.The destination maintenance stepenables the IDOC adapter to create a RFC

connection internally for metadata query of the IDOC structure.

--> The same RFC connection can also be used by the PI system to post IDOC acknowledgement

messages to the R/3 system once the IDOC has been successfully processed or when errors are

encountered by PI.

--> The PI system registers a Program ID with a web application server gateway to receive RFC

calls from the R/3 system. The gateway chosen is typically that of the PI web application server

but can also be that of the R/3 system.

--> Finally a RFC destination is created in the R/3 system. This destination allows the IDOC

layer in the R/3 to call the program ID that is registered on the RFC gateway either on the PI

system or the R/3 system.The RFC destination in the R/3 system is referenced in the IDOC port

configurations.

In NWA

The destination is used by the sender communication channel to retrieve the metadata for the IDoc

types that are processed on the communication channel.The destination must point to a SAP

web application server (e.g ERP) that contains the IDOC definition.

Regards

Bhargava Krishna