Ansicht
Dokumentation

CRMS4_IU_CM_CUSTC - Modify Process Definition (Client-Specific)

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

Using the client-specific process configuration, you can override processes defined in the cross-client Customizing activity and in some cases supplement them with a client.

This means that the process configuration that is ultimately executed corresponds to a combination of cross-client and client-specific customizing.

The following views are available:

• PI Process

• PF Process

• PF Process Parameter

• UI Process View

• UI Process Context

• UI Process

• UI Process Parameter

• UI Process Steps

• UI Process Step Requirement

• UI Process Step Binding

• UI Process Business Role Assignment

In general, the client-specific process configuration works as follows:

• You can only modify objects at the first level (processes, UI process views and the UI process context). This means that only objects that have already been defined independently of the client can be used here.

• Objects at the lower levels can be modified and supplemented. For example, additional PF process parameters can be defined for an existing PF process.

• If an object is overridden on a client-specific basis, only the attributes of the object that are filled in client-specific Customizing are overridden. If an attribute is empty in the client-specific Customizing, the corresponding value from the client-independent Customizing is used.
  The only exception to this are the "Active" checkboxes. If a checkbox is set to "Active" in cross-client Customizing and not set in the client-specific one, the entire checkbox is not set.

PI Process

(PI - Product Integration)

In this view, the cross-client-defined PI processes are overridden on a client-specific basis.

PI processes are the interface of the CM to IS-U. Their task is to implement the CM processes technically.

Example:
When creating a new contract in CM, the PI process ensures that the move-in takes place in IS-U and that the asset can be settled according to the utilities products selected.

PI processes are defined by their technical name, to which an ABAP class implementing them is assigned. PI processes are referenced by PF processes using this technical name.

In the Customizing provided, class CL_CRMS4_IU_CM_PI_PROCESS is used for all PI processes. Customer implementations must be derived from this class.

PF Process

(PF - Process Framework)

In this view, the cross-client-defined PF processes are overridden.

PF processes map the business logic of CM processes. Their task is to check input parameters and implement the CM process technically in IS-U using the PI processes and to manage the utilities sales contract.

PF processes are defined by their technical name, to which an ABAP class implementing them and a PI process are assigned (using its technical name).

The Customizing provided contains PF processes for all CM processes with appropriate classes. The delivered classes are derived from the class CL_CRMS4_IU_CM_PF_PROCESS. Customer implementations must be derived from this class.

PF Process Parameter

PF processes basically work with the values available in the utilities sales contract, such as the start date of the contract. Additional parameters can be assigned to a PF process using this view.

The parameters are defined as a pair consisting of the attribute name and attribute value. The length of the attribute value is limited to 200 characters. To ensure the transfer to the PF process works correctly, the implementing class must have a public attribute with the same name as the attribute name. These attributes are automatically filled with the values defined in this view when the PF process is initialized.

To override or supplement the parameters of a cross-client-defined PF process, the PF process itself must first be overridden. Subsequently, in this view either existing parameters can be changed or additional parameters can be added. Parameters that should not change do not need to be redefined here. They are automatically adopted by the cross-client-defined PF process.

UI Process View

In this view, the cross-client-defined UI process views can be overridden on a client-specific basis. No additional UI process views can be added.

The UI process views depict the CRM WebUI views from which the UI processes of the CM can be set up. The views can come from any UI components.

A UI process view is defined by its technical name. The following technical properties are assigned to this:

• Component Name
  Name of the UI component that contains the view

• Window Name
  Name of the interface windows of the view
  Full window name: [UI component] / [window name]

• Inbound plug, which is used to enter the view

UI Process Context

In this view, the cross-client-defined process contexts can be overridden on a client-specific basis. Technically, the process contexts are additional, dynamic context nodes that exist in all component controllers. Their context is implemented by a class derived from the class CL_CRMS4_IU_CM_UI_PROCESS_CTXT. A UI process context is defined by its technical name, which is assigned an implementation class. This must be derived from CL_CRMS4_IU_CM_CN_NODE.

The name of a dynamic context node corresponds to the technical name of the UI process context.

UI Process

In this view, the cross-client-defined UI processes can be overridden on a client-specific basis. At this point, no new UI processes can be defined.

If only one of the dependent objects, such as the process steps, is to be overridden for a UI process, an entry must first be made in this view.

A UI process is defined by its technical name. This name can be used in the Customizing activity Define Object Hierarchy and Object Attributes to start the UI process via One Click Action or Toolbar Button.

The following attributes can be maintained for a UI process:

• Impl. Class for UI Process
  The class that implements the UI process. This must be derived as a subclass of CL_CRMS4_IU_CM_UI_PROCESS or CL_CRMS4_IU_CM_UIP_CTI.

• Type
  Type of UI Process:

• Overview Page (in planning)
  The steps are displayed on a standard overview page with fold-in detail views for each step.

• Guided
  The individual steps are displayed and processed step by step.

• Tiled (in planning)
  The steps are shown as tiles.

• Short Text
  The short text is a term that summarizes the UI process.

• Text
  Description of the UI process. If the UI process is running in the Contract Overview, this text will be used as the heading. The text can contain placeholders in which, for example, the name of the business partner is dynamically integrated.

• Techn. Name of Process
  Technical name of the PF process assigned to this UI process.

• Process Detail View
  A view can be integrated in the process detail view.
  The short summary is displayed as a default here. The process detail view can be customized.

• Business Partner Detail View
  In the business partner detail view, you can integrate a view.
  The business partner summary is displayed as a default here. The business partner detail view can be customized.

