Hierarchy
⤷ PA-PA-NL (Application Component) Netherlands
⤷ P05FBN (Package) HR Flexible Benefits NL
IMG Activity
ID | FBN_NL_PL_46 | BAdI: Benefit Plan Activation |
Transaction Code | S_L7D_24001261 | (empty) |
Created on | 20070903 | |
Customizing Attributes | FBN_NL_PL_46 | BAdI: Benefit Plan Activation |
Customizing Activity | FBN_NL_PL_46 | BAdI: Benefit Plan Activation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BADI_HR_NL_FBN_PLAN_ACTIVATION |
Use
This Business Add-In (BAdI) is used in the Flexible Benefits NL (FlexBenNL) component.
You can use this BAdI to deactivate a benefit plan. A number of checks cannot be performed in the standard SAP system, because they are dependent on the name of a specific plan. If you know the name of the plan in your organization, you can use this BAdI to activate the plan and perform these checks.
Note that this BAdI determines the activation status of a benefit plan only once, when initializing Flexible Benefits ESS. If you need a dynamic setting of the plan activation status (for example, based on an employee#s selection), you need to use an alternative BAdI and method (BAdI BADI_HR_NL_FBN_ESS and method SET_PLAN_INACTIVE).
Requirements
You have completed FlexBenNL Customizing activities, and have defined at least one source and one goal.
Standard settings
If the BAdI is not implemented, the plan activation status is set according to standard FlexBenNL settings.
The implementations for this BAdI can be filtered according to the following criteria:
- By benefit area, benefit plan, or plan category. You can maintain plan categories as defined in Customizing under Flexible Benefits NL -> Benefits Administration -> Basic Settings -> Plan Attributes -> Define Benefits Categories
- By plan type, as defined in Flexible Benefits NL -> Benefits Administration -> Basic Settings -> Plan Attributes -> Define Benefit Plan Types
An example implementation (CL_HR_NL_FBN_PLAN_ACTIVE) is provided, as follows:
- This example implementation checks whether the employee has already saved for a life-course saving scheme (levensloop) or save-as-you-earn saving scheme (spaarloon). If the employee has saved into a scheme, the employee is not permitted to save into the other saving scheme within the same year (this is a statutory restriction). This choice should therefore not be possible. The check is done via Cumulated Payroll Results (CRT).
- If you want to use the example implementation for your own Flexible Benefits implementation, you need to adjust the constants l_c_levensloop_plan and l_c_spaarloon_plan, to the technical names of your life-course saving and save-as-you-earn schemes.
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
- You want to check that if an employee participates in the save-as-you-earn scheme, he or she cannot choose the lifespan leave-saving scheme (and vice versa).
- An employee with a company car cannot choose a public transport card. In this situation, the Company Car (0442) infotype is used to determine whether the public transport card plan is permitted.
See also
BAdI method documentation:
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
FBN_NL_PL_46 | NL | Netherlands |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20100331 |
SAP Release Created in | 600 |