Results for “iby_transmit_parameters_vl”

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

Overview

IBY_TRANSMIT_PARAMETERS_VL is a seeded, multilingual (VL) view in the APPS schema belonging to the IBY – Payments product. It presents the transmission parameter definitions that Oracle Payments uses to configure how outbound payment instructions, payment files, and related transmissions are formatted and dispatched across the various payment transmission protocols. Each row describes a single parameter that may be required or optional for a given transmit protocol, together with the metadata that determines whether the parameter value is supplied statically or generated dynamically at runtime.

The view is a reporting and integration entry point rather than a transactional object. It exposes translatable parameter names alongside the non-translatable configuration attributes, making it suitable for use in concurrent programs, BI Publisher data models, custom forms, and integration scripts that need to enumerate the transmission parameters available for a protocol. Because it contains the DYNAMIC_FLAG, DYN_CODE_LANGUAGE, DYN_CODE_PACKAGE, and DYN_CODE_ENTRY_POINT columns, the view is also the definitive reference for understanding how Payments resolves programmatically-derived parameter values — the columns the user searched for under “dyn_code_package.”

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• IBY_TRANSMIT_PARAMETERS_B — the base table holding non-translatable configuration attributes for each transmission parameter.
• IBY_TRANSMIT_PARAMETERS_TL — the translation table holding the TRANSMIT_PARAMETER_NAME in each installed language.

The join is performed on the composite key of TRANSMIT_PARAMETER_CODE and TRANSMIT_PROTOCOL_CODE, with the translation restricted to the session language via T.LANGUAGE = USERENV('LANG'). The TL table is therefore the language-dependent side and the B table the language-independent side, which is the standard Oracle EBS VL pattern. Note that the view text repeats DISPLAY_ORDER from the B table in its select list; the second occurrence is a seeded artifact and does not prevent successful querying by column name.

Documented structure confirms the view selects: ROW_ID (B.ROWID), TRANSMIT_PARAMETER_CODE, TRANSMIT_PARAMETER_TYPE, TRANSMIT_PROTOCOL_CODE, MANDATORY_FLAG, audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), DISPLAY_ORDER, DYNAMIC_FLAG, DYN_CODE_LANGUAGE, DYN_CODE_PACKAGE, DYN_CODE_ENTRY_POINT, OBJECT_VERSION_NUMBER, and TRANSMIT_PARAMETER_NAME.

Key Columns

• TRANSMIT_PROTOCOL_CODE — identifies the transmission protocol (for example, a specific payment file delivery mechanism) to which the parameter belongs.
• TRANSMIT_PARAMETER_CODE / TRANSMIT_PARAMETER_NAME — the internal code and the user-facing, translated name of the parameter.
• TRANSMIT_PARAMETER_TYPE — classifies the parameter, controlling how its value is interpreted.
• MANDATORY_FLAG — indicates whether a value must be supplied for the protocol to function.
• DYNAMIC_FLAG — when set, signals that the parameter value is derived at runtime rather than entered statically.
• DYN_CODE_LANGUAGE — the language in which the dynamic resolution code is written (for example, PL/SQL).
• DYN_CODE_PACKAGE — the name of the package containing the dynamic resolution logic; this is the column targeted by the “dyn_code_package” search.
• DYN_CODE_ENTRY_POINT — the specific procedure or function within that package invoked to return the parameter value.
• DISPLAY_ORDER — controls presentation sequence in configuration UIs.
• OBJECT_VERSION_NUMBER and the audit columns — support concurrent-update checking and standard EBS auditing.

Common Use Cases and Queries

Typical uses include auditing which parameters are dynamic for a protocol, verifying the package that resolves a given parameter, and populating configuration reports or migration scripts. A representative query to isolate dynamic parameters and their resolution packages is:

SELECT transmit_protocol_code,
       transmit_parameter_code,
       transmit_parameter_name,
       dynamic_flag,
       dyn_code_package,
       dyn_code_entry_point
FROM   apps.iby_transmit_parameters_vl
WHERE  dynamic_flag = 'Y'
ORDER  BY transmit_protocol_code, display_order;

A second common pattern lists all parameters for a specific protocol:

SELECT transmit_parameter_code,
       transmit_parameter_name,
       transmit_parameter_type,
       mandatory_flag
FROM   apps.iby_transmit_parameters_vl
WHERE  transmit_protocol_code = :p_protocol_code
ORDER  BY display_order;

Because the view restricts translation to USERENV('LANG'), queries return names in the current session language; reports intended for multiple locales should not assume a fixed language. As with all IBY setup objects, the view is read-only and changes must be made through the supported Payments configuration paths.