Overview of Loading Element Entries

You use element entries to capture earnings, deductions, absences, and basic benefit details for an employee assignment. For example, you can create element entries for an employee's overtime hours or medical premium deduction amount.

The element entry values hold the necessary values for the element type. For example, a salary entry can contain the salary value and the salary frequency.

HCM Data Loader provides these two business objects for loading element entries:

Object	What It Loads
Element Entry	Element entries and element entry values. Note: To load costing data for element entries created with the Element Entry object, use the Cost Allocation and Cost Allocation Account objects.
Element Entry Costing	Element entries and element entry values along with the costing information at element entry level.

Element Entry With Costing

Here are some guidelines that you must consider when loading element entries using the Element Entry with Costing object.

• Unlike most 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.

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

• You can't rollback the new element entries with costing information.

• You can't load date effective history of an element.

• You can't load different effective start dates for element entry and costing. The application uses the same effective date as the Element Entry start date and Costing start date.

• The entry sequence of the element entry is automatically generated for you. The Create Entry Sequence is unique within the dat file for an entry. The application reads the existing element entry sequence and automatically increments the sequence number using the number provided in the dat file. You don't have to review the existing entries and provide the next sequence number in the dat file that you do in individual element entry object.

• If you reload the same file with only user keys, the application will create a new element entry on every iteration. This behavior is because CreateEntrySequence isn't stored in the application and doesn't uniquely identify the record.

• Supply a source key when creating element entries, as the element entry sequence number is generated for you. Also, you wouldn't know the user key in order to maintain the element entry or costing records.

• You must use the Cost Allocation and Cost Allocation Account objects to maintain element entry costing that you created using the Element Entry with Costing objects. The source key supplied when creating the element entry can be used to identify the costing record to maintain.

• You must use the Element Entry object to update element entries created using the Element Entry with Costing object. The source key supplied when creating the element entry can be used to identify the element entry. To identify the source keys for entry values, use this combination - <EntrySourceId><InputValueBaseName>.

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