Why does end dating position costing via HDL (CostAllocationV3) create a new open ended row

Summary:

When I end-date an existing position costing record using CostAllocationV3 in HCM Data Loader, a second row appears starting the day after the requested end date.

Content (please ensure you mask any confidential information):

Hello Expert,

I’m trying to end-date position costing effective November 8, 2026, while preserving the existing costing history. I used a MERGE with SourceType = POS, the original effective start date, and the requested effective end date.

After the load, the Position Costing section showed two rows for the same position and legislative data group:

• Original row: November 1, 2024 through November 8, 2026
• New row: November 9, 2026 with a blank effective end date