Oracle CX Sales and Oracle B2B Service: Import and Export — Lesson 1: Import architecture, object relationships, file preparation, identifiers, and mapping strategy

Learning Objectives

• Identify the configuration and data choices that shape Import architecture, object relationships, file preparation, identifiers, and mapping strategy.
• Run normal and boundary tests and record the outcome in import design sheet and source-to-target map.
• Separate root cause from symptom when investigating parent records missing before child records are loaded.

Detailed Topics

• Import architecture
• Object relationships
• File preparation
• Identifiers
• And mapping strategy
• Decision ownership, prerequisites, and acceptance evidence for Import architecture, object relationships, file preparation, identifiers, and mapping strategy
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for Import architecture, object relationships, file preparation, identifiers, and mapping strategy, narrating each decision and showing how it contributes to repeatable CX data movement with validated mappings, recoverable loads, and complete reconciliation. The demonstration records import design sheet and source-to-target map so learners can compare configuration intent with observable behaviour.

Hands-On Exercise

Work through a role-based scenario involving Import architecture, object relationships, file preparation, identifiers, and mapping strategy. Validate the expected path, test the failure case “parent records missing before child records are loaded,” choose the safest corrective action, and capture the reasoning and outcome in import design sheet and source-to-target map.

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 architecture, object relationships, file preparation, identifiers, and mapping strategy.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how import design sheet and source-to-target map should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Import architecture, object relationships, file preparation, identifiers, and mapping strategy by checking effective settings, ownership, source records, dependencies, and recent releases. Use import design sheet and source-to-target map to locate the earliest divergence. Treat “parent records missing before child records are loaded” as a hypothesis until the same test passes after correction and still passes for a boundary case.

Validation Checklist

• Configuration and source data used for Import architecture, object relationships, file preparation, identifiers, and mapping strategy are versioned or otherwise traceable.
• Import design sheet and source-to-target map shows both the baseline and the accepted result.
• Security, performance, integration, and operational side effects have been considered where relevant.
• Recovery steps and handover notes are usable by a support practitioner.

Lesson Outcome

Learners can apply Import architecture, object relationships, file preparation, identifiers, and mapping strategy, explain the decisions made, and defend the result with import design sheet and source-to-target map.