Atribute Relation to be maintained in the Structure

Question

Hi All,
I need to knw about how do we maintain an attribute relation in a structure.
Like I have hierarchy maintained for Item, the hierarchy nodes are like below,
Total Product Revenue
             Product Revenue
             Other Revenue
Now in my second query, I create a structure similar to the item hierarchy and use it instead of Item in the rows.
When i execute these queries and drill down using GL Account along the rows then following are my results,
1.Query with item Hierarchy along the row
                                    GL Account   Balance
Total Product Revenu             1               X
                                            2               Y
Product Revenue                   1                X
Other Revenue                      2                Y
2. Query with Structure in the row
                                      GL Account   Balance
Total Product Revenu             1                 X
                                            2                 Y
Product Revenue                   1                  X
                                            2
Other Revenue                       1
                                            2                  Y
Item is a Navigational attribute of GL Account.
The relationship between item and GL account is maintained in the first output, whereas in the second output, all the GL accounts are obtained.
I need to maintain the relationship between item and GL account in the structure as well.
Ex: Product revenue has GL account 1 only, but in the structure for product revenue i get both GL account 1 and 2 also.
I need to get only GL account 1 for product revenue.
If i restrict product revenue for GL account 1 then later if there is achange in the master data, and a new GL account gets added to product revenue then that will not b displayed int he query, or i will have to manually chage my query also to reflect the change.
Kindly let me know if there is any way to maintain the relation between these 2 objects in the structure as well, like it is done in the hierarchy.
Should i be using a variable restriction of GL account, and create a exit variable refering to the GL account master data.Or is there any simple solution to it.
Regards,
Savitha

Answer 1

Can I use structure as this one?
Target->Statement->Attachments-
action=UPDATE_INSERT
table=Mytable
->access-
Field1
Field2
Field3
Field4 ->
<Statement>
<Mytable action=u201DDELETEu201D>
<key1>
<Field1>S</Field1>
</key1>
</Statement>
Here I am using both Update_insert and Delete operations on same table.
Thanks,
Srinivasa