Manage Resources Setup Task Guidance
Purpose
Provides ResourceUser-specific import and export routing for Manage Resources under Customer Data Management Resources.
Setup Task Skill Contract
- task_code:
HZ_MANAGE_RESOURCES
- task_name:
Manage Resources
- parent_skill_id:
cx.customer-data-management.resources
- pillar:
CX
- offering:
Customer Data Management
- functional_area:
Resources
- functional_area_code:
ORA_CRM_RESOURCES
- available_flag:
Y
- export_import_supported_flag:
N
- csv_export_import_supported_flag:
N
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Resources under Customer Data Management Resources.
CX Resource Import and Export Contract
Use core.data-loader for ResourceUser CX Import and
core.fusion-api.cx-import-export-management only for ResourceUser Export
Management.
- CX Import object code: default to
ResourceUser when this Manage Resources
workflow receives an import without a valid CX mapping CSV. A mapping CSV's
IMPORT OBJECT is authoritative. Stop for clarification if the caller
explicitly requests a different object code.
- CX Import source: one CX ZIP or one or more direct CSV files. Data Loader
resolves the UCM account from live object metadata; do not hard-code or
accept a caller-supplied UCM account or
InputFileContentId.
- Export Management object:
ResourceUser.
- Export options: caller-supplied column names, filter criteria, mapping, file,
output settings, polling duration, and optional local download path.
The FSM catalog flags below describe setup-task export/import support. They do
not prohibit this separate CX Import or Export Management workflow.
Setup Task Metadata
- Task name:
Manage Resources
- Task code:
HZ_MANAGE_RESOURCES
- Available:
Y
- Export/import supported:
N
- CSV export/import supported:
N
- CSV export/import routing:
not supported
FSM Setup-Data Boundary
CSVExportImportSupportedFlag is N, so this task is not marked as CSV export/import supported in the effective setup-task catalog.
The CX REST export workflow is separate from that FSM setup-data capability.
CX ResourceUser Import and Export Routing
All delegated Fusion REST calls in this task, including the ResourceUser role,
parent, and hierarchy lookups, must include Rest-Framework-Version: 9.
Direct Reportees Lookup
Use the read-only resource_user_reportees operation for requests such as
"direct reportees of " or "resources reporting to ."
The request must supply exactly one manager ResourceEmail or exact manager
PartyName. Resolve the manager to one complete Resource User with a nonblank
email, then list Resource Users whose ResourceOrgManagerEmail exactly equals
that resolved email. Retrieve every page and retain only current resources
(blank or future ResourceEndDate).
This branch is read-only: it does not use Data Loader, a preview, approval,
POST/PATCH, Reporting Hierarchy Generation, or Send Pending LDAP Requests.
Return an explicit empty list when the manager has no current reportees. Do not
infer reportees from a shared organization, role name, or hierarchy position.
Read-Only Resource Users and Backport Boundary
Use resource_user_get for exactly one existing Resource User identified by
ResourceEmail or ResourcePartyNumber. Resolve one complete visible match through
core.fusion-api.rest-api-client and return only requested authorized fields.
Use resource_user_reportees for the separate read-only direct-reportees route.
Neither read branch enters Data Loader, preview, approval, or post-processing.
This 26.10 backport does not route one-resource create, update, promotion,
demotion, transfer, end-date, or permanent deletion through Resource Users
REST Data Loader. The required Data Loader REST business-object seed is not
assumed to be available. Do not substitute direct Resource Users POST/PATCH or
construct a one-resource Data Loader source. For resource creation or updates,
use the documented ResourceUser CX Import only when the caller supplies a CSV
or CX ZIP source; otherwise stop and request a supported import source.
Standalone organization-membership changes remain outside the one-resource
route. ResourceUser CX Import retains its documented CSV membership fields.
Use the following task-specific routing. Do not duplicate either core skill's
command templates, OAuth workflow, UCM upload mechanics, or API calls.
For resource_user_reportees, use only
core.fusion-api.rest-api-client for the documented Resource Users GET
lookups. This operation is separate from CX Import and Export Management.
For resource_user_get, use only core.fusion-api.rest-api-client and the
exact Resource Users identity lookup. Return the requested authorized fields
from one complete result; stop on zero, multiple, incomplete, or unauthorized
results. Do not route this operation to Data Loader.
For import, use the core.data-loader CX Import route. Begin with the
immutable preview using upload_and_initiate.py and --cx-import, without
--approve-upload. Direct CSV groups use repeated --ide-file inputs. For a
source without a valid CX mapping CSV, default the object code to
ResourceUser and pass --cx-import-object-code ResourceUser to Data
Loader. Do not override a valid mapping CSV's IMPORT OBJECT. If the caller
explicitly names a different object code, stop for clarification rather than
substituting ResourceUser. Data Loader must read
objectMetadata/ResourceUser?fields=UcmAccount&onlyData=true during preview
and approval, and use that returned nonblank account for all CX uploads.
For each import row, map Role to ResourceOrgRoleCode when an
Organization is supplied. Use IndividualRoleCode only when the caller
explicitly identifies the role as individual; otherwise stop for role-routing
clarification.
A single CSV may contain parent and dependent ResourceUser rows when every
parent row is listed before each row that references it. Validate the ordered
dependency chain before preview; do not split a correctly ordered file solely
because it contains parent and child resources.
Before preview, select only the first 10 non-header CSV rows in source order.
Collect distinct nonblank ResourceOrgRoleCode and IndividualRoleCode
values from that sample only. Use
core.fusion-api.rest-api-client to retrieve active roles from
GET /crmRestApi/resources/11.13.18.05/resourceRoles with
finder=AllActiveResourceRolesRowFinder, an exact q predicate that joins
all distinct sampled role codes with OR, and
Rest-Framework-Version: 9. Compare the returned RoleCode values. A code
is valid only when returned by this exact active-role lookup. Preserve the
routing context (ResourceOrgRoleCode or
IndividualRoleCode) but never include source row details in diagnostics.
If any distinct code is unresolved, block the import and report a sanitized,
de-duplicated list of unresolved codes by routing context. Do not submit a
partial import.
Collect ResourceOrgManagerEmail values from the same first 10 rows only.
An earlier sampled parent row satisfies the dependency; otherwise use the
exact parent lookup below. Do not look up role codes or manager emails from
rows after the first 10. Inform the user that only the first 10 rows were
validated and require explicit confirmation to proceed for all remaining
rows. Record that the result is a first-10-row sample, not full-file
reference validation. This confirmation permits normal import preview and
approval only; it does not initiate the data load.
For every parent email referenced by ResourceOrgManagerEmail that is not
supplied by an earlier CSV row, use the exact ResourceUser lookup
GET /crmRestApi/resources/11.13.18.05/resourceUsers?q=ResourceEmail='<email>'
through core.fusion-api.rest-api-client with Rest-Framework-Version: 9.
Require exactly one returned item
whose ResourceEmail exactly matches the requested email. Do not infer a
missing parent from an unfiltered, partial, or paginated collection request.
A zero-result lookup establishes only that the parent is not visible to the
calling principal; stop for confirmation rather than reporting that the
parent is absent from the target environment. Treat multiple results, a REST
error, or an incomplete response as inconclusive and stop for resolution.
For export, use operation=create-export and ExportObject=ResourceUser.
Pass a unique job name, a caller-provided filter on the top-level object,
optional selected columns and output settings, the activation choice, and an
optional local download path.
For ResourceUser CX Import, after the non-write rules finish, use
core.data-loader.task-hook to build the
data-load preview with the final archive SHA-256 and ordered rule results. Only
after explicit approval, approve and verify that preview to produce the exact
task-validation envelope. Immediately before the first POST, rerun the same
immutable source with --cx-import, --task-routed, the verified
--task-validation-envelope, --approve-upload, and
--approved-sha256 <complete-preview-sha256>.
Data Loader initiation is not import completion. Do not poll automatically.
Only when the user explicitly asks for status, results, counts, or errors, use
the Data Loader status route. Once that route—or another selected completion
check—confirms a successful completed ResourceUser load, continue directly into
post-import ESS routing.
Do not end a successful import result before post-import routing. Independently
validate eligibility and readiness for Reporting Hierarchy Generation and Send
Pending LDAP Requests, then present the eligible job or jobs and ask for one
fresh post_import_ess_execution_approval to submit them. The import approval
never authorizes post-import ESS processing, and no ESS job is submitted until
that fresh approval is supplied.
Post-Import ESS Routing
Only after a Data Loader completion check confirms a complete ResourceUser load
with successful rows, independently determine whether either documented
scheduled process is needed. Do not start a post-import process for an
initiated, unavailable, incomplete, or failed load.
Reporting Hierarchy Generation applies when the import changes resource
organizations or reporting-manager hierarchy. Resolve the active Tree Version
ID through the lookup below, then hand off only the validated current-request
values to cx.customer-data-management.resources.run-reporting-hierarchy-generation:
tree_structure_code=RESOURCE_ORG_TREE_STRUCTURE,
tree_code=GLOBAL_SALES_MARKETING, tree_version_id=<validated ID>,
submit=true, target Fusion environment context, and successful
import-completion evidence. Manage Resources must not construct, preview, or
submit the Reporting Hierarchy CrmEss request. The receiving skill owns the
application, job definition, ordered submit.argument1 through
submit.argument3 bindings, final tree/version validation, ESS submission,
and tracking. After that skill returns its preview, pass the fresh approved
Reporting Hierarchy item as its required execution_approval.
Evaluate CreateUserAccountFlag across every imported row before deciding
Send Pending LDAP Requests. Suppress the LDAP job only when every row
explicitly sets CreateUserAccountFlag=N; state that all rows suppress LDAP
processing. If any row is absent or has a value other than N, ignore this
suppression rule and submit the LDAP job without a flag-specific message.
Invoke core.fusion-api.ess-job-submitter using the verified deployment
contract: application EarHcmEss, job definition
JobDefinition://oracle/apps/ess/hcm/users/ProcessLdapRequests, and these
ordered request parameters:
[
{ "name": "submit.argument1", "paramType": "STRING", "value": "ALL" },
{ "name": "submit.argument2", "paramType": "STRING", "value": "ALL" },
{ "name": "submit.argument3", "paramType": "STRING", "value": "A" }
]
The Oracle Scheduled Processes documentation identifies the business values
User Type=All and Batch Size=A (automatic calculation). Bind them as
submit.argument1=ALL and submit.argument3=A, respectively. Preserve the
required middle value submit.argument2=ALL as part of the verified runtime
contract; the Oracle page does not publish its technical argument name or UI
label. Do not infer or rename that argument, substitute UI display labels for
technical parameter names, or omit a parameter. The caller may override only
a business value when its corresponding technical argument mapping is known
and the resulting complete request is previewed before submission.
After the import result is successful, present a fresh post-import preview for
each eligible ESS job. The preview must identify the target environment,
purpose, application, job definition ID, and exact parameters. For Reporting
Hierarchy Generation, obtain those ESS details from the receiving skill's
validated preview; do not duplicate or infer its CrmEss contract locally.
Require post_import_ess_execution_approval immediately before submitting any
listed job. Pass the approved Reporting Hierarchy item to the receiving skill
as its required execution_approval; the import approval never authorizes
post-import ESS processing. Do not
perform a Scheduler active-instance lookup and do not accept a concurrency
override. Submit only the eligible jobs named in the current approval. When
both are approved, submit and poll them asynchronously and independently; an
unsuccessful job must not cancel monitoring of the other job.
For post-import Reporting Hierarchy Generation, use
core.fusion-api.rest-api-client to query
GET /fscmRestApi/resources/11.13.18.05/fndTreeVersions for the selected Tree
Structure Code and Tree Code, with Rest-Framework-Version: 9. Use a candidate only when all conditions hold on
the target environment's current date: Status=ACTIVE,
EffectiveStartDate is on or before the current date, and EffectiveEndDate
is blank or on or after the current date. If no candidate or more than one
candidate meets these conditions, stop the ESS branch and record the returned
candidate metadata; do not select a version arbitrarily.
Resource Guidance Routing
Use ora-resource/ora_rule_registry.json as the authoritative task-local
execution graph. It selects ResourceUser CX Import, Export Management, exact
single-resource GET, or direct reportees, with separate successful terminals. Use the following guidance files for the
selected branch:
ora-resource/ora_input_intake.md for operation selection and runtime
inputs.
ora-resource/ora_defaulting_rules.md for ResourcePartyNumber import and export
output defaults before validation.
ora-resource/ora_input_validation.md for import or export input checks and
result evaluation.
ora-resource/ora_dependency_readiness.md for import prerequisites and
export visibility dependencies.
ora-resource/ora_reference_lookups.md for role, parent, direct-reportees,
and hierarchy-version lookups.
ora-resource/ora_bulk_intake.md for ResourceUser CSV mapping and bulk
import preparation.
ora-resource/ora_design_enforcement.md for supported import scope,
duplicate-import, export-filter, and access-policy gates.
ora-resource/ora_rest_execution.md for read-only GET and direct-reportees
result branches plus import/export preview, approval, delegated execution,
polling, download, and result-review gates.
ora-resource/ora_error_handling.md for stop-before-retry behavior and
post-import ESS outcomes.
These files define task-specific policy and branch routing. Delegate CX Import
preview, metadata lookup, UCM staging, initiation, and requested status checks
to core.data-loader; delegate only ResourceUser export creation, activation,
polling, and download to core.fusion-api.cx-import-export-management.
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
resource_import_source
cx_import_object_code
cx_import_mapping
data_load_status_request
remaining_rows_validation_confirmation
reporting_hierarchy_tree_version_id
ldap_user_type
ldap_batch_size
resource_operation
resource_export_job_name
resource_export_filter
resource_export_columns
resource_export_output_options
resource_export_activation_choice
polling_request
execution_approval
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
unresolved_resource_role_codes
data_load_preview
data_load_request_id
data_load_status
post_import_ess_summary
reporting_hierarchy_request_id
ldap_request_id
export_activity_summary
export_download_path
diagnostics
audit_summary
skill_run_record
token_usage_record
Implementation Notes
Use the parent functional-area skill cx.customer-data-management.resources 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.resources.manage-resources"3name: manage-resources-setup-task-guidance4description: "Routes ResourceUser CX Import and Export, exact read-only Resource Users lookups, direct reportees, and eligible post-import ESS processing for Manage Resources under Customer Data Management Resources."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Resources"9functional_area_code: "ORA_CRM_RESOURCES"10task_code: "HZ_MANAGE_RESOURCES"11task_name: "Manage Resources"12parent_skill_id: "cx.customer-data-management.resources"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: "planning"20execution_mode: "assisted"21owner_team: "CX customer data management pillar team"22version: "0.1.24"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28 - "resource_import_source"29 - "cx_import_object_code"30 - "cx_import_mapping"31 - "data_load_status_request"32 - "remaining_rows_validation_confirmation"33 - "reporting_hierarchy_tree_version_id"34 - "ldap_user_type"35 - "ldap_batch_size"36 - "resource_operation"37 - "resource_export_job_name"38 - "resource_export_filter"39 - "resource_export_columns"40 - "resource_export_output_options"41 - "resource_export_activation_choice"42 - "resource_user_get"43 - "resource_user_reportees"44 - "resource_email"45 - "manager_resource_email"46 - "manager_party_name"47 - "resource_party_number"48 - "polling_request"49 - "execution_approval"50 - "post_import_ess_execution_approval"51outputs:52 - "setup_task_plan"53 - "setup_data_routing"54 - "validation_checkpoints"55 - "unresolved_resource_role_codes"56 - "data_load_preview"57 - "data_load_request_id"58 - "data_load_status"59 - "post_import_ess_summary"60 - "reporting_hierarchy_handoff"61 - "reporting_hierarchy_request_id"62 - "ldap_request_id"63 - "export_activity_summary"64 - "export_download_path"65 - "resource_user_reportees_summary"66 - "diagnostics"67 - "audit_summary"68 - "post_import_ess_approval_audit"69 - "skill_run_record"70 - "token_usage_record"71uses_core:72 - "core.data-loader"73 - "core.data-loader.task-hook"74 - "core.fusion-api.cx-import-export-management"75 - "core.fusion-api.ess-job-submitter"76 - "core.fusion-api.rest-api-client"77 - "core.project-mgmt.artifact-version-manager"78 - "core.project-mgmt.artifact-registry-manager"79 - "core.project-mgmt.project-state-manager"80depends_on:81 - "cx.customer-data-management.resources.run-reporting-hierarchy-generation"82persists_project_state: true83token_usage_tracking:84 enabled: true85 granularity: "per_skill_run"86 artifact_type: "token_usage_record"87 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"88 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"89 required_fields:90 - "activity_start_time"91 - "skill_id"92 - "task"93 - "trigger"94 - "artifacts_written"95 - "files_read"96 - "estimated_input_tokens"97 - "estimated_output_tokens"98 - "estimated_total_tokens"99 - "estimation_method"100 - "notes"101state_updates:102 - "setup_task_sequence"103 - "configuration_blueprints"104 - "validation_results"105 - "token_usage_records"106workspace_outputs:107 - artifact_type: "configuration_blueprint"108 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/resources/manage-resources/current/"109 versioning_policy: "major-new-version-minor-confirm-update"110 - artifact_type: "validation_result"111 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/resources/manage-resources/current/"112 versioning_policy: "major-new-version-minor-confirm-update"113 - artifact_type: "skill_run"114 default_location: "project/{project_id}/state/runs/"115 versioning_policy: "append-only"116 - artifact_type: "token_usage_record"117 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"118 versioning_policy: "append-only"119applicability:120 industries:121 - "All"122 countries:123 - "All"124 fusion_releases:125 - "Current Oracle Fusion Cloud release"126side_effects:127 - "Delegates approved ResourceUser CX Import initiation to core.data-loader."128 - "Delegates approved ResourceUser Export Management activity creation and activation to core.fusion-api.cx-import-export-management."129 - "Delegates eligible Reporting Hierarchy Generation to its dedicated skill after a successful ResourceUser completion status confirms hierarchy changes and fresh post-import approval is explicit."130 - "Submits Send Pending LDAP Requests after a successful ResourceUser completion status confirms eligible user-account creation, readiness checks pass, and fresh post-import approval is explicit."131required_privileges: []132metadata:133 source: https://skillmd.com/skills/oracle/manage-resources-setup-task-guidance134---135136# Manage Resources Setup Task Guidance137138## Purpose139140Provides ResourceUser-specific import and export routing for `Manage Resources` under `Customer Data Management Resources`.141142## Setup Task Skill Contract143144- task_code: `HZ_MANAGE_RESOURCES`145- task_name: `Manage Resources`146- parent_skill_id: `cx.customer-data-management.resources`147- pillar: `CX`148- offering: `Customer Data Management`149- functional_area: `Resources`150- functional_area_code: `ORA_CRM_RESOURCES`151- available_flag: `Y`152- export_import_supported_flag: `N`153- csv_export_import_supported_flag: `N`154- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`155156## Usage157158Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Resources` under `Customer Data Management Resources`.159160## CX Resource Import and Export Contract161162Use `core.data-loader` for ResourceUser CX Import and163`core.fusion-api.cx-import-export-management` only for ResourceUser Export164Management.165166- CX Import object code: default to `ResourceUser` when this Manage Resources167 workflow receives an import without a valid CX mapping CSV. A mapping CSV's168 `IMPORT OBJECT` is authoritative. Stop for clarification if the caller169 explicitly requests a different object code.170- CX Import source: one CX ZIP or one or more direct CSV files. Data Loader171 resolves the UCM account from live object metadata; do not hard-code or172 accept a caller-supplied UCM account or `InputFileContentId`.173- Export Management object: `ResourceUser`.174- Export options: caller-supplied column names, filter criteria, mapping, file,175 output settings, polling duration, and optional local download path.176177The FSM catalog flags below describe setup-task export/import support. They do178not prohibit this separate CX Import or Export Management workflow.179180## Setup Task Metadata181182- Task name: `Manage Resources`183- Task code: `HZ_MANAGE_RESOURCES`184- Available: `Y`185- Export/import supported: `N`186- CSV export/import supported: `N`187- CSV export/import routing: `not supported`188189## FSM Setup-Data Boundary190191`CSVExportImportSupportedFlag` is `N`, so this task is not marked as CSV export/import supported in the effective setup-task catalog.192193The CX REST export workflow is separate from that FSM setup-data capability.194195## CX ResourceUser Import and Export Routing196197All delegated Fusion REST calls in this task, including the ResourceUser role,198parent, and hierarchy lookups, must include `Rest-Framework-Version: 9`.199200## Direct Reportees Lookup201202Use the read-only `resource_user_reportees` operation for requests such as203"direct reportees of <manager>" or "resources reporting to <manager>."204205The request must supply exactly one manager `ResourceEmail` or exact manager206`PartyName`. Resolve the manager to one complete Resource User with a nonblank207email, then list Resource Users whose `ResourceOrgManagerEmail` exactly equals208that resolved email. Retrieve every page and retain only current resources209(blank or future `ResourceEndDate`).210211This branch is read-only: it does not use Data Loader, a preview, approval,212POST/PATCH, Reporting Hierarchy Generation, or Send Pending LDAP Requests.213Return an explicit empty list when the manager has no current reportees. Do not214infer reportees from a shared organization, role name, or hierarchy position.215216## Read-Only Resource Users and Backport Boundary217218Use `resource_user_get` for exactly one existing Resource User identified by219ResourceEmail or ResourcePartyNumber. Resolve one complete visible match through220`core.fusion-api.rest-api-client` and return only requested authorized fields.221Use `resource_user_reportees` for the separate read-only direct-reportees route.222Neither read branch enters Data Loader, preview, approval, or post-processing.223224This 26.10 backport does not route one-resource create, update, promotion,225demotion, transfer, end-date, or permanent deletion through Resource Users226REST Data Loader. The required Data Loader REST business-object seed is not227assumed to be available. Do not substitute direct Resource Users POST/PATCH or228construct a one-resource Data Loader source. For resource creation or updates,229use the documented ResourceUser CX Import only when the caller supplies a CSV230or CX ZIP source; otherwise stop and request a supported import source.231Standalone organization-membership changes remain outside the one-resource232route. ResourceUser CX Import retains its documented CSV membership fields.233234Use the following task-specific routing. Do not duplicate either core skill's235command templates, OAuth workflow, UCM upload mechanics, or API calls.236237- For `resource_user_reportees`, use only238 `core.fusion-api.rest-api-client` for the documented Resource Users GET239 lookups. This operation is separate from CX Import and Export Management.240241- For `resource_user_get`, use only `core.fusion-api.rest-api-client` and the242 exact Resource Users identity lookup. Return the requested authorized fields243 from one complete result; stop on zero, multiple, incomplete, or unauthorized244 results. Do not route this operation to Data Loader.245246- For import, use the `core.data-loader` CX Import route. Begin with the247 immutable preview using `upload_and_initiate.py` and `--cx-import`, without248 `--approve-upload`. Direct CSV groups use repeated `--ide-file` inputs. For a249 source without a valid CX mapping CSV, default the object code to250 `ResourceUser` and pass `--cx-import-object-code ResourceUser` to Data251 Loader. Do not override a valid mapping CSV's `IMPORT OBJECT`. If the caller252 explicitly names a different object code, stop for clarification rather than253 substituting `ResourceUser`. Data Loader must read254 `objectMetadata/ResourceUser?fields=UcmAccount&onlyData=true` during preview255 and approval, and use that returned nonblank account for all CX uploads.256 For each import row, map `Role` to `ResourceOrgRoleCode` when an257 `Organization` is supplied. Use `IndividualRoleCode` only when the caller258 explicitly identifies the role as individual; otherwise stop for role-routing259 clarification.260 A single CSV may contain parent and dependent ResourceUser rows when every261 parent row is listed before each row that references it. Validate the ordered262 dependency chain before preview; do not split a correctly ordered file solely263 because it contains parent and child resources.264 Before preview, select only the first 10 non-header CSV rows in source order.265 Collect distinct nonblank `ResourceOrgRoleCode` and `IndividualRoleCode`266 values from that sample only. Use267 `core.fusion-api.rest-api-client` to retrieve active roles from268 `GET /crmRestApi/resources/11.13.18.05/resourceRoles` with269 `finder=AllActiveResourceRolesRowFinder`, an exact `q` predicate that joins270 all distinct sampled role codes with `OR`, and271 `Rest-Framework-Version: 9`. Compare the returned `RoleCode` values. A code272 is valid only when returned by this exact active-role lookup. Preserve the273 routing context (`ResourceOrgRoleCode` or274 `IndividualRoleCode`) but never include source row details in diagnostics.275 If any distinct code is unresolved, block the import and report a sanitized,276 de-duplicated list of unresolved codes by routing context. Do not submit a277 partial import.278 Collect `ResourceOrgManagerEmail` values from the same first 10 rows only.279 An earlier sampled parent row satisfies the dependency; otherwise use the280 exact parent lookup below. Do not look up role codes or manager emails from281 rows after the first 10. Inform the user that only the first 10 rows were282 validated and require explicit confirmation to proceed for all remaining283 rows. Record that the result is a first-10-row sample, not full-file284 reference validation. This confirmation permits normal import preview and285 approval only; it does not initiate the data load.286 For every parent email referenced by `ResourceOrgManagerEmail` that is not287 supplied by an earlier CSV row, use the exact ResourceUser lookup288 `GET /crmRestApi/resources/11.13.18.05/resourceUsers?q=ResourceEmail='<email>'`289 through `core.fusion-api.rest-api-client` with `Rest-Framework-Version: 9`.290 Require exactly one returned item291 whose `ResourceEmail` exactly matches the requested email. Do not infer a292 missing parent from an unfiltered, partial, or paginated collection request.293 A zero-result lookup establishes only that the parent is not visible to the294 calling principal; stop for confirmation rather than reporting that the295 parent is absent from the target environment. Treat multiple results, a REST296 error, or an incomplete response as inconclusive and stop for resolution.297- For export, use `operation=create-export` and `ExportObject=ResourceUser`.298 Pass a unique job name, a caller-provided filter on the top-level object,299 optional selected columns and output settings, the activation choice, and an300 optional local download path.301For ResourceUser CX Import, after the non-write rules finish, use302`core.data-loader.task-hook` to build the303data-load preview with the final archive SHA-256 and ordered rule results. Only304after explicit approval, approve and verify that preview to produce the exact305task-validation envelope. Immediately before the first POST, rerun the same306immutable source with `--cx-import`, `--task-routed`, the verified307`--task-validation-envelope`, `--approve-upload`, and308`--approved-sha256 <complete-preview-sha256>`.309310Data Loader initiation is not import completion. Do not poll automatically.311Only when the user explicitly asks for status, results, counts, or errors, use312the Data Loader status route. Once that route—or another selected completion313check—confirms a successful completed ResourceUser load, continue directly into314post-import ESS routing.315316Do not end a successful import result before post-import routing. Independently317validate eligibility and readiness for Reporting Hierarchy Generation and Send318Pending LDAP Requests, then present the eligible job or jobs and ask for one319fresh `post_import_ess_execution_approval` to submit them. The import approval320never authorizes post-import ESS processing, and no ESS job is submitted until321that fresh approval is supplied.322323## Post-Import ESS Routing324325Only after a Data Loader completion check confirms a complete ResourceUser load326with successful rows, independently determine whether either documented327scheduled process is needed. Do not start a post-import process for an328initiated, unavailable, incomplete, or failed load.329330- Reporting Hierarchy Generation applies when the import changes resource331 organizations or reporting-manager hierarchy. Resolve the active Tree Version332 ID through the lookup below, then hand off only the validated current-request333 values to `cx.customer-data-management.resources.run-reporting-hierarchy-generation`:334 `tree_structure_code=RESOURCE_ORG_TREE_STRUCTURE`,335 `tree_code=GLOBAL_SALES_MARKETING`, `tree_version_id=<validated ID>`,336 `submit=true`, target Fusion environment context, and successful337 import-completion evidence. Manage Resources must not construct, preview, or338 submit the Reporting Hierarchy `CrmEss` request. The receiving skill owns the339 application, job definition, ordered `submit.argument1` through340 `submit.argument3` bindings, final tree/version validation, ESS submission,341 and tracking. After that skill returns its preview, pass the fresh approved342 Reporting Hierarchy item as its required `execution_approval`.343- Evaluate `CreateUserAccountFlag` across every imported row before deciding344 Send Pending LDAP Requests. Suppress the LDAP job only when every row345 explicitly sets `CreateUserAccountFlag=N`; state that all rows suppress LDAP346 processing. If any row is absent or has a value other than `N`, ignore this347 suppression rule and submit the LDAP job without a flag-specific message.348 Invoke `core.fusion-api.ess-job-submitter` using the verified deployment349 contract: application `EarHcmEss`, job definition350 `JobDefinition://oracle/apps/ess/hcm/users/ProcessLdapRequests`, and these351 ordered request parameters:352353 ```json354 [355 { "name": "submit.argument1", "paramType": "STRING", "value": "ALL" },356 { "name": "submit.argument2", "paramType": "STRING", "value": "ALL" },357 { "name": "submit.argument3", "paramType": "STRING", "value": "A" }358 ]359 ```360361 The Oracle Scheduled Processes documentation identifies the business values362 `User Type=All` and `Batch Size=A` (automatic calculation). Bind them as363 `submit.argument1=ALL` and `submit.argument3=A`, respectively. Preserve the364 required middle value `submit.argument2=ALL` as part of the verified runtime365 contract; the Oracle page does not publish its technical argument name or UI366 label. Do not infer or rename that argument, substitute UI display labels for367 technical parameter names, or omit a parameter. The caller may override only368 a business value when its corresponding technical argument mapping is known369 and the resulting complete request is previewed before submission.370371After the import result is successful, present a fresh post-import preview for372each eligible ESS job. The preview must identify the target environment,373purpose, application, job definition ID, and exact parameters. For Reporting374Hierarchy Generation, obtain those ESS details from the receiving skill's375validated preview; do not duplicate or infer its `CrmEss` contract locally.376Require `post_import_ess_execution_approval` immediately before submitting any377listed job. Pass the approved Reporting Hierarchy item to the receiving skill378as its required `execution_approval`; the import approval never authorizes379post-import ESS processing. Do not380perform a Scheduler active-instance lookup and do not accept a concurrency381override. Submit only the eligible jobs named in the current approval. When382both are approved, submit and poll them asynchronously and independently; an383unsuccessful job must not cancel monitoring of the other job.384385For post-import Reporting Hierarchy Generation, use386`core.fusion-api.rest-api-client` to query387`GET /fscmRestApi/resources/11.13.18.05/fndTreeVersions` for the selected Tree388Structure Code and Tree Code, with `Rest-Framework-Version: 9`. Use a candidate only when all conditions hold on389the target environment's current date: `Status=ACTIVE`,390`EffectiveStartDate` is on or before the current date, and `EffectiveEndDate`391is blank or on or after the current date. If no candidate or more than one392candidate meets these conditions, stop the ESS branch and record the returned393candidate metadata; do not select a version arbitrarily.394395## Resource Guidance Routing396397Use `ora-resource/ora_rule_registry.json` as the authoritative task-local398execution graph. It selects ResourceUser CX Import, Export Management, exact399single-resource GET, or direct reportees, with separate successful terminals. Use the following guidance files for the400selected branch:401402- `ora-resource/ora_input_intake.md` for operation selection and runtime403 inputs.404- `ora-resource/ora_defaulting_rules.md` for ResourcePartyNumber import and export405 output defaults before validation.406- `ora-resource/ora_input_validation.md` for import or export input checks and407 result evaluation.408- `ora-resource/ora_dependency_readiness.md` for import prerequisites and409 export visibility dependencies.410- `ora-resource/ora_reference_lookups.md` for role, parent, direct-reportees,411 and hierarchy-version lookups.412- `ora-resource/ora_bulk_intake.md` for ResourceUser CSV mapping and bulk413 import preparation.414- `ora-resource/ora_design_enforcement.md` for supported import scope,415 duplicate-import, export-filter, and access-policy gates.416- `ora-resource/ora_rest_execution.md` for read-only GET and direct-reportees417 result branches plus import/export preview, approval, delegated execution,418 polling, download, and result-review gates.419- `ora-resource/ora_error_handling.md` for stop-before-retry behavior and420 post-import ESS outcomes.421422These files define task-specific policy and branch routing. Delegate CX Import423preview, metadata lookup, UCM staging, initiation, and requested status checks424to `core.data-loader`; delegate only ResourceUser export creation, activation,425polling, and download to `core.fusion-api.cx-import-export-management`.426427428## Inputs429430- `implementation_objective`431- `project_context`432- `setup_task_scope`433- `setup_data_artifacts`434- `resource_import_source`435- `cx_import_object_code`436- `cx_import_mapping`437- `data_load_status_request`438- `remaining_rows_validation_confirmation`439- `reporting_hierarchy_tree_version_id`440- `ldap_user_type`441- `ldap_batch_size`442- `resource_operation`443- `resource_export_job_name`444- `resource_export_filter`445- `resource_export_columns`446- `resource_export_output_options`447- `resource_export_activation_choice`448- `polling_request`449- `execution_approval`450451## Outputs452453- `setup_task_plan`454- `setup_data_routing`455- `validation_checkpoints`456- `unresolved_resource_role_codes`457- `data_load_preview`458- `data_load_request_id`459- `data_load_status`460- `post_import_ess_summary`461- `reporting_hierarchy_request_id`462- `ldap_request_id`463- `export_activity_summary`464- `export_download_path`465- `diagnostics`466- `audit_summary`467- `skill_run_record`468- `token_usage_record`469470## Implementation Notes471472Use the parent functional-area skill `cx.customer-data-management.resources` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.