Hierarchy
⤷ IS-HER-CM-AD (Application Component) Administration
⤷ PMIQ (Package) Campus Management
Basic Data
Data Element | PIQ_BEGDA |
Short Description | Valid-From Date |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | FROM_DATE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Valid From |
Medium | 10 | Valid From |
Long | 20 | Valid From |
Heading | 10 | Valid From |
Supplementary Documentation - PIQ_BEGDA 0020
Use
Test für selection screen
Procedure
Examples
Dependencies
Supplementary Documentation - PIQ_BEGDA 0194
Definition
This field should contain the date on which the court declares that employee wages may be garnished to fulfill payment obligations. Rather than the date that the document is entered into the system, this field should contain the date that the garnishment document takes effect.
Exceptions
Within payroll, new garnishments can take effect only during the current pay period. As a result, if the garnishment was established in a previous pay period, then the date in this field cannot reflect the actual date that the garnishment took effect. In such cases, this field should contain the first date of the current pay period.
Procedure
In this field, enter the date that the garnishment takes effect, if that date lies in the current pay period. Otherwise, enter the first date of that period here.
The default entry for this field is the current date.
Supplementary Documentation - PIQ_BEGDA 0195
Definition
This field should contain the effective start date of the garnishment order. Depending upon the repayment schedule established by the court, the start date of the order may coincide with each payroll period, or it may occur on a less frequent basis.
Exceptions
Within payroll, new garnishment orders can take effect only during the current pay period. As a result, if the garnishment was established in a previous pay period, then the date in this field cannot reflect the actual date that the garnishment took effect. In such cases, this field should contain the first date of the current pay period.
Procedure
In this field, enter the date on which processing of the garnishment order should begin. Since a distinct garnishment order should exist for each payment, the date you enter here will depend upon the date you remit payments to the vendor.
The default entry for this field is the current date.
Supplementary Documentation - PIQ_BEGDA 1001
Procedure
Enter the new effective date for all records in the taxability model. This effective date will also apply to entries you have added in the past that have a begin date later than the new effective date.
Examples
You added a tax class for California on May 1 and regenerated the taxability model. You later realize that you forgot to change some tax class definitions for Texas that should be effective January 1. When you regenerate the taxability model with the effective date of January 1, the new tax class you added to California on May 1 will now also be effective from January 1.
What to do
In this case, you will have to remove the extra tax class you added to California and regenerate the taxability model with an effective date of January 1. This will ensure retrocalculations carried out between January 1 and May 1 are correct for California. You then need to reinsert the new California tax class and regenerate the model with the effective date of May 1.
Dependencies
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 472 |