Purpose of TreeMover

TreeMover enables you to move PeopleSoft trees between different PeopleSoft application databases. It enables you to export a tree to a flat file and to import a tree from a flat file. TreeMover moves all types of tree data, including the tree definition, tree structure, tree nodes, tree leaves, tree node data, and tree level data.

TreeMover does not support branched trees. If you import a branched tree, the branches become regular tree nodes.

Advantages of using TreeMover instead of other methods of moving trees, such as Data Mover or custom SQR, include:

• TreeMover can move trees between different versions of PeopleSoft databases, for example, from a PeopleSoft Financials 7.5 database to a PeopleSoft EPM 8 database.

• Tree Mover can move tree node data (description, setID, effective date, and effective status) for trees that have node data stored in the PS_TREE_NODE_TBL (the table that stores the tree node data is specified as part of the tree structure).

• Tree Mover can move tree level data (long description, short description, setID, effective date, and effective status) for trees that have level data stored in the PS_TREE_LEVEL_TBL—the table that stores the tree level data is specified as part of the tree structure.

• TreeMover uses the tree APIs, which means the same logic used for the PeopleSoft Tree Manager application is used to load and unload trees using TreeMover.

All the same edit checks are performed on a tree created with TreeMover as are performed on a tree created manually with PeopleSoft Tree Manager because both use the same functionality to create the tree. Because TreeMover processes are initiated from standard PeopleSoft pages, the ability to import and export tree data can be restricted by using PeopleSoft standard security mechanisms for limiting access to pages. If a source tree uses branches, you need to recreate them after TreeMover finishes its import operation.

Here are some example tasks that you can use with TreeMover:

• Load a winter tree with nodes from a legacy financial database quickly and easily into PeopleSoft 8 databases.

• Automatically replace an account tree every month with a new tree based on current information.

Note:

When the PS_TREEBASEDIR environment variable is set, the flat file for the import process is located in %PS_TREEBASEDIR%\<USER>\InputFilename and the flat file for the export process is located in %PS_TREEBASEDIR%\<USER>\OutputFilename. You can override this and create another location using the Process Definition Override page.

TreeMover currently supports fixed-format files only.

TreeMover does not support related language tables.

When you export a tree containing text data, the data is saved in the codepage of the server—for example, CP1252 Western European on English Windows, or CP932 Shift-JIS on Japanese Windows. Any characters which are not valid in the server's codepage are converted into question mark characters.

TreeMover consists of three parts: a utility to export a tree from a PeopleSoft 8 database, a utility to import a tree into a PeopleSoft 8 database, and a utility to export a tree from a PeopleSoft 7.x database. The import and export functionality for a PeopleSoft 8 database is implemented as a PeopleSoft Application Engine application process. As with other Application Engine processes, they can be scheduled to run automatically from the Process Scheduler. The Application Engine process uses PeopleCode Tree APIs, PeopleCode File APIs, and file layout definitions. The utility that enables you to export trees from a PeopleSoft 7.x database is implemented as an SQR program (TMDOWNLD.SQR).