Configuring Communication Channel for a Receiver IDoc Adapter (AAE)

Prerequisites

You have set the adapter-specific properties to allow the IDoc adapter to recognize the receiver business system.

More information: Configuring the Adapter-Specific Properties
You have created an RFC destination for the receiver business system using the NWA. For example: XI_IDOC_DEFAULT_DESTINATION_SID

More information: Maintaining RFC Destinations
If you want to configure the communication channel in NWA mode, you must configure a JCA connection factory on the outboundRA resource adapter. If you want the communication channel in the NWA mode to receive ALEAUD from R3 system, you must clone a resource adapter from com.sap.aii.adapter.idoc.raclonetemplateRAR.

More information: Configuring Resource Adapters and JCA Connection Factories in NW

For more information about cloning resource adapters, see the section "Cloning Resource Adapters" under the link : Managing Resource Adapters

Procedure

Choose Create Object .
Choose Communication Channel .
In the Communication Component field, enter the name of the receiver system that you want to use.
In the Communication Channel field, enter a name for the receiver communication channel.
In the Edit Channel Screen , choose the Parameters tab, and enter the following properties:
1. In the Adapter Type field, enter the Java IDoc type. The Java IDoc adapter has the following properties:
  - Adapter Type: IDoc_AAE
  - Namespace: http://sap.com/xi/XI/System
  - Software Component Version: SAP BASIS 7.30
2. Choose the Sender radio button to indicate the type of communication channel.
3. In the Transport Protocol enter tRFC .
4. In the Message Protocol field, enter Idoc XML . By default, the Java IDoc adapter uses tRFC transfer protocol and IDoc XML message protocol.
5. In the Adapter Engine field, choose the advanced adapter engine which you want to use for Java IDoc processing.
On the RFC Parameters tab, proceed as follows:
On the RFC Parameters , choose one of the following options:
- In the RFC Client Parameters field, select Default (Recommended) and proceed with the following options:
  
  In the Destination field, enter the RFC destination of the receiver business system.
- In the RFC Client Parameters field, enter Manual and proceed with the following:
  1. In the SAP Client field, enter the client number of the receiver business system.
  2. In the User Name and Password fields, enter user name and password to connect to the receiver business system.
  3. If you want to secure the data communication paths between the adapter engine and the R/3 system using IDoc adapter, select SNC Mode and then perform the following substeps.
    1. Enter the SNC Partner Name .
    2. Select the SNC Level .
      
      Note
      The default level of protection is Level 8.
    3. Optional: Enter the SNC My Name .
    4. Enter the SNC Library Path .
  4. In the Language field, enter the ISO code of the language you want to use.
  5. In the Server Name field, enter the host name of the receiver business system.
  6. In the System Number field, enter the port of the receiver system
  7. In the Program ID (ALEAUD) field, enter the program ID which you used when you created the RFC destination on the receiver business system.
- Alternatively, you can reuse the configuration that is set in the SAP NetWeaver Administrator. In the RFC Service Parameters field, enter From NWA and proceed with the following options:
  1. In the Resource Adapter Name (ALEAUD) field, enter the name of the resource adapter that you have identified.
  2. In the Connection Factory Name (reuse NWA Configuration) field, enter the name of the connection factory that you created in the SAP NetWeaver Administrator.
Caution
Note that for the communication with non-SAP systems you can only use the configuration that is set in the SAP NetWeaver Administrator (setting From NWA ).
In the Interface Version field, enter Interface Version 4.0 or above .

By default, SAP systems prior to release 4.0 do not support Java IDoc adapter processing.
In the SAP Release field, enter 731 .
If you want to compile multiple IDoc XML of the same message type/IDoc type/CIM type into one IDoc, in the Outbound Message Settings section, select Packaging Required and enter the Package Size to specify the maximum number of IDoc XMLs to be put into an IDoc. It is also possible to specify the packaging timeout and packaging memory size in the channel configuration via the properties Package Wait Time (milliseconds) and Package Memory (bytes). See SAP Note 1973427 .
If the receiver system does not have the corresponding IDoc type and you want to choose an external metadata, choose Optional Parameter and select External Metadata Required.
Determine how you want to set the connection to metadata repository, and choose one of the following options.
- To use an existing RFC destination configured in NWA, In the Metadata Client Parameters , select Default (Recommended) and in the Metadata Client Parameters section, enter the Destination .
- To manually provide the connection details for the metadata repository, In the Metadata Client Parameters , select Manual .
  1. In the Metadata Client Parameters section, enter Metadata SAP Client .
  2. Enter the Metadata User Name .
  3. Enter the Metadata Password .
  4. Enter the Metadata Language .
  5. Enter the Metadata Server Name .
  6. Enter the Metadata System Number .
- To choose an existing connection factory configured in NWA as the destination for metadata repository, In the Metadata Client Parameters , select From NWA , and enter the Metadata Connection Factory Name .
  
  Note
  You use this option for debugging purpose.
If you want the receiver IDoc adapter to override the control record information, choose Advanced and choose one of following options.
- If you want the receiver IDoc adapter to ensure that the incoming payload has the control record, in the Control Record in IDoc XML , choose Mandatory (Recommended) .
  Note
  - By default this option is selected.
  - An exception is thrown if the control record is not present in the payload.
- If you want the receiver IDoc adapter to use the adapter specific XI information to update the control record of the incoming payload choose Not Mandatory in the Control Record in IDoc XML .
  
  More information: Java IDoc Adapter Partner Conversion
If the incoming payload has the control record, and if you want to override any of the control record fields, select the relevant options mentioned below.
- If you want to override all the fields of the control record, select Apply Control Records from Payload .
  
  More Information: The Control Record Fields of the IDoc Adapter (AAE)
- If you want only the sender partner fields namely SNDPOR, SNDPRN, SNDPRT and SNDPFC to be updated in the control record, select Apply Sender from Payload .
- If you want only the receiver partner fields (namely RCVPOR, RCVPRN, RCVPRT, and RCVPFC) to be updated in the control record, select Apply Receiver from Payload .
Set the Adapter Status to Active to enable the messages to be exchanged.
Save the communication channel.