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
- Benefit Groups (
BEN_MANAGE_BENEFIT_GROUPS) - Benefit Balances (
BEN_MANAGE_BENEFIT_BALANCE) - Configure Benefits Feature Preferences (
ORA_CONFIGURE_FEATURE_PREFERENCES) - Enrollment Authorizations (
BEN_MANAGE_AUTHORIZATION) - Regulations (
BEN_MANAGE_REGULATIONS) - Benefit Self-Service Configuration (
BEN_MANAGE_GROUP_SPACE) - Year Periods and Billing Calendars (
BEN_MANAGE_PROGRAMS_PLAN_YEARS) - Manage Beneficiary Organizations (
BEN_MANAGE_BENEFICIARY_ORGANIZATION) - Manage Third-Party Administrators (
BEN_MANAGE_THIRD_PARTY_ADMINISTRATOR) - Manage Benefit Providers (
BEN_MANAGE_BENEFIT_PROVIDER_ORG) - Manage Regulatory Bodies (
BEN_MANAGE_REGULATORY_BODY) - Configure Default Benefits Relationships (
BEN_MANAGE_LEGAL_ENTITY_INFORMATION) - Benefit Reporting Groups (
BEN_MANAGE_BENEFIT_REPORTING_GROUPS)
Inputs
implementation_objectiveproject_contextbenefits_general_configuration_scopebenefits_general_configuration_requirements
Outputs
functional_area_setup_planconfiguration_guidancevalidation_checkpointsskill_run_recordtoken_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 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 before preparing
input or requesting upload approval. The configured object is Organization.