fix(finance): widen rm_cost flag_*_used constraints for V2 cascade labels + pass period to Oracle sync procedure

chk_rm_cost_flag_valuation_used/chk_rm_cost_flag_marketing_used still
only allowed V1 stage labels (CONS/STORES/DEPT/PO_1/PO_2/PO_3/INIT),
but buildOrApplyCost (V2 calc engine) has written V2 cascade-resolved
labels (CR/SR/PR/CL/SL/FL, SP/PP/FP) into those columns since
ENG-RM-01/P3. Any head whose cascade resolved to a V2-only label
violated the CHECK, failing RM_COST_CALC jobs chained after oracle-sync
(e.g. head 202006002 on flag_marketing_used). Widen both constraints
to accept the V2 labels alongside the legacy V1 ones.

Also wire the Oracle procedure's newly added p_period parameter
(PRC_CST_CONSSTKPO_MGT now accepts p_period IN VARCHAR2 DEFAULT NULL
'YYYYMM') through executeProcedure via the existing but previously
unused ExecuteProcedureWithParam, so the Oracle-side refresh always
targets the same period the Go job already resolved instead of
relying on the procedure's own SYSDATE-based auto-period fallback.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: ilramdhan

services/finance/internal/application/oraclesync/sync_handler.go

@@ -180,13 +180,18 @@ func (h *SyncHandler) publishCostChain(ctx context.Context, period, createdBy st
 
 func (h *SyncHandler) executeProcedure(ctx context.Context, jobID uuid.UUID, period string) error {
 	logEntry := job.NewExecutionLog(jobID, stepProcedure, job.LogStarted,
-		fmt.Sprintf("Executing %s.%s (auto-period from SYSDATE, requested: %s)", OracleSchema, OracleProcedure, period), nil)
+		fmt.Sprintf("Executing %s.%s(p_period => '%s')", OracleSchema, OracleProcedure, period), nil)
 	if err := h.jobRepo.AddLog(ctx, logEntry); err != nil {
 		h.logger.Warn().Err(err).Msg("Failed to add procedure log")
 	}
 
 	start := time.Now()
-	err := h.oracleRepo.ExecuteProcedure(ctx, OracleSchema, OracleProcedure)
+	// Procedure now accepts p_period IN VARCHAR2 DEFAULT NULL ('YYYYMM'). We
+	// pass the period ResolvePeriod() already computed so the Go-side job
+	// period and the Oracle-side refreshed period can never diverge — the
+	// procedure's own NULL/auto-period job-mode logic (day 1-5 => previous
+	// month, day 6+ => current month) is left as a fallback for other callers.
+	err := h.oracleRepo.ExecuteProcedureWithParam(ctx, OracleSchema, OracleProcedure, period)
 	duration := time.Since(start)
 
 	if err != nil {

services/finance/migrations/postgres/000472_widen_rm_cost_flag_used_constraints.down.sql

@@ -0,0 +1,20 @@
+-- Revert chk_rm_cost_flag_valuation_used / chk_rm_cost_flag_marketing_used
+-- to the original V1-only whitelist.
+--
+-- WARNING: if any row was written with a V2 label (CR/SR/PR/CL/SL/FL or
+-- SP/PP/FP) while this migration was applied, this rollback will fail with
+-- SQLSTATE 23514 until those rows are deleted or corrected.
+
+ALTER TABLE cst_rm_cost
+    DROP CONSTRAINT IF EXISTS chk_rm_cost_flag_valuation_used;
+
+ALTER TABLE cst_rm_cost
+    ADD CONSTRAINT chk_rm_cost_flag_valuation_used
+    CHECK (flag_valuation_used IN ('CONS','STORES','DEPT','PO_1','PO_2','PO_3','INIT'));
+
+ALTER TABLE cst_rm_cost
+    DROP CONSTRAINT IF EXISTS chk_rm_cost_flag_marketing_used;
+
+ALTER TABLE cst_rm_cost
+    ADD CONSTRAINT chk_rm_cost_flag_marketing_used
+    CHECK (flag_marketing_used IN ('CONS','STORES','DEPT','PO_1','PO_2','PO_3','INIT'));

services/finance/migrations/postgres/000472_widen_rm_cost_flag_used_constraints.up.sql

@@ -0,0 +1,36 @@
+-- Migration: Widen chk_rm_cost_flag_valuation_used / chk_rm_cost_flag_marketing_used
+-- to accept the V2 cascade-resolved labels.
+--
+-- Context: ENG-RM-01/P3 (see calculate_handler_v2.go buildOrApplyCost) changed
+-- flag_valuation_used / flag_marketing_used to store the V2 engine's resolved
+-- cascade label (SelectValuationWithFlag / SelectMarketingWithFlag in
+-- calc_formulas_v2.go) instead of the V1 stage enum. The DB constraints from
+-- 000012_create_cst_rm_cost were never updated to match, so any V2 cascade
+-- resolving to a V2-only label (CR/SR/PR/CL/SL/FL for valuation,
+-- SP/PP/FP for marketing) violates the CHECK — this is what caused
+-- RM_COST_CA-* jobs chained after oracle-sync to fail with SQLSTATE 23514.
+--
+-- flag_simulation_used is untouched: buildOrApplyCost always sets it from
+-- head.FlagSimulation() (a V1 Stage), never from a V2 cascade selector.
+--
+-- Old V1 labels are kept in the allowed set for historical rows.
+
+ALTER TABLE cst_rm_cost
+    DROP CONSTRAINT IF EXISTS chk_rm_cost_flag_valuation_used;
+
+ALTER TABLE cst_rm_cost
+    ADD CONSTRAINT chk_rm_cost_flag_valuation_used
+    CHECK (flag_valuation_used IN (
+        'CONS','STORES','DEPT','PO_1','PO_2','PO_3','INIT',
+        'CR','SR','PR','CL','SL','FL'
+    ));
+
+ALTER TABLE cst_rm_cost
+    DROP CONSTRAINT IF EXISTS chk_rm_cost_flag_marketing_used;
+
+ALTER TABLE cst_rm_cost
+    ADD CONSTRAINT chk_rm_cost_flag_marketing_used
+    CHECK (flag_marketing_used IN (
+        'CONS','STORES','DEPT','PO_1','PO_2','PO_3','INIT',
+        'SP','PP','FP'
+    ));