Commerce Actions

Add from Catalog actions allow the user to add line items to a transaction. Destinations can be set for Add from Catalog type actions. Multiple Add from Catalog type actions can be added to the same document to offer users different catalog destinations within the application.

This action has different options for the main document (Transaction) and sub-document (Transaction Line):

• Main Document: Here the tab contains a simple URL field. The valid value for the URL field is the relative path to any page on the Oracle CPQ application.

  For example: On the main document, you can use an Add from Catalog action as a quick link that always goes back to the same page, either a page in the catalog or a Favorites List page.

• Sub-Document: Here the tab contains a simple URL field as well as an advanced function option. On sub-documents, you can set up advanced destination rules for Add to Catalog type actions. This has the added benefit of enabling you to link the Add from Catalog action to different catalog pages depending on the subsystem components that still need to be added to the document.

  The valid value for the URL field is the relative path to any page on your application.

  The advanced function is usually used to display the action in the line item section of the main document.

  Add from Catalog type actions created for sub-documents should be added to the line item group for the main document only. They should not be added to the sub-document view.

Regardless of where you are mastering your customer data, Oracle CPQ makes it easy to find and retrieve account data during your quoting process by using a collection of main document action types such as Auto Fill, Browse, View, and Select Alternate Address.

When an Account is selected during the quoting process, the Auto Fill action populates the Account attribute and address values to the mapped main document attributes.

Back actions are used to take the user back to the previous page, depending on which document they are on.

• If the user is on the main document, clicking Back will take the user to the transactions / quotes list page.

• If the user is on the sub-document, clicking Back will take the user to the main document.

Regardless of where you are mastering your customer data, Oracle CPQ makes it easy to find and retrieve account data during your quoting process by using a collection of main document action types such as Auto Fill, Browse, View, and Select Alternate Address.

Once created, an Account can be selected during the quoting process using the Browse action.

The Calculate Price action applies any pricing changes made on line items to the price attributes. The sub-document (Transaction Line) Prices Array Set is used to hold the prices and charges information for line items.

This actions allows the user to change the currency of an existing quote. By default, users cannot change the currency of a Transaction after it has been created. However, administrators can allow users to change the currency of Transactions that have been created but that do not contain any line items by adding the Change Currency action to the Commerce layout. Once one or more line items exist on a Transaction, the Change Currency button is hidden and cannot be invoked on the Transaction unless all line items are removed from the Transaction. Like any action, access to the Change Currency action can be restricted by using Steps.

When the Change Currency action is on the layout, the site’s supported currencies will be in a drop-down next to the action, with the current currency selected. Selecting a different currency from the drop-down and then clicking Change Currency will change the Transaction’s currency to the selected currency.

The Copy Line Items action can only be defined for the main document. This action enables users to make one or more copies of one or more line items (configured and non-configured) at a time.

Copy Line Items Order of Operations

Splitting Line Items

Implementing Copy Line Items in an Integrated Process

The Copy to Favorites is a special action to copy selected line items from a transaction to the Favorites List.

The Create Price Agreement type action is used to publish the pricing for a CPQ sales agreement to the CPQ Pricing Portal as a Price Agreement.

The Customer Assets type action is used to display Customer Assets when ABO is enabled in standard mode.

Used to extract the change history for a document. This action requires an XSL format file that controls how and which changes appear.

The Display History action contains a special tab called XSL Views tab. The XSLs displayed on this tab come from the Printer Friendly/History XSL Views section. This action can be associated with one or more XSL views. If multiple XSL views are made available with the action, users can select the form they want to use.

Enables users to access email-friendly document formatting. It is a Modify action and hence has all characteristics of a Modify action, including document views, integration and the modify tab.

The Export Attachment action enables a user to add the proposal (PDF) to the related partner opportunity (only on an integrated application). It is a Modify action and hence has all characteristics of a Modify action including document views, integration, and the modify tab.

