Results for “output_program_dsp”

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

Overview

The view JL_BR_AR_BORDEROS_SAB_V is an Oracle E-Business Suite database object owned by the APPS schema and categorized under the JL – Latin America Localizations product family. It is a reporting and integration view that exposes Brazilian receivables borderô (bank remittance or collection batch) records together with their translated lookup meanings and associated payment program information. The view is documented as retrofitted, meaning it was migrated or regenerated to remain compatible with the 12.1.1 and 12.2.2 technology stacks while preserving the legacy interface expected by the Brazilian localization code and downstream reports.

The suffix _SAB_V follows the convention used for Brazilian localization "SAB" (Selection And Bordero) views that support the collection and factoring bordero processing flows. Its principal role is to provide a denormalized, lookup-enriched projection of the base bordero table so that forms, concurrent programs, and external integrations can present human-readable status, type, and media descriptions without joining to FND_LOOKUPS themselves.

Underlying Base Objects

Per the ETRM metadata, the view references the following documented base objects:

• JL_BR_AR_BORDEROS (referenced via a synonym) — the primary base table holding bordero header records, aliased as B.
• AP_PAYMENT_PROGRAMS (referenced via a synonym) — joined to retrieve the friendly program name (OUTPUT_PROGRAM_DSP) for the program that generates the bordero output media.
• FND_LOOKUPS (a view) — joined multiple times (LV, LV1, LV2) to decode the bordero type, remittance output format, and bordero status into displayable meanings.
• FND_GLOBAL (a package) — used to supply runtime environment context such as the operating unit (ORG_ID) in the standard EBS multi-org pattern.

The joins to JL_BR_AR_BORDEROS are the driving set; the lookups and payment programs are all outer or validated joins that restrict rows to enabled, date-effective lookup values (ENABLED_FLAG = 'Y', with active-date windows enforced via START_DATE_ACTIVE / END_DATE_ACTIVE).

Key Columns

The view projects the full identifying and status columns of the bordero, including:

• BORDERO_ID, SELECTION_CONTROL_ID, BANK_ACCT_USE_ID — primary keys and foreign keys identifying the bordero, its selection control, and the bank account used.
• BORDERO_STATUS and BORDERO_STATUS_DSP — the coded status and its lookup meaning. Records where status equals CANCELED are excluded by the view definition.
• BORDERO_TYPE and BORDERO_TYPE_DSP — restricted to COLLECTION and FACTORING types.
• WRITE_OFF_DATE — the date on which the bordero receivable was written off, a key audit field relevant to the user query context.
• SELECTION_DATE, REMITTANCE_DATE, REFUSED_DATE, CANCELLATION_DATE, COLLECTION_DATE, DATE_IN_RECEIPT, RECEIVED_DATE — the lifecycle date milestones of the bordero.
• TOTAL_COUNT, TOTAL_AMOUNT — aggregated item count and monetary total.
• OUTPUT_PROGRAM_DSP, OUTPUT_FORMAT_DSP — decoded output program name and remittance media format.
• ORG_ID and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The view is typically queried to report bordero status and to reconcile write-offs. A representative query returning written-off borderos within an operating unit is:

• SELECT bordero_id, bordero_type_dsp, bordero_status_dsp, total_amount, write_off_date FROM jl_br_ar_borderos_sab_v WHERE org_id = :p_org_id AND write_off_date IS NOT NULL ORDER BY write_off_date;

Other common scenarios include listing all active collection borderos by bank account, extracting remittance media formats for a given output program, and feeding bordero data into Brazilian bank return-file processing. Because the view resolves lookup meanings internally, it is well suited to ad-hoc reporting and to integration interfaces that require descriptive status text rather than internal codes.