R12: GLXJEENT When Enter Journals Or Subledger Transactions Get "This balancing segment value is not valid for the current ledger" (Doc ID 437588.1)

Last updated on JANUARY 31, 2017

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.
Form:GLXJEENT.FMB - Enter Journals/Encumbrances


Symptoms

Symptom 1

A Balancing Segment Value (BSV) was assigned to a Legal Entity and a Start Date was set for that assignment.
Initially the BSV had a start date assigned and then this was changed. For instance from 12-Jun-2007 to 1-Jan-1996.
When entering journals in GL and transactions in the subledgers with a date prior to initial start date (12-Jun-2007), the following message appears:

               This balancing segment value is not valid for the current ledger.

Expected Behaviour:
Since the start date has been backdated it is expected that transactions for dates from the
new start date onwards can be created. The system seems to still look at the original start
date assigned.

Steps to Reproduce
1. Assign Balancing Segment Value to a Legal Entity for a Ledger with a particular start date.
2. Save this.
3. Change the start date for the BSV.
4. Try to create a manual journal for a period prior to the start date set in 1.
    When you enter the first journal line using the BSV, the system give this error.
Note: The error also occurs if creating transactions in the subledgers.

Query for Transactions in Payables and Receivables throws this error:

ID 01 for the flexfield segment COMPANY does not exist in the value set VALUSET_NAME

Symptom 2:

The same error can be happened when a new Legal entity and Balancing segment value (BSV) is assigned to the Ledger, but the Accounting setup program was not completed successfully.

Symptom 3

Same Error can happen when data in GL_LEDGER_SEGMENT_VALUES is not in sync with data GL_LEDGER_NORM_SEG_VALS.

Note : This error can happen in any form/page where user tries to select a specific Balancing segment value (BSV) in any module 

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