Using the Data Migration Workbench for PeopleSoft Allocations
Allocations are widely used to apportion costs and revenues to lines of business, departments, and so on. There can be quite a bit of setup and testing involved in configuring Allocations. For this reason, it would be advantageous to create the Allocations setup in a development database and use Application Data Set (ADS) definitions to migrate Allocations configuration data between development environments, test environments, and ultimately to a production environment.
The following table lists the delivered ADS definitions (delivered in Data Set Designer) to support the migration of PeopleSoft Allocations configuration data:
|
Delivered ADS to Support PeopleSoft Allocations |
Application Data Set (ADS) Usage |
|---|---|
|
ALLOCATION_STEP |
This data set includes the records that store the allocation step definitions. Select this dataset on the Data Migration Workbench page to move allocation steps from one database to another. |
|
ALLOCATION_GROUP |
This data set includes the records that store the allocation group definitions. Select this data set on the Data Migration Workbench page to move allocation groups from one database to another. |
|
ALLOCATION_REQUEST |
This data set includes the records that store the allocation run control requests. Select this data set on the Data Migration Workbench page to move allocation requests from one database to another. |
When you copy the allocation dataset definitions, make sure that the data referenced within in the copied datasets actually exist within the database to which you are copying the Data Set definitions. For example, the tree definitions and ChartField values that are referenced within the Allocation Steps should be current in your source and target databases.
Note: The ADS migration validates record field values during the copy process; however, the validation is limited to report fields that use a prompt table or a translation value. The Allocation Step Definition tables use dynamic or derived prompt edit tables. In other words, the prompt tables are assigned at run-time and are not stored in the record field. As a result, the ADS copy process does not validate these field values.
PeopleSoft delivers an ADS Administrator permission list. For access, the ALLOCATIONS access group should be included on the Data Migration page within the Access Group Permissions and the proper access is granted on the Copy Compare Permissions.
See PeopleTools: Security Administration, Permission Lists.
All relevant records are included in the Query Access Tree, QUERY_TREE_GL within the ALLOCATIONS access group (PeopleTools, Security, Query Security, Query Access Manager).
See also the product documentation for PeopleTools: Lifecycle Management Guide