RMS Async Retry
In ScopeTechnical: RMS_ASYNC_RETRY | ID: OR-MFCS-RMS_ASYNC_RETRY
Table that tracks each attempt to complete an asynchronous call. If the initial call is successful, there will only be one row for the rms_async_id with null in the error_message column.
See how this object fits into Foundation Data
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
- RMS_ASYNC_RETRY
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so RMS_ASYNC_RETRY can be established cleanly. Sequence this object with its foundation data peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)
Cutover
Load during Stage 2 / .
Data Governance
Requires business ownership and source-to-target crosswalk governance.
Field Definitions (7)
Typical Source Systems
Notes
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so RMS_ASYNC_RETRY can be established cleanly. Sequence this object with its foundation data peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)