Results for “financial_number_currency”

50+ results




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

Overview

AMS_ORG_FINANCIAL_NUMS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, documented as part of the AMS (Marketing) product. Its stated purpose is to present details of financial reports, specifically the financial numbers associated with organization-type parties. The view is a denormalized, filtered projection rather than a stored entity; it consolidates financial number records with their parent financial reports and the owning party, applying business filters that restrict the result set to active organizations whose financial content was entered directly by a user.

In Oracle EBS 12.1.1 and 12.2.2, this view serves reporting and integration roles. It exposes the standard EBS audit and concurrent-program columns alongside derived alias columns (CREATED_BY_NAME, LAST_UPDATE_LOGIN_NAME, LAST_UPDATED_BY_NAME) that carry the same values as the source surrogate IDs. These aliases allow downstream reports and interfaces to reference a consistent naming convention without additional joins, and they are why the search term "last_update_login_name" surfaces this object.

Underlying Base Objects

The view is defined over three base objects, documented as synonyms in the APPS schema:

The join is an inner join across all three objects. The WHERE clause enforces three filters: HP.STATUS = 'A' (active parties only), HFN.ACTUAL_CONTENT_SOURCE = 'USER_ENTERED' (excluding system-derived content), and HP.PARTY_TYPE = 'ORGANIZATION' (restricting results to organizations). Consequently, the view does not expose all rows in HZ_FINANCIAL_NUMBERS; it exposes only the subset meeting these criteria. Because it is a view, it inherits the integrity and security characteristics of the underlying HZ tables and cannot be updated directly.

Key Columns

Common Use Cases and Queries

Typical uses include validating that organization financial figures were entered by users, auditing who last modified a financial number, and feeding reporting extracts. A representative query retrieving the audit identity of the most recent changes is:

SELECT FINANCIAL_NUMBER_ID, FINANCIAL_NUMBER, FINANCIAL_NUMBER_NAME, LAST_UPDATED_BY, LAST_UPDATED_BY_NAME, LAST_UPDATE_LOGIN_NAME, LAST_UPDATE_DATE FROM APPS.AMS_ORG_FINANCIAL_NUMS_V WHERE LAST_UPDATE_DATE >= SYSDATE - 30 ORDER BY LAST_UPDATE_DATE DESC;

Because the aliases equal the source IDs, LAST_UPDATE_LOGIN_NAME does not resolve to a user name on its own; it is a copied identifier and must be joined to FND_USER or FND_LOGINS if a readable user name is required. Report authors should remember that the view is already filtered to active, organization, user-entered data, so additional party or status predicates are unnecessary.