Analytics Catalog/Oracle Fusion ERP/Projects/Projects Asset Management Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Projects

Projects Asset Management Report

Projects

Projects that build capital assets — the capital projects and their asset lines, showing construction-in-progress accumulating toward each planned asset, so finance can track what's being built and when it capitalizes.

Run note · Performance  The subledger (XLA) join — especially Projects-to-XLA — is a known BI Publisher performance trap on large ledgers. Pre-join it in the warehouse, or apply tight ledger, period, and source filters before running online.

Sample build of the Projects Asset Management Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Projects Asset Management Report
Sample build · illustrative
Filters
Asset Type
Standard
Gl Location From
Sample
Gl Location To
Sample
Ledger
US Primary
Legal Entity
Globex Holdings
Major Category
Vehicles
42
Capital projects
$22.40M
CIP balance
7
Past in-service
ProjectPlanned AssetCip CostCapitalizedStatusIn-service Date
SampleSample$1,240,500.00SampleOpen2026-04-30
$842,150.75Posted2026-03-31
SampleSample$96,400.00SampleValidated2026-02-28
$1,005,233.10Open2026-01-31
SampleSample$58,720.40SamplePaid2025-12-31
SampleSample$1,240,500.00SampleOpen2026-04-30
AI Analyst · active
reading

The report reads project asset lines accumulating construction-in-progress toward each planned asset.

flag

Seven assets are past their planned in-service date but still in CIP — they should have capitalized and begun depreciating.

root cause & next step

Capitalize the seven; CIP held past in-service understates depreciation and overstates the CIP balance on the books.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.
SQL data set · genericized · parameterized · no hardcoded segments
Show / hide SQL
WITH LEDGER_NAME AS
(
	SELECT DISTINCT
	GL.NAME,
	PPAV.ORG_ID
	FROM
	PJF_PROJECTS_ALL_VL PPAV,
	HR_ORGANIZATION_INFORMATION_F HO,
	GL_LEDGERS GL
	WHERE
	PPAV.ORG_ID =HO.ORGANIZATION_ID
	AND HO.ORG_INFORMATION3=GL.LEDGER_ID

),
SEC_TBL AS
(
SELECT 
	DISTINCT 
	HOU.ORGANIZATION_ID
	FROM 
	HR_OPERATING_UNITS HOU,
	FUN_USER_ROLE_DATA_ASGNMNTS FURDA,
	PER_ROLES_DN PRD,
	PER_USER_ROLES PUR,
	PER_USERS PU
WHERE 
	1=1
	AND FURDA.ORG_ID = HOU.ORGANIZATION_ID
	AND UPPER(FURDA.ROLE_NAME) IN ('XXC_PROJECT_MANAGER_JOB','XXC_PROJECT_INQUIRY_JOB','XXC_PROJECT_ACCOUNTANT_JOB','XXC_PROJECT_ACCOUNTING_MANAGER_JOB')
	AND UPPER(FURDA.ACTIVE_FLAG) = 'Y'
	AND UPPER(FURDA.ROLE_NAME) = UPPER(PRD.ROLE_COMMON_NAME)
	AND PRD.ROLE_ID = PUR.ROLE_ID
	AND PUR.USER_ID = PU.USER_ID
	AND UPPER(PU.USERNAME) = UPPER(:XDO_USER_NAME)
	AND PU.USER_GUID = FURDA.USER_GUID
)

