IM Match Doc
In ScopeTechnical: IM_MATCH_DOC | ID: OR-IM-IM_MATCH_DOC
Stores invoice matching detail for IM match doc in Oracle Retail Invoice Matching, linking invoices, credit notes, receipts, purchase orders, or cost components used during match processing. It supports discrepancy analysis, resolution workflows, and audit reporting.
See how this object fits into Invoice Matching
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
- IM_MATCH_DOC
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 IM_MATCH_DOC can be established cleanly. Sequence this object with its invoice matching peers so IMCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail IMCS documentation.)
Cutover
Load during Stage 2 / .
Data Governance
Requires business ownership and source-to-target crosswalk governance.
Field Definitions (13)
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 IM_MATCH_DOC can be established cleanly. Sequence this object with its invoice matching peers so IMCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail IMCS documentation.)