Oracle CPQ: Performance Impact Due to Extensive Save Logic

In our Oracle CPQ implementation, the Save action is being used to set multiple attributes at both the header and line item grid (LIG) levels. Over time, this has led to a significant increase in the complexity and volume of logic within the Save Before and Save After formulas, which is now causing noticeable performance degradation during quote save operations.

We’re looking for guidance on:

• Best practices to optimize Save logic in CPQ.
• Oracle’s recommendations for managing attribute updates more efficiently.
• Any alternative approaches to reduce the load during Save.

Has anyone faced similar challenges, and how did you address them?