The use of UPK throughout the Implementation Process

Most implementations and implementation methodologies have the samephases. They are Business Requirements Gathering, Gap Analysis, SolutionDesign, Conference Room Pilot, Conversion Testing (CRP 2), User AcceptanceTesting, User Training, “Go Live” and Production Support activities. The UPKtool is sometimes not used until the latter phases of a project. Quite often, it isnot until User Acceptance Testing does UPK play a part in the implementation. Iwant to show you how you can utilize UPK in each of these phases and provide amore effective faster implementation.During BusinessRequirements Gathering,you are researching your client’s processes andmaking sure they will complywith Oracle processcapabilities. UPK can beused to demonstrate thiscompliance using their pre-developed R12 content.During the demonstration,you can record any Gaps inthe process and note themon the BPR documentsprovided with the R12content. These documents provide a clear picture of the screens used in theprocess and clarify to the client any Gap detail.Once you have completed your Gap Analysis, you can start your SolutionDesign. Again, you can use the BRP document to add detail explaining how thesolution will resolve the Gap or improve the business process. In some cases, if the solution involves personalizations,descriptive flexfields or extensions which areeasily developed, you can capture them in theUPK process and provide a visualconformation of the solution to the client. Youmay wish to add signoff areas to the BPR andcollect approval for the Solution Design.As you begin to prepare for Conference RoomPilot, you can develop a set of simple UPKs for basic processes involved in the application,things like Item Creation, Invoice Creation,Purchase Order processing. These should besimple straight forward UPKs without any

exception detail. You can usethe Test Document (Word or PDF) to capture actual testtransactions using theExpected Results, Pass andFail columns provided in thedocument. These UPKs willbecome a baseline for your final set of UPKs you willleave with the client.Once CRP is complete, the implementation is usuallyready for Conversion Testing. Since conversiontesting involved the review of many records, it is goodto develop UPKs showing users how to query thosesets of records and how to cycle through them for conformation of accuracy. You can also developUPKs for exporting of those records showing the user how to extract them to another application such as aspreadsheet for faster filtering and sorting.You should now be ready for User Acceptance Testing. This means youshould have an instance with allconverted data and RICE components inplace. Prior to this, you should havedeveloped a set of UPKs closelyresembling the final UPKs the client willuse. These UPKs need to includeexception handling, such as Purchase Order cancelation, Journal Entries, WIPcomponent returns and so on.Now you should be in theprocess for End User Training. You will find the“know it” mode in UPK to bevery useful. Here the user can follow the UPK withoutthe “bubble” prompts. The