Results for “requested_lockbox_id”

2 results




Overview
Explore in AI Chat

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

Overview

AR_TRANSMISSIONS_ALL is the Oracle Receivables (AR) transaction table that stores lockbox transmission information. It records each lockbox transmission request created by the Automatic Lockbox program, capturing the batch of bank file data submitted for import into Receivables. Located in the AR schema, the table is central to the lockbox processing cycle: when a bank file is loaded, a transmission request is generated here, and the resulting receipt data flows into the payments interface tables and batches for validation and posting.

Based on the foreign key topology — the table anchors references from AR_BATCHES_ALL and AR_PAYMENTS_INTERFACE_ALL while itself referencing AR_LOCKBOXES_ALL and AR_TRANSMISSION_FORMATS — a heuristically derived Data Vault classification suggests this object behaves as a satellite-leaning entity. It carries descriptive and status attributes about a transmission event, tied to hub-like business keys. This classification is a modeling suggestion only, offered as an aid to warehouse design; the operational table remains a transactional table in the EBS data model.

Key Information Stored

The table contains 41 documented columns in ETRM 12.2.2. The surrogate primary key is TRANSMISSION_REQUEST_ID (AR_TRANSMISSIONS_PK), a system-generated identifier that uniquely tags each transmission request. Two unique indexes serve as business-key candidates: AR_TRANSMISSIONS_U1 on TRANSMISSION_ID, and AR_TRANSMISSIONS_U2 on the combination of TRANSMISSION_NAME and ORG_ID.

The most operationally significant columns include:

  • TRANSMISSION_REQUEST_ID — surrogate primary key, propagated into downstream interface and batch tables.
  • TRANSMISSION_ID — business identifier of the transmission, with a unique index; also used as a foreign key to AP_TRANSMISSIONS_SETUP.
  • TRANSMISSION_NAME — descriptive name of the transmission, part of the ORG_ID business key.
  • ORG_ID — operating unit context, required for multi-org query filtering.
  • TRANS_DATE and TIME — the date and time the transmission was requested or processed.
  • COUNT and AMOUNT — the total number of records and monetary amount submitted in the transmission.
  • VALIDATED_COUNT and VALIDATED_AMOUNT — totals successfully validated during lockbox processing.
  • STATUS — current state of the transmission request (for example, submitted, validated, or completed).
  • REQUESTED_LOCKBOX_ID — foreign key to AR_LOCKBOXES_ALL, identifying the lockbox for which the transmission was requested.
  • REQUESTED_TRANS_FORMAT_ID — foreign key to AR_TRANSMISSION_FORMATS, defining the bank file format.
  • REQUESTED_GL_DATE — the general ledger date requested for the resulting accounting entries.
  • LATEST_REQUEST_ID — pointer to the most recent related request, useful for tracking retries or follow-up transmissions.
  • ORIGIN, DESTINATION, COMMENTS — free-form and routing context for the transmission.
  • SOURCE_TYPE_FLAG and SCORING_MODEL_ID — control fields governing processing behavior and any scoring model applied.
  • ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for customer-specific extensions.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include monitoring lockbox transmission status, reconciling counts and amounts submitted against validated totals, and auditing transmissions by operating unit or lockbox.

A simple status report for a given operating unit might resemble:

  • SELECT transmission_name, trans_date, status, count, amount, validated_count, validated_amount FROM ar_transmissions_all WHERE org_id = :org_id AND trans_date >= :from_date ORDER BY trans_date DESC;

Joining to the lockbox definition locates transmissions by bank lockbox:

  • SELECT t.transmission_name, l.lockbox_number, t.status, t.amount FROM ar_transmissions_all t, ar_lockboxes_all l WHERE t.requested_lockbox_id = l.lockbox_id AND t.org_id = :org_id;

Reconciliation against the payments interface links transmissions to the individual receipt lines awaiting processing:

  • SELECT t.transmission_name, p.* FROM ar_transmissions_all t, ar_payments_interface_all p WHERE t.transmission_request_id = p.transmission_request_id;

These patterns support operational dashboards, exception handling for failed validations, and audit trails of lockbox activity.

Related Objects

The table participates in a well-defined relationship graph in Oracle Receivables and adjacent modules:

  • AR_LOCKBOXES_ALL — joined on AR_TRANSMISSIONS_ALL.REQUESTED_LOCKBOX_ID = AR_LOCKBOXES_ALL.LOCKBOX_ID; identifies the lockbox receiving the transmission.
  • AR_TRANSMISSION_FORMATS — joined on REQUESTED_TRANS_FORMAT_ID; defines the bank file layout used.
  • AP_TRANSMISSIONS_SETUP — joined on TRANSMISSION_ID; transmission setup/configuration reference.
  • AR_BATCHES_ALL — references this table via TRANSMISSION_REQUEST_ID; groups receipts created from the transmission.
  • AR_PAYMENTS_INTERFACE_ALL — references this table via TRANSMISSION_REQUEST_ID; holds receipt lines pending validation and posting.
  • AR_PMTS_INTERFACE_HEADER_GT, AR_PMTS_INTERFACE_LINE_DETAILS, AR_PMTS_INTERFACE_LINES_GT — global temporary and detail structures that also reference TRANSMISSION_REQUEST_ID during lockbox import processing.

Collectively, these relationships make AR_TRANSMISSIONS_ALL the linking point between bank lockbox definitions, transmission formats, and the interface and batch structures that ultimately produce receipt records in Receivables.