Transaction Was Adjusted But the Original Transaction is Not Obsoleted. The Transaction Still Show as NEW Status and is not Picked up for Processing. (Doc ID 2224872.1)

Last updated on JANUARY 19, 2017

Applies to:

Oracle Fusion Incentive Compensation - Version 11.1.11.1.0 and later
Oracle Fusion Incentive Compensation Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Symptoms

There are two transactions with the same transaction number but one transaction is in NEW status and one is in CREDITING / CREDIT_ERROR.
When rerun Revert Transaction then Crediting again, it still did not process the transaction in NEW status.
This is causing the base actual amounts to be overstated.

Query to identify transactions :

select source_trx_number
, object_status
, transaction_id
, new_transaction_id
, creation_date
, created_by
, last_update_date
, last_updated_by
, preserve_credit_flag
, process_code
from cn_tp_transactions_all
where source_trx_number in (select source_trx_number
from cn_tp_transactions_all
where new_transaction_id is not null)
order by source_trx_number, object_status

Sample Output :

TRANSACTION_ID NEW_TRANSACTION_ID OBJECT_STATUS CHANGED_TRX_FLAG PRESERVE_CREDIT_FLAG CREATION_DATE          LAST_UPDATE_DATE       COLLECTION_STATUS REQUEST_ID ORG_ID SOURCE_EVENT_DATE
4852111             7456529                      CREDIT_ERROR    N                                                           2016-08-05 06:04:44.0 2017-01-13 13:48:31.0 NO_ERROR    292336 300000002615033 2016-01-31 00:00:00
7456529                                               NEW                    Y                                                           2016-08-31 14:18:43.0 2016-08-31 14:18:43.0 NO_ERROR    124672 300000002615033 2016-01-31 00:00:00

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