eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: AR.AR_POSTING_CONTROL

Object Details

Object Name:	AR_POSTING_CONTROL
Object Type:	TABLE
Owner:	AR
FND Design Data:	AR.AR_POSTING_CONTROL
Subobject Name:
Status:	VALID

The AR_POSTING_CONTROL table stores basic information about each batch of Oracle Receivables transactions that you transfer to either Oracle General Ledger or the GL_INTERFACE table. Each row includes information about the transfer, such as the General Ledger start and end dates. Oracle Receivables creates one row in this table each time that you submit the posting process.
.
The value that you enter for the RUN_GL_JOURNAL_IMPORT_FLAG column using the Run GL Journal Import parameter in the Run General Ledger Interface window determines which concurrent processes Oracle Receivables submits during the transfer process. If you set the RUN_GL_JOURNAL_IMPORT_FLAG column to Y by entering Yes in the Run GL Journal Import field, Oracle Receivables ensures that only one transfer request is submitted at one time.
.
The AR_POSTING_CONTROL table corresponds directly to the fields in the Run General Ledger Interface window. When you submit the transfer process through this window, Oracle Receivables locks all transaction records that were not transferred, that have GL_DATE values between the dates that you specify in the GL Start Date and GL End Date fields, and that have a null GL_POSTED_DATE column in the AR_CASH_RECEIPTS, AR_MISC_CASH_DISTRIBUTIONS, AR_RECEIVABLE_APPLICATIONS, AR_RATE_ADJUSTMENTS, AR_ADJUSTMENTS, RA_CUSTOMER_TRX, and RA_CUST_TRX_LINE_GL_DIST tables. Oracle Receivables generates a unique identifier in the POSTING_CONTROL_ID column for this batch of transactions. For each untransferred record, the Update Posting Control concurrent program inserts this value into the POSTING_CONTROL_ID columns of these tables.
.
If you set the RUN_GL_JOURNAL_IMPORT_FLAG column to N by entering No in the Run Journal Import parameter, the transferred transaction records from these tables that are within the General Ledger date range that you specify remain in the GL_INTERFACE table after they are loaded by the General Ledger Transfer program. Oracle Receivables uses these records to generate the Posting Execution report. Oracle Receivables also generates the Unposted Items report if there are items that you select for posting that are out of balance. The GLLEZL_REQUEST_ID column will be null because Oracle Receivables does not invoke the General Ledger Import program. You define the GL_POSTED_DATE column for these transactions through the GL Posted Date field in the Run General Ledger Interface window.
.
If you set the RUN_GL_JOURNAL_IMPORT_FLAG column to Y by entering Yes in the Run GL Journal Import parameter, Oracle Receivables transfers your batch of transaction entries to Oracle General Ledger via the GL_INTERFACE table. The General Ledger Import program transfers your journal entries to the General Ledger table from the GL_INTERFACE table. The GLLEZL_REQUEST_ID column stores the concurrent process request identifier of the General Ledger Import program that the General Ledger Transfer Program invokes after loading transaction records into the GL_INTERFACE table. The STATUS column indicates whether Oracle Receivables has completed the transfer process for a batch or not.
.
When you transfer a batch of transactions to Oracle General Ledger, the GL_JE_BATCHES table stores the POSTING_CONTROL_ID for this batch as part of a concatenated value in its NAME column.
.
The primary key for this table is POSTING_CONTROL_ID.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
AR_POSTING_CONTROL_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	POSTING_CONTROL_ID
AR_POSTING_CONTROL_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	STATUS

Columns

Name	Datatype	Length	Mandatory	Comments
POSTING_CONTROL_ID	NUMBER	(15)	Yes	Posting program submission identifier
CREATED_BY	NUMBER	(15)	Yes	Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
CREATION_DATE	DATE		Yes	Standard who column - date when this row was created.
ARGLTP_REQUEST_ID	NUMBER	(15)	Yes	Concurrent request identifier of the ARGLTP posting program
ARGCGP_REQUEST_ID	NUMBER	(15)		No longer used
GLLEZL_REQUEST_ID	NUMBER	(15)		Concurrent request identifier of the General Ledger Journal Import program
START_DATE	DATE		Yes	General Ledger start date of items to be posted to General Ledger
POST_THRU_DATE	DATE		Yes	General Ledger end date of items to be posted to General Ledger
INTERFACE_RUN_ID	NUMBER	(15)		Sequence generated identifier for the General Ledger Journal Import program
REPORT_ONLY_FLAG	VARCHAR2	(1)	Yes	Indicates if posting was run in Report Only mode. Y for run in this mode. N for not run in this mode. Always set to N.
RUN_GL_JOURNAL_IMPORT_FLAG	VARCHAR2	(1)	Yes	Indicates if General Ledger Journal Import program was run. Y for program was run. N for program not run.
STATUS	VARCHAR2	(10)	Yes	Posting status, either running or done, for all processes, not just posting program
GL_POSTED_DATE	DATE		Yes	General Ledger date of posted items
CODE_COMBINATION_ID_GAIN	NUMBER	(15)		System parameter to identify account that exchange rate gains and losses are posted to
PROGRAM_APPLICATION_ID	NUMBER	(15)		Concurrent Program who column - application id of the program that last updated this row (foreign key to FND_APPLICATION.APPLICATION_ID).
PROGRAM_ID	NUMBER	(15)		Concurrent Program who column - program id of the program that last updated this row (foreign key to FND_CONCURRENT_PROGRAM.CONCURRENT_PROGRAM_ID).
PROGRAM_UPDATE_DATE	DATE			Concurrent Program who column - date when a program last updated this row).
REQUEST_ID	NUMBER	(15)		Concurrent Program who column - concurrent request id of the program that last updated this row (foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID).
CODE_COMBINATION_ID_LOSS	NUMBER	(15)		Code combination identifier of realized losses

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT POSTING_CONTROL_ID
,      CREATED_BY
,      CREATION_DATE
,      ARGLTP_REQUEST_ID
,      ARGCGP_REQUEST_ID
,      GLLEZL_REQUEST_ID
,      START_DATE
,      POST_THRU_DATE
,      INTERFACE_RUN_ID
,      REPORT_ONLY_FLAG
,      RUN_GL_JOURNAL_IMPORT_FLAG
,      STATUS
,      GL_POSTED_DATE
,      CODE_COMBINATION_ID_GAIN
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      REQUEST_ID
,      CODE_COMBINATION_ID_LOSS
FROM AR.AR_POSTING_CONTROL;

Dependencies

[top of page]

AR.AR_POSTING_CONTROL does not reference any database object

AR.AR_POSTING_CONTROL is referenced by following:

AR: AR_POSTING_CONTROL#