Control Variable Naming Convention for Commerce Entities

In Oracle CPQ 23D, CPQ adopted Oracle CX Sales variable naming conventions for custom items. When an administrator creates a new custom Commerce item, the "_c" suffix is appended to the variable name. Beginning in Oracle CPQ 24C, customers can submit a service request to disable the "_c" suffix on variable names for custom Commerce entities (Actions, Analytics, Attributes, Data Columns, Integrations, Library Functions, Rules, Steps, etc.). The "_c" suffix is enabled by default for standard and legacy Commerce processes.

Oracle CPQ 24C provides the ability for customers to control variable naming conventions for custom Commerce entities.

Steps to Enable

You don't need to do anything to enable the "_c" suffix variable naming conventions for standard and legacy Commerce processes. The  "_c" suffix is enabled by default when you upgrade to Oracle CPQ 24C or create a new Commerce process.

Customers can submit a Service Request (SR) on My Oracle Support to disable the "_c" suffix on variable names for custom Commerce entities.

Tips And Considerations

• When the "_c" is disabled, the "_c" variable name suffix will not be required for newly created custom Commerce entities.

• Disabling the "_c" variable name suffix for custom Commerce entities will not change existing variable names.

• The "_c" suffix setting will not impact existing variable names when cloning a Commerce process or migrating Commerce items. Target variable names will be the same as the variable names from the source Commerce process.