Benefit Reporting Groups Setup Task Guidance
Purpose
Guides the Manage Reporting Groups task, cataloged as Benefit Reporting Groups, using the requested benefitReportingGroups object and its child records.
Setup Task Skill Contract
- task_code:
BEN_MANAGE_BENEFIT_REPORTING_GROUPS - task_name:
Benefit Reporting Groups - 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:
benefitReportingGroups - source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Benefit Reporting Groups under Benefits General Configuration.
Child Object Scope
The requested record tree contains regulatoryBodies, its nested regulatoryPurposes, regulations, reportingGroupForProgramsOrPlans, and translations. Preserve all supplied rows and their parent-child relationships. Validate each supplied row independently. Current target-environment HDL metadata must confirm exact object and child section names, keys, date-effectivity, effectiveOf availability, and supported operations before a row control is derived or an artifact is built or loaded; the names in this request alone do not establish an executable HDL schema.
Read Order and Routing
- Read input validation for shape and presence checks.
- Read dependency readiness for metadata and Run Book gates, then reference lookups for the nine conditional field checks.
- Read defaulting rules, design enforcement, and error handling.
For every row in a section confirmed to expose
effectiveOf, derive it from that row's operation and serialize each embedded date asYYYY-MM-DD; reject invalid or ambiguous source dates. OmiteffectiveOfentirely from a section that does not expose it, includingtranslationsunless current metadata explicitly says otherwise. - Use the active project workflow and
core.fusion-api.rest-api-clientonly when it selects the read-only LOV step. Validate current HDL metadata and artifact shape throughcore.data-loaderbefore preview or submission. Require the active Run Book and the loader's approval workflow for a live load.
An HTTP 403 from a conditional LOV check produces unverified_forbidden for that field and does not throw a field-validation error. It does not establish that the value is valid. Retain that status in the validation result and resolve access or obtain another workflow-approved authoritative check before a live load.
Setup Task Metadata
- Task name:
Benefit Reporting Groups - Task code:
BEN_MANAGE_BENEFIT_REPORTING_GROUPS - Available:
Y - Export/import supported:
N - CSV export/import supported:
N - CSV export/import routing:
not supported - Data Loader import mode:
HDL - Business Object:
benefitReportingGroups
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.