ABT Program Modifications Strategy Plan

June, 2008

May 2008

Better Information for Better Government

Page 1 of 19

Revision History
Version Original v.1 Prepared by Bill NeuhardtCIBER and Sujender ProduturiCIBER Date May 27, 2008 Reviewed by Lisa Gauthier Approved by Marjorie Mills Note

May 2008

Better Information for Better Government

Page 2 of 19

Table of Contents
1.0 INTRODUCTION ..................................................................................................................................................................... 4 1.1 EXECUTIVE SUMMARY...................................................................................................................................................... 4 1.2 OBJECTIVES ...................................................................................................................................................................... 4 1.3 MODIFICATION STRATEGY:............................................................................................................................................... 4 1.4 SUMMARY OF RECOMMENDATIONS: ................................................................................................................................. 5 1.5 ASSUMPTIONS ................................................................................................................................................................... 5 2.0 CHANGE CONTROL....................................................................................................................................................... 6 2.1 ABT FIT/GAP DEVELOPMENT CHANGE CONTROL RECOMMENDED ............................................................................... 6 2.1.1 Key Elements: ........................................................................................................................................................... 6 2.1.2 Procedure: ................................................................................................................................................................ 7 2.2 INITIATION OF A DEVELOPMENT CHANGE FOR ABT MODIFICATIONS, INTERFACES AND CUSTOM REPORTS ................... 7 3.0 MODIFICATION MATRIX............................................................................................................................................. 8 3.1 ORACLE FINANCIALS EBS NEW MODIFICATIONS .......................................................................................................... 8 3.2 ORACLE FINANCIALS IBIS EXISTING MODIFICATIONS ................................................................................................. 10 3.3 ORACLE FINANCIALS EBS CANDIDATES FOR POSSIBLE REMOVAL .............................................................................. 11 3.4 PEOPLESOFT HCM NEW MODIFICATIONS.................................................................................................................... 11 3.5 PEOPLESOFT HCM EXISTING MODIFICATIONS ............................................................................................................ 12 3.6 PEOPLESOFT HCM CANDIDATES FOR POSSIBLE REMOVAL ......................................................................................... 13 3.7 OTHER SYSTEMS NEW MODIFICATIONS ....................................................................................................................... 14 4.0 MODIFICATION APPROACH..................................................................................................................................... 15 4.1 MODIFICATION STANDARDS: .......................................................................................................................................... 15 4.2 CUSTOM SCHEMA ........................................................................................................................................................... 16 4.3 CUSTOM APPLICATIONS AND CUSTOM FOLDERS (CUSTOM TOP)................................................................................... 16 4.4 PRESERVING THE INTEGRITY OF THE ORIGINAL OBJECT .................................................................................................. 16 4.5 NAMING STANDARDS ...................................................................................................................................................... 17 4.6 MODIFICATION TOOLS .................................................................................................................................................... 17 5.0 ABOUT MODIFICATION TOOLS .............................................................................................................................. 18 APPENDIX A: APPENDIX B: SUMMARY OF PEOPLESOFT 8.9 CUSTOMIZATIONS............................................................... 19 PSSD DEVELOPMENT STANDARDS............................................................................................... 19

May 2008

Better Information for Better Government

Page 3 of 19

1.0 Introduction
1.1 Executive Summary
An important goal of ABT Program is to consolidate the functions of Human Capital Management (HCM) and Financials into a common platform by implementing PeopleSoft 9 and Oracle eBusiness Suite Release 12 for the entire county. Modifications are changes that extend the functionality of a software system in the context of this document Oracle EBS and PeopleSoft 9. The modification strategy recognizes the need to change some of the delivered functionality to support specific business needs of King County that cannot be efficiently met by modifying business processes. This plan recommends a change control structure for handling modifications and recommends a process for tracking modifications. The plan also proposes an approach to modifications that includes how, when and why modifications should be done.

