Oracle Identity Governance 12c: Develop Identity Provisioning Ed 1 — Lesson 3: Reconciliation, Matching, Correlation, Transformation, and Exception Handling

Technical Scope

• trusted and target reconciliation, jobs, profiles, and incremental tokens
• matching rules, correlation rules, account linking, and duplicate prevention
• field transformations, defaults, validation, entitlements, and child data
• failed events, retries, manual action, reconciliation manager, and recovery

Instructor Demonstration

Demonstrate trusted and target reconciliation, jobs, profiles, and incremental tokens within an identity engineering team onboarding a business application for automated joiner-mover-leaver provisioning, reconciliation, approvals, exception handling, and auditable deployment, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering matching rules, correlation rules, account linking, and duplicate prevention and field transformations, defaults, validation, entitlements, and child data, then test a failure, exception, or business-control scenario involving failed events, retries, manual action, reconciliation manager, and recovery.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The Reconciliation, Matching, Correlation, Transformation, and Exception Handling result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in trusted and target reconciliation, jobs, profiles, and incremental tokens, matching rules, correlation rules, account linking, and duplicate prevention, field transformations, defaults, validation, entitlements, and child data, or failed events, retries, manual action, reconciliation manager, and recovery without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for Reconciliation, Matching, Correlation, Transformation, and Exception Handling and defend the result with documented evidence.