Results for “user_amount_type”

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

Overview

XTR_AMOUNT_TYPES_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a curated projection of the XTR_AMOUNT_TYPES table, exposing the configuration metadata that defines how monetary amounts are classified and reported across Treasury deal types. The view carries a status of VALID in the ETRM data dictionary, confirming that its definition compiled successfully and that its column list is consistent with the underlying base object.

Amount types drive several core Treasury behaviors: they categorize cash flows on deals, govern how interest and principal components are segregated, and supply the semantic labels used in Treasury reporting. The distinguishing feature of this view is the JOURNAL_USE column, which indicates whether a given amount type is intended for journal entry generation — that is, whether transactions bearing that amount type are passed to the accounting layer. The user search term "journal_use" maps directly to this column, and it is the primary reason the view is queried.

Because the view is a thin projection rather than a denormalized reporting object, it serves both as an integration surface for external systems consuming Treasury amount type metadata and as a validation source for setups prior to transaction processing or accounting transfer. It does not aggregate, join, or filter, so it inherits the row cardinality of the base table exactly.

Underlying Base Objects

The view is defined over a single referenced object, XTR_AMOUNT_TYPES, accessed through a synonym in the APPS schema. The documented definition is:

• Base object: XTR_AMOUNT_TYPES (SYNONYM)
• Owner: APPS
• Definition type: Simple SELECT projection, no joins, no aggregation, no WHERE clause

Because XTR_AMOUNT_TYPES is referenced via synonym rather than a fully qualified table name, the view resolves against the APPS-owned base table at runtime. There is no dependency on other Treasury tables such as XTR_DEAL_TYPES or XTR_AMOUNT_TYPE_MAP; the view is deliberately self-contained so that downstream consumers obtain amount type configuration without traversing additional schema relationships. Any insert, update, or delete against the base table is immediately visible through the view, and DML against the view itself is not supported in the standard seeded form.

Key Columns

• DEAL_TYPE — Identifies the Treasury deal type to which the amount type applies. Amount types are scoped by deal type, so the same logical amount (for example, interest) may be defined independently for different instruments.
• AMOUNT_TYPE — The internal code identifying the amount type. This is the value stored on transaction and cash flow records and is the join key used throughout the Treasury data model.
• USER_AMOUNT_TYPE — The user-defined or user-facing amount type designation, allowing installations to map seeded or custom classifications to their own business terminology.
• AMOUNT_NAME — The display name for the amount type, suitable for reports and list-of-values presentation.
• SEEDED_DESCRIPTION — Oracle-supplied descriptive text. Its presence typically indicates a seeded amount type that should not be redefined by the customer.
• JOURNAL_USE — The journal usage indicator. This flag determines whether the amount type participates in accounting journal generation. It is the column most frequently referenced when verifying which amount types are accounting-relevant.
• UPDATED_BY — Standard audit column recording the application user who last modified the row.

Common Use Cases and Queries

The most frequent scenario is identifying which amount types drive accounting entries for a given deal type, either during configuration review or before diagnosing missing journal lines.

• List accounting-relevant amount types: SELECT deal_type, amount_type, amount_name FROM xtr_amount_types_v WHERE journal_use = 'Y';
• Inspect nomenclature for a deal type: SELECT user_amount_type, amount_name, seeded_description FROM xtr_amount_types_v WHERE deal_type = :deal_type;
• Audit last maintenance: SELECT amount_type, journal_use, updated_by FROM xtr_amount_types_v ORDER BY updated_by;
• Integration extract of all amount type metadata: SELECT * FROM xtr_amount_types_v;

Because the view is unfiltered, callers should always constrain queries by deal_type or journal_use in production. The view is read-only and best treated as a stable configuration interface.