Project Financial Management
Purpose
Provide offering-specific context, domain guidance and catalog-backed functional-area references after the implementation router and shared scope-definition workflow have established Project Financial Management scope. The active workflow owns route selection, ordered task execution, approvals and cross-functional-area handoffs.
When to Use
Use this offering-level skill after Project Financial Management is in scope and before routing to a specific functional-area skill.
Catalog Identity
- Pillar:
ERP - Pillar slug:
erp - Offering code:
PJF_PROJ_MNG - Offering slug:
project-financial-management - Offering folder:
pillars/erp/project-financial-management - Offering mapping source:
knowledge/setup-task-catalog/release/pillars-offerings-mapping.json - Setup task catalog source:
knowledge/setup-task-catalog/release/offering-functional-area-task-catalog.json
Functional-Area References and Ownership
Before any child workflow executes a REST request, require the offering's REST version and query compatibility preflight. The selected core client or workflow owns framework-version selection; pillar queries and the outgoing header must agree with it. This check does not authorize external execution or replace the child's declared workflow gates.
This skill supplies matching functional-area references to the active workflow; it does not start, sequence or own an implementation program. Functional-area references use the catalog-backed path pattern:
pillars/erp/project-financial-management/{functional-area-slug}/
When the catalog matches a task but its skill is absent, retain the exact task identity and report the missing capability to the active workflow. Do not invent a path, generate a skill during setup execution, or substitute a live integration. The workflow selects any declared manual-task route and its prerequisites, or records a blocker. Skill generation is a separate developer authoring activity.
Cross-Functional Task Discovery
Resolve every requested or next runbook task through shared.implementation-planning.offering-task-map-builder and use its catalog-backed task_code, functional_area, and skill_path. Do not infer a task-code prefix, functional area, or filesystem path from the preceding task: an ordered implementation can hand off between functional areas within this offering.
Before declaring a task skill absent or recording a workflow gap:
- Resolve the exact task name against
knowledge/setup-task-catalog/effective/setupTasksAll.json. - Use the resolved task code to search all descendant task manifests under
pillars/erp/project-financial-management, not only the preceding functional-area folder. - Follow the matched manifest's declared
parent_skill_idand confirm it in that functional-area skill's Setup Tasks list.
A failed guessed path is not evidence of a missing skill. If an ad hoc diagnostic is still needed, search manifest contents or full paths; do not combine a task-name basename predicate with -name SKILL.md, because both predicates test the same basename and can incorrectly return no matches.
Known cross-functional handoff: Manage Project Types is under Project Foundation, while the subsequent Manage Project Plan Types task is under Project Control with code PJO_MANAGE_PROJECT_PLAN_TYPES and skill erp.project-financial-management.project-control.manage-project-plan-types.
The catalog lists the whole offering; it does not promise that every functional-area skill is implemented in this checkout. Return the resolved facts and missing capability to the workflow without changing its current step or approvals.
Inputs
implementation_objectiveproject_contexterp_scopeproject_financial_management_requirements
Outputs
project_financial_management_scopefunctional_area_skill_planproject_financial_management_work_productsskill_run_recordtoken_usage_record
Functional Areas From Catalog
Source: knowledge/setup-task-catalog/release/offering-functional-area-task-catalog.json
Offering code: PJF_PROJ_MNG
Functional area count: 20
Setup task count: 292
ORA_ASK_INITIAL_USER: Initial UsersORA_ASK_ENTERPRISE_PROFILE: Enterprise ProfileORA_ASK_LEGAL_STRUCTURES: Legal StructuresORA_ASK_FIN_REPORTING_STRUCT: Financial Reporting StructuresORA_ASK_ORGANIZATION_STRUCTURE: Organization StructuresORA_ASK_WORKFORCE_STRUCTURE: Workforce StructuresORA_PJF_PROJ_ORG: Project OrganizationsORA_ASK_USERS_AND_SECURITY: Users and SecurityORA_PJF_PROJECT_FOUNDATION_FA: Project FoundationPJF_BURDENING: BurdeningPJF_PJO_DEPLOYED: Project ControlORA_PJC_PROJ_COSTING_BASE_FA: Project Costing BasePJC_CAPITAL_PROJECTS: Capital ProjectsOKC_PROJECT_CONTRACTS: Project ContractsORA_PJB_PROJ_BILLING_BASE_FA: Project Billing BasePJB_INTERCOMPANY_BILLING: Internal Project BillingFIN_APPLICABILITY_ZX: Transaction TaxPJF_PJS_DEPLOYED: Project Performance ReportingORA_PJC_PROJECT_ACCOUNTING: Project AccountingORA_ASK_APPLICATION_EXTENSIONS: Application Extensions
Implementation Notes
- Summarize the approved offering scope and applicable domain guidance here. The existing output names remain compatible:
project_financial_management_scopesummarizes shared scope decisions, andfunctional_area_skill_plansupplies catalog-backed recommendations, not an authoritative execution sequence. - Delegate scope decisions to
shared.project-intake.scope-definition, route selection to the implementation router, and instantiated sequencing and cross-functional-area handoffs to the active workflow. Do not update their authoritative scope, skill path or setup-task sequence from this pillar. - Put functional-area-specific implementation guidance in generated child skills under this offering folder.
- Do not create setup-task-specific skills directly under this offering folder unless the user explicitly requests nested task-level skill generation through the pillar skill generator.
Durable Artifacts and Review
For offering-owned durable outputs, resolve the selected project_id from the
existing project_context and active workflow. Reuse prior project artifacts.
If no implementation project exists, follow the repository project-initialization
policy before writing; do not add a new required caller input or infer a different
project. An ambiguous project identity is an input_validation blocker.
- Save the offering scope summary, functional-area recommendations and applicable work products under the declared offering artifact location. These outputs describe the approved scope and recommendations; they do not change the workflow's authoritative scope, route, current step or setup-task sequence.
- Use
core.project-mgmt.artifact-version-managerfor new major versions and confirmed minor updates. Register durable artifacts throughcore.project-mgmt.artifact-registry-managerusingschemas/project-artifact.schema.json, including producing skill, location, version, status, timestamps and checksum when available. - Use
core.project-mgmt.project-state-managerto record the run underproject/{project_id}/state/runs/and update only the declared offering-owned state fields when their work products change. Theskill_run_recordmust conform toschemas/skill-run.schema.json, retain input/output and artifact references, and record the actual status. Append a run for a no-change revisit without replacing existing artifacts. - Record token usage at the manifest's shared token-log location using the core project service's token-usage guidance, and include the estimate and log reference in the run record. Exclude credentials and token-cache contents.
Before writing, validate project identity, destination paths, artifact metadata
and versioning requirements. On persistence failure, stop the affected handoff,
classify it as artifact_persistence, retain safely written artifacts, and report
their references and the next recovery action. Record the failed run and redacted
diagnostics in the selected project when writable; if that write also fails,
report the intended path and failure without claiming completion. Never persist
credentials, tokens, private keys or sensitive payloads. This local persistence
step does not invoke child setup execution or authorize external operations.