R12 GLAMAS Mass Allocation Fails with Warning When No Journal Is Created But in R11i the Behavior Was Different It Did Not Fail (Doc ID 1467044.1)

Last updated on JANUARY 06, 2016

Applies to:

Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.
Executable:GLAMAS - Run MassAllocations

Symptoms

In Rel 12i - GLAMAS - Run MassAllocation program ends in warning.

The output file shows the journal was not created for a specific reason ( say E -- invalid code combination id)

    Journals Not Created:
    Formula Name                            Error   Ledger               Accounting Flexfields
    --------------------------------------- ------- -------------------- ------------------------------------------------------------
    TEST FORMULA                             E       TEST LEDGER     10000.8888.99999.11.411.5570.99999.9999.999999         
 
 
 
Error:
A: Write access is not available to ledger/ledger set in the Target and Offset Lines.
B: Invalid ledger/balancing segment value combination.
C: Invalid ledger/management segment value combination.
D: No journal was created because accounts for allocation basis have zero or no balances.
E: Invalid code combinations id.
F: Flexfield with parent segment value is not allowed.
G: Failed to create a new code combinations id.
 

In Rel 11i -- a journal not being created -- did not cause the mass allocations program to end in error.
It ended normally.

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