Incorrect Scheduled Active Date During Posting Of CreateReplSched Message
(Doc ID 3042443.1)
Last updated on AUGUST 20, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 to 19.3 [Release 19.3]Information in this document applies to any platform.
Symptoms
While calling createReplSched RestServices to post Update to replenshiment attributes, scheduled active date gets posted as incorrectly ( 05/29/2611 ) in repl_attr_update_head table instead of what's in the payload json, 20240801000000
Steps:
1. Using Postman, execute the createReplSched json file as
2. [
{
"links": [
{
"href": "",
"rel": "",
"type": "",
"methodType": ""
},
{
"href": "",
"rel": "",
"type": "",
"methodType": ""
}
],
"attributeNames": [
"",
""
],
"jsonFieldNameMap": {
"utc": ""
},
"schRplDesc": "Modify Repl Test RM SIT1 Date test",
"scheduledActiveDate": "20240801000000",
"replAction": "U",
"replMethodInd": "Y",
"item": "xxxx",
"diff1": "x",
"diff2": "xx",
"diff3": "",
"diff4": "",
"dept": "xx",
"class1": "xx",
"subclass": "xx",
"loc": "xx",
"locType": "X",
"minStock": "9",
"maxStock": "9",
"hyperMediaContent": {}
}
]
3. Send
4. Message successfully processed.
5. Verify table repl_attr_update_head for ACTION 'U', SCHEDULED_ACTIVE_DATE is 05/29/2611
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 |