Ari Interface Test
In ScopeTechnical: ARI_INTERFACE_TEST | ID: OR-MFCS-ARI_INTERFACE_TEST
This table is used for testing the ARI API and for controling the interface behavior when ARI is not installed. It simulates users being set as ARI users and as having new alerts or not having new alerts.
See how this object fits into Configuration
Review the broader sequencing and dependencies for this domain
Migration Details
- Complexity
- Medium
- Stage
- Stage 2
- Cutover Wave
- —
- Dependency Level
- —
Dependencies
No dependencies
Target Structure
- Load API
- Table
- Target Objects
- ARI_INTERFACE_TEST
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Stage 2 to load dependent business records after prerequisite master data is stable. Load once prerequisite cross-domain reference data is available so ARI_INTERFACE_TEST can be established cleanly. Sequence this object with its merchandising system peers so merchandising reference and transaction data resolve correctly across dependent entities. (Inferred from vendor object description, dependency metadata, and Oracle Retail Merchandising System documentation.)
Cutover
Load during Stage 2 / .
Data Governance
Requires business ownership and source-to-target crosswalk governance.
Field Definitions (2)
Typical Source Systems
Notes
Load during Stage 2 to load dependent business records after prerequisite master data is stable. Load once prerequisite cross-domain reference data is available so ARI_INTERFACE_TEST can be established cleanly. Sequence this object with its merchandising system peers so merchandising reference and transaction data resolve correctly across dependent entities. (Inferred from vendor object description, dependency metadata, and Oracle Retail Merchandising System documentation.)