Results for “je_category_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_JE_CATEGORIES_V is a reporting view owned by the APPS schema within the PN - Property Manager product of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). Its purpose is to expose the set of journal entry categories that Property Manager uses when generating accounting entries for property-related transactions such as expense and revenue recognition. Rather than requiring callers to query GL_JE_CATEGORIES and FND_LOOKUPS separately, the view presents a consolidated, ready-to-consume list of journal categories in a simple two-column format.

Because the view name and its column JE_CATEGORY_NAME are frequently referenced in Property Manager setups, integration scripts, and reporting queries, it acts as a controlled enumeration of valid Category values that can be assigned to a journal entry line or used to filter General Ledger data originating from Property Manager. In Oracle EBS 12.2.2 the object is documented and registered with status VALID, confirming that the underlying definition has not been deprecated across releases.

Underlying Base Objects

The view is defined over three documented referenced objects:

• GL_JE_CATEGORIES (SYNONYM) — the General Ledger journal category definitions. The view selects JE_CATEGORY_NAME and USER_JE_CATEGORY_NAME from this object, filtered to the categories 'PM EXPENSE' and 'PM REVENUE'.
• FND_LOOKUPS (VIEW) — the Oracle Application Object Library lookup values view. The view unions in the lookup where LOOKUP_TYPE = 'BOTH_ALL_NONE' and LOOKUP_CODE = 'A', returning the lookup code as JE_CATEGORY_NAME and the meaning as USER_JE_CATEGORY_NAME.
• FND_GLOBAL (PACKAGE) — the standard Oracle EBS global context package, referenced within the view definition (typically for FND_GLOBAL.CONC_LOGIN_ID or related session context used by downstream logic).

The view text is:

• SELECT JE_CATEGORY_NAME, USER_JE_CATEGORY_NAME FROM GL_JE_CATEGORIES WHERE JE_CATEGORY_NAME IN ('PM EXPENSE','PM REVENUE')
• UNION SELECT LOOKUP_CODE, MEANING FROM FND_LOOKUPS WHERE LOOKUP_TYPE = 'BOTH_ALL_NONE' AND LOOKUP_CODE = 'A'

Key Columns

• JE_CATEGORY_NAME — the internal, system-recognized journal category name (for example 'PM EXPENSE', 'PM REVENUE', or the 'A' lookup code). This is the column most often searched for by that name and is used to join or filter against GL_JE_HEADERS.JE_CATEGORY and GL_JE_LINES.
• USER_JE_CATEGORY_NAME — the user-facing descriptive name of the category. For GL categories this is the translated/display name from GL_JE_CATEGORIES; for the unioned FND_LOOKUPS row it corresponds to the MEANING of lookup code 'A' (typically "All").

Common Use Cases and Queries

The view is typically used to populate list of values (LOVs) in Property Manager setup screens, to validate category assignments before posting to GL, and to filter GL journals that originated from Property Manager activities. Because it consolidates a fixed GL subset with a lookup value, it is a convenient reference for integration extracts.

Common query patterns include:

• List every available Property Manager journal category: SELECT je_category_name, user_je_category_name FROM apps.pn_je_categories_v;
• Resolve the display name for a specific category: SELECT user_je_category_name FROM apps.pn_je_categories_v WHERE je_category_name = 'PM EXPENSE';
• Use as a validation set when joining Property Manager accounting events to General Ledger journal headers.

Because the view draws from GL and FND lookup data, results reflect both seeded GL categories and lookup maintenance performed by the applications DBA, so it should be treated as a read-only reference rather than a transactional source.