FA: SCM: Pricing: Row Limit Error Occurs While Using Pricing Algorithms After 22A Upgrade (Doc ID 2846813.1)

Last updated on OCTOBER 31, 2023

Applies to:

Symptoms

Customers that have extended Pricing Algorithms to use View Objects that are not owned by Pricing might see row limit errors after receiving the 22A update. Pricing Algorithms are extended by customers to use View Objects that are not owned by pricing to cater to specific requirements of their implementation. The View Objects are used in Functions to query specific data that is needed in the context of pricing a document (Example: Sales Order)

Depending on how the View Object is defined by the owning product (TCA, Order Management, CRM etc..) and the usage of the Function in the algorithm logic, customers might start seeing errors in the pricing execution flows, like creating a sales order, saving an order etc. This behavior will most likely be seen in situations where there is a bind variable with no value.

For example, you have a custom function that is querying customer accounts using Customer Id or Party Id. When a new Sales Order is being created through the User Interface, till a customer is selected, Customer Id would be blank. If the extension that was set up is not conditionalized not to execute the function call when the Customer Id value is not set, then a blanket query would be fired to get all accounts.

Cause

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