on ‎2013 Jan 15 2:09 PM
dear all,
I am extracting data to 0FIGL_C10.
we use standard info objects.
Everything looks fine.
But to use the balance structure (with accounts regarding their balance to see them on assets-side or on the liabilities-side) I am not sure what to do.
I am extracting 0GL_ACCOUNT form 0GL_ACCOUNT_ATTR.
for example account:
SOCA 3601000 DE X 03601000 Aktivierte Entwicklu Aktivierte Entwicklungskosten
So i would match field SAKAN from the data source to the attribute 0GLACCEXT on the info object 0GL_ACCOUNT:
Is that correct?
When I extract the hierarchy for 0GLACCEXT I get a lot of positions/accounts, which I don´t have/can create.
| InfoObject | Knotenname | Level | Link | Parent | Child | Next | Kennzeich | Vorzeichenumkehr | Saldenabhängigkeit eines Hierarchieknote |
| 0GLACCEXT | SOCA0000036010001A | 8 | 7 | 9 | 1 | ||||
| 0GLACCEXT | SOCA000013601000 A | 7 | 173 | 175 | |||||
| 0GLACCEXT | SOCA0000736010001A | 9 | 1072 | 1076 | 1 | ||||
| 0GLACCEXT | SOCA0000036010002A | 3 | 1432 | 1473 | 2 | ||||
| 0GLACCEXT | SOCA0000736010002A | 3 | 1432 | 1961 | 2 |
I searched to find a how to paper. But couldn´t find anything which would help me in this issue.
How is the correct procedure to use hierarchy with correct alignment of the accounts/positions?
I can not imagine that if i use totally standard objects I have to make any developments to get the accounts in the hierarchy.
many thanks in advance for your help
best regards
Roland
Request clarification before answering.
Hi Ronald,
asset side and balance side of a data is real time data as same account can go in asset side or in liable side.
I guess same should get applied to hierarchy. You can check hierarchy data once it gets loaded. You can read this hierarchy data too, but it is you need to keep drawing hierarchy based on level Parent and next level.
Regards,
Ganesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.