My Oracle Support Banner

CHK_FIF_GL_CRS_RF_TRAN_REF_NO Constraint Not Allowing New Custom Transaction Codes To Use TRAN_REF_NO (Doc ID 2428284.1)

Last updated on AUGUST 01, 2018

Applies to:

Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.

Goal

The constraint CHK_FIF_GL_CRS_RF_TRAN_REF_NO on FIF_GL_CROSS_REF table does not allow new custom transaction codes to use tran_ref_no. The tran codes are hard coded into the constraint:

(tran_code in (37,38,63,64,87,88) and tran_ref_no is not null) or tran_code in (22,23) or (tran_code not in(22,23,37,38,63,64,87,88) and tran_ref_no is null)

What is the reason of this constraint?

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.