Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PY-XX-PS (Application Component) International Functions for the Public Sector⤷
P00PS_DEC (Package) Public Sector Distribution of Employer's Costs
Basic Data
| Data Element | P_99_DEC_CST_ETYPE |
| Short Description | XDEC: Entry Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | P_99_DEC_CST_ETYPE | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Type |
| Medium | 15 | Type |
| Long | 20 | Type |
| Heading | 4 | Type |
Documentation
Definition
This is the entry type of the cost distibution information.
WHEN PAID & WHEN EARNT
N New (Gross Payment)
This is the most important entry. Under both the "when earnt" and "when paid" solutions the N entries will always hold the current period's original payments and the amount of cost that was distributed across those.
Under the "when earnt" solution this is the only set of entries that exist in table COSTS.
WHEN PAID
Changes in Gross Payments
P Previous Calculation
A Current Calculation
These two entries are just for information. They store the necessary history to be able to say when changes in gross payment have occurred between the last time the current period has been calculated and this time.
C Carry Forward
B Brought Forward
PC Previous Carry Forward
CX Previous Carry Forward
BX Previous Brought Forward
These 5 entry types are to control changes in gross and changes in cost object of those changes of gross under the "when paid" solution.
Deltas between P and A entries create C entries which are carried forward to the IN period where they create B entries. The B entries are costed in exactly the same way as N entries except that they are kept separate from N entries, so that it is possible to tell the costs that are associated with brought forward gross payments and the costs that are associated with original gross payments in the period.
The PC entries are simply C entries from the last time this period was calculated. In this way C entries become PC entries when a period is recalculated and PC entries become PC entries. In this way any C entry that has ever been created will always be visible in the A result of table COSTS. This allows changes in cost objects in carried forward amounts to be recognised even if they occur may periods later.
The CX and BX entries are used to make sure that subsequent cost object changes to a period from where C entries were carried forward also effect the B entries that were created. The CX's are carried forward until they reach the FOR period where the B entry was created and they are changed to BX entries. The BX entries are then used to update the B entries.
The CX and BX entries are only created when the related cost object against a wage type has changed. The amount to be distributed has not, so there is no new re-evaluation of the cost in the IN period, but instead the cost is simply switched from its original cost objects to its new cost objects.
Arrears of Costs
CA Carry Forward
BA Brought Forward
PA Previous Carry Forward
C1 Previous Carry Forward
B1 Previous Brought Forward
DA Arrears Deduction Not Taken
PD Previous Arrears Deduction Not Taken
These 7 entry types are to control the "arrears" solution.
Normally, Arrears would not be possible for WHEN EARNT costs as these would be re-assessed and paid in the FOR period that they occured, but it is possible that Arrears are calculated on a WHEN EARNT basis, but are carried forward to the current IN period. This is supported by XDEC, but requires the country development to identify costs that are subject to these unusual rules. This is handled in a country exit called during XDEC - xdec_extra_fields_natio - by setting the T7PBSDEC_COSTS-NATIO field to "A".
Deltas between the last period's arrears and the current period's calculation of arrears create CA entries which are carried forward to the IN period where they create BA entries. The arrears entries are not wage type specific, unlike the gross payments above. The arrears are split across all the payments in the period. The CA entries already have the arrears delta costed across them. The BA entries are not re-assessed in the current period as they are not part of the cost of the current period. The total amount of the arrears on the BA entries is used to reduce the cost in the current period.
The PA entries are simply CA entries from the last time this period was calculated. In this way CA entries become PA entries when a period is recalculated and PA entries become PA entries. In this way any CA entry that has ever been created will always be visible in the A result of table COSTS. This allows changes in cost objects in carried forward arrears to be recognised even if they occur may periods later.
The C1 and B1 entries are used to make sure that subsequent cost object changes to a period from where CA entries were carried forward also effect the BA entries that were created. The C1's are carried forward until they reach the FOR period where the BA entry was created and they are changed to B1 entries. The B1 entries are then used to update the BA entries.
The C1 and B1 entries are only created when the related cost object against a wage type has changed. The amount to be distributed has not, so there is no new re-evaluation of the cost in the IN period, but instead the cost is simply switched from its original cost objects to its new cost objects.
In some rare cases, (i.e. Leave Without Pay scenarios) employer's costs arrears are not deducted in the IN period because the employee doesn't have sufficient monies to pay the employee's proportion so the employer's proportion is not deducted either. In these cases the BA entries are created as DA entries. During the next retro, the DA entries are changed to PD entries to signify that they have been processed. During this initial retro over the DA entry an equivalent CA entry is created to ensure that the Arrears are correctly processed in a later period.
History
| Last changed by/on | SAP | 20040819 |
| SAP Release Created in |
