Guidelines for Loading Pennsylvania PSD Card Components
The Pennsylvania (PA) Political Subdivision (PSD) card component is used to capture information specific to the state of Pennsylvania and should only exist for employees based there.
Pennsylvania PSD Card Component Hierarchy Image
The Pennsylvania PSD card component uses value definitions to capture override values. Value definitions are supplied using the Calculation Value Definition and Enterable Calculation Value record types.
The following sections describe how to provide valid file lines for these record types.
Card Component Attributes for Pennsylvania PSD
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName | A unique identifier for the Pennsylvania PSD card component. For new card components supply the source key attributes. You can also identify card components with the user key attributes. |
| SourceSystemOwner | N/A | The name of the source system owner used to generate the source system ID. |
| LegislativeDataGroupName | N/A | The name of the legislative data group for the card component definition. |
| DirCardId(SourceSystemId) | CardSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName | The parent Tax Withholding calculation card should be identified by using the same key type used to identify the calculation card. When using source keys, supply this attribute with the value supplied for the calculation card’s SourceSystemId attribute. Otherwise, supply the user key attributes with the same values as the parent calculation card. |
| EffectiveStartDate | N/A |
The start date of the Pennsylvania PSD card component, typically the employee’s start date. This must be the same as the EffectiveStartDate on the Tax Withholding calculation card. If updating an existing State Taxes card component, the effective start date must be original start date of the component. |
| EffectiveEndDate | N/A | The end date is optional for the card component |
| DirCardCompDefName | N/A | The component definition name. Specify ‘City Taxes’. |
| ComponentSequence | N/A | The component’s sequence number. Specify ‘1’. |
| Context1 | N/A | The geocode number that identifies the US state. Specify ‘39’. |
| Context2 | N/A | The surrogate ID of the employee’s tax reporting unit. It is an
application generated value to uniquely identify the tax reporting
unit. Refer to the Template: BI Publisher Report: Tax Reporting Units by Legislation topic in Cloud Customer Connect for details on how to retrieve the tax reporting unit ID. Note: This is a required
field. |
These attributes are supplied against the CardComponent file discriminator and must be supplied along with a CalculationCard record for the parent Tax Withholding card. An example is provided in the Examples of Loading Tax Withholding Pennsylvania PSD topic.
Pennsylvania PSD Value Definitions
| Value Definition Name | Functional Description |
|---|---|
| Resident PSD Code | The PSD code for the location where the employee resides. |
| Resident School District | The code of the school district for the employee’s residential location. |
| Work PSD Code | The PSD code for the location where the employee works. |
| Work School District | The code of the school district for the employee’s work location. |
Calculation Value Definition Attributes for Pennsylvania PSD
The Calculation Value Definition record type specifies the value definition name for the override value.
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName | A unique identifier for the calculation value definition record. For new records supply the source key attributes. You can also identify calculation value definition records with the user key attributes. |
| SourceSystemOwner | N/A | The name of the source system owner used to generate the source system ID. |
| LegislativeDataGroupName | N/A | The name of the legislative data group for the card component definition. |
| SourceId(SourceSystemId) | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName | The parent Pennsylvania PSD card component should be referenced by using the same key type used to identify the card component. When using source keys, supply this attribute with the value supplied for the card component’s SourceSystemId attribute. Otherwise, supply the user key attributes with the same values as the parent card component. |
| EffectiveStartDate | N/A | The start date of the parent Pennsylvania PSD card component or the date the calculation value definition starts, if later. |
| DirCardCompDefName | N/A | The definition name of the parent Pennsylvania PSD card component. Specify the same value as provided on the parent card component record. |
| ValueDefinitionName | N/A | The name of the value being overridden. The list of value definitions applicable to this card component are listed above. |
| Context1 | N/A | The geocode number that identifies the Pennsylvania state. Specify ‘39’. |
These attributes are supplied against the CalculationValueDefinition file discriminator and must be supplied along with a CardComponent record for the parent Pennsylvania PSD card component and a CalculationCard record for the owning Tax Withholding card.
An example is provided in the Examples of Loading Tax Withholding Pennsylvania PSD topic.
Enterable Calculation Value Attributes for Pennsylvania PSD
The Enterable Calculation Value provides the override value for the value definition. It references the Calculation Value Definition record which defines the Value Definition being overridden.
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName | A unique identifier for the enterable calculation value record. For new records supply the source key attributes. You can also identify calculation value definition records with the user key attributes. |
| SourceSystemOwner | N/A | The name of the source system owner used to generate the source system ID. |
| LegislativeDataGroupName | N/A | The name of the legislative data group for the override value. |
| ValueDefnIdSourceSystemId | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName, ValueDefinitionName |
Identify the parent Calculation Value Definition record using the same key type used to identify the calculation value definition. When using source keys, supply this attribute with the value supplied for the calculation value definition’s SourceSystemId attribute. Otherwise, supply the user key attributes with the same values as the parent record. |
| EffectiveStartDate | N/A | The effective start date of the parent calculation value definition record, or the update to the override value if supplying date-effective history. |
| EffectiveEndDate | N/A | The optional end date of the override value, or if you are providing date-effective history, the last day of the date-effective changes |
| Value1 | N/A | The value for the value definition identified by the parent
calculation value definition record. Unlike other calculation cards, if you supply a value definition but have no value for it supply ‘-999999999’ to indicate a null value. |
These attributes are supplied against the EnterableValueDefinition file discriminator. You must supply an EnterableValueDefinition record for each CalculationValueDefinition record supplied.
An example is provided in the Example of Loading Tax Withholding Pennsylvania PSD topic.