Financials – General

Get Involved. Join the Conversation.

Topic

    Johanna Rusly
    ERP – Preparing for your Release 13 Upgrade, 23 April 2...Answered
    Topic posted April 17, 2018 by Johanna RuslySilver Medal: 2,000+ Points, last edited January 30, 2019 by Sona SrinivasanSilver Medal: 2,000+ Points, tagged Allocations, Core HR, Financials, General Ledger, Payables, Receivables, Revenue Management 
    668 Views, 7 Comments
    Title:
    ERP – Preparing for your Release 13 Upgrade, 23 April 2018, 9 a.m. PT - Submit Questions
    Content:

    Submit your questions for the ERP – Preparing for your Release 13 Upgrade session to have them answered during the live event. Post your questions by posting a new comment to this topic.

    Please submit your questions by Friday, 20 April 2018.

    Best Comment

    Zoë Read

    Hi Bala,

    1. 18B will be available in your August/September/October update cycle (whichever of those months is allocated to you for updates)

    2. The 18A quarterly update is not only to resolve issues, it also contains new features. The same is true for 18B and all quarterly updates in Release 13 - there will be some new features included as well as the maintenance fixes.You can see which new features are in 18A vs 18B on the Release Readiness portal here: https://cloud.oracle.com/en_US/saas/readiness/overview   

    3. You cannot skip quarterly updates. You also cannot go from 18A direct to 18C, you will have to take the 18B update first. 

    With regards, Zoë

     

     

    Comment

     

    • Balakrishna Chaturvedula

      Hi,

      We are on R12 Oracle Procurement Cloud. We will be upgrading to R13 18A in July.

      1. Once we are upgraded, when will the subsequent patchsets ie 18B or 18C be applicable to us? 
      2. How are the patch sets 18B, 18C different than the Quarterly updates we receive on 18A? In other words, How is 18A April maintenance pack different from 18B?
      3. Right after Go-Live in July we have a quarter update. Can we skip it or does Oracle mandate quarterly updates?
      4. Can we uptake 18C from 18A or should we be mandatorily uptake 18B?

      Regards, Bala.

      • Zoë Read

        Hi Bala,

        1. 18B will be available in your August/September/October update cycle (whichever of those months is allocated to you for updates)

        2. The 18A quarterly update is not only to resolve issues, it also contains new features. The same is true for 18B and all quarterly updates in Release 13 - there will be some new features included as well as the maintenance fixes.You can see which new features are in 18A vs 18B on the Release Readiness portal here: https://cloud.oracle.com/en_US/saas/readiness/overview   

        3. You cannot skip quarterly updates. You also cannot go from 18A direct to 18C, you will have to take the 18B update first. 

        With regards, Zoë

         

         

        • Balakrishna Chaturvedula

          Thanks Zoe. Following up, in R12 we do have monthly or quarterly patch cycles. Does the same hold good for R13. If yes, what is difference between quarterly patches and upgrade patches (18B/18C etc).

          • Zoë Read

            Hi Bala,

            Yes this is still the case in Release 13.

            Your quarterly update will include both new features eg the things documented in the 18A/B New Features Summary and What's New document on the Release Readiness pages, plus it will also include the mandatory quarterly maintenance patches as you had in Release 12 to fix issues. You can still opt-in to monthly maintenance in R13 if needed.

            The difference is that now both your new features (which used to be delivered via upgrades) and problem resolutions (which were delivered via monthly / quarterly maintenance) are now rolled into one single quarterly update, to give greater service availability.  

            With regards, Zoë

             

    • Balakrishna Chaturvedula

      Hi,

      I do have another question on planning upgrade and Refresh of my DEV instance for Post Production support activities. With all other given constraints we are going live with R13 upgrade on second Monday of July ie 9th. I have two options:

      1. I am planning to upgrade DEV by June 30th so that I can request for a refresh soon after Go-Live. This will make my DEV instance available just a day after Go-Live, which is ideal. But, will I be able to refresh DEV from PROD given that fact that, on July 6th my DEV instance was updated with quarterly patch set?

      2. I can delay DEV instance upgrade and refresh till Go-Live and request for that on July 10th. Obviously, I will have to request Upgrade first. When I do that, will Cloud Ops upgrade to R13 and also apply July patchset? If they do, we may not be able to Refresh DEV. So, the sequence should be R13 Upgrade, Refresh and July Patchset application. How would we request for that? Also, the downside of this would be, I will not have DEV instance for about 4 days for all this to happen.

      Regards, Bala.

      • Joe Gum

        Bala, 

        You would probably be best suited to Go-Live, Refresh, and then Upgrade.

        However, it is really your choice.

        Joe

    • Balakrishna Chaturvedula

      Hi Joe,

      Thanks for your response. We are going live with R13. After Go-Live, I cannot refresh DEV as it will still be on R12. Attached is picture of activities on my instances. So, Can I mention the series of activity (Upgrade-Refresh-Quarterly patch) to Cloud Ops team on the SR? Let me know.

      Thanks, Bala.