Ansicht
Dokumentation

PY_99_ESS_CLM_RTS_25 - BAdI: Maintain Visibility Control and Selection Values

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

This Business Add-In (Add-In) is used in the Advanced Claims component.

This Add-In enables you to:

• Control visibility of standard and customer specific fields

• Change the selection values for customer specific fields that have F4 Help (Values From Customizing) dynamically on the ESS screen

In the standard system, you maintain attributes of field in Define Fields and its Attributes at Header Level and Define Fields and its Attributes at Multiple Line Level. In case, you want to control visibility of standard and customer specific fields and determine F4 values dynamically, for a certain set of employees, you can do using this BAdI.

You should only carry out this step if both of the following points apply:

• The SAP standard processes do not suit your needs

• You are a competent ABAP/4 programmer

In the standard system, the Business Add-In is not activated.

1. After calling up the IMG activity, a dialog box appears, in which the existing implementations are displayed. Choose Change, and proceed as follows:
2. From the tab index, choose Interface.
3. Save your entries, and assign the implementation to a development class.
4. Place the cursor on the method, and double-click to enter method processing.
5. Enter the coding for the implementation between the statements method <Interface name> ~ <Name of method> and end method.
6. Save and implement your coding. Return to the Edit Implementation screen.
7. Save the entries on the Edit Implementation screen.

Note

You can also change an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

1. Choose Activate.
2. The coding you stored in the method will be run when the application program is executed.

• Scenario 1: Change selection values dynamically

Consider that you maintained a customer specific field Overtime for which you have defined the following F4 values in the Customizing:

• Night Shift (8pm - 4am)

• Morning Shift (4am - 12pm)

• Regular Shift (12pm - 8pm)

• Extra Working (Upto 2 Hours)

• Extra Working (2 - 4 Hours)

• Extra Working (4 - 8 Hours)

Using this BAdI, you can display different F4 values for different set of employees. For example, if you want that for shift employees, system should display the first three values and for regular employees it should display last three values, you can do so using this BAdI.

• Scenario 2: Control visibility of customer specific fields

Using this BAdI, you can configure scenario 1in the following way:

Consider that you have maintained fields F1and F2 having the same label Overtime. F1 stores overtime data (first three drop down values) of shift employees and F2stores overtime data (last three drop down values) of regular employees.

You can implement this BAdI to dispaly F1for shift employees and F2for regular employees.

Note

We recommend that you congifure your system using the scenario one.

• Scenario 3: Control visibility of standard fields

Consider that there are two standard fields: Off-Cycle Requested and Off-Cycle Providedthat are displayed on the request creation and detail screen. Displaying this fields is relevant only if the employees have authorisation to select the Payment type. If as per your company norms, you always provide Off-Cycle for certain reimbursement types and Regular for others, then you need not display these fileds. Using this BAdI, you can supress the visibility of these fields.

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5450 Date: 20240523 Time: 191031     sap01-206 ( 71 ms )