Search Results jai_om_oe_bond_reg_dtls




Overview
Explore in AI Chat

Overview

The table JAI_OM_OE_BOND_REG_DTLS is a core data object within the Asia/Pacific Localizations (product code JA) of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a detail table within a bonded warehouse or duty deferment registration framework, a common regulatory requirement in several APAC countries. Its primary role is to store and manage the specific types of sales orders and invoices that are permitted or registered under a particular bond or duty suspension scheme. By linking a registration header to specific transaction types, it enables the system to validate and control which transactions can proceed under the bonded warehouse rules, ensuring compliance with local customs and excise regulations.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of three critical columns. The REGISTER_ID column serves as the foreign key link to the master registration header table (JAI_OM_OE_BOND_REG_HDRS), identifying the specific bond registration. The ORDER_TYPE_ID is a foreign key to OE_TRANSACTION_TYPES_ALL, pinpointing the exact sales order type (e.g., Standard, Return) that is authorized under the bond. The ORDER_FLAG column acts as a qualifier, potentially distinguishing between different document flows such as sales orders and their corresponding invoices within the same registration context. Together, these columns enforce a rule that a given bond registration can authorize multiple, specific transaction types.

Common Use Cases and Queries

A primary use case is the validation process during order entry. When a user creates a sales order of a specific type intended for a bonded warehouse, the system queries this table to confirm that the ORDER_TYPE_ID is linked to a valid and active REGISTER_ID. This prevents processing unauthorized transactions. Common reporting needs include listing all authorized order types for a specific bond registration or identifying which registrations permit a particular transaction type. A typical query would join this detail table to its header and the OE_TRANSACTION_TYPES_ALL table to present a readable report.

SELECT hdr.register_code, ott.name order_type_name, dtl.order_flag
FROM jai_om_oe_bond_reg_dtls dtl,
     jai_om_oe_bond_reg_hdrs hdr,
     oe_transaction_types_all ott
WHERE dtl.register_id = hdr.register_id
  AND dtl.order_type_id = ott.transaction_type_id
  AND hdr.register_id = :p_register_id;

Related Objects

  • JAI_OM_OE_BOND_REG_HDRS: This is the parent/master table. The detail record in JAI_OM_OE_BOND_REG_DTLS is linked via the foreign key constraint on the column JAI_OM_OE_BOND_REG_DTLS.REGISTER_ID referencing JAI_OM_OE_BOND_REG_HDRS. It stores the overarching registration information like bond number and validity dates.
  • OE_TRANSACTION_TYPES_ALL: This standard Oracle Order Management table defines all transaction types. The detail table references it via the foreign key on the column JAI_OM_OE_BOND_REG_DTLS.ORDER_TYPE_ID to ensure only valid, predefined order types are associated with a bond registration.