Show TOC

 CPIC: AS ABAP → AS ABAPLocate this document in the navigation structure

Use

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.

Initiator (AS ABAP)

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.

Acceptor (AS ABAP)

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:

  1. Call transaction SNC0 to maintain entries in the SNC system ACL (table SNCSYSACL).
  2. Create an entry for each AS ABAP server from other SAP systems that needs CPIC access to this AS ABAP. To create an entry, choose Edit → New entries; to modify an existing one, choose Goto → Details.
    Note

    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.

  3. Enter the application server's SNC name in the SNC name field.
  4. If you have not already done so, activate the Entry for CPIC activated indicator.
  5. If RFC connections are also to be accepted for this connection, then also activate the Entry for RFC activated indicator.
  6. If you activate RFCs for the destination, then enter the system ID of the initiating AS ABAP in the System ID field. You do not need to make an entry in this field for CPIC connections.
  7. Save the data.

Note the following:

  • The entries that you make at this time are saved as external entries (type = E).
  • In addition, you need to specify whether the accepting AS ABAP should accept CPICs that do not use SNC protection. To allow non-protected CPIC connections, set the profile parameter snc/accept_insecure_cpic to the value "1" (see Profile Parameter Settings on AS ABAP).
  • If CPICs are to occur within a single SAP system or on a single application server, then you also have to make an entry for the destination in table SNCSYSACL.
User Authentication

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.