Search Results generation_date




Overview
Explore in AI Chat

Overview

The view JL_BR_AR_SELECT_CONTROLS_V is an Oracle E-Business Suite (EBS) database object owned by the APPS schema within the JL – Latin America Localizations product family. It is classified as a VALID view and is documented as "Retrofitted," indicating that it was originally created under an earlier release and subsequently migrated or reconciled into the 12.1.1 / 12.2.2 code line without structural redesign. In the Brazilian receivables localization, a "selection control" represents a user-defined selection or grouping of transactions — for example, a Bordero (bank collection remittance batch) or a receipt selection — that drives receivable processing, remittance generation, and reporting.

The view presents selection-control header data alongside descriptive values resolved from related reference tables. Rather than exposing raw identifiers alone, it denormalizes lookup meanings, receipt method names, and transaction-type descriptions so that reports, concurrent programs, and integrations can consume fully readable records without additional joins. As a reporting and integration surface, it shields callers from the base JL_BR_AR_SELECT_CONTROLS table's lack of foreign-key descriptive columns.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

  • JL_BR_AR_SELECT_CONTROLS (SYNONYM) — the primary source of selection-control header rows.
  • AR_RECEIPT_METHODS (SYNONYM) — provides the receipt method name.
  • RA_CUST_TRX_TYPES (SYNONYM) — provides the transaction type description.
  • FND_LOOKUPS (VIEW) — supplies lookup meanings for the Bordero type and selection status.
  • FND_GLOBAL (PACKAGE) — typically referenced in the view's WHERE clause for org-level (multi-org) security context via FND_GLOBAL.ORG_ID.

The view text confirms that JL_BR_AR_SELECT_CONTROLS is aliased SC and joined to AR_RECEIPT_METHODS (RM), RA_CUST_TRX_TYPES (CTT), and two instances of FND_LOOKUPS (LV and LV2). Because the view exposes ORG_ID and depends on FND_GLOBAL, it behaves as a multi-org secured view.

Key Columns

The view returns selection-control identifiers and their operational attributes, including SELECTION_CONTROL_ID, SELECTION_STATUS, SELECTION_TYPE, NAME, BORDERO_TYPE, and the date columns SELECTION_DATE, CANCELLATION_DATE, GENERATION_DATE, REMITTANCE_DATE, INITIAL_DUE_DATE, and FINAL_DUE_DATE. Transaction and customer ranges are exposed through INITIAL_TRX_DATE/FINAL_TRX_DATE, INITIAL_TRX_NUMBER/FINAL_TRX_NUMBER, and INITIAL_CUSTOMER_NUMBER/FINAL_CUSTOMER_NUMBER, while amounts are bounded by INITIAL_TRX_AMOUNT and FINAL_TRX_AMOUNT.

Foreign keys such as CUST_TRX_TYPE_ID and RECEIPT_METHOD_ID are supplemented by descriptive columns: RECEIPT_METHOD_NAME, CUST_TRX_TYPE_ID_DSP, BORDERO_TYPE_DSP, and SELECTION_STATUS_MEANING. Standard DFF columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 are surfaced, along with audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. ORG_ID and REQUEST_ID link the record to its operating unit and originating concurrent request.

Common Use Cases and Queries

Typical uses include reconciliation of Bordero batches, status reporting on outstanding selections, and integration extracts feeding banking or treasury systems. A representative query:

  • SELECT SELECTION_CONTROL_ID, NAME, SELECTION_STATUS_MEANING, BORDERO_TYPE_DSP, RECEIPT_METHOD_NAME, SELECTION_DATE, FINAL_TRX_AMOUNT FROM JL_BR_AR_SELECT_CONTROLS_V WHERE TRUNC(SELECTION_DATE) BETWEEN :p_start AND :p_end;
  • SELECT SELECTION_CONTROL_ID, NAME, GENERATION_DATE, REMITTANCE_DATE FROM JL_BR_AR_SELECT_CONTROLS_V WHERE SELECTION_STATUS = :p_status AND ORG_ID = :p_org_id;

Because the view is multi-org secured and prefilters via FND_GLOBAL, callers should supply an operating unit context when querying directly or from ad hoc tools.