Manage Transaction

Overview

This topic covers administration of the main document (Transaction) using the Redwood interface pages. Refer to Commerce Documents for administration using the classic interface pages.

Each Commerce process contains one document set. There are two types of Commerce documents: main document (e.g. Transaction) and sub-document (e.g. Transaction Line).

A document set is comprised of a main document with an attached sub-document. Using these document types, you can create flexible Commerce processes.

Example: A process named RFQ can contain a main document and a corresponding sub-document (RFQ sub). Main documents are used for general information pertaining to the Transaction, like customer name or billing and shipping information, while sub-documents are used as product detail pages.

Manage Transaction Page

The Manage Transaction page provides access to transaction settings, attributes, actions, library functions, and rules.

  • To access the transaction document, navigate to:  Admin Home > Quotes > Process > Manage Transaction

Manage Transaction

Item Description

1

Access the Deployment Center

2

Transaction tabs:

  • About: Manage transaction level settings
  • Attributes: Manage transaction level attributes
  • Actions: Manage transaction level actions for the selected transaction
  • Library Functions: Manage library functions
  • Rules: Manage transaction level rules

3

Basic: Manage / view the transaction Name, Variable Name, and Description

4

Layout: If enabled, this section provides access to the JET, Legacy, and Mobile layouts.

For Redwood user side quote interface pages, refer to the Redwood Quote Designer to manage the quote layout.

5

Advanced: Manage the following transaction settings.

  • Opportunity Id Mapping: This field is used to map a CRM opportunity id to a Commerce document.

  • Manage Defaults: View / manage the transaction document Advanced Default.

    • Standard Process Documents are pre-populated with a default function.

    • Refer to Manage a Transaction for more information about Advanced Defaults.
  • Manage Auto Updates: View / manage transaction document Auto Update Before and After Formulas.

    • Standard Process Documents are pre-populated with a default values.

    • Refer to Manage a Transaction for more information about Auto Updates.

Administration

ClosedManage a Transaction

Complete the following steps to manage a transaction.

  1. Navigate to Admin Home > Quotes.
  2. Select the applicable Process.
  3. Select Manage Transaction in the left navigation section.
  4. Manage Basic settings.
    1. If applicable, open the Basic section.
    2. Edit the Name, if necessary.
    3. To copy the transaction variable name, click the Copy Variable Name icon icon.
    4. Edit the Description, if necessary.
  5. If enabled, open the Layout section to access to the JET, Legacy, and Mobile layouts.

    Refer Commerce Layout Editor and Commerce Mobile Layouts for layout information.

    Note: For Redwood user side quote interface pages, refer to the Redwood Quote Designer to manage the quote layout.

  6. Manage Advanced settings.

    1. Open the Advanced section.

    2. Enter Opportunity Id Mapping, if necessary.

      This field is used to map a CRM opportunity id to a Commerce document.

    3. Edit the Advanced Default, if necessary.

      • Standard Process Advanced Default - Standard Process documents are pre-populated with default values.

        • To override a default value, check Override Standard Advanced Default, and then click Save.

        • To quickly return to the standard function, uncheck Override Standard Advanced Default then click Save.
        • To view a function in read-only mode, click on View Function.

      • Disable Advanced Default

        Unselect Enable Advanced Default to disable the Advanced Default.

        -or-

      • Select Enable Advanced Default then click Define Function.

        The BML Editor opens.

        1. Select the applicable System Variable Name, Variable Name for (Main Document), Variable Name for (Sub-Document), and/or Library Function(s) for the selected document.

          If required, click Reselect to select attributes.

        2. Click Next Screen to go the Function Editor page.
        3. Enter the BML function, then click Save and Close.
      • Define Advanced Default Function

    4. Edit the Auto Update - Before Formulas, if necessary.

      This allows functions to run before Formulas when the Commerce page performs an auto update.

      • Standard Process Auto Update Before Formulas - There are no standard Auto Update - Before Formulas in the default Standard Process.

        • To override a default value, check Override Standard Auto Update - Before Formulas, and then click Save.

        • To quickly return to the standard function, uncheck Override Standard Auto Update - Before Formulas then click Save.

      • Disable Auto Update - Before Formulas

        Unselect Enable Auto Update - Before Formulas to disable the Auto Update - Before Formulas.

        -or-

      • Define Auto Update - Before Formulas

        Select Enable Auto Update - Before Formulas then click Define Function.

        The BML Editor opens.

        1. Select the applicable System Variable Name, Variable Name for (Main Document), Variable Name for (Sub-Document), and/or Library Function(s) for the selected document.

          If required, click Reselect to select attributes.

        2. Click Next Screen to go the Function Editor page.
        3. Enter the BML function, then click Save and Close.
    5. Edit the Auto Update - After Formulas, if necessary.

      This allows functions to run before Formulas when the Commerce page performs an auto update.

      • Standard Process Auto Update After Formulas - Standard Process documents are pre-populated with default functions.

        • To override a default value, check Override Standard Auto Update - After Formulas, and then click Save.

        • To quickly return to the standard function, uncheck Override Standard Auto Update - After Formulas then click Save.

      • Disable Auto Update - After Formulas

        Unselect Enable Auto Update - After Formulas to disable the Auto Update - After Formulas.

        -or-

      • Define Auto Update - After Formulas

        Select Enable Auto Update - After Formulas then click Define Function.

        The BML Editor opens.

        1. Select the applicable System Variable Name, Variable Name for (Main Document), Variable Name for (Sub-Document), and/or Library Function(s) for the selected document.

          If required, click Reselect to select attributes.

        2. Click Next Screen to go the Function Editor page.
        3. Enter the BML function, then click Save and Close.
  7. Click Save to apply your changes.


ClosedDisable Quantity Explosion

Oracle CPQ 26A implements quantity explosion for the standard quote process to ensure child quantities adjust proportionally when the parent quantity changes. Quantity explosion is only applied to configured products; kits remain unchanged as they are treated as a single unit.

Complete the following steps to disable quantity explosion.

  1. Navigate to Admin Home > Quotes > Process > Manage Transaction.

  2. Open the Advanced section.

  3. Check Override Standard Auto Update – After Formulas, then click Save.

  4. Click Define Function.

  5. Update the Exploded BOM Quantity option to false.

    put(extraParms, "explodedBOMQuantity", false);

    Note: To re-enable quantity explosion, uncheck Override Standard Auto Update - After Formulas to return to the standard function.

  6. Click Save and Close in the function editor.

  7. Click Save.


Notes

Warning: Users cannot create or add quotes from Configuration to Commerce if mandatory items are missing.

Notes:

  • Sub-documents and main documents have a one-to-one relationship, meaning only one sub-document can be associated with a main document.
  • Main document Advanced Default will run when the transaction is first created. Its purpose is to set main document attribute default values. The purpose is to have one script that sets all of these attribute values at once, instead of pulling each of them separately. This also simplifies maintenance because all the defaults are set in a single script.
  • Sub-document (line item) Advanced Default will run whenever a line item is added to a quote. The purpose of writing this script is to set all of the line item attribute values at once.

Tips and Considerations:

  • Edits are not visible until the process is deployed (or redeployed).
  • Create main documents as the primary documents in a set. Create sub-documents as detail pages that link up with main documents, that is, Line Item page for an RFQ.

Related Topics

Related Topics Link IconSee Also