Ansicht
Dokumentation

ISS_V_SSCSSPROCTYPE - Define Self-Service Process Types

General Data in Customer Master   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

In this Customizing activity, you can add new self-service process types. The self-service process types gathers the various technical details that underlie a self-service process type. There is also an underlying ABAP wrapper class for each self-service. The process type is used to filter the self-services available to a user.

You can use this Customizing activity to register self-service process types and class interfaces in a client independent customizing table that facilitates the integration of self-services. Each self-service process type needs to implement at least one self-service process. The self-services are delivered using the self-service process types' ABAP wrapper class.

You have implemented an ABAP class (transaction SE24) with the interface IF_SSC_SS_PROCESS_TYPE.

The standard delivery includes three predefined self-service process types:

• MDG for master data management self services

• DIR for SAP Biller Direct self-service

• FCSfor factsheet self-services

You can use this Customizing activity to define the process types for your self-service solution. In general, you use a specific self-service process type for each connected application. For example Master Data Governance based self-services use the self-service process type MDG.

In some cases, for example for the predefined self-services enabled by the business function Internal Self-Services for Financials (FIN_SSC_ISS_1), three predefined self-service process types are delivered. After the business function is switched on, these self-service process types are available in the system.

However, you may also want to implement your own self-service process types. To do so you need to use the transaction SE24to implement the interface IF_SSC_SS_PROCESS_TYPE.

You must implement the interface for each new self-service process type that you define. The interface must contain the following methods:

• CHECK_AUTHORITY

This method must implement the self-service process type authority check. This method is used to filter the service map and the DDLB of the service requests business context. If the user does not have the authority to execute the service, the entries will be hidden. You need to return the value abap_true, otherwise it will not be possible to use the self-service during runtime.

• GET_SR_LINK_DETAILS

This method is used to return the detailed description from the business context of the CRM service request. You need to implement this method if you want to enable the launch of self-services from within the CRM service request.

• GET_PROCESS

This method reads the processes that are specific to the self-service type and maps it to the generic process ID. This method is required for system customizing and during the launchpad configuration for the self-services home page.

• GET_LOGSYS_OF_PROCTYPE

This method returns the logical system where the self-service process type is implemented. This is required for the integration of self-services with CRM service requests and the self-service home page. The system uses it to identify the system where the self-service is executed or where the self-service application should run.

• GET_URL_PARAM

This method needs to be implemented to map specific URL parameters. This is required for CRM and service map integration to append process specific URL parameters.

For example, for the MDG self-service process type (delivered as part of ISS for Financials), PROCESS= needs to be added to the URL.

• GET_APPL_URL

This method is optional. You need to implement this method if you want to use your self-services without configuring a launchpad in the CRM Interaction Center (IC). This method must return the URL and static URL parameters to launch the self-services application.

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4853 Date: 20240523 Time: 170954     sap01-206 ( 92 ms )