Manage Hierarchies
Purpose
Read accessible hierarchies and import user-supplied hierarchy header or member
CSV files through the shared Trading Community CX Import workflow. This skill
binds the hierarchy object, mode, and activity order, then delegates source
processing to Import Trading Community Data, core.data-loader, and their
declared dependencies. Those workflows may read, inspect, decode, parse,
classify, validate, hash, package, and otherwise process the supplied CSVs as
required by their existing contracts.
Setup Task Contract
- Task:
Manage Hierarchies (HZ_MANAGE_HIERARCHIES)
- Read route:
core.fusion-api.rest-api-client, GET only
- Import route:
cx.customer-data-management.trading-community-foundation.import-trading-community-data
- Import executor:
core.fusion-api.cx-import-export-management, governed by core.data-loader
- FSM export/import: not supported
- FSM CSV export/import: not supported
- CX Import objects:
Hierarchy and HierarchyNode
The catalog's FSM flags remain N/N; they do not prohibit this separate CX
Import Management route. Never substitute FSM import or generic Data Loader
initiateDataLoad for the declared CX Import adapter.
Operation Routing
| User intent |
Supplied file role |
Exact object code |
Exact ImportMode |
| Create hierarchy |
Hierarchy CSV |
Hierarchy |
CREATE_ONLY |
| Import, create or update hierarchy |
Hierarchy CSV |
Hierarchy |
CREATE_RECORD |
| Delete hierarchy |
Hierarchy CSV |
Hierarchy |
DELETE_RECORD |
| Create hierarchy members |
HierarchyNode CSV |
HierarchyNode |
CREATE_ONLY |
| Import, create, update, move, or reparent hierarchy members |
HierarchyNode CSV |
HierarchyNode |
CREATE_RECORD |
| Delete hierarchy members |
HierarchyNode CSV |
HierarchyNode |
DELETE_RECORD |
When the user says only import, default to CREATE_RECORD so Fusion may
create new records and update matching records. Preserve an explicit
create-only choice as CREATE_ONLY. Route an explicit literal delete as
DELETE_RECORD. For an unchanged user-supplied CSV, do not inspect or resolve
row identities before submission. Bind the destructive effect to Core Data
Loader's immutable preview and approval, then let Fusion Import Management
accept or reject the rows. Exact member-edge validation remains available only
when the user explicitly requests data validation or supplies identities
separately for record-level verification.
When both files are supplied, execute two independent activities. For create or
update, use dependency order: Hierarchy first, then HierarchyNode. For
delete, remove HierarchyNode members first, then the Hierarchy header. Each
activity has its own exact object, mode, immutable group digest, UCM checkpoint,
Data Loader authorization, and result. When exactly two unlabeled CSV paths are
supplied in one request, map the first path to Hierarchy and the second path
to HierarchyNode, then apply the operation-specific execution order. Present
that deterministic mapping and execution order in the immutable preview. Do
not combine the two files into one activity or infer roles from their
filenames. The declared shared and Core Data Loader workflows may inspect
either file as required by their contracts.
Supplied CSV Contract
For a user-supplied hierarchy file:
- preserve the supplied source path and basename when handing it to the shared
importer;
- allow
Import Trading Community Data, core.data-loader, and every declared
dependency they select to read, inspect, decode, parse, classify, validate,
hash, package, or otherwise process its headers, rows, and bytes as required;
- do not stop, request a waiver, or report a contract conflict merely because a
declared dependency inspects, parses, or validates the CSV;
- do not add independent Manage Hierarchies business-data checks or task-local
blocking validations beyond the selected shared and Core Data Loader
contracts;
- invoke an optional generation or preparation helper such as
prepare_tca_import_csv.py only when the selected shared workflow requires it
or the user explicitly requests CSV generation or preparation.
The shared route remains authoritative for source review, file eligibility,
mapping detection, live object metadata, UCM account resolution, immutable
preview and digest generation, approval, upload, and activity creation. Normal
shared/Core Data Loader validation may reject an unusable source; this skill
must not preempt that workflow with a stricter hierarchy-specific rule. Fusion
Import Management remains authoritative for accepting or rejecting submitted
data.
Import Workflow
- Begin through the implementation router and select the implementation
project. Load this skill's ready task-node plan.
- Resolve exactly one configured Fusion environment and the supplied file role.
Prefer explicit roles; for exactly two unlabeled paths, use request order:
first
Hierarchy, second HierarchyNode. Apply the operation table, then
permit the declared dependencies to inspect the CSVs as required.
- For each activity, invoke
Import Trading Community Data with the exact
object code, exact mode, and the single unchanged CSV. Use fixed high-volume
routing for both hierarchy objects. For delete, pass DELETE_RECORD; do not
inspect supplied rows or require a pre-delete Trees lookup. Fusion Import
Management is authoritative for row acceptance or rejection.
- Let
core.data-loader produce the authoritative source review, UCM account,
ordered group digest, Task Hook preview, and approval request. Run the
task-local read-only bridge as
python3 scripts/hierarchy_cx_preflight.py <csv> --object-code <Hierarchy|HierarchyNode>
from this skill folder. It invokes Core Data Loader and extracts the
authoritative response.preflight.archiveSha256 from Core's structured
approval-stop result. Consume that JSON internally to build Task Hook; do
not stop because Core's user-facing Markdown omits the digest, and never
compute or reconstruct a replacement digest. Core's normal CSV inspection,
parsing, classification, validation, hashing, and packaging are explicitly
permitted and must not be treated as a Manage Hierarchies contract conflict.
- The Data Loader approval is authoritative for the matching unchanged CX
import. Do not add a second Manage Hierarchies approval prompt. Any change to
environment, bytes, basename, object, mode, activity name, UCM account, or
schedule invalidates that approval.
- After approval, follow the shared importer's checkpointed UCM upload and
mode-aware CX Import activity creation exactly once. Never retry an uncertain
upload or POST. Monitor and report Fusion's activity and data-file counts.
- If both files were supplied for create or update, begin the
HierarchyNode
preview only after the Hierarchy activity succeeds. For delete, begin the
Hierarchy header preview only after the HierarchyNode delete succeeds.
Let the declared shared/Core workflow perform any source inspection it
requires; Fusion remains authoritative for the import result.
- Report the terminal CX Import activity and data-file result as Fusion's
authoritative import outcome. If the user separately asks for hierarchy
generation or record-level absence verification, route the shared
hierarchy-post-process strategy. Party Hierarchy Generation is a separate
ESS mutation with its own resolved parameters, preview, and fresh approval;
an import approval never authorizes it. Without optional record-level
verification, report a successful delete activity as processed in
DELETE_RECORD mode, not as independently verified absent.
Preflight
For supplied-file import, this skill preflights routing inputs: one configured
environment, a usable path, its explicit role or deterministic two-file
request-order role, and the exact object and ImportMode. Delegate source
inspection and all further preflight to the selected shared/Core Data Loader
workflow, including file eligibility, mapping detection, metadata, UCM account,
digest, adapter readiness, and approval freshness. For an unchanged supplied
CSV, exact-object ImportSupport=Y plus mode-aware DELETE_RECORD adapter
readiness is the live capability gate; Fusion may still reject unsupported or
invalid delete rows. Use only the bridge-returned
archiveSha256 for the Task Hook preview. A missing digest in rendered
Data Loader Markdown is not a blocker when the structured bridge result is
preflight_ready; a missing or invalid digest in that structured result is a
real preflight-contract failure. CSV inspection, parsing, or validation by a
declared dependency is expected and must never be treated as a Manage
Hierarchies contract conflict.
Do not inspect a supplied HierarchyNode delete CSV to require PartyId,
PartyNumber, parent identity, AsOfDate, or any other row field. Fusion
evaluates those values after the approved unchanged file is submitted.
For reads, require the configured environment, supported operation, applicable
exact identifiers, ready task-node plan, and GET-only client route. Stop on an
unavailable declared route rather than substituting another endpoint.
Supported Read Operations
| Operation |
Required input |
Result |
describe |
Exactly one configured Fusion environment |
Live describe metadata for the read-only Trees resources |
list |
Optional exact Tree Structure Code and optional as-of date |
One row per hierarchy having exactly one active version effective on the as-of date with NodeCount greater than zero |
inventory |
Optional exact Tree Structure Code |
Raw header inventory: every accessible or exactly matching hierarchy after pagination completes, regardless of version status, effective dates, or node count |
hierarchy_detail |
Tree Structure Code and Tree Code |
One exact hierarchy and its returned canonical and child links |
versions |
Tree Structure Code and Tree Code |
Every version for the exact hierarchy after pagination completes |
nodes |
Tree Structure Code, Tree Code, and Tree Version ID |
Nodes returned for the exact version after pagination completes |
full_read |
Tree Structure Code and Tree Code; optional Tree Version ID |
Exact hierarchy, versions, selected-version nodes, labels, and data-source parameters |
Do not restrict reads to a client-side Tree Structure Code allowlist. Use live
describe metadata to select only readable projection fields; do not hardcode an
optional field such as TreeName, Description, or Status when describe does
not expose it. Query collections with exact filters and follow all pages. For
node reads, prefer the same-environment child link returned by Fusion. If that
link is absent, use the describe-confirmed fndTreeNodes collection only with
the exact current-run TreeStructureCode, TreeCode, and TreeVersionId;
never use an unscoped node query or another namespace.
Interpret an unqualified request to list, show, or list hierarchies as
read_operation=list. Default its as-of date to the current date in the
configured environment's execution context and disclose that date in the
result. This is a UI-aligned hierarchy-level list: its eligibility criteria
match hierarchies that can contribute rows to the UI's All Parties in
Hierarchies result. It returns one hierarchy row, not one party-membership row,
for each eligible hierarchy. Use nodes when the user asks for the detailed
membership rows. Run raw inventory only when the user explicitly requests all
headers, raw inventory, inactive/future/expired hierarchies, or empty
hierarchies.
Read Workflow
- Resolve one configured environment and load the task-node plan.
- Default an unqualified list intent to
list, resolve and disclose its
as-of date, and validate the read operation and required exact identifiers.
- Execute only the applicable GET resolvers from
ora-resource/ora_reference_lookups.md through the core REST client.
- Return environment, scope, match count, pagination completion, sanitized
hierarchy data, applied eligibility criteria and as-of date when listing,
and confirmation that no Fusion data changed.
Read-only operations do not require mutation approval.
Result and Failure Contract
For import, return the target, object, mode, filename, canonical digest, activity
ID and name, UCM document name, status, counts, diagnostics, and any separate
generation result. Never expose credentials, authorization headers, token-cache
contents, encoded source data, or source rows.
If Fusion rejects supplied data, including DELETE_RECORD for the exact target
object, report its diagnostics and stop. Do not repair, rewrite, validate, or
resubmit the file automatically. If an upload or import POST has an uncertain
outcome, reconcile the existing checkpoint or activity; never repeat the
mutation. A successful delete-mode activity proves that Fusion processed the
activity in DELETE_RECORD mode. It does not independently prove a particular
record is absent; perform optional record-level verification only when
separately requested and the necessary identities are supplied outside the
opaque CSV.
Redaction
Persist and display only sanitized routing, digest, external-ID, status, count,
and diagnostic evidence. Redact credentials, authorization headers, token-cache
contents, encoded documents, source rows, customer-sensitive values, opaque
canonical URLs, and raw Fusion payloads from output, diagnostics, run records,
and project artifacts.
Hard Boundaries
- Never add an independent Manage Hierarchies CSV validation gate that blocks a
source before the selected shared/Core Data Loader workflow evaluates it.
- Never block because
Import Trading Community Data, core.data-loader, or a
declared dependency reads, inspects, decodes, parses, classifies, validates,
hashes, packages, or otherwise processes a supplied CSV.
- Never derive approval from a source-file hash or an agent-computed CSV-group
hash. Use only
archiveSha256 extracted from Core Data Loader's structured
preflight response by the task-local bridge.
- Never import both object files in one activity.
- Never route delete through a mode other than
DELETE_RECORD or bypass Core
Data Loader's immutable preview, destructive disclosure, and approval.
- Never inspect an unchanged supplied Hierarchy Member CSV to enforce PartyId,
PartyNumber, parent, as-of-date, identifier-only, or pre-delete match rules.
Fusion Import Management owns row validation for this pass-through branch.
- Never invoke FSM import/export or generic Data Loader
initiateDataLoad.
- Never issue direct Trees REST
POST, PATCH, DELETE, or /action/ calls.
- Never duplicate Core Data Loader's approval for the same CX import activity.
- Never submit Party Hierarchy Generation without a separate fresh approval.
Sources
- Oracle Cloud Customer Data Management:
How You Manage Hierarchies,
Hierarchy Validation Rules, and How do I import hierarchy data?, used for
hierarchy scope and CX Import capability.
Import Trading Community Data, used as the repository execution contract for
unchanged supplied CSVs, object/mode routing, Data Loader authorization, UCM
staging, CX Import activity creation, monitoring, and hierarchy post-processing.
1---2skill_id: "cx.customer-data-management.trading-community-foundation.manage-hierarchies"3name: manage-hierarchies4description: "Lists UI-eligible hierarchies by default, reads hierarchy detail through Applcore Trees REST resources, and imports user-supplied Hierarchy or HierarchyNode CSV files through Oracle CX Import Management. Node reads use a returned child link or a describe-confirmed exact fndTreeNodes collection fallback; the default list retains hierarchies with an active, currently effective version containing at least one node."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Trading Community Foundation"9functional_area_code: "ORA_HZ_CDM_FOUNDATION"10task_code: "HZ_MANAGE_HIERARCHIES"11task_name: "Manage Hierarchies"12parent_skill_id: "cx.customer-data-management.trading-community-foundation"13available_flag: "Y"14export_import_supported_flag: "N"15csv_export_import_supported_flag: "N"16dataloader_import_mode: "CXIMPORT"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "import"20execution_mode: "hybrid"21owner_team: "CX customer data management pillar team"22version: "1.2.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "fusion_environment_context"27 - "operation"28 - "read_operation"29 - "tree_structure_code"30 - "tree_code"31 - "tree_version_id"32 - "as_of_date"33 - "hierarchy_csv"34 - "hierarchy_node_csv"35 - "ordered_hierarchy_csvs"36 - "import_operation"37 - "import_activity_name"38 - "execution_approval"39 - "party_hierarchy_generation_options"40 - "party_hierarchy_generation_approval"41outputs:42 - "ui_aligned_hierarchy_inventory"43 - "hierarchy_inventory"44 - "hierarchy_detail"45 - "hierarchy_version_summary"46 - "hierarchy_node_summary"47 - "immutable_import_preview"48 - "ucm_upload_checkpoint"49 - "cx_import_activity_result"50 - "import_status_and_diagnostics"51 - "party_hierarchy_generation_result"52 - "post_import_verification"53 - "skill_run_record"54 - "token_usage_record"55depends_on:56 - "cx.customer-data-management.trading-community-foundation"57 - "cx.customer-data-management.trading-community-foundation.import-trading-community-data"58 - "cx.customer-data-management.trading-community-foundation.run-trading-community-party-hierarchy-generation"59 - "core.data-loader"60uses_core:61 - "core.data-loader"62 - "core.auth.fusion-oauth-authentication"63 - "core.fusion-api.rest-api-client"64 - "core.fusion-api.ucm-rest-client"65 - "core.fusion-api.cx-import-export-management"66 - "core.fusion-api.ess-job-submitter"67 - "core.project-mgmt.artifact-version-manager"68 - "core.project-mgmt.artifact-registry-manager"69 - "core.project-mgmt.project-state-manager"70persists_project_state: true71token_usage_tracking:72 enabled: true73 granularity: "per_skill_run"74 artifact_type: "token_usage_record"75 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"76 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"77 required_fields:78 - "activity_start_time"79 - "skill_id"80 - "task"81 - "trigger"82 - "artifacts_written"83 - "files_read"84 - "estimated_input_tokens"85 - "estimated_output_tokens"86 - "estimated_total_tokens"87 - "estimation_method"88 - "notes"89state_updates:90 - "setup_task_sequence"91 - "configuration_blueprints"92 - "validation_results"93 - "reports"94 - "token_usage_records"95workspace_outputs:96 - artifact_type: "configuration_blueprint"97 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-hierarchies/current/"98 versioning_policy: "major-new-version-minor-confirm-update"99 - artifact_type: "validation_result"100 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-hierarchies/current/"101 versioning_policy: "major-new-version-minor-confirm-update"102 - artifact_type: "report"103 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-hierarchies/current/"104 versioning_policy: "major-new-version-minor-confirm-update"105 - artifact_type: "skill_run"106 default_location: "project/{project_id}/state/runs/"107 versioning_policy: "append-only"108 - artifact_type: "token_usage_record"109 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"110 versioning_policy: "append-only"111oracle_supplied_guidance_files:112 - purpose: "Read and supplied-file routing checks"113 location: "ora-resource/ora_input_validation.md"114 - purpose: "Read resolvers and hierarchy import object routing"115 location: "ora-resource/ora_reference_lookups.md"116 - purpose: "Safe create-or-update import default"117 location: "ora-resource/ora_defaulting_rules.md"118 - purpose: "Read and import failure handling"119 location: "ora-resource/ora_error_handling.md"120applicability:121 industries:122 - "All"123 countries:124 - "All"125 fusion_releases:126 - "Current Oracle Fusion Cloud release"127side_effects:128 - "Uploads each approved user-supplied hierarchy CSV unchanged through the shared Trading Community CX Import workflow."129 - "Creates and activates one approved create, update, or delete CX Import Management activity for each supplied hierarchy object."130 - "May submit Party Hierarchy Generation only as a separate, freshly approved post-import action."131required_privileges:132 - "Fusion privileges to view Trees Management resources and the selected hierarchy."133 - "Privileges to upload to the live metadata-resolved UCM document account."134 - "CX Import Management privileges for Hierarchy and HierarchyNode."135 - "ESS privilege for Party Hierarchy Generation when separately requested and approved."136metadata:137 source: https://skillmd.com/skills/oracle/manage-hierarchies138---139140# Manage Hierarchies141142## Purpose143144Read accessible hierarchies and import user-supplied hierarchy header or member145CSV files through the shared Trading Community CX Import workflow. This skill146binds the hierarchy object, mode, and activity order, then delegates source147processing to `Import Trading Community Data`, `core.data-loader`, and their148declared dependencies. Those workflows may read, inspect, decode, parse,149classify, validate, hash, package, and otherwise process the supplied CSVs as150required by their existing contracts.151152## Setup Task Contract153154- Task: `Manage Hierarchies` (`HZ_MANAGE_HIERARCHIES`)155- Read route: `core.fusion-api.rest-api-client`, GET only156- Import route: `cx.customer-data-management.trading-community-foundation.import-trading-community-data`157- Import executor: `core.fusion-api.cx-import-export-management`, governed by `core.data-loader`158- FSM export/import: not supported159- FSM CSV export/import: not supported160- CX Import objects: `Hierarchy` and `HierarchyNode`161162The catalog's FSM flags remain `N`/`N`; they do not prohibit this separate CX163Import Management route. Never substitute FSM import or generic Data Loader164`initiateDataLoad` for the declared CX Import adapter.165166## Operation Routing167168| User intent | Supplied file role | Exact object code | Exact ImportMode |169|---|---|---|---|170| Create hierarchy | Hierarchy CSV | Hierarchy | CREATE_ONLY |171| Import, create or update hierarchy | Hierarchy CSV | Hierarchy | CREATE_RECORD |172| Delete hierarchy | Hierarchy CSV | Hierarchy | DELETE_RECORD |173| Create hierarchy members | HierarchyNode CSV | HierarchyNode | CREATE_ONLY |174| Import, create, update, move, or reparent hierarchy members | HierarchyNode CSV | HierarchyNode | CREATE_RECORD |175| Delete hierarchy members | HierarchyNode CSV | HierarchyNode | DELETE_RECORD |176177When the user says only `import`, default to `CREATE_RECORD` so Fusion may178create new records and update matching records. Preserve an explicit179create-only choice as `CREATE_ONLY`. Route an explicit literal delete as180`DELETE_RECORD`. For an unchanged user-supplied CSV, do not inspect or resolve181row identities before submission. Bind the destructive effect to Core Data182Loader's immutable preview and approval, then let Fusion Import Management183accept or reject the rows. Exact member-edge validation remains available only184when the user explicitly requests data validation or supplies identities185separately for record-level verification.186187When both files are supplied, execute two independent activities. For create or188update, use dependency order: `Hierarchy` first, then `HierarchyNode`. For189delete, remove `HierarchyNode` members first, then the `Hierarchy` header. Each190activity has its own exact object, mode, immutable group digest, UCM checkpoint,191Data Loader authorization, and result. When exactly two unlabeled CSV paths are192supplied in one request, map the first path to `Hierarchy` and the second path193to `HierarchyNode`, then apply the operation-specific execution order. Present194that deterministic mapping and execution order in the immutable preview. Do195not combine the two files into one activity or infer roles from their196filenames. The declared shared and Core Data Loader workflows may inspect197either file as required by their contracts.198199## Supplied CSV Contract200201For a user-supplied hierarchy file:202203- preserve the supplied source path and basename when handing it to the shared204 importer;205- allow `Import Trading Community Data`, `core.data-loader`, and every declared206 dependency they select to read, inspect, decode, parse, classify, validate,207 hash, package, or otherwise process its headers, rows, and bytes as required;208- do not stop, request a waiver, or report a contract conflict merely because a209 declared dependency inspects, parses, or validates the CSV;210- do not add independent Manage Hierarchies business-data checks or task-local211 blocking validations beyond the selected shared and Core Data Loader212 contracts;213- invoke an optional generation or preparation helper such as214 `prepare_tca_import_csv.py` only when the selected shared workflow requires it215 or the user explicitly requests CSV generation or preparation.216217The shared route remains authoritative for source review, file eligibility,218mapping detection, live object metadata, UCM account resolution, immutable219preview and digest generation, approval, upload, and activity creation. Normal220shared/Core Data Loader validation may reject an unusable source; this skill221must not preempt that workflow with a stricter hierarchy-specific rule. Fusion222Import Management remains authoritative for accepting or rejecting submitted223data.224225## Import Workflow2262271. Begin through the implementation router and select the implementation228 project. Load this skill's ready task-node plan.2292. Resolve exactly one configured Fusion environment and the supplied file role.230 Prefer explicit roles; for exactly two unlabeled paths, use request order:231 first `Hierarchy`, second `HierarchyNode`. Apply the operation table, then232 permit the declared dependencies to inspect the CSVs as required.2333. For each activity, invoke `Import Trading Community Data` with the exact234 object code, exact mode, and the single unchanged CSV. Use fixed high-volume235 routing for both hierarchy objects. For delete, pass `DELETE_RECORD`; do not236 inspect supplied rows or require a pre-delete Trees lookup. Fusion Import237 Management is authoritative for row acceptance or rejection.2384. Let `core.data-loader` produce the authoritative source review, UCM account,239 ordered group digest, Task Hook preview, and approval request. Run the240 task-local read-only bridge as241 `python3 scripts/hierarchy_cx_preflight.py <csv> --object-code <Hierarchy|HierarchyNode>`242 from this skill folder. It invokes Core Data Loader and extracts the243 authoritative `response.preflight.archiveSha256` from Core's structured244 approval-stop result. Consume that JSON internally to build Task Hook; do245 not stop because Core's user-facing Markdown omits the digest, and never246 compute or reconstruct a replacement digest. Core's normal CSV inspection,247 parsing, classification, validation, hashing, and packaging are explicitly248 permitted and must not be treated as a Manage Hierarchies contract conflict.2495. The Data Loader approval is authoritative for the matching unchanged CX250 import. Do not add a second Manage Hierarchies approval prompt. Any change to251 environment, bytes, basename, object, mode, activity name, UCM account, or252 schedule invalidates that approval.2536. After approval, follow the shared importer's checkpointed UCM upload and254 mode-aware CX Import activity creation exactly once. Never retry an uncertain255 upload or POST. Monitor and report Fusion's activity and data-file counts.2567. If both files were supplied for create or update, begin the `HierarchyNode`257 preview only after the `Hierarchy` activity succeeds. For delete, begin the258 `Hierarchy` header preview only after the `HierarchyNode` delete succeeds.259 Let the declared shared/Core workflow perform any source inspection it260 requires; Fusion remains authoritative for the import result.2618. Report the terminal CX Import activity and data-file result as Fusion's262 authoritative import outcome. If the user separately asks for hierarchy263 generation or record-level absence verification, route the shared264 `hierarchy-post-process` strategy. Party Hierarchy Generation is a separate265 ESS mutation with its own resolved parameters, preview, and fresh approval;266 an import approval never authorizes it. Without optional record-level267 verification, report a successful delete activity as processed in268 `DELETE_RECORD` mode, not as independently verified absent.269270## Preflight271272For supplied-file import, this skill preflights routing inputs: one configured273environment, a usable path, its explicit role or deterministic two-file274request-order role, and the exact object and ImportMode. Delegate source275inspection and all further preflight to the selected shared/Core Data Loader276workflow, including file eligibility, mapping detection, metadata, UCM account,277digest, adapter readiness, and approval freshness. For an unchanged supplied278CSV, exact-object `ImportSupport=Y` plus mode-aware `DELETE_RECORD` adapter279readiness is the live capability gate; Fusion may still reject unsupported or280invalid delete rows. Use only the bridge-returned281`archiveSha256` for the Task Hook preview. A missing digest in rendered282Data Loader Markdown is not a blocker when the structured bridge result is283`preflight_ready`; a missing or invalid digest in that structured result is a284real preflight-contract failure. CSV inspection, parsing, or validation by a285declared dependency is expected and must never be treated as a Manage286Hierarchies contract conflict.287288Do not inspect a supplied `HierarchyNode` delete CSV to require `PartyId`,289`PartyNumber`, parent identity, `AsOfDate`, or any other row field. Fusion290evaluates those values after the approved unchanged file is submitted.291292For reads, require the configured environment, supported operation, applicable293exact identifiers, ready task-node plan, and GET-only client route. Stop on an294unavailable declared route rather than substituting another endpoint.295296## Supported Read Operations297298| Operation | Required input | Result |299|---|---|---|300| `describe` | Exactly one configured Fusion environment | Live describe metadata for the read-only Trees resources |301| `list` | Optional exact Tree Structure Code and optional as-of date | One row per hierarchy having exactly one active version effective on the as-of date with NodeCount greater than zero |302| `inventory` | Optional exact Tree Structure Code | Raw header inventory: every accessible or exactly matching hierarchy after pagination completes, regardless of version status, effective dates, or node count |303| `hierarchy_detail` | Tree Structure Code and Tree Code | One exact hierarchy and its returned canonical and child links |304| `versions` | Tree Structure Code and Tree Code | Every version for the exact hierarchy after pagination completes |305| `nodes` | Tree Structure Code, Tree Code, and Tree Version ID | Nodes returned for the exact version after pagination completes |306| `full_read` | Tree Structure Code and Tree Code; optional Tree Version ID | Exact hierarchy, versions, selected-version nodes, labels, and data-source parameters |307308Do not restrict reads to a client-side Tree Structure Code allowlist. Use live309describe metadata to select only readable projection fields; do not hardcode an310optional field such as `TreeName`, `Description`, or `Status` when describe does311not expose it. Query collections with exact filters and follow all pages. For312node reads, prefer the same-environment child link returned by Fusion. If that313link is absent, use the describe-confirmed `fndTreeNodes` collection only with314the exact current-run `TreeStructureCode`, `TreeCode`, and `TreeVersionId`;315never use an unscoped node query or another namespace.316317Interpret an unqualified request to `list`, `show`, or `list hierarchies` as318`read_operation=list`. Default its as-of date to the current date in the319configured environment's execution context and disclose that date in the320result. This is a UI-aligned hierarchy-level list: its eligibility criteria321match hierarchies that can contribute rows to the UI's All Parties in322Hierarchies result. It returns one hierarchy row, not one party-membership row,323for each eligible hierarchy. Use `nodes` when the user asks for the detailed324membership rows. Run raw `inventory` only when the user explicitly requests all325headers, raw inventory, inactive/future/expired hierarchies, or empty326hierarchies.327328## Read Workflow3293301. Resolve one configured environment and load the task-node plan.3312. Default an unqualified list intent to `list`, resolve and disclose its332 as-of date, and validate the read operation and required exact identifiers.3333. Execute only the applicable GET resolvers from334 `ora-resource/ora_reference_lookups.md` through the core REST client.3354. Return environment, scope, match count, pagination completion, sanitized336 hierarchy data, applied eligibility criteria and as-of date when listing,337 and confirmation that no Fusion data changed.338339Read-only operations do not require mutation approval.340341## Result and Failure Contract342343For import, return the target, object, mode, filename, canonical digest, activity344ID and name, UCM document name, status, counts, diagnostics, and any separate345generation result. Never expose credentials, authorization headers, token-cache346contents, encoded source data, or source rows.347348If Fusion rejects supplied data, including `DELETE_RECORD` for the exact target349object, report its diagnostics and stop. Do not repair, rewrite, validate, or350resubmit the file automatically. If an upload or import POST has an uncertain351outcome, reconcile the existing checkpoint or activity; never repeat the352mutation. A successful delete-mode activity proves that Fusion processed the353activity in `DELETE_RECORD` mode. It does not independently prove a particular354record is absent; perform optional record-level verification only when355separately requested and the necessary identities are supplied outside the356opaque CSV.357358## Redaction359360Persist and display only sanitized routing, digest, external-ID, status, count,361and diagnostic evidence. Redact credentials, authorization headers, token-cache362contents, encoded documents, source rows, customer-sensitive values, opaque363canonical URLs, and raw Fusion payloads from output, diagnostics, run records,364and project artifacts.365366## Hard Boundaries367368- Never add an independent Manage Hierarchies CSV validation gate that blocks a369 source before the selected shared/Core Data Loader workflow evaluates it.370- Never block because `Import Trading Community Data`, `core.data-loader`, or a371 declared dependency reads, inspects, decodes, parses, classifies, validates,372 hashes, packages, or otherwise processes a supplied CSV.373- Never derive approval from a source-file hash or an agent-computed CSV-group374 hash. Use only `archiveSha256` extracted from Core Data Loader's structured375 preflight response by the task-local bridge.376- Never import both object files in one activity.377- Never route delete through a mode other than `DELETE_RECORD` or bypass Core378 Data Loader's immutable preview, destructive disclosure, and approval.379- Never inspect an unchanged supplied Hierarchy Member CSV to enforce PartyId,380 PartyNumber, parent, as-of-date, identifier-only, or pre-delete match rules.381 Fusion Import Management owns row validation for this pass-through branch.382- Never invoke FSM import/export or generic Data Loader `initiateDataLoad`.383- Never issue direct Trees REST `POST`, `PATCH`, `DELETE`, or `/action/` calls.384- Never duplicate Core Data Loader's approval for the same CX import activity.385- Never submit Party Hierarchy Generation without a separate fresh approval.386387## Sources388389- Oracle Cloud Customer Data Management: `How You Manage Hierarchies`,390 `Hierarchy Validation Rules`, and `How do I import hierarchy data?`, used for391 hierarchy scope and CX Import capability.392- `Import Trading Community Data`, used as the repository execution contract for393 unchanged supplied CSVs, object/mode routing, Data Loader authorization, UCM394 staging, CX Import activity creation, monitoring, and hierarchy post-processing.