Ansicht
Dokumentation

PAY_DE_AVMG_330 - BAdI: Restriction of Base Wage Types

PAY_DE_AVMG_330 - BAdI: Restriction of Base Wage Types

Fill RESBD Structure from EBP Component Structure   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Limitation of Base Wage Types

If you use subapplication AVmG: Base Wage Type Can Be Entered in Infotype (AVBI), you can enter the base wage type for an AVmG module in infotype German Pension Reform D (0699).

Cumulation wage type Base Wage Types Permitted in Infotype 0699 (BLAZ) of subapplication AVmG: Base Wage Type Can Be Entered in Infotype (AVBI) is evaluated in the standard SAP system by the BAdI definition provided and by storing class CL_HRPAYDE_FB_AVM_BLGRT as a fallback class. If indicator Entry of Base Wage Type in Infotype has been activated, the wage types entered in cumulation wage type Base Wage Types Permitted in Infotype 0699(BLAZ) as base wage types can automatically be entered in infotype German Pension Reform D (0699).

You can use Business Add-In (BAdI) Limitation of Base Wage Types (HRPAYDE_B_AVM_BLGRT) to specify a different logic to determine the valid base wage types and use the following criteria, for example:

  • Employee subgroup
  • Contract model
  • Module
  • Payroll area

You can still continue to consider cumulation wage type Base Wage Types Permitted in Infotype 0699 (BLAZ) in a customer-defined BAdI implementation or, in dependent of this, you can evaluate cumulation wage types of a customer-defined subapplication.

You have activated subapplication AVmG: Base Wage Type Can Be Entered in Infotype (AVBI).

The use of this BAdI is optional. You only need to implement it if you have different requirements to that of the standard SAP system.

To suggest various groups of base wage types to enter, create your own customer-defined BAdI implementation. The class you have created can inherit from sample class CL_HRPAYDE_FB_AVM_BLGRT. In your class, redefine method LIMIT_INPUT_BLARTof interface IF_HRPAYDE_AVM_BLGRT.

If an administrator enters a base wage type in infotype German Pension Reform D(0699), the program logic calls this method. You can use the return value of parameter RT_BLGRT to determine which wage types are valid in this case.

You can make the valid base wage types dependent on the input parameters of method LIMIT_INPUT_BLART(for example, contract model or the entries of infotype Organizational Assignment(0001)). You can store the valid base wage types in various cumulation wage types of a customer-defined subapplication, for example. Depending on your selection criterion, you can call method GET_LOHNARTEN to read the corresponding cumulation wage type of your subapplication.

Details about Interface IF_HRPAYDE_AVM_INFTY and Fallback and Sample Class CL_HRPAYDE_FB_AVM_BLGRT

Interface IF_HRPAYDE_AVM_INFTY contains the following method:

  • LIMIT_INPUT_BLART: You can use this method to define the valid base wage types that can be maintained in an infotype record. Enter the valid wage types in table RT_BLGRT.

Class CL_HRPAYDE_FB_AVM_BLGRT contains the following service method:

  • GET_LOHNARTEN: You can use this method to read wage types that are assigned to a cumulation wage type in a subapplication.

You would like to specify the base wage types to be maintained based on the employee subgroup. You would like to differentiate between salaried employees and industrial workers. Proceed as follows:

  1. Create a customer-defined subapplication, for example 0PKR. Call up transaction Call View Maintenance (SM30). Create the subapplication in view Validity Intervals for Statutory Subapplications (V_T596A).
  2. Create the customer-defined cumulation wage types, for example DU00 for salaried employees and DI00 for industrial workers. Call up transaction Call View Maintenance (SM30). Create cumulation wage types DU00 and DI00 in view Specification for Cumulation Wage Types for Subapplications(V_T596G) in subapplication 0PKR.
  3. Assign the wage types to cumulation wage types DU00 and DI00 that should be base wage types that can be entered in the relevant category. Call up transaction Call View Maintenance (SM30). Assign the wage types to cumulation wage type DU00or DI00 in view Assignment of Wage Types to Cumulation Wage Types (Customer Table) (V_T596J) in subapplication 0PKR.
  4. Create a customer-defined BAdI implementation, for example ZCL_HRPAYDE_FB_AVM_BLGRT_PERSK. The class you created inherits from sample class CL_HRPAYDE_FB_AVM_BLGRT. Redefine method LIMIT_INPUT_BLART of interface IF_HRPAYDE_AVM_BLGRT in your class and change to code to meet the requirements. You can find code that is commented out that implements this sample scenario in sample implementation CL_HRPAYDE_FB_AVM_BLGRT.





General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 6380 Date: 20240523 Time: 203415     sap01-206 ( 160 ms )