ChRM Claim Reversals Created Via API OZF_Claim_PUB.Create_event() are Not Being Processed by Sub-Ledger Accounting (SLA) Program

(Doc ID 1557270.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Trade Management - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Implemented the API OZF_Claim_PUB.Create_event() to create Reversal Event.  The Subledger Accounting (SLA) program fails to process reversal event of a claim when the normal event of the same claim belongs to a closed period. 


The public API OZF_Claim_PUB.Create_event() used to create SLA events for Claims.

• To create normal event, user has to pass valid CLAIM_ID and EVENT_TYPE_CODE to the AP1
• To create reversal event, apart from CLAIM_ID and EVENT_TYPE_CODE, REVERSAL_FLAG is also mandatory (which is Y).

Reversal Events are not being picked up by SLA.

Examples:

The events are not picked up by the program.

1453419 682 CLAIM_SETTLEMENT_REVERSAL 2/17/2013
1453423 682 CLAIM_SETTLEMENT_REVERSAL 2/18/2013

The Subledger Accounting - Create Accounting program fails with error message: "The GL date 10-FEB-2013 is not in an open or a future enterable period. Please select a valid GL date or open the period."

 

Changes

Applied <patch 16215152>

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