Naming Conventions are Important in Oracle CPQ Cloud

Oracle CPQ Cloud is a SaaS (Software as a Service) product that allows extension of functionality using built-in tools, JCS - SaaS Extension, and external integrations. With great power comes great responsibility — and the need for consistent naming conventions.

Why Naming Conventions Matter

In Oracle CPQ Cloud, you’ll create hundreds (or thousands) of attributes across different levels of your data model. Without proper naming conventions:

• Developers waste time searching for attributes
• Similar attribute names cause confusion
• BML scripts become hard to read and maintain
• New team members struggle to understand the system
• Integration mappings become error-prone

Recommended Naming Patterns

Use suffixes to indicate the level where an attribute exists.

Configuration Product Family Level

Configuration Product Line Level

Configuration Model Level

Transaction/Quote Level

Transaction/Quote Line Level

Additional Naming Guidelines

Use Descriptive Names

• Good: discountPercentage_tl
• Bad: disc_tl or d1_tl

Indicate Data Type When Helpful

• isApproved_tq — Boolean (is/has prefix)
• approvalDate_tq — Date (Date suffix)
• totalPrice_tl — Number (no specific indicator needed)

Group Related Attributes

• customer_name_tq
• customer_email_tq
• customer_phone_tq

Rules and Actions

Apply similar conventions to BML rules and actions:

• calculateDiscount_cm — Configuration rule
• validateConfiguration_cl — Validation rule
• updateLinePrice_tl — Commerce action

Benefits of Consistent Naming

• Self-documenting code — Attribute purpose is clear from the name
• Faster development — Easy to find and reference attributes
• Reduced errors — Clear distinction between levels
• Better team collaboration — Everyone follows the same standard
• Easier maintenance — Future developers understand the system

Implementation Tips

1. Document your standards — Create a naming convention guide for your project
2. Enforce during code review — Make naming conventions part of review criteria
3. Start early — Retrofitting naming conventions is painful
4. Be consistent — One exception leads to many

Investing time in proper naming conventions upfront will pay dividends throughout the life of your Oracle CPQ Cloud implementation.