Search Results ar_posting_control




Overview
Explore in AI Chat

Overview

The AR_POSTING_CONTROL table is a core technical object within Oracle E-Business Suite Receivables (AR), specifically in versions 12.1.1 and 12.2.2. It functions as a central audit and control mechanism for the General Ledger (GL) Interface process. Each time a user submits a request to transfer accounting entries from Receivables to the General Ledger, a unique record is created in this table. This record tracks the status, parameters, and scope of that specific posting submission, ensuring data integrity and providing a critical link between the detailed accounting distributions and the batch job that created them. Its role is pivotal for reconciliation, troubleshooting posting errors, and understanding the posting history of transactions.

Key Information Stored

While the provided metadata does not list specific columns, the table's primary key is documented as POSTING_CONTROL_ID. This unique identifier is the foreign key referenced by numerous distribution and history tables. Based on its functional role, the table typically stores information such as the request ID of the concurrent program run, the posting date range (from and to dates), the set of books (ledger) posted to, the status of the posting run (e.g., pending, completed, error), the accounting mode (final or draft), and the user who initiated the submission. The POSTING_CONTROL_ID acts as a batch identifier, grouping all accounting distributions generated by a single posting execution.

Common Use Cases and Queries

This table is essential for technical and functional analysis of the GL transfer process. A primary use case is tracing the origin of accounting entries. For instance, to find which posting run created the GL distributions for a specific invoice, one would join from RA_CUSTOMER_TRX_ALL to AR_POSTING_CONTROL via POSTING_CONTROL_ID. Common diagnostic queries include identifying incomplete or errored posting runs or generating a summary report of all posting activity within a period. A sample query to list recent posting submissions would be:

  • SELECT posting_control_id, request_id, status_code, posting_date FROM ar_posting_control WHERE creation_date > SYSDATE - 30 ORDER BY posting_control_id DESC;

It is also critical for audit purposes, providing a definitive record of when and how revenue and cash receipts were recognized in the general ledger.

Related Objects

As evidenced by the extensive foreign key relationships in the metadata, AR_POSTING_CONTROL is a parent table to a wide array of Receivables subledger accounting tables. Key dependent objects include:

This network of relationships underscores the table's central role in anchoring the entire posted accounting data model within Oracle Receivables.