Account Mapping for Primary to Secondary Ledger gives GL_BSV_MAP_NOT_BSV_DERIVED (Doc ID 2094042.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Assets - Version 12.2.4 and later
Information in this document applies to any platform.
Accounting Setup Manager

Symptoms

Client has a Tax Book posting to a Secondary Ledger and is using an account mapping that maps a qualified segment to an unqualified segment.  One example of how this can work:

Primary GL Account setup:
 
GL# 1 Company        SEGMENT1 GL_BALANCING Y Y Y
GL# 2 Department     SEGMENT2 FA_COST_CTR Y Y Y
GL# 3 Account        SEGMENT3                        Y Y
GL# 4 Product Line   SEGMENT4                        Y Y
GL# 5 InterCompany   SEGMENT5 GL_INTERCOMPANY Y Y Y
GL# 6 Future         SEGMENT6                      Y Y
GL# 7 Local Use      SEGMENT7 GL_ACCOUNT         Y Y Y
 
Secondary GL Account Setup:
  
GL# 1 Company        SEGMENT1 GL_BALANCING Y Y Y
GL# 2 Department     SEGMENT2 FA_COST_CTR Y Y Y
GL# 3 Account        SEGMENT3 GL_ACCOUNT        Y Y Y
GL# 4 Product Line   SEGMENT4                Y Y
GL# 5 InterCompany   SEGMENT5 GL_INTERCOMPANY Y Y Y
GL# 6 Future         SEGMENT6                Y Y
GL# 7 Local Use       SEGMENT7               Y Y

Note that all is the same except that segment 7 is GL_ACCOUNT in the primary, but segment 3 functions that way in the Secondary.  Any variant of this, where the primary maps a qualified segment to an unqualified in the Secondary, will produce this issue.

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