dokumentacja

confluence/FILE_ARCHIVER_Guide.md

@@ -19,7 +19,18 @@ The FILE_ARCHIVER package provides flexible archival strategies that accommodate
 - **Schema**: CT_MRDS
 - **Package**: FILE_ARCHIVER
 - **Current Version**: 3.1.0
-- **Dependencies**: ENV_MANAGER, FILE_MANAGER, cloud_wrapper, A_SOURCE_FILE_CONFIG, A_LOAD_HISTORY
+- **Dependencies**: ENV_MANAGER, FILE_MANAGER, cloud_wrapper, A_SOURCE_FILE_CONFIG, A_SOURCE_FILE_RECEIVED, A_WORKFLOW_HISTORY
+
+### Critical Prerequisites
+
+⚠️ **IMPORTANT**: FILE_ARCHIVER requires data to be registered in `CT_MRDS.A_SOURCE_FILE_RECEIVED` table. This table is automatically populated when files are processed through the modern Airflow + DBT workflow via `FILE_MANAGER.PROCESS_SOURCE_FILE`.
+
+**For legacy data migrated from Informatica + WLA system:**
+- Legacy data exported using `DATA_EXPORTER` does NOT automatically create `A_SOURCE_FILE_RECEIVED` records
+- Without these records, FILE_ARCHIVER **CANNOT** archive the data
+- See [System Migration Guide](System_Migration_Informatica_to_Airflow_DBT.md) for workaround strategies
+
+**Recommendation for legacy data**: Export directly to ARCHIVE bucket using `DATA_EXPORTER.EXPORT_TABLE_DATA_BY_DATE` with `pBucketArea => 'ARCHIVE'` to bypass this requirement
 
 ## Archival Strategies
 
@@ -542,7 +553,8 @@ WHERE object_name = 'FILE_ARCHIVER';
 
 ### Database Objects
 - **Table**: CT_MRDS.A_SOURCE_FILE_CONFIG - Configuration storage
-- **Table**: CT_ODS.A_LOAD_HISTORY - Workflow tracking
+- **Table**: CT_MRDS.A_SOURCE_FILE_RECEIVED - File processing tracking
+- **Table**: CT_MRDS.A_WORKFLOW_HISTORY - Workflow execution tracking (Airflow + DBT)
 - **Trigger**: TRG_BI_A_SRC_FILE_CFG_ARCH_VAL - Configuration validation
 - **Credential**: DEF_CRED_ARN - OCI bucket access