Manage Chart of Accounts Mappings Setup Task Guidance
Purpose
Build and maintain mappings between one source chart of accounts and one target chart of accounts. Keep mapping headers, segment rules, single-source and multiple-source rollup rules, account rules, hierarchy readiness, overlap analysis, FBDI readiness, and post-implementation review inside this one pillar skill.
Setup Task Skill Contract
- task_code:
GL_MANAGE_CHART_OF_ACCOUNTS_MAPPING - task_name:
Manage Chart of Accounts Mappings - 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/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Chart of Accounts Mappings under Financial Reporting Structures.
Use segment rules for broad mapping logic and account rules for precise exceptions. When both apply to the same source account combination, report the overlap and apply the account rule as the effective result.
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 Chart of Accounts Mappings - Task code:
GL_MANAGE_CHART_OF_ACCOUNTS_MAPPING - Available:
Y - Export/import supported:
Y - CSV export/import supported:
Y - CSV export/import routing:
supported
Supported Mapping Activities
- Compare mapping headers by name, source chart of accounts, target chart of accounts, description, security behavior, and child rules.
- Define target-segment rules with Assign single value, Copy value from source, or Use rollup rules.
- Define rollups from one source segment or exactly two source segments.
- Define and review account rules through the supported application workflow.
- Detect account-rule and segment-rule overlaps and state the precedence result.
- Generate FBDI artifacts only for segment and rollup rules.
- Validate hierarchy versions using the intended accounting date.
Do not create child skills for mapping activities.
Export, Import, and Validation Routing
CSVExportImportSupportedFlag is Y. Route supported setup-data operations through:
- 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. - Import setup task data with
core.data-loader.
Use only the existing FDOS authentication path and core FSM REST client as shared execution primitives. Never store credentials or authorization material.
Lifecycle
- Validate business inputs and intended accounting date.
- Select FSM for standard segment, single-source rollup, and account rules. Obtain a current target-environment template/spec ZIP through shared.setup-export.task-level-export (the default template-only route) whenever needed, independently of mapping inputs, COA resolution, or comparison. Require the Oracle XLSM only for a selected FBDI route.
- For FSM, follow the Template Contract Review and FSM Package Preparation procedures in ora-resource/ora_reference_lookups.md using the current ZIP and the Reviewed FSM Schema and Reviewed FSM Field Semantics sections in ora-resource/ora_reference_lookups.md. This contract is reference data for source/target semantics and S/C/R methods, not an executable dependency; a populated full-task export is not required. Resolve environment-specific identifiers separately. Stop on incompatible headers or metadata rather than guessing.
- Validate source and target charts, segments, referenced values, hierarchies, hierarchy versions, and deployment readiness.
- Find the mapping header using current target-environment evidence and compare its complete requested definition. Template acquisition does not depend on this comparison or on COA resolution. With no current mapping evidence, keep comparison pending and permit local package preparation only; never infer absence from an empty template or another environment's export.
- Stop on an identical mapping, or show field-level differences and obtain direction for a changed mapping.
- Validate segment, rollup, multiple-source, and account rules as one parent-and-children design. A create requires an actual rule definition; never submit a header-only smoke test. A segment-rule design must cover every enabled target segment exactly once, using current verified target metadata and valid values.
- Generate the source mapping, validation result, default-derivation record, and import-readiness record.
- Preview local preparation separately from submission readiness. A pending comparison terminates at prepared-only; do not route it to Data Loader approval. Require all applicable checks before a live preview.
- Route every import through core.data-loader and its Task Hook, immutable artifact, and approval workflow. Use Increment by default. Account rules use the verified FSM CSV contract, not FBDI.
- Check concurrency during preapproval validation for updates. Follow Data Loader's persisted approval-bound artifact procedure after approval; do not rebuild the artifact or duplicate its approval gate.
- A successful Data Loader initiation is terminal for that request. On a requested result check, verify through its status workflow and the Chart of Accounts Mapping Rules Report or equivalent read-only review.
Inputs
implementation_objectiveproject_contextmapping_definitionintended_accounting_datecurrent_fsm_template(FSM route)current_fbdi_template(FBDI route only)existing_mapping_evidence
Outputs
source_mappingmapping_comparisonmapping_validation_resultdefault_derivation_recordimport_readiness_recordconfiguration_blueprintskill_run_recordtoken_usage_record
Persist supported implementation artifacts under:
project/{project_id}/artifacts/pillars/erp/financials/financial-reporting-structures/manage-chart-of-accounts-mappings/current/
Refusal Rules
- Do not infer FBDI columns, codes, or defaults from EDM physical columns or UI labels.
- Do not generate account-rule FBDI rows.
- Do not submit a package with unresolved technical values or failed local validation.
- Do not use Replace for a partial package.
- Do not use failed live imports as default discovery.
- Do not perform a mutating Fusion action without explicit approval.
- Do not proceed when the current mapping changed after the comparison baseline.
FSM Preparation and Evidence
No task-specific executable is required. Use the existing shared task-level exporter, setup-data and reference-data validation workflows, and core.data-loader. Follow the task's explicit procedures in ora-resource/ora_reference_lookups.md for template review, current segment/value evidence, exact-name mapping comparison, and package preparation. The agent evaluates these rules and records the evidence in Task Hook ruleResults before the existing Data Loader preview/approval workflow.
Read the Reviewed FSM Schema and Reviewed FSM Field Semantics sections in ora-resource/ora_reference_lookups.md as the reviewed schema reference. Compare current CSV headers, metadata attribute types, object paths, sequence, and batch names before using their field/code meanings. These sections contain no customer setup rows and do not establish current environment state.
Obtain template/spec exports whenever needed. Obtain current name-scoped mapping evidence separately for duplicate/update checks; templates and foreign or old snapshots cannot establish absence. Both template and data exports can have ProcessType=EXPORT, so retain the originating operation, target environment, scope, timestamp, and artifact fingerprint.
Reject header-only creation, missing target-segment coverage, unverified values, and broken parent-child links before live preview. Preserve string values and leading zeros, leave unwritable audit fields blank, and prepare an immutable ZIP containing only the requested mapping data. Registry readiness means graph validity; package validity and live submission readiness require separate evaluated evidence.
Existing Skill Refinement Notes
No existing shared or core skill requires a functional change. This skill reuses the current task export, setup-data validation, reference-data validation, task import, authentication, and FSM-client responsibilities without redefining them.