Service

Get Involved. Join the Conversation.

Topic

    Mohana Gopal Selvam
    Configure the Prefix and Radix for Service RequestsAnswered
    Topic posted March 11, 2019 by Mohana Gopal SelvamSilver Crown: 22,500+ Points, tagged Configuration and Administration, Setup and Configuration 
    219 Views, 8 Comments
    Title:
    Configure the Prefix and Radix for Service Requests
    Content:

    Hi,

    I tried to create unique sequence for the SR as per the document. 

    https://docs.oracle.com/en/cloud/saas/engagement/19a/faiec/using-profile-options-lookups-and-scheduled-processes.html#FAIEC3263662

    I login as 'Application Administrator' Role user and navigate to 'Manage Public Unique Identifier Sequence Generation' page and click new button. I could not see the Service Request Object in the Object drop down.

    How to fix this?

    Thanks,

    Mohan

    Best Comment

    Hari Menon

    @Mohan: The PUID functionality was added for SR object in 19A release (11.13..19.01)

    For 18C(11.13.18.10), refer to this link on configuring the SR number: https://docs.oracle.com/en/cloud/saas/sales/18c/faiec/using-profile-options-lookups-and-scheduled-processes.html#FAIEC3076532

    @Reghu: You are right. Since the PUId is already configured for the SR object and exists in the table, you will not see it in the drop down,

    -Hari

    Comment

     

    • Hari Menon

      Hi Mohan,

      Sorry, asking a dumb question: Do you not see service request in the table for this task: Manage Public Unique Identifier Sequence Generation?

      Would you mind attaching the screenshot of the page and the drop down?

      Can you also confirm if your pod is a new 19A environment? or an environment upgraded to 19A?

      -Hari

    • Reghu

      I just tried this task,  the SR object was coming by default and with prefix  'SR'.  Is that what you mean  Hari? 

       

      However, its not appearing in the dropdown if I try to add it.  May be because its existing in the list already?

    • Mohana Gopal Selvam

      Hi Hari,

      Please find the screenshot.

      Application Version: Revision 13.18.10 (11.13.18.10.0)

      @Reghu, Do we need to add SR object manually? How?

      Thanks,

      Mohan

    • Hari Menon

      @Mohan: The PUID functionality was added for SR object in 19A release (11.13..19.01)

      For 18C(11.13.18.10), refer to this link on configuring the SR number: https://docs.oracle.com/en/cloud/saas/sales/18c/faiec/using-profile-options-lookups-and-scheduled-processes.html#FAIEC3076532

      @Reghu: You are right. Since the PUId is already configured for the SR object and exists in the table, you will not see it in the drop down,

      -Hari

    • Reghu

      Thanks Hari

    • Mohana Gopal Selvam

      Hi Hari,

      Thanks for your response. How to identify the release from the version number? 

      11.13.YY.MM - My understanding correct?

      Thanks,

      Mohan

       

      • Hari Menon

        Yes, you are correct.

        11.13.YY.MM is the correct format.

        There are typically 4 public releases in a year: ABCD

        so 

        11.13.19.01 is the 19A release or first release of 2019

        11.13.19.05 is the 19B release or 2nd release of 2019

        11.13.19.08 is the 19C release or 3rd release of 2019

        11.13.19.11 is the 19D release or 4th release of 2019

         
        At least that is how it works currently.
         
        Hope that helps
        Hari