Benefits Rates Implementation Guidance
Purpose
Provides HCM Benefits Configuration implementation guidance for the Benefits Rates functional area.
When to Use
Use this functional-area skill after Benefits Configuration scope is confirmed and the project needs benefits rates setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
HCM
- Offering:
Benefits Configuration (ORA_BENEFITS_CONFIG)
- Functional area / Setup Object:
Benefits Rates (ORA_BENEFITS_RATES)
Setup Tasks
- Benefit Rates (
BEN_MANAGE_BENEFIT_RATES)
Inputs
implementation_objective
project_context
benefits_rates_scope
benefits_rates_requirements
Outputs
functional_area_setup_plan
configuration_guidance
validation_checkpoints
skill_run_record
token_usage_record
Implementation Notes
Use the generated setup-task metadata files for task-level planning and sequencing. Track token usage for any generated project artifact or skill-run record using the manifest policy.
HDL Scope and Sources
The selected task is BEN_MANAGE_BENEFIT_RATES; ORA_BENEFITS_RATES
is its functional-area code, not a loader discriminator. Read
the task metadata before routing a request.
The tested environment registers BenefitsStandardRate with ExtraInputValue
and VrpAssociation components. Oracle's overview uses the alternative names
BenefitStandardRate and ExtraInputValues; use the live registered names
for filenames and loader calls. Standard-rate maintenance includes create,
effective-dated update, correction, end dating, and deletion. A variable-rate
profile association is not creation of the referenced variable-rate profile.
Confirm each requested component and operation against target metadata.
Upload routing
Select the root from the requested object or source contents, not the task's
standard-rate default. If an unqualified rates request has no identifying
source, ask whether it concerns standard rates or variable-rate profiles.
| Requested object/component |
Registered root |
DAT filename |
| BenefitsStandardRate |
BenefitsStandardRate |
BenefitsStandardRate.dat |
| ExtraInputValue |
BenefitsStandardRate |
BenefitsStandardRate.dat |
| VariableRateProfile |
VariableRateProfile |
VariableRateProfile.dat |
| VrpAssociation |
BenefitsStandardRate |
BenefitsStandardRate.dat |
Live Data Loader metadata checked on 2026-09-24 confirmed the two roots and
both standard-rate children. This is registration/template evidence, not a
successful upload test or a guarantee for another environment. Resolve the
current target metadata on every new validation; never use fixed attribute
lists or counts as the schema.
VariableRateProfile is a separate root, not a BenefitsStandardRate child.
Resolve its own template, keys, and supported operations through core.
ExtraInputValue and VrpAssociation are child sections of the standard-rate
root. Do not route them as standalone BOs or create ExtraInputValue.dat or
VrpAssociation.dat. Preserve the exact singular component names.
- For child-only changes, resolve the existing parent and required references
using live supported keys. Do not fabricate a parent MERGE row or create a
rate, input value, formula, or profile merely to satisfy a missing reference.
Keep the root filename/container; let core validate the child-only structure.
For XLSX, follow core's root-sheet and child-sheet rules.
- When new profiles and dependent associations are requested together, plan
separate dependency-ordered loads. Load profiles first, then confirm their
successful completion through an explicitly requested status check before
submitting dependent associations. Do not assume ZIP member order guarantees
cross-root dependency processing or silently split a supplied archive.
- Preserve source bytes during review. A wrongly named child file requires a
user-reviewed correction through core, not a guessed standalone registration.
Source: Oracle: How You Manage Benefits Standard Rates Using HDL or HSDL,
reviewed 2026-09-23. The source distinguishes HDL from HSDL; their operation
support must not be treated as interchangeable.
The catalog's N export/import and CSV flags describe FSM setup-data support.
They do not negate the documented HDL route or authorize FSM CSV export.
Do not invent an export endpoint or an HDL schema from those catalog flags.
HDL Workflow
- Establish the requested action: sample, attribute details, validation,
load, or status. For maintenance, retain the user's distinction between
update, correction, end dating, and deletion; do not turn one into another.
Collect the target environment, rate identity, intended effective dates,
requested components, and source artifact when relevant. Use prior project
context where available.
- Read core.data-loader. Hand off
HCM context,
BEN_MANAGE_BENEFIT_RATES, import mode HDL, the documented
root selected from the upload routing table, requested components,
the requested operation, and the unchanged
source path or business values. Preserve any existing Run Book context.
- Let core.data-loader resolve the registered object and its current template,
component hierarchy, required attributes, keys, and supported operations.
Stop on missing or ambiguous registration. Do not substitute payroll
RateDefinition, assume a REST resource with the same name, or fabricate
DAT headers. Exact field and effective-date controls come from that metadata.
- For sample requests, use the core sample workflow: XLSX by default and DAT
only when explicitly requested. Retain its attribute-details and key-fields
companions. Preserve documented children and parent linkage; do not add
populated child records when the user has requested only a standard rate
or a variable-rate profile. For a child sample, select the standard-rate
root and identify the requested child; do not load unrelated sample rows.
Sample generation performs no load.
Create templates use placeholders, not existing rate values. For a request
to derive a new rate from environment data, first use the core read-only
update-sample route and require actual retrieved values. The tested
environment returns 404 for the loader's generated BenefitsStandardRate
FSCM read route. Until an authoritative supported read mapping or supplied
rate export is available, stop that cloning workflow; do not submit a
placeholder template or copy existing record identifiers into a create.
- For source validation or load requests, use the core validation workflow
for the selected HDL contract. Resolve the rate and child identities using
supported keys; report missing references or ambiguous mappings through
the core result. Do not create referenced setup objects as an implicit fix.
Validate the requested date treatment before preparing the immutable archive.
- For a load, let core.data-loader own source review, Task Hook validation,
approval, upload, and initiation. Follow its approval policy without adding
a second approval. Missing task resources follow the core Task Hook policy;
do not claim a custom Benefits rule registry has run. Never call a native
HDL service, import adapter, or UCM upload independently.
- Return the core result in its required Markdown format. Accepted initiation
is not completed import: retain the request ID and end the initiation turn.
Route a subsequent status or errors request through core.data-loader and
report returned counts and diagnostics, including partial failures.
Failure and Recovery
- Input validation or catalog mismatch: identify the missing operation,
ambiguous rate/object, unsupported component, or mismatched metadata and
stop before submission. Do not guess a replacement.
- Authentication, privileges, or transport failures: use the core diagnostic
and retry policy. Do not bypass it with another environment or credential.
- Failed or uncertain import: preserve the returned request ID and successful
records. Inspect status/errors through core on request before considering a
retry; never blindly resubmit a possibly accepted load.
- Corrected data requires a new validation and approval cycle under core's
policy. Do not delete rates to simulate rollback.
- If a selected core operation times out, report its last status and next-check
path; do not invent a completed outcome or an extra polling loop.
Runtime access and load privileges are checked by core.data-loader for the
chosen environment. Keep credentials and business data out of repository files.
The pillar owns durable planning decisions and the manifest's project outputs;
the loader owns its artifact and result contract. Reuse its returned evidence
when recording project results rather than creating duplicate loader logs.
Review and Verification
Reviewers: HCM Benefits Pillar Lead or SME and FSCR A-Team/core reviewer.
Use the synthetic workflow scenarios to review
routing and failure behavior. Schema and catalog validation are offline checks;
live registration, supported field controls, privileges, and successful imports
must be verified in the selected environment at execution time.
1---2skill_id: "hcm.benefits-configuration.benefits-rates"3name: benefits-rates-implementation-guidance4description: "Routes BenefitsStandardRate and VariableRateProfile HDL uploads, including ExtraInputValue and VrpAssociation child components, plus samples, validation, and results through core.data-loader for ORA_BENEFITS_RATES."5layer: "pillar"6pillar: "HCM"7offering: "Benefits Configuration"8functional_area: "Benefits Rates"9functional_area_code: "ORA_BENEFITS_RATES"10type: "planning"11execution_mode: "assisted"12owner_team: "HCM benefits configuration pillar team"13version: "0.2.0"14inputs:15 - "implementation_objective"16 - "project_context"17 - "benefits_rates_scope"18 - "benefits_rates_requirements"19outputs:20 - "functional_area_setup_plan"21 - "configuration_guidance"22 - "validation_checkpoints"23 - "skill_run_record"24 - "token_usage_record"25depends_on:26 - "shared.implementation-planning.offering-task-map-builder"27 - "shared.implementation-planning.task-dependency-resolver"28uses_core:29 - "core.data-loader"30 - "core.project-mgmt.artifact-version-manager"31 - "core.project-mgmt.artifact-registry-manager"32 - "core.project-mgmt.project-state-manager"33 - "core.diagnostics.role-access-check"34persists_project_state: true35token_usage_tracking:36 enabled: true37 granularity: "per_skill_run"38 artifact_type: "token_usage_record"39 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"40 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"41 required_fields:42 - "activity_start_time"43 - "skill_id"44 - "task"45 - "trigger"46 - "artifacts_written"47 - "files_read"48 - "estimated_input_tokens"49 - "estimated_output_tokens"50 - "estimated_total_tokens"51 - "estimation_method"52 - "notes"53state_updates:54 - "setup_task_sequence"55 - "design_decisions"56 - "configuration_blueprints"57 - "validation_results"58 - "token_usage_records"59workspace_outputs:60 - artifact_type: "setup_task_sequence"61 default_location: "project/{project_id}/artifacts/pillars/hcm/benefits-configuration/benefits-rates/current/"62 versioning_policy: "major-new-version-minor-confirm-update"63 - artifact_type: "configuration_blueprint"64 default_location: "project/{project_id}/artifacts/pillars/hcm/benefits-configuration/benefits-rates/current/"65 versioning_policy: "major-new-version-minor-confirm-update"66 - artifact_type: "design_decision"67 default_location: "project/{project_id}/decisions/"68 versioning_policy: "append-only"69 - artifact_type: "validation_result"70 default_location: "project/{project_id}/artifacts/pillars/hcm/benefits-configuration/benefits-rates/current/"71 versioning_policy: "major-new-version-minor-confirm-update"72 - artifact_type: "skill_run"73 default_location: "project/{project_id}/state/runs/"74 versioning_policy: "append-only"75 - artifact_type: "token_usage_record"76 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"77 versioning_policy: "append-only"78required_setup_tasks:79 - "BEN_MANAGE_BENEFIT_RATES"80applicability:81 industries:82 - "All"83 countries:84 - "All"85 fusion_releases:86 - "Current Oracle Fusion Cloud release"87side_effects: []88required_privileges: []89metadata:90 source: https://skillmd.com/skills/oracle/benefits-rates-implementation-guidance91---9293# Benefits Rates Implementation Guidance9495## Purpose9697Provides HCM Benefits Configuration implementation guidance for the Benefits Rates functional area.9899## When to Use100101Use this functional-area skill after Benefits Configuration scope is confirmed and the project needs benefits rates setup planning, baseline export, import sequencing, or validation checkpoints.102103## Catalog Metadata104105- Pillar: `HCM`106- Offering: `Benefits Configuration` (`ORA_BENEFITS_CONFIG`)107- Functional area / Setup Object: `Benefits Rates` (`ORA_BENEFITS_RATES`)108109## Setup Tasks1101111. [Benefit Rates](benefit-rates.md) (`BEN_MANAGE_BENEFIT_RATES`)112113## Inputs114115- `implementation_objective`116- `project_context`117- `benefits_rates_scope`118- `benefits_rates_requirements`119120## Outputs121122- `functional_area_setup_plan`123- `configuration_guidance`124- `validation_checkpoints`125- `skill_run_record`126- `token_usage_record`127128## Implementation Notes129130Use the generated setup-task metadata files for task-level planning and sequencing. Track token usage for any generated project artifact or skill-run record using the manifest policy.131132## HDL Scope and Sources133134The selected task is `BEN_MANAGE_BENEFIT_RATES`; `ORA_BENEFITS_RATES`135is its functional-area code, not a loader discriminator. Read136[the task metadata](benefit-rates.md) before routing a request.137138The tested environment registers `BenefitsStandardRate` with `ExtraInputValue`139and `VrpAssociation` components. Oracle's overview uses the alternative names140`BenefitStandardRate` and `ExtraInputValues`; use the live registered names141for filenames and loader calls. Standard-rate maintenance includes create,142effective-dated update, correction, end dating, and deletion. A variable-rate143profile association is not creation of the referenced variable-rate profile.144Confirm each requested component and operation against target metadata.145146### Upload routing147148Select the root from the requested object or source contents, not the task's149standard-rate default. If an unqualified rates request has no identifying150source, ask whether it concerns standard rates or variable-rate profiles.151152| Requested object/component | Registered root | DAT filename |153|---|---|---|154| BenefitsStandardRate | BenefitsStandardRate | BenefitsStandardRate.dat |155| ExtraInputValue | BenefitsStandardRate | BenefitsStandardRate.dat |156| VariableRateProfile | VariableRateProfile | VariableRateProfile.dat |157| VrpAssociation | BenefitsStandardRate | BenefitsStandardRate.dat |158159Live Data Loader metadata checked on 2026-09-24 confirmed the two roots and160both standard-rate children. This is registration/template evidence, not a161successful upload test or a guarantee for another environment. Resolve the162current target metadata on every new validation; never use fixed attribute163lists or counts as the schema.164165- `VariableRateProfile` is a separate root, not a `BenefitsStandardRate` child.166 Resolve its own template, keys, and supported operations through core.167- `ExtraInputValue` and `VrpAssociation` are child sections of the standard-rate168 root. Do not route them as standalone BOs or create `ExtraInputValue.dat` or169 `VrpAssociation.dat`. Preserve the exact singular component names.170- For child-only changes, resolve the existing parent and required references171 using live supported keys. Do not fabricate a parent MERGE row or create a172 rate, input value, formula, or profile merely to satisfy a missing reference.173 Keep the root filename/container; let core validate the child-only structure.174 For XLSX, follow core's root-sheet and child-sheet rules.175- When new profiles and dependent associations are requested together, plan176 separate dependency-ordered loads. Load profiles first, then confirm their177 successful completion through an explicitly requested status check before178 submitting dependent associations. Do not assume ZIP member order guarantees179 cross-root dependency processing or silently split a supplied archive.180- Preserve source bytes during review. A wrongly named child file requires a181 user-reviewed correction through core, not a guessed standalone registration.182183Source: [Oracle: How You Manage Benefits Standard Rates Using HDL or HSDL](https://docs.oracle.com/en/cloud/saas/human-resources/faibf/how-you-manage-benefits-standard-rates-using-hdl-or-hsdl.html),184reviewed 2026-09-23. The source distinguishes HDL from HSDL; their operation185support must not be treated as interchangeable.186187The catalog's `N` export/import and CSV flags describe FSM setup-data support.188They do not negate the documented HDL route or authorize FSM CSV export.189Do not invent an export endpoint or an HDL schema from those catalog flags.190191## HDL Workflow1921931. Establish the requested action: sample, attribute details, validation,194 load, or status. For maintenance, retain the user's distinction between195 update, correction, end dating, and deletion; do not turn one into another.196 Collect the target environment, rate identity, intended effective dates,197 requested components, and source artifact when relevant. Use prior project198 context where available.1992. Read [core.data-loader](../../../../core/data-loader/SKILL.md). Hand off200 HCM context, `BEN_MANAGE_BENEFIT_RATES`, import mode `HDL`, the documented201 root selected from the upload routing table, requested components,202 the requested operation, and the unchanged203 source path or business values. Preserve any existing Run Book context.2043. Let core.data-loader resolve the registered object and its current template,205 component hierarchy, required attributes, keys, and supported operations.206 Stop on missing or ambiguous registration. Do not substitute payroll207 `RateDefinition`, assume a REST resource with the same name, or fabricate208 DAT headers. Exact field and effective-date controls come from that metadata.2094. For sample requests, use the core sample workflow: XLSX by default and DAT210 only when explicitly requested. Retain its attribute-details and key-fields211 companions. Preserve documented children and parent linkage; do not add212 populated child records when the user has requested only a standard rate213 or a variable-rate profile. For a child sample, select the standard-rate214 root and identify the requested child; do not load unrelated sample rows.215 Sample generation performs no load.216 Create templates use placeholders, not existing rate values. For a request217 to derive a new rate from environment data, first use the core read-only218 update-sample route and require actual retrieved values. The tested219 environment returns 404 for the loader's generated BenefitsStandardRate220 FSCM read route. Until an authoritative supported read mapping or supplied221 rate export is available, stop that cloning workflow; do not submit a222 placeholder template or copy existing record identifiers into a create.2235. For source validation or load requests, use the core validation workflow224 for the selected HDL contract. Resolve the rate and child identities using225 supported keys; report missing references or ambiguous mappings through226 the core result. Do not create referenced setup objects as an implicit fix.227 Validate the requested date treatment before preparing the immutable archive.2286. For a load, let core.data-loader own source review, Task Hook validation,229 approval, upload, and initiation. Follow its approval policy without adding230 a second approval. Missing task resources follow the core Task Hook policy;231 do not claim a custom Benefits rule registry has run. Never call a native232 HDL service, import adapter, or UCM upload independently.2337. Return the core result in its required Markdown format. Accepted initiation234 is not completed import: retain the request ID and end the initiation turn.235 Route a subsequent status or errors request through core.data-loader and236 report returned counts and diagnostics, including partial failures.237238## Failure and Recovery239240- Input validation or catalog mismatch: identify the missing operation,241 ambiguous rate/object, unsupported component, or mismatched metadata and242 stop before submission. Do not guess a replacement.243- Authentication, privileges, or transport failures: use the core diagnostic244 and retry policy. Do not bypass it with another environment or credential.245- Failed or uncertain import: preserve the returned request ID and successful246 records. Inspect status/errors through core on request before considering a247 retry; never blindly resubmit a possibly accepted load.248- Corrected data requires a new validation and approval cycle under core's249 policy. Do not delete rates to simulate rollback.250- If a selected core operation times out, report its last status and next-check251 path; do not invent a completed outcome or an extra polling loop.252253Runtime access and load privileges are checked by core.data-loader for the254chosen environment. Keep credentials and business data out of repository files.255The pillar owns durable planning decisions and the manifest's project outputs;256the loader owns its artifact and result contract. Reuse its returned evidence257when recording project results rather than creating duplicate loader logs.258259## Review and Verification260261Reviewers: HCM Benefits Pillar Lead or SME and FSCR A-Team/core reviewer.262Use [the synthetic workflow scenarios](tests/golden-scenarios.md) to review263routing and failure behavior. Schema and catalog validation are offline checks;264live registration, supported field controls, privileges, and successful imports265must be verified in the selected environment at execution time.