Manage Asset Calendars Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation
guidance for Manage Asset Calendars under Fixed Assets.
Setup Task Skill Contract
- task_code:
FA_MANAGE_CALENDAR - task_name:
Manage Asset Calendars - parent_skill_id:
erp.financials.fixed-assets - CSV export/import routing:
supported - Data Loader import mode:
FSM
Usage
Use this skill when planning, creating, updating, importing, or validating Fixed Assets calendars. Before creating a ZIP, compare the proposed fiscal-year link, periods-per-year, and complete period set with every existing calendar in the target. An equivalent calendar requires a reuse-or-create-duplicate business decision; a different name alone does not permit a duplicate package. Use the parent Fixed Assets skill for shared approval, import-status, and project-state safeguards.
Derive a proposed period set from the selected fiscal year's complete date rows
and the requested periods per fiscal year. For a regular month-aligned cycle,
generate the date ranges and suggest unique period names; do not require the
user to provide example or complete period rows. Keep the generated set as a
proposal until it passes validation and the user approves the design preview.
Show generated period names with a four-digit year and preview dates as
DD-Mon-YYYY; this presentation rule does not change the target export's
technical date format.
Setup Task Metadata
- Offering:
Financials - Functional area / Setup Object:
Fixed Assets - Setup task name:
Manage Asset Calendars - Setup task code:
FA_MANAGE_CALENDAR
Resource Routing
| Need | Read |
|---|---|
| Required names, periods, and calendar consistency | ora_input_validation.md |
| Ledger-derived facts, equivalent Fixed Assets fiscal-year and calendar checks, and existing state | ora_reference_lookups.md |
| Defaults | ora_defaulting_rules.md |
| Dependencies and setup order | ora_dependency_readiness.md |
| Adjustment-period and design rules | ora_design_enforcement.md |
| Failures and safe next actions | ora_error_handling.md |
| Task sequence | ora_rule_registry.json |
CSV Export, Import, and Validation Workflow
- Export setup task data with
shared.setup-export.task-level-export. - Validate setup task data with
shared.validation.setup-data-validator. - Validate reference data with
shared.validation.reference-data-validator. - Build a task-specific delta ZIP containing only the requested create or update rows; use the baseline export only for CSV members, headers, metadata, and supported values. Do not re-import baseline records.
- Import the approved immutable package with
core.data-loader.
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifacts
Outputs
setup_task_plansetup_data_routingvalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Keep technical export and package metadata internal. Track token usage for generated project artifacts and skill-run records using the manifest policy.