Enhancements to Clarification Case Processing 

Use

You want to add your own, installation-specific case attributes and functions to the clarification lists.

Features

Fields that you add are saved and displayed in all clarification cases for a case category.

 If you need a field only for specific cases, you should add the fields to the cases concerned as an object.

Activities

To supplement customer-specific case attributes, proceed as follows:

...

       1.      Create the include structure CI_EMMA_CASE and add the required fields.
You can add the fields at any time during the implementation. Note, however, that the enhancement takes a long time if you already have a large number of clarification cases in your system.

       2.      Create the customer subscreen required in a customer function group.

       3.      Integrate the customer subscreen in the clarification case transaction. To do this, use the following methods of the Business Add-In EMMA_CASE:

                            a.      DETERMINE_CUSTOMER_SUBSCREEN (mandatory)
Defines the program name and screen number of the customer subscreen.

                            b.      TRANSFER_DATA_TO_CUSTSUB (mandatory)
Transfer of the case data from the clarification case transaction to the customer subscreen
To do this, create a function module that is called by this method in the function group of the customer subscreen.

                            c.      TRANSFER_DATA_FROM_CUSTSUB (mandatory)
Transfer of the customer subscreen to the clarification case transaction
To do this, create a function module that is called by this method in the function group of the customer subscreen.

                            d.      PROCESS_CUSTSUB_OKCODE (optional)
Here you can add additional processing for a function in the clarification case transaction, process a function that only appears on the customer subscreen, or implement other customer-specific processing. In the parameter ES_RETURN, you can return your own messages. For example, if you want to prevent a clerk from setting the status Closed and saving the clarification case before a specific process has been run.

                            e.      UPDATE_CASE_ACTION_LOG
Add customer-defined messages to the action log of a clarification case.

                              f.      CHECK_BEFORE_CHANGE
Implementation of customer-specific checks before a user can change a clarification case
If you return a message in the parameter ES_RETURN, the message is displayed and the user cannot change the clarification case.

                            g.      CHECK_BEFORE_DISPLAY
Implementation of customer-specific checks before a user can display a clarification case
If you return a message in the parameter ES_RETURN, the message is displayed and the user cannot display the clarification case.

       4.      Once you have implemented the methods, activate the BAdI EMMA_CASE.