Oracle CX Sales and Oracle B2B Service: Customer Data Mgmt (CDM) — Lesson 3: Import, enrichment, hierarchy maintenance, source-system references, and bulk correction

Learning Objectives

• Identify the configuration and data choices that shape Import, enrichment, hierarchy maintenance, source-system references, and bulk correction.
• Run normal and boundary tests and record the outcome in controlled customer data load and reconciliation report.
• Separate root cause from symptom when investigating imported contacts attaching to the wrong account hierarchy.

Detailed Topics

• Import
• Enrichment
• Hierarchy maintenance
• Source-system references
• And bulk correction
• Decision ownership, prerequisites, and acceptance evidence for Import, enrichment, hierarchy maintenance, source-system references, and bulk correction
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Import, enrichment, hierarchy maintenance, source-system references, and bulk correction from requirement through execution and review. Learners see where evidence should be collected, how controlled customer data load and reconciliation report supports verification, and which warning signs demand investigation.

Hands-On Exercise

Build or execute Import, enrichment, hierarchy maintenance, source-system references, and bulk correction for a defined business case. Introduce the condition “imported contacts attaching to the wrong account hierarchy,” inspect the resulting evidence, correct the cause without discarding the audit trail, and document the final state in controlled customer data load and reconciliation report.

1. Confirm scope, access, sample records, and acceptance criteria.
2. Perform the configuration or transaction using a controlled sequence.
3. Inspect outputs and downstream effects rather than relying on screen messages alone.
4. Close with a support note, preventive action, and reproducible validation step.

Scenario Analysis

• Clarify the business trigger, affected roles, required records, and acceptable result for Import, enrichment, hierarchy maintenance, source-system references, and bulk correction.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how controlled customer data load and reconciliation report should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Import, enrichment, hierarchy maintenance, source-system references, and bulk correction by checking effective settings, ownership, source records, dependencies, and recent releases. Use controlled customer data load and reconciliation report to locate the earliest divergence. Treat “imported contacts attaching to the wrong account hierarchy” as a hypothesis until the same test passes after correction and still passes for a boundary case.

Validation Checklist

• The stated requirement for Import, enrichment, hierarchy maintenance, source-system references, and bulk correction is linked to an owner and an observable acceptance condition.
• Controlled customer data load and reconciliation report contains enough detail for another practitioner to repeat the check.
• Normal processing, one boundary condition, and the identified failure path have all been tested.
• Access, data integrity, downstream impact, rollback, and support ownership are recorded.

Lesson Outcome

Learners can apply Import, enrichment, hierarchy maintenance, source-system references, and bulk correction, explain the decisions made, and defend the result with controlled customer data load and reconciliation report.