# Manage Data Quality Lookups Setup Task Guidance

> Provides task-specific setup guidance for Manage Data Quality Lookups under the Data Quality Foundation functional area.

- Skill: `oracle/manage-data-quality-lookups-setup-task-guidance` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx get-skill add oracle/manage-data-quality-lookups-setup-task-guidance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/manage-data-quality-lookups-setup-task-guidance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/manage-data-quality-lookups-setup-task-guidance

---


# Manage Data Quality Lookups Setup Task Guidance

## Purpose

Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Data Quality Lookups` under `Data Quality Foundation`.

## Setup Task Skill Contract

- task_code: `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`
- task_name: `Manage Data Quality Lookups`
- parent_skill_id: `cx.customer-data-management.data-quality-foundation`
- pillar: `CX`
- offering: `Customer Data Management`
- functional_area: `Data Quality Foundation`
- functional_area_code: `ORA_ZCQ_DATA_QLTY_FOUNDATION`
- available_flag: `Y`
- export_import_supported_flag: `Y`
- csv_export_import_supported_flag: `Y`
- source_catalog: `knowledge/setup-task-catalog/release/setupTasksAll.json`

## Usage

Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Data Quality Lookups` under `Data Quality Foundation`.

## Setup Task Metadata

- Task name: `Manage Data Quality Lookups`
- Task code: `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`
- Available: `Y`
- Export/import supported: `Y`
- CSV export/import supported: `Y`
- CSV export/import routing: `supported`

## CSV Export, Import, and Validation Workflow

`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the shared skills:

1. Export setup task data with `shared.setup-export.task-level-export`.
2. Validate setup task data with `shared.validation.setup-data-validator`.
3. Validate reference data with `shared.validation.reference-data-validator`.
4. Import setup task data with `core.data-loader`.

Use this task metadata when invoking those skills:

- Offering: `Customer Data Management`
- Functional area / Setup Object: `Data Quality Foundation`
- Setup task name: `Manage Data Quality Lookups`
- Setup task code: `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`


## Inputs

- `implementation_objective`
- `project_context`
- `setup_task_scope`
- `setup_data_artifacts`

## Outputs

- `setup_task_plan`
- `setup_data_routing`
- `validation_checkpoints`
- `skill_run_record`
- `token_usage_record`

## Implementation Notes

Use the parent functional-area skill `cx.customer-data-management.data-quality-foundation` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.

## Task-specific lookup baseline

The exact-task Fusion page establishes this closed 21-type Standard lookup inventory:

| Lookup type | Scope |
|---|---|
| `ZCQ_IIR_MATCH_TOLERANCE` | Match tolerance |
| `ZCQ_ADDR_CLEANSED_STATUS` | Address cleansing status |
| `ZCQ_BATCH_MATCH_MODE` | Batch match mode |
| `ZCQ_PARAMETER_LEVEL` | Parameter level |
| `ZCQ_PARAMETER_TYPE` | Parameter type |
| `ZCQ_SORT_BY_SCORE` | Sort by score |
| `ZCQ_BATCH_PURGE_MODE` | Batch purge mode |
| `ZCQ_BATCH_STATUS` | Batch status |
| `ZCQ_BATCH_TYPE` | Batch type |
| `ZCQ_IIR_ASM_CHARSET` | IIR address cleansing character set |
| `ZCQ_IIR_ASM_FORCE_COUNTRY` | IIR forced country |
| `ZCQ_IIR_ASM_VAL_MODE` | IIR address validation mode |
| `ZCQ_OPERATIONS` | Data quality operations |
| `ZCQ_ORG_MATCH_OPTION_CODE` | Organization match option |
| `ZCQ_ASM_ATTRIBUTES` | Address cleansing attributes |
| `ZCQ_BATCH_REQUESTOR_TYPE` | Batch requestor type |
| `ZCQ_ENTITY` | Data quality entity |
| `ZCQ_IIR_SEARCH_WIDTH` | IIR search width |
| `ZCQ_PARAMETER_CARDINALITY` | Parameter cardinality |
| `ZCQ_PER_MATCH_OPTION_CODE` | Person match option |
| `ZCQ_IIR_ASM_PREF_LANG_TYPE` | IIR preferred language type |

Do not infer additional members from the `ZCQ_` prefix, module, or meaning. A current exact GET must reconfirm Standard category, configuration level, codes, seeded origin, and REST-described fields before a live operation.

## Supported operations and safety contract

- Read-only listing and exact type/code retrieval are supported without approval after task-membership resolution.
- Lookup-type creation/deletion, identity changes, category changes, module changes, configuration-level changes, REST-security changes, and seeded-identity changes are unsupported.
- Custom-code create, update, or delete is conditional on current configuration-level rules, `CreatedBy` seed evidence, and current REST describe. Never silently upsert and reject custom codes beginning with `ORA_`.
- Before a manual mutation, show one exact redacted preview bound to environment, method, endpoint, before/after state, payload, impact, and fingerprint; require explicit approval; send exactly one request through the shared Fusion REST client; never automatically retry; verify separately with GET.
- Export with `shared.setup-export.task-level-export` using exact TaskCode `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`. Validate with both shared validators and route import only through `core.data-loader`.
- An FSM import must preserve immutable ZIP bytes, contain exactly one safe `ASM_SETUP_CSV_METADATA.xml`, identify only this exact TaskCode, pass the Core Data Loader Task Hook, and retain an approval-bound SHA-256 envelope through submission.

See `ora-resource/` for the executable validation, lookup, design, and error rules.

