Lc Ordapply
In ScopeTechnical: LC_ORDAPPLY | ID: OR-MFCS-LC_ORDAPPLY
This table will be used as a staging area during the process of attaching Purchase Orders to Letters of Credit. Data will be written to this table as Purchase Orders are Approved and will be removed as the Purchase Order is attached to a Letter of Credit or the Order is Unapproved.
See how this object fits into Trade Management
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
- LC_ORDAPPLY
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 LC_ORDAPPLY can be established cleanly. Sequence this object with its trade management 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 (5)
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 LC_ORDAPPLY can be established cleanly. Sequence this object with its trade management peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)