Hierarchy
⤷ PY-DE-CI (Application Component) Construction Industry
⤷ P01B (Package) Payroll: Construction Industry
IMG Activity
ID | OHADBLS500 | BAdI: Account for Winter Compensation Advance Benefit |
Transaction Code | S_AC0_52000118 | (empty) |
Created on | 20041006 | |
Customizing Attributes | OHADBLS500 | BAdI: Account for Winter Compensation Advance Benefit |
Customizing Activity | OHADBLS500 | BAdI: Account for Winter Compensation Advance Benefit |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRPAYDECI_WAUR_KONTO |
Use
You can use this Business Add-In (BAdI) to influence the working time account determined as standard in the payroll function DBAU WAUR. If the account is positive, then the hours are available for a winter compensation advance payment or for avoidance of days lost during seasonal reduced working hours.
DBAU WAUR: The constant V_5DBK_B-WAVSW must be selected in the given payroll period in order for the BAdI to be called. Information from the internal Tabelle VAR is then no longer evaluated. If you do not want to use this BAdI, then deselect the indicator. In that case, the functions of the subfunction DBAU WAUR remain as they were up to now.
DBAU SKAV:
The constants named under DBAU WAUR do not have any effect on the call.
The BAdI has a default implementation. If you do not create and activate a different implementation, then the system calls the default implemenation, which evaluates the flexible model of internal table AFLEX. Information from internal table VAR is not considered.
Standard settings
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
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 |
---|---|---|
OHADBLS500 | DE | Germany |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20041006 |
SAP Release Created in | 600 |