Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-PS-VA (Application Component) Pension Administration⤷
P00PBSCA_IMG (Package) HCM Calculation Modules (IMG)
IMG Activity
| ID | HR_PBS_00_VG_INDIV_9 | BAdI: Control of Ready for Input Status BDA Depending on Pay Scale Type |
| Transaction Code | S_L4H_49001424 | (empty) |
| Created on | 20100616 | |
| Customizing Attributes | HR_PBS_01_VG_2_2 | Pension Calculation (Optional Activity / Non-Critical) |
| Customizing Activity | HR_PBS_00_VG_INDIV_9 | BAdI: Control of Ready for Input Status BDA Depending on Pay Scale Type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRPAYDE_FED_STATE_CONTROL_BDA |
Use
In the Public Sector basic pay (infotype 0008), the BDA field (reference seniority or pay seniority) and various other fields are used to determine a pay scale level automatically.
Based on changes to the public services regulation for the federation (DNeuG), for example, it is no longer possible to determine the pay scale level based on the BDA. Instead, the pay scale level must be entered manually. Other control options for pay scale level increases are also necessary.
The following differences are described in detail here:
Field Using the BDA Without Using the BDA
BDA Available Not available
Pay scale level No input possible Ready for input
Previous currency Available Not available
Case group catalog Available Not available
Case group Available Not available
Spouse indicator Available Not available
Variable argument PS Increase Not available Available
Date of next PS increase Not available Available
Start date of current PS level Not available Available
Comparison pay scale area Not available Available
The Business Add-In (BAdI) HRPAYDE_FED_STATE_CONTROL_BDA is used to control the ready-for-input status of the pay scale level and additional fields and to hide the fields required for the BDA.
However, the indicator #D# (DNeuG) used until now for control purposes for the transfer table V_T5DPBS3A (Transfer to Collective Agreement Public Sector: Assignment Pay Scale Type Old/New) is still taken into consideration. You therefore need to create an implementation only if you do not belong to the area of the DNeuG and the public services regulation you use is not already included in the standard implementation (see below).
For information about the interface used, see the interface documentation IF_HRPAYDE_FED_STATE.
Requirements
Standard settings
In the default implementation of the BAdI, the return value RV_RESULT for the attributes '03' (Bavaria) and '25' (Federal (DNeuG)) of the Public Services Regulation indicator is set to the value 'X' (ABAP_TRUE).
Activities
If you do not belong to the area of the DNeuG, the public services regulation you use is not already included in the standard implementation, and you also want to use the aforementioned change, create a user-defined implementation and set the return value RV_RETURN of the method IS_VALID for the affected personnel numbers to the value 'X' (ABAP_TRUE). In the same way as in the standard implementation, you can likewise use the Public Services Regulation indicator to distinguish between the personnel numbers.
Then activate the implementation.
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 use the basic pay for the Public Services Regulation Berlin (indicator 10) without BDA.
To do this, you create a customer implementation in which the IS_VALID method is as follows, for example:
METHOD if_hrpayde_fed_state~is_valid.
DATA: ls_t500p TYPE t500p.
ls_t500p = cl_hr_t500p=>read( is_p0001-werks ).
* Land Berlin
IF cl_hrdepbsvavg_dienstrecht=>get_dienstrecht(
iv_molga = ls_t500p-molga
iv_trfar = iv_trfar
iv_trfgb = iv_trfgb
) EQ '10'. "Berlin
rv_result = abap_true.
ELSE.
rv_result = abap_false.
ENDIF.
ENDMETHOD.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20100616 |
| SAP Release Created in |
