溫馨提示×

溫馨提示×

您好，登錄后才能下訂單哦！

密碼登錄×
登錄注冊×
其他方式登錄
點(diǎn)擊 登錄注冊 即表示同意《億速云用戶服務(wù)條款》

HOW TO IDENTITY MISCLASSIFIED CCID

發(fā)布時間：2020-08-11 23:34:39 來源：ITPUB博客 閱讀：152 作者：chenshm329 欄目：大數(shù)據(jù) 

	
		

			
				

					
			
				How
 to Identify Account Code Combinations That Are Misclassified And Have 
An Account_type Different From Account (文檔 ID 259210.1)
			
			
				HOW TO IDENTITY MISCLASSIFIED CCID


	Applies to:


Oracle General Ledger - Version 11.5.10.2 and later

Information 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).




	Query for R11i:



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) ;  




	 




	Query for R12:



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 :




	SELECT glsob.name, 

glsob.short_name, 

glsob.set_of_books_id 

FROM gl_sets_of_books glsob 

WHERE glsob.chart_of_accounts_id = &ChartOfAccountsId;


            
            
向AI問一下細(xì)節(jié)

            
            

            

                
免責(zé)聲明：本站發(fā)布的內(nèi)容（圖片、視頻和文字）以原創(chuàng)、轉(zhuǎn)載和分享為主，文章觀點(diǎn)不代表本網(wǎng)站立場，如果涉及侵權(quán)請聯(lián)系站長郵箱：is@yisu.com進(jìn)行舉報，并提供相關(guān)證據(jù)，一經(jīng)查實(shí)，將立刻刪除涉嫌侵權(quán)內(nèi)容。

                
                
            

            
            
        
        
    


AI
助
手































    • <s id="66666"><source id="66666"></source></s>
    <kbd id="66666"></kbd>
    <strong id="66666"><sup id="66666"></sup></strong>
      •