FND_TREE_VERSION_VL

Common / FoundationUsed in 1 subject areas23 reporting columnsBICC incremental-ready

Foundation / Setup (FND) — view layer — joins the base table with translations for the current language.

Likely primary key: TREE_VERSION_ID (inferred from Oracle naming conventions — verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

Column	Key	In reports	Description (inferred)
CHANGED_SINCE_VALIDATION		●	Changed since validation.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
DESCRIPTION		●	Description.
EFFECTIVE_END_DATE		●	End date of the effective-dated record.
EFFECTIVE_START_DATE		●	Start date of the effective-dated record.
LAST_UPDATED_BY		●	User who last updated the row.
LAST_UPDATE_DATE	INCR	●	Date and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGIN		●	Session login of the user who last updated the row.
LAST_VALIDATION_DATE		●	Last validation date.
LAST_VALIDATION_RESULT		●	Last validation result.
LAST_VALIDATION_RESULT_ID		●	Identifier for the last validation result.
LEVEL_COUNT		●	Level count.
LOCKED_BY		●	Locked by.
LOCK_DATE		●	Lock date.
NODE_COUNT		●	Node count.
SOURCE_TREE_VERSION_ID		●	Identifier for the source tree version.
STATUS		●	Status.
TREE_CODE		●	Code identifying the tree.
TREE_STRUCTURE_CODE		●	Code identifying the tree structure.
TREE_VERSION_ID	PK?	●	Identifier for the tree version.
TREE_VERSION_NAME		●	Name of the tree version.
VERSION_COMMENT		●	Version comment.

No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.

The OTBI subject areas that expose this table. You can't join across them in OTBI — the owned conformed model joins them on shared keys.

Need the extract + dbt staging for FND_TREE_VERSION_VL?

We ship parameterized SQL, BICC config, and dbt models you own.