Search Results jai_om_oe_bond_trxs




Overview
Explore in AI Chat

Overview

The table JAI_OM_OE_BOND_TRXS is a core data object within the Oracle E-Business Suite Asia/Pacific Localizations module (product code JA). It is designed to store transactional records related to bond management, a common regulatory requirement in several Asia/Pacific jurisdictions for managing excise or customs duties. Specifically, this table captures detailed bond transaction information, such as bond amounts, that are linked to sales order fulfillment processes. Its primary role is to facilitate the tracking and accounting of bond liabilities and utilizations against customer orders and their associated picking and shipping activities within the Oracle Order Management and Shipping Execution modules.

Key Information Stored

While the provided metadata does not list all columns, the documented foreign key relationships and primary key define its critical structure. The central column is TRANSACTION_ID, which serves as the unique primary key for each bond transaction record. The table's foreign keys indicate it stores essential reference identifiers that link the bond transaction to its source documents. These include ORDER_HEADER_ID to associate the transaction with a sales order header, and PICKING_HEADER_ID and PICKING_LINE_ID to associate it with specific shipping pick slips. The REGISTER_ID column links the transaction to a parent bond register header in the JAI_OM_OE_BOND_REG_HDRS table, which likely controls the bond master record. Other columns, as suggested by the description, store financial details such as the bond amount, transaction date, and type.

Common Use Cases and Queries

This table is central to reporting and reconciliation for bonded transactions. A common use case is generating a report of all bond amounts utilized for orders shipped within a specific period. Another is reconciling the total bond liability against the master bond register. Sample queries often involve joins to the related order and shipping tables to provide context. For instance, to list bond transactions for a specific order, one might use a query joining JAI_OM_OE_BOND_TRXS to OE_ORDER_HEADERS_ALL on ORDER_HEADER_ID. Auditing and compliance checks would also query this table to ensure bond transactions are correctly recorded against every relevant picking line that involves bonded goods.

Related Objects

The table maintains defined foreign key relationships with several key EBS tables, making it integral to the order-to-ship bond tracking flow. The documented relationships are:

  • JAI_OM_OE_BOND_REG_HDRS: Linked via JAI_OM_OE_BOND_TRXS.REGISTER_ID. This is the parent bond register or declaration.
  • OE_ORDER_HEADERS_ALL: Linked via JAI_OM_OE_BOND_TRXS.ORDER_HEADER_ID. Provides the sales order context.
  • SO_PICKING_HEADERS_ALL: Linked via JAI_OM_OE_BOND_TRXS.PICKING_HEADER_ID. Provides the pick slip (delivery) header context.
  • SO_PICKING_LINES_ALL: Linked via JAI_OM_OE_BOND_TRXS.PICKING_LINE_ID. Provides the specific picked item line detail.
These relationships ensure data integrity and enable comprehensive tracking from the bond register down to the individual shipped line item.