Illustrates how to make use of Value Lists to design reports that require grouping of Time Reporting Codes.

1. PeopleSoft Time and LaborBest Practice Series Value Lists and Reporting www.peoplesofthrms.blogspot.com

2. The Requirement Design a report showing the summary of payable time for a week. A sample format is given below:

3. The challenge There are multiple Time Reporting Codes (TRC) to be considered under each column. A sample of TRCs under each category are given below: What is the best way to group the TRCs together so that the hours under each category can be estimated correctly?

4. The Sub-Optimal Options Sub-Optimal Option 1: Hard coding the TRC names and using a SQL ‘IN’ condition to evaluate the TRC grouping. Sub-Optimal option 2: Creating separate views for each category and using a SQL ‘IN’ condition to evaluate the TRC grouping. Sub-Optimal option 3: Evaluating the TRC in the XML Publisher template XSL formula before printing the hours under each category.

5. Best Practice Use ‘Value Lists’ in Time and Labor to group the Time Reporting Codes under each category together. Further, use the Value List in the report logic to get the total number of hours under each category. Value Lists are a way of grouping data elements together in Time and Labor. Value Lists are commonly used in the setup of Time and Labor rules. Value Lists can be utilized to eliminate the need to hard-code values in Time and Labor.

6. Setting Up Value Lists Value List can be setup under the following navigation: The TRCs that are part of a value list can be added to the Value List definition.

7. Using Value Lists in Reports Setup one value list corresponding to each relevant column in the report. Details of the members of a value list is stored in the table – TL_VAL_LIST_DTL. For printing the hours for a certain column in the report, obtain the total hours corresponding to each TRC of in the relevant value list. This can be easily achieved by the below SQL:

8. Advantages of the method Relevant TRCs under a column can be easily maintained directly from PIA. No code change required to the report when a new TRC is created. Faster performance of the report as minimal number of views will be required with this approach. Online validation of TRC names when configuring through a value list. Elimination of the need for Change Requests for modifying the list of TRCs as no code change will be required to change the list of TRCs.

9. Questions or suggestions?? www.peoplesofthrms.blogspot.com jijucvengal@gmail.com