Results for “ap_je_categories_v”

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

Overview

AP_JE_CATEGORIES_V is a view owned by the APPS schema in Oracle E-Business Suite, residing in the Payables (AP) product family. It is a documented, VALID database object in both release 12.1.1 and 12.2.2. The view presents the set of journal entry categories that Payables uses when generating and reconciling accounting entries, together with the user-facing display name for each category. Because the view exposes the pairing of an internal JE_CATEGORY_NAME with its USER_JE_CATEGORY_NAME, it serves as a lightweight lookup and translation layer for reporting, integrations, and diagnostic queries that must interpret the category values stored on Payables accounting lines.

Searches for "user_je_category_name" typically originate from developers or analysts inspecting subledger accounting data, who need to resolve the internal journal category into a label suitable for presentation or comparison against General Ledger definitions.

Underlying Base Objects

The documented view text is a UNION of two SELECT statements. The first returns JE_CATEGORY_NAME and USER_JE_CATEGORY_NAME from GL_JE_CATEGORIES, restricted to three internal category values: 'PAYMENTS', 'PURCHASE INVOICES', and 'RECONCILED PAYMENTS'. The second selects LOOKUP_CODE and MEANING from the FND_LOOKUPS view where the lookup type is 'BOTH_ALL_NONE' and the lookup code is 'A'. GL_JE_CATEGORIES is accessed through the GL_JE_CATEGORIES synonym. The documented referenced base objects are FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), and GL_JE_CATEGORIES (SYNONYM).

The result is a compact, self-contained list: the three Payables-specific journal categories joined by the single 'A' lookup entry, which represents a generic "Both/All/None" indicator used by the application framework. Because it is a view rather than a table, it stores no data itself and always reflects the current contents of the underlying GL and FND objects at query time.

Key Columns

• JE_CATEGORY_NAME — the internal identifier of the journal category, drawn either from GL_JE_CATEGORIES or from the lookup code column of FND_LOOKUPS. This is the value stored on Payables accounting and subledger lines.
• USER_JE_CATEGORY_NAME — the user-facing label corresponding to the internal category. For GL-sourced rows this is the category's display name; for the FND_LOOKUPS row it is the lookup MEANING for code 'A'.

The two columns form a direct key-to-label mapping. There is no additional filtering or derivation applied, so the view is transparent and inexpensive to query.

Common Use Cases and Queries

A primary use case is resolving an internal category stored on Payables accounting lines into a human-readable label for reports and extracts. A representative query is:

• SELECT je_category_name, user_je_category_name FROM apps.ap_je_categories_v ORDER BY je_category_name;
• SELECT user_je_category_name FROM apps.ap_je_categories_v WHERE je_category_name = 'PAYMENTS';

The view is also useful when building joins against Payables subledger records, where the internal category must be displayed or grouped. For example, an analyst might join the view to a Payables distribution or accounting line query on the category column to obtain the display name, or restrict a report to the three Payables categories plus the 'A' lookup entry. Because the view is small and stable, it is well suited to LOV-style lookups, data validation, and integration mappings that must reconcile the set of categories recognized by Payables against those defined in the ledger. When validating reconciliation logic, querying the view quickly confirms the exact internal values the application expects.