Results for “dyn_code_package”

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

Overview

IBY_TRANSMIT_PARAMETERS_B is a Payments module configuration table in the Oracle E-Business Suite IBY schema. It stores the parameter definitions that describe how a given payment transmission protocol is configured and executed — for example, the parameters required by a specific transmission mechanism (such as FTP, SFTP, or a payment gateway protocol) when a payment instruction is sent to a bank or partner. The "_B" suffix indicates that this is the base (non-translated) table; translatable columns are typically exposed through a corresponding "_TL" view, while the base table holds the language-independent parameter definitions.

From a modeling perspective, the mined metadata classifies this object as satellite-leaning. The table does not appear to be an independent hub, because its identity is anchored to a parent protocol via its foreign key. Instead, it behaves as a dependent entity that carries descriptive, attribute-level detail about parameters belonging to a protocol — consistent with satellite semantics. Each protocol can own multiple parameter rows, and each parameter is uniquely identified by the composite of the protocol and the parameter code.

Key Information Stored

The primary key, IBY_TRANSMIT_PARAMETERS_B_PK, is a composite business key defined on TRANSMIT_PROTOCOL_CODE and TRANSMIT_PARAMETER_CODE. This confirms that the surrogate identity of a parameter is fully derived from its parent protocol plus its individual parameter identifier; there is no independent numeric surrogate column in the documented structure. A unique index, IBY_TRANSMIT_PARAMETERS_B_U1, extends the same two columns with ZD_EDITION_NAME, reflecting the edition-based redefinition pattern used in 12.2.x.

The most significant columns include:

• TRANSMIT_PROTOCOL_CODE — foreign key to the owning protocol; defines the transmission mechanism the parameter belongs to.
• TRANSMIT_PARAMETER_CODE — the individual parameter identifier within the protocol.
• TRANSMIT_PARAMETER_TYPE — the data type or category of the parameter value.
• MANDATORY_FLAG — indicates whether the parameter must be supplied at transmission time.
• DYNAMIC_FLAG — signals whether the value is resolved dynamically at runtime rather than stored statically.
• DYN_CODE_LANGUAGE, DYN_CODE_PACKAGE, and DYN_CODE_ENTRY_POINT — the PL/SQL package and entry point invoked to compute a dynamic parameter value.
• SECURED_FLAG — marks parameters whose values should be protected (for example, credentials).
• DISPLAY_ORDER — controls presentation sequence when parameters are shown to users.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and ZD_EDITION_NAME — standard Oracle audit, concurrency-control, and editioning columns.

Common Use Cases and Queries

Typical usage involves determining which parameters a transmission protocol expects, which are mandatory, and how dynamic values are resolved. A representative query joining to the parent protocol table:

• SELECT p.TRANSMIT_PARAMETER_CODE, p.TRANSMIT_PARAMETER_TYPE, p.MANDATORY_FLAG FROM IBY.IBY_TRANSMIT_PARAMETERS_B p WHERE p.TRANSMIT_PROTOCOL_CODE = :protocol_code ORDER BY p.DISPLAY_ORDER;
• SELECT p.* FROM IBY.IBY_TRANSMIT_PARAMETERS_B p WHERE p.DYNAMIC_FLAG = 'Y'; — auditing dynamically resolved parameters and the packages they call.
• SELECT p.* FROM IBY.IBY_TRANSMIT_PARAMETERS_B p WHERE p.SECURED_FLAG = 'Y'; — reviewing parameters that hold sensitive values.

Reporting scenarios include protocol configuration audits, migration validation when moving payment setups between environments, and documentation of required transmission inputs.

Related Objects

• IBY_TRANSMIT_PROTOCOLS_B — the parent table; joined via TRANSMIT_PROTOCOL_CODE = TRANSMIT_PROTOCOLS_B.TRANSMIT_PROTOCOL_CODE.
• IBY_TRANSMIT_PARAMETERS_TL — translated view/table for language-dependent parameter descriptions.
• Payment transmission configuration and gateway setup components in the IBY schema that resolve protocol parameters at runtime.
• PL/SQL packages referenced by DYN_CODE_PACKAGE and DYN_CODE_ENTRY_POINT, which supply dynamic parameter values.