Code Combinations for Segment Hierarchies

Question

Dear Members,
I have one question on Hierarchies in GL Accounting Flex fields. I read the documentation on Flexfield hierarchies, in which its said that generally hierarchies are used for only GL accounting flexfields.
Suppose One of the Accounting Flexfield Segment Value hierarchy structure is like this :
1000
_________|_______
100 200 300
____|____ ____|______
101 102 301 302 303
_______|______
303A 303B 303C
__|__
303BB
This hierarchy is not coming properly when i post it so i am explaining it in detail here :
Parent Child
1000 ---> 100 200 300
100 ----> 101 102
300 ---> 301 302 303
303 ---> 301A 303B 303C
303B --> 303BB
Here 1000 is the parent which has childs and they inturn have childs. This is used maily for reporting purpose in GL. I do not understand how a code combination is generated for the above structure in gl_code_combination table.
Suppose we have 5 segments in our accounting flexfield structure
ex: seg1,seg2,seg3,seg4,seg5 and 1000 in the above mentioned structure is seg3.
how does a combination is generated if we want the information pertaining to 303BB which is the leaf node value in the hierarchy.
seg1.seg2.seg3.seg4.seg5 --> how does this change if we have hierarchies.
It would be great if you can help me out in this.
Thanks
Sandeep
Message was edited by:
user340
Message was edited by:
user340
Message was edited by:
user340

Answer 1

Hi :
1000 is a parent ---> 100 200 300 are chid
100 is a parent ----> 101 102 are chid
300 is a parent ---> 301 302 303 are chid
303 is a parent ---> 301A 303B 303C are chid
303B is a parent --> 303BB
Here 1000 is the parent which has childs and they inturn have childs. This is used maily for reporting purpose in GL. I do not understand how a code combination is generated for the above structure in gl_code_combination table.
seg1,seg2,seg3,seg4,seg5 and 1000 in the above mentioned structure is seg3.
a combination is generated for every single combination oif child values (child valued should be posting allowed = yes meanwhile parent values should be posting allowed = no) for every segment
so at the end the combination is created whenever you use child value for every single segment
if you have rollup groups associated to the parent values, you can define summary accounts and balances are going to be automatically updated for parent values so even you can query onbalances on parent values
I hope this gives you some light