My Oracle Support Banner

GLXFCXLT Error: FRM-41830 List of values contain no entries, When Select The Period in Translate Balances Form (Doc ID 2631085.1)

Last updated on JANUARY 28, 2020

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.
GLXFCXLT.fmb

Symptoms

After defining a new ledger, attempt to translate the first ever period of the ledger. Receive the following error when try to select the period in the Translate Balances form (GLXFCXLT):

ERROR
-----------------------
FRM-41830 List of values contain no entries

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to General Ledger Super User responsibility.
2. Setup a new ledger, open the first period ever for the ledger and enter/post journal entries for this period.
3. Define and attempt to run translation. 

The following items were checked to determine if they were impacting the issue:
1) This issue is only being seen in this ledger, other ledgers being translated do not have this issue.
2) This period that is needing to be translated is open.
3) The period that is needing to be translated does have posted journal entries and balances that can be translated.
4) The period prior to this first ever period is defined in the calendar.
Even though this is the first ever period of the ledger, it can be translated as the period prior to the period needing to be translated is defined.
See  Bug 2968869 - TRANSLATION CAN BE RUN FOR THE FIRST OPEN PERIOD WHEN IT SHOULD NOT BE POSSIBLE
Development notes in this bug "Translation should work for the first opened period as long as the period that is immediately before the first open period is defined".

5) As per note GLXFCXLT Translation Balances: Period with Open Status Not Available in Period List of Values (LOV) for Translation (Doc ID 1930347.1)
verified that the period end and period average rates were defined for the rate types selected in the Accounting Setup Manager (ASM).
   a. The rate types defined to be used can be verified via output from: EBS General Ledger Analyzer (Doc ID 2117528.1) This output will also provide the conversion_type value for these rate types that can be used
       to verify the rates are defined.
   b. The following sql can be used to verify rates are defined as needed:
     select *
     from GL_DAILY_RATES
     where CONVERSION_TYPE in ('&ConversionType1','&ConversionType2')
     and FROM_CURRENCY = '&fromCurrency'
     and TO_CURRENCY = '&toCurrrency'
     and CONVERSION_DATE = 'DD-MON-YY';

 6) Verified that the period was not previously translated for any BSV used in the ledger, see: While Running Translation, Period field not showing the complete Period Names in the LOV (List of Values) (Doc ID 2001072.1).
     and How To Find Out The First Ever Translated Period? (Doc ID 780084.1):

     select * from GL_TRANSLATION_TRACKING
     where LEDGER_ID = &ledger_id
     and TARGET_CURRENCY = '&target_currency'
     and AVERAGE_TRANSLATION_FLAG = 'N'
     and ACTUAL_FLAG = 'A';    

7) The data access set being used as full access to the ledger, journals can be viewed for this ledger using the same responsibility and user attempting to submit the translation.

8) Form trace provided the list of values (LOV) query, which was run and provide the periods needing to be returned by the form:
   
    select ps.period_name, ps.period_year, ps.period_num,ps.end_date-ps.start_date max_rollback, ps.End_Date
    from gl_period_statuses ps, gl_ledgers l
    where ps.ledger_id = &ledger_id
    and l.ledger_id = &ledger_id
    and ps.application_id = 101
    and ps.closing_status not between 'F' and 'N'
    and ps.effective_period_num >= ( select nvl(max(nvl(gltt.earliest_ever_period_year,0)*10000 + nvl(gltt.earliest_ever_period_num,0)), 0) from gl_translation_tracking gltt where gltt.ledger_id = &ledger_id and gltt.target_currency = '&targert_currency'' and gltt.actual_flag = 'A' and gltt.average_translation_flag = 'N' )
    ORDER BY ps.period_year Desc, ps.period_num Desc;

 None of these items were found to be an issue on why the list of values was not returning the expected period.



Changes

 Added a new ledger, attempting to translate the first ever opened period for the ledger for the first time.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.