Guidelines for Loading Court Orders for Bahrain
You should always include the Court Orders calculation card record, even if you’re updating an existing Court Orders card.
Even if the calculation card itself isn’t being updated, you must still include the calculation card record to group other related data supplied in the file.
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName | A unique identifier for the Court Orders 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 ‘Court Orders’ |
| 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. |
| CardSeqeunce | N/A | A number to uniquely identify this card when multiple calculation
cards for the same card definition exist for the employee. Note: Not
required when source keys are used. |
Court Order Details Card Component
The Court Order Details card component is a predefined card component which acts as a parent to the element specific card component.
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName | A unique identifier for the Court Orders Details 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 Court Orders 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 Court Order Details card component. This must be the same or after the EffectiveStartDate on the Court Orders calculation card. |
| EffectiveEndDate | N/A | The end date is optional for the card component |
| DirCardCompDefName | N/A | The component definition name. Specify ‘Court Orders Details’. |
| ComponentSequence | N/A | A number to uniquely identify this card component when multiple
card components for the same card component definition exist on the
same card. Note: Not required when source keys are used.
|
Card Component Named for the Court Order Element
This card component is a named for the court orders element and is created as a child to the Court Order Details card component.
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, ComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName | 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, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName |
The parent Court Orders 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. |
| ParentDirCardCompId (SourceSystemId) | CardSequence, ParentComponentSequence, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, ParentDirCardCompDefName | The parent Court Order Details card component. Use the same key type used to identify the Court Order Details card component. |
| EffectiveStartDate | N/A | The start date of the card component. This must be the same as the EffectiveStartDate on the Court Orders calculation card. |
| EffectiveEndDate | N/A | The end date is optional for the card component |
| DirCardCompDefName | N/A | The component definition name. Specify the name defined when creating the court order element. |
| ComponentSequence | N/A | A number to uniquely identify this card component when multiple card components for the same card component definition exist on the same card. Not required when source keys are used. |
| Context1 | N/A | Reference code of the court order. |
Component Detail Attributes for Court Orders
Court Orders uses a single flexfield context. Use the Component Detail record type to load the flexfield segment values.
In addition to the attributes defined here, include the necessary flexfield segment attribute values for these flexfield contexts:
- Bahrain Involuntary Deduction Details (ORA_HRX_BH_INVOL_DED_DETAILS)
To supply third-party details on the Bahrain Involuntary Deduction Details flexfield context, refer to the Cloud Customer Connect topic BI Publisher Report: Third Party Payees for Involuntary Deduction Cards for a report that extracts the third-party names and party IDs for the country, legislation and payee type specified.
| HCM Data Loader Attribute | Alternative User Key Attributes | Functional Description |
|---|---|---|
| SourceSystemId | CardSequence, ComponentSequence, DirInformationCategory, LegislativeDataGroupName, AssignmentNumber, DirCardDefinitionName, DirCardCompDefName | A unique identifier for the component detail. 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, AssignmentNumber, DirCardDefinitionName, LegislativeDataGroupName, DirCardCompDefName |
The parent card component should be referenced using the same key type used to identify the parent record. This is the card component that is named after the Court Order element. 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. |
| DirInformationCategory | N/A | The code for the flexfield context. Supply ORA_HRX_SA_INVOL_DED_DETAILS. Flexfield context codes are visible on the Flexfield Attributes tab of the View Business Objects task. |
| FLEX:Deduction DeveloperDF | N/A | Supply the same value as for the DirInformationCategory attribute. |