SAP ABAP IMG Activity OHFBNTL06 (BAdI : Enhancement for GB FlexBens Processing Dates Calculation)
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 OHFBNTL06 BAdI : Enhancement for GB FlexBens Processing Dates Calculation  
Transaction Code S_P2H_60000045   (empty) 
Created on 20040220    
Customizing Attributes OHFBNTL06   BAdI : Enhancement for GB FlexBens Processing Dates Calculation 
Customizing Activity OHFBNTL06   BAdI : Enhancement for GB FlexBens Processing Dates Calculation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PFBN0004    

BAdI : Enhancement for GB FlexBens Processing Dates Calculation (PFBN0004)

Use

This Business Add-In (BAdI) is used in Flexible Benefits for Great Britain (PA-BN-FB-GB), in the process of creating a benefits offer.

In Flexible Benefits for Great Britain (GB FlexBens), the processing data for creating a benefits offer is calculated by the subroutine SAP_GET_PROCESS_DATES, within the function HR_BEN_GET_PROCESS_DATES. Alternatively, you can use the SAP-delivered Business Add-In (BAdI) PFBN0004.

Therefore, BAdI PFBN0004 is called to calculate the processing data for a benefits offer instead of calculation using the subroutine SAP_GET_PROCESS_DATES.

Requirements

You must use the following input parameters:

  • EE_BENEFIT_DATA Benefits-specific employee data
  • EVENT_DESCRIPTION Event description
  • ENRTY Type of plan enrollment
  • DATUM Validity date

You can specify the following as output parameters:

  • PROCESS_BEGDA Start of processing
  • PROCESS_ENDDA End of processing

In addition to this, you can define two exceptions to the standard coding:

  1. STANDARD_PROCEDURE execute SAP_GET_PROCESS_DATES

In the following sample coding, the processing data for creating a benefit offer should be read from the customer-specific table ZDATE. You can store the start of processing and end of processing in table ZDATE.

The processing data should be read from ZDATE in all clients. Only in client 00 should SAP_GET_PROCESS_DATES be accessed.

TABLES: ZDATE.

CASE SY-MANDT.

WHEN 0.

RAISE STANDARD_CALCULATION.

WHEN OTHERS.

SELECT * FROM ZDATE WHERE BAREA EQ _EE_BENEFIT_DATA-BAREA

AND EVENT EQ _EVENT_DESCRIPTION-EVENT

AND ENDDA GE _DATUM

AND BEGDA LE _DATUM.

EXIT.

ENDSELECT.

IF SY-SUBRC NE 0.

RAISE CUSTOMER_ERROR.

ENDIF.

_PROCESS_BEGDA = ZDATE-BEGDA.

_PROCESS_ENDDA = ZDATE-ENDDA.

ENDCASE.

Default Settings

  • This BAdI is not activated in the standard system.
  • If this BAdI is activated without first being modified, no output will be given by the function module HR_FBN_GET_PROCESS_DATES.
  • The standard routine is executed when there is no active customer implementation.
  • This BAdI is filter-dependent, according to country molga.
  • This BAdI cannot be enhanced or reused.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

If you have created customer-specific infotypes or database tables, you can use their contents to calculate processing data to create a benefits offer.

See also

Methods

GET_PROCESS_DATES

For more information on how to use Business Add-Ins, access the SAP Library and choose: mySAP Technology Components -> SAP Web Application Server -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins.

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
OHFBNTL06 GB United Kingdom
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20040225 
SAP Release Created in 200