Invc Detail Temp2
In ScopeTechnical: INVC_DETAIL_TEMP2 | ID: OR-MFCS-INVC_DETAIL_TEMP2
This table is created to insert the data INVC_DETAIL data in posupld.pc batch to avoid the primary key contention. This table will be truncated by prepost post posupld function.
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
- INVC_DETAIL_TEMP2
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 INVC_DETAIL_TEMP2 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 (18)
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 INVC_DETAIL_TEMP2 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.)
