Guidelines for Loading the Statutory Deduction for India

You need to have one Calculation Card record for every India employee you're maintaining Statutory Deduction data for.

Even if you're updating an existing Statutory Deduction card and the calculation card itself isn’t being updated, you need to still include the calculation card record to group other related data supplied in the file.

Calculation Card Attributes

The Statutory Deduction Calculation Card uses these attributes:

HCM Data Loader Attribute	Alternative User Key Attributes	Functional Description
SourceSystemId	CardSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName	A unique identifier for the Statutory Deductions calculation card. For new calculation card supply the source key attributes. You can also identify calculation cards 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 calculation card.
DirCardDefinitionName	N/A	The name of the card definition. Specify ‘Statutory Deductions’
AssignmentId(SourceSystemId)	AssignmentNumber	Either supply the source system ID, or assignment number that identifies the employee assignment this calculation card is for.
EffectiveStartDate	N/A	The start date of the calculation card, typically the employee’s start date.
CardSequence	N/A	A number to uniquely identify this card when multiple calculation cards for the same card definition exist for the employee. Not required when source keys are used.

Common Card Component Attributes

Card components commonly use these attributes:

HCM Data Loader Attribute	Alternative User Key Attributes	Functional Description
SourceSystemId	CardSequence, ComponentSequence, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName And PayrollStatutoryUnitName Or TaxRepUnitName	A unique identifier for the 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, DirCardDefinitionName, LegislativeDataGroupName And PayrollStatutoryUnitName Or TaxRepUnitName	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 card component. If updating an existing card component, the effective start date must be original start date of the card component.
EffectiveEndDate	N/A	The end date is optional for the card component.
DirCardCompDefName	N/A	The component definition name. Review the guidance for card component being loaded for the value to supply.
ComponentSequence	N/A	The number to uniquely identify this card component when multiple card components with the same DirCardCompDefName exist. Not required when source keys are used.

These attributes are supplied against the CardComponent file discriminator.

Common Component Detail Attributes

The component detail record type enables upload of data into flexfield segments.

In addition to the attributes defined here, include the necessary flexfield segment attribute values for the flexfield contexts used by the card component. See the guidance for the card component being loaded.

You can find the flexfield segment attribute name for this flexfield context using the View Business Objects task.

The component details use these attributes:

HCM Data Loader Attribute	Alternative User Key Attributes	Functional Description
SourceSystemId	CardSequence, ComponentSequence, DirInformationCategory, LegislativeDataGroupName, DirCardDefinitionName, DirCardCompDefName And PayrollStatutoryUnitName Or TaxRepUnitName	A unique identifier for the component detail record. For new component detail records 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.
DirCardCompId(SourceSystemId)	CardSequence, ComponentSequence, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName And PayrollStatutoryUnitName Or TaxRepUnitName	The parent card component should be referenced using the same key type used to identify the parent record. 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 component detail, or update to the component detail if you are providing date-effective history. This must be after or equal to the EffectiveStartDate provided for the parentcard component.
EffectiveEndDate	N/A	The optional end date of the component detail, or if you are providing date-effective history the last day of the date-effective changes.
DirCardCompDefName	N/A	The name of the card component this detail is for. This is used to identify the flexfield context and should be supplied even when a source key is used to identify the parent card component. Supply the same value as supplied to this attribute on the parent card component.
DirInformationCategory	N/A	The code for the flexfield context. Refer to the guidance for the card component for valid values.
FLEX:Deduction DeveloperDF	N/A	Supply the same value as for the DirInformationCategory attribute.

Note: When supplying values to lookup validated flexfield segments, you can provide the lookup meaning using the ‘_Display’ suffixed attribute name, but it's recommended that you supply the lookup code to remove potential translation issues.

Common Calculation Value Definition Attributes

The Calculation Value Definition record type specifies the value definition name for the override value.

The Calculation Value Definition record type uses these attributes:

HCM Data Loader Attribute	Alternative User Key Attributes	Functional Description
SourceSystemId	CardSequence, ComponentSequence, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName, ValueDefinitionName And PayrollStatutoryUnitName Or TaxRepUnitName	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, LegislativeDataGroupName, DirCardDefinitionName, DirCardCompDefName And PayrollStatutoryUnitName Or TaxRepUnitName	The parent 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 card component or the date the calculation value definition starts, if later.
DirCardCompDefName	N/A	The name of the card component this value definition is for. This is used to identify the value definition and should be supplied even when source keys are used to identify the record. Supply the same value as supplied to this attribute on the parent card component.
ValueDefinitionName	N/A	The name of the value being overridden. Refer to the guidance for the card component being loaded for the list of applicable value definitions.

These attributes are supplied against the CalculationValueDefinition file discriminator and must be supplied along with a CardComponent record for the parent Income Tax card component and a CalculationCard record for the owning Statutory Deductions card.

Enterable Calculation Value Attributes

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.

The Enterable Calculation Value record type uses these attributes:

HCM Data Loader Attribute	Alternative User Key Attributes	Functional Description
SourceSystemId	CardSequence, ComponentSequence, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName, ValueDefinitionName And PayrollStatutoryUnitName Or TaxRepUnitName	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, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName, ValueDefinitionName And PayrollStatutoryUnitName Or TaxRepUnitName	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're 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.