|
|
How to Identify Account Code Combinations That Are Misclassified And Have An Account_type Different From Account (文档 ID 259210.1) |
转到底部
|
|
Applies to:
Oracle General Ledger - Version 11.5.10.2 and laterInformation in this document applies to any platform.
Goal
How to identify account code combinations which have a different account_type to that defined in the Account Flexfield Segment Value, in order to prevent balance problems related to misclassified accounts in the beginning of a new year?
Solution
The following script should be able to identify the misclassified code combinations.
You need to enter the set of books short name (sobname) and the segment
number representing the position of the account segment (segnum).
select
c.chart_of_accounts_id coa,
c.concatenated_segments code_combination,
c.code_combination_id ccid,
c.gl_account_type type_is,
substr(v.compiled_value_attributes,5,1) should_be
from
gl_code_combinations_kfv c,
fnd_flex_values v,
fnd_id_flex_segments s,
gl_sets_of_books b
where
b.short_name = '&SOBNAME' and
c.chart_of_accounts_id = s.id_flex_num and c.template_id is null and
c.chart_of_accounts_id = b.chart_of_accounts_id and
s.application_id = 101 and
s.id_flex_code = 'GL#' and
s.segment_num = &&SEGNUM and
s.flex_value_set_id = v.flex_value_set_id and
v.flex_value = c.segment&&SEGNUM and
c.gl_account_type != substr(v.compiled_value_attributes,5,1) ;
SELECT
c.chart_of_accounts_id coa,
c.concatenated_segments code_combination,
c.code_combination_id ccid,
c.gl_account_type type_is,
SUBSTR(v.compiled_value_attributes,5,1) should_be
FROM
gl_code_combinations_kfv c,
fnd_flex_values v,
fnd_id_flex_segments s,
gl_ledgers b
WHERE
b.short_name = '&LEDGERNAME' AND
c.chart_of_accounts_id = s.id_flex_num AND c.template_id IS NULL AND
c.chart_of_accounts_id = b.chart_of_accounts_id AND
s.application_id = 101 AND
s.id_flex_code = 'GL#' AND
s.segment_num = &SEGNUM AND
s.flex_value_set_id = v.flex_value_set_id AND
v.flex_value = c.SEGMENT&SEGNUM AND
c.gl_account_type != SUBSTR(v.compiled_value_attributes,5,1) ;
The identified code combinations need to be fixed before the
opening of the first period of the new year, otherwise you may need to
follow steps from Note:1050920.6
This sql identifies additional sets of books which may also need correcting :
glsob.short_name,
glsob.set_of_books_id
FROM gl_sets_of_books glsob
WHERE glsob.chart_of_accounts_id = &ChartOfAccountsId;
