# Manage Benefit Providers Setup Task Guidance

> Provides task-specific setup guidance for Manage Benefit Providers under the Benefits General Configuration functional area.

- Skill: `oracle/manage-benefit-providers-setup-task-guidance` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx get-skill add oracle/manage-benefit-providers-setup-task-guidance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/manage-benefit-providers-setup-task-guidance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/manage-benefit-providers-setup-task-guidance

---


# 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_objective`
- `project_context`
- `setup_task_scope`
- `setup_data_artifacts`

## Outputs

- `setup_task_plan`
- `setup_data_routing`
- `validation_checkpoints`
- `skill_run_record`
- `token_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](ora-resource/ora_input_validation.md), [reference
resolution](ora-resource/ora_reference_lookups.md), [dependency
readiness](ora-resource/ora_dependency_readiness.md),
[defaulting](ora-resource/ora_defaulting_rules.md), [design
enforcement](ora-resource/ora_design_enforcement.md), and [error
handling](ora-resource/ora_error_handling.md).

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.

