Does anyone knows how to find the relationship between a main session and ALL its related subsessions?

From the Form fields you can get the information of the zoomed sessions calles from here, but what about the ones called by the program? or Option Buttons?

Is there any way to get all this information from one place (report or table)?

Thanks for any help on the subject!!!!!!

The only place I know of to get this information is from the source code. You can check ttadv237(sessions by functions/programs), but I have never been positive of its accuracy.

The only place I know of to get this information is from the source code. You can check ttadv237(sessions by functions/programs), but I have never been positive of its accuracy.
Mark,

Refer to - Pragma codes (preprocessor) (http://www.baanboard.com/programmers_manual_baanerp_help_3gl_features_pragma_codes_preprocessor)

Where-used list

In some cases the where-used list is not updated automatically. For example, when a session code is entered but not expected:

message("ttadv2130m000")
or
bms.send("command", event, "ttaad3100m000", pr.id)

To put this session code into the where-used list, enter the following command line:

#pragma used session ttadv2130m000

The following example illustrates the pragma codes to update the where-used list:

#pragma used include <file>
#pragma used table <table code>
#pragma used field <field code>
#pragma used domain <domain code>
#pragma used message <message code>
#pragma used question <question code>
#pragma used session <session code>
#pragma used menu <menu code>
#pragma used dll <dll objectname>
#pragma used chart <chart code>

Usually the where-used list is updated. In the case of functions, the where-used list is updated if the function call contains the string value. For example:

mess("ttadvs0000", 1) | Where-used list will be updated

str = "ttadvs0000"
mess(str, 1) | Where-used list will not be updated

#pragma used message ttadvs0000

Hello NPR!

It seems to me that in somecases even Baan does not follow this structure. I know I only do it in my API sessions. I do it there so when the DEM flows are generated they get permissions to the session. There have been a couple of cases on my QKEY sessions where I have to go in and manually add a pragma used session. Again this is for the DEM flow generator. With Qkey it auto generates all of the pragma statements from ttadv237 - and some are missing for whatever reasons.

I have a similar requirement (for SOX audit). It is surprising that baan does not have a standard report listing subsessions for a main session.

I have logged a case with baan and no one in baan knows the answer to this basic requirement.

The baan support response was "You can use the so called where-used tables with are ttadv237, ttadv238, ttadv244, this tables are used for subsession authorization and from those you can generate the report."