# Benefits General Configuration Implementation Guidance

> Provides HCM Benefits Configuration implementation guidance for the Benefits General Configuration functional area.

- Skill: `oracle/benefits-general-configuration-implementation-guidance` (Agent Skill)
- Install (CLI): `npx get-skill add oracle/benefits-general-configuration-implementation-guidance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/benefits-general-configuration-implementation-guidance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/benefits-general-configuration-implementation-guidance

---


# Benefits General Configuration Implementation Guidance

## Purpose

Provides HCM Benefits Configuration implementation guidance for the Benefits General Configuration functional area.

## When to Use

Use this functional-area skill after Benefits Configuration scope is confirmed and the project needs benefits general configuration setup planning, baseline export, import sequencing, or validation checkpoints.

## Catalog Metadata

- Pillar: `HCM`
- Offering: `Benefits Configuration` (`ORA_BENEFITS_CONFIG`)
- Functional area / Setup Object: `Benefits General Configuration` (`ORA_BENEFITS_GENERAL_CONFIGURATION`)

## Setup Tasks

1. [Benefit Groups](benefit-groups/SKILL.md) (`BEN_MANAGE_BENEFIT_GROUPS`)
2. [Benefit Balances](benefit-balances/SKILL.md) (`BEN_MANAGE_BENEFIT_BALANCE`)
3. [Configure Benefits Feature Preferences](configure-benefits-feature-preferences/SKILL.md) (`ORA_CONFIGURE_FEATURE_PREFERENCES`)
4. [Enrollment Authorizations](enrollment-authorizations/SKILL.md) (`BEN_MANAGE_AUTHORIZATION`)
5. [Regulations](regulations/SKILL.md) (`BEN_MANAGE_REGULATIONS`)
6. [Benefit Self-Service Configuration](benefit-self-service-configuration/SKILL.md) (`BEN_MANAGE_GROUP_SPACE`)
7. [Year Periods and Billing Calendars](year-periods-and-billing-calendars/SKILL.md) (`BEN_MANAGE_PROGRAMS_PLAN_YEARS`)
8. [Manage Beneficiary Organizations](manage-beneficiary-organizations/SKILL.md) (`BEN_MANAGE_BENEFICIARY_ORGANIZATION`)
9. [Manage Third-Party Administrators](manage-third-party-administrators/SKILL.md) (`BEN_MANAGE_THIRD_PARTY_ADMINISTRATOR`)
10. [Manage Benefit Providers](manage-benefit-providers/SKILL.md) (`BEN_MANAGE_BENEFIT_PROVIDER_ORG`)
11. [Manage Regulatory Bodies](manage-regulatory-bodies/SKILL.md) (`BEN_MANAGE_REGULATORY_BODY`)
12. [Configure Default Benefits Relationships](configure-default-benefits-relationships/SKILL.md) (`BEN_MANAGE_LEGAL_ENTITY_INFORMATION`)
13. [Benefit Reporting Groups](benefit-reporting-groups/SKILL.md) (`BEN_MANAGE_BENEFIT_REPORTING_GROUPS`)

## Inputs

- `implementation_objective`
- `project_context`
- `benefits_general_configuration_scope`
- `benefits_general_configuration_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.

For a routed HDL task, confirm date-effectivity, `effectiveOf` availability, and
supported operations separately for every included DAT section using current
target-environment Data Loader metadata before deriving row controls. Where a
section exposes `effectiveOf`, derive it from each row's exact operation and
required date; serialize any embedded date as `YYYY-MM-DD`. Omit `effectiveOf`
from sections that do not expose it. Stop artifact preparation when a section's
date-effective contract is missing or ambiguous; do not infer it from another
section or from the task name. The task-local operation mapping remains the
authority for supported actions and required dates.

For Manage Beneficiary Organizations, follow the
[Organization HDL workflow](manage-beneficiary-organizations/SKILL.md) before
preparing input or requesting upload approval. The configured object is
`Organization`; existing tasks retain their own workflows.

For Manage Regulatory Bodies, follow the
[Organization HDL workflow](manage-regulatory-bodies/SKILL.md) before preparing
input or requesting upload approval. The configured object is `Organization`.

