Setting Up FACTS I Trees

Use the Tree Definition and Properties page (PSTREEDEFN) to create a new tree, beginning with the tree definition to identify the tree name, related structure ID, SetID, and any other rules or characteristics of the tree.

Upon clicking OK, you are directed to the Enter Root Node for Tree page where you define levels and root node. Once done, the OK button directs you to the Tree Manager page to build your tree.

Navigation:

Tree Manager > Tree Manager > Create New Tree > Tree Definition and Properties

Enter a tree name and click the Add button.

Use the Tree Manager page (PSTREEMGR) to access an existing tree with options that enable you to access and modify the tree definition and properties, print, and configure tree display options.

Navigation:

Tree Manager > Tree Manager > Find an Existing Tree

Create the Transfer Agency tree using PeopleSoft Tree Manager based on the following example.

This tree contains nodes for each of the transfer agencies and is used by both FACTS I and FACTS II. If you have decided to use the same ChartField for both Transfer Agency and Transfer Account, then the values in your ledger for that ChartField will represent both Transfer Agency and Transfer Account at the same time. The tree will allow the program to translate the combination Transfer Agency/Account value of the ledger to the Transfer Agency value that is required by U.S. Treasury.

This example illustrates the fields and controls on the FACTS Transfer Agency tree - Tree Manager page. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a FACTS I Bureau tree similar to this example for your organization.

This example illustrates the fields and controls on the FACTS I Bureau Tree Manager page. You can find definitions for the fields and controls later on this page.

The node values at one level of the tree represent the values that the U.S. Treasury is expecting in the FACTS I flat file. You select this level on the FACTS Tree Group page.

See also PeopleTools documentation: PeopleSoft Tree Manager, "Introduction to PeopleSoft Tree Manager"

Using PeopleSoft Tree Manager, set up a Fund Group tree similar to this example for your organization.

This example illustrates the fields and controls on the Tree Manager page - FACTS I Fund Group tree. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a Department tree similar to this example for your organization.

This example illustrates the fields and controls on the FACTS I Department Tree page. You can find definitions for the fields and controls later on this page.

This tree consists of a hierarchy of department levels with the ledger values that roll up into them. The level that appears for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

Using PeopleSoft Tree Manager, set up an Account tree similar to this example for your organization.

This example illustrates the fields and controls on the Tree Manager page - FACTS I Account tree. You can find definitions for the fields and controls later on this page.

For FACTS I reporting, the Account value is four characters; the node value is 1000 at the ACCDT_TYPE level in the FACTS_ACCOUNT tree.

Using PeopleSoft Tree Manager, set up an Exchange/Account tree similar to this example.

This example illustrates the fields and controls on the Tree Manager page - FACTS I Exchange Account tree. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a Custodial/Acct tree similar to this example.

This example illustrates the fields and controls on the Tree Manager page - FACTS I Custodial/Acct tree. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a Budget Subfunction tree similar to this example.

This example illustrates the fields and controls on the Tree Manager page - FACTS I Budget Subfunction / Account tree. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a FACTS I Tran Partner tree similar to this example.

This example illustrates the fields and controls on the FACTS I/II Transaction Partner Tree Manager page. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a Transaction Partner / Acct. tree similar to this example.

This example illustrates the fields and controls on the FACTS I Transaction Partner/Acct Tree Manager page. You can find definitions for the fields and controls later on this page.

Using PeopleSoft Tree Manager, set up a FACTS I Accounts Req Attributes tree similar to this example.

This example illustrates the fields and controls on the Tree Manager page - FACTS I Accounts Req Attributes (accounts requiring attributes) . You can find definitions for the fields and controls later on this page.

Use the FACTS Tree Group page (FACTS_TREE_GRP) to associate all of the FACTS I trees and the rollup levels for processing.

This page is identified on the run control page for FACTS I reporting and processing.

Navigation:

General Ledger > Federal Reports > Define FACTS Tree Group > FACTS Tree Group

This example illustrates the fields and controls on the FACTS Tree Group page (1 of 2). You can find definitions for the fields and controls later on this page.

This example illustrates the fields and controls on the FACTS Tree Group page (2 of 2). You can find definitions for the fields and controls later on this page.

Carefully choose the SetIDs to be used for the FACTS Tree Group and the FACTS I Trees and configure the TableSet Control SetIDs accordingly. Incorrect configuration could result in the unavailability of tree group names or tree names in prompt lists on pages, or in the inability of the FACTS I process to retrieve data.

If your organization has only one business unit and you use only one SetID to set up your ChartFields, trees, and tree groups, then your TablesSet Control SetIDs should all be the same and do not need changing. Also, if you use more than one business unit that uses the same default SetID, then the Control Tables should not need to be modified. However, check the TableSet Control pages for each business unit and SetID, using their values as the Set Control Values, to ensure that all tables and trees are using the same SetID. Note that the Tree Group table is in the GL_15 Federal Reports Record Group in the TableSet Control Record Group page.

If you use more than one SetID in your organization for setting up your ChartFields, trees, and tree groups, then you must make sure that each SetID that you use is set up correctly in TableSet Controls. The SetIDs used in the following steps are only examples:

1. Set up your FACTS I ChartFields, trees, and tree group using the FEDRL SetID.

2. Identify the general ledger business unit (for example, FED01) that you want to use for FACTS I processing.

   Access the SetControl Value (FED01) in TableSet Control - Record Group page. The Default SetID designated at the top of this page is the default SetID that you set up for the general ledger business unit.

3. Find the GL_15 Federal Reports Record Group and select the SetID (FEDRL) for GL_15 to match the SetID (FEDRL) that you used to create your tree group.

   The FACTS Tree Group table is a part of the GL_15 Record Group and must have the same SetID. This selection enables the Tree Group list box to appear on the Accumulate FACTS I Data page so that you can select a FACTS Tree Group to process.

4. Verify whether the Default SetID (SHARE) on the TableSet Control Record Group page is the same (YES) or not the same (NO) as the SetID that you used to set up your trees.

   The FACTS I processes normally refer to the Default SetID in the TableSet Control Record Group page and uses the default SetIDs to retrieve the FACTS I tree.

5. If YES, save and exit TableSet Control.

6. If NO, you must enter each tree on the TableSet Control - Tree page that has a SetID that is different from the Default SetID on the TableSet Control - Record Group page.

7. If you run FACTS I processing on multiple business units, repeat these steps.

Use the TableSet Control - Record Group page (SET_CNTRL_TABLE1) to defines all the record groups based on a specific Set Control Value and their associated SetIDs.

Also identifies the default SetID of the PeopleSoft General Ledger business unit.

Navigation:

PeopleTools > Utilities > Administration > TableSet Control > Record Group

This example illustrates the fields and controls on the TableSet Control - Record Group page. You can find definitions for the fields and controls later on this page.

Use the TableSet Control - Tree page (SET_CNTRL_TABLE2) to set up tree values on this table if your SetID for your business units do not match your default SetID.

Navigation:

PeopleTools > Utilities > Administration > TableSet Control > Tree

This example illustrates the fields and controls on the TableSet Control - Tree page. You can find definitions for the fields and controls later on this page.