Results for “xtr_settlement_scripts_v”

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

Overview

XTR_SETTLEMENT_SCRIPTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR (Treasury) product family. It exposes configuration and execution metadata for settlement scripts — the stored definitions that Treasury uses to generate and transmit electronic settlement and payment files to banks and other counterparties. In EBS 12.1.1 and 12.2.2 the object is documented with a status of VALID, and it functions as a read-oriented presentation layer over the settlement script definition table, allowing concurrent programs, inquiry forms, and downstream extracts to retrieve script definitions without directly referencing the base table.

Because settlement processing is sensitive to authorisation state, output path configuration, and run history, the view centralises the attributes that administrators and support teams need to monitor. It is particularly relevant to the script_type search term: SCRIPT_TYPE is one of the view's projected columns and is the primary discriminator used to classify each settlement script by the format or mechanism it represents.

Underlying Base Objects

The view is defined over a single documented base object: XTR_SETTLEMENT_SCRIPTS, referenced through a synonym in the APPS schema. The view text is a straightforward projection — it selects a defined column list directly from XTR_SETTLEMENT_SCRIPTS with no joins, unions, or aggregation. Consequently, XTR_SETTLEMENT_SCRIPTS_V carries no filtering logic of its own; row visibility and data content are inherited entirely from the base table. This one-to-one mapping means the view is effectively a column-restricted alias, useful for granting controlled read access and for insulating custom reports from physical table changes. Any insert, update, or delete against settlement scripts must still be performed on the base table, since the view is not documented as an updatable or instead-of trigger view.

Key Columns

• COMPANY_CODE — the legal entity or company context to which the script belongs.
• SCRIPT_NAME — the user-defined identifier of the settlement script.
• SCRIPT_TYPE — classifies the script by its settlement/payment format or transmission mechanism, and is the column most commonly used to filter and group settlement script records.
• AUTHORISED — indicates whether the script has been approved for execution.
• EFT_SCRIPT_OUTPUT_PATH — the file system or directory location where generated output files are written.
• PACKAGE_NAME — the PL/SQL package invoked to build or format the settlement output.
• CURRENCY_CODE — the currency associated with the script, where the definition is currency specific.
• RUN_REQUESTED_ON, LAST_RUN_ON, LAST_RUN_BY, LAST_FILE_CREATED — execution audit attributes recording when a run was requested, when it last completed, who ran it, and the resulting output file.
• COMMENTS — free-text descriptive notes maintained by the administrator.
• ONLY_NEW_TRANSACTIONS — a processing flag controlling whether the run includes only transactions not previously settled.
• TRANSMISSION_CODE — identifies the transmission method or channel used to deliver the settlement file.
• IBY_TRANSMIT_CONFIGURATION_ID — foreign key to the Payments (IBY) transmit configuration that governs delivery of the generated file.

Common Use Cases and Queries

Typical uses include inventorying configured scripts by type, verifying authorisation before a settlement run, auditing the last execution and output file, and joining to IBY transmit configuration data for delivery diagnostics. Because SCRIPT_TYPE drives classification, it is the natural filter for most queries.

• List authorised scripts by type: SELECT script_name, script_type, currency_code, eft_script_output_path FROM xtr_settlement_scripts_v WHERE authorised = 'Y' ORDER BY script_type, script_name;
• Latest execution audit: SELECT script_name, last_run_on, last_run_by, last_file_created FROM xtr_settlement_scripts_v WHERE script_type = :p_type ORDER BY last_run_on DESC;
• Delivery configuration lookup: SELECT s.script_name, s.transmission_code, s.iby_transmit_configuration_id FROM xtr_settlement_scripts_v s WHERE s.iby_transmit_configuration_id IS NOT NULL;

All queries should be issued from the APPS schema or a responsibility with equivalent read privileges on the XTR objects.