1.2 Objectives
The objectives of this document are three fold. This first is to provide a structure for Change Control as modifications are made to the PeopleSoft HCM and Oracle EBS systems. The process also includes an approval process for interfaces, and custom reports. The second is to provide a high level overview of the currently identified modifications that the ABT reimplementations will need to be aware of and handle while moving the County to PeopleSoft HCM 9 and Oracle EBS 12. The last is to list new modifications and modifications to be removed from existing baseline, identified by the ABT DIP analysis effort.

1.3 Modification Strategy:

In general, the strategy will serve as an initial guide on the following areas and it will evolve over time during the ABT implementation: Recommend processes and methodology to track Configurations, Modifications, User Defined Fields, and Interfaces Create a Modification Matrix of current and possible future modifications.

May 2008

Better Information for Better Government

Page 4 of 19

1.4 Summary of Recommendations:

Oracle EBS, PeopleSoft 9 and the new Budget System and are general purpose software systems, as such some of the delivered functionality may need to be modified or extended to fit the needs of the County or specific departments. Modification can be defined as changing or adding logic to the delivered functionality or by extending the functionality by providing a bolt-on application or sub module. It is highly recommended to avoid modifying the delivered functionality, but rather adjust the business process. Business process change should be considered where it can substitute for system modification and is adequately efficient and effective. A naming standard is recommended and will be designed so that all modified objects can be identified. It is recommended that the same naming standards be followed that are currently used for custom objects within Oracle IBIS and PeopleSoft 8.9. Modification of delivered objects, if needed, should be done only to a copy of the original object that is intended to be modified, renamed according to standard and saved in a separate location. This practice preserves the original version of the object and also prevents overwriting during upgrades to Oracle EBS or PeopleSoft 9. Modifications are done using the same tools and technologies that are used to develop the original objects. As such, when modifying the object, the same version of the tools and technologies need to be used.

1.5 Assumptions
This assessment was based on the following assumptions. The ABT Program will be re-implementing Oracle EBS 12 and PeopleSoft HCM 9. Fit/Gap sessions will be held on each module to be implemented or re-implemented, which may result in further modification requests. Information gathered from the County on current Modifications made to PeopleSoft 8.9 and IBIS are representative of the state of the two systems when the ABT Program starts the re-implementation activities. Knowledgeable King County representatives will be available for guidance on the modifications that are currently used in IBIS and PeopleSoft 8.9. Interfaces and Custom Reports will follow the modifications change control processes, as well as the development and testing schedule.

May 2008

Better Information for Better Government

Page 5 of 19

2.0 Change Control

CIBER has performed research on the Modification Change Control practices and documentation that is currently in place around the Countys core HR/Payroll and Financial systems, and recommends using a targeted process for Development Change Control which will provide an appropriate level of project development tracking and approval visibility.

2.1 ABT Fit/Gap Development Change Control Recommended

The ABT Fit/Gap Development Change Control process encompasses approval to fund all design and configuration work coming out of Fit/Gap and BPR, including modifications, interfaces, temporary interfaces, and custom reports. The process includes notifying ABT Program Management of elements going into design and configuration and noting whether they deviate from the DIP. Variances to the planned design and configuration work tasks, resources, or schedule will require notification of intended changes, and include justification and analysis of the impact on the project. Development Change Control will include effective tracking, monitoring and control over changes by: Establishing a central point of control and decision making. Minimizing changes, even those that are easy to make. This step includes identification and analysis of alternatives. Establishing quantification for each proposed change and requiring business justification to be documented and approved by the Program Manager or delegate, prior to design. Any proposed modifications, interfaces, or custom reports are subject to the Development Change Control process. This Development Change Control process does not include changes to the scope of the ABT Program or fundamental universe of tasks agreed to in the Project Charter. Included at the discretion of the Program Manager are any modifications, interfaces or custom reports, not included in the project plan at the conclusion of the Fit/Gap process, or tasks identified in the plan for which new requirements surface which align with project scope.

2.1.1 Key Elements: Establishment of project baseline, variation from which triggers the Development Change Control process Documentation and analysis of proposed changes, including alternatives Approval process Structured tracking

May 2008

Better Information for Better Government

Page 6 of 19

2.1.2 Procedure: Process flow diagram for Development Change Control process Detailed instructions on the Change Control process steps

