Search Results item_category_code




Overview
Explore in AI Chat

Overview

APPS.PN_VAR_LINES_V is a form view in the Oracle Property Manager (PN) module, valid in EBS 12.1.1 and 12.2.2. It is documented in the ETRM metadata as a "form view used to input line item related information," meaning it is the query surface behind the Property Manager variance line-item form, not a standalone reporting table. Its principal role is to join the transactional variance line records in PN_VAR_LINES to their period definitions, their rent summary aggregates, and their lookup code descriptions, so the form — and by extension any query written against it — receives a single denormalized row per variance line item with human-readable meanings already resolved.

Because the view carries the standard EBS WHO columns and ORG_ID, it is also a convenient integration point for extracting Property Manager variance data into external reporting or reconciliation processes. The search term item_category_code is directly satisfied by this view: the column ITEM_CATEGORY_CODE is exposed alongside its decoded lookup value ITEM_CATEGORY.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PN_VAR_LINES (synonym) — the driving table supplying the variance line item, period, sales type, item category code, descriptive flexfield attributes, and audit columns.
  • PN_VAR_RENT_SUMM_ALL (synonym) — the source of the actual and forecasted rent aggregates. In the view text an inline subquery groups this table by LINE_ITEM_ID and PERIOD_ID to produce ACTUAL_RENT and FORECASTED_RENT.
  • PN_VAR_PERIODS — joined on PERIOD_ID to validate and anchor each line to its reporting period.
  • FND_LOOKUPS (view) — joined twice, once for the PN_SALES_CHANNEL lookup type and once for PN_ITEM_CATEGORY, to decode codes into meanings.
  • FND_GLOBAL (package) — referenced for session context such as ORG_ID.
  • PN_VAR_TEMPLATES_ALL (synonym) — documented as a base object for the variance line entity.

All lookup joins are outer joins ((+)), as is the rent summary join on LINE_ITEM_ID and PERIOD_ID. This ensures a variance line is returned even when no rent summary row or no lookup value exists.

Key Columns

  • LINE_ITEM_ID / LINE_ITEM_NUM — primary identifier and user-visible number for the variance line item.
  • PERIOD_ID — the Property Manager period the line belongs to.
  • ITEM_CATEGORY_CODE — the stored item category code; ITEM_CATEGORY — its decoded meaning from the PN_ITEM_CATEGORY lookup.
  • SALES_TYPE_CODE — stored sales type; SALES_CHANNEL — its decoded meaning from the PN_SALES_CHANNEL lookup.
  • ACTUAL_RENT / FORECASTED_RENT — summed actual and forecasted variable rent for the line and period.
  • COMMENTS — free-text line comments.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values.
  • ORG_ID and the WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — multi-org and audit context.

Common Use Cases and Queries

Typical uses include retrieving item category descriptions for variance lines, reconciling actual against forecasted rent by period, and feeding variance data into financial or property reporting. A representative query filtering on the searched attribute:

  • SELECT LINE_ITEM_NUM, PERIOD_ID, ITEM_CATEGORY_CODE, ITEM_CATEGORY, ACTUAL_RENT, FORECASTED_RENT FROM APPS.PN_VAR_LINES_V WHERE ITEM_CATEGORY_CODE = :p_category AND ORG_ID = :p_org_id;

Because lookup values are already decoded and rent aggregates pre-summed, no additional joins to FND_LOOKUPS or PN_VAR_RENT_SUMM_ALL are required in consuming queries.