Benefit Balances Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Benefit Balances under Benefits General Configuration.
Setup Task Skill Contract
- task_code:
BEN_MANAGE_BENEFIT_BALANCE - task_name:
Benefit Balances - 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:
benefitBalances - source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Benefit Balances under Benefits General Configuration.
Setup Task Metadata
- Task name:
Benefit Balances - Task code:
BEN_MANAGE_BENEFIT_BALANCE - Available:
Y - Export/import supported:
N - CSV export/import supported:
N - CSV export/import routing:
not supported - Data Loader import mode:
HDL - Business Object:
benefitBalances
HDL Business Object and Routing
CSVExportImportSupportedFlag is N; FSM CSV export/import is therefore not a supported route for this task. This does not prohibit the explicitly selected HDL route.
Use core.data-loader for Benefit Balances data loads. The supported HDL business object is benefitBalances; do not substitute the task label or a guessed REST resource. Generate the DAT structure from current Fusion Data Loader metadata before preparing a file. Do not use FSM CSV export/import, browser entry, REST, or an alternate loader as a substitute route.
The object configures a benefit balance. Validate the balance name, legal employer, and every other identity or prerequisite required by the current Data Loader sample before load preparation. The source DAT header and mandatory/optional attributes are release-sensitive, so the live Data Loader sample is authoritative over this skill.
For each supplied benefitBalances.BalanceUsageMeaning, NonMonetaryUnitsMeaning,
LegalEmployerName, or CurrencyName, apply the exact-match, read-only checks
in reference lookups before finalizing
the source. Use core.fusion-api.rest-api-client only when the active project
workflow selects this lookup step. A 403 records unverified_forbidden for that
field and does not fail field validation or stop independent checks; it does
not verify the value. Resolve access or use another workflow-approved
authoritative check before a live load. Keep HDL schema validation and loading
on the core.data-loader route.
For a supported date-effective create, update, or correction row whose current
section exposes EffectiveEndDate, default an omitted value to the end-of-time
date 4712/12/31; preserve a supplied value. Serialize the resulting DAT date
in the format required by the current section contract. An End date operation
requires the user's explicit end date and never uses this default.
HDL CRUD Operations
| Requested operation | HDL route | Control point |
|---|---|---|
| Create or merge | Create a benefitBalances DAT using the generated current sample. |
Validate the immutable artifact and obtain Data Loader workflow approval before upload. |
| Read / verify | Inspect metadata, load status, or a workflow-selected supported read route. | Read-only inspection does not authorize a subsequent load. |
| Update | Create a corrected or replacement DAT only when the current HDL schema and source identity support it. | Do not guess user keys or action syntax; revalidate and obtain a new approval. |
| Delete | Use an explicitly reviewed delete DAT only when current HDL metadata supports the requested deletion. | Treat as destructive; require explicit approval immediately before upload or initiation. |
Preflight and Approval Gates
- Confirm task
BEN_MANAGE_BENEFIT_BALANCE, thebenefitBalancesbusiness object, intended environment, and active project Run Book. - Generate or retrieve the current Data Loader sample; validate the DAT format, balance name, legal employer, and all required source identifiers and configuration facts required by that sample. For every included section, confirm its date-effectivity,
effectiveOffield availability, and supported row operations independently; stop if any contract is missing or ambiguous. - Validate every record and preserve row-level errors. Run the four conditional
reference lookups through the selected shared REST client; record each
supplied field as
valid,invalid,ambiguous, orunverified_forbidden. Stop on ambiguous identities, missing dependencies, unsupported action semantics, or CSV routing. For each included section that exposeseffectiveOf, derive it per row using the task-local operation mapping. Format every embedded date asYYYY-MM-DDbefore constructing the DAT; reject invalid or ambiguous source dates. OmiteffectiveOfentirely from a section that does not expose it. - Create an immutable load artifact and preflight it through
core.data-loader. - For Create, Update, or Delete, use the Data Loader workflow's current approval gate immediately before upload or initiation. Any artifact, target, or record change invalidates the approval.
Failure Handling
Load the task-local ora-resource/ora_input_validation.md, ora_dependency_readiness.md, ora_reference_lookups.md, ora_defaulting_rules.md, ora_design_enforcement.md, and ora_error_handling.md before preflight or live activity. Persist sanitized preflight and load diagnostics under the declared project workspace when project_id is provided.
Never automatically retry a DAT upload, load initiation, update, or delete. On an uncertain or failed load, preserve the artifact checksum, target environment, task code, object, request or process identifier, status, elapsed wait, and available process log; redact payload values and all credentials. Reconcile the outcome through the workflow-selected read-only status route before any newly approved action.
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. Benefit Reporting Groups precedes this task in the catalog dependency sequence. Track token usage for any generated project artifact or skill-run record using the manifest policy.