2.2 Initiation of a Development Change for ABT Modifications, Interfaces and Custom Reports
The ABT Implementation team will initiate development change process and work with the affected department on justification for development requests. After estimates have been provided and reviewed, ABT Program Manager will make an approval decision. Based on Decision by the ABT Program Manager or delegate, the ABT Implementation Team will initiate design.

May 2008

Better Information for Better Government

Page 7 of 19

3.0 Modification Matrix

For the estimation part of the DIP, the assumption has been made that the modifications listed below will be included in the re-implementation of Oracle Financials and PeopleSoft EBS. These potential modifications have been identified during the DIP Fit/Gap Analysis. These lists of modifications will be analyzed during the Fit/Gap sessions for each module. At that time, these modifications will be included in the system rollout or Business Processes will be implemented to satisfy the Business Requirements identified:

3.1 Oracle Financials EBS New Modifications

Module
Oracle Payables Oracle Inventory Oracle Fixed Assets Oracle Purchasing Oracle Purchasing Oracle GL Oracle Payables Oracle Purchasing Oracle Accounts Receivable

Functional Area

Justification

Complexity
Low Low Low Low Low Low Med Low Med

Crosswalk

Oracle Projects

Project Supplier Invoice Template to be modified for generating Account Generator - Workflow accounting codes Template to be modified for generating Inventory Account Generator accounting codes FA Account Generator Template to be modified for generating Workflow accounting codes PO Requisition Account Template to be modified for generating Generator - Workflow accounting codes PO Account Generator Template to be modified for generating Workflow accounting codes Journal approval rules for Template to be modified for generating Workflow accounting codes AP Invoice Approvals Rule Customize the AP invoice approvals Workflow and Credit Memo - using AME based on department rules configuration Requisition approval rules for Template to be modified for generating Requisitions - Workflow accounting codes AR Credit memo approval Customize the AP Credit Memo approvals rules Workflow based on department rules Need to build a set of tables and user entry Cross Walk screen to manage the crosswalk on a daily 1. ARMS - GL basis. GL Crosswalk maintenance screens 2. ARMS - Projects may already exist in IBIS. The same can be 3. ARMS - Projects for Labor leveraged. Trigger to change the Expenditure Item Date in Accounts Payable to be the system date. This should occur when the AP invoice is interfaced to GL or approved or some other current action. The Expenditure Item Date needs to be changed because it is populated Change to Invoice Workbench with a date corresponding to when the original user entry screen blanket PO is created, or when the inventory is initially purchased which could be in the past. The revised Expenditure Item Date will slot the expenditure into the proper period within Grants-Projects and will also send the transaction to the corresponding GL Period.

High

Low

May 2008

Better Information for Better Government

Page 8 of 19

Module
Oracle Projects

Functional Area
Populate GL Value set for Project Segment

Justification
Trigger to populate the GL Project segment value set with a newly entered Project Number created in Grants Accounting. This eliminates the need to manually populate every new Project Number in General Ledger. May be needed in PeopleSoft Time and Labor & iProcurement

Complexity
Low

Oracle Projects

Oracle Projects

Oracle Projects

Oracle Payables Oracle Inventory Oracle Purchasing iProcurement Oracle Accounts Receivable Oracle Accounts Receivable Oracle Accounts Receivable Oracle Payables Oracle Purchasing Oracle Purchasing

Limit some Project Number List of Values to List of Values for Time Entry show only those Projects where the logon limit based on certain criteria user is a Key Member. This prevents users from charging Projects out of their domain. the area where This will probably be necessary is Time Entry Modify the template to build Project creation Projects Approval Workflow approvals Workflow based on department Changes rules Modify the template to build Project budget Project Budget Approval creation approvals Workflow based on Workflow Changes department rules AP Invoice Approvals Changes to notifications and message body Changes to Workflow etc. for AP invoice approval workflow notifications as necessary Inventory Alerts/Notifications - Changes to notifications and message body Workflow etc. for approval workflow PO Approvals - Workflow Changes to notifications and message body changes for Notifications etc etc. for PO Approval workflow Workflow Changes for Changes to notifications and message body electronic output of system etc. for approval workflow generated approved releases XML/BPA invoice billing Assumption - 2 templates - potentially change templates the data presented in the body of the form XML dunning letter templates Assumption 3 templates Statement XML template Assumption 3 templates

