Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-CI (Application Component) Construction Industry⤷
P01B (Package) Payroll: Construction Industry
IMG Activity
| ID | OHADBLU120 | BAdI: Payroll Function DBAU URLG - Date for Reading Leave Regulations |
| Transaction Code | S_EG4_04000072 | (empty) |
| Created on | 20080129 | |
| Customizing Attributes | OHADBLU120 | Payroll Function DBAU URLG - Date for Reading Leave Regulations |
| Customizing Activity | OHADBLU120 | Payroll Function DBAU URLG - Date for Reading Leave Regulations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRPAYDECI_DBAU_URLG |
Use
You can use the BAdI HRPAYDECI_DBAU_URLG to influence the DBAU URLG payroll function.
The existing methods and their meanings are explained below:
- SET_DATUM # Change of key date for reading T5DBF/T5DB_ZUORDUREG
Up to now, for reading table T5DBF/T5DB_ZUORDUREG the system used the date on the allowed leave day as the key date for reading table T5DBF/T5DB_ZUORDUREG containing the regulations for calculating leave. Due to a change in the collective agreement for the fiscal year change 2007/2008, it is necessary to use the value (such as the day rate) that was valid at the time it arose for leave before 2008. Using the method SET_DATUM, you can change the date for reading the table containing the leave regulations. We provide a default implementation for the method SET_DATUM. If the customer does not create their own implementation of the method, then the system uses this default implementation.
Note: Implement the BAdI only if the functions provided by the default implementation are not sufficient to meet your needs.
Standard settings
Activities
After you access the IMG activity, a dialog box appears in which you have to enter a name for the implementation.
If implementations have already been created for the BAdI, a dialog box appears displaying the existing implementations. Normally there is usually either no implementation or just one implementation. If there is no implementation, choose Create in the dialog box and proceed as follows:
1. In the Implementation field in the dialog box, enter a name for the BAdI implementation and choose Create.
The initial screen for creating BAdI implementations appears.
2. Enter a text for the implementation in the Implementation short text field.
3. In the tab index, choose Interface.
The Name of implementing class field is filled automatically because the system assigns a class name on the basis of your implementation.
4. Save your entries and assign a package.
5. Place the cursor on the method and double-click to go to method processing.
6. Enter the required code for the implementation between the method <interface name>~<method name>. and endmethod. statements.
7. Save your code and activate it. Return to the Change Implementation screen.
8. Save the data on the Change Implementation screen.
Note: You can also create an implementation for a BAdI first and then activate it later on. If you want to do so, complete processing now.
9. Choose Activate.
Example
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 |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADBLU120 | DE | Germany |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20110902 |
| SAP Release Created in |
