Results for “patd_eod”

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

Overview

The view ITG_AMOUNT_TYPES_V belongs to the ITG product family (Internet Procurement Enterprise Connector), which provides the integration bridge between Oracle E-Business Suite and external procurement or enterprise connector platforms. In Oracle EBS 12.1.1 and 12.2.2 this view functions as a lightweight reference or lookup view that enumerates the valid amount-type semantics used when translating General Ledger balance data into a procurement-facing representation. Its name reflects that it exposes amount type codes (such as period-to-date and year-to-date) alongside their seeded meanings, scoped to a specific set of books.

The view does not store data of its own. It exists to present a denormalized, join-ready list of lookup values so that ITG integration processes, concurrent programs, or reporting queries can resolve amount type codes to human-readable descriptions without embedding lookup logic in application code. Its role is therefore primarily descriptive and reference-oriented rather than transactional.

The presence of the column SET_OF_BOOKS_ID indicates that the view is set-of-books aware: the same lookup codes may be exposed once per set of books, and the composition of the lookup list can vary depending on configuration — specifically the ENABLE_AVERAGE_BALANCES_FLAG on the set of books.

Underlying Base Objects

The ETRM metadata records no separately documented base owner or base objects; however, the view text itself defines the dependency clearly. The view is defined over two GL objects:

• GL_LOOKUPS — the source of the lookup code, meaning, and description values.
• GL_SETS_OF_BOOKS — the source of the set of books identifier and the average-balances configuration flag that conditions which lookup types are returned.

The join is effectively a cross product of sets of books and the qualifying lookup rows, filtered by the LOOKUP_TYPE predicate. Because GL_LOOKUPS is keyed by LOOKUP_TYPE and LOOKUP_CODE, and GL_SETS_OF_BOOKS is keyed by SET_OF_BOOKS_ID, the view introduces no new data relationships beyond those two dictionary tables.

Key Columns

• SET_OF_BOOKS_ID — the identifier of the accounting set of books against which the amount types are valid; sourced from GL_SETS_OF_BOOKS.
• LOOKUP_CODE — the stored code for the amount type, drawn from GL_LOOKUPS; typical values include the PTD/YTD family referenced by the search term "ptd_ytd".
• MEANING — the user-facing display name for the lookup code, used for labels and reports.
• DESCRIPTION — the extended description of the lookup code, if populated.

The critical filter logic is the LOOKUP_TYPE IN ('PTD_YTD', DECODE(B.ENABLE_AVERAGE_BALANCES_FLAG, 'Y', 'PATD_EOD', NULL)) predicate. When average balances are enabled on the set of books, the view also returns lookup types associated with PATD_EOD (period-average-to-date / end-of-day), expanding the available amount types; otherwise only PTD_YTD values are returned.

Common Use Cases and Queries

Typical use is validating or listing the amount types available for a given set of books, or driving downstream ITG mapping logic that expects a code-to-meaning pairing.

• Listing all amount types for a set of books: SELECT set_of_books_id, lookup_code, meaning FROM itg_amount_types_v WHERE set_of_books_id = :p_sob;
• Resolving a code to its display meaning for reporting.
• Confirming whether PATD_EOD types are exposed, as an indirect check of the average-balances setting on the set of books.

Because the underlying tables are GL dictionary tables, standard EBS access rules and any GL lookup customization apply; organizations that add custom lookup codes to the relevant lookup types will see those codes reflected here automatically.