Pricing

Get Involved. Join the Conversation.

Topic

    carl casey
    You Must Use the Sand Box to Edit Service Mappings
    Topic posted October 17, 2019 by carl casey, tagged Pricing 
    27 Views, 1 Comment
    Title:
    You Must Use the Sand Box to Edit Service Mappings
    Summary:
    You must use a sand box when you edit a service mapping.
    Content:

    If you access the Manage Service Mappings page outside of a sand box, then the page disables the actions you need to edit the mapping, such as Add Row.

    Try it.

    1. In the Navigator, click Sandboxes.
    2. On the Sandbox page, click Create Sandbox.
    3. On the Create Sandbox page, enter any text in the Name attribute. For this example, enter Sandbox for Pricing Administration.

        You can also use a sand box that already exists.

    1. Add a check mark to the Manage Service Mappings tool, then click Create and Enter.
    2. Edit your service mapping.
    3. At the top of the page, click Sandbox for Pricing Administration > Publish.

    For details about how to use the sand box, see the Create and Activate Unified Sandboxes topic.

    Image:

    Comment

     

    • Shyam Singh Patel

      Hi Carl,

      Thanks for letting us know this change in 19D

      I had gone through this feature. They are recommending to use this opt-in feature from 19C itself so that we can get used to this new feature now itself. From 19D onwards, this will be the default feature for Sandbox related customisations. Few critical points summarised below on how they will affect us (if we opt-in this feature):

       

      1. New profile options
        1. Maximum Number of Sandboxes: Controls the number of Sandboxes that can be created at any point in time. The default value is 20, we can increase this value as per our requirement (there is no maximum limit specified)
        2. Control Publish Sandbox Action in Production Environment: To enable publishing, set this profile option to Yes. In the Setup and Maintenance work area, use the Manage Applications Core Administrator Profile Values task in the Application Extensions functional area.
      2. New Privileges:
        1. Administer Sandbox (FND_ADMINISTER_SANDBOX_PRIV) privilege, is required for publishing sandboxes.
        2. Users having the Manage Sandbox (FND_MANAGE_SANDBOX_PRIV) privilege can edit but not publish sandboxes.
        3. While those having the View Sandbox (FND_VIEW_SANDBOX_PRIV) privilege can view sandboxes in read-only mode.
      3. Flexfields deployment not supported: You can't deploy your flexfields to a sandbox if you have opted in to Unified Sandboxes. You must deploy them directly to the mainline environment.
      4. Import and Export impact: You must delete existing sandboxes before importing new configurations to release all locks and to prevent users from thinking that they can refresh and publish after an import.
      5. Preview Sandbox: Test or validate your changes in the sandbox in preview mode before actually publishing it. If you made changes using Page Composer, don't forget to close it before testing. To preview your changes, click the Sandbox Mode drop-down button on the sandbox bar above the global header, and select Preview as if Published (Context: All).

      Note: You can see the sandbox bar only when you're in an active sandbox.

       

      More info can be read here: https://docs.oracle.com/en/cloud/saas/applications-common/19d/oaext/configuration-life-cycle.html#OAEXT3456432


      Regards

      Shyam