Hierarchy
⤷ PY-DE-NT-TX (Application Component) Tax
⤷ P01T (Package) HR Germany: Tax
IMG Activity
ID | PAY_DE_B2A_FIN_580 | BAdI: Determine Statement Periods |
Transaction Code | S_L7D_24001867 | (empty) |
Created on | 20081119 | |
Customizing Attributes | PAY_DE_B2A_FIN_000 | Data Exchange with Financial Administration |
Customizing Activity | PAY_DE_B2A_FIN_580 | BAdI: Determine Statement Periods |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRPAYDEST_LB_PERIODS |
Use
You can use this Business Add-In (BAdI) Determine Statement Periods (HRPAYDEST_LB_PERIODS) to determine your own statement periods as an alternative to the standard flow logic.
In this case, you must implement the two methods CONDENSE_PERIODS and DETERMINE_REASON of interface IF_EX_HRPAYDEST_LB_PERIODS. Only periods with a statement reason are statemented.
Method CONDENSE_PERIODS
You use method CONDENSE_PERIODS to condense the statement periods ct_periods, meaning that they are merged so that there is a maximum of one active and inactive period for each 'STKRT' period.
You set the output parameter e_ok to 'TRUE' if there are no errors, otherwise there is no subsequent processing.
Method DETERMINE_REASON
You use the method DETERMINE_REASON to determine the statement reason for each period of table ct_periods and to enter this reason in field LBGRD. Statements are only created for periods with a statement reason. The value of input parameter i_date is the end date of the evaluation period.
You set the output parameter e_ok to 'TRUE' if there are no errors, otherwise there is no subsequent processing.
Requirements
Standard settings
An implementation is not usually necessary. An implementation can be useful if a differentiation of the employment status (Actions (0001) infotype) between 'Left Company' (value '0') and the other values is not sufficient.
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
When implementing the methods, you can use the implementations of the methods 'CONDENSE_PERIODS' and 'DETERMINE_REASON' of class CL_HRPAYDEST_LB_NOTIF_PERIOD as a guide.
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 | 20081119 |
SAP Release Created in |