Kontakt

Ansicht
Dokumentation

ICM_DFPS_INTEGRATION - Setting Up DFPS Integration

ICM_DFPS_INTEGRATION - Setting Up DFPS Integration

General Material Data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

This Customizing node describes the activities that are required for the following:

  • Secure connection between the systems in which Investigative Case Management (ICM) and Defense Forces & Public Security(DFPS) are located. We recommend setting up a bidirectional trustedconnection between CRM and DFPS.

You use these settings to launch Uniform Resource Locators (URLs).

Settings in the DFPS system

  • The authorization object S_RFCACL must be assigned to users who communicate with the CRM system (trusting system).
  • You have configured the Internet Transaction Server (ITS) and the ITS service "webgui" is active.
  • You have activated the business function DFPS_ICM_OF using transaction SFW5 (Switch Framework: Business Function Status Change).
In this activity you must configure the RFC destination (used to call the DFPS system) with the security option Trusted System (the Yes radio button is selected).
Note:
For any user who uses this RFC destination, a corresponding user (with identical name) must exist in the CRM system.
For more information about trusted systems, see SAP Library for SAP NetWeaver on SAP Help Portal at http:// help.sap.comand navigate to Trusted System: Trust Relationships Between SAP Systems.
  • You have assigned the RFC destination for the CRM system to the client in the activity Defense Forces & Public Security-> Investigative Case Management-> Specify RFC Destination for CRM System.
Note:
You cannot map two different clients in the ERP system to the same client in the CRM System.
  • You have defined the default Measure Type in the activity Defense Forces & Public Security-> Investigative Case Management ->Define Settings for Investigative Case Management.

Settings in the CRM system

  • You have defined the logical system using transaction Maintaining Logical Systems. This logical system must be the same as the one you have defined and assigned to the corresponding client in the DFPS system.
In this activity you configure the RFC destination (to call the DFPS system) using the security option Trusted System(theYesradio button is selected).
Note:
Any user who uses this RFC destination requires a corresponding user (with an identical name) in the DFPS system (trusted system).
For more information about trusted systems, see SAP Library for SAP NetWeaver on SAP Help Portal at http:// help.sap.com and navigate to Trusted System: Trust Relationships Between SAP Systems.
  • The authorization object S_RFCACL must be assigned to users who communicate with the ERP system (as a trusting system).
In this activity you configure the node that refers to the logical system for the DFPS system. For this node you assign a standard destination for BAPI calls.
  • Name of the logical system (of the DFPS system)

  • ITS client

  • URL of the ITS Server used for starting the "webgui" service.
    This URL uses the following syntax:
    http [or: https]://:///sap/bc/gui/sap/its/webgui/

    Note:
    You can use either the HTTP or HTTPS protocol.

If you use HTTP, you can leave the URL empty in transaction CRMS_IC_CROSS_SYS. The system automatically determines the URL for the HTTP protocol.
If you use HTTPS, you must assign the corresponding http server (host) and port. You can find the server and port data in the DFPS system using transaction SMICM and selecting Goto-> Services.
Once you have completed this activity, the system uses this mapped logical system to navigate to operation organizational structures.
  • You have set up the Use of DPS Integration for the relevant ICM case types in the activity Define ICM Case Types.

Use of DFPS integration is not activated as a default setting.






PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7410 Date: 20240523 Time: 184810     sap01-206 ( 98 ms )