SA Bank Ach
In ScopeTechnical: SA_BANK_ACH | ID: OR-MFCS-SA_BANK_ACH
This table will contain totals for each PARTNER combination that has an entry in SA_STORE_ACH for a day. It will be used to hold the bank information to be exported for ACH.
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_BANK_ACH
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 SA_BANK_ACH 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 Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so SA_BANK_ACH 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.)