Manage Oracle Data as a Service Attribute Mapping and Preferences
Purpose
Change only explicitly requested existing rows for task
ORA_ZCM_DAAS_ATTRIBUTE_MAPPING_PREFERENCES. A normal FSM export can omit
unchanged seeded rows, so this skill uses the sanitized complete seeded-row
catalog in assets/seeded-attribute-mappings.csv as a fallback row source.
Supported Operations
- Export the current task package from one selected Fusion environment.
- Prepare one or more selected existing rows for import.
- Validate and preview the exact selected-row ZIP.
- Import the approved ZIP through
core.data-loader in FSM mode.
- Resume status polling for an already captured process identifier.
- Re-export and verify the requested fields after import.
Do not create rows, delete rows, reset the complete task, or import the complete
seeded catalog.
Selected-Row Contract
- Identify a row with the exact composite key
AttributeCategory plus
DaasAttributeName. Require exactly one match in the complete seeded catalog.
- Accept changes only for
AutofillBlank, AutoupdateNonBlank,
FusionObjectName, and FusionAttributeName. The two preference flags accept
only Y or N. When either mapping field changes, require fresh target-pod
object metadata and validate the effective FusionObjectName and nonblank
FusionAttributeName by exact case-sensitive AttributeCode match.
- Export the current task before package preparation. For each selected row and
CSV member, preserve the current exported row when present; otherwise copy
the row from the complete seeded catalog. Apply only the requested fields.
- Write only selected rows to both Oracle members:
ORA_ZCM_DATA_CLOUD_ENRICH_PREFERENCE.csv and
ORA_ZCM_DATA_CLOUD_MAPPING_PREFERENCE.csv. Preserve the fresh export's
member names, per-member header order, metadata, and ZIP structure.
- Reject a request when the two member schemas differ from the catalog, a key
is missing or duplicated, a requested field is outside the allowlist, live
attribute metadata is missing or incomplete, or an effective object/attribute
pair is invalid.
The import changes only rows present in the prepared CSV members. Do not add
unrequested rows as a precaution and do not infer deletion from omitted rows.
Friendly Preference Questions
Ask about preferences using the labels shown in Manage Enrichment Preferences
and Attribute Mapping for Oracle Data as a Service. Do not lead with CSV
column names or Y/N unless the user asks for the technical representation.
| UI label to use with the user |
How to ask |
FSM field/value |
| Don't Apply Blank Values |
“Should Don't Apply Blank Values be on or off for this attribute?” |
AutofillBlank: on = Y; off = N |
| Don't Overwrite |
“Should Don't Overwrite be on or off for this attribute?” |
AutoupdateNonBlank: on = N; off = Y |
For example, normalize “leave existing values unchanged” to Don't Overwrite:
on (AutoupdateNonBlank=N), and normalize “allow enrichment to overwrite
existing values” to Don't Overwrite: off (AutoupdateNonBlank=Y). Repeat
the readable label and its on/off value in the selected-row and approval
previews; include the technical field/value only as supporting detail.
Display During Real-time Enrichment is a distinct UI checkbox. It is not
one of the four editable fields in this selected-row FSM package. When a user
asks to change it, clearly explain that this package cannot perform that change,
do not translate it to either preference flag, and keep it out of the import
change document. Offer the task's UI/manual configuration route as the separate
next action.
Workflow
Resolve or create the implementation project through the implementation
router and select the exact source/target environment.
Route a fresh unfiltered task export through
shared.setup-export.task-level-export using task code
ORA_ZCM_DAAS_ATTRIBUTE_MAPPING_PREFERENCES. Persist its ProcessId, status,
ZIP, and SHA-256.
Normalize the user's requested rows into a JSON change document:
{
"changes": [
{
"AttributeCategory": "ACCOUNT_CONFIG_B",
"DaasAttributeName": "Account/Industry",
"set": {"AutofillBlank": "N"}
}
]
}
When a change includes FusionObjectName or FusionAttributeName, resolve
the effective object name from the fresh-export row or seeded fallback plus
the requested changes. For every distinct nonblank effective object, route a
read-only GET through core.fusion-api.rest-api-client:
/crmRestApi/resources/11.13.18.05/objectMetadata/{FusionObjectName}/child/attributes
Request fields=AttributeCode, limit=1000, offset=0, onlyData=true,
and totalResults=true. Require hasMore=false and
count=totalResults=items.length; otherwise stop instead of validating a
partial catalog. Keep raw responses in a temporary local location and retain
only their hashes, counts, requested-pair results, and sanitized target
identity in the project preview.
Build the selected-row package locally. Supply one fresh response for every
effective object used by a mapping change:
python3 pillars/cx/sales/accounts-and-contacts/manage-oracle-data-as-a-service-attribute-mapping-and-preferences/scripts/prepare_daas_attribute_mapping_import.py \
--export-zip "{fresh_export_zip}" \
--changes "{changes_json}" \
--fusion-attributes "Account={temporary_account_attributes_json}" \
--target-environment "{sanitized_target_environment}" \
--output-zip "{prepared_import_zip}" \
--preview "{selected_row_preview_json}"
Omit the two metadata arguments only when no requested change includes either
mapping field. An empty FusionAttributeName is an explicit unmapping and is
allowed; a nonblank attribute requires a nonblank, metadata-resolved object.
Validate that the preview lists only the requested keys, the correct before
and after values, exact object/attribute validation evidence when applicable,
the two CSV members, and the final ZIP SHA-256.
Route the immutable ZIP to core.data-loader with
dataloader_import_mode=FSM, the exact task context, target environment,
validation evidence, and archive SHA-256. Data Loader owns the import
approval preview and the single approval gate.
After approval, submit once, capture the returned process identifier, and
poll only that process. Do not replay an uncertain or timed-out import.
Re-export the task and compare the requested fields for each selected key.
Persist a verification result without importing again.
Project Artifacts
Keep the source export, normalized changes, selected-row preview, prepared ZIP,
SHA-256, Data Loader approval envelope, import status/log, verification result,
skill-run record, and token-usage record under project/{project_id}. Never
persist credentials, token caches, authorization headers, or the raw attached
source archive's environment-specific metadata.
Failure and Retry Boundary
Use the task-local ora-resource rules for validation, dependency readiness,
design enforcement, approval, and errors. Refresh a cache-managed token once
only when the routed workflow permits it. Never retry an export or import POST
automatically. On timeout, report the same task code, process identifier, last
status, elapsed time, diagnostic path, and status-only continuation.
Preflight and Redaction
Before any external operation, preflight the operation, exact environment,
privileges, task/catalog flags, source paths, fresh-export ZIP, metadata task
binding, CSV schemas, selected row keys, requested fields, complete live
attribute metadata for mapping changes, destination paths, validation evidence,
and approval requirements. Stop before side effects when any check is missing,
ambiguous, unsupported, or unsafe.
Redact credentials, tokens, authorization headers, opaque protected URLs,
customer data, raw Base64 file content, and environment-specific source
metadata from console output, previews, diagnostics, and durable artifacts.
Persist only the sanitized identifiers and evidence required to resume or audit
the declared workflow.
Sources
1---2skill_id: "cx.sales.accounts-and-contacts.manage-oracle-data-as-a-service-attribute-mapping-and-preferences"3name: manage-oracle-data-as-a-service-attribute-mapping-and-prefer4description: "Exports, prepares, validates, and imports selected Oracle Data as a Service attribute-mapping or enrichment-preference rows through the task-level FSM CSV workflow. Use when users need to change existing seeded rows for ORA_ZCM_DAAS_ATTRIBUTE_MAPPING_PREFERENCES; refuse new rows, deletions, whole-baseline imports, and execution outside the approved FSM route."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Accounts and Contacts"9functional_area_code: "ORA_SVC_ACCOUNTS_AND_CONTACTS"10task_code: "ORA_ZCM_DAAS_ATTRIBUTE_MAPPING_PREFERENCES"11task_name: "Manage Oracle Data as a Service Attribute Mapping and Preferences"12parent_skill_id: "cx.sales.accounts-and-contacts"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: "import"20execution_mode: "hybrid"21owner_team: "CX sales pillar team"22version: "0.3.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "fusion_environment_context"27 - "operation"28 - "row_changes"29 - "fresh_setup_task_export"30 - "fresh_target_attribute_metadata"31outputs:32 - "setup_task_export_result"33 - "selected_row_change_preview"34 - "fusion_attribute_validation_result"35 - "prepared_setup_data_zip"36 - "setup_data_validation_result"37 - "data_loader_approval_preview"38 - "setup_data_import_result"39 - "post_import_verification_result"40 - "skill_run_record"41 - "token_usage_record"42depends_on:43 - "shared.setup-export.task-level-export"44 - "shared.validation.setup-data-validator"45 - "core.fusion-api.rest-api-client"46 - "core.data-loader"47uses_core:48 - "core.fusion-api.rest-api-client"49 - "core.data-loader"50 - "core.project-mgmt.artifact-version-manager"51 - "core.project-mgmt.artifact-registry-manager"52 - "core.project-mgmt.project-state-manager"53persists_project_state: true54token_usage_tracking:55 enabled: true56 granularity: "per_skill_run"57 artifact_type: "token_usage_record"58 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"59 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"60 required_fields:61 - "activity_start_time"62 - "skill_id"63 - "task"64 - "trigger"65 - "artifacts_written"66 - "files_read"67 - "estimated_input_tokens"68 - "estimated_output_tokens"69 - "estimated_total_tokens"70 - "estimation_method"71 - "notes"72state_updates:73 - "setup_task_sequence"74 - "configuration_blueprints"75 - "validation_results"76 - "reports"77 - "token_usage_records"78workspace_outputs:79 - artifact_type: "other"80 default_location: "project/{project_id}/exports/sales/accounts-and-contacts/manage-oracle-data-as-a-service-attribute-mapping-and-preferences/"81 versioning_policy: "append-only"82 - artifact_type: "validation_result"83 default_location: "project/{project_id}/artifacts/pillars/cx/sales/accounts-and-contacts/manage-oracle-data-as-a-service-attribute-mapping-and-preferences/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 a task-level FSM export process when approved and writes export artifacts to the project workspace."100 - "Reads target-environment Fusion object metadata when a requested change includes FusionObjectName or FusionAttributeName."101 - "Writes a selected-row FSM import ZIP and immutable preview to the project workspace."102 - "Submits one approved task-level FSM import through core.data-loader and polls the returned process identifier."103required_privileges:104 - "Fusion privileges appropriate to export and import setup task CSV data"105 - "Fusion privileges to read Sales object metadata"106metadata:107 source: https://skillmd.com/skills/oracle/manage-oracle-data-as-a-service-attribute-mapping-and-prefer108---109110# Manage Oracle Data as a Service Attribute Mapping and Preferences111112## Purpose113114Change only explicitly requested existing rows for task115`ORA_ZCM_DAAS_ATTRIBUTE_MAPPING_PREFERENCES`. A normal FSM export can omit116unchanged seeded rows, so this skill uses the sanitized complete seeded-row117catalog in `assets/seeded-attribute-mappings.csv` as a fallback row source.118119## Supported Operations120121- Export the current task package from one selected Fusion environment.122- Prepare one or more selected existing rows for import.123- Validate and preview the exact selected-row ZIP.124- Import the approved ZIP through `core.data-loader` in FSM mode.125- Resume status polling for an already captured process identifier.126- Re-export and verify the requested fields after import.127128Do not create rows, delete rows, reset the complete task, or import the complete129seeded catalog.130131## Selected-Row Contract1321331. Identify a row with the exact composite key `AttributeCategory` plus134 `DaasAttributeName`. Require exactly one match in the complete seeded catalog.1352. Accept changes only for `AutofillBlank`, `AutoupdateNonBlank`,136 `FusionObjectName`, and `FusionAttributeName`. The two preference flags accept137 only `Y` or `N`. When either mapping field changes, require fresh target-pod138 object metadata and validate the effective `FusionObjectName` and nonblank139 `FusionAttributeName` by exact case-sensitive `AttributeCode` match.1403. Export the current task before package preparation. For each selected row and141 CSV member, preserve the current exported row when present; otherwise copy142 the row from the complete seeded catalog. Apply only the requested fields.1434. Write only selected rows to both Oracle members:144 `ORA_ZCM_DATA_CLOUD_ENRICH_PREFERENCE.csv` and145 `ORA_ZCM_DATA_CLOUD_MAPPING_PREFERENCE.csv`. Preserve the fresh export's146 member names, per-member header order, metadata, and ZIP structure.1475. Reject a request when the two member schemas differ from the catalog, a key148 is missing or duplicated, a requested field is outside the allowlist, live149 attribute metadata is missing or incomplete, or an effective object/attribute150 pair is invalid.151152The import changes only rows present in the prepared CSV members. Do not add153unrequested rows as a precaution and do not infer deletion from omitted rows.154155## Friendly Preference Questions156157Ask about preferences using the labels shown in **Manage Enrichment Preferences158and Attribute Mapping for Oracle Data as a Service**. Do not lead with CSV159column names or `Y`/`N` unless the user asks for the technical representation.160161| UI label to use with the user | How to ask | FSM field/value |162|---|---|---|163| **Don't Apply Blank Values** | “Should **Don't Apply Blank Values** be on or off for this attribute?” | `AutofillBlank`: on = `Y`; off = `N` |164| **Don't Overwrite** | “Should **Don't Overwrite** be on or off for this attribute?” | `AutoupdateNonBlank`: on = `N`; off = `Y` |165166For example, normalize “leave existing values unchanged” to **Don't Overwrite:167on** (`AutoupdateNonBlank=N`), and normalize “allow enrichment to overwrite168existing values” to **Don't Overwrite: off** (`AutoupdateNonBlank=Y`). Repeat169the readable label and its on/off value in the selected-row and approval170previews; include the technical field/value only as supporting detail.171172**Display During Real-time Enrichment** is a distinct UI checkbox. It is not173one of the four editable fields in this selected-row FSM package. When a user174asks to change it, clearly explain that this package cannot perform that change,175do not translate it to either preference flag, and keep it out of the import176change document. Offer the task's UI/manual configuration route as the separate177next action.178179## Workflow1801811. Resolve or create the implementation project through the implementation182 router and select the exact source/target environment.1832. Route a fresh unfiltered task export through184 `shared.setup-export.task-level-export` using task code185 `ORA_ZCM_DAAS_ATTRIBUTE_MAPPING_PREFERENCES`. Persist its `ProcessId`, status,186 ZIP, and SHA-256.1873. Normalize the user's requested rows into a JSON change document:188189 ```json190 {191 "changes": [192 {193 "AttributeCategory": "ACCOUNT_CONFIG_B",194 "DaasAttributeName": "Account/Industry",195 "set": {"AutofillBlank": "N"}196 }197 ]198 }199 ```2002014. When a change includes `FusionObjectName` or `FusionAttributeName`, resolve202 the effective object name from the fresh-export row or seeded fallback plus203 the requested changes. For every distinct nonblank effective object, route a204 read-only GET through `core.fusion-api.rest-api-client`:205206 ```text207 /crmRestApi/resources/11.13.18.05/objectMetadata/{FusionObjectName}/child/attributes208 ```209210 Request `fields=AttributeCode`, `limit=1000`, `offset=0`, `onlyData=true`,211 and `totalResults=true`. Require `hasMore=false` and212 `count=totalResults=items.length`; otherwise stop instead of validating a213 partial catalog. Keep raw responses in a temporary local location and retain214 only their hashes, counts, requested-pair results, and sanitized target215 identity in the project preview.2165. Build the selected-row package locally. Supply one fresh response for every217 effective object used by a mapping change:218219 ```bash220 python3 pillars/cx/sales/accounts-and-contacts/manage-oracle-data-as-a-service-attribute-mapping-and-preferences/scripts/prepare_daas_attribute_mapping_import.py \221 --export-zip "{fresh_export_zip}" \222 --changes "{changes_json}" \223 --fusion-attributes "Account={temporary_account_attributes_json}" \224 --target-environment "{sanitized_target_environment}" \225 --output-zip "{prepared_import_zip}" \226 --preview "{selected_row_preview_json}"227 ```228229 Omit the two metadata arguments only when no requested change includes either230 mapping field. An empty `FusionAttributeName` is an explicit unmapping and is231 allowed; a nonblank attribute requires a nonblank, metadata-resolved object.2326. Validate that the preview lists only the requested keys, the correct before233 and after values, exact object/attribute validation evidence when applicable,234 the two CSV members, and the final ZIP SHA-256.2357. Route the immutable ZIP to `core.data-loader` with236 `dataloader_import_mode=FSM`, the exact task context, target environment,237 validation evidence, and archive SHA-256. Data Loader owns the import238 approval preview and the single approval gate.2398. After approval, submit once, capture the returned process identifier, and240 poll only that process. Do not replay an uncertain or timed-out import.2419. Re-export the task and compare the requested fields for each selected key.242 Persist a verification result without importing again.243244## Project Artifacts245246Keep the source export, normalized changes, selected-row preview, prepared ZIP,247SHA-256, Data Loader approval envelope, import status/log, verification result,248skill-run record, and token-usage record under `project/{project_id}`. Never249persist credentials, token caches, authorization headers, or the raw attached250source archive's environment-specific metadata.251252## Failure and Retry Boundary253254Use the task-local `ora-resource` rules for validation, dependency readiness,255design enforcement, approval, and errors. Refresh a cache-managed token once256only when the routed workflow permits it. Never retry an export or import POST257automatically. On timeout, report the same task code, process identifier, last258status, elapsed time, diagnostic path, and status-only continuation.259260## Preflight and Redaction261262Before any external operation, preflight the operation, exact environment,263privileges, task/catalog flags, source paths, fresh-export ZIP, metadata task264binding, CSV schemas, selected row keys, requested fields, complete live265attribute metadata for mapping changes, destination paths, validation evidence,266and approval requirements. Stop before side effects when any check is missing,267ambiguous, unsupported, or unsafe.268269Redact credentials, tokens, authorization headers, opaque protected URLs,270customer data, raw Base64 file content, and environment-specific source271metadata from console output, previews, diagnostics, and durable artifacts.272Persist only the sanitized identifiers and evidence required to resume or audit273the declared workflow.274275## Sources276277- `assets/seeded-attribute-mappings.json`278- `knowledge/setup-task-catalog/effective/setupTasksAll.json`279- `shared/setup-export/task-level-export/SKILL.md`280- `core/fusion-api/rest-api-client/SKILL.md`281- `core/data-loader/SKILL.md`282- https://docs.oracle.com/en/cloud/saas/applications-common/26c/farca/api-setup-task-csv-exports.html283- https://docs.oracle.com/en/cloud/saas/applications-common/26c/farca/api-setup-task-csv-imports.html284- https://docs.oracle.com/en/cloud/saas/sales/fadsi/add-fields-to-the-mapping.html285- https://docs.oracle.com/en/cloud/saas/customer-data-management/fagcd/configure-enrichment-preferences.html286- https://docs.oracle.com/en/cloud/saas/sales/faaps/api-object-metadata-attributes.html