Modifying the P11D Data Extract Tool

The P11D Data Extract tool is designed to be adapted to different third-party P11D solutions, and to enable organizations to modify the data extracted.

Each third-party P11D solution is different and therefore the steps for adapting the P11D data extract tool vary for each solution. Here are some guidelines describing the key tasks:

  1. Review the documentation for your third-party P11D solution to determine data requirements and the file format required for importing data.

  2. Map your PeopleSoft data to the third-party data structure.

    Find out if the data items are in the same format in both systems or require manipulation. You need to determine which PeopleSoft tables store the data required by your third-party P11D solution.

  3. Determine if any of the delivered sections can be reused.

    For example the section P11D SE EE DETS may already select all the data elements you need relating to employee details.

  4. If an existing section is close to your requirements, copy the section and supporting elements then modify the new section, rather than modifying the delivered section.

  5. Create any new sections and supporting elements, if required.

    Review the design of the delivered sections and the supporting elements. Use these as a basis for creating new sections and supporting elements.

  6. Create a new process list and include the sections previously identified or created.

  7. Determine whether you can use one of the existing result tables.

    Review the definition of tables, GPGB_P11DRSLT_L, GPGB_P11DRSLT_M, and GPGB_P11DRSLT_S. Use the smallest table with enough fields to match your data requirements. For example, if the smallest table, GPGB_P11DRSLT_S, has enough fields then use that rather than GPGB_P11DRSLT_L or GPGB_P11DRSLT_M, which have more fields. If your data does not easily map to one of the existing result tables you may need to create a new table and a writable array to populate it.

  8. Decide if new views are required.

    For example, you need views if the data for an item in the third-party P11D solution exists across various tables in HR, or if only a subset of data is required based on some criteria.

  9. Use the Define P11D Solution page to specify the mappings.

  10. If complex data manipulation is required, then you may need to create some PeopleCode by adding methods to the Application Class GPGB_P11D:Extract.

During the development process, you can make use of a debug field. PeopleCode in the application engine sets the value of a debug field GPGB_P11D_AET.P11D_DEBUG. The field is set to "N" when delivered. If you modify the PeopleCode to set the debug field to "Y" then the log file generated by the Extract P11D Data process includes additional information which may help when developing modifications.

Typically the data required by your third-party P11D solution comes from a number of different sources. The data that resides in HR can be extracted using the P11D data extract tool. The data from other systems can be loaded into your third-party P11D solution directly. Alternatively you could make use of the various PeopleSoft integration tools to load the data into PeopleSoft HR first and then channel it through the P11D data extract tool.