Ansicht
Dokumentation
VC_QA_T77TB02 - Define Ticket Benefit Subtypes and Beneficiary IDs
Addresses (Business Address Services) Addresses (Business Address Services)This documentation is copyright by SAP AG.
In this activity, you do the following steps:
Define Ticket Benefit Subtypes | You define ticket benefit subtypes, which you can use to support different business scenarios at your organization (for example, different subtypes may be created for scholarship and annual leave ticket benefits). |
If you have to support both accrual and ticket grant scenarios, you must use more than one subtype. For details, see the system documentation for Define Ticket Benefit Cycle and Compensation Mode Customizing activity (and feature TBPAR). | |
Define Ticket Beneficiary IDs | Create the beneficiary IDs that you want to use in the solution. You use those to map different wage types for different dependents and the employee. |
For the employee, you make the beneficiary ID assignment in the Assign Beneficiary Ticket ID to Employee Customizing activity. For the dependents, the assignment is made by an HR operator while creating Ticket Benefit: Entitlement (3408) infotype records for a particular employee. | |
Assign Beneficiary ID to TB Subtype and Wage Types | Map each beneficiary ID that you have created to the relevant wage types for the corresponding calculation method. The settings are country/region-specific. You must make this assignment for each one of the ticket benefit subtypes that you have created. |
Important: To ensure consistency in your payroll results, you must assign one unique wage type for each individual entry, for each subtype. See the example below for details. |
Important: Once you have run payroll with this customizing in place, don't change any of these settings, as this will result in error. If you want to modify any of the settings, create and use a new subtype.
Assume that your implementation covers the following scenario:
- Your organization grants tickets for annual leave and mandate.
- A maximum of 4 dependents can be granted the benefit, per employee.
You would make the following settings:
Define Ticket Benefit Subtypes
TB Subty | Ticket Benefit Subtype Text |
---|---|
LEAV | Leave Ticket |
MAND | Mandate Ticket |
Define Ticket Beneficiary IDs
Beneficiary ID | Ticket Beneficiary ID Text |
---|---|
D001 | Dependent 1 |
D002 | Dependent 2 |
D003 | Dependent 3 |
D004 | Dependent 4 |
E000 | Employee |
Assign Beneficiary ID to TB Subtype and Wage Types
Here, considering that you must assign unique wage types as described above, you have 2 subtypes, 5 beneficiary types, and must assign 7 different, unique wage types for each. You therefore must have created 70 wage types. Here is what it'd look like, for a few of the assignments:
Beneficiary ID E000:
CGrp | TB Subty | TB Subtype Text | Tot TktBal | PrevMonBal | Cashing WT | IntTktBaWT | Differ.WT | IssueWT | ExpiryWT |
---|---|---|---|---|---|---|---|---|---|
AE | LEAV | Leave Ticket | /710 | /720 | /750 | /740 | /730 | /760 | /770 |
AE | MAND | Mandate Ticket | /717 | /727 | /757 | /747 | /737 | /767 | /777 |
Beneficiary ID D001:
CGrp | TB Subty | TB Subtype Text | Tot TktBal | PrevMonBal | Cashing WT | IntTktBaWT | Differ.WT | IssueWT | ExpiryWT |
---|---|---|---|---|---|---|---|---|---|
AE | LEAV | Leave Ticket | /711 | /721 | /751 | /741 | /731 | /761 | /771 |
AE | MAND | Mandate Ticket | /718 | /728 | /758 | /748 | /738 | 768 | /778 |
And the list goes on for the remaining beneficiary ticket IDs.
General Material Data SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 6938 Date: 20240523 Time: 173106 sap01-206 ( 66 ms )