Manage Organization Hierarchies and Classifications Setup Task Guidance
Purpose
Provide customer-FSCR-only assisted guidance to select the enterprise organization-hierarchy model, maintain the organization classifications used by Project Financial Management, and verify the resulting target state. A controlled FSM import is available only after the customer supplies or freshly exports the exact target-pod template and its import metadata.
REST Request Preflight
Before any workflow-selected REST request, apply the offering's
REST version and query compatibility preflight.
Determine the effective framework version from the selected core client or
workflow, construct compatible query parameters, and verify that the outgoing
header agrees. Do not hardcode a separate pillar version. Existing route,
validation, classification/matching, persistence and approval gates still apply.
Setup Task Skill Contract
- task_code:
PJF_MANAGE_ORGANIZATION_HIERARCHIES_AND_CLASSIFICATIONS
- task_name:
Manage Organization Hierarchies and Classifications
- parent_skill_id:
erp.project-financial-management.project-organizations
- pillar:
ERP
- offering:
Project Financial Management
- functional_area:
Project Organizations
- functional_area_code:
ORA_PJF_PROJ_ORG
- available_flag:
Y
- export_import_supported_flag:
Y
- csv_export_import_supported_flag:
Y
- dataloader_import_mode:
FSM
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, maintaining, importing, or validating setup data for Manage Organization Hierarchies and Classifications under Project Organizations.
Customer Inputs
- Target environment and an accountable owner for the enterprise hierarchy decision.
- Approved current and desired hierarchy type, selected organization classifications, business impact, deployment window, and rollback expectation.
- For a non-None hierarchy, the approved target-visible tree, active tree version, and starting organization.
- Current target-task state or a fresh current-data export for update reconciliation.
- For FSM import, the customer-provided or freshly exported target-pod template, metadata, package contract, and process-log access.
Supported Task Behavior
The task owns the Projects hierarchy type, selected organization classifications, and the default tree/version/starting-organization combination. Adding, moving, or removing organization-tree nodes is a manual PER_MANAGE_ORGANIZATION_TREE prerequisite boundary on this branch. Obtain a same-target handoff with tree structure, tree code, tree version, saved relationship/change evidence, and validation/activation state. Do not invoke an unavailable Workforce Structures skill or substitute an HDL import from this task.
Use a target-template-gated FSM import to set the hierarchy type only when the target does not already have one and to add validated classification values. Do not use the proven import contract to replace a different existing hierarchy type or remove classifications. Those operations remain unsupported for automated execution unless a fresh target contract directly proves them; do not redirect them to UI maintenance.
No direct customer REST write or internal application-module invocation is supported by this skill. Internal source behavior informs validation and sequencing only.
Assisted Workflow
- Confirm the exact target, owner, approved hierarchy outcome, selected classifications, impact, deployment window, and rollback expectation.
- Reconcile the current target-visible hierarchy type, classifications, and applicable default-tree selection. Treat supplied current-data reports as guidance, not as a universal required value set.
- Select the route by operation:
- Use template-gated FSM import only when the exact target-pod template and metadata prove the required package contract and the proposed change is supported by that contract.
- Return an operation-specific unsupported result for replacement or removal when the target contract does not prove it. Continue unrelated supported additive work.
- Return the manual
PER_MANAGE_ORGANIZATION_TREE prerequisite handoff for node placement and stop affected work until its saved same-target evidence is supplied. This handoff is outside this task's execution and does not approve the subsequent ESS sequence.
- Validate that at least one approved classification remains selected. For a non-None hierarchy, resolve one valid tree, active version, and starting organization from the target task.
- Preserve every current value outside the approved scope. Never use the source-observed first-visit None initialization as a customer design default.
- Validate the customer's template and current export, preserve template metadata and translations, prepare only the supported delta, and run the shared setup-data and reference-data validations.
- Create an immutable preview showing the target, route, current and desired hierarchy state, classifications added or preserved, default-tree selection when applicable, package members and row counts, warnings, and checksum.
- Route the immutable package to
core.data-loader. A same-request auto-approve, auto approve, approve without asking, or skip confirmation instruction authorizes this one load after every validation gate passes; otherwise wait for later approval of the exact preview. Auto-approval never waives validation or authorizes a retry.
- Before submission, designate a safe writable task-local execution-receipt record. Immediately register the returned UCM Content ID, Data Loader Request ID, approved checksum, target/project/task and latest status through the declared core project services. Accepted initiation ends the submission request In Progress without status, process-log or export calls. If persistence fails, preserve any known ID and stop; repair local evidence without resubmitting or changing route.
Only on a later explicit status/results/verification request, use OHCL.STATUS_REQUEST_GATE to validate the registered receipt and exact project/target/task/request/archive binding before the core status/count/error workflow. Never repeat preparation, approval or submission. A status-only request returns that status without setup reads. Active status or timeout returns Processing/In Progress and waits for another request; terminal failure stops. For requested setup verification after terminal success, compare a fresh same-task target export with the approved changes and preserved values. Missing or mismatched evidence blocks completion, not a reason to replay an import.
- When the task reports that Maintain Project Organizations is required, hand off to its separately scoped setup task. Do not submit that process implicitly from this skill.
Runtime Readiness
- The operator needs authorized target-task access and permission to review, maintain, and verify the hierarchy configuration.
- The accountable owner must approve the hierarchy model, selected classifications, non-None default-tree selection, impact, and rollback expectation.
- Before package generation or import, the customer must provide or freshly export the exact target-environment FSM template and current data. Exact mappings, package names, metadata, member headers, translations, identity behavior, and process-log interpretation are resolved from that target evidence.
- A conflicting existing hierarchy type or a requested classification removal is not supported by the proven additive import contract. Report only that operation as unsupported unless current target evidence proves a non-UI contract.
- No supported direct REST mutation contract is evidenced.
Refined Best-Practice Control Contract
Before producing a design recommendation, validation result, import preview, or completion claim, execute ora-resource/ora_rule_registry.json and apply the refined controls from the standard ora_input_validation.md, ora_defaulting_rules.md, ora_reference_lookups.md, ora_dependency_readiness.md, ora_design_enforcement.md, and ora_error_handling.md resources selected by that graph.
- Treat every Blocking control as a stop gate. Do not preview or approve a configuration that violates it.
- Treat every Required evidence item as mandatory decision evidence. Return
needs_input with the missing fields instead of silently defaulting.
- Treat every Operational control as a required readiness output. A one-time setup can be technically valid without the report, but the skill must not claim operational readiness until the report or reconciliation is defined.
- Preserve documented exceptions only where the control explicitly allows one; capture rationale, owner, approval reference, effective dates, and review date.
- Recalculate source-document population counts from the current target. Historical counts in the source are context, not validation constants.
Durable Artifacts and Review
Resolve project_id from the selected existing implementation project before preparation or execution; missing project identity is an input-validation blocker. Persist plans, validation results, immutable previews, approved package references, execution receipts and redacted failure diagnostics under project/{project_id}/artifacts/pillars/erp/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/current/. Raw exports belong under project/{project_id}/exports/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/. Never persist credentials or tokens there.
Use core.project-mgmt.artifact-version-manager for major new versions and confirmed minor updates, core.project-mgmt.artifact-registry-manager to register each durable artifact, and core.project-mgmt.project-state-manager to update only declared state fields and record the run under project/{project_id}/state/runs/. Persist each receipt before the next external call; append later statuses and retain partial failures, environment, operation, external IDs, artifact references and next action. Recover uncertain writes through supported reads; do not resubmit automatically. Record token usage using the manifest policy.
Required reviewers: responsible ERP Pillar Development Lead or SME, FSCR A-Team/core reviewer, and QA for validation/execution changes. Package readiness does not replace merge approval.
1---2skill_id: "erp.project-financial-management.project-organizations.manage-organization-hierarchies-and-classifications"3name: manage-organization-hierarchies-and-classifications-setup-ta4description: "Provides customer-FSCR-only assisted setup guidance for Manage Organization Hierarchies and Classifications under Project Organizations."5layer: "pillar"6pillar: "ERP"7offering: "Project Financial Management"8functional_area: "Project Organizations"9functional_area_code: "ORA_PJF_PROJ_ORG"10task_code: "PJF_MANAGE_ORGANIZATION_HIERARCHIES_AND_CLASSIFICATIONS"11task_name: "Manage Organization Hierarchies and Classifications"12parent_skill_id: "erp.project-financial-management.project-organizations"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: "ERP project financial management pillar team"22version: "0.2.1"23inputs:24 - "project_id"25 - "target_environment"26 - "approved_organization_hierarchy_scope"27 - "current_target_state"28 - "setup_data_artifacts"29outputs:30 - "organization_hierarchy_readiness_review"31 - "template_gated_import_preview"32 - "target_state_verification"33 - "execution_receipt_record"34 - "skill_run_record"35 - "token_usage_record"36depends_on:37 - "shared.setup-export.task-level-export"38 - "shared.validation.setup-data-validator"39 - "shared.validation.reference-data-validator"40 - "core.data-loader"41uses_core:42 - "core.project-mgmt.artifact-version-manager"43 - "core.project-mgmt.artifact-registry-manager"44 - "core.project-mgmt.project-state-manager"4546token_usage_tracking:47 enabled: true48 granularity: "per_skill_run"49 artifact_type: "token_usage_record"50 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"51 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"52 required_fields:53 - "activity_start_time"54 - "skill_id"55 - "task"56 - "trigger"57 - "artifacts_written"58 - "files_read"59 - "estimated_input_tokens"60 - "estimated_output_tokens"61 - "estimated_total_tokens"62 - "estimation_method"63 - "notes"64persists_project_state: true65state_updates:66 - "setup_task_sequence"67 - "configuration_blueprints"68 - "validation_results"69 - "reports"70 - "token_usage_records"71workspace_outputs:72 - artifact_type: "configuration_blueprint"73 default_location: "project/{project_id}/artifacts/pillars/erp/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/current/"74 versioning_policy: "major-new-version-minor-confirm-update"75 - artifact_type: "validation_result"76 default_location: "project/{project_id}/artifacts/pillars/erp/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/current/"77 versioning_policy: "major-new-version-minor-confirm-update"78 - artifact_type: "report"79 default_location: "project/{project_id}/artifacts/pillars/erp/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/current/"80 versioning_policy: "major-new-version-minor-confirm-update"81 - artifact_type: "skill_run"82 default_location: "project/{project_id}/state/runs/"83 versioning_policy: "append-only"84 - artifact_type: "token_usage_record"85 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"86 versioning_policy: "append-only"87applicability:88 industries:89 - "All"90 countries:91 - "All"92 fusion_releases:93 - "Current Oracle Fusion Cloud release"94side_effects:95 - "Writes task plans, validation/preview evidence, execution receipts and redacted diagnostics to the selected project workspace through core project services."96required_privileges: []97metadata:98 source: https://skillmd.com/skills/oracle/manage-organization-hierarchies-and-classifications-setup-ta99---100101# Manage Organization Hierarchies and Classifications Setup Task Guidance102103## Purpose104105Provide customer-FSCR-only assisted guidance to select the enterprise organization-hierarchy model, maintain the organization classifications used by Project Financial Management, and verify the resulting target state. A controlled FSM import is available only after the customer supplies or freshly exports the exact target-pod template and its import metadata.106107## REST Request Preflight108109Before any workflow-selected REST request, apply the offering's110[REST version and query compatibility preflight](../../references/rest-query-compatibility.md).111Determine the effective framework version from the selected core client or112workflow, construct compatible query parameters, and verify that the outgoing113header agrees. Do not hardcode a separate pillar version. Existing route,114validation, classification/matching, persistence and approval gates still apply.115116## Setup Task Skill Contract117118- task_code: `PJF_MANAGE_ORGANIZATION_HIERARCHIES_AND_CLASSIFICATIONS`119- task_name: `Manage Organization Hierarchies and Classifications`120- parent_skill_id: `erp.project-financial-management.project-organizations`121- pillar: `ERP`122- offering: `Project Financial Management`123- functional_area: `Project Organizations`124- functional_area_code: `ORA_PJF_PROJ_ORG`125- available_flag: `Y`126- export_import_supported_flag: `Y`127- csv_export_import_supported_flag: `Y`128- dataloader_import_mode: `FSM`129- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`130131## Usage132133Use this skill when planning, maintaining, importing, or validating setup data for `Manage Organization Hierarchies and Classifications` under `Project Organizations`.134135## Customer Inputs136137- Target environment and an accountable owner for the enterprise hierarchy decision.138- Approved current and desired hierarchy type, selected organization classifications, business impact, deployment window, and rollback expectation.139- For a non-None hierarchy, the approved target-visible tree, active tree version, and starting organization.140- Current target-task state or a fresh current-data export for update reconciliation.141- For FSM import, the customer-provided or freshly exported target-pod template, metadata, package contract, and process-log access.142143## Supported Task Behavior144145The task owns the Projects hierarchy type, selected organization classifications, and the default tree/version/starting-organization combination. Adding, moving, or removing organization-tree nodes is a manual `PER_MANAGE_ORGANIZATION_TREE` prerequisite boundary on this branch. Obtain a same-target handoff with tree structure, tree code, tree version, saved relationship/change evidence, and validation/activation state. Do not invoke an unavailable Workforce Structures skill or substitute an HDL import from this task.146147Use a target-template-gated FSM import to set the hierarchy type only when the target does not already have one and to add validated classification values. Do not use the proven import contract to replace a different existing hierarchy type or remove classifications. Those operations remain unsupported for automated execution unless a fresh target contract directly proves them; do not redirect them to UI maintenance.148149No direct customer REST write or internal application-module invocation is supported by this skill. Internal source behavior informs validation and sequencing only.150151## Assisted Workflow1521531. Confirm the exact target, owner, approved hierarchy outcome, selected classifications, impact, deployment window, and rollback expectation.1542. Reconcile the current target-visible hierarchy type, classifications, and applicable default-tree selection. Treat supplied current-data reports as guidance, not as a universal required value set.1553. Select the route by operation:156 - Use template-gated FSM import only when the exact target-pod template and metadata prove the required package contract and the proposed change is supported by that contract.157 - Return an operation-specific unsupported result for replacement or removal when the target contract does not prove it. Continue unrelated supported additive work.158 - Return the manual `PER_MANAGE_ORGANIZATION_TREE` prerequisite handoff for node placement and stop affected work until its saved same-target evidence is supplied. This handoff is outside this task's execution and does not approve the subsequent ESS sequence.1594. Validate that at least one approved classification remains selected. For a non-None hierarchy, resolve one valid tree, active version, and starting organization from the target task.1605. Preserve every current value outside the approved scope. Never use the source-observed first-visit None initialization as a customer design default.1616. Validate the customer's template and current export, preserve template metadata and translations, prepare only the supported delta, and run the shared setup-data and reference-data validations.1627. Create an immutable preview showing the target, route, current and desired hierarchy state, classifications added or preserved, default-tree selection when applicable, package members and row counts, warnings, and checksum.1638. Route the immutable package to `core.data-loader`. A same-request `auto-approve`, `auto approve`, `approve without asking`, or `skip confirmation` instruction authorizes this one load after every validation gate passes; otherwise wait for later approval of the exact preview. Auto-approval never waives validation or authorizes a retry.1649. Before submission, designate a safe writable task-local execution-receipt record. Immediately register the returned UCM Content ID, Data Loader Request ID, approved checksum, target/project/task and latest status through the declared core project services. Accepted initiation ends the submission request In Progress without status, process-log or export calls. If persistence fails, preserve any known ID and stop; repair local evidence without resubmitting or changing route.165 Only on a later explicit status/results/verification request, use OHCL.STATUS_REQUEST_GATE to validate the registered receipt and exact project/target/task/request/archive binding before the core status/count/error workflow. Never repeat preparation, approval or submission. A status-only request returns that status without setup reads. Active status or timeout returns Processing/In Progress and waits for another request; terminal failure stops. For requested setup verification after terminal success, compare a fresh same-task target export with the approved changes and preserved values. Missing or mismatched evidence blocks completion, not a reason to replay an import.16610. When the task reports that Maintain Project Organizations is required, hand off to its separately scoped setup task. Do not submit that process implicitly from this skill.167168## Runtime Readiness169170- The operator needs authorized target-task access and permission to review, maintain, and verify the hierarchy configuration.171- The accountable owner must approve the hierarchy model, selected classifications, non-None default-tree selection, impact, and rollback expectation.172- Before package generation or import, the customer must provide or freshly export the exact target-environment FSM template and current data. Exact mappings, package names, metadata, member headers, translations, identity behavior, and process-log interpretation are resolved from that target evidence.173- A conflicting existing hierarchy type or a requested classification removal is not supported by the proven additive import contract. Report only that operation as unsupported unless current target evidence proves a non-UI contract.174- No supported direct REST mutation contract is evidenced.175176## Refined Best-Practice Control Contract177178Before producing a design recommendation, validation result, import preview, or completion claim, execute [ora-resource/ora_rule_registry.json](ora-resource/ora_rule_registry.json) and apply the refined controls from the standard `ora_input_validation.md`, `ora_defaulting_rules.md`, `ora_reference_lookups.md`, `ora_dependency_readiness.md`, `ora_design_enforcement.md`, and `ora_error_handling.md` resources selected by that graph.179180- Treat every **Blocking control** as a stop gate. Do not preview or approve a configuration that violates it.181- Treat every **Required evidence** item as mandatory decision evidence. Return `needs_input` with the missing fields instead of silently defaulting.182- Treat every **Operational control** as a required readiness output. A one-time setup can be technically valid without the report, but the skill must not claim operational readiness until the report or reconciliation is defined.183- Preserve documented exceptions only where the control explicitly allows one; capture rationale, owner, approval reference, effective dates, and review date.184- Recalculate source-document population counts from the current target. Historical counts in the source are context, not validation constants.185186## Durable Artifacts and Review187188Resolve `project_id` from the selected existing implementation project before preparation or execution; missing project identity is an input-validation blocker. Persist plans, validation results, immutable previews, approved package references, execution receipts and redacted failure diagnostics under `project/{project_id}/artifacts/pillars/erp/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/current/`. Raw exports belong under `project/{project_id}/exports/project-financial-management/project-organizations/manage-organization-hierarchies-and-classifications/`. Never persist credentials or tokens there.189190Use `core.project-mgmt.artifact-version-manager` for major new versions and confirmed minor updates, `core.project-mgmt.artifact-registry-manager` to register each durable artifact, and `core.project-mgmt.project-state-manager` to update only declared state fields and record the run under `project/{project_id}/state/runs/`. Persist each receipt before the next external call; append later statuses and retain partial failures, environment, operation, external IDs, artifact references and next action. Recover uncertain writes through supported reads; do not resubmit automatically. Record token usage using the manifest policy.191192Required reviewers: responsible ERP Pillar Development Lead or SME, FSCR A-Team/core reviewer, and QA for validation/execution changes. Package readiness does not replace merge approval.