Orphan Events Created in XLA_EVENTS When a Credit Memo is Deleted Or Updated to a Zero Dollar Amount (Doc ID 1677210.1)

Last updated on AUGUST 03, 2017

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

You are attempting to delete or zero out Credit Memos taht are interfaced from OKS and the Events are created in XLA_EVENTS table and the status code: EVENT_STATUS_CODE is updated.

1. You 'zero out' a credit memo in the AR table
2. You delete a credit memo in the AR table

When either of these two actions occur, events are created in the Subledger Accounting Events table, XLA_EVENTS, and retain the following status codes:
EVENT_STATUS_CODE: U or I
PROCESS_STATUS_CODE: U or I

After the 'Submit Accounting' concurrent program is run, these events never get pushed all the way through to the Subledger Accounting layer and, when the 'Subledger Period Exceptions Report' is run in AR, they appear in the output.

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