GLXCODEF When run Consolidation the Consolidation Mapping Rules do not Map the Accounts as Expected (Doc ID 125945.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle General Ledger - Version 11.5.10.2 and later
Information in this document applies to any platform.
Form:GLXCODEF.FMB - Consolidation Mappings

Symptoms

Users ran a consolidation and the accounts do not appear to be mapped as expected.

Definition for Consolidation mapping:

  Responsibility = General Ledger Super User
  GUI Navigation = Consolidation/Define/Mapping
  GUI Form Name = Consolidation Mapping (GLXCODEF)

  Click on the [Segment Rules] button and define the mapping as follows:

       Parent            Action             Subsidiary
       --------------------------------------------
       Segment 1         Copy Value         Segment 1
       Segment 2         Copy Value         Segment 2
       Segment 3         Not assigned     
       Segment 4         Copy Value         Segment 4
       Segment 5         Copy Value         Segment 5

  Click the [Account Rules] button and assign a range of subsidiary accounts to be mapped to a parent account code combination in the parent set of books.  

When running the consolidation, the range of subsidiary accounts map to that specific parent account code combination defined in the Account Rule, not the value intended. 

Changes

 

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