SAP ABAP IMG Activity OHFBNTL09 (BAdI: Check Corequisite Insurance Plan Option Consistency)
Hierarchy
EA-HRCGB (Software Component) Sub component EA-HRCGB of EA-HR
   PA-BN-FB-XX (Application Component) General Parts
     PAOC_BEN_FBN (Package) Flexible Benefits System
IMG Activity
ID OHFBNTL09 BAdI: Check Corequisite Insurance Plan Option Consistency  
Transaction Code S_AEN_10000928   (empty) 
Created on 20050406    
Customizing Attributes OHFBNTL09   BADI: Check Corequisite Insurance Plan Option Consistency 
Customizing Activity OHFBNTL09   BADI: Check Corequisite Insurance Plan Option Consistency 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PFBN0007    

Use

This Business Add-In (BAdI) is used in Flexible Benefits for Great Britain (PA-BN-FB-GB). This BAdI enables you to implement your own rules regarding permit options of slave plan when you configure Critical Illness Plan.

You need to configure separated insurance plan for employee and partner, and define configure Insurance plan option for employee and partner in IMG step. The SAP-delivered Business Add-In (BAdI) PFBN0007 allows you to implement your own check rule for checking corequisite insurance plan option consistency. This BAdI is called when employee enrollment Critical Illness Plan option. For example:

  • When a user wishes to display the plan maintenance detail screen generated using transaction HRFBN0001 and ESS transactions PZ63, PZ64, and so on.
  • When a user wishes to display a cost summary from the plan cost summary screen using transaction HRFBN0001 and ESS transactions PZ63, PZ64, and so on.

Standard settings

  • There is no standard implementation delivered for this BAdI.
  • As there is no standard implementation for this BAdI, it is not possible to activate it without modification.
  • This BAdI is not filter-dependent.
  • This BAdI is not reusable.

Activities

After calling the IMG activity, a dialog box appears in which you must enter a name for the implementation.

If implementations for this Business Add-In already exist, a dialog box appears that lists these existing implementations. Choose Create in this dialog box and proceed as follows:

  1. In the dialog box, enter a name for the implementation of the Business Add-In in the Implementation field and choose Create.

    This takes you to the initial screen for Business Add-In implementations.

  2. In the initial screen, enter an implementation short text in the Implementation Short Text field.
  3. Choose the Interface tab page.

    On the tab, the Name of Implementing Class field is filled automatically , since the system assigns a class name based on the name of the implementation.

  4. Save your entries and assign a package.
  5. Position the cursor on a method and double-click to go to method processing.
  6. Between the statements method <Interface Name>~<Name of Method>. and endmethod., enter your implementation code.
  7. Save and activate your code and go back to the Change Implementation screen.
  8. On the screen, save Change Implementation.

    Note: It is also possible to create an implementation for a Business Add-In and activate it later. In this case, stop processing at this point.

  9. Choose Activate.

    When your application program is executed, the system now runs through the code you added in the method.

Example

Your organisation wishes to apply its own rule for checking corequisite insurance plan option consistency. You therefore implement (BAdI) PFBN0007 to implement your own checking rule. The system then uses the values produced by this BAdI when checking corequisite insurance plan option consistency.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHFBNTL09 GB United Kingdom
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050406 
SAP Release Created in