Results for “xtr_one_step_settle_codes”

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

Overview

The XTR_ONE_STEP_SETTLE_CODES table is an Oracle Treasury (XTR) configuration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores company-level settlement codes that are applied when the one-step settlement method is used. In Treasury processing, settlement instructions determine how cash movements from deals, debt instruments, investments, and foreign exchange contracts are routed to bank accounts. The one-step method consolidates what would otherwise be a two-stage settlement into a single instruction, and this table supplies the settlement code that drives that instruction at the company level.

The table resides in the XTR schema and is documented with a status of VALID. Its heuristic Data Vault classification is standalone. Under a dimensional or Data Vault modeling suggestion, this object would be modeled as a reference or lookup structure rather than a hub, link, or satellite, because it holds descriptive configuration values keyed to a company and schedule combination rather than representing a business event or an intersection of business entities.

Key Information Stored

The documented physical schema contains nine columns. The most significant are described below.

• ONE_STEP_ID — The surrogate primary key, defined by the unique index XTR_ONE_STEP_SETTLE_CODES_PK. It uniquely identifies each one-step settlement code row.
• COMPANY_CODE — The company to which the settlement code applies. This is a business-key candidate column, participating in the unique index XTR_ONE_STEP_SETTLE_CODES_U1.
• SCHEDULE — The schedule associated with the settlement arrangement. Together with COMPANY_CODE it forms the composite business key in XTR_ONE_STEP_SETTLE_CODES_U1, ensuring one settlement code per company and schedule combination.
• SETTLEMENT_CODE — The settlement code value used for the one-step settlement method. This is the substantive configuration payload of the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS who-columns capturing audit and concurrency information for each row.

Note that ONE_STEP_ID also appears in a second unique index, XTR_ONE_STEP_SETTLE_CODES_U2, describing it as a business-key candidate in addition to its primary key role. The composite unique index U1 on COMPANY_CODE and SCHEDULE is the primary candidate for a natural business key.

Common Use Cases and Queries

Typical uses center on validating, reporting, and troubleshooting settlement configuration for companies using the one-step method.

• Retrieving the settlement code for a given company and schedule: SELECT settlement_code FROM xtr.xtr_one_step_settle_codes WHERE company_code = :company AND schedule = :schedule;
• Listing all one-step settlement configurations across companies for audit or setup review: SELECT one_step_id, company_code, schedule, settlement_code FROM xtr.xtr_one_step_settle_codes ORDER BY company_code, schedule;
• Auditing recent changes using the who-columns: SELECT one_step_id, company_code, last_updated_by, last_update_date FROM xtr.xtr_one_step_settle_codes WHERE last_update_date >= :since;
• Feeding Treasury settlement and cash-position reporting, where the settlement code determines the bank account and routing used for one-step settlements.

Related Objects

The metadata classifies this object as standalone, with no foreign keys documented in the mined relationship data. As a result, direct foreign-key relationships to other XTR tables are not established at the schema level. Related Treasury objects that logically participate in the same settlement configuration flow include company and legal entity definitions referenced through COMPANY_CODE, bank and bank account setup tables used to resolve the settlement code into an actual cash account, and the Treasury deal and settlement tables that consume the settlement code during one-step settlement processing. Because ONE_STEP_ID serves as the internal key, any downstream reference would resolve through it or through the COMPANY_CODE and SCHEDULE business key rather than through a documented foreign key constraint. Implementation and DBA analysis should rely on the two unique indexes, XTR_ONE_STEP_SETTLE_CODES_U1 and XTR_ONE_STEP_SETTLE_CODES_U2, when planning joins and data migration activities.