Maintain Element Entries Created with Element Entry With Costing

To update or correct the element entries along with the costing information when the effective date is same for both element entry and costing, you can use the ElementEntrywithCosting object.

If you need to use separate effective dates for element entry and costing while updating, use the respective individual objects, such as ElementEntry for updating or correcting the Element Entry information and CostAllocationV3 and CostAllocationAccountV3 for Costing Information.

Let's consider, after loading a recurring element entry with an open end date along with costing information, you realize that both the Funding Source and Amount were incorrect on the original element entry.

To correct Amount and Funding Source using the ElementEntrywithCosting object, use the ElementEntrywithCosting.dat file:

METADATA|ElementEntryWithCosting|EffectiveEndDate|EffectiveStartDate|ElementName|EntryType|AssignmentNumber|EntrySequence|InputValueName1|ScreenEntryValue1|Segment1|Segment2
MERGE|ElementEntryWithCosting||2019/04/01|Housing Allowance|E|E3141464|1|Amount|2500|100|300

Let’s say, you want to increase the housing allowance for Lisa Jones effective 01-April-2020. You would like to charge the amount to Cost Center 200 and Funding Source 400. In this scenario, you can update the element entry and costing information using the ElementEntrywithCosting object with the respective date.

To update the Amount, Cost Center and Funding Source using ElementEntrywithCosting object, use the ElementEntrywithCosting.dat file:

METADATA|ElementEntryWithCosting|EffectiveEndDate|EffectiveStartDate|ElementName|EntryType|AssignmentNumber|EntrySequence|InputValueName1|ScreenEntryValue1|Segment1|Segment2
MERGE|ElementEntryWithCosting||2020/04/01|Housing Allowance|E|E3141464|1|Amount|3500|200|400

To correct amount entry value supply the ElementEntry.dat file:

METADATA|ElementEntry|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate
MERGE|ElementEntry|VISION|E3141464_HSEALW_190401|2021/04/01|4712/12/31
METADATA|ElementEntryValue|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|ScreenEntryValue|ElementEntryId(SourceSystemId)
MERGE|ElementEntryValue|VISION|E3141464_HSEALW_190401_Amount|2021/04/01|4712/12/31|1000|E3141464_HSEALW_190401
Note: The source key from the ElementEntryWithCosting file is used to identify the element entry. To identify the element entry value, the same source key is used appended with the input value name.

To correct a costing segment, supply the CostAllocationAccountV3.dat file.

METADATA|CostAllocationAccountV3|SourceSystemOwner|SourceSystemId|EffectiveDate|ElementCode|LegislativeDataGroupName|SourceSubType|AssignmentId(SourceSystemId)|ElementEntryId(SourceSystemId)|SourceType|Segment4 

MERGE|CostAllocationAccountV3|VISION|E3141464_HSEALW_190401|2021/04/01|EC_US_SEARMY_ELEMENT|ZHRX_USVS_ST LDG One|COST|E3141464|E3141464_HSEALW_190401|EE|300
Note: The source key from the ElementEntryWithCosting file is used to identify the cost allocation account record.