The balancing segment value is not valid for the ledger

This error could happen when importing journals and posting journals.

The below notes from Oracle website:
------------------------------------------------------------------------------------------
To implement the solution, please execute the following steps:
Run the following sql to check if the balancing segment value exists in the tables.This will show if the balancing segment value does not exist in the gl_ledger_norm_seg_vals table, which means that the flattening program "General Ledger Accounting Setup Program", which is triggered when the Accounting setup is completed for Ledger, is not called or it errors out, the data is not populated completely in GL_LEDGER_SEGMENT_VALUES and hence it will not be in sync with GL_LEDGER_NORM_SEG_VALS and a data fix may be required.

If the sql in step 6 does not show all the BSV's that are shown by the sql in step 7 or the accounting setup manager screen for balancing segment values, then there might be a problem with the flattening program.

1. select * from gl_ledgers where ledger_id =&ledger_id ;

2. select * from gl_ledger_configurations where configuration_id = configuration_id returned from step1;

3. select * from gl_ledger_config_Details where configuration_id = configuration_id returned from step1;

4. select * from gl_le_value_sets where legal_entity_id in
( select object_id from gl_ledger_config_details where configuration_id = configuration_id returned from step1
and object_type_code = 'LEGAL_ENTITY');

5. select * from gl_legal_entities_bsvs where legal_entity_id in
( select object_id from gl_ledger_config_details where configuration_id = configuration_id returned from step1
and object_type_code = 'LEGAL_ENTITY');

6. select * from gl_ledger_norm_seg_vals where ledger_id in
(select OBJECT_ID from gl_ledger_config_Details where configuration_id = configuration_id returned from step1
and object_type_code in ('PRIMARY','SECONDARY'))
or legal_entity_id in (select OBJECT_ID from gl_ledger_config_Details
where configuration_id = configuration_id returned from step1
and object_type_code in ('LEGAL_ENTITY') ) ;

7. select * from gl_ledger_segment_values where ledger_id in
(select OBJECT_ID from gl_ledger_config_Details where configuration_id = configuration_id returned from step1
and object_type_code in ('PRIMARY','SECONDARY'))
or legal_entity_id in (select OBJECT_ID from gl_ledger_config_Details
where configuration_id = configuration_id returned from step1
and object_type_code in ('LEGAL_ENTITY') ) ;

8. select * from gl_ledger_relationships;

Please raise a service request and upload the results of the above sql.Support will then ask for development to assist in providing a datafix based on the results of the above queries. There is no generic datafix, each datafix is unique to each customer.
------------------------------------------------------------------------------------------
Open a SR with Oracle is a painful process. You need to spend more time to give them the information not important or you have already provided.

We ended up resolving it by ourselves before Oracle sending us the data fix.

Case analysis:
The record for segment being complained exist in GL.GL_LEDGER_ENTITIES_BCVS, but not exist in GL.GL_LEDGER_NORM_SEG_VALS and GL.GL_LEDGER_SEGMENT_VALUES tables. Which should be the reason described above: the flattening program "General Ledger Accounting Setup Program" which is triggered when the Accounting setup is completed for Ledger, is not called or it errors out.

Workaround/Solution: Delete that record in GL.GL_LEDGER_ENTITIES_BCVS table and redo the setup for that balancing segment (accounting setup)

Responsibility: GL SuperUser.Setup -> Financials -> Accounting Setup Manager -> Accounting Setup
Under Ledger,click on Update Accounting Options:
Click on Updating Balancing Segment Values
Then Add Balancing Segments Value

View requests to make sure all concurrent programs finish with no error.

[平安是福mtl]

回複九月豆的評論:

九妹，目的達到了。嗬嗬。。。

問好！

[九月豆]

I'm so confused, 雲裏霧裏啊，嘻嘻～～

早安，平安！～～