Manage Benefit Providers Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Benefit Providers under Benefits General Configuration.
Setup Task Skill Contract
- task_code:
BEN_MANAGE_BENEFIT_PROVIDER_ORG - task_name:
Manage Benefit Providers - 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:
Organization - source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Benefit Providers under Benefits General Configuration.
Setup Task Metadata
- Task name:
Manage Benefit Providers - Task code:
BEN_MANAGE_BENEFIT_PROVIDER_ORG - Available:
Y - Export/import supported:
N - CSV export/import supported:
N - CSV export/import routing:
not supported - Data Loader import mode:
HDL - Business Object:
Organization
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.
Organization HDL workflow
Use Organization and operation-required OrgUnitClassification only; exclude
OrgInformation. Validate through core.data-loader before every preview or
upload. Do not accept ClassificationCode or ClassificationName as user input.
Resolve exactly one ClassificationName with
GET /hcmRestApi/resources/latest/organizationClassificationsLOV?q=ClassificationCode='BEN'
and REST-Framework-Version: 9; populate that returned name in both rows and
leave ClassificationCode blank. Use the standards in this order: input
validation, reference
resolution, dependency
readiness,
defaulting, design
enforcement, and error
handling.
Use an explicit complete LocationCode/LocationSetCode pair as-is; otherwise,
resolve exactly matching LocationName and SetName through locationsLov at the
effective start date with REST-Framework-Version: 9, mapping LocationCode and
SetCode. Reject partial, ambiguous, or unmatched location inputs. Default
omitted OrgUnitClassification Status to A. Use YYYY/MM/DD dates. Bind every
load to core's immutable-artifact and fresh-approval workflow; never retry a
mutation automatically.