Results for “cp_name”

50+ results




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

Overview

XTR_SWIFT_EFT_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered under the XTR — Treasury product. It was designed to expose Treasury payment settlement information in the flattened, payment-message-oriented layout required for SWIFT and electronic funds transfer (EFT) processing. The view consolidates data from settlement, counterparty, and bank account sources so that external payment instruction files — notably SWIFT MT-series messages and EFT transmissions — can be generated from a single queryable object.

The view is restricted to outgoing Treasury payments: the predicate S.SETTLEMENT_AMOUNT < 0 filters to net disbursements, and S.STATUS = 'A' limits output to active settlement summaries. Records tagged with an external source of 'ZBA' (zero-balance account) are explicitly excluded via NVL(S.EXTERNAL_SOURCE,'N') <> 'ZBA'. The result is a targeted, payment-ready data set representing the company and its counterparty, together with the banking and address details each side requires for message construction.

Underlying Base Objects

The documented base objects referenced by XTR_SWIFT_EFT_V are XTR_BANK_ACCOUNTS (synonym), XTR_PARTIES_V (view), XTR_SETTLEMENT_SUMMARY (synonym), and XTR_USER_ACCESS (package).

  • XTR_SETTLEMENT_SUMMARY (S) — the driving object, supplying settlement number, company, counterparty, currency, amount, date, account numbers, status, and external source.
  • XTR_BANK_ACCOUNTS (B, BC, IC) — joined three times. B resolves the company's own bank/account; BC supplies the counterparty's bank record and correlative bank fields; IC provides IBAN data for the counterparty account.
  • XTR_PARTIES_V (P, PC, PB) — joined three times to resolve full names and address lines: P for the company, PC for the counterparty, and PB for the counterparty bank party.

The view text joins these aliases through account number and party code equality, with additional type and status filters (notably B.PARTY_TYPE = 'C'), producing a denormalized record per settlement.

Key Columns

Common Use Cases and Queries

The view is typically queried to build or audit SWIFT/EFT payment files and to reconcile counterparty banking data. A representative query follows:

SELECT settlement_number, comp_name, cp_name, currency, settlement_amount, settlement_date, cp_iban, cp_swift_id FROM apps.xtr_swift_eft_v WHERE currency = 'USD' ORDER BY settlement_date DESC;

Other scenarios include locating payments for a specific counterparty by name using the CP_NAME column, and reviewing company and counterparty address blocks prior to message generation.

SELECT settlement_number, cp_name, cp_address1, cp_bank_name, cp_iban FROM apps.xtr_swift_eft_v WHERE UPPER(cp_name) LIKE '%ACME%';

Because access to underlying Treasury data is subject to user security, XTR_USER_ACCESS is referenced in the documented metadata to govern which settlements a given user may retrieve through the view.