Results for “output_program_id”

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

Overview

JL_BR_AR_REMIT_BORDEROS_ALL is a Latin America Localizations (JL) table that stores the concurrent program request identifiers associated with formatted Brazilian bank transfer batches (borderôs). In the Oracle EBS 12.1.1 and 12.2.2 environments, this table acts as the bridge between the Accounts Receivable remittance process and the formatted output generated for bank submission. Each row records that a specific borderô was processed by an output program, capturing the request ID returned by the concurrent manager for that formatting run. This allows users, reports, and follow-up processes to trace a formatted remittance file back to the exact concurrent request that produced it.

From a Data Vault modeling perspective (heuristic, mined from the foreign key structure), this object is classified as a link. It resolves a relationship between two business entities—the bank transfer batch (borderô) and the output program—rather than storing descriptive attributes of a single entity. The presence of a single-column primary key, FORMAT_REQUEST_ID, positions the table as a request-tracking link keyed on the concurrent request identity.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• FORMAT_REQUEST_ID — The primary key (JL_BR_AR_REMIT_BORDEROS_ALL_PK) and the sole unique-index business-key candidate (JL_BR_AR_REMIT_BORDEROS_U1). It holds the concurrent request identifier of the formatting job. This is the column users search for when tracing a formatted bank file.
• BORDERO_ID — Foreign key to JL_BR_AR_BORDEROS_ALL, identifying the specific bank transfer batch (borderô) that was formatted.
• OUTPUT_PROGRAM_ID — Foreign key to AP_PAYMENT_PROGRAMS, identifying the output program used to produce the formatted file.
• ORG_ID — The operating unit (organization) that owns the remittance record, supporting multi-org security and data segregation.
• LAST_UPDATE_DATE / CREATION_DATE — Standard audit timestamps recording when the row was created and last modified.
• LAST_UPDATED_BY / CREATED_BY — Standard audit columns identifying the application user who created or updated the record.
• LAST_UPDATE_LOGIN — The login associated with the most recent update, used for audit tracking.

The surrogate identity of the row is FORMAT_REQUEST_ID itself, which doubles as the business key candidate; there is no separate meaningless sequence column documented. The remaining columns are standard WHO-style audit and organization context attributes.

Common Use Cases and Queries

The primary operational use is reverse-traceability: given a request ID, identify which borderô and output program were involved, or given a borderô, find the formatting requests that processed it. Typical queries include:

• Retrieve the borderô tied to a formatting request:
  SELECT BORDERO_ID, OUTPUT_PROGRAM_ID, ORG_ID FROM JL_BR_AR_REMIT_BORDEROS_ALL WHERE FORMAT_REQUEST_ID = :request_id;
• List all formatting requests for a specific batch:
  SELECT FORMAT_REQUEST_ID, OUTPUT_PROGRAM_ID, CREATION_DATE FROM JL_BR_AR_REMIT_BORDEROS_ALL WHERE BORDERO_ID = :bordero_id ORDER BY CREATION_DATE DESC;
• Audit reporting joining to concurrent request metadata or to JL_BR_AR_BORDEROS_ALL to show batch names alongside request IDs for a given operating unit.

These patterns support troubleshooting of failed or re-run bank file generation, reconciliation of remittance output to request logs, and operational dashboards tracking formatting activity by organization.

Related Objects

• JL_BR_AR_BORDEROS_ALL — joined via JL_BR_AR_REMIT_BORDEROS_ALL.BORDERO_ID; the parent bank transfer batch definition.
• AP_PAYMENT_PROGRAMS — joined via JL_BR_AR_REMIT_BORDEROS_ALL.OUTPUT_PROGRAM_ID; the output program responsible for formatting.
• FND_CONCURRENT_REQUESTS — implicitly related through FORMAT_REQUEST_ID, providing request status, phase, and completion details for the formatting job.
• JL_BR_AR_REMIT_BORDEROS_ALL_PK / _U1 — the primary key constraint and unique index enforcing request-level uniqueness.

Together these objects allow full navigation from a formatting request to its originating borderô, its output program, and its execution status within the concurrent manager.