Performing Setup Tasks

This chapter provides an overview of the setup task list and discusses how to:

Review the setup tasks.
Complete tasks in parallel.
Track setup tasks.
View setup task details.
Generate Excel to CI (Component interface) templates.
Generate Data Mover scripts.
Test the implementation.

Understanding the Setup Task List

The Setup Tasks List identifies the setup tasks that are required to complete your implementation based on the feature selections that you made in your implementation projects. Setup tasks appear in sequence in which they must be completed. The system indicates how each setup task relates to a specific PeopleSoft setup component.

Common Elements Used in This Section

Seq (sequence)	Displays the sequence number in which the setup tasks must be completed. Tasks that have the same sequence number can be performed in parallel.
	Click to access the PeopleBook help for the identified task. This icon appears only for component-based setup tasks.
Setup Task	Displays the name of the task that must be completed. This name is also a link to the first page of the component if the task is a component-based task.

Pages Used to Manage Setup Tasks

Page Name	Object Name	Navigation	Usage
Manage Setup Tasks	PTLT_TASK_LIST	PeopleTools, Setup Manager, Manage Implementation Projects, View	View individual setup tasks, navigate to any additional tasks that must be completed, track implementation progress, and view load methods.
Discussion	PTLT_DISCUSSION	Click the Discussion icon on the Manage Setup Tasks page.	Enter information and discussion about the progress of this setup task.
Generate Data Mover Scripts	PTLT_PROJ_RECS	Click the Generate Data Mover Scripts link on the Manage Setup Tasks page.	Create and save a Data Mover script to migrate data for selected setup tasks.
Generate Excel to CI Template	PTLT_PROJ_CI	Click the Generate Excel to CI Template link on the Manage Setup Tasks page.	Create and save an component interface template for selected setup tasks.

Reviewing the Setup Tasks

Access the Manage Setup Tasks page.

The summary shows the step-by-step sequenced list of setup tasks and reflects the order in which the setup components must be configured.

Status	Displays the status of the task. Move the cursor over the icon. Values are Not Started, In Progress, and Complete.
Setup Task and Description	Displays the task, in bold, that must be completed. The content of this field also contains the portal hover text, defined for the component associated with this setup task. This text provides you with information about the purpose of the task.
Navigation	Displays the portal navigation for the setup component-based tasks and navigation path to non-component-based setup tasks.
Features Affected	Displays the features that are associated with the task.
Products Affected	Displays the products that are associated with the task.

Completing Tasks in Parallel

The setup tasks are ordered and displayed in the sequence that they need to be performed. The setup tasks that share the same main sequence number can be performed in parallel. For example, setup tasks 1.001, 1.002, and 1.005 could be performed in parallel; however, they must all be performed before any setup tasks at level 2. Tasks that share the same main sequence number still appear in the order that they should be performed if they are not done in parallel.

Tracking Setup Tasks

Access the Manage Setup Tasks page; select Tracking tab.

Use the Tracking tab to manage the process and personnel associated with completing the setup tasks. The fields on this page are only informational and can be used by the project team and project manager to track the progress of the setup tasks.

Assigned To	Enter an owner for this setup task. This is a free-form edit box, so you can enter multiple names or the role of the individual who owns this task.
Start Date	Enter the start date for this setup task.
End Date	Enter an end date for this setup task.
Percent Complete	Enter the percentage of the task that has been completed. When you enter 100 percent, the Status field indicates Complete.

Viewing Setup Task Details

Access the Manage Setup Tasks page; select the Task Details tab.

The Task Details page displays the setup task, task code, whether a cross-database impact exists, and the load method that you can use to load the data for the component during the implementation.

Task Code	Displays the system-assigned code that identifies this task.
Cross Database	Identifies whether the setup task has a cross-database impact.
Load Method	Displays details about the load methods available for a given task. Values are: Component Interface, ETL, Other, and Online.
Method Name	Depending on the type of load method, displays the name of the component interface, ELT, or other load program.

Load Methods

For any component task, multiple methods exist by which to load the component with application data. Methods available for a given task display in the Load Method column. Examples of the methods are:

Online pages might be used to enter application data manually.
A component interface could be invoked using the Excel to Component Interface utility to load the component.
A custom load program could be used to load application data.

Viewing Associated Products

Select a product code or Associated Products in the Products Affected column to view associated products.

Generating Excel to CI Templates

Access the Generate Excel to CI Templates page.

The fields on this page are part of the component interface connection parameters. However, note the following two fields:

Language	Identifies the language used by the component interface (and thus from the database) and determines which Excel to CI base template is used. For example, if you select French from the dropdown list, the system uses the FRA subdirectory for the Excel to CI template.
File Directory	Identifies the location to which the template is generated. The system administrator should provide a path local to the Process Scheduler to which the user can map a drive.

Generating Data Mover Scripts

Access the Generate Data Mover Scripts page.

This page enables you to select the components for a specific task and generate Data Mover scripts that export and import your setup data to another database. This assists with the migration of application setup data from one environment to another. You can use the Data Mover scripts to populate other databases with setup data that you’ve entered in another environment.

Note. Some component-based tasks cannot be exported or imported by using Data Mover; these do not appear as selections.

After you select the component-based tasks and click the Generate Data Move Scripts button, an additional section of the page appears, showing the text of the Data Mover script and fields to enter a name for the scripts. The script includes a sequenced list of the tables that support the selected tasks. Where a table is identified within the script more than once, the duplicate references are commented out.

Note. Setup Manager identifies the primary tables that support the setup components that you select to migrate. Other tables, such as prompt edit tables that are defined on the component, are not identified by Setup Manager but might be necessary for the component to function in the new environment. You should identify these tables ahead of time when planning your implementation.

Generate Data Mover Script	Click to display an additional area of the page that displays the text of the Data Mover script as well as the directory where the script will be saved and filename of the script. Note. This button is not available for selection until you have selected the check box for at least one setup task.
Export	Select to view the Data Mover export script.
Import	Select to view the Data Mover import script.
File Name	Enter the file name for the Data Mover script. No directory separators are allowed in the filename edit.
Save Export File	Click to save the file to the default output directory. The PeopleSoft default directory is $PSHOME\appserv\files, where $PSHOME is the home PS directory. Your system administrator might have specified other locations for the output directory including: The directory for the environment variable $PS_FILEDIR that is defined during installation of the application server. The directory for the environment variable $PS_SERVDIR that is defined during installation of the application server.

Testing the Implementation

When the tasks in the Setup Task List have been completed, the implementation team should verify that the application functions as designed and supports the business scenarios that the implementation was based on. The approach to verifying that the setup is complete is based on the team's implementation methodology.

After you have finished testing the implementation and are using the software in a live environment, you can use Setup Manager when you implement new releases, products, features, or business processes.

Tasks associated with testing the implementation might include:

Testing individual online transactions and batch processes.
Verifying whether you can access any existing data and enter new data successfully.
Performing the steps of business processes end-to-end.