Understanding the PTIA Data Conversion Process

The PeopleTools Impact Analysis (PTIA) process uses many pieces of the previous style data conversion delivered in PeopleSoft 9.1 applications and lower. For example, PTIA uses the Application Engine section grouping and sequencing in the PS_PTIA_DCAEPGMS table for its dependency modeling. The PTIA process also uses the terminology – root or top section. A root or top section is an Application Engine section defined in PS_PTIA_DCAEPGMS. We use root or top section to distinguish between sections being called from the data conversion program as opposed to sections being called from an Application Engine call section step.

The PTIA process includes analyzing the insert, update, and delete SQL steps in your data conversion to determine the Source and Target tables and state records that are used. This includes analyzing dynamic SQL, App Classes, SQLExec’s, and platform-specific code.

The Application Engine program gathers a list of Application Engine sections required for data conversion from a given upgrade path. These sections are analyzed and SQL statements are extracted and stored in the Application Engine Analyzer repository. Each SQL statement is analyzed to derive a list of tables that are manipulated or queried during the execution of that SQL. Once all the SQL is analyzed, the information is used to derive section dependency information, which is then saved in the Application Engine Analyzer repository. PTIA allows the Application Engine data conversion to run out of the box on a number of threads.

There are two types of analysis for PTIA: initial and dependency. This section will describe both analysis types in detail.