Readiness Tool for Delivery Continuity in IFS Cloud

This tool is designed to analyze the codebase and database schema to ensure compliance with the new code architecture we have with IFS Cloud 25R2 which conforms to Oracle Edition-Based Redefinition(EBR) standards. It will generate a comprehensive report highlighting non-compliant areas, along with the required changes, enabling customers to proactively address issues before deployment.

This tool is integrated to the IFS Developer Studio. It will only validate aspects not covered by the Preparation Tool, ensuring no overlap and maintaining a clear separation of responsibilities.

Once you check out the repo, the tool can be executed either at the project level or on an individual component.

Executing this tool results in an output as shown below indicating the tests that have passed and failed.

Following are the validations the tool performs, and notifies the user in case of discrepancies.

1. Table Naming Convention - All tables in the IFSAPP (and optionally IFSINFO) schema must use the _RTB suffix.

2. EBR Preparation Method Usage - All current tables must be passed to the Prepare_Table_For_Ebr method in cdb.

3. Indexes and Constraints - All indexes and constraints must be defined on the _RTB tables, not on editioning views.

4. Declarative Syntax - All entity modeling must use declarative syntax (e.g., .storage files). Non-declarative syntax must be converted.

5. Temporary Tables - No temporary or regular tables should exist without editioning views.

6. Materialized Views - All materialized views must be passed to the Prepare_MV_For_Ebr method. Naming convention: original name as a synonym, and actual MV with _RMV suffix.