Ansicht
Dokumentation

SIMG_ICL_QC_ALLOWED - BAdI: Check Whether Processing in Quick Claim Mode Is Possible

SIMG_ICL_QC_ALLOWED - BAdI: Check Whether Processing in Quick Claim Mode Is Possible

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

Use

You can use this Business Add- In (BAdI) to determine whether a claim can be changed or displayed in quick claim mode. The system checks whether the claim can be changed or displayed at the following points:

  • The first check takes place in PAI of the initial screen if you are in change or display mode and want to access claims processing in quick claim mode.
  • In claims processing in quick claim mode you can switch to expert mode and back. In expert mode you can change the claim in such a way that processing in quick claim mode is no longer possible (for example, if you create several subclaims in expert mode). For this reason, before a user switches back from expert mode to quick claim mode, the system also checks whether the claim can be changed or displayed in quick claim mode.
  • The check is also called at BDT event DCUAC to determine whether the button for returning from expert mode to quick claim mode should even be displayed (see above list point).

If you do not implement this BAdI, every claim can be changed or displayed at any time in quick claim mode.

Requirements

Standard settings

In the standard implementation quick claim mode is not permitted for claims with more than one subclaim. Subclaims with the status Invalid: Not Processed are not considered.

If you have a customer-specific implementation, note that this BAdI is not only called during claims processing but also on the initial screen.

The BAdI is not filter dependent.

The BAdI can be used more than once.

Activities

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

Method:

Change and Display Possible in Quick Claim Mode?






Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4315 Date: 20240524 Time: 010834     sap01-206 ( 71 ms )