1 Copyright © 2011, Oracle and/or its affiliates. All ... · PDF file• Step 1...

1 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.


The following is intended to outline our general product direction. It is intended for information purposes only, and may not be

incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making

purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the

sole discretion of Oracle.

Safe Harbor Statement

3 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. 3 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Leveraging Historical Customer Context in Planning Future Upgrades

Nirmal Natarajan / Rajesh Dhandayuthapani Senior Software Engineer –EBS Product Support Group


Program Agenda •  Why Upgrade to latest Release •  Abstract •  Value Proposition •  Flow Chart •  Before Upgrade/Migration •  How to gather and categorize Historical Data •  Checking the availability of prior release fixes •  Additional References •  Q&A


Flow Chart


Abstract

•  Conventionally, upgrades to new releases (for e.g. EBS R12.1.x) can sometimes be a catch 22 situation. Leveraging the benefits of new features can make a business more efficient, however the cost/risk to upgrade is unknown and timelines may be uncertain.

•  Often we may overlook the value of historical (known issues from prior releases/past upgrade experience) context when it comes to predicting the future, however if we believe that past performance is any indicator of future outcomes, leveraging historical customer context can provide a good head-start in planning future upgrades.


Value Proposition

•  With the above premise, the objective of this R12.1.x upgrade white paper encompassing EBS modules is two-fold

•  The while paper would contain a) recommended phased Migration /Upgrade approaches, b) suggest resources from our vast expanse of KM to help resolve functional / technical issues which could come up during the EBS R12.1.x upgrade / Post Upgrade process by analyzing known issues in prior/present releases and c) identify post upgrade support (for e.g. patching) requirements based on experience

•  The white paper would be intended primarily for technicians who are helping to evaluate or manage an upgrade, but it also contains useful information for anyone who might be involved in the upgrade process


Before Upgrade/Migration Data Migration

•  User Guide for upgrade http://docs.oracle.com/cd/B53825_08/current/acrobat/121upgrade.pdf

•  Patching & Maintenance Advisor: E-Business Suite (EBS) 11i and R12 (Doc ID 313.1)

•  E-Business Suite Release 12 Upgrade Sizing and Best Practices Note# 399362.1

•  Patch Wizard Utility (Doc ID 976188.1) •  Upgrade Advisor: E-Business Suite (EBS) Upgrade from 11.5.10.2 to 12.1.3 (Doc ID

269.1)


Before Upgrade/Migration


Upgrade Documents

•  R12.1 documentation roadmap (790942.1) •  Database preparation guidelines for R12.1 upgrade (761570.1) •  Patching FAQs (459156.1, 225165.1) •  OAM “Patch Wizard” overview and FAQ (976188.1) •  AD Command Line Options for Release R12 (1078973.1) •  R12 Upgrade Sizing & Best Practices (399362.1)


How to gather and Categorize Historical Data •  The below steps will assist in gathering / categorizing the historical data •  Step 1 – Historical SRs logged in MOS (formerly Metalink) •  Step 2 – Issues identified and solved by customer/DBA outside of the SR process

•  A sample spreadsheet (Historical_Data_Categorization.xls) has been enclosed in this white paper to aid the categorization of the data gathered from MOS / Metalink and other sources.

Issue Type Solution Document ID/Bug Code Fix Patch Number 432.1

Setup Setup 256496.1

Data Fix Specific Fix Data script


How to gather and categorize Historical Data Step 1 – Historical SRs logged in MOS (formerly Metalink) •  Gather all the SRs which were created in the last one year. Please use the respective

CSI in MOS and export the SR data as CSV.


How to gather and categorize Historical Data •  Open the csv file and copy and paste the S.R. No and SR Description columns into the

Sample spreadsheet (Historical_Data_Categorization.xls) provided. •  Identify the solution from the SR’s and classify the SR’s ( Issue type ) based on the

solution. •  If it’s a Code Fix , note down the patch number in the solution

•  A sample illustration after you have completed this process is shown below


How to gather and categorize Historical Data Step 2 : Issues identified and solved by customer/DBA outside of the SR process •  There may be instances where Customers/DBA’s will have the details archived of all

the solutions applied in the prior releases/instances which have not been tracked in MOS (Step 1)

Code: To obtain the patches applied in the prior releases

