Manage Customer Data Management Options
Purpose
Export, review, change, import, and validate only the profile-option-backed settings exposed by Manage Customer Data Management Options under Customer Hub.
Setup Task Skill Contract
- task_code:
ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS
- task_name:
Manage Customer Data Management Options
- 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
Supported Operations
export: Export this exact task with shared.setup-export.task-level-export and preserve the returned ZIP as an immutable baseline.
prepare_import: Copy the baseline, change only existing FND_APP_PROFILE_VALUE.csv SITE rows for supported codes, validate the package, and produce an exact before/after preview.
import: Submit the reviewed immutable ZIP only through core.data-loader in FSM mode and use its approval workflow unchanged.
view: Read one supported profile definition and configured SITE value through core.fusion-api.apps-common.
update_one: Create or update one supported SITE value through core.fusion-api.apps-common after an exact preview and explicit approval. Use this route when a supported profile is omitted from an otherwise successful task export; never synthesize an absent FSM row.
validate or status: Validate the artifact or continue an existing export/import process without creating another mutation.
Reject arbitrary profile-option codes, product or user levels, profile-option definition changes, loose CSV imports, and edits to audit columns or unrelated task rows.
Supported Option Inventory
The inventory is closed. UI labels are aliases; runtime validation and CSV edits use the stored codes below. Lookup-backed values must also be active in the target environment when the preview is built.
Duplicate Identification
| Setting |
Profile Option Code |
Stored Values |
| Enable Real-Time Key Generation |
ORA_ZCQ_ENABLE_REALTIME_KEYGEN |
Y, N |
| Number of Batch Key Generation Jobs |
ZCQ_BATCH_KEYGEN_NUMJOBS |
Positive integer; Oracle publishes no maximum |
| Number of Batch Matching Jobs |
ZCQ_BATCH_MATCH_NUMJOBS |
Positive integer; Oracle publishes no maximum |
| Number of Real-Time Possible Duplicates |
ORA_ZCQ_MAX_CANDIDATES |
Positive integer; documented default 20 |
| Batch Duplicate Identification Debug Level |
ORA_ZCQ_BATCHMATCH_DEBUG_LEVEL |
DEBUG, INFO |
| Enable Fine Logging for Match Value Conversion |
ORA_ZCQ_CONVERTER_FINEST_LOGGING |
Y, N |
Duplicate Resolution
| Setting |
Profile Option Code |
Stored Values |
| Maximum Concurrent Resolution Request Jobs |
ORA_ZCH_MERGE_MAX_REQUEST_LIMIT |
Positive integer or blank; documented default 10 |
| Merge Mode |
ORA_ZCH_OPTIMIZE_LOAD |
Y optimized, N standard |
| Resolution Request Job Size |
ORA_ZCH_MERGE_REQUEST_BATCH_SIZE_LIMIT |
Positive integer or blank; documented default 100 |
| Merge Scope |
ORA_ZCH_MERGE_SCOPE |
ALL, CDM, CRM, CDM_HV |
| Merge Request Notifications |
ZCH_REQUEST_NOTIFICATIONS |
ORA_ZCH_NOTIFICATION_DEF_YES, ORA_ZCH_NOTIFICATION_DEF_NO, ORA_ZCH_NOTIFICATION_DISABLED |
| Automerge Threshold |
ZCH_AUTO_MERGE_THRESHOLD |
Integer 0 through 101; 101 disables automerge |
| Customer Center Merge Requests |
ZCA_MERGE_REQUEST |
Y, N |
| Default Resolution Type |
ZCH_DEDUP_REQUEST_TYPE_OPTION |
MERGE, CHOICE, LINK, LINK_DUP |
| Data Steward Resolution Request Handling |
ORA_ZCH_DS_MERGE_REQUESTS |
ZCH_PROCESS_WITHOUT_APPROVAL, ZCH_SUBMIT_FOR_APPROVAL |
| User Resolution Request Handling |
ZCH_USER_MERGE_REQUESTS |
ZCH_PROCESS_WITHOUT_APPROVAL, ZCH_SUBMIT_FOR_APPROVAL |
| Agreement Rules Type |
ZCH_AGREEMENT_TYPE |
ORA_ZCH_DEFAULT, ORA_ZCH_GROOVY, ORA_ZCH_RULE |
| Attribute Selection Type |
ZCH_SETATTRIBUTE_TYPE |
ORA_ZCH_NONE, ORA_ZCH_SC_OLDEST, ORA_ZCH_SC_NEWEST, ORA_ZCH_RULE |
| Enable Attribute Source Tracking |
ZCH_ENABLE_SURVIVORSHIP |
Y, N; once enabled, do not disable |
| Master Record Selection |
ORA_ZCH_SETMASTER_TYPE |
RULE, OLDEST, NEWEST, ANY, ORA_ZCH_GROOVY |
| Merge Identical Child Records |
ORA_ZCH_MERGE_IDENTICAL |
Y, N |
| Add Groovy to Attribute Selection |
ZCH_GROOVY_RULE |
Y, N |
| Main Record Selection for Link |
ORA_ZCH_LINK_SETMAIN_TYPE |
ANY, NEWEST, OLDEST, ORA_ZCH_GROOVY, ORA_ZCH_QUALITY_SCORE |
| Autolink Threshold |
ZCH_AUTO_LINK_THRESHOLD |
Integer 0 through 101; 101 disables autolink |
The exact UI meaning for each lookup code is resolved through the lookup type named by the live profile definition. Do not replace a stored code with its display label.
FSM CSV Change Workflow
- Export exact TaskCode
ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS and retain the original ZIP and SHA-256.
- Require exactly one safe
ASM_SETUP_CSV_METADATA.xml and the task identity in its metadata. For a profile-value edit, require FND_APP_PROFILE_VALUE.csv.
- Match an existing row by profile code, application id,
LevelName=SITE, and LevelValue=SITE. Modify only ProfileOptionValue in a copied package.
- Never add an absent row. Report
export_content_discrepancy and use update_one only after the live definition confirms SITE is enabled and updatable.
- Validate every requested value against this inventory and, for lookup-backed values, against the current active lookup codes.
- Show target environment, task, option code, UI meaning, current stored value, proposed stored value, ZIP path, and SHA-256. Any change invalidates approval.
- Route the immutable reviewed ZIP to
core.data-loader; do not duplicate its Task Hook, adapter, approval, submission, polling, or retry logic.
- After import, re-export or read every affected configured SITE value and run the task's
Validate Setup process. Never report success from submission alone.
For update_one, perform the same membership, level, value, dependency, preview, approval, and verification gates, then let core.fusion-api.apps-common own the profile-value child-resource operation. Do not retry a POST or PATCH automatically.
Design Constraints
- Source-confidence attribute selection requires
ZCH_ENABLE_SURVIVORSHIP=Y.
- Once attribute source tracking is enabled, block a request to set it to
N.
CDM_HV merge scope is incompatible with business-rule or Groovy-based master, attribute, or agreement selection.
ZCH_GROOVY_RULE=Y is incompatible with ZCH_SETATTRIBUTE_TYPE=ORA_ZCH_RULE.
- Autolink threshold applies to link resolution; automerge threshold applies to merge resolution.
- Blank handling is supported only for options whose Oracle contract explicitly permits no value. Do not translate blank, null, and an empty quoted CSV field interchangeably without target evidence.
Sources and Runtime Evidence
Use current Oracle Customer Data Management documentation for setting purpose, UI grouping, defaults, and dependency rules. Treat the target profile definition, profile levels, active lookup codes, and fresh task export as runtime authority for stored codes, eligibility, current values, and package shape. A mismatch is a blocker, not permission to broaden the inventory.
Oracle documentation:
Golden Scenarios
- Existing exported row: Export the exact task, change
ORA_ZCH_MERGE_SCOPE from one active stored lookup code to another in its existing SITE row, produce a ZIP/hash-bound preview, and import only through Core Data Loader after its approval gate.
- Profile omitted from export: When
ORA_ZCQ_MAX_CANDIDATES is absent from FND_APP_PROFILE_VALUE.csv, report export_content_discrepancy; verify its live SITE definition and use update_one only after an exact direct-update preview and approval.
- Display label supplied: If a user supplies
All functional areas instead of stored code ALL, resolve and display the mapping but require the exact code in the reviewed change. Never write the UI label to CSV or the profile-value REST resource.
- Unsafe dependency: Block
ZCH_ENABLE_SURVIVORSHIP=N after source tracking has been enabled, and block a CDM_HV merge scope combined with incompatible business-rule or Groovy selections.
Setup Task Metadata
- Task name:
Manage Customer Data Management Options
- Task code:
ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS
- 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 Data Management Options
- Setup task code:
ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS
For import, provide the exact immutable ZIP and target environment to Core Data Loader. Do not rewrite ASM_SETUP_CSV_METADATA.xml or construct a replacement package from loose CSV files.
Preflight and Error Handling
Load the task-local ora-resource files before preview or execution. Confirm the fixed task identity, environment, requested operation, closed inventory membership, SITE eligibility, current value, allowed stored value, dependencies, immutable artifact, and required approval. Classify and persist failures using the task-local error contract. Redact credentials, tokens, client secrets, token-cache contents, Authorization headers, full base64 packages, and sensitive values.
Inputs
operation
implementation_objective
project_context
fusion_environment_context
setup_task_scope
setup_data_artifacts
requested_option_changes
execution_approval
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
fsm_export_package
profile_option_change_preview
profile_option_change_result
execution_result
diagnostics
audit_summary
skill_run_record
token_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.
1---2skill_id: "cx.customer-data-management.customer-hub.manage-customer-data-management-options"3name: manage-customer-data-management-options-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Customer Data Management Options under the Customer Hub functional area."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Customer Hub"9functional_area_code: "ZCH_CUST_HUB_OPT"10task_code: "ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS"11task_name: "Manage Customer Data Management Options"12parent_skill_id: "cx.customer-data-management.customer-hub"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: "orchestration"20execution_mode: "hybrid"21owner_team: "CX customer data management pillar team"22version: "0.1.0"23inputs:24 - "operation"25 - "implementation_objective"26 - "project_context"27 - "fusion_environment_context"28 - "setup_task_scope"29 - "setup_data_artifacts"30 - "requested_option_changes"31 - "execution_approval"32outputs:33 - "setup_task_plan"34 - "setup_data_routing"35 - "validation_checkpoints"36 - "fsm_export_package"37 - "profile_option_change_preview"38 - "profile_option_change_result"39 - "execution_result"40 - "diagnostics"41 - "audit_summary"42 - "skill_run_record"43 - "token_usage_record"44depends_on:45 - "core.fusion-api.apps-common"46 - "shared.setup-export.task-level-export"47 - "shared.validation.setup-data-validator"48 - "shared.validation.reference-data-validator"49 - "core.data-loader"50uses_core:51 - "core.project-mgmt.artifact-version-manager"52 - "core.project-mgmt.artifact-registry-manager"53 - "core.project-mgmt.project-state-manager"54persists_project_state: true55token_usage_tracking:56 enabled: true57 granularity: "per_skill_run"58 artifact_type: "token_usage_record"59 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"60 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"61 required_fields:62 - "activity_start_time"63 - "skill_id"64 - "task"65 - "trigger"66 - "artifacts_written"67 - "files_read"68 - "estimated_input_tokens"69 - "estimated_output_tokens"70 - "estimated_total_tokens"71 - "estimation_method"72 - "notes"73state_updates:74 - "setup_task_sequence"75 - "configuration_blueprints"76 - "validation_results"77 - "token_usage_records"78workspace_outputs:79 - artifact_type: "configuration_blueprint"80 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/customer-hub/manage-customer-data-management-options/current/"81 versioning_policy: "major-new-version-minor-confirm-update"82 - artifact_type: "validation_result"83 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/customer-hub/manage-customer-data-management-options/current/"84 versioning_policy: "major-new-version-minor-confirm-update"85 - artifact_type: "skill_run"86 default_location: "project/{project_id}/state/runs/"87 versioning_policy: "append-only"88 - artifact_type: "token_usage_record"89 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"90 versioning_policy: "append-only"91applicability:92 industries:93 - "All"94 countries:95 - "All"96 fusion_releases:97 - "Current Oracle Fusion Cloud release"98side_effects:99 - "Creates and downloads a task-scoped FSM CSV export through shared.setup-export.task-level-export."100 - "After Core Data Loader validation and approval, may import an immutable FSM ZIP containing reviewed profile-value changes."101 - "After an exact direct-update preview and approval, may create or update one supported site-level profile value through core.fusion-api.apps-common."102required_privileges:103 - "Fusion privileges to export and import setup task CSV data."104 - "FND_APP_MANAGE_ALL_PROFILE_VALUES_PRIV for a direct site-level profile-value update."105metadata:106 source: https://skillmd.com/skills/oracle/manage-customer-data-management-options-setup-task-guidance107---108109# Manage Customer Data Management Options110111## Purpose112113Export, review, change, import, and validate only the profile-option-backed settings exposed by `Manage Customer Data Management Options` under `Customer Hub`.114115## Setup Task Skill Contract116117- task_code: `ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS`118- task_name: `Manage Customer Data Management Options`119- parent_skill_id: `cx.customer-data-management.customer-hub`120- pillar: `CX`121- offering: `Customer Data Management`122- functional_area: `Customer Hub`123- functional_area_code: `ZCH_CUST_HUB_OPT`124- available_flag: `Y`125- export_import_supported_flag: `Y`126- csv_export_import_supported_flag: `Y`127- dataloader_import_mode: `FSM`128- businessObject: ``129- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`130131## Supported Operations1321331. `export`: Export this exact task with `shared.setup-export.task-level-export` and preserve the returned ZIP as an immutable baseline.1342. `prepare_import`: Copy the baseline, change only existing `FND_APP_PROFILE_VALUE.csv` SITE rows for supported codes, validate the package, and produce an exact before/after preview.1353. `import`: Submit the reviewed immutable ZIP only through `core.data-loader` in FSM mode and use its approval workflow unchanged.1364. `view`: Read one supported profile definition and configured SITE value through `core.fusion-api.apps-common`.1375. `update_one`: Create or update one supported SITE value through `core.fusion-api.apps-common` after an exact preview and explicit approval. Use this route when a supported profile is omitted from an otherwise successful task export; never synthesize an absent FSM row.1386. `validate` or `status`: Validate the artifact or continue an existing export/import process without creating another mutation.139140Reject arbitrary profile-option codes, product or user levels, profile-option definition changes, loose CSV imports, and edits to audit columns or unrelated task rows.141142## Supported Option Inventory143144The inventory is closed. UI labels are aliases; runtime validation and CSV edits use the stored codes below. Lookup-backed values must also be active in the target environment when the preview is built.145146### Duplicate Identification147148| Setting | Profile Option Code | Stored Values |149|---|---|---|150| Enable Real-Time Key Generation | `ORA_ZCQ_ENABLE_REALTIME_KEYGEN` | `Y`, `N` |151| Number of Batch Key Generation Jobs | `ZCQ_BATCH_KEYGEN_NUMJOBS` | Positive integer; Oracle publishes no maximum |152| Number of Batch Matching Jobs | `ZCQ_BATCH_MATCH_NUMJOBS` | Positive integer; Oracle publishes no maximum |153| Number of Real-Time Possible Duplicates | `ORA_ZCQ_MAX_CANDIDATES` | Positive integer; documented default `20` |154| Batch Duplicate Identification Debug Level | `ORA_ZCQ_BATCHMATCH_DEBUG_LEVEL` | `DEBUG`, `INFO` |155| Enable Fine Logging for Match Value Conversion | `ORA_ZCQ_CONVERTER_FINEST_LOGGING` | `Y`, `N` |156157### Duplicate Resolution158159| Setting | Profile Option Code | Stored Values |160|---|---|---|161| Maximum Concurrent Resolution Request Jobs | `ORA_ZCH_MERGE_MAX_REQUEST_LIMIT` | Positive integer or blank; documented default `10` |162| Merge Mode | `ORA_ZCH_OPTIMIZE_LOAD` | `Y` optimized, `N` standard |163| Resolution Request Job Size | `ORA_ZCH_MERGE_REQUEST_BATCH_SIZE_LIMIT` | Positive integer or blank; documented default `100` |164| Merge Scope | `ORA_ZCH_MERGE_SCOPE` | `ALL`, `CDM`, `CRM`, `CDM_HV` |165| Merge Request Notifications | `ZCH_REQUEST_NOTIFICATIONS` | `ORA_ZCH_NOTIFICATION_DEF_YES`, `ORA_ZCH_NOTIFICATION_DEF_NO`, `ORA_ZCH_NOTIFICATION_DISABLED` |166| Automerge Threshold | `ZCH_AUTO_MERGE_THRESHOLD` | Integer `0` through `101`; `101` disables automerge |167| Customer Center Merge Requests | `ZCA_MERGE_REQUEST` | `Y`, `N` |168| Default Resolution Type | `ZCH_DEDUP_REQUEST_TYPE_OPTION` | `MERGE`, `CHOICE`, `LINK`, `LINK_DUP` |169| Data Steward Resolution Request Handling | `ORA_ZCH_DS_MERGE_REQUESTS` | `ZCH_PROCESS_WITHOUT_APPROVAL`, `ZCH_SUBMIT_FOR_APPROVAL` |170| User Resolution Request Handling | `ZCH_USER_MERGE_REQUESTS` | `ZCH_PROCESS_WITHOUT_APPROVAL`, `ZCH_SUBMIT_FOR_APPROVAL` |171| Agreement Rules Type | `ZCH_AGREEMENT_TYPE` | `ORA_ZCH_DEFAULT`, `ORA_ZCH_GROOVY`, `ORA_ZCH_RULE` |172| Attribute Selection Type | `ZCH_SETATTRIBUTE_TYPE` | `ORA_ZCH_NONE`, `ORA_ZCH_SC_OLDEST`, `ORA_ZCH_SC_NEWEST`, `ORA_ZCH_RULE` |173| Enable Attribute Source Tracking | `ZCH_ENABLE_SURVIVORSHIP` | `Y`, `N`; once enabled, do not disable |174| Master Record Selection | `ORA_ZCH_SETMASTER_TYPE` | `RULE`, `OLDEST`, `NEWEST`, `ANY`, `ORA_ZCH_GROOVY` |175| Merge Identical Child Records | `ORA_ZCH_MERGE_IDENTICAL` | `Y`, `N` |176| Add Groovy to Attribute Selection | `ZCH_GROOVY_RULE` | `Y`, `N` |177| Main Record Selection for Link | `ORA_ZCH_LINK_SETMAIN_TYPE` | `ANY`, `NEWEST`, `OLDEST`, `ORA_ZCH_GROOVY`, `ORA_ZCH_QUALITY_SCORE` |178| Autolink Threshold | `ZCH_AUTO_LINK_THRESHOLD` | Integer `0` through `101`; `101` disables autolink |179180The exact UI meaning for each lookup code is resolved through the lookup type named by the live profile definition. Do not replace a stored code with its display label.181182## FSM CSV Change Workflow1831841. Export exact TaskCode `ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS` and retain the original ZIP and SHA-256.1852. Require exactly one safe `ASM_SETUP_CSV_METADATA.xml` and the task identity in its metadata. For a profile-value edit, require `FND_APP_PROFILE_VALUE.csv`.1863. Match an existing row by profile code, application id, `LevelName=SITE`, and `LevelValue=SITE`. Modify only `ProfileOptionValue` in a copied package.1874. Never add an absent row. Report `export_content_discrepancy` and use `update_one` only after the live definition confirms SITE is enabled and updatable.1885. Validate every requested value against this inventory and, for lookup-backed values, against the current active lookup codes.1896. Show target environment, task, option code, UI meaning, current stored value, proposed stored value, ZIP path, and SHA-256. Any change invalidates approval.1907. Route the immutable reviewed ZIP to `core.data-loader`; do not duplicate its Task Hook, adapter, approval, submission, polling, or retry logic.1918. After import, re-export or read every affected configured SITE value and run the task's `Validate Setup` process. Never report success from submission alone.192193For `update_one`, perform the same membership, level, value, dependency, preview, approval, and verification gates, then let `core.fusion-api.apps-common` own the profile-value child-resource operation. Do not retry a POST or PATCH automatically.194195## Design Constraints196197- Source-confidence attribute selection requires `ZCH_ENABLE_SURVIVORSHIP=Y`.198- Once attribute source tracking is enabled, block a request to set it to `N`.199- `CDM_HV` merge scope is incompatible with business-rule or Groovy-based master, attribute, or agreement selection.200- `ZCH_GROOVY_RULE=Y` is incompatible with `ZCH_SETATTRIBUTE_TYPE=ORA_ZCH_RULE`.201- Autolink threshold applies to link resolution; automerge threshold applies to merge resolution.202- Blank handling is supported only for options whose Oracle contract explicitly permits no value. Do not translate blank, null, and an empty quoted CSV field interchangeably without target evidence.203204## Sources and Runtime Evidence205206Use current Oracle Customer Data Management documentation for setting purpose, UI grouping, defaults, and dependency rules. Treat the target profile definition, profile levels, active lookup codes, and fresh task export as runtime authority for stored codes, eligibility, current values, and package shape. A mismatch is a blocker, not permission to broaden the inventory.207208Oracle documentation:209210- [Getting Started with Your Customer Data Management Implementation](https://docs.oracle.com/en/cloud/saas/customer-data-management/fagcd/getting-started-with-your-customer-data-management-cdm-implementation.pdf)211- [Manage Customer Data Management Options](https://docs.oracle.com/en/cloud/saas/customer-data-management/faicd/Chunk106261974.html)212- [Implementing Applications](https://docs.oracle.com/en/cloud/saas/applications-common/26b/facia/implementing-applications.pdf)213214## Golden Scenarios2152161. **Existing exported row:** Export the exact task, change `ORA_ZCH_MERGE_SCOPE` from one active stored lookup code to another in its existing SITE row, produce a ZIP/hash-bound preview, and import only through Core Data Loader after its approval gate.2172. **Profile omitted from export:** When `ORA_ZCQ_MAX_CANDIDATES` is absent from `FND_APP_PROFILE_VALUE.csv`, report `export_content_discrepancy`; verify its live SITE definition and use `update_one` only after an exact direct-update preview and approval.2183. **Display label supplied:** If a user supplies `All functional areas` instead of stored code `ALL`, resolve and display the mapping but require the exact code in the reviewed change. Never write the UI label to CSV or the profile-value REST resource.2194. **Unsafe dependency:** Block `ZCH_ENABLE_SURVIVORSHIP=N` after source tracking has been enabled, and block a `CDM_HV` merge scope combined with incompatible business-rule or Groovy selections.220221## Setup Task Metadata222223- Task name: `Manage Customer Data Management Options`224- Task code: `ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS`225- Available: `Y`226- Export/import supported: `Y`227- CSV export/import supported: `Y`228- CSV export/import routing: `supported`229- Data Loader import mode: `FSM`230- Business Object: ``231232## CSV Export, Import, and Validation Workflow233234`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:2352361. Export setup task data with `shared.setup-export.task-level-export`.2372. Validate setup task data with `shared.validation.setup-data-validator`.2383. Validate reference data with `shared.validation.reference-data-validator`.2394. Import setup task data with `core.data-loader`.240241Use this task metadata when invoking those skills:242243- Offering: `Customer Data Management`244- Functional area / Setup Object: `Customer Hub`245- Setup task name: `Manage Customer Data Management Options`246- Setup task code: `ORA_ZCH_MANAGE_CUSTOMER_DATA_MANAGEMENT_OPTIONS`247248For import, provide the exact immutable ZIP and target environment to Core Data Loader. Do not rewrite `ASM_SETUP_CSV_METADATA.xml` or construct a replacement package from loose CSV files.249250## Preflight and Error Handling251252Load the task-local `ora-resource` files before preview or execution. Confirm the fixed task identity, environment, requested operation, closed inventory membership, SITE eligibility, current value, allowed stored value, dependencies, immutable artifact, and required approval. Classify and persist failures using the task-local error contract. Redact credentials, tokens, client secrets, token-cache contents, Authorization headers, full base64 packages, and sensitive values.253254255256257## Inputs258259- `operation`260- `implementation_objective`261- `project_context`262- `fusion_environment_context`263- `setup_task_scope`264- `setup_data_artifacts`265- `requested_option_changes`266- `execution_approval`267268## Outputs269270- `setup_task_plan`271- `setup_data_routing`272- `validation_checkpoints`273- `fsm_export_package`274- `profile_option_change_preview`275- `profile_option_change_result`276- `execution_result`277- `diagnostics`278- `audit_summary`279- `skill_run_record`280- `token_usage_record`281282## Implementation Notes283284Use 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.