Results for “status_lookup_code”

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

Overview

AR_TRANSMISSION_FORMATS is a Receivables (AR) setup and configuration table that stores lockbox transmission format definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. A transmission format describes how data from a bank lockbox file is parsed and interpreted when it is loaded into Receivables through the AutoLockbox process. Each row defines a named format that is referenced when a transmission is processed, giving the application the structural rules required to map incoming bank file content to receipt records.

The object resides in the AR schema and is classified as VALID. Based on the foreign key topology, the heuristic Data Vault classification is hub-leaning: AR_TRANSMISSION_FORMATS functions as a central reference dictionary from which dependent format-detail and transmission objects derive their identifiers. This classification is a modeling suggestion only; in practice the table serves as a configuration master whose surrogate identifier is disseminated across several child and referencing tables.

Key Information Stored

The table contains 27 documented columns. The most important are:

• TRANSMISSION_FORMAT_ID — the surrogate primary key (AR_TRANSMISSION_FORMATS_PK). It uniquely identifies each format and is the column propagated to dependent tables.
• FORMAT_NAME — the user-facing unique name of the transmission format. It is a documented business-key candidate (UK1).
• DESCRIPTION — free-text explanation of the format's purpose or origin.
• STATUS_LOOKUP_CODE — controlled status value indicating whether the format is active or inactive.
• ZD_EDITION_NAME — the editioning column introduced by the 12.2 online patching architecture; it participates in the unique index AR_TRANSMISSION_FORMATS_U1 alongside TRANSMISSION_FORMAT_ID.
• ZENGIN_CHAR_SET — character set configuration associated with the format, relevant to bank file encoding.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, available for customer-specific extension.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking record provenance.

Two unique indexes serve as documented business-key candidates: UK1 on FORMAT_NAME, and U1 on (TRANSMISSION_FORMAT_ID, ZD_EDITION_NAME), the latter reflecting the edition-aware uniqueness model of 12.2.2.

Common Use Cases and Queries

Typical usage centers on identifying which formats are defined, which are active, and what structures they contain. A common listing query is:

• SELECT transmission_format_id, format_name, status_lookup_code FROM ar.ar_transmission_formats ORDER BY format_name;
• Joining to dependent format-detail tables to inspect a format's record and field definitions, for example joining on TRANSMISSION_FORMAT_ID to AR_TRANS_RECORD_FORMATS and AR_TRANS_FIELD_FORMATS.
• Resolving the format applied to a given lockbox transmission by joining AR_TRANSMISSIONS_ALL.REQUESTED_TRANS_FORMAT_ID back to TRANSMISSION_FORMAT_ID.

Reporting use cases include auditing configured formats before lockbox file onboarding, validating active status prior to AutoLockbox runs, and generating inventories of formats with their DFF attribute values for implementation documentation.

Related Objects

The FK metadata identifies three dependent or referencing tables, each joined on TRANSMISSION_FORMAT_ID:

• AR_TRANSMISSIONS_ALL — references this table through REQUESTED_TRANS_FORMAT_ID, recording the format requested for each transmission.
• AR_TRANS_FIELD_FORMATS — references this table through TRANSMISSION_FORMAT_ID; holds field-level parsing definitions belonging to a format.
• AR_TRANS_RECORD_FORMATS — references this table through TRANSMISSION_FORMAT_ID; holds record-level structural definitions belonging to a format.

Together these children supply the granular parsing rules that the parent format governs, while AR_TRANSMISSIONS_ALL provides the runtime link between a submitted lockbox file and the chosen format. The 12.2.2 editioning column and unique index further tie this object into the online patching framework.