Refactor archival strategies in FILE_ARCHIVER package

- Removed CURRENT_MONTH_ONLY strategy, replacing it with MINIMUM_AGE_MONTHS = 0 for current month retention.
- Updated validation logic to allow MINIMUM_AGE_MONTHS to be non-negative.
- Consolidated documentation to reflect changes in archival strategies.
- Adjusted rollback script to reset all archival parameters to NULL for 25 Release 01 tables.
- Enhanced README and installation scripts to clarify new configuration requirements and usage examples.
- Updated version history to indicate breaking changes and migration steps for existing configurations.

MARS_Packages/REL01_ADDITIONS/MARS-828/README.md

@@ -17,7 +17,7 @@ WHERE extract(day from (systimestamp - workflow_start)) > DAYS_FOR_ARCHIVE_THRES
 
 **Solution**: Introduce ARCHIVAL_STRATEGY configuration column with four strategies:
 - `THRESHOLD_BASED` - Days-based threshold (backward compatible)
-- `CURRENT_MONTH_ONLY` - Keep only current month data
+- `MINIMUM_AGE_MONTHS` - Retain data for specified months (0 = current month only)
 - `MINIMUM_AGE_MONTHS` - Archive data older than X months
 - `HYBRID` - Combination of current month and minimum age
 
@@ -38,7 +38,7 @@ DAYS_FOR_ARCHIVE_THRESHOLD NUMBER DEFAULT 30
 ARCHIVAL_STRATEGY VARCHAR2(30) DEFAULT 'THRESHOLD_BASED' NOT NULL,
 MINIMUM_AGE_MONTHS NUMBER(3),
 DAYS_FOR_ARCHIVE_THRESHOLD NUMBER DEFAULT 30,
-CONSTRAINT CHK_ARCHIVAL_STRATEGY CHECK (ARCHIVAL_STRATEGY IN ('THRESHOLD_BASED', 'CURRENT_MONTH_ONLY', 'MINIMUM_AGE_MONTHS', 'HYBRID'))
+CONSTRAINT CHK_ARCHIVAL_STRATEGY CHECK (ARCHIVAL_STRATEGY IN ('THRESHOLD_BASED', 'MINIMUM_AGE_MONTHS', 'HYBRID'))
 ```
 
 **New Trigger**: TRG_BI_ARCHIVAL_STRATEGY_VAL
@@ -69,17 +69,17 @@ CONSTRAINT CHK_ARCHIVAL_STRATEGY CHECK (ARCHIVAL_STRATEGY IN ('THRESHOLD_BASED',
 | Strategy | WHERE Clause Logic | Configuration Required | Use Case |
 |----------|-------------------|----------------------|----------|
 | `THRESHOLD_BASED` | `extract(day from (systimestamp - workflow_start)) > DAYS_FOR_ARCHIVE_THRESHOLD` | DAYS_FOR_ARCHIVE_THRESHOLD | Legacy compatibility |
-| `CURRENT_MONTH_ONLY` | `TRUNC(workflow_start, 'MM') < TRUNC(SYSDATE, 'MM')` | None | General sources (LM, TOP) |
+| `MINIMUM_AGE_MONTHS` | `workflow_start < ADD_MONTHS(TRUNC(SYSDATE, 'MM'), -N)` | MINIMUM_AGE_MONTHS (0=current month) | All sources |
 | `MINIMUM_AGE_MONTHS` | `workflow_start < ADD_MONTHS(TRUNC(SYSDATE, 'MM'), -X)` | MINIMUM_AGE_MONTHS | CSDB (6 months retention) |
-| `HYBRID` | Both CURRENT_MONTH_ONLY AND MINIMUM_AGE_MONTHS | MINIMUM_AGE_MONTHS | Advanced scenarios |
+| `HYBRID` | Combines month truncation AND minimum age | MINIMUM_AGE_MONTHS | Advanced scenarios |
 
 ## Configuration Examples
 
 ```sql
 -- LM/TOP sources: Archive everything except current month
 UPDATE A_SOURCE_FILE_CONFIG 
-SET ARCHIVAL_STRATEGY = 'CURRENT_MONTH_ONLY',
-    MINIMUM_AGE_MONTHS = NULL
+SET ARCHIVAL_STRATEGY = 'MINIMUM_AGE_MONTHS',
+    MINIMUM_AGE_MONTHS = 0,  -- 0 = current month only
 WHERE A_SOURCE_KEY IN ('LM', 'TOP');
 
 -- CSDB: Archive only data older than 6 months
@@ -189,7 +189,7 @@ sql "ADMIN/Cloudpass#34@ggmichalski_high" "@rollback_mars828.sql"
 **Main Test Script**: test/test_archival_strategies.sql
 
 ```sql
--- Test 1: CURRENT_MONTH_ONLY strategy
+-- Test 1: MINIMUM_AGE_MONTHS=0 strategy (current month only)
 -- Expected: Archives data from previous months only
 SELECT COUNT(*) FROM table WHERE TRUNC(workflow_start, 'MM') < TRUNC(SYSDATE, 'MM');
 
@@ -249,7 +249,7 @@ No automatic migration required. New columns have sensible defaults:
 - MINIMUM_AGE_MONTHS = NULL (not required for THRESHOLD_BASED)
 
 ## Version History
-- **v3.0.0** (2026-01-27): Added flexible archival strategies (CURRENT_MONTH_ONLY, MINIMUM_AGE_MONTHS, HYBRID) via ARCHIVAL_STRATEGY configuration
+- **v3.0.0** (2026-01-27): Added flexible archival strategies (MINIMUM_AGE_MONTHS with 0=current month, HYBRID) via ARCHIVAL_STRATEGY configuration
 - **v2.0.0** (2025-10-01): Initial FILE_ARCHIVER package with threshold-based archival
 
 ## Related JIRA Issues