Retail Price Management (MOSC)

MOSC Banner

RPM- Conflict Check

in Retail Price Management (MOSC) Question

We have an entry in the rpm_conflict_query_control table for a custom rule and the custom rule pkg is existing in the DB. The rule was working fine for a few set of price changes applied. A change to the function name inside the pkg is causing all records to go into conflict check. Even more strange is the fact that when we just rename the function to its original name, the rule starts working fine. It appears as if this name is being held in memory or tagged somewhere which is causing the same rule to fail when it is

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center