The SNC configuration for a CPIC connection to an AS ABAP (type = I in TXCOM) is almost identical to that for RFC internal destinations that do not use load balancing (see RFC: AS ABAP → AS ABAP), with the only difference being that you make your entries in the table TXCOMSECU instead of RFCDESSECU.
For the communicationpath between two AS ABAPs when using CPIC, the calling AS ABAP is the initiator of the communication and the AS ABAP that is defined as the CPIC destination system is the acceptor.
To specify the SNC options for the initiator (AS ABAP), use transaction SM54. See Maintaining CPIC Destinations and Their SNC Options Using Transaction SM54. The SNC name to enter in the SNC options is the destination application server's SNC name.
To be able to receive SNC-protected CPICs fromother AS ABAP servers, you need to specify the corresponding systems in the SNC system ACL (table SNCSYSACL).
In the accepting AS ABAP:
If you have multiple application servers in a remote SAP System that use different credentials (different SNC names), you need to make an entry for each application server in the table SNCSYSACL.
The table maintenance screen appears.
Note the following:
The SAP system performs the user authentication for CPIC connections with SNC in the same manner as for those without SNC. The user and password are always checked for authenticity.