Results for “both_all_none”

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

Overview

APPS.AP_JE_CATEGORIES_V is a reporting view in the Oracle E-Business Suite Payables (AP) module that exposes the set of journal entry categories relevant to subledger accounting for supplier transactions. Its purpose is to present a consolidated, filter-ready list of journal categories that Payables uses when generating accounting entries — most notably Payments, Purchase Invoices, and Reconciled Payments — together with a special control value denoting "All." The view is defined as a UNION of two sources: the general ledger journal categories catalog and the FND lookup type BOTH_ALL_NONE. The inclusion of the BOTH_ALL_NONE lookup, and specifically the lookup code 'A', signals that the view supports a tri-state selection convention (Both / All / None), where 'A' represents "All." This makes the view particularly useful for parameter lists in concurrent programs, Oracle Reports, OAF pages, and other inquiry screens where a user must select one, several, or all Payables journal categories. The user search term "both_all_none" corresponds directly to the FND_LOOKUPS lookup type that this view queries.

Underlying Base Objects

The view is defined over the following documented base objects:

• GL_JE_CATEGORIES (SYNONYM) — The General Ledger journal categories repository. The synonym resolves to the GL schema object. The view selects JE_CATEGORY_NAME and USER_JE_CATEGORY_NAME from this source, restricted to the categories 'Payments', 'Purchase Invoices', and 'Reconciled Payments'.
• FND_LOOKUPS (VIEW) — The standard Oracle Application Object Library lookup view. The view selects LOOKUP_CODE and MEANING from this source for LOOKUP_TYPE = 'BOTH_ALL_NONE' and LOOKUP_CODE = 'A'.
• FND_GLOBAL (PACKAGE) — Referenced by the metadata, indicating that the view depends on FND_GLOBAL for session and context resolution (for example, language or responsibility context used by dependent lookups and category name resolution).

The UNION combines the three named GL journal categories with the single "All" lookup row, producing a normalized two-column result set of code and description.

Key Columns

• JE_CATEGORY_NAME — The internal journal category code. For the GL rows, values are 'Payments', 'Purchase Invoices', and 'Reconciled Payments'; for the lookup row, the value is 'A' (meaning "All").
• USER_JE_CATEGORY_NAME — The user-facing, translatable description. For GL rows this is the user category name; for the lookup row it is the MEANING of lookup code 'A' (typically "All").

Note that the view exposes only these two columns; the UNION aligns the lookup code with the category name column and the lookup meaning with the user category name column, preserving a consistent two-column contract for downstream consumers.

Common Use Cases and Queries

A typical use is to populate a parameter LOV for a Payables accounting report or concurrent program, offering the standard categories plus an "All" option. A representative query follows:

• SELECT je_category_name, user_je_category_name FROM apps.ap_je_categories_v ORDER BY 2; — retrieves the complete selection list for a parameter.
• SELECT user_je_category_name FROM apps.ap_je_categories_v WHERE je_category_name = 'PAYMENTS'; — resolves the description for a single category.
• SELECT * FROM apps.ap_je_categories_v WHERE je_category_name = 'A'; — isolates the "All" control row derived from FND_LOOKUPS (BOTH_ALL_NONE).

Because the view is a simple UNION without aggregation, it can be safely embedded in larger subqueries and reporting joins. Developers should treat the "A" code as a sentinel value, not an actual GL category, when applying filters to journal data.