Results for “settlement_code”

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

Overview

XTR_ONE_STEP_SETTLE_CODES_V is a secured Oracle EBS view owned by the APPS schema in the XTR (Treasury) product. It presents a filtered, security-aware rendition of the XTR_ONE_STEP_SETTLE_CODES table, which stores one-step settlement code definitions used in treasury deal and settlement processing. Rather than exposing every row of the underlying table, the view applies a company-level authorization filter so that a given user only sees settlement code combinations belonging to companies for which that user holds input authority.

Because the view enforces row-level security via FND_GLOBAL.USER_ID, it is the preferred access path for treasury forms, reports, and integration interfaces that require user-scoped visibility into one-step settlement definitions. Its role is therefore both functional (returning settlement code data) and security-oriented (restricting the visible company population per user).

Underlying Base Objects

The view is defined over a single physical source object, XTR_ONE_STEP_SETTLE_CODES, referenced in the dictionary as a synonym. The security predicate is built from two additional synonym-referenced objects: XTR_COMPANY_AUTHORITIES and XTR_DEALER_CODES, together with the FND_GLOBAL package. The defining query is essentially:

• Select the settlement code rows from XTR_ONE_STEP_SETTLE_CODES.
• Restrict COMPANY_CODE to values returned by a subquery joining XTR_COMPANY_AUTHORITIES (CA) and XTR_DEALER_CODES (DC), where CA.COMPANY_AUTHORISED_FOR_INPUT = 'Y' and DC.USER_ID = FND_GLOBAL.USER_ID.

This linking of the dealer code to the currently logged-in user is the mechanism that ties company visibility to the operator's treasury authority configuration. All base objects are referenced as APPS synonyms, consistent with standard EBS view construction.

Key Columns

The view exposes nine columns mirroring the base table, plus the security-relevant COMPANY_CODE:

• ONE_STEP_ID — Primary identifier for the one-step settlement code record.
• COMPANY_CODE — The company/party to which the settlement code belongs; the column constrained by the security subquery.
• SCHEDULE — The schedule associated with the one-step settlement definition.
• SETTLEMENT_CODE — The settlement code value used in one-step settlement processing.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording record creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and login context.

Common Use Cases and Queries

Typical scenarios include populating settlement code lists in treasury setup forms, validating permitted one-step settlement combinations during deal entry, and feeding downstream reports or integration extracts that must honor treasury company authority. A representative query retrieving all visible settlement codes is:

• SELECT ONE_STEP_ID, COMPANY_CODE, SCHEDULE, SETTLEMENT_CODE
• FROM APPS.XTR_ONE_STEP_SETTLE_CODES_V
• ORDER BY COMPANY_CODE, SCHEDULE;

To isolate codes for a specific company, add a predicate such as WHERE COMPANY_CODE = :company_code. Because the view already applies the FND_GLOBAL.USER_ID security constraint, results automatically reflect the responsibilities and dealer code authority of the connected user, making it unsuitable for cross-company administrative extracts unless run under an appropriately authorized login.

Oracle Proprietary, Confidential Information — Legal Notices apply to this documentation and associated objects.