Hierarchy
SAP_HRCCA (Software Component) Sub component SAP_HRCCA of SAP_HR⤷
PY-CA (Application Component) Canada⤷
P07C (Package) HR customizing: Canada
IMG Activity
| ID | OHAKGR126 | Model for the relationship to other debts |
| Transaction Code | S_AHR_61008129 | IMG-Aktivität: OHAKGR126 |
| Created on | 19981221 | |
| Customizing Attributes | OHAKGR126 | Model for the relationship to other debts |
| Customizing Activity | OHAKGR126 | Model for the relationship to other debts |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAKGR126 |
If there exist more than one order or debt that an employee has to pay off during one payroll run, then it must be determined how the garnishable amount should be distributed to these orders and debts. This is determined in this step.
In the Garnishment order infotype you specify a Priority for the order. If more than one order has the same priority, then you can specify here whether they should be sorted according to the receive date, the court order date or whether they should not be sorted according to a date.
If several orders still have the same priority or if there is one order with several debts, then the Debt priority as specified in this step determines which debt should be served first.
If several debts still have the same priority after all these considerations, then the available amount is distributed equally to these debts. Here you can specify whether this distribution should be made according to the number of debts or weighted according to the requested amount.
The amount paid for a debt can never be larger than the non-exempt amount for that debt. In addition, the remaining amount after that cheque is reduced by the amount that has already been paid to a higher-priority debt. This means that if the remaining amount is lower than the amount paid to the other debt, then the lower-priority debt receives nothing. Now suppose that the higher-priority debt (say a family support debt) has a non-exempt amount of $ 500, and the lower-priority debt (e.g., a creditor debt with a large initial balance) has a limit of $ 200. Furthermore, assume that the family support debt only needs $ 400. Normally, the creditor debt receives no money at all. However, one can argue that the limit of the family support debt is not filled to the top and that the creditor debt should receive the unclaimed $ 100. Then you can specify in this view that the limit of the family support debt should define an Extended limit. By specifying that the creditor debt has Access to the extended limit, the remaining amount of the creditor debt is lifted above the amount paid to the higher-priority debt, and it can receive an amount up to the difference between the extended limit and the amount paid to the higher-priority debt. In this case the creditor debt receives $ 100.
Example
Requirements
Standard settings
The SAP system provides certain standard models:
- Family support: arrears (relevant for determining extended limit; dates are not relevant for sorting; weighting according to initial balance)
- Family support: ongoing payment (relevant for extended limit; dates are not relevant for sorting; weighting according to ongoing payment)
- Garnishment (sort according to receive date; weighting according to number of debts)
- Garnishment with access to extended limit (sort according to receive date; weighting according to number of debts)
Recommendation
Activities
Create the necessary relationship models.
Further notes
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 |
|---|---|---|
| OHAKGR126 | CA | Canada |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAKGR126 | 0 | HLA0003914 | Garnishment |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_5KG5_B | V - View | SM30 | Generated table maintenance: V_5KG5_B |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
