Note: In this document, the term "lifecycle entity" is used to mean a proposal, a project, or an asset, and "lifecycle entities" are any combination of proposals, projects, and assets.
All lifecycle entities and programs have financial summaries that can include forecast and actual costs in the Cost Details and forecast and actual benefits (also known as financial benefits) in the Benefit Details sections. All lifecycle entities, programs, and organization units have financial summaries that can include approved budgets in the Approved Budget section.
When created, a proposal, a project, an asset, a program, or an organization unit becomes the parent of an automatically created financial summary.
A financial summary must have a parent entity; a financial summary cannot exist independently. Conversely, each proposal, project, asset, program, or organization unit has a financial summary.
When a proposal is approved and becomes a project, and when a project is completed and becomes an asset, the same financial summary (not a copy) is carried forward across these three "lifecycle entities"—the proposal, the project, and the asset.
Administrators can configure financial data tables as part of requests of any type, including but not limited to lifecycle entity requests. Separate from financial summaries, financial data tables allow tracking of other financial information related to requests.
This section explains how to use financial summaries and financial data tables.
For detailed information about financial summaries, see the following sections:
Financial Summaries of Lifecycle Entities (Proposals, Projects, and Assets) for lifecycle entities.
Financial Summaries of Programs for programs.
Financial Summaries of Organization Units for organization units.
For detailed information about financial data tables, see Financial Data Tables in Requests.