Results for “op_lkbx_mst”

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

Overview

OP_LKBX_MST is a master (reference) table owned by the GML schema and delivered as part of the Oracle Process Manufacturing Logistics module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is unambiguous in the ETRM metadata: it stores lockbox codes. A lockbox is a bank-operated receiving address to which a customer remits payment; when that payment is captured electronically, the lockbox identifier on the receipt or remittance advice lets the application route and reconcile the incoming funds to the correct customer, order, or proposal.

The table therefore acts as the central registry of valid remit-to lockbox references used throughout the order-to-cash flow in Process Manufacturing. It is referenced — not owned — by the customer, sales order, and proposal tables, all of which point back to a single LOCKBOX_CODE per record. The ETRM heuristic Data Vault classification describes this object as hub-leaning: its primary key is a stable, single-column business identifier, which is consistent with a hub pattern, while descriptive and audit attributes sit alongside it in the same physical table, which is typical of the legacy Oracle master-table design that Data Vault models later normalize into hub plus satellite.

Key Information Stored

The documented physical schema lists 43 columns in GML.OP_LKBX_MST. The most significant are summarized below.

• LOCKBOX_CODE — the single-column primary key (constraint OP_LKBX_MST_PK) and the only documented business-key candidate. This is the value carried as a foreign key by every dependent table.
• LOCKBOX_DESCRIPTION — the user-facing name or description of the lockbox, used on screens and reports in place of the raw code.
• ADDR_ID — foreign key to SY_ADDR_MST, linking the lockbox to a registered address record. This is the table's only outbound foreign key and typically identifies the physical bank or remit-to address.
• LOCKBOX_COMMENT — free-text annotation maintained by the user for operational notes.
• TEXT_CODE — a short code value used for supplementary classification of the lockbox entry.
• TRANS_CNT — a transaction counter column, standard in GML master tables, used to detect concurrent change and drive propagation/refresh logic.
• DELETE_MARK — the soft-delete flag; rows are logically deactivated rather than physically removed, so all queries should filter on this column.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — provide the standard who/when lineage.
• Flexfield columns — ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — supply the descriptive flexfield region, allowing customers to extend the lockbox record without schema change.

Common Use Cases and Queries

The principal use case is validation and lookup during order entry and remittance processing: when a sales order, customer, or proposal is saved with a remit-to lockbox, the application verifies that the entered code exists in OP_LKBX_MST. A second use case is reporting — producing a listing of active lockboxes with their associated addresses, or analyzing how many orders or proposals are routed to each lockbox.

A basic validated listing:

• SELECT l.LOCKBOX_CODE, l.LOCKBOX_DESCRIPTION, l.ADDR_ID, a.ADDRESS1
• FROM GML.OP_LKBX_MST l
• LEFT JOIN APPS.SY_ADDR_MST a ON a.ADDR_ID = l.ADDR_ID
• WHERE NVL(l.DELETE_MARK, 0) = 0
• ORDER BY l.LOCKBOX_CODE;

To count downstream usage, aggregate the dependent order header table by lockbox code, joining OP_ORDR_HDR.LOCKBOX_CODE to OP_LKBX_MST.LOCKBOX_CODE. Because LOCKBOX_CODE is highly selective and indexed through the primary key, joins from any of the referencing tables are inexpensive. Reports that must remain stable over time should key on LOCKBOX_CODE rather than LOCKBOX_DESCRIPTION, since the description is a mutable attribute.

Related Objects

Six documented foreign keys reference OP_LKBX_MST, making it one of the more widely consumed lookup tables in the GML order-to-cash schema.

• SY_ADDR_MST — referenced by OP_LKBX_MST via ADDR_ID; supplies the address detail for the lockbox.
• OP_CUST_MST — joins on LOCKBOX_CODE; holds the customer's default remit-to lockbox.
• OP_CUST_MST_OPM — joins on LOCKBOX_CODE; the Process Manufacturing customer master variant carrying the same default.
• OP_ORDR_HDR — joins on LOCKBOX_CODE; the order header's remit-to lockbox for the transaction.
• OP_ORDR_DTL — joins on LOCKBOX_CODE; line-level lockbox assignment where it differs from the header.
• OP_PRSL_HDR — joins on REMIT_TO_LOCKBOX; the proposal header's remit-to designation.
• OP_PRSL_DTL — joins on REMIT_TO_LOCKBOX; the proposal line's remit-to designation.

Note that the two proposal tables use the column name REMIT_TO_LOCKBOX rather than LOCKBOX_CODE; joins must account for this naming difference. No API or view specific to this master table is documented in the ETRM extract, so maintenance is normally performed through the Process Manufacturing logistics setup forms or direct DML governed by the standard audit and DELETE_MARK conventions.