IM_RECEIPT_ITEM_POSTING_STAGE Table Never Gets Purged (Doc ID 746682.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Retail Invoice Matching - Version 12.0 to 12.0.9 [Release 12.0]
Information in this document applies to any platform.
Checked Sept-2014

Symptoms

When AutoMatch is run, the system automatically posts matched invoice data as a feature of the AutoMatch process. During matching, posted receipt records are written to the tables IM_RECEIPT_ITEM_POSTING and IM_RCPT_ITEM_POSTING_INVOICE. When posting occurs, this data is moved to the IM_RECEIPT_ITEM_POSTING_STAGE and IM_RCPT_ITEM_POSTING_INV_STAGE tables.

These staging tables facilitate receipt tracking for the retailer in order to assist in reporting. The data in IM_RECEIPT_ITEM_POSTING_STAGE and IM_RCPT_ITEM_POSTING_INV_STAGE tables is never purged. The purging process in Invoice Matching (ReIM),  BatchPurge, also does not purge these tables.

Expected Results
The two tables IM_RECEIPT_ITEM_POSTING_STAGE and IM_RCPT_ITEM_POSTING_INV_STAGE should be purged.

Application Impact
When the size of the table IM_RECEIPT_ITEM_POSTING_STAGE becomes very large, AutoMatch performs poorly.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms