1059 upgrade vs reimplement final
TRANSCRIPT
-
8/11/2019 1059 Upgrade vs Reimplement Final
1/25
A 12:
D A K ?
Oracle Apps Reimplement VS Upgrade
..
. . L.
D @.
-
8/11/2019 1059 Upgrade vs Reimplement Final
2/25
A :
1: I
.
..Copyright 2011 eprentise. All rights reserved.
2
2: L
.
3: I E
B 12.
-
8/11/2019 1059 Upgrade vs Reimplement Final
3/25
I
EB D
D D F
F C C (C) E
..
B
C G 12
C EB L 12
( + ) .
A
10 C I
3Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
4/25
E 2006 EB H A, CE
? :
D C
A
A
, A , D
EB :
C EB
C ,
C A, F
..Copyright 2011 eprentise. All rights reserved.
4
B
E A
A
I , ,
E
I
G, L E, L
C
, ,
ID
D
-
8/11/2019 1059 Upgrade vs Reimplement Final
5/25
,
, , .
EB
.
..
E 11 12
5Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
6/25
,,
..
C
(C) EB
12
6Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
7/25
-
8/11/2019 1059 Upgrade vs Reimplement Final
8/25
.. 8Copyright 2011 eprentise. All rights reserved.
Source:oracle open world/stevenChan
-
8/11/2019 1059 Upgrade vs Reimplement Final
9/25
A
12.
C
,
,
..
, ,
E
C, ,
12 .
G
.
9Copyright 2011 eprentise. All rights reserved.
Has been the preferred path to new EBS
releases
Many experts now advising this path
-
8/11/2019 1059 Upgrade vs Reimplement Final
10/25
E
D
C A
..
B G, L, L E,
D EB
E
Copyright 2011 eprentise. All rights reserved. 10
-
8/11/2019 1059 Upgrade vs Reimplement Final
11/25
L
G 12
I
..
,
F , 12
Copyright 2011 eprentise. All rights reserved. 11
-
8/11/2019 1059 Upgrade vs Reimplement Final
12/25
ReimplementationTasks
To Implementor
Reimplement(person days)
Cost based on$/Rs---/day
Assumptions
C
I 60
3 Business Cycles (purchase-to-pay, order-to-cash,hire-to-retire),One month,2 functional resources per businesscycle
C E 240 2 technical resources, 2 months per business cycle
C
C 180 3 technical resources, 1 month per business cycle
C L 240 2 technical resources, 2 months per business cycle
/C 180 3 technical resources, 1 month per business cycle
E
..
E 90 3 technical resources, .5 month per business cycle
I
C I 60One month,2 functional resources per businesscycle
C C
I 30One month,.5 functional resource per businesscycle
I 60One month, 2 functional resources per businesscycle
I
C II 60One month, 2 functional resources per businesscycle
C C
II 30One month,.5 functional resource per businesscycle
A 180One month, 3 functional resources per businesscycle
G L C 45 3 resources 15 days
D 1455 $........................Duration approximately 14 months
Copyright 2011 eprentise. All rights reserved. 12
-
8/11/2019 1059 Upgrade vs Reimplement Final
13/25
Phase 3 - Technical Upgrade to R12Duration(workdays)
Total Tech& Func StaffNeeded forPhase
FunctionalDays
TechnicalDays
FunctionalCost
TechnicalCost
StaffResourceCost
I:
11.5.10 12 20 5 30 60
..Copyright 2011 eprentise. All rights reserved. 13
Subtotal - Resource Costs Phase 3
E
-
8/11/2019 1059 Upgrade vs Reimplement Final
14/25
11 12
: E 11 ()?
L () 12 ?
E 12
11 12
11
..
12 11
I 12: . ()
E , 12
,
14Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
15/25
: 11
C C A
C C, C
B G, B, L
E,
..
C I
Copyright 2011 eprentise. All rights reserved. 15
-
8/11/2019 1059 Upgrade vs Reimplement Final
16/25
-
8/11/2019 1059 Upgrade vs Reimplement Final
17/25
,
Traditional Migration Approach Cons Remodeling Approach Pros
Requires technical knowledge of all tables and usage inthe E-Business Suite.
Repeatable results, reusable as requirements change. Asrequirements change, only need to add/change rules, astep that is usually done by a functional user on aspecially designed user interface in the software In a veryshort time.
APIs do not exist for all tables. There is a risk ofcompromising the data integrity by extracting and loading
data incorrectly. Oracle Support not available.
All data integrity is maintained because the code isautomatically generated.
..
History is generally not converted. Generally a sunsetinstance is required for reporting, reconciliation, businessintelligence, and audits. Every time the sunset instance isaccessed, data must be transformed to align with the R12instance.
All history is converted so there is no need to maintain asunset instance for reporting, reconciliation, etc. All thedata is complete and consistent.
Need to configure R12 instance No need to configure R12 instance
Scripts are written for the current state of the data. Anychanges require re-writing of the scripts.
Full documentation of existing instance includingcomparison of instances
12-24 months duration 3-8 months duration
17Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
18/25
:
F C
L E, B,
C,
CA
B
D
..
EB
I
C A
(CA)
B I
Copyright 2011 eprentise. All rights reserved. 18
-
8/11/2019 1059 Upgrade vs Reimplement Final
19/25
12: +
.. 19Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
20/25
-
8/11/2019 1059 Upgrade vs Reimplement Final
21/25
EBS 1COA w/ Obsolete
COA
1.A Change
COA
EBS 1COA w/ Global
COA
11.5.10
11.5.10
1. 1
.
2. 2
.
3. 11 .
.
4. 12, .
, , .
12:
.
.
EB 1
EB 2
1.BReorganization
2CA /
2CA / G
2.Consolidation
EBS 1 GlobalGlobal COA and
calendar
3. R12
Upgrade 1
12
11.5.10
11.5.10
11.5.10
1211.5.10
Copyright 2011 eprentise. All rights reserved. 21
-
8/11/2019 1059 Upgrade vs Reimplement Final
22/25
10
1. .
2. C A.
3. EB 11.
7.
.
8. A
.
..
4. , .
5. .
6. A .
.
12
.
10. .
Copyright 2011 eprentise. All rights reserved. 22
-
8/11/2019 1059 Upgrade vs Reimplement Final
23/25
C 11
.
.
CA.
..
.
CA CA.
.
.
D .
D .
. *
23Copyright 2011 eprentise. All rights reserved.
-
8/11/2019 1059 Upgrade vs Reimplement Final
24/25
?
..Copyright 2011 eprentise. All rights reserved. 24
-
8/11/2019 1059 Upgrade vs Reimplement Final
25/25
!
Satish Tiwari eprentise [email protected]
..
25Copyright 2011 eprentise. All rights reserved.