SA Missing Tran
In ScopeTechnical: SA_MISSING_TRAN | ID: OR-MFCS-SA_MISSING_TRAN
Stores all the transaction missing in the RTLOGs at a store/tran_date/register level. This table is populated with the missing transaction numbers that are detected during the transaction sequence check.
See how this object fits into Sales Audit
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
- SA_MISSING_TRAN
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so SA_MISSING_TRAN can be established cleanly. Sequence this object with its sales audit 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 (6)
Typical Source Systems
Notes
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so SA_MISSING_TRAN can be established cleanly. Sequence this object with its sales audit peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)