Manage Beneficiary Organizations Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Beneficiary Organizations under Benefits General Configuration.
Setup Task Skill Contract
- task_code:
BEN_MANAGE_BENEFICIARY_ORGANIZATION - task_name:
Manage Beneficiary Organizations - parent_skill_id:
hcm.benefits-configuration.benefits-general-configuration - pillar:
HCM - offering:
Benefits Configuration - functional_area:
Benefits General Configuration - functional_area_code:
ORA_BENEFITS_GENERAL_CONFIGURATION - available_flag:
Y - export_import_supported_flag:
N - csv_export_import_supported_flag:
N - dataloader_import_mode:
HDL - businessObject:
Organization - source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Beneficiary Organizations under Benefits General Configuration.
Setup Task Metadata
- Task name:
Manage Beneficiary Organizations - Task code:
BEN_MANAGE_BENEFICIARY_ORGANIZATION - Available:
Y - Export/import supported:
N - CSV export/import supported:
N - CSV export/import routing:
not supported - Data Loader import mode:
HDL - Business Object:
Organization
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is N, so this task is not marked as CSV export/import supported in the effective setup-task catalog.
Do not route CSV export work to shared.setup-export.task-level-export or CSV import work to core.data-loader unless live Fusion metadata or Oracle guidance confirms support. Use shared.validation.setup-data-validator only when a setup data artifact is available for review. Use shared.validation.reference-data-validator when the task depends on cross-pillar reference data.
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifacts
Outputs
setup_task_plansetup_data_routingvalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill hcm.benefits-configuration.benefits-general-configuration for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
HDL workflow and validation
Read the task contract before intake, validation, preview, or submission. It owns the field checks, conditional requirements, identity rules, failure classes, and recovery policy. Use its standards resources in this order: input validation, reference resolution, dependency readiness, defaulting, design enforcement, and error handling.
- Establish operation, target environment, and task context. Collect the
organization name, effective start date, and any other metadata-required
organization values when no file is given. Collect either
LocationCodeandLocationSetCode, or Task Location Name and Location Set Name; request only missing required values. Do not solicitClassificationCodeorClassificationName: derive the classification name through the required LOV lookup. - Use core.data-loader for live
schema validation and file preparation. Resolve reference data through
the shared REST client,
using live supported lookup contracts; resolve
ClassificationNamefromorganizationClassificationsLOVforHR_BEN. When location names are supplied instead of explicit codes, resolve them throughlocationsLovat the organization effective start date. SendREST-Framework-Version: 9on both LOV requests. Do not add DB access to this skill. - Apply every task-contract preflight check to all rows. Return a blocked validation result for missing/invalid fields, uncertain identity, unsupported operations, or unresolved dependencies. These are assisted checks, not a compiled rule registry; do not report Task Hook automation as passed when task rules are not available.
- Follow core's immutable artifact and Task Hook approval workflow. Skill editing, sample generation, or prior upload approval does not authorize a new load. Never bypass core with a direct REST write.
- Report initiation separately from completion. If status monitoring is requested, use core's status and error queries until terminal status or the task-contract observation deadline. Preserve partial successes.
The catalog's FSM CSV support flag is not a ban on core's metadata-validated
spreadsheet-to-HDL conversion. Do not claim FSM export/import support from a
successful native HDL load. Native Organization source uses only the
Organization and OrgUnitClassification sections; exclude OrgInformation
from every generated DAT file. Use YYYY/MM/DD dates.
Failure handling and execution boundaries
Use the task contract's Preflight and validation results and Error handling and bounded recovery sections for input validation, metadata, authentication, authorization, transport, API, timeout, process failure, persistence, and approval errors. Stop before upload on a blocking check. Do not retry uncertain writes or roll back successful rows automatically. Corrected submissions need new validation and approval. Core's documented authentication and protocol-level retries remain authoritative.
Keep source records, secrets, and test-environment data out of tracked files. For delegated Data Loader operations, core's report and persistence policies take precedence over the generated planning-artifact defaults above; do not create extra run records or token logs for a loader-only operation.
Verification and review
- Run offline contract tests.
- Exercise workflow scenarios with synthetic inputs and mocked results; these scenarios are manual, not automated proof of live validation.
- Organization and trust create-oriented MERGE smoke tests have succeeded. Update, end-date, delete, and negative live tests remain unverified.
- Reviewers: Benefits Pillar Lead/SME and FSCR A-Team/core reviewer; QA review for workflow changes. A fresh live upload requires separate authorization.