Search Results application_user

Overview

APPS.XTR_DEALER_CODES_V is a reporting and integration view in the Oracle E-Business Suite Treasury (ETRM) module, available in releases 12.1.1 and 12.2.2. It presents dealer code configuration data maintained in the Treasury dealer management functionality, enriching the underlying dealer code records with the corresponding Oracle Applications user account name. The view is owned by the APPS schema, consistent with the standard EBS convention in which application-facing views are deployed under APPS and granted to responsibility-based users and integration accounts.

The view serves as the primary denormalized access point for dealer code definitions. Rather than requiring consumers to join the base transaction table to the application user table, the view performs that join internally, exposing both the dealer user name stored on the dealer record and the resolved FND user name in a single result set. This makes it suitable for concurrent program reports, Oracle Reports and BI Publisher data sources, and inbound or outbound interface components that need to validate or translate dealer identities. Because it is a view rather than a table, it reflects the current state of dealer code configuration and user account data at query time.

Underlying Base Objects

The view is defined over two documented base objects:

• XTR_DEALER_CODES (referenced as synonym) — the Treasury dealer code definition table, aliased as XDC in the view text. This is the driving table and supplies all dealer-specific attributes.
• FND_USER (referenced as synonym) — the Oracle Applications user repository, aliased as FU. It supplies the application user name associated with the dealer record.

The two objects are joined with the predicate XDC.USER_ID = FU.USER_ID, an equi-join on the Applications user identifier. Because this is an inner join, a dealer code row is returned only when a matching FND_USER record exists for the stored USER_ID. The synonyms referenced in the metadata resolve to the underlying EBS tables in the APPS schema.

Key Columns

• DEALER_CODE — the dealer code identifier from XTR_DEALER_CODES, the principal business key of the view.
• DEALER_USER_NAME — the dealer user name held on the dealer code record itself, which may differ from the resolved application user name.
• USER_ID — the Applications user identifier linking the dealer record to FND_USER.
• APPLICATION_USER — the FND_USER.USER_NAME value resolved through the join; the login name of the associated application user.
• AUDIT_INDICATOR — flag indicating the audit status or audit requirement associated with the dealer code.
• ALLOW_OVERRIDE — flag governing whether the dealer code setting may be overridden during Treasury transaction processing.
• CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — standard EBS audit columns recording who created and last updated the dealer code record and when.

Common Use Cases and Queries

The view supports dealer lookup and validation in Treasury deal capture and settlement flows, reconciliation of dealer codes to application users, and reporting on dealer configuration and audit metadata. A typical lookup by dealer code:

• SELECT dealer_code, dealer_user_name, application_user, allow_override FROM apps.xtr_dealer_codes_v WHERE dealer_code = :dealer_code;

A listing of all active dealer-to-user mappings for reconciliation:

• SELECT dealer_code, dealer_user_name, user_id, application_user FROM apps.xtr_dealer_codes_v ORDER BY dealer_code;

For audit and change tracking, the standard audit columns can be selected directly:

• SELECT dealer_code, created_by, created_on, updated_by, updated_on, audit_indicator FROM apps.xtr_dealer_codes_v;

Because the view enforces an inner join to FND_USER, queries intended to detect dealer codes with missing or invalid user assignments should be run against the base table XTR_DEALER_CODES, not this view, since orphaned rows will not appear in the view result set.