Creating Query Trees
Use the Query Access Manager page (PSTREEMGRACC) to create query trees or search for existing query trees.
Navigation:
This example illustrates the fields and controls on the Query Access Manager page.
PeopleSoft provides sample trees with all of its applications. You can configure these trees; however, because these trees may get replaced when you upgrade to subsequent application releases, you should create your own query trees based on your organization’s needs.
In your query trees, include all record components that you want users to be able to query. Note that you do not have to put all record components in the same query tree. Instead, you can use the sample query trees to provide access to the standard PeopleSoft record definitions, but create additional query trees for record definitions that you want to add while adapting your system. This strategy enables you to take advantage of the sample trees but avoid overwriting your changes during future application upgrades.
How you organize the contents of your query trees depends on the needs of your organization and users. For example, for nontechnical or casual users, you might want to create small trees that are not intimidating.
To simplify the trees, you can create separate trees that contain subcategories of each function. For example, you could create separate trees for human resources, general ledger, and projects record components so that users in each region can access only those record components that they use.
When creating your tree, you should also have an access group that includes all components of the tree. This enables you to give users access to all tables more easily—you need only to add one row on the Access Groups tab in Query Security.
Note:
Consider adding record components to your query trees in a hierarchy that matches the parent/child relationship of records in your database. Although you do not have to organize records in this way—PeopleSoft Application Designer actually controls the parent/child hierarchy in your database—you will probably find it helpful to keep your query trees consistent with your database structure.