Ansicht
Dokumentation

HRPAYAT_AJST0_001 - Customer Enhancement to Determine Annual Sixth (from 2020)

Vendor Master (General Section)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in Payroll Austria (PY-AT). You can use this BAdI to trigger the following operations:

• Generation of wage type /4JW (effective sixth) so that a control calculation takes place in accordance with EStG Sec. 77 4a.

For this, set the parameters EX_4JW_CALC = ‘X’ and EX_U4JW_VAR = initial in the method generate_4jw.

• Generation of the entry U4JW in table VAR if the wage type /4JW is suppressed so that only the part of the control calculation in accordance with EStG Sec. 77 4a second clause takes place.

If you suppress the generation of /4JW, you must always write the entry U4JW to table VAR at the same time.

To do this, set the parameter EX_4JW_CALC = initial and EX_U4JW_VAR = ‘X’ in generate_4jw.

• If no wage type /4JW is generated (and therefore the generation is not suppressed), set both parameters = initial: EX_4JW_CALC and EX_U4JW_VAR.

A full control calculation is performed for the annual sixth only if wage type /4JW was generated. It makes sense to generate the wage type, for example, if an employee leaves the work relationship again in the current month after a mid-year end of the work relationship and after a reentry (re-leaving).

Most of the cases in which no control calculation may be performed are illustrated in the standard system. An exception is checking the payment of rehabilitation pay according to § 143a ASVG. For this, implement the method generate_4jw to suppress the generation of /4JW.

Note: Your wage type must have the value 2 in processing class 30 in order for this wage type to be cumulated to CRT. The wage type is located in the import parameter IM_CRT in the method.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4066 Date: 20240607 Time: 072548     sap01-206 ( 59 ms )