Commerce Attribute and Array Sets
Overview
There are several document attributes sets, for both the Main Document and the Sub-Document.
Main Document Attribute Sets
Attribute sets contain more than one Commerce attribute. There are a number of attribute sets you can include in your documents, including Address Attribute Sets (Additional Address Attribute Sets and Bill To/Ship To Attribute Set), Array Sets (also known as Transaction Arrays), eSignature Sets, Submit Attribute Set, and Version Attribute Set. Each attribute set is made up of a group of individual attributes. The individual attributes can be customized, or hidden from the set. All attribute sets are created together or removed together.
Additional Address Attribute Set
The Additional Address attribute set can be created multiple times on every main document. When you create an additional Address attribute set, the Commerce system automatically generates 13 fields, each of which has editable characteristics.
Name | Type | Description |
---|---|---|
Additional Address First Name | Text | First Name of the contact person for the additional address set. |
Additional Address Last Name | Text | Last Name of the contact person for the additional address set. |
Additional Address Company Name | Text | Company Name of the organization for the additional address set. |
Additional Address Company Name 2 | Text | Secondary Company Name of the organization for the additional address set. |
Additional Address | Text | First Line of the Address of the organization for the additional address set. |
Additional Address 2 | Text | Second Line of the Address of the organization for the additional address set. |
Additional Address City | Text | City of the organization for the additional address set. |
Additional Address State | State | State or Province of the organization for the additional address set. |
Additional Address Zip | Zip | Zip Code of the organization for the additional address set. |
Additional Address Country | Country | Country of the organization for the additional address set. |
Additional Address Phone | Phone | Phone Number for the contact person for the additional address set. |
Additional Address Fax | Phone | Fax Number for the contact person for the additional address set. |
Additional Address Email | Text | Email Address for the contact person for the additional address set. |
Array Set (also known as Transaction Arrays)
Organizations using Oracle CPQ rely heavily on Oracle CPQ Commerce to sell their product offerings to customers and capture the orders. In the quote life cycle, there is a lot of information that needs to be captured at the Transaction and Transaction Line level. Some of this information is repetitive, but dynamically varies from one Transaction to another. This requires customers to maintain a large number of attributes and control their access through rules. Transaction Arrays allow customers to group multiple, scalar attributes using a single array structure to capture repeatable data and reduce administrative overhead. The array attributes can then be instantiated multiple times at runtime without explicitly defining each instance.
For more information, refer to Transaction Arrays.
Bill To/Ship To attribute sets can be created only once on every main document. When you create an Address attribute set, the Commerce system automatically generates 26 fields, each of which has editable characteristics.
Name | Type | Description |
---|---|---|
Billing First Name | Text | First Name of the contact person for the organization to which this order will be billed. |
Billing Last Name | Text | Last Name of the contact person for the organization to which this order will be billed. |
Billing Company Name | Text | Company Name of the organization where this transaction will be billed. |
Billing Company Name 2 | Text | Secondary Company Name of the organization where this transaction will be billed. |
Billing Address | Text | First Line of the Address of the organization where this transaction will be billed. |
Billing Address 2 | Text | Second Line of the Address of the organization where this transaction will be billed. |
Billing City | Text | City of the organization where this transaction will be billed. |
Billing State | State | State or Province of the organization where this transaction will be billed. |
Billing Zip | Zip | Zip Code of the organization where this transaction will be billed. |
Billing Country | Country | Country of the organization where this transaction will be billed. |
Billing Phone | Phone | Phone Number for the contact person for the organization to which this order will be billed. |
Billing Fax | Phone | Fax Number for the contact person for the organization to which this order will be billed. |
Billing Email | Text | Email Address for the contact person for the organization to which this order will be billed. |
Shipping First Name | Text | First Name of the contact person for the organization to which this order will be shipped. |
Shipping Last Name | Text | Last Name of the contact person for the organization to which this order will be shipped. |
Shipping Company Name | Text | Company Name of the organization where this transaction will be shipped. |
Shipping Company Name 2 | Text | Secondary Company Name of the organization where this transaction will be shipped. |
Shipping Address | Text | First Line of the Address of the organization where this transaction will be shipped. |
Shipping Address 2 | Text | Second Line of the Address of the organization where this transaction will be shipped. |
Shipping City | Text | City of the organization where this transaction will be shipped. |
Shipping State | State | State or Province of the organization where this transaction will be shipped. |
Shipping Zip | Zip | Zip Code of the organization where this transaction will be shipped. |
Shipping Country | Country | Country of the organization where this transaction will be shipped. |
Shipping Phone | Phone | Phone Number for the contact person for the organization to which this order will be shipped. |
Shipping Fax | Phone | Fax Number for the contact person for the organization to which this order will be shipped. |
Shipping Email | Text | Email Address for the contact person for the organization to which this order will be shipped. |
Notes:
- Bill To/Ship To Attribute Sets are generated automatically.
- Only one Bill To/Ship To attribute set can be added per main document.
When you create an eSignature set, the Commerce system automatically generates five fields, each of which has editable characteristics.
For eSignature integration information, refer to DocuSign eSignature Integration.
Name | Type | Description |
---|---|---|
eSignature File Attachment | File Attachment | The File Attachment attribute holds the documents to be sent to the eSignature Vendor |
eSignature Recipients | Text Area | The Recipients holds the emails and names of the intended recipients |
eSignature Date Modified | Date | The Date Modified field contains the date of the most recently performed action on this document |
eSignature Envelope ID | Text | The Envelope ID is a hidden field that is sent along with the document to the eSignature Vendor |
eSignature Status | Menu | The Status field contains the current status of this document |
A Price Book attribute set allows you to store Price Book information for all parts in a transaction. Only one Price Book attribute set can be added per main document. A transaction can support only one Price Book. When you create a Price Book attribute set, the Commerce system automatically generates several fields, each of which has editable characteristics.
Name | Type | Description |
---|---|---|
Price Book Name | Text | Price Book Name |
Price Book Description | Text Area | Price Book Description |
Price Book Custom Fields | Composite Attribute | Price Book Custom Field Values |
Price Book Custom Field Text | Composite Attribute | Price Book Custom Field Text |
Partner Price Book Id | Text | Partner Price Book Id |
Notes:
- Price Book attribute sets are generated automatically.
- Only one Price Book attribute set can be added per main document.
When a submit action is created, Oracle CPQ automatically creates a Submit attribute set which contains the following attributes.
For more information refer to Submit Attribute Sets
Name | Type | Description |
---|---|---|
My Approval | Text | This attribute lists all approval currently pending for current logged in user. This is not available as rule input. |
Approval Status | Text Area | This attribute lists all currently pending active approvals for a transaction. |
Approval History | Text Area | This attribute records approval history of a transaction. If a reason is reset, it is erased from the approval history. |
Approval Revision | Integer | This attribute tracks the number of times a quote has been revised |
Remote Approval Process ID | Text | This attribute stores the corresponding process id in the remote approval system |
The Submit attribute set is automatically created when a Submit action is created.
The Version attribute set is created only when Version type action is created. This action is mainly used in Oracle CX Sales integration, to version Quotes. For more information, see the topic Oracle CX Sales Integration.
Name | Type | Description |
---|---|---|
Version Number | Text | This Attribute Lists the Version Number for a document. |
Parent Transaction Id | Text | This Attribute contains the parent transaction id. |
The Version attribute set is automatically created when a Version action is created.
Sub-Document Attribute & Array Sets
Attribute sets contain more than one Commerce attribute. There are a number of attribute sets you can include in your documents, including Address attribute sets, Product Line attribute sets, and so on. Each attribute set is made up of a group of individual attributes. The individual attributes can be customized, or hidden from the set. All attribute sets are created together or removed together.
Array Set (also known as Transaction Arrays)
Organizations using Oracle CPQ rely heavily on Oracle CPQ Commerce to sell their product offerings to customers and capture the orders. In the quote life cycle, there is a lot of information that needs to be captured at the Transaction and Transaction Line level. Some of this information is repetitive, but dynamically varies from one Transaction to another. This requires customers to maintain a large number of attributes and control their access through rules. Transaction Arrays allow customers to group multiple, scalar attributes using a single array structure to capture repeatable data and reduce administrative overhead. The array attributes can then be instantiated multiple times at runtime without explicitly defining each instance.
For more information, refer to Transaction Arrays.
The Available Rate Plan Set array set captures the list of Rate Plans for a given product.
Name |
Variable Name |
Type |
Description |
---|---|---|---|
Available Rate Plan Name |
_availableRatePlanSet_rate_plan_name |
Text |
The name of the Rate Plan |
Available Rate Plan Number |
_availableRatePlanSet_rate_plan_number |
Text |
The number of the Rate Plan |
Available Rate Plan Integration Id |
_availableRatePlanSet_rate_plan_integration_id |
Text |
The Integration ID for the Rate Plan |
The Transaction Line Charge Array Set allows customers to synchronize the pricing charge schema with Commerce to enable multiple charges for transaction line items. The pricing charge schema is defined by standard and extensible custom charge attributes. The Synchronize Charge Array Set action allows administrators to synchronize the Transaction Line Charge Array Set with the pricing charge schema. The Charge Array Set contains the following read-only attributes:
Name | Variable Name | Type | Description |
---|---|---|---|
Calculation Information |
_chargeSet_calculationInfo |
Text Area |
A JSON array of the Price Models used in calculating this charge's price. |
Charge Definition |
_chargeSet_chargeDefinition |
Text |
The display label of the charge definition. |
Charge Definition Code |
_chargeSet_chargeDefinitionCode |
Text |
The code of the charge definition. |
Charge Definition Integration ID |
_chargeSet_chargeDefinitionIntegrationId |
Text |
The charge definition code in the integrated order management system. |
Charge Type |
_chargeSet_chargeType |
Menu |
The classification of a charge associated with the price for a product or service. This attribute differentiates the purpose of charges with the same price type and price period. For example, the sale of a network device may have both a one-time purchase price (with charge type of 'Purchase Price') and a one-time installation price (with charge type of 'Installation Fee'). |
Discount Amount |
_chargeSet_discountAmount |
Currency |
The extended custom discount amount per period for this charge. |
Discount Type |
_chargeSet_discountType |
Menu |
The type of custom discount applied to this charge. Typically this may be an override price, a discount value, or a discount percentage. |
Discount Value |
_chargeSet_discountValue |
Float |
The numeric value for a custom discount associated with the discount type for this charge. For example, if the Discount Type is Override, this value with be the override unit price for this charge. |
Net Amount |
_chargeSet_netAmount |
Currency |
The extended net price or amount per period that will be paid for this charge. |
Net Price |
_chargeSet_netPrice |
Currency |
The unit price net of all discounts for this charge. The Net Price is the unit price that the customer will be invoiced. |
Price Period |
_chargeSet_pricePeriod |
Menu |
The time period, frequency, or recurrence with which the price or charge is levied. |
Price Type |
_chargeSet_priceType |
Menu |
The basis on which a price or charge is levied, whether one time, on a periodic basis or based on usage. |
Rate Card |
_chargeSet_rateCard |
String |
Display label for the Rate Card applied in calculating this charge's price. |
Rate Card in HTML |
_chargeSet_rateCardinHTML |
Text Area |
The HTML-formatted rate card data. |
Rate Card Structure |
_chargeSet_rateCardStructure |
Text Area |
The rate card used to calculate this charge's price. |
Rate Card Variable Name |
_chargeSet_rateCardVariableName |
String |
Variable Name for the Rate Card applied in calculating this charge's price. |
Unit Price |
_chargeSet_unitPrice |
Currency |
The unit price to be paid by the customer for this charge. |
Usage UOM |
_chargeSet_usageUOM |
Menu |
The unit of measure of usage for usage charges, which may differ from the unit of measure used for the parent product. |
Notes:
- To enable multiple charges for transaction line items, refer to Synchronize Charge Array Set.
- If the Transaction Line Charge Array Set doesn’t exist, it will be created when the Synchronize Charge Array Set action is invoked.
- Refer to Pricing Portal > Charge Attributes for more information about pricing charge attributes.
A Config attribute set contains all the configuration attribute details of the current catalog line item. Only one Config attribute set can be added per sub-document. When you create a Config attribute set, the Commerce system automatically generates three composite fields, each of which has editable characteristics.
Name | Variable Name | Type | Description |
---|---|---|---|
Config Attributes |
_config_attr_info |
Composite Attribute | Configurable Attribute is a composite attribute. This attribute is always read only. However Reconfigure action may be used to modify the values. |
Config Attribute Text |
_config_attr_text |
Composite Attribute | Configurable Attribute Text format is similar Configurable Attribute. The only difference is that the values correspond to the display text of the attributes. |
Config Attribute Information |
_config_attr_info |
Composite Attribute | Configurable Attribute Information is populated with variable name, attribute name, data type and menu type information. |
Config Attribute Values |
_config_attr_values |
Text Area |
Stores configurable attribute values from partner on integration in a user-friendly JSON format. Use of default configuration attributes should be limited to ten or fewer attributes to assure performance. Only simple configuration attribute data types are supported. |
Default Configuration Attributes for Import Revenue Lines Integration
The Config Attribute Values attribute allows Oracle CX Sales to provide configuration defaults for CPQ models during the import of Oracle CX Sales revenue lines. This supports the mapping of revenue line product groups to different versions of the same CPQ product model. In addition, revenue lines for configurable products can be imported with preset configuration values. The default values are applied in the Configuration UI when a sales user initially configures an imported model-type transaction line.
Configurable attribute values are stored in a JSON name:value pair format.
- Boolean, Currency, Date, Float, Integer, Text, and Menu attributes with single values are supported.
- HTML attributes and Menu attributes with more than one item (e.g. '
val1~val2
') are not supported.
A sales representative has created an Opportunity for their customer with three revenue lines. The sales representative wants to import those revenue lines into CPQ and populate the default configuration attribute values from Oracle CX Sales. The revenue lines are an "SUV" model-type item, an "Interior" model-type item, and a "Spare Wheel" part item.
-
The following configuration values are provided for the SUV model.
{"vehicle":"Luxury","vColor":"red","addMandatoryReccItemPartAndModel":true, "includedInteriorStylingKit":true}
-
The following default configuration values are provided for the Interior model
{"doorSillGuard":true,"includeSeatCovers":true,"windowSunShadeMesh":4}
A Model attribute set contains all the details of the current catalog line item. Only one Model attribute set can be added per sub-document. When you create a Model attribute set, the Commerce system automatically generates several fields, each of which has editable characteristics.
Name | Type | Description |
---|---|---|
Model Name | Text | Name of the model |
Model Segment Name | Text | Segment to which the model belongs |
Model Segment Variable Name | Text | Segment to which the model belongs |
Is Model Valid | Boolean | Check if model is configured or unconfigured |
Model Product Line Name | Text | Product Line to which the model belongs |
Model Product Line Attributes | Composite Attribute | Product Line Attributes of Product Line to which the model belongs |
Model Base Price | Currency | Base price of the model |
Model Attributes | Composite Attribute | Placeholder for all model attributes |
Model Supplier Company Name | Text | Model supplier company name |
Model BOM | Link to a Dialog Window | Model BOM Link. |
Model Variable Name | Text | Variable name of the model |
Model Product Line Variable Name | Text | Variable name of the product line that the model belongs to. |
Part attributes can be created or removed individually except the Part Number and Part Display Number. Also, any part attribute can be created only once in a document.
Name | Variable Name | Type | Description | Standard Component |
---|---|---|---|---|
Company Associations | _part_company_associations | Text Area | Company Associations | Yes |
Default UOM Code | _part_default_uom | Text | Default unit of measure | Yes |
Direct Buy | _part_direct_buy | Text | Direct Buy | Yes |
Drawing Position | _part_drawing_position | Text | Drawing Position | Yes |
Eligible for Service | _part_serv_req_enabled | Text | Eligible for service | Yes |
Eligible to Sell | _part_sale_enabled | Text | Eligible to sell or order | Yes |
Enable Customer Self-Service | _part_css_enabled | Text | Customer Self-service enabled flag | Yes |
External Key 1 | _part_external_key1 | Text | External system's key | Yes |
External Key 2 | _part_external_key2 | Text | External system's key | Yes |
Number of Price Periods | _part_default_periods | Text | Default number of price periods | Yes |
Part Base Price | _part_base_price | Currency | Price of the part | Yes |
Part Description | _part_desc | Text Area | Description of the part | Yes |
Part Display Number | _part_display_number | Text | Part Display Number | Yes |
Part Extended Description 1 | _part_extended_desc_1 | Link to a Dialog Window | Extended description of the part | Yes |
Part Extended Description 2 | _part_extended_desc_2 | Link to a Dialog Window | Extended description of the part | Yes |
Part Lead Time | _part_lead_time | Text | Lead time | Yes |
Part Number | _part_number | Text | Part Number | Yes |
Part Price Period | _part_default_periodicity | Text | Default Price Periodicity | Yes |
Part Price Type | _part_default_price_type | Text | Default Price Type | Yes |
Part Supplier Company Name | _part_supplier_company_name | Text | Name of the part supplier company | Yes |
Part Units | _part_units | Text | Units of the part | Yes |
Partner Entity Id | _partner_entity_id | Text Area | Partner Entity Id | Yes |
Partner Organization Id | _partner_organization_id | Text Area | Partner Organization Id | Yes |
Sales Product Type | _part_sales_product_type | Text | ProductTypeCode Valid values comes from a lookup. E.g Goods, Included Warranty etc. | Yes |
Service Duration | _part_service_duration | Text | Service Duration | No * |
Service Duration Period | _part_service_duration_period_code | Text | Service Duration Period | No * |
Service Duration Type | _part_service_duration_type_code | Text | Service Duration Type | No * |
Note: * Service Duration attributes are added to sites that are integrated with Oracle CX Sales
Notes:
-
After a part is added to a transaction, Part Attribute Set attribute values, including Part Custom Fields, cannot be modified in the Transaction UI by the user or through (advanced) modify, integrations, or API calls. Part fields can only be modified in the Part Editor. The Attribute Editor - Document View settings do NOT change access for these attributes on the Transaction UI.
-
Part Custom Fields can be used to create part filters or supplement the set of base attributes available for parts.
-
Prior to CPQ 22A, all standard part fields and the 30 part custom fields were part of the part attribute set. Beginning in CPQ 22A, customers can select which standard part fields and part custom fields for the part attribute set. Refer to Manage Part Attributes for more information.
- Part attribute sets are generated automatically.
A Price attribute set allows you to store all pricing related data for a line item. Only one Price Attribute Set can be added per sub-document. Price Attribute Sets, including several attributes are automatically created.
There are several pricing methods that update pricing attribute values, for more information refer to Pricing Overview.
Name | Variable Name | Type | Description |
---|---|---|---|
Applied Agreement Integration ID |
_price_applied_agreement_integrationid |
Text | The integration ID for the applied price agreement |
Applied Agreement Name |
_price_applied_agreement_name |
Text | The name of the applied price agreement. |
Applied Agreement Number |
_price_applied_agreement_number |
Text | The number of the applied price agreement |
Applied Rate Plan |
_price_applied_ratePlan |
Text | The name of the applied rate plan |
Applied Rate Plan Integration ID |
_price_applied_ratePlan_integrationId |
Text | The integration ID for the applied rate plan |
Applied Rate Plan Number |
_price_applied_ratePlan_number |
Text | The number of the applied rate plan |
Calculation Information |
_price_calculation_info |
Text Area | JSON array of aggregated calculation information returned from advanced pricing profiles |
Component Prices |
_price_component_prices |
Composite Attribute | Additional prices based on configuration |
Configurable Price |
_price_configurable_price |
Currency | Original price as per catalog (inclusive of discount and premium) |
Discount % |
_price_discount_percent |
Float |
Discount in percentage This item is not included in the Standard Process Price Attribute Set. |
Discount Comment |
_price_discount_comment |
Read-only text or HTML | Discount description This item is not included in the Standard Process Price Attribute Set. |
Item Price |
_price_item_price_each |
Currency | The starting price. For Parts it will be the base price or price book price. For models it may be the base model price or the pricing rule or attribute value prices. |
List Price |
_price_list_price_each |
Currency | Will usually be the same value as the Item Price, unless a recommended item price applies. |
Net Price |
_price_net_price |
Currency |
Net price is subtotal minus the total discount This item is not included in the Standard Process Price Attribute Set. |
Override Discount |
_price_override_discount |
Menu |
Override original discount This item is not included in the Standard Process Price Attribute Set. |
Override Price |
_price_override_price |
Menu |
Override original list price This item is not included in the Standard Process Price Attribute Set. |
Override Quantity |
_price_override_quantity |
Boolean |
Override original quantity This item is not included in the Standard Process Price Attribute Set. |
Pricing Rule Price |
_pricing_rule_price_each |
Currency | Currently the customer level pricing. (Not applicable for Models) |
Quantity |
_price_quantity |
Integer | Quantity |
Subtotal |
_price_subtotal |
Subtotal |
Subtotal This item is not included in the Standard Process Price Attribute Set. |
Total Discount |
_price_total_discount |
Currency |
Total discount amount This item is not included in the Standard Process Price Attribute Set. |
Unit Price |
_price_unit_price_each |
Currency | Will usually be the same value as the List Price, unless a contract price applies. |
Warnings:
- Unit Price has been changed to List Price. List Price still behaves as it did in previous versions. The variable name remains _price_list_price_each.
- Unit Price is now the final price, prior to quantity and discounting. This will take all previous pricing (including customer-specific pricing) into account.
Notes: The Standard Process attributes (introduced in Oracle CPQ 23B) were rationalized to remove redundant attributes and to streamline and simplify Commerce integrations. The following attributes are not included in the Standard Process sub-document Price Attribute Set:
_price_subtotal
_price_discount_percent
_price_total_discount
_price_net_price
_price_override_price
_price_override_discount
_price_discount_comment
_price_override_quantity
This change only impacts new sites and newly created Standard Processes. These attributes will not be removed from existing Price Attribute Sets.
A Product Line attribute set contains all the details of the product line to which the catalog line item belongs. Only one Product Line attribute set can be added per sub-document. When you create a Product Line attribute set, the Commerce system automatically generates five fields, each of which has editable characteristics.
Name | Type | Description |
---|---|---|
Product Line Name | Text | Name of the product line |
Product Line Segment Name | Text | Name of the segment to which the product line belongs |
Product Line Attributes | Composite Attribute | Placeholder for product line attributes |
Product Line Supplier Company Name | Text | Product line supplier company name |
Product Line Variable Name | Text | Variable name of the product line |
The sub-document Revenue Attributes set contains the following revenue attributes that store aggregate revenue values and other information used for financial analysis and forecasts.
Name | Variable Name | Type | Description |
---|---|---|---|
Revenue Category |
_revenueCategory_l |
Single Select Menu |
This attribute identifies the category of revenue for this line (e.g. renewal versus new business). The menu options are:
Beginning in CPQ 22A administrators can rename the default menu options. They can also add, edit, and delete custom revenue category menu options. |
Revenue ID |
_revenueId_l |
Text | This attribute lists the ID of the Revenue Line Item in the associated opportunity. |
- The Revenue Attributes set is only available for sub-documents.
- Only one Revenue Attribute set can be added per sub-document.
- The Revenue Attributes set Variable Names (
_revenue_category_l)
and (_revenueId_l
) are not editable. -
Revenue Category menu item Variable Names for the Revenue Category attribute are not editable.
A Segment attribute set contains all the details of the segment to which the catalog line item belongs. Only one Segment attribute set can be added per sub-document. When you create a Segment attribute set, the Commerce system automatically generates five fields, each of which has editable characteristics:
Name | Type | Description |
---|---|---|
Segment Name | Text | Name of the segment the item belongs to. |
Segment Attributes | Composite Attribute | |
Segment Supplier Company Name | Text | Segment supplier company name |
A Serial Number attribute set allows you to store serial number information for each part line item in a transaction. Only one Serial Number attribute set can be added per sub-document. When you create a Serial Number attribute set, the Commerce system automatically generates several fields, each of which has editable characteristics.
Name | Type | Description |
---|---|---|
Serial Number | Text | Serial Number |
Serial Number Description | Text Area | Serial Number Description |
Serial Number Custom Fields | Composite Attribute | Serial Number Custom Field Values |
Serial Number Custom Field Text | Composite Attribute | Serial Number Custom Field Text |
Administration
Create a Main Document Attribute Set
-
Navigate to the Attribute List page.
- Click Admin to go to the Admin Home Page.
-
Click Process Definition in the Commerce and Documents section.
The Processes page opens.
-
For the process you are interested in, confirm that Documents is selected in the Navigation drop-down menu, and click List.
The Document List page opens.
-
Confirm that Attributes is selected for the main document Navigation drop-down menu, and click List.
The Attribute List page opens.
-
Click Add at the bottom of the Attribute List page.
-
Enter a Label and Variable Name for the set.
The Variable Name field populates automatically. Variable names can only contain alpha-numeric characters and underscores. The entry can be changed before saving, but after saving the value is read-only.
- Select the desired Attribute Set as an Attribute Type.
-
Click Add.
Notes:
- Click the attribute set to edit individual attributes contained in a set.
- For instructions to create Array Sets (also known as Transaction Arrays), refer to Transaction Arrays.
- Each main document can only contain one instance of the following attribute sets:
- Bill To/Ship To Attribute Set
- Price Book Attribute Set
- The Submit attribute set is automatically created when a Submit action is created.
For more information refer to Submit Attribute Sets - The Version attribute set is automatically created when a Version action is created.
Create a Sub-Document Attribute Set
-
Navigate to the Attribute List page.
- Click Admin to go to the Admin Home Page.
-
Click Process Definition in the Commerce and Documents section.
The Processes page opens.
-
For the process you are interested in, confirm that Documents is selected in the Navigation drop-down menu, and click List.
The Document List page opens.
-
Confirm that Attributes is selected for the sub-document Navigation drop-down menu, and click List.
The Attribute List page opens.
-
Click Add at the bottom of the Attribute List page.
Notes:
- The Label and Variable Name are not used for Config, Model, Part, Price, Product Line, Segment, and Serial Number attribute sets.
- For instructions to create Array Sets (also known as Transaction Arrays), refer to Transaction Arrays.
-
Select the appropriate attribute set from the Attribute Type drop-down.
-
Click Add.
Notes:
- Click the attribute set to edit individual attributes contained in a set.
- For instructions to create Array Sets (also known as Transaction Arrays), refer to Transaction Arrays.
- Each sub-document can only contain one instance of the following attribute sets:
- Config Attribute Set
- Model Attribute Set
- Part Attribute Set
- Price Attribute Set
- Product Line Attribute Set
- Revenue Category Attribute Set
- Segment Attribute Set
- Serial Number Attribute Set
Complete the following steps to synchronize the Transaction Line Charge Array Set with the pricing charge schema, which is comprised of standard and extensible custom charge attributes. If the Transaction Line Charge Array Set doesn’t exist, it will be created when the Synchronize Charge Array Set action is invoked.
- Navigate to the Admin Home Page.
- Click Process Definition in the Commerce and Documents section.
- Select Documents from the applicable process Navigation drop-down menu, and then click List.
- Select Attributes from the Transaction Line Navigation drop-down menu, and then click List.
- Click Synchronize Charge Array Set at the bottom of the Attribute List page.
Notes:
- If the Transaction Line Charge Array Set doesn’t exist, it will be created when the Synchronize Charge Array Set action is invoked.
- Refer to Pricing Portal > Charge Attributes for more information about pricing charge attributes.