Low

High

High

Low Low Low Low Low Low Low Low Low Low

XML Warrant (check Printing ) Check printing changes form with electronic signatures XML PO Templates XML Requisition template Assumption - 2 Templates Assumption - 1 Template

May 2008

Better Information for Better Government

Page 9 of 19

3.2 Oracle Financials IBIS Existing Modifications

This modifications listed below are currently in use within IBIS and will be migrated during the Oracle EBS implementation.

Module
Oracle Payables

Functional Area
Purchasing Card Data AP Supplier Query: Custom PLL form revision for 50-80 forms to block view to Supplier Tax ID when employee ID; ( HR API Payroll Interface revision/conversion addressed this in 11i10 Upgrade)

Comments

Complexity
Low Effort to Migrate and test

Oracle Payables

Oracle Accounts Receivable Oracle Accounts Receivable Oracle Accounts Receivable Oracle Accounts Receivable Oracle Accounts Receivable Oracle GL

Oracle GL

Oracle GL iProcurement

iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement

Oracle Release 12 offers this functionality on some of the screens. For Med Effort to the rest, the preferred Migrate and test if needed at all way would be to Personalize the form rather that Customize. Low Effort to Lockbox Submission Migrate and test Low Effort to Customer Query Migrate and test Modify Customer Query to include full history Low Effort to of Customer Primary Bill-to information Migrate and test Custom Cap Charge Invoice: add the Low Effort to Customer number and Profile Class in the Migrate and test first line of the Bill To address that prints on the invoice AR Custom Invoices revised to place past Low Effort to due amounts on the invoice Migrate and test Low Effort to HR Payroll Scrubber Form Migrate and test HR Payroll Scrubber program changes: Update the scrubber program to write out the records that cause program errors Low Effort to Migrate and test Provide feedback at key points in the process to determine status and confirm program proceeding Low Effort to Project-Subproject Description form Migrate and test Accounting Regions Low Effort to (King County specific GL Accounting Migrate and test Distribution Segments) Profile for Accounting Regions Low Effort to POR: Edit Accounts Region Migrate and test POR:Multiple Accounts Region Low Effort to Preferences/My Profiles Accounting Regions Migrate and test Low Effort to Requisition DFF - Accounting Regions Migrate and test Default Taxable Status : Default value "Don't Low Effort to Know" Migrate and test Low Effort to Suggested Buyer displayed in Delivery Page Migrate and test Low Effort to Single Row/Multiple Row Migrate and test Better Information for Better Government

May 2008

Page 10 of 19

Module
iProcurement iProcurement Oracle GL Oracle GL Oracle GL Oracle Inventory Oracle Inventory Order Management Order Management Oracle Purchasing Oracle Purchasing Oracle Purchasing

