Search Results ptd_ytd




Overview
Explore in AI Chat

Overview

APPS.GL_LOOKUPS_AVG_AMOUNT_TYPES_V is a lightweight reporting and integration view in the Oracle E-Business Suite General Ledger module. Its purpose is to expose the seeded lookup values that the application uses to classify average balance amount types — specifically the period-to-date and year-to-date conventions that drive Average Balance Processing (ABP) in Oracle General Ledger. The view does not store data of its own; it is a filtered projection of the general lookup repository, presenting only those lookup rows whose LOOKUP_TYPE is either PTD_YTD or PATD_EOD.

The name itself signals its function: it surfaces "average amount types," the codes that distinguish how Average Balance Processing aggregates balances. Values such as PTD (Period-to-Date), YTD (Year-to-Date), PATD (Prospective Average-to-Date), and EOD (End-of-Day) are represented here as lookup codes, allowing reports, concurrent programs, and third-party integrations to resolve the human-readable meaning and description for each code without hard-coding them. In both EBS 12.1.1 and 12.2.2 the view is defined in the APPS schema and is available to any responsibility with access to GL lookup data.

Underlying Base Objects

According to the documented view metadata, GL_LOOKUPS_AVG_AMOUNT_TYPES_V is defined over a single referenced base object: GL_LOOKUPS, itself exposed in EBS as a view (public synonym GL_LOOKUPS, owner APPS). The view applies a simple filter to that object:

  • WHERE l.lookup_type = 'PATD_EOD' OR l.lookup_type = 'PTD_YTD'

This means the view inherits all columns of GL_LOOKUPS but returns only the two lookup types tied to average balance amount-type selection. Because GL_LOOKUPS is a view over the underlying FND_LOOKUP_VALUES / FND_LOOKUPS foundation tables, changes made to those lookups through the application's lookup maintenance forms flow through automatically. The view introduces no joins, aggregations, or functions, so it remains a thin, low-cost selector that can be queried freely in reports.

Key Columns

The view exposes exactly three columns, each aliased for clarity and stable consumer use:

  • AMOUNT_TYPE — aliased from l.lookup_code. This is the stored code value that identifies the average amount type, e.g., PTD or YTD. It is the value typically compared against configuration or transaction columns.
  • SHOW_AMOUNT_TYPE — aliased from l.meaning. The translatable, user-facing display name of the amount type, suitable for list-of-values presentation and report headings.
  • DESCRIPTION — aliased from l.description. An optional explanatory text field providing additional context about the code's intended use.

All three map one-to-one to their GL_LOOKUPS source columns; no concatenation or formatting occurs inside the view.

Common Use Cases and Queries

The view is most commonly used to populate selection lists and to translate stored lookup codes into display values in custom reports and integrations. It also serves form-based validation, ensuring that a value written into a profile option, report parameter, or interface table matches a valid average amount type.

A typical query retrieves all available average amount types with their display names:

  • SELECT amount_type, show_amount_type, description FROM apps.gl_lookups_avg_amount_types_v ORDER BY amount_type;
  • SELECT show_amount_type FROM apps.gl_lookups_avg_amount_types_v WHERE amount_type = 'PTD';
  • SELECT amount_type FROM apps.gl_lookups_avg_amount_types_v WHERE lookup-like criteria on description IS NOT NULL;

In practice, developers reference this view when building Average Balance Processing reports that must distinguish PTD against YTD accumulation, or when an interface must map an incoming amount-type indicator to its EBS meaning. Because it is a simple lookup view, it can be joined to balance or interface queries on the amount-type code without performance concern. Note that translatable meanings depend on the runtime language environment, so report output will reflect the session's language setting.