• Group ID
  The profile group refers to the type of BOL tree. The ID can be used to select and display different trees.

• Active
  By selecting the flag, you activate the UI process.
  If the flag is not selected, the process is not active and is therefore not available.
  This function can for example be used to provide a specific client with a limited pre-selection of processes.

• Short Summary
  This short summary provides an overview of the current UI process and is dynamically generated during the process. The ad is located in the right-side panel of the UI. The agent here can see the current selection, for example when creating a contract, such as the contract start or product. By default, the delivery role includes the display of the product.
  The short overview is configurable in transaction SO10. The text that is displayed here in the Process Detail View can be defined individually.

• Summary
  The summary provides an overview of the completed UI process in the last UI process step. The ad is located at the bottom of the UI. The agent can see in the last process step, the selected settings and information, for example when creating a contract, such as the contract start, contract type or address.
  The summary is configurable in transaction SO10. Here you can individually define which information should be displayed in the last process step.

• Business Partner Summary
  The summary provides an overview of the confirmed business partner within the UI process and is dynamically generated during the process.
  The ad is located on the UI to the left of the Process Detail View. By default, the delivery role includes the start of the contract.
  The business partner summary can be configured in transaction SO10. The text that is displayed here in the Business Partner Detail View can be defined individually.

UI Process Parameter

In this view, parameters for a client-specific overridden UI process can be overridden or added.

Parameters that exist in the cross-client version of the process but are not client-specifically overridden at this point are transferred unchanged during runtime of the UI process. This means that not all parameters have to be repeated at this point.

The parameters are defined as a pair consisting of the attribute name and attribute value. The length of the attribute value is limited to 200 characters. To ensure the transfer to the UI process works correctly, the implementing class must have a public attribute with the same name as the attribute name. These attributes are automatically filled with the values defined in this view when the UI process is initialized.

UI Process Step

The UI process steps represent the step-by-step processing that takes place during a UI process. They are displayed in Customer Management in the form of buttons, which agents can use to navigate and process a procedure. Both icons and texts can be specified for these buttons. They also contain a status display for the current processing status of the individual process steps.

In this view, the cross-client-defined UI process steps can be overridden, supplemented or deactivated. Process steps that are not specified in this view are transferred unchanged at runtime from the cross-client version of the process. It is therefore not necessary to repeat all UI process steps at this point.

A process step is defined by its technical name. It has the following attributes:

• Techn. Name of UI Process View
  The technical name of the UI process view to be displayed.

• Sequence
  Sequnece of UI Process Steps
  The field contains a unique number that defines the order of the process steps. The number is usually specified in increments of ten. This allows further intermediate steps to be added later.

• Type
  Kind of UI Process Step:

• Default
  The process can only proceed if all validations of this step have been positive.

• Optional
  The process can proceed if this step was not performed and if warnings occurred during execution.

• Warnings allowed
  The process can proceed even if there are warnings during execution.

• Stateless (Summaries)
  No state, and therefore no icon is displayed for the process step. By default, this option is provided for the summaries.

• Active
  By selecting the flag you activate the UI process step.
  If the flag is not selected, the process step is not active and is therefore not available.
  This function can for example be used to provide a specific client with a limited pre-selection of process steps.

• Short Text
  In this field, you can specify a name for the process step that appears in the button for navigating through the UI process.

• Text
  In this field you can enter a text that appears when the cursor is positioned over the short text or the icon of the process step.

• Icon Name
  The Icon field contains the name of an icon, which is to be displayed before the short text for the process step. The icon name can be the name of a SAP icon, for instance: sap-icon: // home (Name of SAP symbol in Icon Explorer)

• Icon Color
  In this field you can specify the preferred color of the icon.
  The input is made, for example, in hexadecimal notation or by color names.

UI Process Step Requirement

In this view, the cross-client-defined requirements for a UI process step can be overridden, supplemented or deactivated.

One condition refers to the status of another process step. A step may require one or more other steps to have already been successfully completed.

• Example:
  20 CHOOSE_PRODUCT before 25 PRODUCT_CONFIG
  During contract creation, the agent must select a product in the first process step before they can configure it in a further process step.

A requirement for a UI process step is defined by a serial number. The following attributes can be defined:

• Name of UI Process Step
  Technical name of the required UI process step

• Sequence
  Sequence number
  All requirements for a UI process step are performed in the order of their sequence numbers.

• Active
  A requirement is only checked if this flag is set.

UI Process Steps Binding

In this view, the cross-client-defined name assignments of the context nodes of UI processes and linked context nodes of the views can be overwritten or supplemented by the client.

The following nodes can be assigned:

• Target Context Node
  Context node in the view

• Source Context Node
  Context node in the UI process

By default, the context nodes of the views are bound to the context nodes of the UI process with the same name. This can be changed by using the name mapping in the UI process step bind. The same context node in a view can be bound to other context nodes of the UI process for each step. This allows a view to be reused in different processes or steps.

UI Process Business Role Assignment

In this view, the assignment of UI processes for each user role takes place.

The mapping defines which user role can perform specific UI processes. UI processes that are not assigned to a user role cannot be executed or started for users with the corresponding user role.

Example:
An agent is authorized to perform a move-in. However, move-outs should not be in their area of responsibility. Its user role can therefore be assigned the UI process "Move-In" at this point.

CPI1466 during Backup   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 19602 Date: 20240523 Time: 164247     sap01-206 ( 264 ms )