Year Periods and Billing Calendars Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Year Periods and Billing Calendars under Benefits General Configuration.
Setup Task Skill Contract
- task_code:
BEN_MANAGE_PROGRAMS_PLAN_YEARS
- task_name:
Year Periods and Billing Calendars
- 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:
benefitYearPeriods
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Year Periods and Billing Calendars under Benefits General Configuration.
Setup Task Metadata
- Task name:
Year Periods and Billing Calendars
- Task code:
BEN_MANAGE_PROGRAMS_PLAN_YEARS
- Available:
Y
- Export/import supported:
N
- CSV export/import supported:
N
- CSV export/import routing:
not supported
- Data Loader import mode:
HDL
- Business Object:
benefitYearPeriods
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. For an HDL source whose registered top-level business object is benefitYearPeriods, route local validation, immutable preview, approval, upload, initiation, and diagnostics through core.data-loader. Do not replace this route with direct REST calls, browser entry, or another loader.
HDL Workflow
- Confirm the task code, target environment, requested operation, and
benefitYearPeriods object.
- Format every populated
StartDate, EndDate, LimitationYearStartDate, and LimitationYearEndDate as a valid calendar date in YYYY-MM-DD format before validation; reject ambiguous or invalid dates rather than silently converting them.
- Treat
PeriodType as a current-metadata foreign key. The live
benefitYearPeriods contract exposes PeriodTypeMeaning as its user-key
alternative. For each supplied PeriodTypeMeaning, use the read-only
reference lookup to require an exact
Meaning match from commonLookupsLOV with
LookupTypeFinder;LookupType=BEN_PERD_TYP. Use
core.fusion-api.rest-api-client only when the active project workflow
selects that lookup step. Preserve the supplied meaning and use the
metadata-supported key form. A 403 records unverified_forbidden without
failing field validation or stopping independent checks; it does not
verify the value. Resolve access or use another workflow-approved
authoritative check before live load. Do not load a display label such as
Calendar into PeriodType unless current metadata or lookup evidence
identifies it as the accepted key.
- Validate the exact source against current Data Loader metadata through
core.data-loader; the current contract requires RestAction and exposes EndDate, StartDate, and PeriodType as the primary user-key components. Do not infer HDL attributes, user keys, or supported operations.
- Save the validated immutable preview and task diagnostics in the project workspace when
project_id is supplied.
- Obtain the Data Loader workflow's approval for the exact artifact and target before any upload or initiation.
- After submission, use the Data Loader status and diagnostics workflow. Do not automatically retry an uncertain, failed, or timed-out live load.
Read the task-local ora-resource/ guidance before preview or live execution.
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
diagnostics
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.
1---2skill_id: "hcm.benefits-configuration.benefits-general-configuration.year-periods-and-billing-calendars"3name: year-periods-and-billing-calendars-setup-task-guidance4description: "Provides task-specific setup guidance for Year Periods and Billing Calendars under the Benefits General Configuration functional area."5layer: "pillar"6pillar: "HCM"7offering: "Benefits Configuration"8functional_area: "Benefits General Configuration"9functional_area_code: "ORA_BENEFITS_GENERAL_CONFIGURATION"10task_code: "BEN_MANAGE_PROGRAMS_PLAN_YEARS"11task_name: "Year Periods and Billing Calendars"12parent_skill_id: "hcm.benefits-configuration.benefits-general-configuration"13available_flag: "Y"14export_import_supported_flag: "N"15csv_export_import_supported_flag: "N"16dataloader_import_mode: "HDL"17businessObject: "benefitYearPeriods"18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "import"20execution_mode: "hybrid"21owner_team: "HCM benefits configuration pillar team"22version: "0.2.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28outputs:29 - "setup_task_plan"30 - "setup_data_routing"31 - "validation_checkpoints"32 - "diagnostics"33 - "skill_run_record"34 - "token_usage_record"35depends_on:36 - "core.data-loader"37 - "shared.validation.setup-data-validator"38uses_core:39 - "core.data-loader"40 - "core.fusion-api.rest-api-client"41 - "core.project-mgmt.artifact-version-manager"42 - "core.project-mgmt.artifact-registry-manager"43 - "core.project-mgmt.project-state-manager"44persists_project_state: true45token_usage_tracking:46 enabled: true47 granularity: "per_skill_run"48 artifact_type: "token_usage_record"49 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"50 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"51 required_fields:52 - "activity_start_time"53 - "skill_id"54 - "task"55 - "trigger"56 - "artifacts_written"57 - "files_read"58 - "estimated_input_tokens"59 - "estimated_output_tokens"60 - "estimated_total_tokens"61 - "estimation_method"62 - "notes"63state_updates:64 - "setup_task_sequence"65 - "configuration_blueprints"66 - "validation_results"67 - "reports"68 - "token_usage_records"69workspace_outputs:70 - artifact_type: "configuration_blueprint"71 default_location: "project/{project_id}/artifacts/pillars/hcm/benefits-configuration/benefits-general-configuration/year-periods-and-billing-calendars/current/"72 versioning_policy: "major-new-version-minor-confirm-update"73 - artifact_type: "validation_result"74 default_location: "project/{project_id}/artifacts/pillars/hcm/benefits-configuration/benefits-general-configuration/year-periods-and-billing-calendars/current/"75 versioning_policy: "major-new-version-minor-confirm-update"76 - artifact_type: "report"77 default_location: "project/{project_id}/artifacts/pillars/hcm/benefits-configuration/benefits-general-configuration/year-periods-and-billing-calendars/current/"78 versioning_policy: "major-new-version-minor-confirm-update"79 - artifact_type: "skill_run"80 default_location: "project/{project_id}/state/runs/"81 versioning_policy: "append-only"82 - artifact_type: "token_usage_record"83 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"84 versioning_policy: "append-only"85applicability:86 industries:87 - "All"88 countries:89 - "All"90 fusion_releases:91 - "Current Oracle Fusion Cloud release"92side_effects:93 - "Creates local validation, preview, and diagnostic artifacts."94 - "Reads selected-environment commonLookupsLOV when the active workflow authorizes PeriodTypeMeaning validation."95 - "An approved HDL import is uploaded and initiated only through core.data-loader."96required_privileges:97 - "Access to the target Fusion environment and privileges for the registered benefitYearPeriods Data Loader business object."98 - "Read access to selected-environment commonLookupsLOV for supplied PeriodTypeMeaning values."99metadata:100 source: https://skillmd.com/skills/oracle/year-periods-and-billing-calendars-setup-task-guidance101---102103# Year Periods and Billing Calendars Setup Task Guidance104105## Purpose106107Provides task-specific setup planning, routing, export, import, and validation guidance for `Year Periods and Billing Calendars` under `Benefits General Configuration`.108109## Setup Task Skill Contract110111- task_code: `BEN_MANAGE_PROGRAMS_PLAN_YEARS`112- task_name: `Year Periods and Billing Calendars`113- parent_skill_id: `hcm.benefits-configuration.benefits-general-configuration`114- pillar: `HCM`115- offering: `Benefits Configuration`116- functional_area: `Benefits General Configuration`117- functional_area_code: `ORA_BENEFITS_GENERAL_CONFIGURATION`118- available_flag: `Y`119- export_import_supported_flag: `N`120- csv_export_import_supported_flag: `N`121- dataloader_import_mode: `HDL`122- businessObject: `benefitYearPeriods`123- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`124125## Usage126127Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Year Periods and Billing Calendars` under `Benefits General Configuration`.128129## Setup Task Metadata130131- Task name: `Year Periods and Billing Calendars`132- Task code: `BEN_MANAGE_PROGRAMS_PLAN_YEARS`133- Available: `Y`134- Export/import supported: `N`135- CSV export/import supported: `N`136- CSV export/import routing: `not supported`137- Data Loader import mode: `HDL`138- Business Object: `benefitYearPeriods`139140## CSV Export, Import, and Validation Workflow141142`CSVExportImportSupportedFlag` is `N`, so this task is not marked as CSV export/import supported in the effective setup-task catalog.143144Do not route CSV export work to `shared.setup-export.task-level-export`. For an HDL source whose registered top-level business object is `benefitYearPeriods`, route local validation, immutable preview, approval, upload, initiation, and diagnostics through `core.data-loader`. Do not replace this route with direct REST calls, browser entry, or another loader.145146## HDL Workflow1471481. Confirm the task code, target environment, requested operation, and `benefitYearPeriods` object.1492. Format every populated `StartDate`, `EndDate`, `LimitationYearStartDate`, and `LimitationYearEndDate` as a valid calendar date in `YYYY-MM-DD` format before validation; reject ambiguous or invalid dates rather than silently converting them.1503. Treat `PeriodType` as a current-metadata foreign key. The live151 `benefitYearPeriods` contract exposes `PeriodTypeMeaning` as its user-key152 alternative. For each supplied `PeriodTypeMeaning`, use the read-only153 [reference lookup](ora-resource/ora_reference_lookups.md) to require an exact154 `Meaning` match from `commonLookupsLOV` with155 `LookupTypeFinder;LookupType=BEN_PERD_TYP`. Use156 `core.fusion-api.rest-api-client` only when the active project workflow157 selects that lookup step. Preserve the supplied meaning and use the158 metadata-supported key form. A 403 records `unverified_forbidden` without159 failing field validation or stopping independent checks; it does not160 verify the value. Resolve access or use another workflow-approved161 authoritative check before live load. Do not load a display label such as162 `Calendar` into `PeriodType` unless current metadata or lookup evidence163 identifies it as the accepted key.1644. Validate the exact source against current Data Loader metadata through `core.data-loader`; the current contract requires `RestAction` and exposes `EndDate`, `StartDate`, and `PeriodType` as the primary user-key components. Do not infer HDL attributes, user keys, or supported operations.1655. Save the validated immutable preview and task diagnostics in the project workspace when `project_id` is supplied.1666. Obtain the Data Loader workflow's approval for the exact artifact and target before any upload or initiation.1677. After submission, use the Data Loader status and diagnostics workflow. Do not automatically retry an uncertain, failed, or timed-out live load.168169Read the task-local `ora-resource/` guidance before preview or live execution.170171172173174## Inputs175176- `implementation_objective`177- `project_context`178- `setup_task_scope`179- `setup_data_artifacts`180181## Outputs182183- `setup_task_plan`184- `setup_data_routing`185- `validation_checkpoints`186- `diagnostics`187- `skill_run_record`188- `token_usage_record`189190## Implementation Notes191192Use 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.