FAQ: Configuration for Smooth Functioning of Price Event Cache Jobs and ReST Service (Doc ID 2978191.1)

Last updated on OCTOBER 25, 2023

Applies to:

Oracle Retail Pricing Cloud Service - Version 22.1 and later
Information in this document applies to any platform.

Purpose

This article addresses configuration for smooth functioning of Price Event Cache jobs and ReST Service

Questions and Answers

	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

Questions and Answers

On: RPCS/RPM 22.1.401.7 version

Concerning the specifications for the REST services, v1/item/price, v2/item/price, v1/item/promo, and v2/item/promo, the users want to know if these are correct. If not, please share the corrections/additions to be made.
The objective is to have the correct configuration for the above four ReST services so, that the Price Event Cache jobs and the Price Event publication ReST services (v1/item/price, v2/item/price, v1/item/promo, and v2/item/promo) produce the expected outcomes
MERCHAPI_CONFIG table - Only a few columns are populated for v1/v2 REST APIs compared to other REST APIs (say as compared to foundation/item/vat). What updates must be made to this table's records corresponding to v1/v2 REST APIs?

Web Service Configuration Screen of MFCS: Only v2/item/price and v2/item/promo features in this, however upon running creating price events, both v1 and v2 records get loaded for item/price as well as item/promo in the table, RPM_ICL_PRICE_EVENT_PAYLOAD - What impact does this screen have on the functioning of Price Event Cache jobs and Price Event publication REST services

Also, most of the columns for v2/item/price and v2/item/promo are blank, unlike other web services featuring in this screen - What values should be populated in the blank columns for these two web services

MERCHAPI_ASYNC_REQUEST table: v1/item/price and v2/item/price do not feature here despite running the Merch API Data Rebuild Request process - What needs to be done for including v1/item/price and v2/item/price in this table?

Status of v1/item/promo and v2/item/promo is Rejected despite running Merch API Data Rebuild Request process - What needs to be done so, that the status is COMPLETED?

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