•  Go to System Administration -> Oracle Application Manager -> Patching and Utilities •  Make note of the patch/ bug numbers which were applied outside the SR process.


Issues identified and solved by customer/DBA outside of the SR process


Issues identified and solved by customer/DBA outside of the SR process •  . Functional/Setup: Verify with Apps DBA to check if any notes/documents relevant to

setups in prior releases are relevant for the upgraded release. Take note of the note/document Ids.

•  A sample illustration after you have completed this process is shown below


Checking the availability of prior release fixes •  From the sample (Historical_Data_Categorization.xls) , query the first Bug or Patch

number (Issue Type – Code Fix) in MOS (Formerly Metalink) under the Patches •  Example: Search the patch 5593841 (fixed in 11i) – in All “Sources Search” , the result

will display the note id which contains the information of R12 Patch

Code


Checking the availability of prior release fixes

•  If a Code/setup fix/suggestion is not available for Upgraded release, you may need to raise a Service Request with support.


Checking the availability of prior release fixes •  From the sample (Historical_Data_Categorization.xls) xls, query the first Bug or Patch

number (Issue Type – Setup) in MOS (Formerly Metalink) under the Knowledge. •  Example: Search the Note 1114515.1 (fixed in 11i) – in All “Sources Search” or

Knowledge Search , the result will display the note id which contains the information of R12 Patch

Setup



•  If a setup fix is not available for Upgraded release, you may need to raise a Service Request with support.



1 32

MOS Search


Checking the availability of prior release fixes •  Knowledge” - Note id , Profile options •  “Patches and update” – Bugs , Patch “All Sources” - Error No, Setup , Keywords Example : If an Purchase Order Stuck in status “In Process” we can use the option 1

and 3 to search “PO” “INPROCESS”

•  Similarly we can user the Error code or setups to verify the errors.


Data Fix Generic fixes •  The root cause is unknown, however the generic data fix is available to resolve the

issue in prior release. •  In generic data fix there won’t be any hard coded values in the SQL statements.

How to Verify the fix available for upgraded release •  From the PIC “E-Business Suite Product Information Center Index (Doc ID 444.1)” •  Navigate to the respective modules, known generic data fix with root cause will be

listed.


Generic fixes



Specific fixes •  There could be some data corruption in the table for an specific document .We might

have provided specific fix for your case. Example: Purchase order quantity is wrong in shipment and distributions, we might

have updated the correct quantity for an single/set document.

•  Normally once the patch (data script) is applied, the same issue should not exist. •  If the issue still exists, you may need to raise a Service Request with support.


Service Request with Support •  Case 1 (Code) – Code Fix •  11i Patch/Bug Number, if SR number available provide that detail also •  Business Impact (like Go Live Date) •  Case 2 (Data Fix) – Specific •  Please provide the data from the R12 instance ( Upgraded instance )

•  Business Impact (like Go Live Date) •  Case 3 (Data Fix) – Generic •  Please confirm that there is not generic fix exits from the above note 444.1 •  Note(Document) Number of Data fix page based on the SR. Also check whether the

issue exists in R12 instance .

•  Business Impact (like Go Live Date)


Other useful Resources

•  You can refer the Product Information Center for guidance on Functional/Setup and new feature related information

•  E-Business Suite Product Information Center Index (Doc ID 444.1) •  Get Proactive with Oracle E-Business Suite (Doc ID 1388190.1) •  EBS Support Delivery Proactive Catalog Matrix (Doc ID 1328360.1)

•  EBS Release 11i Information Center (Doc ID 112552.1) •  EBS Release 12.0 Information Center (Doc ID 401740.1) •  EBS Release 12.1 Information Center (Doc ID 806593.1)

1. Product Information Center


Additional References 2. Communities •  https://communities.oracle.com 3. News Letter •  Oracle Discrete/Process Mfg News Volume 35, September/October 2011 (Doc ID

1370683.1)

•  Oracle Order Management News Volume 20, September/October 2011 (Doc ID 1371658.1)

•  Oracle Inventory News Current Edition (Doc ID 205.1) •  Oracle Procurement News Current Edition [Document 111111.1]


Post Migration

Performance best practices •  Review document 244040.1 for latest EBS recommended performance fixes


Q&A



Date post:	14-Mar-2018
Category:	Documents
Upload:	lynhan
View:	221 times
Download:	8 times