Update Synonyms procedure - What it does and why it is important to EBS/ASCP - Demantra implementations (Doc ID 1061331.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Demantra Demand Management - Version 7.2 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Nov-2016***

Goal

This document discusses the Update Synonyms procedure and what is does and what objects it updates. 

1) When should it be run?

Anytime a Demantra -  EBS/ASCP integration patch is run.  Example of one of these patches is <Patch 8703840>

2) How is this procedure run?

Navigation -
   Demand Management System Administrator
      -> Other  -> Requests
                  -> Submit a New Request  -> Single Request

Special instructions for Clients who have more than one Demantra schema

The "Update Synonyms" concurrent program has a hidden parameter p_schema_name.

If the user has only one Demantra schema then the user can leave the parameter to be hidden. But, if the user has mutiple demantra schemas then user can enable hidden parameter to visibility.

System Administrator Responsibility   
    -> Concurrent
        -> Program
            -> Define

After enabling the parameter, when the user submits the concurrent program then the user can
specify against which demantra schema user wishes to run the concurrent program.
Enabling the parameter option is given to select th correct Demantra schema out of multiple schemas by the user

3) What are the more common issues that indicate that this Update Synonyms procedure needs to be run?

Any issue where EBS/ASCP doesn't seem to be communicating correctly.  For example, a user logs into the Demand Management responsibility in EBS but doesn't get transferred over to the Demantra application

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms