Search Results threshold_dtl_id

Overview

The JAI_RGM_THRESHOLD_DTLS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a detail table designed to store specific classification and rule details associated with a regulatory threshold header. This table is integral to the system's management of region-specific compliance rules, such as tax or financial reporting thresholds mandated by local legislation in various Asia/Pacific countries. Its primary role is to provide the granular, conditional data that defines how a broader threshold rule is applied, enabling precise and configurable localization logic.

Key Information Stored

While the provided metadata does not list all columns, the structure is defined by its primary and foreign keys. The central column is THRESHOLD_DTL_ID, which serves as the unique primary key identifier for each detail record. The THRESHOLD_ID column is a critical foreign key that links each detail line to its parent header record in the JAI_RGM_THRESHOLDS table. Typically, detail tables in this context store conditional attributes such as classification codes (e.g., item categories, party types, transaction types), applicable rate or amount limits, effective date ranges, and specific calculation modifiers. These columns collectively define the exact scenario under which the parent threshold rule becomes active.

Common Use Cases and Queries

This table is primarily accessed during transaction processing to determine if a business event, such as an invoice or receipt, crosses a defined regulatory limit. A common use case is validating whether a supplier's cumulative purchase volume within a period exceeds a threshold requiring additional tax withholding or reporting. A typical query would join the detail to its header and other related setup tables to retrieve applicable rules for a given transaction context.

• Sample Query Pattern: Retrieving all active threshold details for a specific header to evaluate a transaction.
• Reporting Use Case: Generating audits of configured threshold rules by joining header and detail information for compliance reviews.
• Maintenance: Through the EBS localization forms, users create and maintain these detail records to tailor threshold rules to evolving business or legal requirements.

Related Objects

The JAI_RGM_THRESHOLD_DTLS table exists within a defined hierarchy and has explicit relationships with other localization objects, as documented in the ETRM metadata.

• Primary Key: JAI_RGM_THRESHOLD_DTLS_PK on THRESHOLD_DTL_ID.
• Foreign Key Relationship: The table has a mandatory foreign key relationship with the parent header table.
  • Foreign Key Column: JAI_RGM_THRESHOLD_DTLS.THRESHOLD_ID
  • References Table: JAI_RGM_THRESHOLDS
  • This relationship ensures every detail record is associated with a valid threshold header, maintaining referential integrity.
• Dependent Objects: While not listed, it is common for localizable views, APIs (e.g., JAI_RGM_THRESHOLD_PKG), and concurrent programs within the JA module to query this table to apply threshold logic.