Product Ui Integration Config
In ScopeTechnical: PRODUCT_UI_INTEGRATION_CONFIG | ID: OR-MFCS-PRODUCT_UI_INTEGRATION_CONFIG
This table is used by the application ui to launch other applications. This table will be populated during application installation process.
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
- PRODUCT_UI_INTEGRATION_CONFIG
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 PRODUCT_UI_INTEGRATION_CONFIG 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 (2)
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 PRODUCT_UI_INTEGRATION_CONFIG 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.)