RPM - Price Change Induction REST Responds With HTTP 200 Instead of Error
(Doc ID 2941542.1)
Last updated on APRIL 12, 2023
Applies to:
Oracle Retail Pricing Cloud Service - Version 19.2 and laterInformation in this document applies to any platform.
Symptoms
Price Changes
ACTUAL BEHAVIOR
---------------
When calling the Price Change induction REST service, there are certain situations where the call to the service fails (and no price-change is created in RPM - not even in conflict) but the return code from the HTTP call is 200-OK.
In case of an error in the call, if the price change was not created, the return code should not be 200.
EXPECTED BEHAVIOR
-----------------------
In the JSON returned by the call should be a received error code.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Passing the following JSON to the service:
[
{
"action" : "NEW",
"newGroupBatch" : 1,
"priceChangeGroup" : null,
"priceChangeGroupDesc" : "68892",
"priceChange" : null,
"item" : "100120028",
"diff" : null,
"locationType" : 1,
"location" : 260,
"effectiveDate" : "2022-06-13",
"updatedEffectiveDate" : null,
"changeType" : 2,
"changeValue" : 140,
"sellingUom" : "EA",
"multiUnitImpact" : null,
"multiUnitRetail" : null,
"multiUnits" : null,
"multiUnitSellingUom" : null,
"roundingRule" : null,
"reason" : null,
"status" : 4,
"ignoreConstraints" : null
}
]
2. We get a 200 HTTP response, but the price change actually fails to be created in RPM (this is the JSON returned by the call):
{"statusMsg":"Processed with errors","failPcTable":[{"priceChange":653405,"item":"100120028","diff":null,"locationType":"1","location":260,"effectiveDate":"2022-06-13","errorMsg":"RANGING_ERROR","links":[],"hyperMediaContent":{"linkRDO":[]}}],"links":[],"hyperMediaContent":{"linkRDO":[]}}
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 |