Ansicht
Dokumentation

OHARUBP_SC_MGT_006 - Define Sickness Certificate Processing Steps

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this customizing activity, you set up Sickness Certificate Processing Steps and the texts for the steps that are displayed in the user interface.

Each entity in the Sickness Certificates Management transaction has a current Processing Step. This step can be changed after the processing of a particular operation on the entity.

By changing the texts for the pre-delivered steps, you can control the text that is shown for an entity in the Sickness Certificates Management transaction.

If you create and set up your own operations that are enabled for entities in the Sickness Certificates Management transaction, then after processing they can set the entity to a custom step. In this case, maintain a record in this Customizing activity to set up a text for this new step.

The standard functionality of the Sickness Certificates Management transaction assumes a defined business process for processing a sickness certificate. Each step of this process is associated with a particular processing step and processing operation (ABAP class). Each of these operations can be executed on an entity with a particular processing step. After the execution, these operations change the entity processing step to the next one according to the standard business process.

For instance, the Save operation that creates master data for the sickness certificate can process an entity only for which the previous business step has been successfully completed (entity is in step XML Loading). After successful execution, Save operation changes the entity processing step to Infotype Creation.

If you want to enhance the standard business process (the sequence of steps) that a sickness certificate entity should pass through, you need to perform several activities:

1. Add a new processing step
   
   Create a new step in this Customizing activity.
2. Create a new operation associated with the new processing step
   
   This requires the creation of a new ABAP class and appropriate customizing.
   A new class will be a direct successor of CL_HRPADRU_OPERATION_LN or any of its successors (indirect inheritance).
   
   Define a new operation by creating a new Operation ID, link it to an ABAP class, assign it to the relevant application, and set up its UI representation. To do this, use the following Customizing activities:

• Define Operations for Applications

• Set Up Applications for UI Environments

For details of how to create your own operation, see Report Operations Framework in the SAP Help Portal, under Payroll Russia (PY-RU) -> Reporting -> General Reporting.

Hint: In order to define the requirements for the entity that will be accepted for processing by a new operation (for example, only for records in a particular processing step), you need to implement this logic in method IS_AVAILABLE of an operation’s ABAP class. For reference, check the code of pre-delivered operations. In general, operations check that an entity has a pre-defined processing step that is previous to the current one according to the business process.

Additionally, you need to set the sickness certificate entity’s processing step that is expected by the operation that is associated with the next business process step. You can do this by implementing GET_TARGET_STATUS_FOR_ENTITY. In method EXECUTE, after execution of the main business logic, you add special processing for affected entities to set up their result processing step. You add a call for either the SET_FINAL_STATUS method for all affected records or add calls for SET_FINAL_STATUS_FOR_ENTITY for each of the processed entities separately. Both of the mentioned methods call the earlier redefined GET_TARGET_STATUS_FOR_ENTITY.

For reference, check the code of pre-delivered operations.

1. Enhance the operation that is associated with the previous business process step
   
   You need to redefine the processing logic of this operation so that, after execution, the affected sickness certificates entities are set to the new processing step that you enhance in the business process.
   
   You can make an enhancement directly in the ABAP class associated with this operation or create a successor class. In the second variant, you must also assign a successor class to the affected operation in Customizing activity Define Operations for Applications.
   
   If you enhance a pre-delivered operation, then you just need to redefine method GET_TARGET_STATUS_FOR_ENTITY, which defines the target processing step and processing state of a processed sickness certificate entity.
   
   For reference about target processing step definition, check the code of pre-delivered operations.
2. Set up logic to define rules for the definition of the state of Sickness Certificate processing
   
   Each sickness certificate entity has a processing state in addition to a processing step. In the Worklist of the Sickness Certificates Management transaction, the processing state is shown for each entity (as a description text and icon). This parameter indicates the overall condition of an entity from the perspective of its processing step and any other programmed checks.
   
   To define this value, you need to define logic for what is shown in the Worklist according to the current condition of the entity.
   
   To define logic, perform the following actions:

• Inherit CL_HRPADRU_OP_LN_TR_LIGHT ABAP-class (A). In this new class, redefine method GET_STATE and CHECK_STEP to set up the logic for the state of Sickness Certificate processing.

• Create a new Operation ID (B) in Application ID LN_REPORT and assign class (A) to this operation in Customizing activity Define Operations for Applications.

• Inherit CL_HRPADRU_OP_LN_ADD_EXT_DATA ABAP-class (C) and redefine the implementation of method GET_TR_LIGHT_OPERATION_ID. In this implementation, you define that if an entity has a newly created processing step, then operation (B) is used for the definition of the state of Sickness Certificate processing.

• Assign class (C) to operation ADD_EXT_DATA for Application ID LN_REPORT in Customizing activity Define Operations for Applications.

Example

Business process before enhancement: step 1 -> step 2

• Operation 1
  Associated with Step 1.
  Process entity in Step 0 and set entity to Step 1 after processing

• Operation 2
  Associated with Step 2.
  Process entity in Step 1 and set entity to Step 2 after processing

You want to enhance the business process such that: step 1 -> step X -> Step 2.

You create Operation 3:
Associated with Step X.
The step processes an entity in Step X and sets entity to Step 1 after processing.

You enhance Operation 1 so that it processes an entity in Step 0 and sets it to Step X.

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 8188 Date: 20240523 Time: 202206     sap01-206 ( 143 ms )