Manage Accounting Calendars Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, import, and validation guidance for Manage Accounting Calendars under Financial Reporting Structures.
Setup Task Skill Contract
- task_code:
GL_MANAGE_ACCOUNTING_CALENDARS
- task_name:
Manage Accounting Calendars
- parent_skill_id:
erp.financials.financial-reporting-structures
- pillar:
ERP
- offering:
Financials
- functional_area:
Financial Reporting Structures
- functional_area_code:
ORA_ASK_FIN_REPORTING_STRUCT
- available_flag:
Y
- export_import_supported_flag:
Y
- csv_export_import_supported_flag:
Y
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, importing, or validating setup data for Manage Accounting Calendars under Financial Reporting Structures.
Definition Source Boundary
For a project's first accounting-calendar run, obtain the same-environment,
same-release task template through the approved template-only route owned by
shared.setup-export.task-level-export. Validate the template package and
persist its metadata XML, member names, headers, column order, task identity,
environment, release, and fingerprint as that project's reusable technical
baseline. A later run for the same project may reuse the baseline only while
those compatibility checks still pass; otherwise obtain and persist a fresh
template-only package before authoring.
For calendar creation, derive the package definition only from that validated template baseline,
documented calendar rules, and the requested calendar definition. A
template-only fetch is not a Data Only Export: it must use
setupTaskCSVTemplateExports, never setupTaskCSVExports, and must contain no
current setup rows. Do not copy attribute values, period rows, naming choices,
or defaults from exported setup data or an existing calendar. Read-only
exact-name lookup is permitted solely to prevent a duplicate; it is not a
definition source.
Never request, initiate, or depend on an FSM Data Only Export for calendar
creation, general lookup, or failed-import troubleshooting. A permitted
existing-calendar update has one narrow exception for obtaining the complete
current parent carrier that Fusion requires:
- Reuse the final FSCR-authored calendar package only when the calendar was
created successfully in the current project/session and the retained package,
successful load result, and post-load verification prove the exact task,
environment, release,
UserPeriodSetName, PeriodSetName, complete parent
header, and current period rows. Treat any later external change or missing
evidence as making this source unusable.
- Otherwise automatically run one full current-data task export through
shared.setup-export.task-level-export and setupTaskCSVExports as read-only
update preflight. Do not ask for separate export approval; authentication may
still pause for login. Do not use export criteria for this task because the
tested calendar-name criteria were ignored by Fusion.
- From that package, require exactly one
GL_PERIOD_SET.csv row whose
UserPeriodSetName and PeriodSetName match the identity resolved through
accountingCalendarsLOV, and retain only that calendar's child rows as update
evidence. If the exact target is absent, duplicated, ambiguous, or linked to
inconsistent child rows, stop. Never substitute a similar calendar or derive
defaults from unrelated exported rows.
Use current-data export values only to preserve and validate the exact existing
calendar in the requested update. They are not defaults for creation or another
calendar. Data Loader/FSM import remains the authoritative final product
validation, and an import failure is not a reason to run another Data Only
Export.
Treat deletion as unsupported. Existing-calendar updates use the controlled
update path below; never convert one into a duplicate create or a generic FSM
submission attempt. The permitted update scope is deliberately narrow:
- The description may be edited only by an FSM package submitted through the
mandatory Data Loader workflow after exact identity resolution. Both the
display name (
UserPeriodSetName) and PeriodSetName are immutable; do not
rename a calendar or rewrite child-row parent keys.
- A period-name format may change only while adding a new fiscal year. Select
only a format allowed for the calendar frequency, generate the added year's
rows using that format, and leave every existing/historical period row, name,
date, and boundary unchanged. Before generating the added year, verify that
the complete existing calendar has its expected rows, continuous standard
dates, sequential numbering, valid quarters and adjustments, reconciled
counts, and a complete immediately preceding fiscal year. The added year
therefore has the newly requested format while prior years retain their
prior format.
- An existing period's supported FSM/Data Loader fields are
PeriodNum,
QuarterNum, StartDate, EndDate, and AdjustmentPeriodFlag. Every
changed row is affected and must be eligible. Block an existing-period name
change through this task's FSM CSV route: PeriodName is the matching key
and changing it causes Fusion to treat the row as a new period, while an
EnteredPeriodName-only change does not update the displayed period name.
Do not use a period-name prefix/header value as a workaround for existing
rows.
When associated ledgers exist, prove Never Opened (ClosingStatus=N)
across every ledger and every returned application-specific status row.
A per-ledger accountingPeriodStatusLOV response normally contains the
ledger's full period history; this is not a blocker and requires no user
follow-up. Retrieve every page, then automatically project the response onto
the immutable affected PeriodNameId set, retain every matching
ApplicationId row, and build the affected-period x associated-ledger
coverage matrix. Ignore unrelated history rows. Use the original composite
period identity only to cross-check the ID match, or as an exact fallback
when PeriodNameId is unavailable; never use fuzzy name or date matching.
Call this LOV with the cached OAuth bearer token and
REST-Framework-Version: 9. A convenience-client call that returns no
captured HTTP status or response body is a transport/client failure, not an
empty result; retry the explicit GET with that header before blocking.
For each successfully completed per-ledger query, matching rows must all be
N. If the complete response has no matching row for an affected period--or
no rows for that ledger at all--record NO_STATUS_INSTANTIATED for that
ledger/period and allow it to pass without synthesizing an N row. This rule
applies independently per ledger, so one empty ledger result may coexist with
other ledgers whose matching rows are all N.
Continue directly from successful retrieval through reduction and eligibility
evaluation without asking the user to request another check or isolate rows.
When a complete exact ledgersLOV query
proves that the calendar has zero associated ledgers, query
accountingPeriodStatusLOV directly for every affected period using its
original name, year, number, and dates; resolve every returned LedgerId, and
require that no returned status belongs to the target calendar. This
zero-ledger/no-status branch is eligible because no ledger/application period
status is instantiated for the calendar; an empty result is not mislabeled as
N. Repeat the applicable complete check immediately before submission.
Treat an inaccessible/truncated page, ambiguous identity, a target-calendar non-N
row, or an evidence change as a blocker. Persist pagination receipts and the
compact filtered matrix with period, ledger, application, status, dates, and
retrieval time. A date change that requires
an adjacent period boundary change makes that adjacent period affected and
subject to the same rule.
Preserve the original PeriodNameId in eligibility evidence. Preserve
PeriodName, EnteredPeriodName, PeriodYear, calendar identity, frequencies, header
counts, and header dates. Period numbers and quarters must still start and
progress according to the calendar rules; adjustment-flag changes must retain
the existing adjustment policy and reconciled counts. If the requested edit
cannot preserve full-calendar continuity, uniqueness, numbering, quarter
assignment, adjustment geometry, and those protected fields, stop. Treat the
UI Additional Information region as DFF data, not a core calendar field; edit
it only through a separately validated context/segment contract.
Changes to an existing calendar's start date, non-adjusting frequency,
adjustment policy, UserPeriodSetName, PeriodSetName, parent linkage, or
any period field outside the conditionally permitted UI-editable core fields
remain blocked. Require an explicit update approval before any permitted
existing-calendar update.
Budgetary-control-only calendars are a separate mode. They use the
budgetary-control calendar type, OTHER frequency, an explicit number of
budget periods, no user-selectable adjustment policy, and the budget-period
naming generated by the approved template. Do not apply normal accounting
calendar frequency, adjustment, or naming defaults to this mode.
Weekly (WEEK) is the finest-grain supported standard calendar frequency.
Reject Daily or any finer-grain generated or manual calendar design, including
an attempt to express daily periods through OTHER.
Read Order
- Read
ora-resource/ora_input_intake.md.
- Read
ora-resource/ora_input_validation.md.
- Read
ora-resource/ora_dependency_readiness.md.
- Read
ora-resource/ora_reference_lookups.md.
- Read
ora-resource/ora_defaulting_rules.md.
- Read
ora-resource/ora_design_advisory.md.
- Read
ora-resource/ora_design_enforcement.md.
- Read
ora-resource/ora_bulk_intake.md.
- Read
ora-resource/ora_rest_execution.md.
- Read
ora-resource/ora_error_handling.md.
Setup Task Metadata
- Task name:
Manage Accounting Calendars
- Task code:
GL_MANAGE_ACCOUNTING_CALENDARS
- Available:
Y
- Export/import supported:
Y
- CSV export/import supported:
Y
- CSV export/import routing:
supported
Template Acquisition, Import, and Validation Workflow
The catalog's CSVExportImportSupportedFlag remains Y. Creation uses only the
template route; a permitted update may use the controlled current-value source
rule above. Route acquisition, package validation, and import through:
- On the project's first run, or when its persisted template baseline is
incompatible, automatically fetch the header-only task template with
shared.setup-export.task-level-export in template-only mode. Treat this as
normal non-business-data preflight under the user's calendar request; do not
ask for a separate conversational approval. Authentication may still pause
for user login when the token is stale.
- Validate setup task data with
shared.validation.setup-data-validator.
- Validate reference data with
shared.validation.reference-data-validator.
- Import setup task data with
core.data-loader.
For a permitted update, resolve its complete current parent and period baseline
before step 2: reuse the verified current-session FSCR creation package when
eligible; otherwise automatically obtain one full task data export and isolate
the exact target. The full export is required for description-only updates,
period-name-format changes that add a fiscal year, and eligible existing-period
field edits whenever the verified current-session source is unavailable.
core.data-loader is the mandatory execution owner for every calendar import.
It must perform the task validation, immutable-preview, approval, and submission
workflow for the FSM ZIP, including the adapter handoff and invocation.
shared.setup-import.task-level-import may be used only as the Data
Loader-invoked FSM adapter; never call that adapter directly after a chat
approval, a locally approved preview, or a Data Loader authorization record.
Use this task metadata when invoking those skills:
- Offering:
Financials
- Functional area / Setup Object:
Financial Reporting Structures
- Setup task name:
Manage Accounting Calendars
- Setup task code:
GL_MANAGE_ACCOUNTING_CALENDARS
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 erp.financials.financial-reporting-structures for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Runtime Verification and Result Reporting
- Never access Fusion setup UI for discovery, duplicate checks, validation or verification, including through delegates or user-supplied screenshots. Use the declared endpoints and FSCR framework; authentication through core.auth is the sole user-completed browser handoff. Follow endpoint-only verification.
- Inspect the actual matching process logs before reporting any submitted import as successful or failed. For lookups or pre-submission checks, inspect their actual response or diagnostics. Follow result reporting.
1---2skill_id: "erp.financials.financial-reporting-structures.manage-accounting-calendars"3name: manage-accounting-calendars-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Accounting Calendars under the Financial Reporting Structures functional area."5layer: "pillar"6pillar: "ERP"7offering: "Financials"8functional_area: "Financial Reporting Structures"9functional_area_code: "ORA_ASK_FIN_REPORTING_STRUCT"10task_code: "GL_MANAGE_ACCOUNTING_CALENDARS"11task_name: "Manage Accounting Calendars"12parent_skill_id: "erp.financials.financial-reporting-structures"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"17type: "planning"18execution_mode: "assisted"19owner_team: "ERP financials pillar team"20version: "0.1.0"21inputs:22 - "implementation_objective"23 - "project_context"24 - "setup_task_scope"25 - "setup_data_artifacts"26outputs:27 - "setup_task_plan"28 - "setup_data_routing"29 - "validation_checkpoints"30 - "skill_run_record"31 - "token_usage_record"32depends_on:33 - "shared.setup-export.task-level-export"34 - "shared.validation.setup-data-validator"35 - "shared.validation.reference-data-validator"36 - "core.data-loader"37uses_core:38 - "core.project-mgmt.artifact-version-manager"39 - "core.project-mgmt.artifact-registry-manager"40 - "core.project-mgmt.project-state-manager"41persists_project_state: true42token_usage_tracking:43 enabled: true44 granularity: "per_skill_run"45 artifact_type: "token_usage_record"46 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"47 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"48 required_fields:49 - "activity_start_time"50 - "skill_id"51 - "task"52 - "trigger"53 - "artifacts_written"54 - "files_read"55 - "estimated_input_tokens"56 - "estimated_output_tokens"57 - "estimated_total_tokens"58 - "estimation_method"59 - "notes"60state_updates:61 - "setup_task_sequence"62 - "configuration_blueprints"63 - "validation_results"64 - "token_usage_records"65workspace_outputs:66 - artifact_type: "configuration_blueprint"67 default_location: "project/{project_id}/artifacts/pillars/erp/financials/financial-reporting-structures/manage-accounting-calendars/current/"68 versioning_policy: "major-new-version-minor-confirm-update"69 - artifact_type: "validation_result"70 default_location: "project/{project_id}/artifacts/pillars/erp/financials/financial-reporting-structures/manage-accounting-calendars/current/"71 versioning_policy: "major-new-version-minor-confirm-update"72 - artifact_type: "skill_run"73 default_location: "project/{project_id}/state/runs/"74 versioning_policy: "append-only"75 - artifact_type: "token_usage_record"76 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"77 versioning_policy: "append-only"78applicability:79 industries:80 - "All"81 countries:82 - "All"83 fusion_releases:84 - "Current Oracle Fusion Cloud release"85side_effects: []86required_privileges: []87metadata:88 source: https://skillmd.com/skills/oracle/manage-accounting-calendars-setup-task-guidance89---9091# Manage Accounting Calendars Setup Task Guidance9293## Purpose9495Provides task-specific setup planning, routing, import, and validation guidance for `Manage Accounting Calendars` under `Financial Reporting Structures`.9697## Setup Task Skill Contract9899- task_code: `GL_MANAGE_ACCOUNTING_CALENDARS`100- task_name: `Manage Accounting Calendars`101- parent_skill_id: `erp.financials.financial-reporting-structures`102- pillar: `ERP`103- offering: `Financials`104- functional_area: `Financial Reporting Structures`105- functional_area_code: `ORA_ASK_FIN_REPORTING_STRUCT`106- available_flag: `Y`107- export_import_supported_flag: `Y`108- csv_export_import_supported_flag: `Y`109- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`110111## Usage112113Use this skill when planning, sequencing, importing, or validating setup data for `Manage Accounting Calendars` under `Financial Reporting Structures`.114115## Definition Source Boundary116117For a project's first accounting-calendar run, obtain the same-environment,118same-release task template through the approved **template-only** route owned by119`shared.setup-export.task-level-export`. Validate the template package and120persist its metadata XML, member names, headers, column order, task identity,121environment, release, and fingerprint as that project's reusable technical122baseline. A later run for the same project may reuse the baseline only while123those compatibility checks still pass; otherwise obtain and persist a fresh124template-only package before authoring.125126For calendar creation, derive the package definition only from that validated template baseline,127documented calendar rules, and the requested calendar definition. A128template-only fetch is not a Data Only Export: it must use129`setupTaskCSVTemplateExports`, never `setupTaskCSVExports`, and must contain no130current setup rows. Do not copy attribute values, period rows, naming choices,131or defaults from exported setup data or an existing calendar. Read-only132exact-name lookup is permitted solely to prevent a duplicate; it is not a133definition source.134135Never request, initiate, or depend on an FSM **Data Only Export** for calendar136creation, general lookup, or failed-import troubleshooting. A permitted137existing-calendar update has one narrow exception for obtaining the complete138current parent carrier that Fusion requires:1391401. Reuse the final FSCR-authored calendar package only when the calendar was141 created successfully in the current project/session and the retained package,142 successful load result, and post-load verification prove the exact task,143 environment, release, `UserPeriodSetName`, `PeriodSetName`, complete parent144 header, and current period rows. Treat any later external change or missing145 evidence as making this source unusable.1462. Otherwise automatically run one full current-data task export through147 `shared.setup-export.task-level-export` and `setupTaskCSVExports` as read-only148 update preflight. Do not ask for separate export approval; authentication may149 still pause for login. Do not use export criteria for this task because the150 tested calendar-name criteria were ignored by Fusion.1513. From that package, require exactly one `GL_PERIOD_SET.csv` row whose152 `UserPeriodSetName` and `PeriodSetName` match the identity resolved through153 `accountingCalendarsLOV`, and retain only that calendar's child rows as update154 evidence. If the exact target is absent, duplicated, ambiguous, or linked to155 inconsistent child rows, stop. Never substitute a similar calendar or derive156 defaults from unrelated exported rows.157158Use current-data export values only to preserve and validate the exact existing159calendar in the requested update. They are not defaults for creation or another160calendar. Data Loader/FSM import remains the authoritative final product161validation, and an import failure is not a reason to run another Data Only162Export.163164Treat deletion as unsupported. Existing-calendar updates use the controlled165update path below; never convert one into a duplicate create or a generic FSM166submission attempt. The permitted update scope is deliberately narrow:167168- The description may be edited only by an FSM package submitted through the169 mandatory Data Loader workflow after exact identity resolution. Both the170 display name (`UserPeriodSetName`) and `PeriodSetName` are immutable; do not171 rename a calendar or rewrite child-row parent keys.172- A period-name format may change only while adding a new fiscal year. Select173 only a format allowed for the calendar frequency, generate the added year's174 rows using that format, and leave every existing/historical period row, name,175 date, and boundary unchanged. Before generating the added year, verify that176 the complete existing calendar has its expected rows, continuous standard177 dates, sequential numbering, valid quarters and adjustments, reconciled178 counts, and a complete immediately preceding fiscal year. The added year179 therefore has the newly requested format while prior years retain their180 prior format.181- An existing period's supported FSM/Data Loader fields are `PeriodNum`,182 `QuarterNum`, `StartDate`, `EndDate`, and `AdjustmentPeriodFlag`. Every183 changed row is affected and must be eligible. Block an existing-period name184 change through this task's FSM CSV route: `PeriodName` is the matching key185 and changing it causes Fusion to treat the row as a new period, while an186 `EnteredPeriodName`-only change does not update the displayed period name.187 Do not use a period-name prefix/header value as a workaround for existing188 rows.189 When associated ledgers exist, prove **Never Opened** (`ClosingStatus=N`)190 across every ledger and every returned application-specific status row.191 A per-ledger `accountingPeriodStatusLOV` response normally contains the192 ledger's full period history; this is not a blocker and requires no user193 follow-up. Retrieve every page, then automatically project the response onto194 the immutable affected `PeriodNameId` set, retain every matching195 `ApplicationId` row, and build the affected-period x associated-ledger196 coverage matrix. Ignore unrelated history rows. Use the original composite197 period identity only to cross-check the ID match, or as an exact fallback198 when `PeriodNameId` is unavailable; never use fuzzy name or date matching.199 Call this LOV with the cached OAuth bearer token and200 `REST-Framework-Version: 9`. A convenience-client call that returns no201 captured HTTP status or response body is a transport/client failure, not an202 empty result; retry the explicit GET with that header before blocking.203 For each successfully completed per-ledger query, matching rows must all be204 `N`. If the complete response has no matching row for an affected period--or205 no rows for that ledger at all--record `NO_STATUS_INSTANTIATED` for that206 ledger/period and allow it to pass without synthesizing an `N` row. This rule207 applies independently per ledger, so one empty ledger result may coexist with208 other ledgers whose matching rows are all `N`.209 Continue directly from successful retrieval through reduction and eligibility210 evaluation without asking the user to request another check or isolate rows.211 When a complete exact `ledgersLOV` query212 proves that the calendar has zero associated ledgers, query213 `accountingPeriodStatusLOV` directly for every affected period using its214 original name, year, number, and dates; resolve every returned `LedgerId`, and215 require that no returned status belongs to the target calendar. This216 zero-ledger/no-status branch is eligible because no ledger/application period217 status is instantiated for the calendar; an empty result is not mislabeled as218 `N`. Repeat the applicable complete check immediately before submission.219 Treat an inaccessible/truncated page, ambiguous identity, a target-calendar non-`N`220 row, or an evidence change as a blocker. Persist pagination receipts and the221 compact filtered matrix with period, ledger, application, status, dates, and222 retrieval time. A date change that requires223 an adjacent period boundary change makes that adjacent period affected and224 subject to the same rule.225 Preserve the original `PeriodNameId` in eligibility evidence. Preserve226 `PeriodName`, `EnteredPeriodName`, `PeriodYear`, calendar identity, frequencies, header227 counts, and header dates. Period numbers and quarters must still start and228 progress according to the calendar rules; adjustment-flag changes must retain229 the existing adjustment policy and reconciled counts. If the requested edit230 cannot preserve full-calendar continuity, uniqueness, numbering, quarter231 assignment, adjustment geometry, and those protected fields, stop. Treat the232 UI Additional Information region as DFF data, not a core calendar field; edit233 it only through a separately validated context/segment contract.234235Changes to an existing calendar's start date, non-adjusting frequency,236adjustment policy, `UserPeriodSetName`, `PeriodSetName`, parent linkage, or237any period field outside the conditionally permitted UI-editable core fields238remain blocked. Require an explicit update approval before any permitted239existing-calendar update.240241Budgetary-control-only calendars are a separate mode. They use the242budgetary-control calendar type, `OTHER` frequency, an explicit number of243budget periods, no user-selectable adjustment policy, and the budget-period244naming generated by the approved template. Do not apply normal accounting245calendar frequency, adjustment, or naming defaults to this mode.246247Weekly (`WEEK`) is the finest-grain supported standard calendar frequency.248Reject Daily or any finer-grain generated or manual calendar design, including249an attempt to express daily periods through `OTHER`.250251## Read Order2522531. Read `ora-resource/ora_input_intake.md`.2542. Read `ora-resource/ora_input_validation.md`.2553. Read `ora-resource/ora_dependency_readiness.md`.2564. Read `ora-resource/ora_reference_lookups.md`.2575. Read `ora-resource/ora_defaulting_rules.md`.2586. Read `ora-resource/ora_design_advisory.md`.2597. Read `ora-resource/ora_design_enforcement.md`.2608. Read `ora-resource/ora_bulk_intake.md`.2619. Read `ora-resource/ora_rest_execution.md`.26210. Read `ora-resource/ora_error_handling.md`.263264## Setup Task Metadata265266- Task name: `Manage Accounting Calendars`267- Task code: `GL_MANAGE_ACCOUNTING_CALENDARS`268- Available: `Y`269- Export/import supported: `Y`270- CSV export/import supported: `Y`271- CSV export/import routing: `supported`272273## Template Acquisition, Import, and Validation Workflow274275The catalog's `CSVExportImportSupportedFlag` remains `Y`. Creation uses only the276template route; a permitted update may use the controlled current-value source277rule above. Route acquisition, package validation, and import through:2782791. On the project's first run, or when its persisted template baseline is280 incompatible, automatically fetch the header-only task template with281 `shared.setup-export.task-level-export` in template-only mode. Treat this as282 normal non-business-data preflight under the user's calendar request; do not283 ask for a separate conversational approval. Authentication may still pause284 for user login when the token is stale.2852. Validate setup task data with `shared.validation.setup-data-validator`.2863. Validate reference data with `shared.validation.reference-data-validator`.2874. Import setup task data with `core.data-loader`.288289For a permitted update, resolve its complete current parent and period baseline290before step 2: reuse the verified current-session FSCR creation package when291eligible; otherwise automatically obtain one full task data export and isolate292the exact target. The full export is required for description-only updates,293period-name-format changes that add a fiscal year, and eligible existing-period294field edits whenever the verified current-session source is unavailable.295296`core.data-loader` is the mandatory execution owner for every calendar import.297It must perform the task validation, immutable-preview, approval, and submission298workflow for the FSM ZIP, including the adapter handoff and invocation.299`shared.setup-import.task-level-import` may be used only as the Data300Loader-invoked FSM adapter; never call that adapter directly after a chat301approval, a locally approved preview, or a Data Loader authorization record.302303Use this task metadata when invoking those skills:304305- Offering: `Financials`306- Functional area / Setup Object: `Financial Reporting Structures`307- Setup task name: `Manage Accounting Calendars`308- Setup task code: `GL_MANAGE_ACCOUNTING_CALENDARS`309310311## Inputs312313- `implementation_objective`314- `project_context`315- `setup_task_scope`316- `setup_data_artifacts`317318## Outputs319320- `setup_task_plan`321- `setup_data_routing`322- `validation_checkpoints`323- `skill_run_record`324- `token_usage_record`325326## Implementation Notes327328Use the parent functional-area skill `erp.financials.financial-reporting-structures` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.329330## Runtime Verification and Result Reporting3313321. Never access Fusion setup UI for discovery, duplicate checks, validation or verification, including through delegates or user-supplied screenshots. Use the declared endpoints and FSCR framework; authentication through core.auth is the sole user-completed browser handoff. Follow [endpoint-only verification](ora-resource/ora_reference_lookups.md#endpoint-only-verification).3332. Inspect the actual matching process logs before reporting any submitted import as successful or failed. For lookups or pre-submission checks, inspect their actual response or diagnostics. Follow [result reporting](ora-resource/ora_error_handling.md#mandatory-log-review-before-outcome-reporting).