The Export Line Items action enables users to download the Transaction Line Items with all the attributes currently accessible to them. The export includes all their viewable information from the Line Item Grid as determined by their user profile settings.

Upon executing the Export Line Items action, users can download the Transaction Line Items with all the attributes currently accessible to them. The export includes all their viewable information from the Line Item Grid as determined by their user profile settings. If a Line Item Grid column is hidden from the end user by a Commerce access rule or a Line Item Grid view filter, that data is exported.

The GenAI Assist type action is used to retrieve the GenAI summary from an integrated Oracle Sales site. CPQ leverages Generative AI (GenAI) to automatically generate comprehensive quote summaries. Users can then choose to use the generated quote summary when communicating with customers or internal stakeholders, as needed.

The Import Line Items action enable users to export line item data to a Microsoft Excel (XLSX) file on the user's local computer. With this file users can run formulas and calculations on the Transaction data quickly and easily.

Upon executing the Import Line Items action, users can import line item data from a modified CPQ-exported Microsoft Excel (XLSX) file. This feature leverages Microsoft Excel with Oracle CPQ Commerce to add new or modify existing transaction line data. End users can perform analysis and approval activities before importing line item modifications into the CPQ Transaction. Independent line items or unconfigured Model line items can be added to the CPQ export XLSX file. The export XLSX file provides necessary identification data to determine modifications to a pre-existing CPQ Line Item.

The Lock action enables users to lock a Transaction for situations when a Transaction owner needs to freeze activity on the Transaction and prevent any further changes. For example, prior to submitting a quote for approval or when finalizing a quote and converting it to an order. When a Transaction is locked, only the locking user can make changes. Other users are only able to view the Transaction in read-only mode.

Refer to Transaction Locking for more details.

Most common type of user-defined action. A Modify action can be entirely customized to suit the FullAccess user's needs.

The Open Doc action displays the Line Details for a specified transaction line.

Enables users to access printer-friendly forms for printing.

It is a Modify action and hence has all characteristics of a Modify action, including document view, integration and the Modify tab.

The Reconfigure action allows the user to edit a configuration after its been added to the transaction. The functionality attached to this action will fire before moving to Configuration.

The Reconfigure Inbound action is called when the user returns to the quote after editing a configuration. The functionality attached to this action won't fire until the user has returned to the transaction.

This action refreshes the current Transaction or Transaction Line with last saved data; the refresh action removes the existing values and replaces with the last saved data.

Regardless of where you are mastering your customer data, Oracle CPQ makes it easy to find and retrieve account data during your quoting process by using a collection of main document action types such as Auto Fill, Browse, View, and Select Alternate Address.

When alternate addresses are used, the Select Address action can be used to choose one of the additional addresses to replace the default address set or to populate an alternate address set on the transaction.

The Submit action set is a series of Modify actions in Commerce that are essentially sub-actions of Submit. The Submit action set is comprised of

• Submit - Submits the transaction for approval. If no approvals are defined or triggered for the transaction, the status will move directly to the approved step.
• Request Approval - This action is performed when submit action is clicked and there is at least one reason to approve.
• Approve - This action is performed when a transaction is approved by the approver.
• Reject - This action is performed when a transaction is rejected by the approver.
• Revise - This action is performed when an approver requests revision of a transaction.

Refer to Submit Action Set for more details.

Unlock is a main document action type that is only available when administrators enable Collaborative Quoting or Transaction Locking for an existing Commerce process. Unlock type actions unlock a Transaction when performed. However, Unlock type actions do not perform any further action on the Transaction, such as modify. Administrators can configure the Commerce process to allow users other than the Transaction owner to unlock a Transaction using an Unlock type action.

Refer to Transaction Locking for more details.

The Version action creates a new version of the subject transaction and displays this new version for editing. This action is mainly used in Oracle Sales integration, to version Quotes.

The following table shows which tabs are available per action type.