Manage Customer Hub Common Lookups Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Customer Hub Common Lookups under Customer Hub.
Setup Task Skill Contract
- task_code:
ZCH_MANAGE_CUSTOMER_HUB_COMMON_LOOKUPS - task_name:
Manage Customer Hub Common Lookups - parent_skill_id:
cx.customer-data-management.customer-hub - pillar:
CX - offering:
Customer Data Management - functional_area:
Customer Hub - functional_area_code:
ZCH_CUST_HUB_OPT - available_flag:
Y - export_import_supported_flag:
Y - csv_export_import_supported_flag:
Y - dataloader_import_mode:
FSM - businessObject: ``
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Customer Hub Common Lookups under Customer Hub.
Setup Task Metadata
- Task name:
Manage Customer Hub Common Lookups - Task code:
ZCH_MANAGE_CUSTOMER_HUB_COMMON_LOOKUPS - Available:
Y - Export/import supported:
Y - CSV export/import supported:
Y - CSV export/import routing:
supported - Data Loader import mode:
FSM - Business Object: ``
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is Y for this task, so route task setup data work through the relevant 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:
Customer Hub - Setup task name:
Manage Customer Hub Common Lookups - Setup task code:
ZCH_MANAGE_CUSTOMER_HUB_COMMON_LOOKUPS
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifacts
Outputs
setup_task_plansetup_data_routingvalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill cx.customer-data-management.customer-hub 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 6-type Standard lookup inventory:
| Lookup type | Scope |
|---|---|
ZCH_BATCH_TYPE | Customer Hub batch type |
ZCH_VALUE_CODE_OP | Code comparison operator |
ZCH_VALUE_STRING_OP | String comparison operator |
ZCH_VALUE_NUMBER_OP | Number comparison operator |
ZCH_BATCH_STATUS_CODE | Customer Hub batch status |
ZCH_VALUE_DATE_OP | Date comparison operator |
Do not infer additional members from the ZCH_ 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 and identity, category, module, configuration-level, REST-security, or seeded-identity changes are unsupported.
- Custom-code create, update, or delete is conditional on current configuration-level rules,
CreatedByseed evidence, and current REST describe. Never silently upsert and reject custom codes beginning withORA_. - A manual mutation requires an exact redacted preview, fingerprint-bound explicit approval, one non-retried shared-client request, and separate GET verification.
- Export with
shared.setup-export.task-level-exportusing exact TaskCodeZCH_MANAGE_CUSTOMER_HUB_COMMON_LOOKUPS. Validate with both shared validators and import only throughcore.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.


