Oracle CX Sales and Oracle B2B Service: Implementation Foundation — Lesson 2: Accounts, contacts, resources, territories, service requests, queues, and reference data

Learning Objectives

• Identify the configuration and data choices that shape Accounts, contacts, resources, territories, service requests, queues, and reference data.
• Run normal and boundary tests and record the outcome in configured core objects and process walkthrough.
• Separate root cause from symptom when investigating sales resources unable to access assigned accounts.

Detailed Topics

• Accounts
• Contacts
• Resources
• Territories
• Service requests
• Queues
• And reference data
• Decision ownership, prerequisites, and acceptance evidence for Accounts, contacts, resources, territories, service requests, queues, and reference data
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Accounts, contacts, resources, territories, service requests, queues, and reference data within a scenario aimed at a secure, supportable Oracle CX Sales and B2B Service foundation aligned to business processes and adoption needs. The walkthrough contrasts a valid setup with a flawed one and uses configured core objects and process walkthrough to make the difference explicit.

Hands-On Exercise

Configure and test Accounts, contacts, resources, territories, service requests, queues, and reference data with representative records. Use “sales resources unable to access assigned accounts” as the troubleshooting challenge, compare competing hypotheses, retest only the affected path, and complete configured core objects and process walkthrough for peer review.

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 Accounts, contacts, resources, territories, service requests, queues, and reference data.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how configured core objects and process walkthrough should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When results from Accounts, contacts, resources, territories, service requests, queues, and reference data are unexpected, first reproduce the issue with the same role, record, date, and transaction context. Inspect configured core objects and process walkthrough, then test whether “sales resources unable to access assigned accounts” explains the evidence before changing configuration. Retest the corrected path and one unaffected path to guard against regression.

Validation Checklist

• The scope of Accounts, contacts, resources, territories, service requests, queues, and reference data is clear, including what is deliberately excluded from the test.
• Evidence in configured core objects and process walkthrough supports each material decision and outcome.
• A negative test demonstrates that controls reject or flag an invalid condition.
• Open risks, owners, due actions, and production safeguards are documented.

Lesson Outcome

Learners can apply Accounts, contacts, resources, territories, service requests, queues, and reference data, explain the decisions made, and defend the result with configured core objects and process walkthrough.