SELECT 
	PPAV.PROJECT_ID,
	PPEV.PROJ_ELEMENT_ID,
	PPAV.SEGMENT1 PROJECT_NUMBER,
	PPAV.NAME PROJECT_NAME,
	PPAV.PROJECT_STATUS_CODE PROJECT_STATUS,
	PPTV.PROJECT_TYPE PROJECT_TYPE,
	PPEV.NAME TASK_NAME,
	PPEV.ELEMENT_NUMBER TASK_NUMBER,
	PPEV.SERVICE_TYPE_CODE TASK_SERVICE_TYPE,
	PPAA.MANUFACTURER_NAME MANUFACTURER_NAME,
	PPAA.ASSET_NUMBER ASSET_NUMBER,
	PPAA.ASSET_NAME ASSET_NAME,
	PPAA.ASSET_DESCRIPTION,
	PPAA.ESTIMATED_IN_SERVICE_DATE ESTIMATED_IN_SERVICE_DATE,
	PPAA.DATE_PLACED_IN_SERVICE ACTUAL_IN_SERVICE_DATE,
	PPAA.PROJECT_ASSET_TYPE,
	PPAA.BOOK_TYPE_CODE ASSET_BOOK,
	PPAA.ESTIMATED_ASSET_UNITS,
	PPAA.ASSET_UNITS ACTUAL_ASSET_UNITS,
	FCV.SEGMENT1||'-'||FCV.SEGMENT2 ASSET_CATEGORY,
	FAK.SEGMENT1||'.'||FAK.SEGMENT2||'.'||FAK.SEGMENT3||'.'||FAK.SEGMENT4||'.'||FAK.SEGMENT5||'.'||FAK.SEGMENT6||'.'||FAK.SEGMENT7||'.'||FAK.SEGMENT8||'.'||FAK.SEGMENT9||'.'||FAK.SEGMENT10 ASSET_KEY,
	GCC.SEGMENT1||'.'||GCC.SEGMENT2||'.'||GCC.SEGMENT3||'.'||GCC.SEGMENT4||'.'||GCC.SEGMENT5||'.'||GCC.SEGMENT6||'.'||GCC.SEGMENT7||'.'||GCC.SEGMENT8||'.'||GCC.SEGMENT9 GL_CODE_COMBINATION,
	FL.SEGMENT1 ||'-'||FL.SEGMENT2 ||'-'||FL.SEGMENT3||'-'||FL.SEGMENT4||'-'||FL.SEGMENT5 ASSET_LOCATION,
	PPAA.DEPRECIATE_FLAG
FROM 
	PJF_PROJECTS_ALL_VL PPAV,
	PJF_PROJECT_TYPES_VL PPTV,
	PJF_CLASS_CODES_VL PCCV,
	PJF_PROJECT_CLASSES PPC,
	PJF_PROJ_ELEMENTS_VL PPEV,
	PJC_PRJ_ASSETS_ALL PPAA,
	PJC_PRJ_ASSET_ASGS PPAAS,
	FA_CATEGORIES_VL FCV,
	FA_ASSET_KEYWORDS FAK,
	GL_CODE_COMBINATIONS GCC,
	XLE_ENTITY_PROFILES XEP,
	FA_LOCATIONS FL,
	LEDGER_NAME LN,
	SEC_TBL ST
