SOLAR01, SOLAR02 trees: data model, anybody?

[Former Member]

Has anybody understood the data model behind these trees? How the tree itself is built, with the links between a node and its parent? How to follow a shortcut (node types e.g. 'SAS2', 'SAS3') to its original node? How to read the links from the additional info in the tabs to the node to which they belong?

I know that the links to transaction codes, for instance, are in table DFTNODE01R, with REF_TYPE = 'BMTA', and I know that the links to the HR objects (the end user roles, in my case) are in table BMTNODE01R, with REF_TYPE = 'HROB'. But how do these link back to the tree? To process steps (node type 'BMPC') and processes ('BMPG')?

All these tables are built and linked with GUIDs, no foreign key relationships to speak of... I'm lost.

And here's the background info about what we want to achieve...

In Solution Manager, we have broken down all our processes, and on process step level, we have stored the transaction codes required to carry out the activity, as well as the end user roles (HR objects of type "job") responsible for it. Besides the obvious documentary purposes, we use this data for testing, for training planning, and also as input for building authorizations.

The standard reports (filtering on the tree, and the cross-tab analysis reports in transaction SOLAR_EVAL) allow to display the mapping between transactions and roles, but we would like to extract the data with a custom program, in order to process it further. Hence my problem with the data model. I've tried to debug, to trace... There are so many SELECTs, some with JOINs, that I gave up.

Thanks for helping...

Kindest regards

Rainer

[Former Member · Accepted solution]

Hi,

you are not the only one lost with this and i fear there is no documentation available.

I figured out that the data storage is different for almost every tab.

But you could try the following tables, starting from the ones you mentioned:

DFTNODE01R:

1. dftnode01where node_id = dftnode01r-node_id

2. ttree where id = dftnode01-tree_id

3. tpr_index where refnode_id = ttree-node_id

tpr_index-node_id: GUID of the node

BMTNODE01R:

1. tpr_index where refnode_id = bmtnode01r-node_id

tpr_index-node_id: GUID of the node

or

1. bmtnode01where reftree_id = bmtnode01r-ref_object

bmtnode01-node_id: GUID of the node

If this does not work, you may experiment a bit with this tables, some other combination should do it.

Hope this helps,

Christoph

[Former Member · Accepted solution]

Christoph,

Thanks for your suggestions. From a known entry in DFTNODE01R I can navigate back to TTREE and TPR_INDEX, as follows:

1. dftnode01 WHERE node_id EQ dftnode01r-node_id

2. ttree WHERE id EQ dftnode01-tree_id

3. tpr_index WHERE node_id EQ ttree-node_id.

(The same method works for BMTNODE01R / BMTNODE01 as well.)

Alternatively, the following seems to work as well:

1. dftnode01 WHERE refnode_id EQ dftnode01r-node_id

2. ttree WHERE node_id EQ dftnode01r-node_id

3. tpr_index WHERE node_id EQ dftnode01r-node_id.

Trouble is that I still have no clue as to what I'm doing...

I'm pulling some strings, hoping I can find someone who knows the thing - if I'm not mistaken, the underlying tree concept has been used since the dawn of times, when SPRO and the IMG first came along with release 3.0 or so; there must be somebody who knows how it works.

Again, thanks for your suggestions - and for those of anyone else who may have more ideas or insight.

Regards

Rainer

[Former Member]

Dear Rainer and Christoph .......!!!!!!

I have done some work over these data of TXN - Solar01....!!!!!!!!!!!!

Infact I am a newbie in this area so I could not understand your need....!!!!!!!!!!!!!

could you please elaborate it a bit more...!!!!!!!

Thanking You.

[Former Member]

Hi,

I'm not exactly sure about what's clear and what isn't, so I'll start slow.

In SolMan, you define the business processes of your company, breaking them down into their individual steps (like: post goods movement, post incoming invoice, confirm production order, and what have you). To each step you can assign the corresponding transaction codes (on the detail tab "Transactions"), and also the user or user group responsible for carrying out the step (on the detail tab "End User Roles", as user IDs, HR organizational units, or HR jobs).

The combination of this information is useful for many purposes: documentary, testing, training - and we're using it as basis for authorization definition.

The DB structure is somewhat complicated by the use of shortcuts. If you have the same step in several processes (as you're bound to have; posting vendor invoices for instance happens time and again across many business processes), you can define it once, and then link it to all processes where it occurs as a shortcut (appears in the SOLAR... tree with a little chain symbol).

So I'm looking for a way to extract the assignment of transaction codes to process steps, of HR objects to process steps, and of shortcuts, and for that I need to understand how these things are stored and linked on the database.

Does this explain my problem sufficiently?

Thanks & regards

Rainer

[krzysztof_murkowski2]

Hi Rainer,

I've asked the same questions about data model of solution manager hierarchies. Finally I've developed a small program to show it as tree. This kind of graphic presentation and above all the program developing helped me a lot.

Perhaps it can also be interesting for you:

[http://www.kerum.pl/infodepot/00022|http://www.kerum.pl/infodepot/00022]

regards,

Kris