Results for “ar_posting_control”

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

Overview

AR_POSTING_CONTROL is a Receivables (AR) module table that stores the details of each General Ledger Interface submission. Every time the Receivables subledger transfers accounting entries to the General Ledger, a controlling record is created in this table, allowing the application to track the posting lifecycle — including submission of the transfer, execution of the General Ledger journal import, and the eventual posting of the journal to the GL period. It is a transactional control table rather than a master setup table.

In heuristic Data Vault terms, the FK structure suggests a hub-leaning classification, since the table's primary key (POSTING_CONTROL_ID) is referenced by an unusually large number of child tables, making it a genuine business key hub around which many dependent satellites and links revolve. This classification should be treated as a modeling suggestion, not a documented designation.

Key Information Stored

The table is documented with 19 columns. The most significant include:

• POSTING_CONTROL_ID — the surrogate primary key, backed by unique index AR_POSTING_CONTROL_U1 and the constraint AR_POSTING_CONTROL_PK. It is also the business-key candidate, so it is the value propagated into all dependent FK columns.
• INTERFACE_RUN_ID — identifies the specific GL Interface run associated with this control record.
• ARGLTP_REQUEST_ID, ARGCGP_REQUEST_ID, GLLEZL_REQUEST_ID — concurrent request IDs for the Receivables transfer, the GL cost grouping process, and the GL journal import (GLLEZL) respectively.
• START_DATE and POST_THRU_DATE — the date range of transactions included in the submission.
• STATUS, REPORT_ONLY_FLAG, RUN_GL_JOURNAL_IMPORT_FLAG — flags and status codes indicating whether the run was report-only or actually submitted for GL posting.
• GL_POSTED_DATE — the date the resulting journal was posted in the General Ledger.
• CODE_COMBINATION_ID_GAIN and CODE_COMBINATION_ID_LOSS — the accounting flexfield combinations used to book exchange gain and loss arising from the posting.
• Standard audit columns CREATED_BY, CREATION_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID support EBS audit and concurrent program tracking.

Common Use Cases and Queries

The most common diagnostic scenario is determining whether a specific GL Interface run completed successfully. A representative query joins this table to the GL interface request identifiers:

SELECT posting_control_id, interface_run_id, status,
       gl_posted_date, start_date, post_thru_date
  FROM ar_posting_control
 WHERE interface_run_id = :run_id;

Reconciliation reporting often filters on REPORT_ONLY_FLAG and RA_GL_JOURNAL_IMPORT_FLAG to identify runs submitted in report-only mode, or on GL_POSTED_DATE to confirm the accounting date on which the journal reached the GL. Subledger accounting and cash-basis analyses frequently join POSTING_CONTROL_ID to child distribution tables to trace how each accounting line was posted. Analysts also use the GAIN/LOSS code combination columns to review exchange rate adjustments captured at posting time.

Related Objects

AR_POSTING_CONTROL is a hub referenced by a very large number of downstream tables. The most significant relationships include:

• RA_CUSTOMER_TRX_ALL and RA_CUST_TRX_LINE_GL_DIST_ALL — transactions and their GL distributions, both joined on POSTING_CONTROL_ID.
• AR_CASH_RECEIPT_HISTORY_ALL — joined on both POSTING_CONTROL_ID and REVERSAL_POSTING_CONTROL_ID.
• AR_RECEIVABLE_APPLICATIONS_ALL — application accounting lines.
• AR_ADJUSTMENTS_ALL, AR_MISC_CASH_DISTRIBUTIONS_ALL, AR_RATE_ADJUSTMENTS_ALL, AR_CASH_BASIS_DISTS_ALL — adjustment, miscellaneous cash, rate adjustment, and cash-basis distributions.
• AR_TRANSACTION_HISTORY_ALL — transaction history postings.
• AR_POSTING_REPORT_INTERIM — interim reporting table joined on POSTING_CONTROL_ID.
• Multiple multi-currency (AR_MC_*) and localization (PSA_*, IGS_*, JL_BR_*) tables that carry POSTING_CONTROL_ID as a foreign key.