WHERE
	1=1
	AND PPAV.PROJECT_TYPE_ID 					= PPTV.PROJECT_TYPE_ID
	AND PPAV.PROJECT_ID 						= PPC.PROJECT_ID
	AND PPC.CLASS_CODE_ID 						= PCCV.CLASS_CODE_ID
	AND PPTV.ENABLE_CAPITALIZATION_FLAG 		= 'Y'
	AND PPAV.TEMPLATE_FLAG 						= 'N'
	AND PCCV.CLASS_CODE							IN ('CER','MER','TER')
	--AND PPAV.SEGMENT1							= 'CER337124OP0005'
	AND PPAV.PROJECT_ID 						= PPAA.PROJECT_ID
	AND PPAA.ASSET_CATEGORY_ID 					= FCV.CATEGORY_ID
	AND PPAA.PROJECT_ASSET_ID					= PPAAS.PROJECT_ASSET_ID(+)
	AND PPAAS.PROJECT_ID 						= PPEV.PROJECT_ID(+)
	AND PPAAS.TASK_ID							= PPEV.PROJ_ELEMENT_ID(+)
	AND PPAA.ASSET_KEY_CCID 					= FAK.CODE_COMBINATION_ID
	AND PPAA.DEPRECIATION_EXPENSE_CCID 			= GCC.CODE_COMBINATION_ID
	AND PPAA.LOCATION_ID 						= FL.LOCATION_ID
	AND PPAV.LEGAL_ENTITY_ID 					= XEP.LEGAL_ENTITY_ID
	AND PPAV.ORG_ID								= LN.ORG_ID
	AND ST.ORGANIZATION_ID						= PPAV.ORG_ID
	AND (LN.NAME            					IN (:P_LEDGER)
    OR  'ALL'                					IN (:P_LEDGER||'ALL'))
	AND (XEP.LEGAL_ENTITY_ID            		IN (:P_LEGAL_ENTITY)
    OR  'ALL'                					IN (:P_LEGAL_ENTITY||'ALL'))
	AND CAST(PPAV.ATTRIBUTE2 AS NUMERIC)		BETWEEN CAST(:P_SELL_METHOD_FROM AS NUMERIC) AND CAST(:P_SELL_METHOD_TO AS NUMERIC)
	AND CAST(PPAV.ATTRIBUTE1 AS NUMERIC)		BETWEEN CAST(:P_GL_LOCATION_FROM AS NUMERIC) AND CAST(:P_GL_LOCATION_TO AS NUMERIC)
	AND (PCCV.CLASS_CODE            			IN (:P_PROJECT_CLASS_CODE)
    OR  'ALL'                					IN (:P_PROJECT_CLASS_CODE||'ALL'))
	AND (PPAV.SEGMENT1		            		IN (:P_PROJECT_NUMBER)
    OR  'ALL'                					IN (:P_PROJECT_NUMBER||'ALL'))
	AND (PPAV.PROJECT_STATUS_CODE		        IN (:P_STATUS)
    OR  'ALL'                					IN (:P_STATUS||'ALL'))
	AND (FCV.SEGMENT1            				IN (:P_MAJOR_CATEGORY)
    OR  'ALL'                					IN (:P_MAJOR_CATEGORY||'ALL'))
	AND (FCV.SEGMENT2            				IN (:P_MINOR_CATEGORY)
    OR  'ALL'                					IN (:P_MINOR_CATEGORY||'ALL'))
	AND (PPAA.PROJECT_ASSET_TYPE            	IN (:P_ASSET_TYPE)
    OR  'ALL'                					IN (:P_ASSET_TYPE||'ALL'))
:P_ASSET_TYPE :P_GL_LOCATION_FROM :P_GL_LOCATION_TO :P_LEDGER :P_LEGAL_ENTITY :P_MAJOR_CATEGORY :P_MINOR_CATEGORY :P_PROJECT_CLASS_CODE :P_PROJECT_NUMBER :P_SELL_METHOD_FROM :P_SELL_METHOD_TO :P_STATUS :XDO_USER_NAME

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

PJC_PRJ_ASSETS_ALLdimensionPJC_PRJ_ASSET_LNS_ALLdimensionPJC_EXP_ITEMS_ALLdimensionGL_CODE_COMBINATIONSdimensionPJF_PROJECTS_ALL_VLfact · one row per source transactionCip Cost
●— fact → dimension join
ElementTypeDefinition
PJC_PRJ_ASSETS_ALLdimensiondimension
PJC_PRJ_ASSET_LNS_ALLdimensiondimension
PJC_EXP_ITEMS_ALLdimensiondimension
GL_CODE_COMBINATIONSdimensiondimension
Cip Costmeasuremeasure
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full picture, via conformed keys.
Projects data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

TableReporting columnsSubject areas
PJF_PROJECTS_ALL_VL3167
PJC_PRJ_ASSETS_ALL251
PJC_PRJ_ASSET_LNS_ALL152
PJC_EXP_ITEMS_ALL988
GL_CODE_COMBINATIONS761
Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.