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:
- Export setup task data with
shared.setup-export.task-level-export.
- Validate setup task data with
shared.validation.setup-data-validator.
- Validate reference data with
shared.validation.reference-data-validator.
- 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.
1---2skill_id: "cx.customer-data-management.data-quality-foundation.manage-data-quality-lookups"3name: manage-data-quality-lookups-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Data Quality Lookups under the Data Quality Foundation functional area."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Data Quality Foundation"9functional_area_code: "ORA_ZCQ_DATA_QLTY_FOUNDATION"10task_code: "ZCQ_MANAGE_DATA_QUALITY_LOOKUPS"11task_name: "Manage Data Quality Lookups"12parent_skill_id: "cx.customer-data-management.data-quality-foundation"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16dataloader_import_mode: "FSM"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "planning"20execution_mode: "assisted"21owner_team: "CX customer data management pillar team"22version: "0.1.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28outputs:29 - "setup_task_plan"30 - "setup_data_routing"31 - "validation_checkpoints"32 - "skill_run_record"33 - "token_usage_record"34depends_on:35 - "shared.setup-export.task-level-export"36 - "shared.validation.setup-data-validator"37 - "shared.validation.reference-data-validator"38 - "core.data-loader"39uses_core:40 - "core.project-mgmt.artifact-version-manager"41 - "core.project-mgmt.artifact-registry-manager"42 - "core.project-mgmt.project-state-manager"43persists_project_state: true44token_usage_tracking:45 enabled: true46 granularity: "per_skill_run"47 artifact_type: "token_usage_record"48 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"49 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"50 required_fields:51 - "activity_start_time"52 - "skill_id"53 - "task"54 - "trigger"55 - "artifacts_written"56 - "files_read"57 - "estimated_input_tokens"58 - "estimated_output_tokens"59 - "estimated_total_tokens"60 - "estimation_method"61 - "notes"62state_updates:63 - "setup_task_sequence"64 - "configuration_blueprints"65 - "validation_results"66 - "token_usage_records"67workspace_outputs:68 - artifact_type: "configuration_blueprint"69 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/data-quality-foundation/manage-data-quality-lookups/current/"70 versioning_policy: "major-new-version-minor-confirm-update"71 - artifact_type: "validation_result"72 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/data-quality-foundation/manage-data-quality-lookups/current/"73 versioning_policy: "major-new-version-minor-confirm-update"74 - artifact_type: "skill_run"75 default_location: "project/{project_id}/state/runs/"76 versioning_policy: "append-only"77 - artifact_type: "token_usage_record"78 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"79 versioning_policy: "append-only"80applicability:81 industries:82 - "All"83 countries:84 - "All"85 fusion_releases:86 - "Current Oracle Fusion Cloud release"87side_effects: []88required_privileges: []89metadata:90 source: https://skillmd.com/skills/oracle/manage-data-quality-lookups-setup-task-guidance91---9293# Manage Data Quality Lookups Setup Task Guidance9495## Purpose9697Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Data Quality Lookups` under `Data Quality Foundation`.9899## Setup Task Skill Contract100101- task_code: `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`102- task_name: `Manage Data Quality Lookups`103- parent_skill_id: `cx.customer-data-management.data-quality-foundation`104- pillar: `CX`105- offering: `Customer Data Management`106- functional_area: `Data Quality Foundation`107- functional_area_code: `ORA_ZCQ_DATA_QLTY_FOUNDATION`108- available_flag: `Y`109- export_import_supported_flag: `Y`110- csv_export_import_supported_flag: `Y`111- source_catalog: `knowledge/setup-task-catalog/release/setupTasksAll.json`112113## Usage114115Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Data Quality Lookups` under `Data Quality Foundation`.116117## Setup Task Metadata118119- Task name: `Manage Data Quality Lookups`120- Task code: `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`121- Available: `Y`122- Export/import supported: `Y`123- CSV export/import supported: `Y`124- CSV export/import routing: `supported`125126## CSV Export, Import, and Validation Workflow127128`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the shared skills:1291301. Export setup task data with `shared.setup-export.task-level-export`.1312. Validate setup task data with `shared.validation.setup-data-validator`.1323. Validate reference data with `shared.validation.reference-data-validator`.1334. Import setup task data with `core.data-loader`.134135Use this task metadata when invoking those skills:136137- Offering: `Customer Data Management`138- Functional area / Setup Object: `Data Quality Foundation`139- Setup task name: `Manage Data Quality Lookups`140- Setup task code: `ZCQ_MANAGE_DATA_QUALITY_LOOKUPS`141142143## Inputs144145- `implementation_objective`146- `project_context`147- `setup_task_scope`148- `setup_data_artifacts`149150## Outputs151152- `setup_task_plan`153- `setup_data_routing`154- `validation_checkpoints`155- `skill_run_record`156- `token_usage_record`157158## Implementation Notes159160Use 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.161162## Task-specific lookup baseline163164The exact-task Fusion page establishes this closed 21-type Standard lookup inventory:165166| Lookup type | Scope |167|---|---|168| `ZCQ_IIR_MATCH_TOLERANCE` | Match tolerance |169| `ZCQ_ADDR_CLEANSED_STATUS` | Address cleansing status |170| `ZCQ_BATCH_MATCH_MODE` | Batch match mode |171| `ZCQ_PARAMETER_LEVEL` | Parameter level |172| `ZCQ_PARAMETER_TYPE` | Parameter type |173| `ZCQ_SORT_BY_SCORE` | Sort by score |174| `ZCQ_BATCH_PURGE_MODE` | Batch purge mode |175| `ZCQ_BATCH_STATUS` | Batch status |176| `ZCQ_BATCH_TYPE` | Batch type |177| `ZCQ_IIR_ASM_CHARSET` | IIR address cleansing character set |178| `ZCQ_IIR_ASM_FORCE_COUNTRY` | IIR forced country |179| `ZCQ_IIR_ASM_VAL_MODE` | IIR address validation mode |180| `ZCQ_OPERATIONS` | Data quality operations |181| `ZCQ_ORG_MATCH_OPTION_CODE` | Organization match option |182| `ZCQ_ASM_ATTRIBUTES` | Address cleansing attributes |183| `ZCQ_BATCH_REQUESTOR_TYPE` | Batch requestor type |184| `ZCQ_ENTITY` | Data quality entity |185| `ZCQ_IIR_SEARCH_WIDTH` | IIR search width |186| `ZCQ_PARAMETER_CARDINALITY` | Parameter cardinality |187| `ZCQ_PER_MATCH_OPTION_CODE` | Person match option |188| `ZCQ_IIR_ASM_PREF_LANG_TYPE` | IIR preferred language type |189190Do 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.191192## Supported operations and safety contract193194- Read-only listing and exact type/code retrieval are supported without approval after task-membership resolution.195- Lookup-type creation/deletion, identity changes, category changes, module changes, configuration-level changes, REST-security changes, and seeded-identity changes are unsupported.196- 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_`.197- 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.198- 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`.199- 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.200201See `ora-resource/` for the executable validation, lookup, design, and error rules.