Results for “initial_trx_amount”

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

Overview

JL_BR_AR_SELECT_CONTROLS_ALL is a Latin America Localization (JL) table in Oracle E-Business Suite Release 12.1.1 and 12.2.2, owned by the JL schema. It stores the selection criteria definitions used to identify Oracle Receivables invoices that are eligible for inclusion in bank transfer (bordero) batches. Each row in the table represents a named selection control — a reusable set of filtering parameters such as transaction date ranges, due date ranges, customer number ranges, transaction number ranges, transaction types, and receipt methods — that the Brazilian localizations employ when generating remittance borders for banking transmission.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. It behaves as a hub because SELECTION_CONTROL_ID serves as a stable surrogate key referenced by dependent tables, and the surrounding attributes describe the reusable identity of the selection definition rather than an immutable business transaction. In EBS terms, it functions as a configuration and control master that drives the invoice selection process for bank transfer batches.

Key Information Stored

The table contains 45 documented columns. The most significant include:

• SELECTION_CONTROL_ID — Surrogate primary key (JL_BR_AR_SELECT_CONTROL_ALL_PK) and also the unique business-key candidate (JL_BR_AR_SELECT_CONTROLS_U1). It uniquely identifies each selection control.
• NAME — User-defined name/label used to identify the selection criteria set.
• SELECTION_STATUS and SELECTION_TYPE — Control the processing state and the nature of the selection (for example, manual versus automatic).
• BORDERO_TYPE — Indicates the type of bordero (bank transfer batch) for which the criteria are intended.
• SELECTION_DATE, GENERATION_DATE, REMITTANCE_DATE, CANCELLATION_DATE — Operational dates tracking the lifecycle of the control.
• DUE_DATE_BREAK_FLAG, INITIAL_DUE_DATE, FINAL_DUE_DATE — Define the due-date window used to filter invoices.
• INITIAL_TRX_DATE and FINAL_TRX_DATE — Define the invoice transaction-date window.
• CUST_TRX_TYPE_ID — Foreign key to RA_CUST_TRX_TYPES_ALL, restricting selection to a specific transaction type.
• INITIAL_TRX_NUMBER / FINAL_TRX_NUMBER and INITIAL_CUSTOMER_NUMBER / FINAL_CUSTOMER_NUMBER — Numeric ranges for invoice and customer filtering.
• RECEIPT_METHOD_ID — Foreign key to AR_RECEIPT_METHODS, tying selection to a specific receipt method.
• INITIAL_TRX_AMOUNT / FINAL_TRX_AMOUNT — Amount range bounds for invoice inclusion.
• ORG_ID — Multi-org operating unit identifier, supporting multi-organization partitioning.
• REQUEST_ID — Links the selection control to the concurrent request that generated or processed it.

The ATTRIBUTE1–15 DFF columns and standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical scenarios include auditing which selection controls exist for a given operating unit, reviewing the parameters behind a bank transfer batch, and reconciling invoices selected for remittance. A representative query lists active controls with their transaction type descriptions:

• SELECT s.selection_control_id, s.name, s.selection_status, s.cust_trx_type_id, t.name trx_type FROM jl.jl_br_ar_select_controls_all s, ra_cust_trx_types_all t WHERE s.cust_trx_type_id = t.cust_trx_type_id AND s.org_id = :org_id;
• To inspect the borderos produced by a control: SELECT b.* FROM jl_br_ar_borderos_all b WHERE b.selection_control_id = :id;
• To inspect associated selection accounts: SELECT a.* FROM jl_br_ar_select_accounts_all a WHERE a.selection_control_id = :id;

Related Objects

• JL_BR_AR_BORDEROS_ALL — References this table via SELECTION_CONTROL_ID; holds generated bank transfer batches.
• JL_BR_AR_SELECT_ACCOUNTS_ALL — Child table keyed by SELECTION_CONTROL_ID, storing accounts tied to a selection.
• RA_CUST_TRX_TYPES_ALL — Referenced via CUST_TRX_TYPE_ID; supplies transaction type context.
• AR_RECEIPT_METHODS — Referenced via RECEIPT_METHOD_ID; supplies receipt method context.
• RA_CUSTOMER_TRX_ALL — The invoice source from which selection criteria ultimately draw candidate records.
• FND_CONCURRENT_REQUESTS — Linked through REQUEST_ID for process tracking.