My Oracle Support Banner

RPM Webservices Stuck In Conflict Checking (Doc ID 2760862.1)

Last updated on MAY 16, 2022

Applies to:

Oracle Retail Price Management - Version 15.0.3 and later
Information in this document applies to any platform.

Symptoms

RPM webservices stuck in Conflict Checking.
When calling RPM webservices (in this case to create clearances), when the price events have conflicts, the price event in RPM_CLEARANCE table gets stuck in Conflict Checking status.

However the response sent to the webservice is the correct one, sending the exact conflict message raised (BUSINESS_ERROR).

Expect to have events in Worksheet status, in case of conflict.


Steps to reproduce:


1. Create Clearance by Webservice>>clearance approved in RPM
2. Create clearance by webservice for the exact same item/loc/date to get in conflict.
-RPM_CLEARANCE table with new record but in Conflict Checking status, even if Webservice response is BUSINESS_ERROR.
3.  Create clearance by webservice raising the retail to a value higher than the regular retail
-RPM_CLEARANCE table with new record but in Conflict Checking status, even if Webservice response is BUSINESS_ERROR.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.