Manage Third-Party Administrators Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Third-Party Administrators under Benefits General Configuration.
Setup Task Skill Contract
- task_code:
BEN_MANAGE_THIRD_PARTY_ADMINISTRATOR - task_name:
Manage Third-Party Administrators - 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 Third-Party Administrators under Benefits General Configuration.
Setup Task Metadata
- Task name:
Manage Third-Party Administrators - Task code:
BEN_MANAGE_THIRD_PARTY_ADMINISTRATOR - 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.
HDL workflow and validation
Read the task contract before intake, validation, preview, or submission. It owns the field checks, conditional requirements, identity rules, defaulting, failure classes, and recovery policy. Read its standards in this order: input validation, reference resolution, dependency readiness, defaulting, design enforcement, and error handling.
- Establish the operation, target environment, and task context. Collect the
organization name, effective start date, and either
LocationCodeplusLocationSetCode, or Task Location Name plus Location Set Name. Do not solicitClassificationCodeorClassificationName. - Use core.data-loader for live
schema validation and file preparation. Resolve references through the
shared REST client.
Resolve
ClassificationNamethroughorganizationClassificationsLOVusingClassificationCode='BEN TPA'; resolve name-based locations throughlocationsLoveffective on the organization start date. IncludeREST-Framework-Version: 9on both LOV requests. - Apply every contract preflight check to all rows. Block preview for missing or invalid fields, uncertain identity, unsupported operations, or unresolved dependencies. Do not report Task Hook automation as passed when task rules are not available.
- Follow core's immutable-artifact and Task Hook approval workflow. A prior upload approval does not authorize a new load. Never bypass core with a direct REST write.
- Report initiation separately from completion. When status monitoring is requested, use core's status and error queries until a terminal status or the contract observation deadline. Preserve partial successes.
The catalog CSV-support flag is not a ban on core's metadata-validated
spreadsheet-to-HDL conversion. Do not claim FSM export/import support from a
successful native HDL load. Native Organization source uses only the
Organization and OrgUnitClassification sections; exclude OrgInformation
from every generated DAT file. Use YYYY/MM/DD dates.
Failure handling and execution boundaries
Stop before upload on every blocking check. Corrected submissions need fresh validation and approval. Never automatically retry uncertain writes or roll back successful rows. For input, metadata, authentication, authorization, transport, API, timeout, process failure, persistence, or approval errors, record the environment, operation, stage, class, redacted message, artifact reference, and one safe next action. Core's retry and diagnostic policies are authoritative.
Keep source records, secrets, and test-environment data out of tracked files. For delegated Data Loader operations, core's report and persistence policies take precedence over generated planning-artifact defaults; do not create extra run records or token logs for a loader-only operation.
Verification and review
- Run offline contract tests.
- Exercise workflow scenarios with synthetic inputs and mocked results; they are manual, not proof of live validation.
- A fresh live upload requires separate authorization.