Question 101 and 102 1.1.5.

A Describe the process you will utilize to finalize requirements and roles for User etups durin! "hase #A Desi!n. $ow will this process ensure that User etups completed for "hase #A do not cause e%cessi&e rewor' for future phases( )ole *ame
Purchasing Super User

Department

Description+"ersona
1. Creating Approval Limits 2. Creating Create Buyer 3. Creating HR !mployees " #o$s% Positions &. 'e(ine Purchasing Categories 1. Create Re)uisitions

,ocation + - of persons

Re)uester

2. *anage Re)uisitions 3. Receive +oo,s% Services &. Return +oo,s

Re)uisition Approver Buyer

1. Approve Re)uisitions 2. Action Re)uisition 1. Create P2. Action P3. *anage P-s

Paya$le Super User

1. Responsi$le (or Con(iguration o( -racle Paya$les *anager $oth (or Stan,ar, an, Custom Process. 2. *antaianance o( Con(iguration o( Paya$les in aligns .ith any changes. /his .oul, inclu,e maintaining Custom Loo0ups1 2alues Set 3'44 values5. 3. Responsi$le (or *aintaining Users1 .hich .oul, inclu,e creating ne. Users1 ,eactivating 6nvali, Users an, *o,i(ying User 'etails.

Paya$le User

1. *atching AP 6nvoices to P- an, 2ali,ating 2. Run 6nter(ace Program to maintain 2en,or 'etails in sync .ith Legacy systems. An, also maintain *aster ,ata in -racle Paya$les. 3. Run 6nter(ace Program to sync 6nvoice Payment status (rom 2PS 1. Rea, only -ptions to vie. 6nvoices

Paya$le 6n)uiry User P- an, AP *onth en, Activity User

2. Rea, only -ption to vie. Payment Status

1. Post #ournals to -racle +L an, Reconcile 2. Responsi$le (or all P- an, AP *onth !n, activities 3. Close AP Perio, &. Supplier Reporting 7. 6n)uiries an, Reporting

)ole *ame

Department

Description+"ersona
8. Close Purchasing Perio,

,ocation + - of persons

+eneral Le,ger Super User

1. Responsi$le (or Con(iguration o( -racle +eneral Le,ger $oth (or Stan,ar, an, Custom Process. *aintain Chart o( Accounts *aintain Security an, Cross 2ali,ation Rules *aintain Calen,ar *aintain Currency an, !9change Rates *aintain Bu,get 'e(initions *aintain /a9 Setup

2. *antaianance o( Con(iguration o( -racle +L in align .ith any changes. /his .oul, inclu,e maintaining Custom Loo0ups1 2alues Set 3'44 values5. 3. Responsi$le (or *aintaining Users1 .hich .oul, inclu,e creating ne. Users1 ,eactivating 6nvali, Users an, *o,i(ying User 'etails.

1.Creating an, 6mporting #ournals -racle +L User 3Accouting A,min5 +L *onth !n, Activity User 2.Revie.ing #ournals 3.Create Reverse #ournals 1. Reconcile Control Accounts 2. Process Accruals : A,;ustments 3. Close +L &. 'e(ine : Run 4S+ Reports 7. Run Stan,ar, Reports : Listings 8. /a9 Reporting

QU. /01* 102 3 1.2.1.A ummarize your understandin! of the functionality in scope4 in terms of processes within 1racle .5 that will be included in confi!uration( 0n cope 1. Configuration of Oracle Payables 2. Adding, Modifying and Deleting Vendor Data to sync with Legacy yste! ". #nbound #nterface fro! Content Manager for Vendor Attributes ". Matching AP #n$oice with PO

%. #nterfacing Pay!ent tatus of AP #n$oice fro! VP &. Configuration of Oracle 'L (. #nterface to ync COA fro! )A to Oracle 'L to Ma* 'L accounts. 1ut of cope 1. #n$oice Pay!ent acti$ity 2. Maintenance of +an, !aster data ". Pro$iding Vendor details to VP %. -econciling +an, tate!ent &. Creating and *ay!ent of .!*loyee ./*enses

Question 1#6 0 1.5.D "lease describe your approach to &alidatin! and applyin! standard functionality to client business processes. 7hat is the process for determinin! what e%tensions may be required( Oracle 1nified Methodology is one of Ca*ge!ini2s leading !ethodologies which is le$eraged to our custo!ers around the globe and is *ro*osed for this engage!ent. Ca*ge!ini has ado*ted Oracle3s O1M !ethodology for the Pro4ect #!*le!entation which is aligned with the $arious #ndustry tandards including the 1ML, 1nified Process, +usiness Analysis +ody of )nowledge 5+A+o)6, +usiness Process Modeling 7otation 5+PM76. 8his section s*ecifically e/*lains the O1M *ro4ect !ethodology and so!e of the ,ey ad$antages it offers.
Capgemini Approach and Methodology /his complete section ,escri$es a$out o( the lea,ing Capgemini implementation metho,ology i.e.1 -RACL! Uni(ie, metho,ology .hich .e have leverage, to our customers an, is propose, (or this engagement.

OUM Implementation Process

Phases
Inception Elaboration Construction Transition Production

Pro;ect *anagement Business Re)uirements Re)uirements Analysis Analysis 'esign 6mplementation /esting Per(ormance *anagement /echnical Architecture 'ata Ac)uisition an, Conversion 'ocumentation -rgani<ational Change *anagement /raining /ransition -perations an, Support Iterations Milestones LO LA IOC SP SO
6nitial !la$. =1 !la$ =2 Constr. =1 Constr. =2 Constr. =3 /ran. =1 /ran. =2 Pro,. =1 Pro,. =2

Camel hump diagram highlighting 15 Processes involved and 5 Phases of OUM Methodology which would be leveraged for this engagement.

Project Implementation Methodology

+ased on our re$iew of )roger3s business re9uire!ents, we *ro*ose a iterati$e and incre!ental a**roach to rollout Oracle a**lication solution across Co!*utec : erasa. 8his a**roach will utili;e the Oracle 1nified Method 5O1M6, which is a standards0based !ethod to de$elo* and de*loy infor!ation syste!s.
Phases in OUM

Inception

Elaboration

Construction

Transition

Production

C P!

C P"

SIT

UAT

Prod

Various phases in our implementation methodology for smooth e ecution of the pro!ects for our customers across industries using OUM methodology 0nception 8,ifecycle 1b9ecti&es :ilestone ;,1<. 8he #nce*tion *hase is used as the s*ringboard to begin the *ro4ect. During this *hase we will analy;e the sco*e of the *ro4ect, significant ris,s and confir!, docu!ent and *rioriti;e the high0le$el re9uire!ents. Processes will be established for issue !anage!ent, ris, !anage!ent, status re*orting, *ro4ect *lan u*dates, staffing, resource !anage!ent and on0boarding. trategy for configuration !anage!ent, testing, data con$ersion, integration and all related *lanning is docu!ented. .laboration 8,ifecycle Architecture :ilestone ;,A<. 8he ob4ecti$es during this *hase are to de$elo* and $erify the detailed business re9uire!ents, *artition the solution, create *rototy*es and baseline the architecture of the syste!. =onstruction 8 0nitial 1perational =apacity :ilestone ;01=+ 0/<. 8he goal of the Construction *hase is to ta,e the solution fro! detailed re9uire!ents !odels, through configuration of standard *ac,aged software functionality, de$elo*!ent and testing of custo! co!*onents, and integration to a syste! that is ready for a first release that goes into *roduction. /ransition8 ystem in "roduction :ilestone ; "+UA/<. 8he goals of the 8ransition *hase will be to !o$e the new solution into the Production syste!, *erfor! user acce*tance testing 51A86, conduct user training and de*loy the new syste! to the user co!!unity 5'o0Li$e<6. During this *hase, the new syste! is acce*ted by the organi;ation, the organi;ation is !ade ready for the new syste!, and the syste! is *ut into *roduction. "roduction8 i!n31ff :ilestone ; 1+"roduction<. 8he Production *hase is focused on su**orting the new syste! and users, and assessing the *rogress of the new syste!.Ca*ge!ini will su**ort and transition this ,nowledge to the )roger hel* des, and su**ort tea!.

During .laboration "hase4 re9uire!ent gathering and deter!ining ./tensions will be co$ered. Detail Acti&ity of the same is e%plained below.
Elaboration Phase 8he ob4ecti$es during this *hase are to de$elo* and $erify the detailed business re9uire!ents, *artition the solution, create *rototy*es and baseline the architecture of the syste!.

Business Requirements Discovery )ey ele!ents of the .laboration *hase are consensus, docu!entation and acce*tance of the future state business re9uire!ents. #nfor!ation about the e/isting business *rocesses and future )roger re9uire!ents will be collected and docu!ented through structured wor,sho*s and focused inter$iews. 8hese wor,sho*s and inter$iews will address the locali;ation re9uire!ents and *rocesses. Ca*ge!ini leads will facilitate these e/ercises and bring benefit *rocesses for e$aluation. 8he underlying a**roach to this *ro4ect is to focus on standard business *rocesses which are already *art of current te!*late to reduce any ga*s which !ay result in enhance!ents. During this *hase, we will e$aluate Oracle -12 out of the bo/ functionality or fro! current te!*late in order to align )roger business with the future state business *rocesses and re9uire!ents. 8his is an i!*ortant ele!ent of a transfor!ation where we loo, to utili;e e/isting )roger 5=A 0# >6 business *rocesses in current te!*late for the future state 5=8O0+.>6 )roger business. 8he ulti!ate goal is to reduce business *rocess e/ce*tions. +usiness and #8 consensus is essential to docu!ent business *rocesses, confir! re9uire!ents and address e/ce*tions in ter!s of wor, around *rocesses or de$elo*!ent of custo! ob4ects 5enhance!ents6. .ach de$iation 5ga*6 will re9uire a solid business case a**ro$ed by the steering co!!ittee before an enhance!ent re9uest is tabled for *rocessing. +usiness re9uire!ents are signed off by the )roger business to for! the basis for the *ro4ect functional sco*e. Elaboration Instances De$elo*!ent 5De$ 16 D.V 1 will begin the de$elo*!ent efforts for the custo! a**lications Data Con$ersion Data con$ersion instance will be used for data con$ersion !oc,0u* runs 5!ulti*le cycles6 in su**ort of data con$ersion. )eports4 0nterfaces4 =on&ersions4 and .nhancements ;)0=.>< )equirements At a !ini!u!, the *ro4ect will re9uire data con$ersion and interface -#C.? co!*onents. ?or each a**ro$ed -e*orts, #nterfaces, Con$ersions, .nhance!ents 5-#C.?6 ob4ect the functional tea! will de$elo* functional s*ecifications that will go through a rigorous *eer re$iew with the business and the technical tea!s. 8he hand0off *rocess has been enhanced fro! functional to technical de$elo*!ent tea! in the interests of achie$ing high 9uality standards of de$elo*ed -#C.? ob4ects. 8his reduces -#C.? re0 wor, significantly to a$oid e/tended ti!e lines and budget o$erruns. 8he *rocess for the design of the custo! a**lications and -#C.? ob4ects consists of the following@ Pre0defined te!*lates 5based on Oracle O1M6 for functional s*ecifications for each custo! a**lication and -#C.? ty*e is agreed to by the de$elo*!ent tea! #nclusion of business scenarios in the functional s*ecification facilitates de$elo*!ent of the ob4ect, test scri*ts and test data for 9ualification of the ob4ect Peer re$iews will include the a**ro*riate )roger business user, Ca*ge!ini functional *rocess lead and de$elo*!ent tea! with right of refusal by the de$elo*!ent tea! if there is not sufficient infor!ation in the functional s*ecification Peer re$iews will be conducted for all -#C.? functional s*ecifications to enable 9uality control. -e$iews are su**orted by a *eer re$iew log and acce*tance signatures.

An inte!ral *art of the -#C.? co!*onents is con$ersions. 8he source of the con$erted data for this *ro4ect will be the current Legacy syste!. 8he con$ersion tea! !ust start as soon as *ossible after the start of the *ro4ect. 8he tea! will start !a**ing the source data to -12, s*ecifically static data. Ae ha$e sco*ed our offering on the basis that data cleansing if any would be )roger3s res*onsibility. As the tea! *rogresses they will include any other data sources and *otential transactional data con$ersions. Please reference the list for to be !aster and transactional data ob4ects. 8here is an o**ortunity at the end of the .laboration *hase to re0e$aluate the *lanning de*ending on the outco!e of the re9uire!ents $alidation assess!ent. #n the interests of !aintaining !o!entu! on the *ro4ect and accelerating the ti!e line, it is reco!!ended that -#C.? ob4ects ,nown to be ,ey to the )roger business be released for de$elo*!ent 5*art of the Construction *hase6 against an initial target budget B the designCde$elo*!ent cycle is usually a cascaded e$ent to a$oid a lengthy brea, in the *ro4ect while waiting on co!*letion of the design *hase. Ae will wor, with )roger3s re*ository of current ob4ects fro! current *rocess for *otential re0use of e/isting ob4ects in su**ort of the agreed business *rocess. #t is essential to e/*ose ,ey tea! !e!bers of the de$elo*!ent tea! to the functional re9uire!ents as soon as *ossible in the *rocess B this has far reaching benefits during the de$elo*!ent cycle.