When mapping a primary ledger to secondary ledger can you map a non balancing segment to a

balancing segment [ID 1261566.1]

  Modified 29-NOV-2010     Type HOWTO     Status  

PUBLISHED

In this Document
  Goal
  Solution
  References

Applies to:

Oracle General Ledger - Version: 12.1.1 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.

Goal

You have a Primary Ledger  and Secondary Ledger 

Both have same chart of account structure, except for the flexfield qualifier.
Company - Department - Account - Product

In the primary ledger, the first segment 'company' is the Balancing segment.

In the secondary ledger, second segment 'Department' is the balancing segment

1) can we have different chart of accounts in the primary ledger and secondary ledger
2) Can we have different balancing segments for the primary ledger and secondary ledger
3) how do we map this primary ledger to this secondary ledger

Solution

1) can we have different chart of accounts in the primary ledger and secondary ledger
Answer:  Primary and secondary ledgers can have different Chart of Accounts

2) Can we have different balancing segment for the primary ledger and secondary ledger 
Answer:  since you can have a different chart of accounts,  you can have a different balancing segments

3) how do we map this primary ledger to this secondary ledger.

There is a restriction when it comes to mapping the primary ledger to the secondary ledger.
The restriction is that you cannot map a non balancing segment in the primary ledger to a balancing
segment in the secondary ledger

If you attempt to do this,  the posting program is likely to fail with

SHRD0181: glpvsl() - gl_accounts_map_grp.map ret_status = S
SHRD0180: glpvsl() - Performing action >> open cursor get_err_ccid...
SHRD0026: Current system time is: 22-OCT-2010 12:51:50
SHRD0180: glpvsl() - Performing action >> Following accounts Does not having mapping accounts in
Target Ledger...
SHRD0026: Current system time is: 22-OCT-2010 12:51:50
SHRD0180: glpvsl() - Performing action >> upd_coamap_error_headers...
SHRD0026: Current system time is: 22-OCT-2010 12:51:50
SHRD0118: Updated 0 record(s) in table: GL_JE_HEADERS
SHRD0118: Updated 0 record(s) in table: GL_JE_BATCHES
SHRD0117: Inserted 0 record(s) into GL_ACCTS_MAP_BSV_GT
SHRD0181: glpvsl() - gl_accounts_map_grp.bsv ret_status = E
PPOS0270: Posting was terminated. The following chart of accounts mapping is disabled or invalid:
&COAMAP. Correct the chart of accounts mapping and then rerun posting.
...
PPOS0002: Posting terminated with fatal errors

Why this restriction:

The original journal (in the primary ledger) is balanced.
Now when you try to post the journal in the primary ledger,
it will try to map the accounts from Source to Target using the mapping rules defined,
to create a journal in the secondary ledger that will be posted too.

But based on these mapping rules (mapping of a non balancing segment to a balancing segment)
the resulting lines in the secondary ledger may not balance by balancing segment.
[because data is coming from a non balancing segment in the primary ledger]

This scenerio is not presently supported in GL.