Network Communication and Security

The table below shows the communication paths used by the SAP Collateral Management (CM), the protocol used for the connections and the type of data transferred.

Communication Path	Protocol Used	Type of Data Transferred	Data Requiring Special Protection
Financial Customer Information System (FS- Business Partner)	RFC	Business partner master data
SAP Document Management System (DMS)	RFC	Document data
Loans Management (CML)	RFC	Loan data
SAP Business Information Warehouse (BIW)	IDoc and RFC	Collateral agreements, collateral objects, charges, collateral agreement – receivable assignment and calculations data
SAP Bank Analyzer (Basel II)	IDoc and RFC	Collateral agreements, collateral objects, charges, collateral agreement – receivable assignment and calculations data

The following RFC connections have to be set up for operating the CM. You are advised not to create the users belonging to these as dialog users.

· RFC communication with the Tool BW

· RFC communication within the Tool BW

· RFC communication in the context of import methods for the client copy. The relevant authorization objects are:

S_TABU_DIS; S_RS_ICUBE; S_RS_ADMWB; S_RS_ISOUR; S_BTCH_ADM; S_ADMI_FCD; S_BTCH_JOB; S_RS_ODSO; S_RS_ISET

CM provides the following business application programming interfaces (BAPIs) for allowing external systems to connect to it:

· BAPI_CM_AST_GET_MULTI

· BAPI_CM_CAG_CREATE

· BAPI_CM_CAG_GETDETAIL_MULTI

· BAPI_CM_CAG_GET_BY_RBL

· BAPI_CM_GENLNK_RBL_ON_RBL_01

· BAPI_CM_GENLNK_RBL_ON_RBL_02

· BAPI_CM_SEC_GETDETAIL_MULTI

· BAPI_CM_RE_GETDETAIL_MULTI

· BAPI_CM_RIG_GETDETAIL_MULTI

· BAPI_CM_MOV_GETDETAIL_MULTI

BAPIs are standard SAP interfaces and are important in the technical integration and in exchange of business data between SAP components and between the SAP and non-SAP components. BAPIs enable you to integrate these components. They are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the internet.

BAPIs allow integration at the business level and not at the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.

The current requirement for BAPIs in CM caters mainly to the migration scenarios. Hence these BAPIs are not protected by special authorizations. Authorization checks for BAPIs can be provided (in the future releases), if there are requirements for them.

CM also provides an extensive enhancement concept that offers user exits in the form of Business Add-Ins (BADIs).

Network Security and Communication Channels

Collateral Management (CM) uses the same communication channels that are described in the SAP Netweaver AS security guide. No further customer-specific communication channels are provided. Hence the aspects and actions described in the SAP Netweaver AS security guide (such as use of SAPRouter in combination with Firewall, use of Secure Network Communication (SNC), Communication Front-End-Application Server, connection to the database) also apply for CM.