Results for “date_name”

26 results




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

Overview

XTR_DATE_TYPES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR (Treasury) product family. It exposes date-type configuration data used by Treasury deal processing, where date types define the meaningful dates attached to a deal — value dates, maturity dates, settlement dates, and similar milestone dates — and where the user-facing terminology for each of those dates is controlled through the USER_DATE_TYPE and DATE_NAME attributes. The view presents this configuration in a stable, read-only form suitable for reporting, integration, and concurrent program queries.

In EBS 12.1.1 and 12.2.2 the object carries a status of VALID and is defined over the XTR_DATE_TYPES table accessed through the XTR_DATE_TYPES synonym. The view does not itself store data; it is a projection of the underlying configuration table. It is typically referenced when building custom reports, extracts, or validation queries that need to resolve how a given deal type identifies and labels its dates, and when consumers must map internal date type codes to the user-defined names presented on Treasury forms.

Underlying Base Objects

The view is defined over a single documented base object:

  • XTR_DATE_TYPES (SYNONYM) — the Treasury date type configuration table, referenced in the view definition as XTR_DATE_TYPES. The synonym resolves to the corresponding APPS-owned table.

Because the view text is a straightforward SELECT over that object with no joins, aggregation, or filtering, the row cardinality and content of XTR_DATE_TYPES_V mirror XTR_DATE_TYPES exactly. Each row represents one date type belonging to one deal type. Consumers therefore gain no derived or computed values beyond the column projection, and any change made to the base table through Treasury setup or maintenance is immediately visible through the view.

Key Columns

  • DEAL_TYPE — identifies the Treasury deal type to which the date type definition belongs, grouping date types by instrument or deal category.
  • DATE_TYPE — the internal code for the date type, used by Treasury processing logic to identify which date is being referenced.
  • USER_DATE_TYPE — the user-defined date type identifier, allowing installations to apply site-specific terminology; this is the column most often searched when resolving a user-facing date type.
  • DATE_NAME — the descriptive name displayed for the date, providing the label associated with the date type.
  • SEEDED_DESCRIPTION — the seeded (Oracle-provided) description of the date type, retained for reference alongside user modifications.
  • JOURNAL_USE — indicates whether the date type is used in journal/accounting processing, supporting determination of which dates drive accounting entries.
  • UPDATED_BY — the user identifier of the last person to update the record, useful for audit and change tracking.

Common Use Cases and Queries

The view supports lookups of date type configuration, reconciliation of user-defined versus seeded descriptions, and filtering of accounting-relevant date types. Because it is a simple projection, queries are efficient and require no knowledge of joins. A typical retrieval by user date type is:

  • SELECT deal_type, date_type, user_date_type, date_name, journal_use FROM xtr_date_types_v WHERE user_date_type = :p_user_date_type;
  • SELECT date_type, date_name, seeded_description FROM xtr_date_types_v WHERE deal_type = :p_deal_type ORDER BY date_type;
  • SELECT deal_type, date_type, date_name FROM xtr_date_types_v WHERE journal_use = 'Y';
  • SELECT date_type, user_date_type, date_name, updated_by FROM xtr_date_types_v ORDER BY deal_type, date_type;

These patterns are commonly used in custom Treasury reporting, in interface validation routines that must confirm a supplied date type exists for a deal type, and in analysis of which date types participate in journal generation.