Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Siebel Business Process & Functionality (MOSC)

ACR 500 Promotion Disconnect Action enhancement

Oct 30, 2015 10:07PM edited Dec 16, 2016 12:07AM in Siebel Business Process & Functionality (MOSC) 2 commentsAnswered

Hi All,

as per the ACR 500 Promotion Disconnect Action enhancement,

A. The statement as per ACR 500

When Disconnect is specified in the Disconnect Action field:

The instance(s) associated to the relationship will be disconnected when the promotion is disconnected.
Promotion can be disconnected through the disconnect process or the upgrade process.

B. The Requirement

We have a requirement for Upgrade promotion, while migration from Old Promo to New Promo,

- if the Root Product exist in new Promo then move the Root Product to the new Promo

- if the Root Product does not exist in the new Promo then Delete the Root Product.

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

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

Category Leaderboard

Top contributors this month