1. HCM Data Loading Business Objects
  2. Overview of Loading Element Entry with Costing

Overview of Loading Element Entry with Costing

Use the Element Entry with Costing object to load the element entries along with the costing information at the element entry level.

The load validates whether the costing segment value is active or not as on the load date. The load fails, if the costing segment value isn't valid as on the load date. Unlike many HCM Data Loader objects, the Element Entry with Costing object isn't hierarchical. The entry values and costing segments are supplied on the same line as the element entry information. The costing information is optional. Using the Element Entry with Costing object, you can create just element entries too.

Consider these guidelines when creating new element entries using the Element Entry with Costing object.

  • You must supply the CreateEntrySequence attribute with a value that's unique within the ElementEntryWithCosting.dat file for the Element Type and Assignment the entry is for. The entry sequence on the created element entry is then automatically generated for you by incrementing the largest existing element entry sequence for the combination of element type and assignment number.

  • It's always recommended that you supply source keys when creating new records. The source key supplied can then be used to identify the element entry, entry values and costing records when maintaining them.

  • If you don't supply source keys and reload the same file, new records will be created.

  • You can't create date-effective history using this object.

  • You can't specify different effective start dates for the element entry and costing using the object.

  • You can't end-date element entries using the Element Entry with Costing object.

  • You can’t do a replace end date operation using the Element Entry with Costing object.

  • Supply #NULL as entry value for an input value if you’re using HCM Spreadsheet data loader and wanted to use the default value from the element eligibility input value level. Otherwise, default values from element input value level will be used if you leave it blank. You can also supply the desired value if you want a specific value other than the default from element input value or element eligibility input value.

    For example, element input value has a default of 1000 and element eligibility input has the default of 2000 in the element setup. When HCM Spreadsheet template is generated for this element, the row will be generated with 1000 by default. You need to supply #NULL to this entry value in order to use 2000 from element eligibility input value.

Consider these guidelines when updating existing element entries that were created using the Element Entry with Costing object.

  • To correct or update the element entry and costing information created with this object, use the Element Entry with Costing object . The effective date supplied in the dat file is used for updating or correcting both element entry and costing information. If you have a requirement to use separate effective dates for element entry and costing, you should use the respective individual objects to perform the operation.

  • To maintain costing records created with the Element Entry with Costing object, use the CostAllocationV3 and CostAllocationAccountV3 objects . The source key supplied when creating the Element Entry is the same used to identify the costing records.

  • To correct or update element entries that you created with the Element Entry with Costing object, and need a separate effective date for entry and costing information, use the ElementEntry object . The source key supplied when creating the Element Entry is the same used to identify the Element Entry records. Element Entry Value records use with same source system ID but with the Input Value Base Name appended. Replace any spaces in the Input Value Base Name with underscores.

    Note: You must replace the spaces with underscores in InputValueBaseName.

Consider this when deleting element entries using the Element Entry with Costing object.

  • To uniquely identify the record to delete, supply either the source key or the EntrySequence along with the other user key attributes.