Results for “bch_id”

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

Overview

OKL_TRX_MSGS is a transaction-message table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) module. It stores system messages generated against a leasing or finance transaction and resolves their display text through standard Oracle Application Object Library (AOL) message definitions. The table functions as the diagnostic and audit trail for transaction processing outcomes — recording errors, warnings, and informational messages produced by concurrent programs, batch validations, contract generation, and accounting flows. Each row is anchored to a specific transaction and optionally to a batch, which allows support staff and end users to identify exactly which contract or funding record triggered a given message.

Mined from the foreign-key structure, the heuristic Data Vault classification for this object is link. The table sits between a leasing transaction and a reusable AOL message definition, materializing the association between the two and capturing the context (transaction source, batch, and request) in which that association occurred. Modelers building a raw vault from the ETRM schema should treat OKL_TRX_MSGS as a transactional link rather than a hub or satellite.

Key Information Stored

The physical schema documented for 12.2.2 contains twenty columns. The most consequential for querying and reporting are:

• ID — surrogate primary key (OKL_TRX_MSGS_PK) and the sole unique index candidate (OKL_TRX_MSGS_U1). It carries no business meaning beyond row identity.
• TRX_ID and TRX_SOURCE_TABLE — the transaction identifier plus the source table from which it originates. Together these form the polymorphic business link to the underlying leasing transaction, since OKL transaction messages may be attached to more than one transaction entity.
• BCH_ID — batch identifier. This column is self-referencing according to the documented foreign-key listing and groups messages produced by a single batch run.
• TMG_APPLICATION_ID, TMG_MESSAGE_NAME, and TMG_LANGUAGE_CODE — the composite foreign key into FND_NEW_MESSAGES. These identify which AOL application-owner message is being referenced and in which language.
• MESSAGE_TEXT — the resolved message text, or the tokenized text that the AOL message framework substitutes at runtime.
• TMG_RUN — distinguishes message rows across successive executions, preventing collisions when the same transaction is reprocessed.
• SEQUENCE_NUMBER — orders messages within a transaction or batch.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — the standard concurrent-program audit block, essential for tracing the job that emitted the message.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — WHO columns and optimistic locking, consistent with the ETRM schema conventions.

Common Use Cases and Queries

The principal use case is transaction troubleshooting. A typical query lists all messages for a contract, ordered by sequence:

SELECT m.id, m.trx_id, m.trx_source_table, m.sequence_number, m.message_text FROM okl.okl_trx_msgs m WHERE m.trx_id = :p_trx_id AND m.trx_source_table = :p_source_table ORDER BY m.tmg_run, m.sequence_number;

A second pattern traces a failed concurrent request back to the affected transactions by joining on REQUEST_ID:

SELECT m.trx_id, m.message_text FROM okl.okl_trx_msgs m, fnd_concurrent_requests r WHERE m.request_id = r.request_id AND r.request_id = :p_request_id;

Batch operators query by BCH_ID to review every message raised in a single run, while localization teams use TMG_LANGUAGE_CODE to confirm that the correct translated AOL message was resolved. Reporting extracts typically join MESSAGE_TEXT to FND_NEW_MESSAGES to compare stored text against the master definition.

Related Objects

• FND_NEW_MESSAGES — joined via TMG_APPLICATION_ID, TMG_MESSAGE_NAME, and TMG_LANGUAGE_CODE; supplies the authoritative AOL message definition.
• OKL_TRX_MSGS.BCH_ID — the documented foreign-key relationship on the batch column, used for batch-level message grouping.
• OKL_TRX_MSGS_PK / OKL_TRX_MSGS_U1 — primary key and unique index on ID.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to associate messages with the originating concurrent program run.
• The OKL transaction header tables referenced by TRX_ID and TRX_SOURCE_TABLE, which supply the parent contract or funding context for each message.