Promo Offers Are Not Listed in the Integration JSON Files
(Doc ID 3046852.1)
Last updated on SEPTEMBER 11, 2024
Applies to:
Oracle Retail Pricing Cloud Service - Version 24.0 to 24.1 [Release 24.0 to 24.1]Information in this document applies to any platform.
Symptoms
If Offer1 is created using the Promo Induction REST API and then Offer2 is created using the same REST API, then the Payload tables get an offerDelete record for Offer1. This causes the integration JSON files to not including Offer1.
Steps to reproduce:
-----------------------------
1. Using the Promo Induction API, create Offer1.
2. Confirm it was successful.
3. Confirm there's an OfferCreate in the payload tables.
4. Using the Promo Induction API, create Offer2.
5. Confirm it was successful (2-NewPromo+NewOffer_Response.json).
6. Confirm there's an OfferCreate in the payload tables (2-Payloads.png) for the new Offer but there's an OfferDelete for Offer1.
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 |