Injector Batch Is Using a Wrong Sequence For Customer Attribute Clearances
Last updated on JULY 05, 2017
Applies to:Oracle Retail Price Management - Version 14.1.1 and later
Information in this document applies to any platform.
RPM_PRICE_EVENT_INJECTOR_SQL.GENERATE_CLEARANCE() is using RPM_PRICE_CHANGE_CUST_ATTR_SEQ.
We expect RPM_PRICE_EVENT_INJECTOR_SQL.GENERATE_CLEARANCE() to use RPM_CLEARANCE_CUST_ATTR_SEQ.
Steps to Reproduce:
- Create a clearance customer attribute.
- Insert data for clearance in stage table with customer attribute.
- Run injector batch.
- Data is inserted with ID following RPM_PRICE_CHANGE_CUST_ATTR_SEQ in place of RPM_CLEARANCE_CUST_ATTR_SEQ.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms