Search Results ack_transmit_protocol_code

Overview

The view IBY_SYS_PMT_PROFILES_VL in the Oracle E-Business Suite Payments (IBY) module exposes system-level payment profile definitions in a language-translated format. It is owned by the APPS schema and is defined as a VALID view in both Oracle EBS 12.1.1 and 12.2.2. Because it is a "_VL" (translated view), it joins the base table to its translation table and filters results by the session language, ensuring that descriptive attributes such as the system profile name and description are returned in the user's active language. Payment system profiles establish the operational defaults used when processing payments — including transmission and security settings, payment format selection, printer configuration, and positive pay handling. As such, this view serves as the primary reporting and integration interface for querying those definitions, abstracting the multi-table storage model into a single flat, read-consistent result set.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the ETRM metadata: IBY_SYS_PMT_PROFILES_B and IBY_SYS_PMT_PROFILES_TL. The "_B" table stores the operational (non-translated) attributes of each system payment profile and provides the primary key SYSTEM_PROFILE_CODE. The "_TL" table stores the language-dependent text — SYSTEM_PROFILE_NAME and SYSTEM_PROFILE_DESCRIPTION — for each supported language. The join condition links the two tables on SYSTEM_PROFILE_CODE and constrains T.LANGUAGE = USERENV('LANG'), so each row reflects the profile's functional data plus its localized descriptive text. Nearly all exposed columns originate from the "_B" table; only the name and description columns come from the translation table.

Key Columns

• SYSTEM_PROFILE_CODE — Primary key identifying the payment system profile.
• SYSTEM_PROFILE_NAME / SYSTEM_PROFILE_DESCRIPTION — Localized descriptive text from the translation table.
• SECURITY_PROTOCOL_CODE — The security protocol used for transmitting payment files, a frequently queried column for transmission and compliance reporting.
• TRANSMIT_PROTOCOL_CODE — The transport protocol associated with the profile.
• PAYMENT_FORMAT_CODE, POSITIVE_PAY_FORMAT_CODE, PAY_FILE_LETTER_FORMAT_CODE — Format identifiers governing generated payment output.
• BEPID — Payment system identifier linking the profile to its payment system.
• PRINT_INSTRUCTION_IMMED_FLAG, TRANSMIT_INSTR_IMMED_FLAG, SEND_TO_FILE_FLAG — Processing behavior indicators.
• DEFAULT_PRINTER, DEFAULT_PAYMENT_DOCUMENT_ID — Output defaults.
• DECLARATION_* columns — Regulatory declaration settings (option, currency, FX rate type, threshold amount, report format).
• ACK_TRANSMIT_PROTOCOL_CODE, ACK_SECURITY_PROTOCOL_CODE — Acknowledgement transmission settings.
• INACTIVE_DATE, SEEDED_FLAG, OBJECT_VERSION_NUMBER — Lifecycle and concurrency control.
• Attribute columns 1–15 and ATTRIBUTE_CATEGORY — Descriptive flexfield segments.

Common Use Cases and Queries

Analysts commonly use this view to review protocol and format configurations across payment profiles, to audit which profiles use a given security protocol, and to drive integration extracts. A representative query retrieving the security protocol alongside profile identification is shown below.

• Query profiles filtered by security protocol:
  SELECT SYSTEM_PROFILE_CODE, SYSTEM_PROFILE_NAME, SECURITY_PROTOCOL_CODE, TRANSMIT_PROTOCOL_CODE
FROM IBY_SYS_PMT_PROFILES_VL
WHERE SECURITY_PROTOCOL_CODE = :P_SECURITY_PROTOCOL_CODE;
• Audit active profiles and their payment formats:
  SELECT SYSTEM_PROFILE_CODE, PAYMENT_FORMAT_CODE, POSITIVE_PAY_FORMAT_CODE
FROM IBY_SYS_PMT_PROFILES_VL
WHERE INACTIVE_DATE IS NULL;
• Review acknowledgement and declaration settings for compliance reporting.

Because the view returns data in the session language and flattens the base/translation structure, it is preferred over querying the underlying tables directly for reporting and integration purposes.