Functional Area
Urgent Requisition Check Box Customized removal of field Requestor ID in iProcurement forms (included SSN # for user) The unit price field on the order transmittal form does not allow enough digits Receipt Form: Customize to alert user when Receipt Flag not checked in form Budget Upload:To be replaced with ADI Use Tax Interface: CSV To be replaced by ADI Calculate lead times for inventory items Pass Sales Inventory Sales Account Update Pass Sales Generate Standing Orders OM: No Pick, No Ship Validate Employee Trigger SSN custom library

Comments

Complexity
Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test Low Effort to Migrate and test

3.3 Oracle Financials EBS Candidates for Possible Removal

Module
Oracle Payables

Functional Area
AP Supplier Query: Custom PLL form revision for 50-80 forms to block view to Supplier Tax ID when employee ID; ( HR API Payroll Interface revision/conversion addressed this in 11i10 Upgrade)

Comments
Oracle Release 12 offers this functionality on some of the screens. For the rest, the preferred way would be to Personalize the form rather that Customize.

3.4 PeopleSoft HCM New Modifications

Module
Time & Labor

Functional Area
Time Admin Process must enforce Project/Grant Entry Rules

Justification
This is a business requirement agreed to by the SMEs and approved by the ABT Governance Structure during HLBP and HLBD This is a business requirement agreed to by the SMEs and approved by the ABT Governance Structure during HLBP and HLBD

Complexity
High

Time & Labor

Administrative Time and Labor Entry must follow Project/Grant Entry Rules

Med

May 2008

Better Information for Better Government

Page 11 of 19

Module
Time & Labor

Functional Area
Self Service Time and Labor Entry must follow Project/Grant Entry Rules Time Capture needs to allow for a Work Order to be entered for DES employees using Maximo for Work Order Management Position Management must carry an MSA Position Mgt value to cross walk back to MSA. Also, assign the sequence number for new positions created in PeopleSoft. Organization / DeptID cross walk back to MSA

Justification
This is a business requirement agreed to by the SMEs and approved by the ABT Governance Structure during HLBP and HLBD This mod replaces current functionality in POL This is required in order to maintain the existing functionality between MSA and ARMS This is required in order to maintain the existing functionality between MSA and ARMS

Complexity
Low

Time & Labor

Med

Human Resources

Med

Human Resources

Low

3.5 PeopleSoft HCM Existing Modifications

The summary results of the DIP analysis on existing modifications are included here, and the details are included in the Appendix C. Identified menu items listed on the King County custom menus. This method identified only King County Bolt-On modification not changes to PeopleSoft delivered objects. There are 248, menu items lists in this category that were identified by complexity from a Functional testing perspective of: High = 111, Medium = 94, Low = 37, Not Needed = 5 and Dont Know = 1. These menu items made up of the following functionality areas: 1. 2. 3. 4. Report Run Controls Setup and Configurations Update Process Run Controls Page Groups called Components that capture data to support custom Functionality.

Counts of current pages and records that have been modified by someone other than PeopleSoft denotes another set of customizations. Pages and records represent the major objects that other modifications are attached or are built to support. Both contain a multitude of triggers that can contain PeopleCode that may have been changed or create by King County. The counts are shown here:

Customized Pages
Delivered from PeopleSoft and changed by King County Created by King County Total: 63 438 501

Customized Records
Delivered from PeopleSoft and changed by King County Created by King County Total: 138 768 906

May 2008

Better Information for Better Government

Page 12 of 19

Reviewing the migration logs from the 8 to 8.9 Upgrade Project identified the customizations that were moved into production 8.9. The summary results are shown here:

KC RFW Upgrade Migrations

Reports Interfaces Processes Online Pages Other Total: 66 17 41 133 4 261

Each migration can represent many custom objects in the database and the majority has a Functional and Technical Specification that details the modification. Reviewing the list of custom SQR programs that are executable within PeopleSoft production system provided more customization efforts. The summary results are shown here:

Custom SQRs by Function

Interface Report Process Other Total: 58 93 64 53 268

Additional modifications were found by counting the number of objects by type by Project or migration folder. The summary results of Project, Object Type and Count filled close to 3000 lines in a spreadsheet with a total count of 25,133 objects changed. This proved too large to be analyzed and placed in this document. In conclusion, it can be assumed that PeopleSoft is heavily modified by King County and will take significant resources to ensure that the functionality is not lost during the re-implementation of PeopleSoft 9 by the ABT Program. Estimates have been entered into the Detailed Project Schedule based on CIBER knowledge base and a review of the PeopleSoft 8 to 8.9 Upgrade recently completed by the County.

3.6 PeopleSoft HCM Candidates for Possible Removal

Initial analysis has determined that some current modifications maybe able to be removed. The last PeopleSoft Upgrade from 8 to 8.9 performed extensive analysis attempting to remove unneeded modifications. That project was successful in that effort which completed in the third quarter of 2007. This list contains a few more possible candidates:

Module
Time & Labor Time & Labor Time & Labor Time & Labor Time & Labor

Functional Area
KC Feeder Batch Status KC Feeder Error Display KC Feeder Error Report KC Feeder File Available Report Not Needed Not Needed Not Needed Not Needed

Comments

KC Feeder Files Avail Display Not Needed Better Information for Better Government

May 2008

Page 13 of 19

Module

Functional Area

Comments
KC_JOB_CLASS_TB, lookup table for kc_msa_class (fields ** KC_JOB_CLASS, ** EFFDT, DESCR, KC_MSA_CLASS) stores the all the King County Class Specification codes and serves as a cross walk to the MSA class code. KC_JOBCODE_TBL contains a foreign key relationship to KC_JOB_CLASS_TB to group job codes to a class specification. KC_JOB_CLASS_TB could possibly be replaced by PS_JOB_PROFILE_TBL and the parent-child relationship recreated using the JOB_PROFILE_ID field on PS_JOBCODE_TBL. Cindy Baumeyer of CIBER, recommendation to use delivered Life Events in Self Service.

Human Resources

Job Class Lookup Table

Benefits

Qualifying Life Events

3.7 Other Systems New Modifications

Enforcement of Project/Grant Entry Rules at the source system, as well as corrections for prior period adjustments will create a condition for modifications, as will a restructuring of the accounting coding structure elements for data transmissions. Some modifications work to side systems has been planned, and additional work has been estimated and added to the ABT Project Schedule and Budget in this area.

May 2008

Better Information for Better Government

Page 14 of 19

4.0 Modification Approach

Modifications are done to provide additional functionality or to change the behavior of the available functionality within an application. Modifications fall into two broad categories. Changing the delivered objects provided by the vendor of the software systems and extending the application by providing a bolt-on application. Modifying vendor delivered objects: Modifications are done to objects that are provided by the vendor of the software systems to change the behavior to suit a specific need. Different tools and technologies are used within the different software applications. As such, any modification that is done essentially has to use the same technology to change the behavior as needed. The most common modifications are listed below. Changes to user interface screens. Changes to underlying program logic. Changes to an existing delivered report. Changes to a workflow process.

Software vendors provide the ability to change the behavior of user interface screens without having to make changes to the underlying code. As such, it is important to understand and differentiate the type of modification that is needed. Personalization is a change to a user interface screen to tailor the user interface screens look-andfeel, layout or visibility of built-in content to suit a business need or a user preference. Extensions are changes to the business logic or adding new content to extend the functionality of an application. Extensions require that the underlying program code be modified to achieve the intended functionality.

Bolt-On Modifications: Software vendors may not deliver all the functionality that is needed. As such, additional functionality may need to be provided to meet specific business needs. Such requirements are categorized as extensions and usually need a combination of user entry screen, reports and specific program logic to achieve the intended functionality.

4.1 Modification Standards:

Objects that have been modified need to be easily identified from objects that are delivered by the software vendor. The following modification approach is recommended for ensuring custom objects are preserved during software patching and upgrades. Custom Schema Custom Applications and Custom Folders Preserving the integrity of the Original Object
Better Information for Better Government

May 2008

Page 15 of 19

Naming Standards Modification Tools

4.2 Custom Schema

A Schema is a location within a database that contains database objects such as tables, packages, procedures and views among other database objects. It is recommended that all custom objects be created in the custom schema. Permissions will be given to the appropriate database user as necessary.

4.3 Custom Applications and Custom Folders (Custom TOP)

Custom Applications are defined with system Administration so that all custom objects are can be registered under the custom applications. Also a file structure is created for all custom objects that need be placed in folders. The below diagram illustrates how the file structure is defined.
$APPL_TOP $APPL_TOP (for each instance) (for each instance) <Oracle App short name> <Oracle App short name> (GL, AP, etc.) (GL, AP, etc.)

<version> <version>

<object type> <object type> (Forms, SQL, etc.) (Forms, SQL, etc.)

<Delivered object files> <Delivered object files>

XXNYS XXNYS XXKC (for all all project custom objects) (for project custom objects) <object type> <object type> (Forms, SQL, etc.) (Forms, SQL, etc.)

<Custom object files> <Custom object files>

4.4 Preserving the integrity of the original object

When modifications are made to an object that is delivered by the software vendor, the following standards are recommended. The change should be done only to the copy of the original object that is intended to be modified. The modified version should be renamed and easily distinguishable from the original name. The location of the modified version should be different from the original version.

May 2008

Better Information for Better Government

Page 16 of 19

4.5 Naming Standards

It is recommended that the same naming standards be followed that are currently used for custom objects within Oracle IBIS and PeopleSoft 8.9. In the absence of proper naming standards in IBIS, the below is recommended. See Appendix B PSSD Development Standards Characters KC concatenated with the module name, such as GL or AP followed by a brief description of the functionality of the modification is the recommended naming convention. Example: KCAP - Invoice Import Program o KC stands for King County o AP stands of Oracle Payables o Invoice Import Program is the brief description of the process.

4.6 Modification Tools

In order to preserve the integrity of the object within Oracle EBS and PeopleSoft, Modifications are done using the same tools and technologies that are used to develop the original objects. As such, when modifying the object, the same version of the tools and technologies need to be used. The following table lists out the tools and technologies used within Oracle EBS and PeopleSoft

Tool
Oracle Forms OAF( Oracle Application Framework) Oracle Reports BI Publisher PLSQL PeopleTools

Version
10G 10G 10G 8.48 or higher

Common Tool for PeopleSoft and Oracle EBS

No No No No

Purpose
Used to develop User Interface Screens Used to develop Web based User Interface Screens. Version changes with the installation Reporting tool Reporting tool Used to develop programs that contain business logic. Version is not an issue. Used to develop User Interface Screens and processes

No

May 2008

Better Information for Better Government

Page 17 of 19

5.0 About Modification Tools

Oracle Forms is a proprietary tool that has been used within Oracle e-Business Suite to provide the user interface screens. OAF (OA Framework) is a unified platform for all HTML-based applications. OAF is used to provide Web Based user interface screens within Oracle EBS. Oracle Reports is a proprietary tool that has been used within Oracle e-Business Suite to provide a complete set of ready-to-run and easy-to-read standard reports for each Oracle application module. Oracle reports 10G is the version that is currently used with Oracle applications Release 12 and can be used to design and build a variety of standard and custom Web and paper reports. BI Publisher (formerly XML Publisher) is a template-based publishing solution. By utilizing a set of familiar desktop tools such as Adobe Acrobat and Microsoft Word, users can create and maintain their own report formats based on development-delivered xml data extracts. This enables users to easily and quickly convert a prepackaged, plain-text Oracle report into a pretty-print report, with graphs and tables, and in multiple formats (such as PDF, HTML, MS Excel, etc).

PLSQL (Procedural Language/Structured Query Language) is Oracle Corporation's proprietary

procedural extension to the SQL database language. Some other SQL database management systems offer similar extensions to the SQL language. The key strength of PL/SQL is its tight integration with the Oracle database; some of the features are outlined below Can be used to create Oracle packages, procedures and triggers Data centric and tightly integrated into the database Proprietary to Oracle and difficult to port to other database systems Data manipulation is slightly faster in PL/SQL than in Java

PeopleTools is the proprietary software development environment that was created by the PeopleSoft
Corporation. Since Oracle Corporation acquired PeopleSoft, Oracle has significantly increased its development of the PeopleSoft tools with Version 8.49 as the current "latest and greatest" version of PeopleTools. The PeopleTools consist of Application Designer, Application Engine, Data Mover, PeopleCode and various other developer tools.

May 2008

Better Information for Better Government

Page 18 of 19

Appendix A: Summary of PeopleSoft 8.9 Customizations

SupportDocs\FromJenniferMa\KC Custom Menus_Complexity From JenniferMa.xls SupportDocs\FromJenniferMa\Mods from 8 0 to 8 9 Upgrade From JenniferMa.xls SupportDocs\FromBetschart-Ken\Listing of KC Modified SQRs.xls SupportDocs\FromBetschart-Ken\Count of objects in project from Betschart.xls

Appendix B: PSSD Development Standards

SupportDocs\FromBetschart-Ken\PSSD Development Standards.doc

May 2008

Better Information for Better Government

Page 19 of 19