11i use and implement quoting ed 2 student guide

11i Use and Implement Quoting Ed 2 Student Guide

Copyright © Oracle Corporation, 2003. All rights reserved.

11i Use and Implement Quoting Ed 2 Table of Contents i

Table of Contents

Quoting Overview............................................................................................................................................1-1 Quoting Overview .........................................................................................................................................1-2 Objectives ......................................................................................................................................................1-3 Overview of Quoting.....................................................................................................................................1-4 Quoting User Interfaces.................................................................................................................................1-5 Key Quoting Capabilities ..............................................................................................................................1-6 Oracle E-Business Suite ................................................................................................................................1-7 Quoting in the E-Business Suite....................................................................................................................1-8 Opportunity to Quote to Order ......................................................................................................................1-9 Quote to Order...............................................................................................................................................1-11

Guided Demonstration - Logging in to Quoting........................................................................................1-12 Guided Demonstration - Opportunity to Quote to Order Flow in the HTML UI ......................................1-13 Guided Demonstration - Opportunity to Quote to Order Flow in the Forms UI .......................................1-16

Summary........................................................................................................................................................1-19 Implementation Overview ..............................................................................................................................2-1

Implementation Overview .............................................................................................................................2-2 Objectives ......................................................................................................................................................2-3 Quoting Dependencies and Integration Points ..............................................................................................2-4 Optional Integration Points............................................................................................................................2-5 Mandatory Implementation Tasks .................................................................................................................2-7 Optional Implementation Tasks.....................................................................................................................2-8 Optional Integrations .....................................................................................................................................2-9 Resources.......................................................................................................................................................2-10 Summary........................................................................................................................................................2-12

Enabling the Cache (HTML UI Only) ...........................................................................................................3-1 Enabling the Cache (HTML UI only)............................................................................................................3-2 Objectives ......................................................................................................................................................3-3 Cache Overview ............................................................................................................................................3-4

Guided Demonstration - Enabling and Setting Up Cache .........................................................................3-7 Summary........................................................................................................................................................3-9

User and Salesperson Setups ..........................................................................................................................4-1 User and Salesperson Setups .........................................................................................................................4-2 Objectives ......................................................................................................................................................4-3 Overview of Setting up Salespeople..............................................................................................................4-4

Guided Demonstration - Setting Up a Salesperson ...................................................................................4-5 Practice - Creating an Employee ...............................................................................................................4-8 Solution – Creating an Employee ..............................................................................................................4-9

Summary........................................................................................................................................................4-12 Setting Profile Options for Quoting ...............................................................................................................5-1

Setting Profile Options for Quoting ..............................................................................................................5-2 Objectives ......................................................................................................................................................5-3 Overview: Setting Profile Options for Quoting Functionality .....................................................................5-4 ATP Profile Options ......................................................................................................................................5-5 Configurator Profile Options.........................................................................................................................5-6 Quote Profile Options....................................................................................................................................5-7 Order Profile Options ....................................................................................................................................5-9 Application Profile Options...........................................................................................................................5-10

Guided Demonstration - Setting Oracle Quoting Profile Options .............................................................5-11 Practice - Setting Oracle Quoting Profile Options.....................................................................................5-12


11i Use and Implement Quoting Ed 2 Table of Contents ii

Solution – Setting Oracle Quoting Profile Options ...................................................................................5-13 Summary........................................................................................................................................................5-14

Setting Up Quote Status and Quote Status Transitions...............................................................................6-1 Setting Up Quote Statuses and Quote Status Transitions ..............................................................................6-2 Objectives ......................................................................................................................................................6-3 Seeded Quote Statuses...................................................................................................................................6-4 Seeded Quote Statuses (cont'd) .....................................................................................................................6-5

Guided Demonstration - Modifying Seeded Quote Status Names ............................................................6-6 Guided Demonstration - Creating a New Quote Status.............................................................................6-7 Practice - Creating a New Quote Status ....................................................................................................6-8 Solution – Creating a New Quote Status ...................................................................................................6-9

Seeded Quote Status Transitions ...................................................................................................................6-10 Seeded Status Transition Restrictions ...........................................................................................................6-12

Guided Demonstration - Creating a New Quote Status Transition............................................................6-14 Practice - Creating a Quote Status Transition............................................................................................6-15 Solution – Creating a Quote Status Transition ..........................................................................................6-16

Related Profile Options .................................................................................................................................6-17 Summary........................................................................................................................................................6-18

Customizing the User Interface......................................................................................................................7-1 Customizing the User Interface .....................................................................................................................7-2 Objectives ......................................................................................................................................................7-3 Customization Overview ...............................................................................................................................7-4 Lines Page Customization (HTML) ..............................................................................................................7-6

Guided Demonstration - Customizing the Lines Page...............................................................................7-8 Overview Page Customization (HTML) .......................................................................................................7-9

Guided Demonstration - Customizing the Overview Page........................................................................7-10 Practice - Customizing the Overview Page ...............................................................................................7-11 Solution – Customizing the Overview Page..............................................................................................7-12

Enabling or Disabling Actions and Buttons (HTML) ...................................................................................7-13 Guided Demonstration - Enabling or Disabling Action Menus and Buttons ............................................7-15

Practice Overview: Customizing the Lines Page (HTML)...........................................................................7-16 Practice - Customizing the Lines Page ......................................................................................................7-17 Solution – Customizing the Lines Page.....................................................................................................7-18

Customizing Forms Using Folder Functionality ...........................................................................................7-20 Guided Demonstration - Customizing Forms............................................................................................7-22

Summary........................................................................................................................................................7-23 Setting Up Manual Pricing and Tax Calculation Requests .........................................................................8-1

Setting Up Manual Pricing and Tax Calculation Requests............................................................................8-2 Objectives ......................................................................................................................................................8-3 Manual Pricing and Tax Calculation Requests Overview.............................................................................8-4 Manual Pricing and Tax Calculation: Options ..............................................................................................8-6 Setting Up Manual Pricing and Tax Calculation Requests: Profile Options .................................................8-8

Guided Demonstration - Enabling Manual Pricing ...................................................................................8-10 Practice - Manually Calculating Pricing and Tax......................................................................................8-11 Solution – Manually Calculating Pricing and Tax.....................................................................................8-12

Summary........................................................................................................................................................8-13 Enabling interMedia Search...........................................................................................................................9-1

Enabling interMedia Search ..........................................................................................................................9-2 Objectives ......................................................................................................................................................9-3 Overview: interMedia Search.......................................................................................................................9-4 interMedia Profile Options ............................................................................................................................9-5 Practice Overview: Enabling interMedia Search..........................................................................................9-6

Guided Demonstration - Enabling interMedia Search...............................................................................9-7 Guided Demonstration - Performing an interMedia Search ......................................................................9-8


11i Use and Implement Quoting Ed 2 Table of Contents iii

Summary........................................................................................................................................................9-10 Setting Up Quote Security ..............................................................................................................................10-1

Setting Up Quote Security.............................................................................................................................10-2 Objectives ......................................................................................................................................................10-3 What is Quote Security?................................................................................................................................10-4 Related Profile Options .................................................................................................................................10-6 Quote Access Security...................................................................................................................................10-7 Quote Availability: Sales Team Access........................................................................................................10-8

Guided Demonstration - Setting Up Sales Team Member Access (Forms UI) .........................................10-10 Practice - Setting Up Sales Team Member Access....................................................................................10-11 Solution – Setting Up Sales Team Member Access ..................................................................................10-12

Quote Availability: Manager Access............................................................................................................10-13 Guided Demonstration - Setting Up Manager Access...............................................................................10-14 Practice - Setting Up Manager Access ......................................................................................................10-16 Solution – Setting Up Manager Access .....................................................................................................10-17

Quote Availability Security: Identifying a Manager's Subordinates ............................................................10-19 Quote Data Security: Specifying View-only or Update Access ....................................................................10-20

Guided Demonstration - Setting the Full Access Flag ..............................................................................10-21 Quote Function Security................................................................................................................................10-22 New Quote Security ......................................................................................................................................10-23 Security-Related Profile Options...................................................................................................................10-24 Summary........................................................................................................................................................10-28

Enabling Account Creation Requirements ...................................................................................................11-1 Enabling Account Creation Requirements ....................................................................................................11-2 Objectives ......................................................................................................................................................11-3 Overview of Account Creation Requirements...............................................................................................11-4 Account Creation Profile Options .................................................................................................................11-5

Guided Demonstration - Setting Account Creation Requirement Profile Options ....................................11-6 Summary........................................................................................................................................................11-8

Setting Up Credit Checks ...............................................................................................................................12-1 Setting Up Credit Checks ..............................................................................................................................12-2 Objectives ......................................................................................................................................................12-3 Credit Check Overview .................................................................................................................................12-4 Internal Credit Check Overview....................................................................................................................12-5 External Credit Check Overview...................................................................................................................12-6 Enabling Credit Checks.................................................................................................................................12-7 Enabling Credit Checks: Credit Check Rules...............................................................................................12-8

Guided Demonstration - Defining Credit Check Rules .............................................................................12-9 Enabling Credit Checks: Profile Options .....................................................................................................12-10

Guided Demonstration - Enabling Credit Checks .....................................................................................12-11 Practice - Enabling and Initiating Credit Checks.......................................................................................12-13 Solution – Enabling and Initiating Credit Checks .....................................................................................12-14

Summary........................................................................................................................................................12-16 Setting Up Web Publishing.............................................................................................................................13-1

Setting Up Web Publishing ...........................................................................................................................13-2 Objectives ......................................................................................................................................................13-3 What is Web Publishing? ..............................................................................................................................13-4 Web Publishing Process Flow - Salesrep ......................................................................................................13-5 Web Publishing Process Flow - Customer ....................................................................................................13-7 Setting Up Web Publishing ...........................................................................................................................13-8 Setting Up Web Publishing: Profile Options................................................................................................13-9 Setting Up Web Publishing: iStore Requirements........................................................................................13-10 B2B User Setup for Web Publishing.............................................................................................................13-11

Guided Demonstration - Creating and Publishing a Quote .......................................................................13-12


11i Use and Implement Quoting Ed 2 Table of Contents iv

Practice - Creating and Publishing a Quote...............................................................................................13-13 Solution – Creating and Publishing Quotes...............................................................................................13-14

Summary........................................................................................................................................................13-16 Setting Up Approvals ......................................................................................................................................14-1

Setting Up Approvals ....................................................................................................................................14-2 Objectives ......................................................................................................................................................14-3 Approvals Overview......................................................................................................................................14-4 Approvals Process Flow................................................................................................................................14-5 Approvals Functionality ................................................................................................................................14-7 Approval Setup Process Flow .......................................................................................................................14-8

Guided Demonstration - Specifying Jobs and Approval Authority...........................................................14-10 Guided Demonstration - Adding Responsibilities for Approvals..............................................................14-11 Practice - Specifying Jobs and Approval Authority ..................................................................................14-12 Solution – Specifying Jobs and Approval Authority.................................................................................14-13

Setting Profile Options for Approvals ...........................................................................................................14-14 Understanding OAM Rules for Approvals....................................................................................................14-15

Guided Demonstration - Creating Rules for Approvals ............................................................................14-17 Practice - Creating Rules for Approvals....................................................................................................14-19 Solution – Creating Rules for Approvals ..................................................................................................14-20

Setting up Quote Status Transitions for Approvals .......................................................................................14-22 Concurrent Programs.....................................................................................................................................14-23 Summary........................................................................................................................................................14-24

Setting Up Sales Supplement Templates .......................................................................................................15-1 Setting Up Sales Supplement Templates .......................................................................................................15-2 Objectives ......................................................................................................................................................15-3 What are Sales Supplements?........................................................................................................................15-4 Sales Supplement Templates .........................................................................................................................15-5 Sales Supplement Template Structure ...........................................................................................................15-6

Guided Demonstration - Setting Up a Sales Supplement Template ..........................................................15-8 Practice - Setting Up a Sales Supplement Template..................................................................................15-10 Solution – Setting Up a Sales Supplement Template ................................................................................15-11


Setting Up Print Quote....................................................................................................................................16-1 Setting Up Print Quote ..................................................................................................................................16-2 Objectives ......................................................................................................................................................16-3 Print Quote Overview....................................................................................................................................16-4 Formats and Layout .......................................................................................................................................16-5 Printed Quote Content ...................................................................................................................................16-6 Executable vs. Non-executable......................................................................................................................16-8 Setting Up Print Quote ..................................................................................................................................16-9 Setting Print Quote Related Profiles..............................................................................................................16-10 Customizing and Personalizing the Print Quote Report ................................................................................16-12

Guided Demonstration - Customizing the Print Quote Report..................................................................16-13 Adding New Print Quote Templates to Quoting Lookups (Quick Codes) ....................................................16-14

Guided Demonstration - Adding a Print Quote Template to the Quoting Lookup....................................16-15 Personalizing Print Quote..............................................................................................................................16-16

Guided Demonstration - Adding a Logo to the Print Quote Report ..........................................................16-17 Summary........................................................................................................................................................16-18

Integrating Quoting and Oracle Sales Online...............................................................................................17-1 Integrating Quoting and Oracle Sales Online................................................................................................17-2 Objectives ......................................................................................................................................................17-3 OSO and Quoting Functionality Overview ...................................................................................................17-4 OSO/Quoting Integration Functional Flow .................................................................................................17-5


11i Use and Implement Quoting Ed 2 Table of Contents v

Quoting interfaces with Telesales and Oracle Sales Online ..........................................................................17-6 OSO and Quoting Integration Interface.........................................................................................................17-7 Integrating Oracle Sales Online and Oracle Quoting (HTML) .....................................................................17-8

Guided Demonstration - Setting Up and Enabling Sales Online Quoting Integration ..............................17-10 Practice - Setting Up a Sales Online and Quoting User ............................................................................17-14 Solution - Creating an Employee...............................................................................................................17-15


Integrating Oracle Quoting and Oracle TeleSales .......................................................................................18-1 Integrating Oracle Quoting and Oracle Telesales..........................................................................................18-2 Objectives ......................................................................................................................................................18-3 OTS and Quoting Integration Functionality Overview ................................................................................18-4 Quoting interfaces with Telesales and Oracle Sales Online ..........................................................................18-5 OTS/Forms Quoting Interface .......................................................................................................................18-6 Integrating Oracle Quoting and Oracle Telesales..........................................................................................18-7

Guided Demonstration - Setting Up and Enabling OTS/Quoting Integration...........................................18-9 Practice - Setting Up an OTS and Quoting User .......................................................................................18-13 Solution - Creating an Employee...............................................................................................................18-14


Integrating Quoting and Oracle Sales Contracts .........................................................................................19-1 Integrating Oracle Quoting and Oracle Sales Contracts................................................................................19-2 Quoting and Contracts Integration Functionality ..........................................................................................19-3 Contracts for Sales Quoting Integration Functionality Overview .................................................................19-4 Contracts and Quoting Functional Flow........................................................................................................19-5 Integrating Oracle Contracts and Oracle Quoting .........................................................................................19-6

Guided Demonstration - Setting Up an Independent Condition................................................................19-8 Related Quoting Profile Options ...................................................................................................................19-9 Summary........................................................................................................................................................19-10

Resources..........................................................................................................................................................20-1 Resources.......................................................................................................................................................20-2


11i Use and Implement Quoting Ed 2 Table of Contents vi


Quoting Overview Chapter 1 - Page 1

Quoting Overview Chapter 1



Quoting Overview

Quoting Overview

Schedule: Timing Topic

60 minutes Lecture/Demonstration 60 minutes Total



Objectives

Objectives

After completing this module, you should be able to do the following:• Describe Quoting user interfaces, their primary

integration points, and functional differences• Describe the Oracle E-Business Suite• Describe Quoting’s role in the Oracle E-Business

Suite• Explain the business flows in which Quoting is

involved• Summarize the key features of Quoting



Overview of Quoting

Overview of Quoting

What is Quoting?Quoting is a dual-UI product that

enables simple, secure creation of customer quotes across all sales

interaction channels.

Overview of Quoting

Oracle Quoting enables simple, secure creation and management of customer quotes across all sales and interaction channels. Organizations can use Oracle Quoting to propose product solutions and perform negotiations, while enforcing consistent business rules throughout the sales cycle. Quoting users can create quotes using modifiable quote templates, add and configure complex products, manually adjust prices, and perform real-time global availability checks. Users can accept product trade-ins and assign sales credits. Quoting integration with Contracts allows users to negotiate a quote with a specific sales contract. Complex customer approval chains are supported and users can publish and print quotes, and eventually convert quotes to orders. Oracle Quoting is available with an HTML and a Forms user interface. Oracle Quoting-HTML is integrated with Sales Online and Oracle Quoting-Forms with Oracle TeleSales.



Quoting User Interfaces


HTML UI

Field Sales Reps

OSO

Yes

Java-Enabled Browser

Forms UI

Telesales Agents

OTS

Yes

• Java-EnabledBrowser

• Forms Client(jInitiator)

Most Common Users

Primary Integration

Can be Implemented “Stand alone”?

UI Requirements


Oracle Quoting provides both an Oracle Forms and an HTML user interface. Although the appearance and navigation of the two interfaces differ significantly, the functionality available is essentially the same. A key difference between the two interfaces is their primary integration points. The Forms UI is designed to work seamlessly with the Oracle TeleSales application. This provides consistent data and a smooth transitions in the opportunity to order business flow using Oracle Forms technology. Quoting’s HTML UI integrates with Oracle Sales Online to provide the same robust quoting functionality and enable the opportunity to order business flow using industry-standard HTML technology.



Key Quoting Capabilities


• Advanced Security• Quote Search Capabilities• Quote from Opportunity• Pricing• Centralized Product

Access• Quote Statuses and

Transitions• Quote Templates

• Quote Approvals• Sales Supplement• Contracts Integration• Web Publishing• Advanced Printing• Sales Credits• Customer Model

Integration• Quote to Order


Regardless of the implementation scenario, Oracle Quoting delivers the key functionality required for sales representatives and managers to provide the customer with cost and product information accurately, consistently, and quickly.



Oracle E-Business Suite


Procurement

Supply Chain

Marketing Sales

Service

OrderManagement

FinancialsHR

Customers,Products, and Everything Else!


The Oracle E-Business Suite automates every aspect of your business—every department and every function—within your company: marketing, sales, support, finance, human resources, consulting, education, engineering, and so on. It automates functions that include procurement, order management, contracting, projects, supply chain, alliances, and many others. Oracle’s goals in engineering this automation were to integrate all corporate data and processes within a single database, to use only standard tools (HTML, Java, XML, and the Oracle database), and to accommodate all essential business processes while eliminating any need for customization. Where the “best of breed” approach attempted to automate processing within departments, the Oracle E-Business Suite automates within and across departments in order to accommodate complete business flows. Among the major flows the suite has been engineered to support are those for campaign to cash, cash to customer, problem to resolution, procurement to payment, and opportunity to quote, to name a few. The suite also offers industry-specific modules and an information architecture that support integration with complementary business systems.



Quoting in the E-Business Suite


OSO/OTS Quoting OM

Opportunities Quotes Orders


Oracle Quoting most commonly fits in the E-Business solution as a “bridge” between CRM sales applications and Order Management. When integrated with sales applications (i.e., Oracle Sales Online or Oracle TeleSales), Quoting uses customer and sales data entered in those applications to create, modify, approve, and publish formal sales quotes. When sales negotiations are complete, Quoting’s integration with Order Management enables the quote to be quickly converted into an order for order processing and fulfillment. Quoting can be implemented to enable a seamless flow of information in the opportunity to order business flow or as the starting point in the quote to order business flow.



Opportunity to Quote to Order

Opportunity to Quote to Order

EnterShipping

Information

EnterPayment

Information

PlaceOrder

EnterBilling

Information

AddRelated

Products

AddServices

CreateQuote

SelectOpportunity

The Opportunity to Quote to Order Business Flow

You begin this business flow in Oracle Sales Online (OSO) or Oracle TeleSales (OTS) with a sales opportunity that is being managed in that application. When the opportunity is ready to be transitioned into a quote, the integration of the E-Business Suite enables seamless access to Quoting functionality while transmitting relevant OSO opportunity data to Quoting. While in Quoting, you can perform a variety of tasks during the quote creation and negotiation process. For example, you can:

• Use Oracle Approvals Management integration to initiate a rule-based approval process • Use Oracle Workflow integration to send notifications and gather responses • Modify pricing via price lists, promotions, price overrides, surcharges, and discounts • Configure items • Publish the quote for customer review and acceptance (either by printing the quote and

faxing or by posting to a Web store. • Add or delete items • Modify quantities • Enter sales supplement information



• View sales credits • Check item availability • Create non-standard Contracts (Oracle Contracts integration required) • Perform credit checks



Quote to Order

Quote to Order

SelectTemplate

EnterShipping

Information

EnterPayment

Information

PlaceOrder

AddRelated

Products

AddServices

CreateQuote

Enter Billing

Information

The Quote to Order Business Flow

Oracle Quoting can also be implemented without sales application integration. In this scenario, Quoting is used by businesses to quickly provide customer quotes and place orders. You begin this business flow in Quoting and end it when the order is submitted to Order Management.



Guided Demonstration - Logging in to Quoting

Responsibility: Customer Support, Vision Enterprises

1. Navigate to the Oracle E-Business Suite HTML Login (JTF login):

http://<host>:<port>/OA_HTML/jtflogin.jsp

2. Log in with the user ID and initial password created in the previous demonstration.

3. Reset the password and record the new password for future use.

4. Click (B) Update. You are now logged into Quoting's HTML UI as the user you created.

5. Click (I) Sign Out.


6. Log in to Oracle Forms using the login for the user you created in the previous demonstration.

7. Select (N) Quoting.

You are now logged into the Quoting forms user interface.



Guided Demonstration - Opportunity to Quote to Order Flow in the HTML UI

1. Navigate to the Oracle E-Business Suite HTML Login (JTF login):

http://<host>:<port>/OA_HTML/jtflogin.jsp

2. Log in as a sales rep with username/password LJONES/WELCOME. Explain that you are logging in to OSO.

3. Click the Opportunity tab.

4. Click the opportunity name BWorld Deluxe Laptop Deal.

5. In the Opportunity Detail page, click Create Quote.

Explain that information from the opportunity is pulled directly into the quote header as shown in the Create Quote from Opportunity page, and that the sales rep can modify it here (except for the customer name).

Explain that the sales rep can change the quote name, account number, contact name, expiration date, primary salesperson, primary sales group, sales channel, source name, order type, agreement, currency, or price list at this point.

6. Click Apply. The quote is created and you see its Overview page.

Explain that you crossed over into the Quoting application. You are automatically taken to the Lines page.

Note that the Lines page displays the products from the opportunity.

Make sure you remember the quote number! There may be multiple quotes with the same name.

Opportunity information that is pulled into the quote includes: − Customer name, contact, address, and account number − Opportunity name − Sales team − Products

7. Select the radio button for the product AS18947 (Sentinel Deluxe Desktop).

Explain that the product must be serviceable if you want to add service products. To verify that a product is serviceable, click on the hyperlinked description to see the product details.

8. Choose Add Services from the Actions menu. Click Go.



9. In the Add Services page, select the optional service WR18533 (Extended Desktop PC Service Program). Keep the defaulted start date. Ensure that the duration is set to 3 and the period to Year.

10. Click Select. The Lines page displays the service under the related product. Select the product AS18947 (Sentinel Deluxe Desktop).

11. In the Actions menu, choose Add Related Products. Click Go.

12. In the search page, choose All from the Relationship menu. Click Go.

13. In the search results, select this product: CM76840 (Lightning Inkjet Printer) -- Cross-sell

14. Click Select. The Lines page shows the added products.

15. Click Shipping and Billing.

Explain that the sales rep may be able to enter various information here depending on the sales rep’s security setup:

− Select or create shipping/billing addresses and contacts for the quote-to customer − Select shipping/billing customers other than the quote-to customer − Create new customers and addresses

16. Click Copy to copy the quote-to customer’s information into the shipping and billing addresses.

17. In the Shipping section, set these values: − Shipping Method = UPS − Requested Delivery Date = two weeks from today − Under Payment, set these values: − Payment Terms = Immediate − Payment Type = Credit Card − PO Number = 2002 − Credit Card Type = Visa − Credit Card Number = 4111 1111 1111 1111 − Cardholder Name = Diane Lyon − Credit Card Expiration = 27-DEC-2004. Click Apply. The Shipping and Billing

page refreshes with the shipping, billing, and payment information you have entered.

18. Click Approvals.

19. Click Initiate Approval.

The Initiate Approval page shows that no approvers are required for the quote, since no approval rules have been triggered (e.g., by discounts or specific products). The sales rep can self-approve the quote.



Note: Do not select the checkbox for “A non-standard contract is required for this quote”

20. Click Approve. The Approvals page opens and shows that the quote has been approved.

21. In the Quoting window, click Overview. Show that the quote status is now “Approved.”

22. Select Print Quote from the Actions menu and click Go.

23. In the Printing page, choose Adobe PDF from the Output Format menu. Make sure the checkbox for “Print in executable mode” is selected.

24. Choose Sales Contract from the Template menu.

25. Click Submit. Adobe Acrobat Reader launches and displays the printer-friendly quote.

26. Review the quote detail layout. The executable quote displays: − Terms and conditions − Signature block − Different title (it is now an in Ordering Document, not a Quotation) − No disclaimer footer

The merchant can define a title and footer for printed quotes, and also add a company logo.

27. Click the Back button on the browser.

28. In the Printing page, click Done. The application returns you to the Overview page.

Explain the quote will be delivered to the customer. Explain that the customer has signed the hard copy of the quote and returned it to the sales rep.

29. In the Overview page, choose Place Order from the Actions menu and click Go. The order is placed. An order number is displayed on the Overview page. Clicking the linked number displays the Order Details page.



Guided Demonstration - Opportunity to Quote to Order Flow in the Forms UI

Responsibility: TeleSales Agent

1. Navigate to the eBusiness Center.

• (N) eBusiness Center

2. Select (B) Find.

3. Change the Find drop-down menu to Organization.

4. Enter Business World and click (B) Search.

5. Select Business World from the search results and click (B) OK.

6. Select (T) Opportunity.

7. Select the opportunity BWorld Deluxe Laptop Deal and click (B) Create Quote.

Explain that information from the opportunity is pulled directly into the quote header as shown in the Create Quote from Opportunity page, and that the sales rep can modify it here (except for the customer name).

Explain that the sales rep can change the quote name, account number, contact name, expiration date, salesperson, sales group, sales channel, source name, order type, agreement, currency, contract template, or price list at this point.

8. Click (B) Create Quote. The quote is created.

Explain that you crossed over into the Quoting application.

Note that the Quote Lines tab displays the products from the opportunity.

Make sure you remember the quote number! There may be multiple quotes with the same name.

Opportunity information that is pulled into the quote includes: − Customer name, contact, address, and account number − Opportunity name − Sales team − Products

9. Navigate to the Quote Lines tab. Select product AS18947 (Sentinel Deluxe Desktop).



Explain that the product must be serviceable if you want to add service products. To verify that a product is serviceable, select the oval button to the left of the Description field in the Details section.

10. Choose Actions > Service Items. Click (B) OK.

Explain that this form shows services that are automatically included with the product as well as optional services that can be purchased.

11. In the Service Items form, select the optional service WR18533 (Extended Desktop PC Service Program) and click Add to Quote.

12. The Quote Lines tab displays the service under the related product. Select Service from the drop-down menu. Verify that the Duration is 3 and the Period is YR.

13. Select Pricing from the drop-down menu. Select the product AS18947 (Sentinel Deluxe Desktop).

14. Select Actions > Add Related Products. Click (B) OK.

15. Select: CM76840 (Lightning Inkjet Printer) -- Cross-sell

16. Click (B) Apply. The related product appears in the Quote Lines tab.

17. Select (T) Quote Header. Select Address from the drop-down menu.

Explain that the sales rep may be able to enter various information here depending on the sales rep’s security setup:

− Select or create shipping/billing addresses and contacts for the quote-to customer − Select shipping/billing customers other than the quote-to customer

18. Click Copy from Quote To to copy the quote-to customer’s information into the shipping and billing addresses.

19. Select Payment, Shipping from the drop-down menu. In the Payment section, set these values:

− Payment Terms = Immediate − Payment Type = Credit Card − PO Number = 2002 − Credit Card Type = Visa − Credit Card Number = 4111 1111 1111 1111 − Cardholder Name = Diane Lyon − Credit Card Expiration = 27-DEC-2004. − In the Shipping section, set these values: − Shipping Method = UPS − Requested Delivery Date = two weeks from today

20. Save your work.



21. Select Actions > Approvals > OK.

22. Select (B) Initiate Approval Process.

The Initiate Approval form shows that no approvers are required for the quote, since no approval rules have been triggered (e.g., by discounts or specific products). The sales rep can self-approve the quote.

Note: Do not select the checkbox for “A non standard contract is required for this quote”

23. Click (B) Approve Quote. The Approvals form shows that the quote has been approved. Close the Approvals form.

24. In the main Quoting form the quote status is now “Approved.”

25. Select Actions > Print Quote > OK.

26. In the Printing page, choose Adobe PDF from the Output Format menu. Make sure the checkbox for “Print in executable mode” is selected.

27. Choose Sales Contract from the Template menu.

28. Click (B) Submit. Adobe Acrobat Reader launches and displays the printer-friendly quote.

29. Review the quote detail layout. The executable quote displays: − Terms and conditions − Signature block − Different title (it is now an in Ordering Document, not a Quotation) − No disclaimer footer

The merchant can define a title and footer for printed quotes, and also add a company logo.

30. Click the Back button on the browser.

31. In the Printing page, click (B) Done.

Explain the quote will be delivered to the customer. Explain that the customer has signed the hard copy of the quote and returned it to the sales rep.

32. Select (B) Place Order. The order is placed. An order confirmation form displays the order number. Explain that you can use this number to track the order in Oracle Order Management.



Summary

Summary

In this lesson, you should have learned how to:• Describe Quoting user interfaces, their primary

integration points, and functional differences• Summarize the key features of Quoting• Describe the Oracle E-Business Suite• Describe Quoting’s role in the Oracle E-Business

Suite• Explain the business flows in which Quoting is

involved


Implementation Overview Chapter 2 - Page 1

Implementation Overview Chapter 2



Implementation Overview

Implementation Overview





Objectives

Objectives

After completing this module, you should be able to do the following:• List the Quoting mandatory dependencies and options

integration points• List the Quoting implementation tasks that are covered in

this course• Distinguish between mandatory and optional tasks• List optional integration points• Identify implementation resources



Quoting Dependencies and Integration Points


Receivables

Order Mgmt

AdvancedPricing

InventoryConfigurator

Gen. Ledger

BOMIncentive

Compensation

Contracts

Approvals Management

Workflow

Install Base

Reports

Oracle Quoting


Required Oracle Quoting requires that the following applications be installed and implemented:

• Oracle Receivables — Provides tax information and customer account information. • Oracle Advanced Pricing — Allows set up of price lists, discounts, adjustments, and

promotions. • Oracle Bill of Materials — Contains information about the components associated with a

product. • Oracle General Ledger — Enables set up of ledgers and books, and stores exchange rates. • Oracle Inventory — Provides Availability to Promise (ATP) and reservation functions, and

all product information from Inventory. • Oracle Order Management — Allows creation of orders from quotes.



Optional Integration Points


• Oracle Approvals Management

• Oracle Configurator• Oracle Contracts for Sales• Oracle Install Base• Oracle Reports Developer

6i

• Oracle Reports Server • Oracle Sales Online• Oracle Service Contracts• Oracle TeleSales• Oracle Workflow• Oracle iStore


The following Oracle applications and modules provide additional functionality but are not required for Oracle Quoting to function:

• Oracle Approvals Management — Allows users to create an approval chain. • Oracle Configurator — Configures model items. • Oracle Contracts for Sales — Enables users to include standard and non-default contracts

with quotes. • Oracle Install Base — Provides a list of all customer’s products and installation details. • Oracle Reports Developer 6i — Centralizes report processing and manages reporting. • Oracle Reports Server — Enables development of print quote. Oracle Reports Server must

be configured for quote printing. • Oracle Sales Online — Allows sales representatives to create quotes in a campaign-to-

order work flow from the HTML UI. • Oracle Service Contracts — Provides contract details for service items. • Oracle TeleSales — Allows sales representatives to create quotes in a campaign-to-order

workflow from the Forms UI.



• Oracle Workflow — Provides notifications related to Approvals and Contracts integration and Web Publishing.

• Oracle iStore — Enables quotes to be published to a Web storefront for customer review and order submission.



Mandatory Implementation Tasks

Mandatory Implementation TasksNot covered in this course Covered in this course

Install software

1Verify

dependency setup

2Set up quote

statuses

3

Set profile options

4

Set up sales representatives

6

Enable cache (HTML UI only)

5

Mandatory Implementation Tasks

1. Before proceeding with the implementation of Oracle Quoting and its dependencies, you must verify that you have installed Oracle Applications correctly. See Installing Oracle Applications for more information. 2. Refer to the specific product documentation to ensure that all dependencies are installed, implemented, and set up correctly. These documents are available on MetaLink. Refer to the Oracle CRM Application Foundation Implementation Verification Checklists as well. 3-6. Separate modules for each of these tasks are provided in this course. See the relevant module for more information.



Optional Implementation Tasks

Optional Implementation Tasks

• Setting up security• Setting up approvals• Setting up web publishing• Setting up sales supplements• Setting up print quote• Setting up contracts

• Enabling credit checks• Customizing the HTML UI• Setting up manual pricing

and tax calculations• Enabling interMedia search• Setting up account creation

requirements for quotes

The following tasks are optional, and should be implemented based on your business requirements. A module for each task is provided in this course.



Optional Integrations


The following application integrations can be set up to add functionality to Quoting and complete business flows. • Oracle Sales Online (HTML UI only)• Oracle TeleSales (Forms UI only)• Oracle Sales Contracts• Oracle Approvals Management


Modules discussing the integration benefits, requirements, and setup of these optional integrations are provided in this course.



Resources

Resources

• Technical Documentation• AppsNet• Oracle Support Services• Oracle MetaLink

Resources

Technical Documentation The following documents are relevant to Quoting:

• Oracle Quoting User Guide • Oracle Quoting Implementation Guide • Oracle Sales Online User Guide • Oracle Sales Online Implementation Guide • Oracle Applications System Administrator’s Guide, Release 11i • Implementing Oracle CRM: ERP Functional Checklist, Release 11i • Oracle Order Management User Guide. • Oracle Inventory User Guide • Order Management Suite Implementation Manual.

Portable Document Format (PDF) versions of these documents can be found on the Oracle Applications 11i Documentation CD or downloaded from Oracle MetaLink. AppsNet



Oracle AppsNet is a key information portal for the E-Business Suite. Presentations, documentation, e-Seminars, chat, articles, demonstrations, and other application related information can be found at http://www.oracle.com/appsnet/index.htm. Oracle Support Services Contact Oracle Support services for self-service support requests, troubleshooting tips, and technical support issues. Oracle MetaLink Go to Oracle MetaLink for the latest information, downloads, and eTRM access.



Summary

Summary

In this module, you should have learned how to:• Identify Quoting’s mandatory dependencies and optional

integration points• List the Quoting implementation tasks that are covered

in this course• Distinguish between mandatory and optional tasks• List optional integrations• Identify implementation resources


Enabling the Cache (HTML UI Only) Chapter 3 - Page 1

Enabling the Cache (HTML UI Only) Chapter 3



Enabling the Cache (HTML UI only)

Enabling the Cache (HTML UI only)





Objectives

Objectives

After completing this module, you should be able to do the following:• Describe why cache must be enabled for Quoting’s

HTML UI• Explain how cache is enabled for Quoting• Explain the concept of cache policies and filters



Cache Overview

Cache Overview

• The Performance Framework in Oracle CRM Technology Foundation optimizes application performance with a Java objects cache that is based in the middle tier.

• Use of Oracle Quoting - HTML requires that you enable the cache. APIs will not work properly if you do not.

Cache Overview

Note: This task is NOT required if you are implementing the Forms UI only. For detailed information on cache management see Oracle CRM Technology Foundation Concepts and Procedures. Seeded Caches

• QOT_ATP_STATUS_CACHE -- Stores information about ATP statuses, including status code and meaning.

• QOT_BOM_ITEM_TYPE_CACHE -- Stores information about BOM item styles, including BOM item type code and meaning.

• QOT_CREDIT_CARD_TYPE_CACHE -- Stores information about credit card types, including credit card type and name.

• QOT_CURRENCY_CACHE -- Stores information about currencies, including currency code, meaning, symbol, and price list Ids

• QOT_IB_REL_TYPE_CACHE -- Stores information about Install Base relationship types, including relationship type code and meaning



• QOT_ITEM_CTG_LIST_CACHE -- Stores information about the list of item categories available for a particular category set.

• QOT_ITEM_TYPE_CACHE -- Stores information about item types, including item type code and meaning.

• QOT_LINE_TYPE_LIST_CACHE -- Stores information regarding the list of line types available, based on operating unit, order type, and line category

• QOT_LOOKUP_VALUES_CACHE -- Stores information about lookup types and the corresponding lookup values

• QOT_MKTG_SRC_TYPE_CACHE -- Stores information about marketing source types, including source type code and name.

• QOT_MODIFIER_LEVEL_CACHE -- Stores information about price modifier levels, including code and name.

• QOT_MODIFIER_LINE_TYPE_CACHE -- Stores information about price modifier line types, including code name and price.

• QOT_OU_CACHE -- Stores information about operating units, including operating unit ID and default territory code

• QOT_PAYMENT_METHOD_CACHE -- Stores information about payment methods, including payment method code and meaning.

• QOT_PAYMENT_TERM_CACHE -- Stores information about payment terms, including payment term ID and name.

• QOT_PQUOTE_OUTPUT_FMT_CACHE -- Stores information about print quote formats, including code and name.

• QOT_PQUOTE_TEMPLATE_CACHE -- Stores information about print quote templates, including code and name.

• QOT_PRICE_LIST_CACHE -- Stores information about price lists, including price list ID, name, and currency code.

• QOT_QUOTE_STATUS_CACHE -- Stores information about quote statuses. • QOT_RELATIONSHIP_TYPE_CACHE -- Stores information about relationship types,

including relationship type code and meaning. • QOT_RESOURCE_CTG_CACHE -- Stores information about resource categories,

including resource category code and meaning. • QOT_RESOURCE_GROUP_CACHE -- Stores information about resource groups,

including resource group ID and name. • QOT_SALESUPP_COMP_CACHE -- Stores information about sales supplement

components, including component ID, name, instruction, description, component type, response type, and mandatory flag.

• QOT_SALESUPP_RESP_CACHE -- Stores information about sales supplement responses, including response ID and name.

• QOT_SALESUPP_SECT_CACHE -- Stores information about sales supplement sections, including section ID and name.

• QOT_SALESUPP_TEMPL_CACHE -- Stores information about sales supplement templates, including template ID and name.



• QOT_SALES_CHANNEL_CACHE -- Stores information about sales channels, including sales channel code and meaning

• QOT_SALES_CREDIT_TYPE_CACHE -- Stores information about sales credit types, including sales credit type ID, name, and quota flag.

• QOT_SHIPPING_METHOD_CACHE -- Stores information about shipping methods, including shipping method code and name.

• QOT_TAX_CACHE -- Stores tax information, including tax code and printed tax meaning. • QOT_TAX_EXEMPT_REASON_CACHE -- Stores information about tax exempt

reasons, including tax exempt reason code and meaning. • QOT_TAX_EXEMPT_STATUS_CACHE -- Stores information about tax exempt statuses,

including tax exempt status code and meaning. • QOT_TERRITORY_CACHE -- Stores information about territories, including territory

code and name. • QOT_TRANSACTION_TYPE_CACHE -- Stores information about transaction types,

including transaction type ID, name, code, and price list ID. • QOT_TRXN_LINE_CTG_CACHE -- Stores information about transaction line categories,

including line category code and meaning. • QOT_UOM_CACHE -- Stores information about units of measure, including UOM code

and name. • QOT_YES_NO_CACHE -- Stores information about yes/no lookups, including code and

meaning.



Guided Demonstration - Enabling and Setting Up Cache

Responsibility: System Administrator

1. Launch the JTF login page by clicking (H) CRM HTML Login.

2. Log in as sysadmin/sysadmin.

3. Navigate to the Host Detail page.

• Deployment > Configuration > Hosts.

4. Select (B) Create. Explain that the Host Detail page is where caching is enabled for Quoting.

Host Name: This is the name of the middle-tier machine on which the application server is running and also where objects are cached for applications.

Ports: This is where you specify port numbers for your Apache Web server(s).

Applications: All applications installed in the database are available to select in the Available Applications list. You must explicitly add Oracle Quoting to the list of Deployed Applications using this UI.

Selecting the Create button sets up the host and Quoting application for further cache management tasks.

Creating a Cache Policy and Filter

5. Select (T) Performance.

6. Select (H) Applications. A list of hosts, applications, policies, and filters displays. You can use the View pull-down list to restrict your view to a particular host.

7. Select the Application name hyperlink. A list of cache components displays. This is a granular view of what java objects are being (or not being) cached for a specific application.

8. Select the Policy pull-down menu. Here you will specify the type of caching you want for the particular object(s):

− Cache Only: only java objects (classes) are cached − Cache and Priming: java objects and images − Disabled: Cache is disabled for the application or component specified. − Custom: Use a custom cache policy the user has created.

9. Select (H) Filters. This is where you can view existing filters or create a new one.

10. Select an existing filter name. The filter will specify what responsibilities and languages apply to the cache policy. Filters help performance by restricting a middle-tier cache policy to only those responsibilities and/or languages that are specified.



11. Select (I) Sign Out.



Summary

Summary

In this module, you should have learned how to:• Describe why cache must be enabled for Quoting’s

HTML UI• Explain how cache is enabled for Quoting• Explain the concept of cache policies and filters


User and Salesperson Setups Chapter 4 - Page 1

User and Salesperson Setups Chapter 4



User and Salesperson Setups

User and Salesperson Setups


45 minutes Lecture/Demonstration 30 minutes Lab 75 minutes Total



Objectives

Objectives

After completing this module, you should be able to do the following:• Enter a new employee in the system• Create a user ID and initial password• Assign seeded Quoting responsibilities to a user• Import a CRM resource• Specify a sales credit type• Log in to both Quoting UIs

Note

This module uses seeded users and responsibilities and is based on a Vision demonstration environment. It assumes that all mandatory E-Business Suite dependencies for Quoting have been previously installed and implemented.



Overview of Setting up Salespeople

Overview of Setting up Salespeople

You must set up users as salespeople in order for them to be able to access and use Quoting. To set up a salesperson, you must:

1. Create an employee in Human Resources2. Create a User ID with responsibilities and assign

the user to that User ID3. Import the resource in CRM Resource Manager

Overview of Setting Up Salespeople

1. You create employees in Human Resources 2. You must assign the appropriate responsibilities to the User ID 3. After importing the resource, you must assign the resource a salesperson number and sales credit type

- A resource is a basic unit used by the resource manager. It can be a person, place or thing.



Guided Demonstration - Setting Up a Salesperson

Responsibility: HRMS Management

1. Log in to Oracle Forms using login ebusiness/welcome.

2. Select the HRMS Management responsibility.

Explain that you must enter a person in Human Resources as an employee before making them a valid salesperson.

3. Navigate to the People form.

• Select (N) HRMS Manager > People > Enter and Maintain.

4. In the Find Person form, select (B) New.

5. Enter a fictional employee’s first and last names in the respective fields.

6. Select the appropriate gender from the pull-down menu.

7. Place your cursor in the Action field. Select Create Employment from the Action LOV.

8. Select Employee as the Person Type.

9. In the Identification block, enter a social security number for the employee (use the format: XXX-XX-XXXX).

10. Enter a date of birth in the Payroll tab (use the format DD-MMM-YYYY).

11. Select (I) Save.

12. Record the employee number.

13. Close the People form.

14. Switch responsibilities (M) File > Switch Responsibility to System Administrator.

Explain that user IDs and responsibilities are created and maintained by the system administrator. Explain that you must create a user ID and assign it responsibilities in order for a user to log in to the system. Explain that the responsibilities you are going to assign your user ID are seeded with the Oracle Quoting application.

15. Select (N) Security > User > Define.

16. Enter a user name for the employee you created. Record the user name.

17. Enter an initial login password for the user. Tab out and enter it again.



Explain that you must enter the password twice for validation purposes.

18. Use the Person LOV to search for the employee name.

19. Select (T) Responsibilities. Use the Responsibility LOV to assign the following responsibilities to your user:

Oracle HTML Quoting Sales Agent (Explain that this responsibility allows the user to log in to the HTML UI.)

Quoting Sales Manager (Explain that this responsibility allows the user to log in to the Forms UI.)


21. Close the Users form.

22. Switch responsibilities (M) File > Switch Responsibility to CRM Resource Manager, Vision Enterprises.

Explain that for a salesperson to be valid, they must be set up as a resource. Explain that since you entered the person as an employee in HR, you can now import that person in to the Resource Manager.

23. Select (N) Maintain Resources > Import Resources.

24. Select Employee from the Resource Category pull-down menu.

25. In the Number field, enter the employee number of the employee you created in HR and select (B) Search.

Remind them that the employee number was generated in HR when you created the employee.

26. In the Search Results region, select the checkbox next to the employee’s name and then select (B) Create Resource.

27. In the Default Values form, select (B) OK.

28. Select the checkbox next to the employee’s resource record and select (B) Save Resource.

Explain that once a person is a valid resource they can perform many functions within Quoting, but they must be a valid salesrep to use the product to the fullest extent.

29. When the transaction number appears, select (B) Details.

30. In the Salesperson number field, enter a unique identifying number for the salesperson.

Explain that this number is what makes the person a valid salesperson.



31. Select (T) Receivables.

32. In the Sales Credit Type field, use the LOV to enter Quota Sales Credit.


34. Close all forms and return the Navigator.

35. Select (M) File > Exit Oracle Applications.

Verify that you can log in to Quoting.



Practice - Creating an Employee

Overview

This practice demonstrates how to create an employee in Human Resources. This practice enters the minimal data required to create an employee. Additional data may be required depending on employee job or role and application integrations.

Assumptions

• Oracle Technology stack is implemented

• Human Resources, Vision Enterprises

• System Administrator

• CRM Resource Manager, Vision Enterprises

• You must have access to an Oracle Application Vision database or comparable training or test instance at your site on which to complete this practice.

Tasks

Create an Employee

Log in to Oracle Forms using the Human Resources, Vision Enterprises responsibility to create employees.

Create a User ID and Assign Quoting Responsibilities for an Employee

Use the System Administrator responsibility to create a User ID for your employee and assign responsibilities to the User ID.

Import Resource

Use the CRM Resource Manager, Vision Enterprises responsibility to set up your user as a resource in the database, assigns a salesperson number, and sets the sales credit type for Quoting.



Solution – Creating an Employee

Creating an Employee

Responsibility = HRMS Management

1. Log in to Oracle Forms using login ebusiness/welcome. − http://<host>:port/ − Select Apps Logon Links > VIS Logon through the Forms cartridge − Log in with ebusiness/welcome


3. Navigate to the Find Person form.

• (N) HRMS Manager > People > Enter and Maintain.


5. Enter a fictional employee’s first and last names in the respective fields. Record the name.





10. In the Personal tab, enter a birth date for the employee (use the format: DD-MMM-YYYY).




Create a User ID and Assign Quoting Responsibilities

Responsibility = System Administrator

14. Select (M) File > Switch Responsibility.

15. Select the System Administrator responsibility.




17. Enter a user name in the field provided for the employee you created in the previous task. Record the name for later use.

18. Enter an initial login password for the user. Tab out of the field and enter the password again to validate it. Record the password for later use.

19. Use the Person LOV to search for the employee name you created in the previous task.

20. Select (T) Responsibilities. Place your cursor in the Responsibility field and use the LOV to assign the following seeded responsibilities to this user ID:

− Oracle HTML Quoting Sales Agent − Quoting Sales Manager



Import Resources

Responsibility = CRM Resource Manager, Vision Enterprises


24. Select the CRM Resource Manager, Vision Enterprises responsibility.



27. Enter the employee number of the employee you previously created and select (B) Search.



30. Select the checkbox next to the employee’s resource record and then select (B) Save Resource.

31. When the Transaction number appears, select (B) Details.









38. Verify that you can log in to Quoting.



Summary

Summary

In this module, you should have learned how to:• Create an employee• Create a user ID and initial password• Assign seeded Quoting responsibilities to a user• Import a CRM resource• Specify a sales credit type• Log in to both Quoting UIs


Setting Profile Options for Quoting Chapter 5 - Page 1

Setting Profile Options for Quoting Chapter 5



Setting Profile Options for Quoting

Setting Profile Options for Quoting





Objectives

Objectives

After completing this module, you should be able to do the following:• Identify profile options for basic Quoting

functionality• Identify mandatory profile options• Identify default values• Identify the user interface(s) that listed profile

options affect• Identify the application level at which the listed

profile options can be set



Overview: Setting Profile Options for Quoting Functionality

Overview: Setting Profile Options for Quoting

Functionality

This module covers profile options settings for basic, standalone Oracle Quoting functionality. Profile options for enhanced functionality (e.g., Security, Approvals, Print, Publish, etc.) are listed within those respective modules.

Overview: Setting Profile Options for Quoting Functionality

Profile options listed with an asterisk (*) are mandatory. See Notes sections below slides for additional details.



ATP Profile Options

ATP Profile Options

ATP (Availability to Promise) profile options determine if sourcing rules are used to derive the relevant inventory orgs for ATP and identify the warehouse against which ATP checks are performed.

ATP Profile Options

Profile Option Default Value UI Level(s) ASO: ATP Default Customer ID* <none> Both S, A, R ASO: ATP Default Ship To Site ID* <none> Both S, A, R ASO: ATP Use Sourcing Rule No Both S, A, R ASO: Default Ship From Org <none> Both All ATP (Availability to Promise) is the current, on-hand, uncommitted stock, outstanding receipts and planned production. In Oracle Inventory, you define the types of supply and demand that should be included in your ATP calculation. Both ASO: ATP Default Customer ID and ASO: Default Ship To Site are mandatory if ASO: ATP Use Sourcing Rule is set to Yes.



Configurator Profile Options


Configurator profile options affect your ability to configure model products.


Profile Option Default Value UI Level(s) ASO: Allow Quantity Updates for Top Level Model Item Yes Both S, A ASO: Allow Quantity Updates for Component Item Yes Both S, A ASO: Configurator URL* N/A Forms All ASO: Configurator URL supplies the URL for the Configurator window, while ASO: Allow Quantity Updates for Top Level Model Item and ASO: Allow Quantity Updates for Component Item determine if you can update quantities within configurations. ASO: Configurator URL is mandatory if you are using Oracle Configurator.



Quote Profile Options


Quote profile options affect the actual quotes you create in Quoting. They control quote numbering, expiration dates, default information, and more.


Profile Option Default Value UI Level(s) ASO: Automatic Numbering* Yes Forms S, A, R ASO: Category Set <none> Both A ASO: Default Currency Code USD Forms All ASO: Default Customer Type Organization HTML S, A ASO: Default Expiration GL Calendar* <none> Both S ASO: Default Expiration GL Period Type* <none> Both S ASO: Default Ordered Quantity in OC UI 1 Both All ASO: Default Quote Status* Draft Both S, A ASO: Default Sales Channel <none> Both All ASO: Discounting Privilege None Both All ASO: Enable ASO Debug <none> Both U ASO: Enable Manual Warehouse Selection <none> Both All ASO: GSA Pricing <none> Both S, A



ASO: Max Number of Results 100 Forms S, A ASO: Quote Duration No Forms All ASO: Require Minus Sign For Manual Discount No HTML S ASO: Require Service Reference on Add to Quote Yes Forms S QP: Verify GSA Violations* No Both S JTF_PROFILE_DEFAULT_CURRENCY* <none> HTML All JTF_PROFILE_DEFAULT_NUM_ROWS* <none> HTML All

• ASO: Default Expiration GL Calendar is mandatory if ASO: Quote Duration is not being used. A default quote expiration must be set using one of the profiles listed to use copy quote functionality.

• ASO: Default Expiration GL Period Type is mandatory if ASO: Quote Duration is not being used.

• QP: Verify GSA Violations is mandatory if ASO: GSA Pricing is set to Error or Warning.



Order Profile Options


Order profile options affect the orders placed from Quoting.


Profile Option Default Value UI Level(s) ASO: Default Order State Booked Both All ASO: Default Order Type* <none> Both All ASO: Default Return Reason* <none> Both All ASO: OM Defaulting No Both S, A ASO: Order Feedback Queue Retention Time <none> Forms S, A ASO: Quote Conversion Type* <none> Both All ASO: Reservation Level Manual Both All

• ASO: Default Return Reason is mandatory if the Return line type is used.



Application Profile Options


Application profile options affect the performance of the Quoting application.


Profile Option Default Value UI Level(s) ASO: Enable Debug <none> Both U ASO: Manage Quote Templates No HTML All JTF_PROFILE_DEFAULT_RESPONSIBILITY* <none> HTML All JTF_PROFILE_DEFAULT_APPLICATION* <none> HTML All MO: Operating Unit* <none> Both S, R



Guided Demonstration - Setting Oracle Quoting Profile Options


1. Log in to Oracle Forms with the system administrator responsibility.

Explain that the system administrator is the only one who can change profile options at all levels. Users can change profile options that are editable at the User level.

2. Navigate to the Find System Profile Values form.

• (N) Profile > System.

3. Select the level(s) at which you want to set the profile option. The available levels are:

Site

Explain that setting a profile at the Site level is the most general setting. Also explain, that many profile options within Oracle Quoting can only be set at the site level, and therefore are controlled by the system administrator.

Application — If you select this level, choose Oracle Quoting (for HTML UI) or Oracle Order Capture (for the Forms UI) from the Application LOV.

Responsibility — If you select this level, choose the responsibility from the Responsibility LOV for which you want to set the profile option.

User — If you select this level, choose the user from the User LOV for whom you want to set the profile option. Users will be able to log into Quoting and change the value of these profile options.

Explain that User-level profile options can also be set by the user by logging in to Forms and selecting Personal Profile.

4. In the Profile field, enter the profile name, such as ASO: Update Customer, or a wildcard search criterion such as ASO%.

5. Select (B) Find.

The System Profile Values form opens with the results of your search.

6. Verify or set the profile option(s) at the levels that you selected.

7. Save your work.



Practice - Setting Oracle Quoting Profile Options

Overview

This practice teaches users how to set Quoting-specific profile options at various levels.

Assumptions




Tasks

Setting Quoting Profile Options

Log in to Oracle Forms as the System Administrator, to set Quoting profile options.



Solution – Setting Oracle Quoting Profile Options

Setting Quoting Profile Options


1. Log in to Oracle Forms with the system administrator responsibility.


• (N) Profile > System.

3. Select the User checkbox and enter the user name you created.

4. In the Profile field, enter ASO%Default Order Type.

5. Select (B) Find.

The System Profile Values form opens with the results of your search.

6. Change the value of this profile in the User column. Do not change the Site value.

7. Save your work.

8. Close this form and log out of Forms. Log back in as your new user.

9. Navigate to the Quoting form by selecting CRM HTML Login.

10. Select Create Quote.

You will notice that the default Order Type on the Create Quote page, is the value you specified in the profile option ASO: Default Order Type.



Summary

Summary

In this module, you should have learned how to:• Identify profile options for basic Oracle Quoting -

HTML functionality• Identify which profile options are mandatory• Identify default values• Identify the user interface(s) that listed profile

options effect• Identify the application level at which the listed

profile options can be set


Setting Up Quote Status and Quote Status Transitions Chapter 6 - Page 1

Setting Up Quote Status and Quote Status Transitions Chapter 6



Setting Up Quote Statuses and Quote Status Transitions

Setting Up Quote Statuses and Quote Status Transitions





Objectives

Objectives

After completing this module, you should be able to do the following:• Identify seeded and obsolete quote statuses• Identify seeded quote status transitions and quote

status transition restrictions• Modify a seeded quote status name• Create a new quote status• Create quote status transitions



Seeded Quote Statuses


Seeded Quote Status

Approval Canceled

Approval Pending*

Approval Rejected

Approved*

Contract Canceled*

Contract Pending*

Contract Required*

Draft

Description

Approval process canceled

Quote is pending approval

Approval rejected by the approvers

Approved by the approvers

Contract canceled by contract admin

Contract is under review

A contract is required with the quote

Initial quote status for all quotes

* Denotes a read-only status


• Seeded quote statuses cannot be removed. • The statuses Ordered and Entered are obsolete. They remain in the Quote Status setup

form; however, they cannot be enabled nor can you create transitions to or from them. • All user-defined quote statuses designated as read-only in previous releases remain read-

only in this release. • Although a quote status may be read-only, the following data can be modified in the quote

(providing that the user has the appropriate permission): - Payment information - Status - Tasks and notes - New attachments may be added - Publish or unpublish quotes

NOTE: Sales Contracts is no longer on the Oracle price list. Therefore, the statuses Contract Canceled and Contract Pending will only be supported for user’s that bought Sales Contracts before it went into maintenance mode.



Seeded Quote Statuses (cont’d)

Seeded Quote Statuses (cont’d)

* Denotes a read-only status

Seeded Quote Status

Inactive*

Order Submitted*

Store Draft

Description

Quote is inactive; no activity permitted

Order has been submitted to OM

iStore internal use only



Guided Demonstration - Modifying Seeded Quote Status Names

Responsibility: Quoting Sales Manager

1. Log in to Oracle Forms with the Quoting Sales Manager responsibility.

• (N) Setup > Quote Status.

2. In the Status region, select the Draft status. Modify it as follows: − Code: New − Name: New − Description: This status replaces the old DRAFT status.

3. Save your work.

4. Close the Quote Status Setup form.

5. Launch Quoting.

6. Verify that the modified status name and description show up in the Status LOV.



Guided Demonstration - Creating a New Quote Status



2. Navigate to the Quote Status Setup form.


3. Place your cursor in any line and select (B) New.

4. Enter ACI in the Code field. This is an internal name and is not visible to the user.

5. Enter Awaiting Customer Approval in the Name field and Customer input required to proceed in the Description field. These values are displayed in the Status LOV in Quoting.

6. Ensure that the Update Allowed box is selected. This enables end-user initiated changes to quotes in this status. If not selected, quotes in this status are read only.

7. Ensure that the Auto Versioning checkbox is not selected. This checkbox is for a Forms-only feature that creates a new version when the user updates the quote.

8. Ensure that the Enabled checkbox is selected.

Note: If you want to deactivate a status, but not delete it, deselect the Enabled checkbox. You can also delete statuses (not seeded statuses) by highlighting the status and selecting Edit > Cut.

9. Save your work.

10. Open the Navigator.


12. Verify that the new status appears in the Status LOV.



Practice - Creating a New Quote Status

Overview

This practice teaches users how to set create new quote statuses.

Assumptions


• Quoting Sales Manager


Tasks

Creating a New Quote Status

Log in to Oracle Forms as the Quoting Sales Manager, to create new quote statuses.



Solution – Creating a New Quote Status

Creating a New Quote Status

Responsibility = Quoting Sales Manager




3. Place your cursor in any line and select (B) New.

4. Enter XX ACI in the Code field. This is an internal name and is not visible to the user.

5. Enter XX Awaiting Customer Approval in the Name field and XX Customer input required to proceed in the Description field. These values are displayed in the Status LOV in Quoting.

6. Select the Update Allowed box. This enabled and-user initiated changes to quotes in this status. If not selected, quotes in this status are read only.

7. Deselect the Auto Versioning checkbox. This checkbox is for a Forms-only feature that creates a new version when the user updates and saves the quote.

8. Select the Enabled checkbox.

Note: If you want to deactivate a status, but not delete it, deselect the Enabled checkbox. You can also delete statuses (not seeded statuses) by highlighting the status and selecting Edit > Cut.

9. Save your work.

10. Close the form.

11. From the Navigator, select (N) Quoting.

12. Verify that the new status appears in the Status LOV.



Seeded Quote Status Transitions


Draft

Approval Pending Approved

Order Submitted

Approval Canceled

Approval Rejected Contract

Required

Contract Pending

Inactive

Store Draft

Contract Canceled


Oracle Quoting comes seeded with the following quote status transitions: • Approval Pending to Approved • Approval Pending to Approval Canceled • Approval Pending to Approval Rejected • Approval Pending to Contract Required • Contract Pending to Approved • Contract Pending to Contract Canceled • Contract Required to Contract Pending • Store Draft to Draft • Store Draft to Inactive • Store Draft to Order Submitted • Store Draft to Contract Pending



The seeded transitions listed above are not user maintainable. Seeded status transitions are system driven based on user actions at various points in the quoting cycle. For example, if a sales representative requests approval for a quote, then the system automatically changes the quote status to Approval Pending. If the sales representative cancels the approval, then the system automatically transitions the quote status to Approval Canceled. Not all transitions are seeded. You may have to set up certain transitions to use additional functionality. For example, the status transition Draft to Inactive is not seeded but is necessary if you want to inactivate quotes.



Seeded Status Transition Restrictions


Status transitions are regulated to prevent accidental changes, such as reverting an ordered quote back to a non-ordered status. Oracle Quoting uses rules to govern which statuses you can transition to and from.


Seeded Quote Status Transitions Restricted Transitions Restricted From this Status To This Status Draft No restrictions No restrictions Approval Pending All LOV Driven Approval Canceled N/A All Approval Rejected No restrictions All Approved No restrictions All Contract Required All All Contract Pending All LOV Driven Contract Canceled No restrictions All Inactive No restrictions No restrictions Order Submitted All LOV Driven The following rules apply to quote status transitions:



• You cannot set up a transition from a status to the same status. • You cannot create new transitions to the following statuses:

- Approval Canceled - Approval Rejected - Approved - Contract Canceled - Contract Required - Store Draft

• You cannot create new transitions from the following statuses: - Approval Pending - Contract Canceled - Contract Pending - Contract Required - Order Submitted - Store Draft



Guided Demonstration - Creating a New Quote Status Transition




• (N) Setup > Quote Status

3. Highlight the Draft status in the Quote Statuses region.

4. Place your cursor in any line in the Allows Transition to Status region. Select (I) New.

5. Using the Code LOV, select Approval Pending.

6. Select the Enabled checkbox to enable the transition.

7. Repeat steps 3 through 6 for the following status transitions: − Approved to Order Submitted − Approval Rejected to Approval Pending − Approval Canceled to Approval Pending

8. Select (I) Save.



Practice - Creating a Quote Status Transition

Overview

This practice teaches users how to set create new quote statuses.

Assumptions




Tasks

Creating a Quote Status Transition

Log in to Oracle Forms as the Quoting Sales Manager, to create new quote status transitions.



Solution – Creating a Quote Status Transition






3. Highlight the Draft status in the Quote Statuses region.

4. Place your cursor in an empty line in the Allows Transition to Status region.

5. Using the Code LOV, select Approval Pending.

6. Select the Enabled checkbox to enable the transition.

7. Repeat steps 3 through 6 for the following status transitions:

Approved to Order Submitted

Approval Rejected to Approval Pending

Approval Canceled to Approval Pending

8. Save your work.



Related Profile Options


• ASO: Default Quote Status– Sets the default status of a new quote– Can be set at the site and application level– Values are all Quote Statuses– Defaults to Draft



Summary

Summary

In this module, you should have learned how to:• Identify seeded and obsolete quote statuses• Identify seeded quote status transitions and quote

status transition restrictions• Modify a seeded quote status name• Create a new quote status• Create quote status transitions


Customizing the User Interface Chapter 7 - Page 1

Customizing the User Interface Chapter 7



Customizing the User Interface

Customizing the User Interface



Objectives

Objectives

After completing this module, you should be able to do the following:• Identify how you can customize the Lines and Overview pages

of the HTML UI• Identify which objects on the Lines page can be customized

(HTML)• Identify which fields or sections must be displayed (HTML)• Identify which forms you can customize In the Forms UI• Identify which forms fields you can change (Forms)



Customization Overview


Oracle Quoting allows you to customize some elements of the Lines and Overview pages in the HTML user interface. You can:

Change column sequence (Lines page only)

Edit column labels (Lines page only)

Hide or display columns or sections

Enable/disable line level actions and buttons

Customize the Details column (Lines page only)


Customization of the Lines and Overview pages allows you to determine what information is important to your sales representatives. Your business needs may not be in-line with what you get out-of-the-box. Therefore, you can change field names, expose or hide fields, or change column sequence based on the importance of the information. Additionally, you can enable customizable fields, allowing you to include your own information. The following table shows the column/attribute mapping for the Lines page. This information is necessary to make changes to columns on the Lines page. Column Name (Label) Attribute Name Select QOT_SELECT Product QOT_PRODUCT Description QOT_DESCRIPTION Quantity QOT_QUANTITY UOM QOT_UOM Unit List Price QOT_UNIT_LIST_PRICE



Unit Adjustment Percent QOT_UNIT_ADJUST_PERCENT Line Discount QOT_LINE_DISCOUNT Unit Selling Price QOT_UNIT_SELLING_PRICE Total Price QOT_TOTAL_PRICE Charges QOT_CHARGES Line Category QOT_LINE_CATEGORY Line Type QOT_LINE_TYPE Line (Line Number) QOT_LINE Instance Name QOT_INSTANCE_NAME Custom Columns QOT_CUSTOM_COL1, QOT_CUSTOM_COL2, QOT_CUSTOM_COL3 Tax Details QOT_TAX_DETAILS The following table shows the section/attribute mapping for the Overview page. This information is necessary to make changes to sections on the Overview page. Section Name Attribute Name Lines QOT_LINES Grand Total QOT_GRAND_TOTAL Addresses QOT_ADDRESS Shipping QOT_SHIPPING Payment QOT_PAYMENT



Lines Page Customization (HTML)

Lines Page Customization (HTML)

In the Lines page, you can:• Hide or expose columns• Change column sequence• Change column names• Enable or disable actions and buttons• Enable or disable customizable columns

Lines Page Customization

Note: Once you change seeded values, there is no way to automatically revert them back to the original definitions. Display or Hide Columns You can choose which columns to display on the Lines page and in the Lines section of the Overview page. The following mandatory columns are always displayed: Note: Column names followed by an asterisk are displayed by default out-of-the-box.

• Select* • Product* • Description* • UOM* • Quantity*

The following seeded columns are optional: • Unit List Price* • Unit Adjustment Percent*



• Line Discount Note: If ASO: Calculate Price is set to Manual, the Line Discount field is not shown even if it is enabled and the user has the ability to perform price overrides.

• Unit Selling Price* • Total Price* • Charges • Line Category • Line Type • Line* • Instance Name • Link to Customer Page • Tax Details

Enable or Disable Line Level Actions or Table Level Buttons You can customize the Actions menu and buttons available on the Lines page. You determine which options appear on the UI. The Action menu options and buttons are controlled by lookup types and codes. See the slide on Enabling or Disabling Action Menu Options and Buttons. Customizing the Details Columns The Details columns on this page are hardcoded to the file names:

• customLineDetails1.jsp • customLineDetails2.jsp • customLineDetails3.jsp

If you want to enable and use these columns, you must provide the JSP files, using the filenames provided above. Oracle Quoting passes in two parameters for these columns:

• qotHdrId – Quote Header ID • qotLnId – Quote Line ID



Guided Demonstration - Customizing the Lines Page

Responsibility: Application Developer Common Modules

1. Log in to Oracle Forms using the Application Developer Common Modules responsibility.

2. Navigate to the Define Regions form.

• (N) Define Region.

3. Select (M) View > Query by Example > Enter.

4. Enter QUOTELINEDETAILS in the Region ID field.

5. Select (M) View > Query by Example > Run.

6. Select (B) Region Items.

To hide a seeded column, deselect the Node Display checkbox for the corresponding column. To display a column, select the Node Display checkbox.

Note: Although you can deselect the Node Display checkbox for the mandatory columns, the columns will still display in the Quoting UI. You cannot hide mandatory columns.

To edit column labels, enter a new value in the Long Label field for the corresponding line.

To edit the column sequence, change the value in the Sequence field. The lowest sequence number if the first column displayed on the Lines page.

7. Click (I) Save.

Note: You will not see the change until you bounce the web server and login again.



Overview Page Customization (HTML)

Overview Page Customization (HTML)

You can determine which sections appear on the Overview page in the HTML user interface. You can also determine which actions appear in the Actions menu.

Overview Page Customization

By default, the Overview page displays the following sections: • General Information • Lines • Grand Total • Addresses • Shipping • Payment

You can hide all sections except General Information. Note: The Lines section organization is based on the customization of the Lines page.



Guided Demonstration - Customizing the Overview Page

Responsibility: Application Developer Common Modules

1. Log in to Oracle Forms.


• (N) Define Regions.


4. Enter QUOTEOVERVIEWSECTIONS in the Region ID field.


6. Select Region Items.

To hide a seeded column, deselect the Node Display checkbox for the corresponding column. To display a column, select the Node Display checkbox.

Note: Although you can deselect the Node Display checkbox for the mandatory columns, the columns will still display in the Quoting UI. You cannot hide mandatory columns.

7. Click (I) Save.

Note: You will not see the change until you bounce the web server and login again.



Practice - Customizing the Overview Page

Overview

This practice teaches users how to customize the Overview page in the HTML user interface.

Assumptions


• Application Developer Common Modules


Tasks

Customizing the Overview Page

Log in to Oracle Forms as the Application Developer Common Modules, to customize the Overview page.



Solution – Customizing the Overview Page

Customizing the Overview Page

Responsibility = Application Developer Common Modules

1. Log in to Oracle Forms (ebusiness/welcome) with the Application Developer Common Modules responsibility.


• (N) Define Regions

3. From the View menu, select Query by Example > Enter.

4. Enter QUOTEOVERVIEWSECTIONS in the Region ID field.

5. From the View menu, select Query by Example > Run.


7. Deselect the Node Display checkbox for the following sections: − Addresses − Shipping

8. Close this form and select the CRM HTML Login link.

9. Log in to Oracle Quoting (Ljones/welcome).

10. Navigate to the Overview page by selecting the Overview link in the sidebar menu.

The Overview page should display the General Information, Lines, Grand Total, and Payment sections, but not the Addresses and Shipping sections.



Enabling or Disabling Actions and Buttons (HTML)

Enabling or Disabling Actions and Buttons (HTML)

You can customize certain Actions menus and buttons that appear throughout the HTML user interface. Using lookup types, you determine the available functionality.

Enabling or Disabling Action Menu Options and Buttons

The following table lists the lookup type that controls the Action Menu and buttons on the Lines page. Lookup Type Description ASO_LINE_ITEM_ACTION Determines which actions appear in the Lines page Actions menu. ASO_LINE_ACTION Determines which line level actions appear on the Lines page. ASO_QUOTE_ACTION Determines which actions appear In the Overview page Actions menu. ASO_PRODUCT_SOURCE Determines sources available when performing a product search. ASO_IB_RELATIONSHIP_TYPES Determines which Install Base relationship types are available.



ASO_IB_ACTION_TYPES Determines which actions are available on the Search and Select: Installed Base Product page.



Guided Demonstration - Enabling or Disabling Action Menus and Buttons


1. Log in to Oracle Forms (ebusiness/welcome) using the Quoting Sales Manager responsibility.

2. Navigate to the Quick Codes form.

• (N) Setup > Quick Codes


4. Enter one of the following lookup types in the Type field.

ASO_LINE_ITEM_ACTION – To enable or disable actions in the Lines page actions menu.

ASO_LINE_ACTION – To enable or disable line level actions on the Lines page.

ASO_QUOTE_ACTION – To enable or disable actions in the Overview page Actions menu.

ASO_IB_ACTION_TYPES – To enable or disable actions on the Search and Select: Installed Base Product page.

ASO_PRODUCT_SOURCE – To enable or disable sources available when performing a product search.

ASO_IB_RELATIONSHIP_TYPES – To enable or disable Install Base relationship types.


6. Locate the code to enable and select the Enabled checkbox. To disable a code, deselect the checkbox.

7. Click (I) Save.

8. Bounce the web server. When you next log in to Quoting, the change is visible.



Practice Overview: Customizing the Lines Page (HTML)

Practice Overview: Customizing the Lines Page

(HTML)This practice covers the following topics:• Hiding and Displaying Columns• Changing Column Names• Changing the Sequence of the Columns



Practice - Customizing the Lines Page

Overview

This practice teaches users how to customize the Lines page in the HTML user interface.

Assumptions


• Application Developer Common Modules


Tasks

Customizing the Lines Page

Log in to Oracle Forms as the Application Developer Common Modules, to customize the Lines page.



Solution – Customizing the Lines Page

Customizing the Lines Page

Responsibility = Application Developer Common Modules

1. Log in to Oracle Forms with the Application Developer Common Modules responsibility.


• (N) Define Regions

3. From the View menu, select Query by Example > Enter.

4. Enter QUOTELINEDETAILS in the Region ID field.

5. From the View menu, select Query by Example > Run.


7. Deselect the Node Display checkbox for the following column: − Unit Selling Price

8. Select the Node Display checkbox for the following columns: − Charges − Line Type

9. Change the Long Label value for the Line column to Line #.

10. Reorder the sequence of the columns as follows. To reorder the columns, change the value in the Sequence fields.

− Select; Sequence = 10 − Line #; Sequence = 20 − Product; Sequence = 30 − Description; Sequence = 40 − Quantity; Sequence = 50 − UOM; Sequence = 60 − Unit List Price; Sequence = 70 − Unit Adjustment Percent; Sequence = 80 − Charges; Sequence = 90 − Total Price; Sequence = 100

11. Click (I) Save.

12. Bounce the web server and log in to Quoting.

Note: The change is not visible until you bounce the web server and log back in to Quoting.



13. Navigate to the Lines page to view your changes.



Customizing Forms Using Folder Functionality


You can customize the following forms using folder functionality:

Quote Customer Search

Quote Search

Quote Header

Quote Lines

Sales Team


Quoting Forms uses Oracle Applications Folder technology to allow users to customize certain forms in the UI. You can perform the following actions to the fields on these forms:

• Hide/show • Move fields • Change field size • Rename prompt

There are certain field that cannot be hidden in each form: Form Field Quote Search Quote Number Customer Search > Organization Customer Customer Search > Person Last Name Quote Header > Summary Order Type Quote Header > Summary Currency Quote Header > Summary Salesperson



Quote Header > Addresses Quote To Address Details Quote Header > Addresses Bill To Address Details Quote Header > Addresses Ship To Address Details Quote Header > Addresses Default From Quote To (Bill To) Quote Header > Addresses Default From Quote To (Ship To) Quote Header > Addresses Bill To Customer Quote Header > Payment, Shipping Payment Terms Quote Header > Payment, Shipping Payment Type Quote Header > Tax Tax Handling Quote Header > Tax Tax Code Quote Header > Tax Amount Quote Lines > Pricing Line Quote Lines > Pricing Model Status Quote Lines > Pricing Product Quote Lines > Pricing Qty Quote Lines > Pricing UOM Quote Lines > Bill To Customer Quote Lines > Ship To Customer Quote Lines > Shipping Requested Date Quote Lines > Service Reference Type Sales Team Full Access Sales Team Name



Guided Demonstration - Customizing Forms

Responsibility: Quoting Sales Agent

1. Log in to Oracle Forms (ebusiness/welcome) using the Quoting Sales Agent responsibility.

Explain that you can customize the forms using the Quoting Sales Manager responsibility as well.

2. Navigate to the main Quoting form.

• (N) Quoting

3. Enter 1608 in the Account field.

4. Place your cursor in the Agreement field and select (M) Folder > Hide Field.

Explain that you can also show this field by selecting (M) Folder > Show Field. A pop-up window lists the available fields to show.

5. Place your cursor in the Order Number field and select (M) Folder > Change Prompt.

6. In the Prompt field, enter Order # and click Ok.

7. Place your cursor in the Price List field and select (M) Folder > Move Up.

You can repeat this process until all fields are in line.

8. Once your form is customized to meet your needs, select (M) Folder > Save As.

9. Name your folder and click (B) OK.

Your folder name appears next to the folder icon. When you select the folder icon, your folder is now an available option.



Summary

Summary

In this module, you should have learned how to:• Identify which columns you can customize on the Lines

page• Customize the Lines page columns, Overview page

sections, and Actions menu and buttons


Setting Up Manual Pricing and Tax Calculation Requests Chapter 8 - Page 1

Setting Up Manual Pricing and Tax Calculation Requests Chapter 8



Setting Up Manual Pricing and Tax Calculation Requests

Setting Up Manual Pricing and Tax Calculation Requests


<30> minutes Lecture <15> minutes Practice <45> minutes Total



Objectives

Objectives

After completing this module, you should be able to do the following:• Explain manual pricing and tax requests• Identify manual pricing and tax profile options• Identify possible manual pricing and tax settings• Identify related concurrent programs• Explain the difference between online and batch

processing



Manual Pricing and Tax Calculation Requests Overview


Out-of-the-box, Quoting automatically calls Oracle Advanced Pricing to calculate pricing and tax when a price-affecting change is made to a quote. Quoting now allows users to manually calculate pricing and tax for a quote by request.


• The option to manually price a quote is particularly helpful to users who are: - Entering a large number of quotes lines - Entering a large number of quote lines in a Configurator session - Making a large number of quote line changes - Entering a large number of quote lines in a quote template or across multiple

templates. - Have complex tax or pricing setups

• Any quote change NOT listed below affects the pricing for a quote:

- Sales credits changes - Attachments changes - Notes changes - Tasks changes - Initiate/Cancel Approvals



- Request Contract Creation or Assistance - Sales Team changes - Web Publish or Unpublish - Initiate Credit Check - Sales Supplement changes - System driven quote status changes - Place Order



Manual Pricing and Tax Calculation: Options


When you choose to manually calculate pricing and tax, you can select to calculate interactively or through batch processing. • Now – Calculates tax interactively, while you wait.

You cannot perform any actions on the quote while the request is in process.

• Submit pricing request and notify me when it is complete – Runs a concurrent program in the background. You can check the details.


The following table shows suggested settings for the Pricing Options profile options, based on user needs. Scenario ASO: Calculate Price ASO: Calculate Tax ASO: Enable Batch Processing Large # of Manual Manual Yes quote lines, Complex pricing and tax setups Large # of Manual Manual Yes quote lines, simple pricing and tax setups



Small # of Automatic Manual Yes quote lines, simple pricing setups, complex tax setups Small # of Automatic Automatic No quote lines, simple pricing and tax setups Small # of Manual Automatic Yes quote lines, complex pricing, simple tax setups Note: This combination is not recommended and not supported.



Setting Up Manual Pricing and Tax Calculation Requests: Profile Options

Setting Up Manual Pricing and Tax Calculation Requests: Profile Options

The following profile options must be set to enable manual pricing and tax calculation requests:• ASO: Calculate Price• ASO: Calculate Tax• ASO: Enable Batch Processing

Profile Options

ASO: Calculate Price Determines when the products and services in the quote are priced. This profile can be set at all levels. If set to Automatic, the quote is priced automatically each time a price-affecting change is made. If set to Manual, users can price the quote whenever they choose. If null, defaults to Automatic. ASO: Calculate Tax Determines when tax is calculated for a quote. This profile option can be set at all levels. If set to Automatic, tax is calculated each time a price affecting change is made. If set to Manual, users can calculate tax whenever they choose. If null, defaults to Automatic.



Note: Setting ASO: Calculate Price to Automatic and ASO: Calculate Tax to Manual is not recommended and not supported. This is not a valid set up, and the tax calculation may be wrong. ASO: Enable Batch Processing Determines how the quote is priced. If you choose to price the quote interactively, you must wait while the quote is being priced – you cannot perform any action on the quote. If the quote is priced via a batch process, you will be notified when the pricing call is complete. If null, defaults to No. This profile can be set at the site level.



Guided Demonstration - Enabling Manual Pricing


1. Log in to Oracle Forms (sysadmin/sysadmin) using the System Administrator responsibility.

2. Navigate to the Find System Profile Values page.

• (N) Profile > System

3. Select the level at which you want to set the profiles.

4. In the Profile field, enter ASO%Calculate%.

5. Select (B) Find.

6. Change the values of the ASO: Calculate Tax and ASO: Calculate Tax profiles to Manual at the Site level.


8. In the Profile fields, enter ASO%Enable Batch%.

9. Select (M) View > Query by Example > Run. The ASO: Enable Batch Processing profile appears.

10. Change the profile value to Yes at the Site level.

11. Click (I) Save.

12. Log in to Quoting.

13. Create a quote or select an existing quote that contains products.

14. From the Actions menu on the Overview page, select Price Quote.

15. Choose to compute Both tax and pricing.

16. Choose to Submit pricing request and notify me when it is complete. A pop-up window confirms the request and displays a concurrent request number. Note the concurrent request number.

17. To view the details of the pricing request, select Actions > Pricing Request Details > OK. When the pricing request is complete, the Pricing Status and Tax Status change to Complete.



Practice - Manually Calculating Pricing and Tax

Overview

This practice teaches users how to manually calculate tax and pricing for a quote.

Assumptions



• The following profile options are set: − ASO: Calculate Prices = Manual − ASO: Calculate Tax = Manual − ASO: Enable Batch Processing = Yes


Tasks

Manually Calculating Pricing and Tax

Log in to Oracle Forms as the System Administrator, to manually calculate pricing and tax for a quote.



Solution – Manually Calculating Pricing and Tax

Manually Calculating Pricing and Tax


1. Log in to Oracle Quoting (LJones/welcome) using the CRM HTML Login link.

2. Select the Quote tab.

3. Create a quote by selecting the Create Quote button.

4. Enter the following information on the Create Quote page: − Customer: BusinessWorld − Account: 1608

5. Select Apply.

6. On the Lines page, select Add Products. Add the following product to the quote: − AS54888

7. Navigate to the Overview page. The Pricing and Tax statuses will be incomplete.

8. Select Actions > Price Quote.

9. Choose to calculate both pricing and tax.

10. Choose to Submit pricing request and notify me when it is complete. A pop-up window displays confirmation that the pricing request has been submitted and lists the request number.

11. To view request details, select Actions > Pricing Request Details.

The Pricing and Tax status fields will change to Complete, when the Pricing and Tax calculations are complete.



Summary

Summary

In this module, you should have learned how to:• Explain the difference between manual and

automatic pricing• Explain the difference between online and batch

pricing requests• Identify Manual Pricing profile options


Enabling interMedia Search Chapter 9 - Page 1

Enabling interMedia Search Chapter 9



Enabling interMedia Search

Enabling interMedia Search



Objectives

Objectives

After completing this module, you should be able to do the following:• Identify interMedia set up steps• Identify related profile options



Overview: interMedia Search


The interMedia search allows you to search the product catalog for products using any of the following criteria:

Description

Part Number

Long Description


If interMedia search is not enabled, you can search by product number and description in the Product field. You must enter a value followed by the wildcard character or an exact match, whereas the interMedia performs keyword searches and does not require wildcards.



interMedia Profile Options


To enable interMedia search, you must set the following profile option:• ASO: Enable interMedia Search


ASO: Enable interMedia Search This profile determines if the product search (against the product catalog) uses interMedia search. If set to Yes, the product search uses interMedia. If set to No, you can only perform searches using the product number and description. You can set this profile at the Site and Application levels. Defaults to No.



Practice Overview: Enabling interMedia Search

Practice Overview: Enabling interMedia Search

To enable interMedia search, you must perform the following steps:1. Set the related profile option.2. Run the concurrent program iStore Search Insert.3. Refresh the Search Index



Guided Demonstration - Enabling interMedia Search

Responsibility: iStore Administrator, Vision Enterprises

1. Ensure that the profile option ASO: Enable interMedia Search is set to Yes.

2. Log in to Oracle Forms using the iStore Administrator, Vision Enterprises responsibility.

3. Select Single Request and select (B) Ok.

4. Select iStore Search Insert from the Name LOV.

5. Select (B) Submit. Note the Request ID.

6. You can view the progress of the request by selecting View Requests and searching by request ID.



Guided Demonstration - Performing an interMedia Search


1. Log in to Quoting using the CRM HTML Login page (Ljones/welcome)

2. Select the Quote tab.

3. Click (B) Create Quote.

4. In the Create Quote page, enter the following information: − Quote Name = iMedia Search Test − Customer Name = Business World − Account Number= 1608

5. Select (B) Apply.

6. Select (B) Add Product.

7. Enter Sentinel in the Product field and click (B) Go.

No products are returned because the profile option ASO: Enable interMedia Search is, by default, set to No. Therefore, interMedia search is not currently enabled.

8. Log out of Quoting.

9. Log in to Oracle Forms (sysadmin/sysadmin) with the System Administrator responsibility.


• (N) Profiles > System

11. In the Find System Profile Value form, select Site.

12. In the Profile field, enter ASO%interMedia% and click Find.

13. Change the value of this profile to Yes.

14. Click (I) Save.

15. Log back into Quoting using the CRM HTML Login page (Ljones/welcome).

16. Select the quote you created earlier and navigate to the Lines page.


18. Enter Sentinel in the Product field and click (B) Go.



The results list displays all products whose descriptions contain the word Sentinel.



Summary

Summary

In this module, you should have learned how to:• Enable interMedia Search• Identify the difference between regular search and

interMedia search• Identify related profile options


Setting Up Quote Security Chapter 10 - Page 1

Setting Up Quote Security Chapter 10



Setting Up Quote Security

Setting Up Quote Security





Objectives

Objectives

After completing this module, you should be able to do the following:• Define overall quote security• Distinguish between access security, function

security, and new quote security• Manually set up basic quote security for sales team

and manager access to quotes• Identify security-related profile options



What is Quote Security?


Overall quote security comprises the following:• Quote access security• Quote function security• New quote security


Quote Access Security Quote access security addresses the following concerns: Which quotes should be available to each user? With security enabled, users may only have access to a subset of the total quotes available to him/her. Determining which quotes make up this subset is the first security component. Available quotes should be those where the user is on the sales team or those where the user’s subordinates are on the quote sales team. Given the quotes available to a user, what level of data access should the user have to each of these quotes? For some quotes, the user should have update ability, for other quotes the user should only have view access. This data access level is in part determined by why the quote is available to the user and partly by application setup options. Quote Function Security Set up independently from quote access security, quote function security determines the following:



Once a user has update access to a quote, what are the restrictions for which application menu items, buttons and fields should be enabled/disabled for that user? For example, one user may be restricted from performing manual overrides or from placing orders from quotes, while another user can perform both of these functions. This security is determined by profile options settings assigned to a user or responsibility. Quote function security only applies to quotes where the user has update ability. For quotes that are view only, the user is not be able to a perform any quote function that changes the quote in any way, regardless of function security settings. New Quote Security While the other security solutions determine security for existing quotes, new quote security determines whether a user can create new stand alone quotes, and if so, for which customers. This option can be enabled or disabled independently of quote access security. For example, a user may have update access to all quotes, yet may not have the ability to create any new stand alone quotes.





The following profile options enable quote security. Once set, further quote security options can be implemented.• ASO: Security Enable from API

– Used to enable or disable quote security– Must be set to Yes at the site level

• ASO: Enable Security Check – Used to enable or disable quote security– Should be set at all levels


ASO: Security Enable from API Determines if security is enabled through the security APIs. Mandatory if security is enabled. Defaults to No. Note: This profile completely disables security. It is intended to improve application performance and should be set to No only if there are no users with security enabled through ASO: Enable Security Check. ASO: Enable Security Check Determines whether Quote Access Security is enabled. Quote Access Security determines which quotes users can access and at what level. Defaults to No. Note: If this profile is set to No, you should not set other security profile options, as they do not work when security is turned off.



Quote Access Security


Once overall quote security is enabled, quote availability and quote data security can be implemented.• Quote availability security determines which quotes

are available to each user.• Quote data security determines whether the user

has view-only or update access.


Quote access security is not concerned with what actions a user can perform on an updateable quote. To restrict actions on a quote to which a user has update access, you must implement quote function security. Use ASO: Enable Security Check to enable Quote Access Security.



Quote Availability: Sales Team Access


To implement availability security for sales team members, the following conditions must be met:• Access is restricted to members of the quote’s sales

team. A sales team member is any user that has been assigned to a quote, whether manually or automatically.

• To be a valid sales team member, the user must be set up as a resource.

• A resource can only be listed once on a sales team at any given point in time.


Users are not required to have a role or group to be a member of the sales team. This ensures that a sales team can consist of cross-functional employees (e.g., contract administrators, service agents). Automatic Sales Team Assignments

• If the quote creator is a resource (therefore security can be enabled), the quote creator is automatically be added as a member to the quote sales team.

• If different from the quote creator, the primary sales agent assigned to a quote is also automatically be added as a member to the quote sales team.

• If a quote is created from an OTS/OSO opportunity, the sales team for the quote defaults to the resources on the Opportunity sales team. This includes the values for resource, group, role, title, phone number, email, and full access flag.

The Primary Sales Agent • The logged in user is the default primary sales agent if the user meets the following criteria:

- The user is a valid resource - The user is set up as a sales rep



• If the primary sales agent doesn’t meet these criteria, then the system uses the person listed in the ASO: Default Salesrep profile option.

• The default primary sales agent can be changed if the value of the ASO: Update Sales Team profile option is set to Yes .

• A primary sales agent is required to save a quote.



Guided Demonstration - Setting Up Sales Team Member Access (Forms UI)


1. Log in to Oracle Forms (ebusiness/welcome) with the System Administrator responsibility.


• Select (N) Profile > System.

3. Verify that the following profile options are set to Yes:

ASO: Enable Security Check

ASO: Security Enable from API

4. Switch to the Quoting Sales Agent responsibility by choosing File > Switch Responsibility.

5. Navigate to the Quoting form.

• Select (N) Quoting.

6. Create a quote and add the item AS54888.

7. Save the quote and record the quote number.

8. Select Actions > Sales Team > OK. The logged in user is listed as the primary sales rep.

9. Select an empty line and enter the name of the user that has been set up as a sales rep (Lisa Jones) and that has also been assigned the Quoting Sales Agent responsibility.

10. Select the Full Access checkbox.

11. Click (I) Apply and then close the quote.


13. Log back in as the sales team member you added to the quote.


15. Use F11 to search.

16. Enter the quote number, you previously created, in the Quote Number field and press CTRL + [F11]. The quote is now accessible to the sales team member.



Practice - Setting Up Sales Team Member Access

Overview

This practice teaches users how to set up sales team member access.

Assumptions




Tasks

Setting Up Sales Team Member Access

Log in to Oracle Forms as the System Administrator, to set up sales team member access.



Solution – Setting Up Sales Team Member Access

Setting Up Sales Team Member Access

Responsibility =Customer Support, Vision Operations

1. Log in to Oracle Forms with the System Administrator responsibility.

2. Navigate to the System Profile Values form.


3. Verify that the following profile options are set to Yes:

ASO: Enable Security Check

ASO: Security Enable from API

4. Log out and log back in as a user with the Quoting Sales Agent responsibility.


6. Create a quote and add the item AS54888.

7. Save the quote and record the quote number: ________________

8. Select Actions > Sales Team > OK. The logged in user is listed as the primary sales rep.

9. Select an empty line and enter the name of the user that has been set up as a sales rep (Lisa Jones) and that has also been assigned the Quoting Sales Agent responsibility.

10. Select the Full Access checkbox.

11. Click (I) Apply and then close the quote.


13. Log back in as the sales team member you added to the quote.


15. Use F11 to search.

16. Enter the quote number, you previously created, in the Quote Number field and press CTRL + [F11]. The quote is now accessible to the sales team member.



Quote Availability: Manager Access


• Resource Manager Role Types and Role Attributes are used to determine which users should be considered managers and given manager access by Quoting security.– Role types allow roles to be striped by application

group. – Role Attributes are flags that are selected for

each role to indicate if that role is a Manager, Member, Lead, or Administrator.


The ASO: Manager Role Access profile option determines whether a manager receives update permission for the entire sale team or inherits the highest level permission assigned to a sales team member. If the logged in user is set up as a resource and is also a manager, then the following quotes are available:

• All quotes where the user is on the quote sales team • All quotes where a subordinate of the user is on the quote sales team



Guided Demonstration - Setting Up Manager Access

Responsibility: CRM Resource Manager, Vision Enterprises

1. Log in to Oracle Forms (ebusiness/welcome) with the CRM Resource Manager responsibility.

2. Navigate to the Define Groups form.

• (N) Maintain Resources > Groups

3. In the Define Groups form, enter a name for the group in the Name field.

4. Select (T) Members and use the Category field LOV to select Employee.

5. On the same line, use the Number LOV to enter a sales agent number or the Name LOV to enter a sales agent name. The resource number and operating unit fields automatically populate.

6. Select the sales agent line, and then click (B) Member Roles.

7. Use the Role and Role Type LOVs to select Sales and Sales Representative, respectively. Click (B) OK.

8. From (T) Members, select the next available line and repeat steps 5-8 substituting Sales Manager for Sales Representative.

9. Select (T) Roles. Use the Role Type LOV to enter Sales. Use the Role LOV to enter Sales Representative.

10. Select the next available line and repeat step 10 this time entering Sales Manager in the Role field.

11. Click (I) Save. A group number is created.

12. Click (T) Usages. Use the Usages LOV to enter Sales and Telesales.

13. Click (I) Save.

14. Select (M) File > Switch Responsibility and select the System Administrator responsibility.

15. Navigate to Profile > System.

16. In the Find System Profile form, enter the manager’s user name in the User field.

17. Enter ASO%Manager% in the profile field and then click (B) Find.



18. Set the ASO: Manager Role Access profile option value to Update for the user and then click (I) Save.

19. Log in to Quoting and verify that the manager can access and update any quote created by the subordinate sales team member.



Practice - Setting Up Manager Access

Overview

This practice teaches users how to set up manager access.

Assumptions





Tasks

Setting Up Manager Access

Log in to Oracle Forms as the CRM Resource Manager, Vision Enterprises to set up manager access.



Solution – Setting Up Manager Access

Setting Up Manager Access


1. Log in to Oracle Forms (ebusiness/welcome) with the CRM Resource Manager, Vision Enterprises responsibility.

2. Navigate to the Find Resources form.

• Maintain Resources > Resources

3. In the Name field, query for the user you created.

4. Select (T) Roles.

5. In the Role Type field, select Sales.

6. In the Role field, select Sales Manager.

7. Save your work.

8. Close this form and navigate to the Define Groups form.

• (N) Maintain Resources > Groups

9. In the Define Groups form, enter XXSales Group for the group in the Name field.

10. Select (T) Members and use the Category field LOV to select Employee.

11. Use the Name LOV to enter the following sales agents: − Ms. Rachel Abbott (Number 11092) − Mrs. Lisa Jones (Number 10125) − The user you created

The resource number and operating unit fields automatically populate.

12. Select the sales agent line for Ms. Rachel Abbott, and then click (B) Member Roles.

13. Use the Role and Role Type LOVs to select Sales and Sales Representative, respectively. Click (B) OK. Repeat these steps for the user you created.

14. Repeat this process for Mrs. Lisa Jones.

15. From (T) Members, select the line for your user and repeat steps 5-8 substituting sales manager for sales agent.



16. Select (T) Roles. Use the Role Type LOV to enter Sales. Use the Role LOV to enter Sales Representative.

17. Select the next available line and repeat step 16 this time entering Sales Manager in the Role field.

18. Click (I) Save. A group number is created.

19. Click (T) Usages. Use the Usages LOV to enter Sales and Telesales.

20. Click (I) Save.

21. Select (M) File > Switch Responsibility and select the System Administrator responsibility.

22. Navigate to Profile > System.

23. In the Find System Profile form, enter PSTOCK in the User field.

24. Enter ASO%Manager% in the profile field and then click (B) Find.

25. Set the ASO: Manager Role Access profile option value to Update for the user and then click (I) Save.

26. Log in to Quoting and verify that the manager can access and update any quote created by the subordinate sales team member.



Quote Availability Security: Identifying a Manager’s Subordinates

Quote Availability Security: Identifying a Manager’s Subordinates

• Resource Manager groups are used to determine which resources are subordinates for each manager

• A group can only have one resource with a manager role.

• Groups can be parents or children of other groups. The parent-child relationship is used to establish group hierarchies.

• Only groups with the usage type “Sales and TeleSales” are used to establish the quote access hierarchy.



Quote Data Security: Specifying View-only or Update Access

Quote Data Security:Specifying View-only or Update Access

If other sales team members are permitted access to a quote, then quote data security can determine if they can modify or if they have view-only access to the quote.• The setting of the Full Access checkbox determines

update access for individual sales team members. Note: Quote data security does not determine what specific actions can be performed on an updateable quote.

Update Access

Update access means that the user can modify any quote field and perform any quote function that is not restricted via other quoting requirements. For example, a user with update status can change any quote field when the quote is in an updateable status. If the same quote is changed to a view-only status, the user may only update the payment information and other fields that are updateable for read-only statuses.

View Only Access View access means that the user cannot modify any quote field or perform any quote function which changes quote data regardless of the restrictions imposed by other quoting requirements. For example, a user with view only access cannot modify any quote data even though the quote may be in an updateable status. If the same quote is changed to a read only status, the user still may not update the payment information and other fields that are updateable for read only statuses.

Full Access flag For each resource selected on the quote sales team, there is a full access flag which can be selected or un-selected. The primary sales agent on the sales team should always have the Full Access flag selected.



Guided Demonstration - Setting the Full Access Flag

Responsibility: Quoting Sales Agent

1. Log in to Oracle Forms (ebusiness/welcome) with the Quoting Sales Agent responsibility.

2. Navigate to the Quoting form.

• (N) Quoting.

3. Retrieve or create a quote.

4. Select Actions > Sales Team > OK.

5. Add a Sales Team member and de-select the Full Access checkbox.

6. Select (I) Save.

7. Verify that the sales team member cannot update the quote.

Sales team members that do not have the Full Access flag checked, can view quotes, but cannot update them. The Primary Salesperson should always have the Full Access flag checked.



Quote Function Security


Quote function security determines which actions can be performed by a user with update access to a quote (e.g., manual price overrides, trade-ins, submit orders, etc.)• Profile options restrict the functionality available to

the users who can update a quote.


Any user with a valid user ID is impacted by quote function security. There is no requirement that the user be a valid resource or have an assigned role since these security requirements are not based on sales team, group, or other context dependent information. See the Security-Related Profile Options section of this module for descriptions of profile options that impact function security.



New Quote Security

New Quote Security

New quote security restricts the parties (customers) for which a sales agent can create quotes. • The ASO: New Quote Security profile option

determines new quote security restrictions.

New Quote Security

ASO: New Quote Security If set to Yes, the user cannot create new standalone quotes or copy existing quotes to a new quote. Users can create quotes from opportunities. If set to No, the user can create quotes for all customers. If set to Sales Team, the user must be on the Account sales team for the customer in order to select that customer in the quote header or copy a quote for the customer. Note: Account sales teams are set up in Oracle TeleSales or Oracle Sales Online. You cannot set up account sales teams in Quoting. Therefore, if you are using Quoting standalone, you should not set this profile to Sales Team.



Security-Related Profile Options


The security profile options enable security and determine the level of security for a quote or a user.


Profile options listed with an asterisk (*) are mandatory for quote security. See Notes sections for additional details. ASO: Create New Customer Default Value: Yes Allows a user to create new customer information. This ensures that administrators wishing to protect the integrity of customer data can restrict creation of new customers to a limited number of users. This profile can be set at all levels. For Forms, this profile option enables or disables the AR Quick Customer Entry form. For HTML, this profile option determines if there are active links to the Quoting Create Customer pages. Note: if a customer has set up OTS/OSO security to restrict customer access based on account sales team, this profile option should be set to “No” and customers should be created from OTS/OSO. ASO: Create New Shipping/Billing Customer Default Value: Yes



Determines if HTML users can create new shipping and billing customers. If set to Yes, users can create new shipping and billing customers. If set to No, users cannot create new shipping and billing customers. This profile can be set at all levels. ASO: Default Sales Group Default Value: <none> Populates the primary sales representative group when the primary sales representative defaults from ASO: Default Salesrep. This group must be a sales group with the usage "Sales and TeleSales.“ Ensure that the selection is valid for the sales representative selected in ASO: Default Salesrep. This profile can be set at all levels. ASO: Default Salesrep Default value: <none> Provides a default sales representative on the quote, if the logged-in user is not a valid sales representative. This profile can be set at all levels. ASO: Enable Security Check Default Value: No Determines whether quote access security is enabled. If set to No, users have update access to all quotes. If this profile is set to No, you should not set other Security profiles, as they do not work when security is turned off. This profile can be set at all levels. ASO: Enable Submit Button Default Value: Yes Determines whether a user or responsibility can submit quotes to Order Management as orders. This profile can be set at all levels. ASO: Enforce Account Relationships Default Value: No Determines if a user can select only ship-to/bill-to customers with existing relationships to the sold-to customer. If set to Yes, the user can only select ship-to or bill-to customers with existing relationships to the sold-to customer. In the HTML UI, allows the user to conduct a blank search for ship-to or bill-to customers. If set to No, the user can select any ship-to or bill-to customer regardless if there is an existing relationship with the sold-to customer. This profile can be set at all levels. ASO: Manager Role Access Default Value: Inherit Determines whether a user can access subordinate sales team member quotes. The profile values are:

• Update: User can update all quotes where a subordinate is on the quote sales team • Inherit: User has the same access level as subordinate on the quote sales team.

If a manager has “Inherit” level access and has more than one subordinate on a sales team with different access levels, the manager receives the higher (update) access level. This profile can be set at all levels. Note: Sales reps and managers must be defined in the system as part of a group of type “Sales and Telesales” in order for managers to to access subordinate’s quotes. ASO: New Quote Security



Default Value: No Controls a users ability to create new quotes. This profile can be set at all levels. If set to Yes, the user is not able to create new stand alone quotes. This includes copying existing quotes to new quotes. This does not restrict the user’s ability to create quotes from opportunities. If set to No, the user is able to create new quotes for all customers. If set to Sales Team, the requirements listed below apply:

• When querying customer information for the creation of a new quote, users are restricted to selecting only those customers where the user is on the account sales team.

Note: Account sales teams are set up in Oracle Sales Online or Oracle TeleSales. If you are using standalone Quoting, not integrated with either OSO or OTS, you should not use this profile setting.

• If the user is not on the account sales team for a customer, the user will not be able to select that customer in the quote header. This does not mean that a user cannot access an existing quote for a customer if the quote meets the security requirements listed previously (e.g., the user is on the quote sales team or manager of someone on a quote sales team). However, the user is prevented from copying the existing quote header to a new quote.

ASO: OM Access Default Value: Full Determines the mode of access to Oracle Order Management forms via the Customer History form. Access can be Full or Read Only. These values are based on the lookup type ASO_OM_ACCESS_PRIVILEGE. If set to Full, the user can update an order in the Oracle Order Management form. If set to Read Only, the user can only view an order in the Oracle Order Management form. This profile can be set at the responsibility and user levels. Note: This profile applies to the Forms UI only. ASO: Price List Override Default Value: Yes Allows a user to change the selected price list for a quote. This ensures that users cannot inadvertently quote an inaccurate price based upon an incorrect price list selection. This profile can be set at all levels. ASO: Require Group Default Value: No Determines if a group selection is required for the Primary Sales Agent. If set to Yes, the user cannot save the quote until a group selection is made. If set to No, the user can save the quote without a group selection. If this profile option is set to Yes, setting up at least one group for each sales representative is mandatory. This profile option can be set at the site level. ASO: Security Enable from API Default Value: No Determines if security is enabled through the security APIs. This profile is mandatory if Security is enabled. This profile is intended to improve application performance and must be set to Yes if you have any users with security enabled through ASO: Enable Security Check.This profile option can be set at the Site level. ASO: Status Override Default Value: No



Allows a user to update a quote while it is in a read-only status. This ensures that there is a mechanism to override quote data if a mistake has been made prior to the quote transitioning to read only status. This profile option can be set at all levels. ASO: Update Customer Default Value: Yes Allows the user to update existing customer information in the HTML UI. This profile can be set at all levels. ASO: Update Sales Team Default Value: Yes Allows a user to manually update sales team information, including manual assignment of the primary sales agent. This restricts sales agents from assigning or removing team members inappropriately. This profile can be set at all levels. ASO: Validate Salesrep Default Value: Yes This profile is used to determine whether a sales representative must be specified on the quote prior to creating an order. If this profile is set to Yes, a sales representative must be specified on the quote prior to creating an order. If this profile is set to No, a sales representative will be defaulted from the ASO: Default Salesrep profile option value. This profile can be set at all levels. ASO: View Customers Without Accounts Default Value: Yes Determines if a user can view only customers with at least one active account. If set to Yes, a user can view all sold-to/ship-to/bill-to customers. If set to No, a user can view only sold-to/ship-to/bill-to customers with at least one active account. This profile can be set at all levels.



Summary

Summary

In this module, you should have learned how to:• Define overall quote security• Distinguish between access security, function

security, and new quote security• Manually set up basic quote security for sales team

and manager access to quotes• Identify security-related profile options


Enabling Account Creation Requirements Chapter 11 - Page 1

Enabling Account Creation Requirements Chapter 11



Enabling Account Creation Requirements

Enabling Account Creation Requirements



Objectives

Objectives

After completing this module, you should be able to do the following:• Distinguish between prospects and customers• Identify account requirement options/levels• Identify related profile options



Overview of Account Creation Requirements


Quoting does not require financial accounts, for parties without any accounts, when creating a quote. Account creation requirements allow you to determine when an account is created.

Prospect CustomerAccount

=


Sales representatives can create quotes for either customers or prospects. • Customers – Have at least one financial account. • Prospects – Have no financial accounts.

Use of the account creation profile allows you to create quotes for prospects without having to create an account.



Account Creation Profile Options


The following profile option controls account creation requirements:• ASO: Auto Account Creation


ASO: Auto Account Creation Default Value: As Required Determines if an account should be automatically created when the quote is updated. If set to Always an account is created for each party on the quote (that does not have one) when you save the quote. If a new party is created, an account is created simultaneously. If set to As Required an account is created for each party on the quote (that does not have one) when the quote is web published, a new contract is initiated, or the quote is submitted to Order Management. If set to Place Order an account is created for each party on the quote (that does not have one) when the quote is submitted to Order Management. You can set this profile at the site and application levels.



Guided Demonstration - Setting Account Creation Requirement Profile Options

Responsibility: CRM Administrator, Vision Enterprises

1. Log in to Oracle Forms with the System Administrator responsibility.



3. In the Profile field, enter ASO%Auto Account%.

4. Click (B) Find.

5. In the Site column, select Always.

6. Click (I) Save.


8. Select the Quoting Sales Manager responsibility and log in to Quoting.

• (N) Quoting

9. Create a quote and select a party without an account.

10. Click (I) Save.

Notice that Quoting creates an account for the customer immediately when you save the quote.


12. Select the System Administrator responsibility and navigate back to the Profiles form.


13. In the Profile field, enter ASO%Auto Account%.

14. Click (B) Find.

15. In the Site column, select As Required.

16. Click (I) Save.




18. Select the Quoting Sales Manager responsibility and log in to Quoting.

• (N) Quoting

19. Create a Quote and select a party without an account.

20. Add products to the quote.

21. From the Overview page, select Place Order.

You receive confirmation that the order was placed. On the Overview page, you will notice that the customer now has an account number.



Summary

Summary

In this module, you should have learned how to:• Distinguish between prospects and customers• Identify related profile options• Identify the different levels of account creation

requirements


Setting Up Credit Checks Chapter 12 - Page 1

Setting Up Credit Checks Chapter 12



Setting Up Credit Checks

Setting Up Credit Checks



Objectives

Objectives

After completing this module, you should be able to do the following:• Define credit check functionality• Distinguish between internal and external credit

checks• Identify credit check related profile options• Define a credit check rule and enable internal credit

checks



Credit Check Overview


Oracle Quoting allows users to determine the credit worthiness of customers, before a quote is converted into an order, using credit checks.


Quoting provides a public API for credit checking: ASO_CREDIT_CHECK_PUB.CREDIT_CHECK. This API consists of two sections:

• Internal credit check – Based on transaction data in the quote, and historic transaction data in Oracle Order Management and Oracle Receivables.

• External credit check – Configurable by the application developer and allow users to make calls to non-Oracle applications.

The following information is mandatory for the public API:

• Header level bill-to customer, bill-to account, and bill-to address • Credit Check Rule • Quote Total • Quote Currency



Internal Credit Check Overview


• Internal credit checks are performed by the Oracle Order Management public API: OE_EXTERNAL_CREDIT_PUB.CREDIT_CHECK

• Internal credit checks require the use of credit check rules


The key differences between internal credit checking and the credit checking functionality in Oracle Order Management are:

- Item category limits are not checked in the public credit check API provided for internal credit checks.

- Credit checking is only available at the header level in internal credit checking, while OM credit checking supports both header and line level credit checks.

- There is no Holds functionality for Internal credit check



External Credit Check Overview


• External credit checks are configurable and allow users to make calls to non-Oracle applications.

• Users can write code for the pre-hook and post-hook in the Quoting public API, ASO_CREDIT_CHECK_PUB.CREDIT_CHECK, to invoke external credit checks.


Customers can write code for the pre-hook and post-hook in the Quoting public API, ASO_CREDIT_CHECK_PUB.CREDIT_CHECK. The pre-hook is executed prior to the internal credit check and the post-hook is executed after the internal credit check. Customers can use these hooks to invoke the external credit check. For user hooks to work properly, the following SQL scripts must run: asocruhk.sql – The Populate script populates data into the JTF_USER_HOOKS table. This script is run automatically. asoenuhk.sql – The Enabling script enables or disables the user hook based on the parameter passed. You must manually execute this script.



Enabling Credit Checks


Enabling credit checks involves the following tasks:

Set up credit check rules (Internal credit checks only)

Ensure that customer is set up for credit checks

Set ASO profile options



Enabling Credit Checks: Credit Check Rules

Enabling Credit Checks: Credit Check Rules

Credit Check Rules, set up in Oracle Order Management, are used when calculating a customer’s outstanding credit balance.

Credit Check Rules

The credit check rule definition allows you to determine if freight and special charges are included in credit checks. The quote total passed to OM is based on the setting of the credit check rule. There are two flags available when you set the credit check rule:

• Include Freight and Special Charges • Include Tax

Note: Credit check rules must be set up at the order level, not the line level. When setting up credit check rules, ensure that each rule has a Credit Check Level of Sales Order.



Guided Demonstration - Defining Credit Check Rules

Responsibility: Order Management Super User, Vision Operations

1. Log in to Oracle Forms (ebusiness/welcome) with the Order Management Super User responsibility.

2. Navigate to the Credit Check Rules window.

• (N) Setup > Credit > Define Credit Check Rules

3. Name your rule XXCredit Check Rule.

4. Set the Credit Check Level to Sales Order.

5. Set the Credit Hold Level to Sales Order.

6. Set the Conversion Type to Corporate.

7. In the Exposure tab, deselect Use Pre-Calculated Exposure.

8. Select the following checkboxes: − Include Open Receivables Balance − Include Payments at Risk − Include Uninvoiced Orders − Include Freights and Special Charges − Include Tax

9. Click (I) Save.



Enabling Credit Checks: Profile Options

Enabling Credit Checks: Profile Options

The following profile options must be set to enable web publishing:• ASO: Enable Credit Check• ASO: Credit Check Rule

ASO: Enable Credit Check

Default: <none> Determines if credit check functionality is enabled. If set to No, the Initiate Credit Check option will not be available. This profile options can be specified at the site and application levels. ASO: Credit Check Rule Default: <none> Determines the credit check rule used for performing internal credit checks. If not set, internal credit checks cannot be performed. This profile option can be specified at the site, application, and responsibility levels.



Guided Demonstration - Enabling Credit Checks

Responsibility: Receivables, Vision Operations

Setting up Customers for Credit Checks

1. Log in to Oracle Forms (ebusiness/welcome) with the Receivables responsibility.

2. Navigate to the Find/Enter Customers form.

• (N) Customers > Standard

3. Type Bus% in the Customer Name field.

4. Click (B) Find.

5. Select BusinessWorld with account #1608 and click (B) OK.

6. Navigate to (T) Profile : Transaction. In the Credit section, select the Credit Check checkbox.

7. Navigate to (T) Profile : Amounts. In the Curr column, select USD.

8. Enter the following information Currency Rates and Limits section: − Credit Limit = $1,000,000 − Order Credit Limit= $10,000

9. Click (I) Save.

10. Navigate to (T) Addresses.

11. Select the following address:

2391 L Street, San Jose, Santa Clara, CA, 95106, United States

The Customer Addresses form displays information about the selected address.

12. Navigate to (T) Profile : Transaction. In the Credit section, select the Credit Check checkbox.

13. Navigate to (T) Profile : Amounts. Select USD in the Curr column.

14. Enter the following information in the Currency Rates and Limits section: − Credit Limit= $1,000,000 − Order Credit Limit= $10,000

15. Click (I) Save.



16. Close the form.

Setting Profile Options

17. Log in to Forms as System Administrator.



19. Enter ASO%Credit%Check% in the Profile field and select Find.

20. Enter the following information: − ASO: Credit Check Rule = XXCredit Check Rule (the one you created in the

previous demo) − ASO: Enable Credit Check = Yes

21. Click (I) Save.

22. Log in to Quoting.

23. Find a quote that has a total of more then $10,000.

24. From the Actions menu, select Initiate Credit Check > Go.

The credit check will fail because you have exceeded the Order Credit Limit. You will receive the following error:

Credit Check has failed.

Credit check failed. Transaction limit exceeded. Using customer credit profile.



Practice - Enabling and Initiating Credit Checks

Overview

This practice teaches users how to enable and initiate.

Assumptions


• Receivables, Vision Operations


Tasks


Log in to Oracle Forms as the Receivables Manager to enable credit checks.

Initiating Credit Checks

Log in to Oracle Quoting as a Quoting Sales Agent to initiate credit checks.



Solution – Enabling and Initiating Credit Checks


Responsibility = Receivables, Vision Operations

1. Log in to Oracle Forms (ebusiness/welcome) with the Receivables responsibility.

2. Navigate to the Find/Enter Customers form.

• (N) Customers > Standard.

3. Type Bus% in the Customer Name field.

4. Click Find.

5. Select Business World with account # 1608 and click OK.

6. Navigate to the Profile : Transaction tab. In the Credit section, select the Credit Check checkbox.

7. Navigate to the Profile : Amounts tab. In the Curr column, select USD.

8. Enter the following information in the Currency Rates and Limits section: − Credit Limit = $1,000,000 − Order Credit Limit= $1,000,000

9. Click (I) Save.

10. Navigate to the Addresses tab.

11. Select the following address:

2391 L Street, San Jose, Santa Clara, CA, 95106, United States

The Customer Addresses form displays information about the selected address.

12. Navigate to the Transaction > Profiles tab. In the Credit section, select the Credit Check checkbox.

13. Navigate to the Transaction > Amounts tab. Select USD in the Curr column.

14. Enter the following information in the Currency Rates and Limits section: − Credit Limit= $1,000,000 − Order Credit Limit= $1,000,000

15. Click (I) Save.



16. Close the form.

Initiating a Credit Check

17. Switch responsibilities (M) File > Switch Responsibility to Quoting Sales Agent.

18. Create a quote.

19. From the Actions menu, select Initiate Credit Check > Go.

You should receive confirmation that the credit check passed.



Summary

Summary

In this module, you should have learned how to:• Distinguish between internal and external credit

checks• Identify related profile options• Define credit check rules• Enable credit checking functionality


Setting Up Web Publishing Chapter 13 - Page 1

Setting Up Web Publishing Chapter 13



Setting Up Web Publishing





Objectives

Objectives

After completing this module, you should be able to do the following:• Define Web publishing• Explain the Web publishing process flow for both

sales reps and customers• Identify Web publishing related profile options• Assign required roles for B2B users• Publish a quote to a seeded specialty store



What is Web Publishing?


• Web publishing is the act of electronically sharing a quote, created by a Salesrep, with a customer through the iStore interface.

• The goal of the web publishing is to allow a salesrep to execute paperless, real-time sharing of quotes with a customer, thereby leveraging integration between Quoting and the iStore web storefront.


A quote version may be web published if it meets all of the following conditions: • The user has update access to the quote. • It is the highest version of the quote. • The quote is not in Ordered Submitted or Inactive status. • The quote is not expired. • If the customer is an organization, a contact has been specified. • There is at least one specialty store in which the quote can be web published.

If a web published quote does not meet all of the aforementioned criteria after it is web published, the Publish flag still indicates that it is web published, but it will not show up in the customer facing UI.



Web Publishing Process Flow - Salesrep

Web Publishing Process Flow - Salesrep

Org

Person

No

Yes

Yes

No

e-mailnotification

Select orcreateemail

address

Enter username

Selectquote_tocontact

Selectspecialty

store

2

3

4 5

Salesrepcommences

web publishing

1

Is the customeran organization

or a person?

Does the quoteversion have a

quote-to contact?

Is the customer or

contactan FND_USER?

Process Flow - Sales Rep

A salesrep has the option of electronically sharing a quote version with the customer by web publishing the quote. 1. If the sold-to customer is of type person, the quote version is web published to him/her. If the sold-to customer is of type organization, the quote version is web published to the sold-to contact. 2. The quote-to customer/quote-to contact must be an FND_USER to access the web published quote version through the iStore web storefront. 3. If the quote-to customer/quote-to contact is not an FND_USER, the salesrep can create an FND_USER for the sold-to customer/sold-to contact by entering a username when attempting to publish a quote. The system auto-generates a password for the FND_USER. If the FND_USER created in this manner is for the sold-to customer, it will be as a B2C user. If the FND_USER created in this manner is for the sold-to contact, it will be as B2B user. Note: FND_USER created must be assigned the default responsibility for the iStore application. If a B2B user is created, s/he must be assigned the role.



4. Prior to web publishing the quote version, the salesrep also has to select a specialty store in which the quote version should be web published and an e-mail address to which all notifications should be sent. The selected specialty store ID is stored in the quote header. 5. After a quote version is web published, the quoting application sends an e-mail to the quote-to contact/customer with instructions on accessing the web published quote version. If the FND_USER was created, an additional e-mail notification is sent to the sold-to contact/customer with the appropriate details. Pre-conditions

• The user must have Update access to the quote. • The web publish action is permitted. Thus, the quote must be the highest version, not in

Order Submitted or Inactive status and not expired. • If the sold-to customer is of type organization, there must be a sold-to contact specified. • There is at least one specialty store in which the quote version can be web published. • The profile option ASO: Enable Web Publishing must be set to Yes at the appropriate

level. Post-conditions The quote version is web published and visible to the quote-to customer/quote-to contact through the iStore web storefront as long as it remains the highest version, is not changed to a status of Order Submitted or Inactive and does not expire.



Web Publishing Process Flow - Customer

Web Publishing Process Flow - Customer

Modifypayment

information

No

Yes

Yes

No

Customerreceives

emailnotification

Placeorder

Yes

No

Exit

Accessweb

publishedquote

Contactsalesrepto modify

quote

Submitquote asorder?

1

ModifyQuote?

2

Modifypayment

informationonly?

34

5

Process Flow - Customer

1. When a quote version is web published the customer or contact receives an email notification with instructions for how to access the web published quote. 2. After reviewing the web published quote version, the customer/contact may wish to modify it. 3. The customer/contact can modify the payment information only. 4. For additional modifications, the customer/contact can notify the Salesrep (who can modify the web published quote version). 5. Alternately, the customer may be satisfied with it and wish to place it as an order.





Web publishing setup involves the following tasks:• Set ASO and IBE profile options• Set up an iStore specialty store• Set up B2B users to view quotes



Setting Up Web Publishing: Profile Options

Setting Up Web Publishing: Profile Options

The following profile options must be set to enable web publishing:

ASO: Enable Web Publishing

IBE: iStore Non Secure URL

ASO: Enable Web Publishing Default: No Determines if web publishing functionality should be enabled in Quoting. This profile option can be specified at the site and application levels. IBE: iStore Non Secure URL Default: <none> This profile option specifies the base URL for the non-secure server (HTTP protocol). The profile option value must have the following syntax: http://<host>:<port>/OA_HTML If the profile option is not set, switching between HTTP and HTTPS protocols is not possible. Note: If you are using the HTML UI and are integrated with Oracle Sales Online, you must set the IBE: iStore Non Secure URL at the Application level for the application Oracle Field Sales. If you are not integrated with OSO, the profile should be set at the Application level for Oracle Quoting.



Setting Up Web Publishing: iStore Requirements

Setting Up Web Publishing: iStore Requirements

Web publishing functionality in Quoting has the following iStore requirements:• You must have at least one specialty store set up to

publish quotes.• Web published quotes must be published in

specialty stores that do not have access restrictions (i.e., those specialty stores that are not restricted by responsibility or party).



B2B User Setup for Web Publishing

B2B User Setup for Web Publishing

The following roles must be assigned to iStore business users in order for these users to view quotes on a web store:• IBE_PRIMARY_USER_ROLE• IBE_BUSINESS_USER_ROLE

Once these roles have been assigned to the business user type, any user created as a business user will have the required roles.



Guided Demonstration - Creating and Publishing a Quote

1. Set the appropriate profile options: − ASO: Enable Web Publishing is set to Yes − IBE: iStore Non Secure URL is set to iStore URL at the application level

2. Log in to Quoting through the CRM HTML Login page using the login (Ljones/welcome).

3. Navigate to the Quote tab.

4. Select (B) Create Quote.

5. Enter the following information: − Quote Name: PublishedQuote − Customer: BusinessWorld − Account: 1608 − Contact: Andre Beaulie

6. Select (B) Apply.


8. Add AS54888 to your quote.

9. Navigate to the Overview page.

10. Select Actions > Web Publish Quote > Go.

11. Enter a username.

Explain that if the customer is not an FND_USER, you will be prompted to enter a user name. The system then auto generates a password and creates an FND_USER for the customer. This information is then emailed to the customer.

12. Select the store to which the quote will be published.

The Specialty Store ID will be stored in the quote header.

13. Choose to send the notification email to an existing address.

Explain that FND_USER information and all notifications will be sent to this email address.

14. Optionally, enter comments and select (B) Submit.

In the Overview page, you receive confirmation that the quote was published.

15. Log out of Oracle Quoting.



Practice - Creating and Publishing a Quote

Overview

This practice teaches users how to create and publish new quotes.

Assumptions




Tasks


Log in to Oracle Forms as the Quoting Sales Manager, to create and publish quotes.



Solution – Creating and Publishing Quotes

Creating and Publishing Quotes


1. Set the appropriate profile options: − ASO: Enable Web Publishing is set to Yes − IBE: iStore Non Secure URL is set to iStore URL at the application level


3. Navigate to the main Quoting form.

• (N) Quoting

4. Create a basic quote. Select Create Quote.

5. Enter the following information: − Quote Name: XXPublishedQuote − Customer: BusinessWorld − Account: 1608 − Contact: Andre Beaulie

6. Select Apply.

7. Select Add Product.

8. Add AS54888 to your quote.

9. Navigate to the Overview page by selecting the Overview link in the left side bar.

10. Select Web Publish Quote from the Actions menu and select Go.

11. If the customer is not an FND_USER, you will be prompted to enter a user name. The system auto generates a password and creates an FND_USER for the customer. The information is then emailed to the customer.

12. Select the store to which the quote will be published.

The Specialty Store ID will be stored in the quote header.

13. Choose to send the notification email to the existing address.

14. Optionally, enter comments and select Submit.

In the Overview page, you receive confirmation that the quote was published.



15. Log out of Oracle Quoting.



Summary

Summary

In this module, you should have learned how to:• Define Web publishing• Explain the Web publishing process flow for both

sales reps and customers• Identify Web publishing related profile options• Assign required roles for B2B users• Publish a quote to a seeded specialty store


Setting Up Approvals Chapter 14 - Page 1

Setting Up Approvals Chapter 14



Setting Up Approvals

Setting Up Approvals




Objectives

Objectives

After completing this module, you should be able to do the following:• Describe the modules that provide approvals

functionality to Quoting• Explain the approvals process flow• Describe the process and tasks required to

implement approvals functionality in Quoting• Specify jobs for employees and assign approval

authority to jobs• Identify approvals-related profile options• Identify approvals-related concurrent programs• Identify required quote status transition• Create an approval rule in OAM



Approvals Overview

Approvals Overview

Quoting integrates with Oracle Approvals Management (OAM) and Oracle Workflow to provide quote approval functionality. • OAM stores and processes information on rules related

to quote approvers. OAM determines situations requiring approvals and obtains a list of required approvers

• Oracle Workflow enables automated notification and response gathering from approvers identified by OAM

Approver 1 Approver 2 Approver 3



Approvals Process Flow


1

Approval Initiated

6

Quote status updated

5Quote

traverses approval hierarchy

4

Workflow notifications

sent

3

Quote status updated

7

Order placed or quote revised

2

Approver list determined


1. The salesrep creates a quote and selects “Initiate Approvals” from the Quoting application. OAM processes the request and returns a list of approvers and any applicable rules. 2. While processing the request, Quoting checks the value of the “Allow Skip Approvers” profile option to determine whether a full or partial list of approvers is required. If the approver list is empty, then either the quote does not require approval or the salesrep has sufficient authority to approve the quote. With Oracle Contracts integration, the salesrep can also indicate whether a non-standard contract is required for the quote by selecting the appropriate checkbox in the Initiate Approval Form. 3. Quoting updates the quote status to Approval Pending, Approved, or Contract Required depending on the scenario. 4. Integration with Oracle Workflow enables notifications to be sent to the first/next approver on the list. 5. If a quote is approved, then it is automatically sent to the next approver in the hierarchy. 6. If the quote is approved by all approvers then its status is changed to “Approved” unless the salesrep or quote conditions require a non-standard contract. In this case the status is changed



to “Contract Required.” If the quote is rejected by an approver, then the quote status is changed to “approval rejected.” 7. Quotes in “Approved” status can then be submitted as orders. If the quote was rejected, the salesrep can view the reason, revised the quote appropriately and begin the approval process again.



Approvals Functionality


Approval functionality includes:

Tight integration with Quoting –Quote attributes basis of approval

rules

Enforcement of business rules

Ability to commence approval process at a specified level

Dynamic calculation of approvers against any org hierarchy


Note: See the Oracle Quoting Implementation Guide for a complete list of seeded OAM attributes that can be used to set up OAM approval rules for Quoting.



Approval Setup Process Flow

Approval Setup Process FlowHR

Create employee1 Assign

job/approval authority

2

CRM Resource ManagerCreate or

assign roles and role types

5 Import resources and associate with role/role type

6 Create group and assign usage7

Sys Admin

Start concurrent processes

10

OAM

Create conditions and rules

8

Create user ID

/assign responsibilities

Sys Admin3 Set

profileoptions

4

Create status

transitions

9

Quoting

Approval Setup Process Flow

Approval setup involves several tasks across several E-Business Suite modules. The diagram above illustrates the steps and the application or responsibility required to complete each task. 1. Using the HR application, an employee is created. In addition to HR-required data, approvals requires an email address (to be used for notifications). 2. Once the employee is created in the system, additional employee assignment data can be entered via the Assignment button on the employee form. Required approvals data includes:

• Organization • Job • Grade

Approval authority level for specific job is also set in the HR application module. 3. The employee must be assigned a unique user ID and password via the System Administrator responsibility. In addition to Quoting responsibilities, the user setting up approvals must have OAM and Workflow responsibilities assigned. 4.System profile options must be set to enable approvals functionality



5. Using the CRM Resource Manager responsibility, you must either create or assign role type for Quoting (i.e., Quoting) and a role for the role type (i.e., Quoting Manager or Quoting Agent). 6. The user must be set up as a resource in the system by importing resources and associating the resource with the user name. You must also associate the newly created resource with the role and a role type previously created. 7. A CRM Resource Manager group must be defined and resources are then added to the group. For each member of the group, you assign a role type and role by clicking the Member Roles button. You must also assign the usage type of “Sales and Telesales” for the group via the Usages tab. You can use the Parent or Child Group tabs to establish group hierarchies, if desired. 8. Via Self-Service login, OAM module is accessed. Here you create conditions and rules that are used by the approvals engine. 9. Using the Quoting Sales Manager responsibility in Quoting, you must set up quote status transitions required by approvals. 10. Once approval rules are created in OAM, you again log in as System Administrator to ensure that required concurrent programs are running. These programs ensure that workflow processes are running and that notifications can be sent.



Guided Demonstration - Specifying Jobs and Approval Authority

Responsibility: HRMS Management

1. Log in to Oracle Forms (ebusiness/welcome) using the HRMS Management responsibility.

2. Navigate to the Find Person page.

• HRMS Manager > People > Enter and Maintain.

3. Enter an existing employee number and select (B) Find.

4. Click (B) Assignment. Enter the following information: − Organization = Vision Corporation − Job = Enter a job that corresponds with the employee’s position in the organization

(i.e., sales rep, manager, vice president, etc.) − Grade = Select a grade that is valid for the job

5. Close all open forms and return to the navigator.

6. Select (N) Work Structures > Job > Description.

7. Query for the job name (e.g., sal600) you’ve specified for an employee.

The Approval Authority for this job is 1. You can enter a different approval authority level (1-10). Do not change the approval authority at this time.

Approval authority levels are denoted by an integer between one and ten. Employee hierarchy, jobs, grades, and approval authorities should be decided and setup in advance. The higher the integer, the more authority associated with a given job.

8. Click (I) Save.



Guided Demonstration - Adding Responsibilities for Approvals


1. Log in to Oracle Forms (ebusiness/welcome) using the system administrator responsibility.

2. Navigate to the Define Users page.

• Security > User > Define.

3. Search for a user you previously created and add the following responsibilities: − Workflow Administrator, Vision Enterprises − Approvals Management Application Administrator

4. Click (I) Save.



Practice - Specifying Jobs and Approval Authority

Overview

This practice teaches users how to specify approval authority for a sales representative.

Assumptions


• HRMS Management


Tasks

Specifying Jobs and Approval Authority

Log in to Oracle Forms as the HRMS Management responsibility to specify jobs and approval authority.



Solution – Specifying Jobs and Approval Authority

Specifying Jobs and Approval Authority



2. Navigate to the Find Person page.

• HRMS Manager > People > Enter and Maintain.

3. Enter the employee number for the employee you created and select (B) Find.

4. Click (B) Assignment. Enter the following information: − Organization = Vision Corporation − Job = Enter SAL600.Sales Representative − Grade = Select 500.2.West

5. Save your work.

6. Close all open forms and return to the navigator.

7. Select (N) Work Structures > Job > Description.

8. Query for the job name (SAL600.Sales Representative) you specified for the employee.

9. Enter an approval authority level (1-10).

Approval authority levels are denoted by an integer between one and ten. Employee hierarchy, jobs, grades, and approval authorities should be decided and setup in advance. The higher the integer, the more authority associated with a given job.

10. Click (I) Save.



Setting Profile Options for Approvals


The following profile options must be set or verified for Approvals functionality:

ASO: Enable Approvals

ASO: Allow Skip Approvers


ASO: Enable Approvals Default: Yes Determines if approvals functionality is enabled in Quoting. This is not a mandatory profile option. This profile option can be specified at the site and application levels.

ASO: Allow Skip Approvers Default: No Determines if the salesrep has the ability to skip approvers. If set to Yes, then prior to initiating the approval process, salesreps can choose to shorten the approval process by specifying which approver is the starting point for the approval process. This functionality does not allow salesreps to “pick and choose” approvers but rather it expedites the process if the quote was previously approved by lower levels and rejected by a higher level approval authority. In this case, the salesrep may want to may the appropriate changes and send the revised quote directly to the authority level that originally rejected the quote. This is not a mandatory profile option. This profile option can be specified at the site and application levels.



Understanding OAM Rules for Approvals


RuleApproval Type(e.g., “approval required

up to level 10”)

Condition 1 Condition 2AND + =

Attribute 1

Attribute 2

Attribute 3

Attribute 4

OAM Seeded Quote Attributes(e.g., quote total, customer, etc.)


In OAM, a situation or rule requiring approval is defined through the use of attributes, conditions, and approval type. Each application integrating with OAM must seed the desired attributes. For example, the Quoting application seeds “Quote Total” as an attribute. (See the Oracle Quoting Implementation Guide for a complete list of seeded attributes.) Attributes are then used to define conditions. For example, a condition using the quote total attribute may be “Quote Total > = $10,000.” An approval type determines the approvers to be obtained. These may be dynamic (e.g., “obtain all supervisors up to Level 10,” “obtain three levels of supervisors,” etc). or these may be static (e.g., “obtain approval from John, Sales Manager, and Jill, Regional Sales Manager). One or several conditions and an approval type constitute a rule. Multiple conditions in a rule are always applied using the AND operator. Multiple rules, on the other hand, are applied using the OR operator. For example, assume there are two conditions. The first one being “Quote Total >=$10,000,000” and the second one being “Manual Discount Percentage >=10”. If these two conditions are in the same rule, it will be applied only in the situation where BOTH of the conditions are satisfied. However, if the conditions are in separate rules, they will be applied in situations where EITHER of them hold true.



If multiple rules are invoked, the approvers are combined and ranked in sequence to determine the list of approvers for the entire object. If the approvers are obtained by traversing the HRMS hierarchy, they are ranked by job level. For additional information on the logic for combining and ranking approvers, refer to the OAM User Guide. Note: Salesreps and approvers do not have to be set up as employees in HRMS tables. However, they do all need to be FND_USERs. Salesreps and approvers need to be set up as employees only if using seeded OAM logic, which is only against the HRMS tables, for traversing a hierarchy. However, the OAM infrastructure allows each installation to write its own logic to traverse any hierarchy in any table. This logic is stored in a handler. See OAM documentation for additional details on writing custom handlers. Nevertheless, the implicit assumption is that a salesrep is set up either as a resource in JTF Resources or as an employee in HRMS tables. Thus, when displaying the name of the approver and the requester in the Quoting application, the name will be derived from HRMS tables, if an employee, else from JTF Resources.



Guided Demonstration - Creating Rules for Approvals

Responsibility: Approvals Management Application Administrator

1. Launch the Self Service Applications login page.

2. Login with user ID/pwd created for a user assigned the Approvals Management Application Administrator responsibility.

3. Click (H) Approvals Management Application Administrator.

4. Click (H) Approvals.

5. Click (T) Conditions.

6. Choose Oracle Quoting from the Transaction Type pull-down menu and click (B) Continue.

7. Click (B) Add a Condition.

8. Select the Ordinary Header condition type and then click (B) Continue.

9. Select Quote Total from the list of attributes and then click (B) Continue.

10. Specify the following: − Currency Code = USD − Lower limit = 0 − Upper limit = 10000 − Include both the lower and upper limit.

11. Click (B) Create Condition.

12. Click (T) Rules

13. Choose Oracle Quoting from the Transaction Type pull-down menu and click (B) Continue.

14. Click (B) Add Rule and Usage. − Description: enter text that describes the nature of the rule (i.e., QT 0-10K). − Rule Type: Select list-creation rule − Start Date/End Date: Use today’s date as the start date and “none” as the end date.

15. Click (B) Continue.

16. Select the Chain of authority based on absolute job level radio button and then click (B) Continue.

Explain that the chain of approval will stop at the highest job level you define in Oracle Human Resources.



17. Select an appropriate approval level based on your approval hierarchy setup. Click (B) Continue.

18. Select Quote Total as the Ordinary -Condition Attribute and then click (B) Continue.

19. Check the condition you created as the Ordinary Condition and then click (B) Continue. The rule is created.

Explain that now when you create a quote with a USD amount between 0K and 10K and you initiate the approval process, you will see a list of approvers that must approve the quote before you can place an order.



Practice - Creating Rules for Approvals

Overview

This practice teaches users how to create rules for approvals.

Assumptions


• Approvals Management Application Administrator


Tasks

Creating Rules for Approvals

Log in to Self Service Applications to create rules for approvals.



Solution – Creating Rules for Approvals

Creating Rules for Approvals

Responsibility = Approvals Management Application Administrator

1. Launch the Self Service Applications login page.

2. Login with user ID/pwd created for a user assigned the Approvals Management Application Administrator responsibility.

3. Click the Approvals Management Application Administrator hyperlink.

4. Click the Approvals hyperlink.

5. Click (T) Conditions.

6. Choose Oracle Quoting from the Transaction Type pull-down menu and click Continue.

7. Click (B) Add a Condition.

8. Select the Ordinary Header condition type and then click (B) Continue.

9. Select Quote Total from the list of attributes and then click (B) Continue.

10. Specify the following: − Currency Code = USD − Lower limit = 0 − Upper limit = 5000 − Include both the lower and upper limit.

11. Click (B) Create Condition.

12. Click (T) Rules

13. Choose Oracle Quoting from the Transaction Type pull-down menu and click Continue.

14. Click (B) Add Rule and Usage. − Description: Enter XX QT 0-5K. − Rule Type: Select list-creation rule − Start Date/End Date: Use today’s date as the start date and “none” as the end date.

15. Click (B) Continue.

16. Select the radio button for the Approval Type: chains of authority based on absolute job level and then click (B) Continue.



Explain that the chain of approval will stop at the highest job level you define in Oracle Human Resources.

17. Select Require approvals up to at least level 1 from the Approval drop-down menu. Click (B) Continue.

18. Select Quote Total as the Ordinary-Condition Header Attribute and click (B) Continue.

19. Select the condition you created as the Ordinary Condition and then click (B) Continue. The rule is created.

Explain that now when you create a quote with a USD amount between 0K and 5K and you initiate the approval process, you will see a list of approvers that must approve the quote before you can place an order.



Setting up Quote Status Transitions for Approvals


Approvals requires that approvals-related quote status transitions are setup. These transitions are not seeded.


Verify that the following quote status transitions are set up and enabled: • Draft to Approval Pending • Approved to Order Submitted • Approval Rejected to Approval Pending • Approval Canceled to Approval Pending

See the Quote Status and Quote Status Transitions module of this course for details on completing this task.



Concurrent Programs

Concurrent Programs

Make sure the following concurrent programs are up and running:

Workflow Background Process

Notification Mailer

Concurrent Programs

Running these concurrent programs ensures that emails and notifications are sent to the appropriate approvers. For information on running concurrent programs, see the Oracle Applications System Administrator’s Guide.



Summary

Summary

In this module, you should have learned how to:• Describe the modules that provide approvals

functionality to Quoting• Explain the approvals process flow• Describe the process and tasks required to

implement approvals functionality in Quoting• Specify jobs for employees and assign approval

authority to jobs• Identify approvals-related profile options• Identify approvals-related concurrent programs• Identify required quote status transitions.• Create an approval rule in OAM


Setting Up Sales Supplement Templates Chapter 15 - Page 1

Setting Up Sales Supplement Templates Chapter 15



Setting Up Sales Supplement Templates

Setting Up Sales Supplement Templates




Objectives

Objectives

After completing this module, you should be able to do the following:• Describe the purpose of sales supplements• Explain the sales supplement template structure• List profile options related to sales supplement

functionality• Create and view a sales supplement template



What are Sales Supplements?

What are Sales Supplements?

A sales supplement contains additional structured data that can be captured in Quoting’s HTML UI. Some examples include:• Competitive information• Key selling points

What are Sales Supplements

Since sales supplement data is structured, you can run approval rules against it and incorporate sales supplement data into business processes. Sales supplement data is like an extension of flexfields without the column limit and with greater display options. Sales supplement data and template mappings are stored in the ASO schema. Note: This information is NOT passed to Order Management.



Sales Supplement Templates


Sales supplement templates are configurable content templates that can be set up to capture additional quote-related information based on business requirements.


• Sales supplement templates are set up in Forms for use in Quoting’s HTML UI • Each template is composed of re-usable “building blocks” • Multiple templates may be created • You cannot delete templates, selections, components, or responses. • Once you apply a template to a quote it cannot be changed.



Sales Supplement Template Structure


Sections

Component(Note/Header/Footer)

Responses(Pre-defined)

DefaultPre-definedResponses

Pre-definedResponses

Templates

Component(Question)

InstructionsResponses(Number/

Date/Currency/Text)

Display Style


A sales supplement template is composed of one or more sections. The same sections may be reused in multiple templates. Thus, template - section mappings are stored. A section is composed of multiple components. Since the same components may be reused in different sections, section - component mappings are also stored. There are four component types:

• Note • Header • Footer • Question

The first three are rendered as text. “Question” component types, are rendered as component - response pairs. Question component types can have Responses of types:

• Date • Number • Currency



• Text • Predefined Responses

The first four accept user-entered responses only. For these, component - response type - instruction text mappings are stored. Response type “Predefined” mandates that the response be chosen from a predefined selection. To allow the flexibility of the same predefined response (e.g., Yes/No) to be used with multiple components, component - response type -predefined response - instruction text mappings are stored. Note: The Response Type field is enabled only if the component type is Question. Responses are enabled if Response Type is Question. A component of component type “Question” and response type “Predefined Response” must have a default presentation or display style. There are four types of display styles:

• List of Values • List of Values with Blank • Radio Group • Checkbox

Note: You can specify a default value along with the presentation style. The default value is optional except when the presentation style is List of Values. Note: You must manually query each tab in the Sales Supplement form. The tabs are not automatically queried, each tab behaves as a standalone tab. Sales supplement templates are created in reverse order. That is, responses are created first, then components, followed by sections and ultimately the template.



Guided Demonstration - Setting Up a Sales Supplement Template


1. Set the appropriate profile options:

ASO: Enable Sales Supplement is set to Yes

2. Log in to Oracle Forms using the Quoting Sales Manager responsibility.

3. Navigate to the Sales Supplement Setup Form.

• (N) Quoting > Setup > Sales Supplements

4. Click (T) Responses.

Explain that you create sales supplements in reverse order: starting with the Responses and finishing with the Templates.

5. In the Response Name field, enter the following responses on separate lines: − 0K to 10K − 10K to 50K − 50K to 100K − 100K or more

6. Click (I) Save.

Note: You must save your work in each tab of the Sales Supplement Setup Form before proceeding to the next step.

7. Click (T) Components. In the Components region, enter the following information (you must scroll to the right to view all fields):

− Name = Quarterly IT Spending − Component Type = Question − Response Type = Predefined − Instruction = How much money does the customer plan to spend IT this quarter?

The Name and the Instructions you enter appear in the UI.

8. Place your cursor in the Sequence field of the Responses region. The sequence field determines the display order of your Reponses. You must manually enter the sequence and use the LOV to enter your predetermined responses.

9. Enter the following information on separate lines: − Sequence = 1; Response = 0K to 10K − Sequence = 2; Response = 10K to 50K − Sequence = 3; Response = 50K to 100K



− Sequence = 4; Response = 100K or more

10. Click (I) Save.

11. Click (T) Sections.

In the Section region, enter Planned Spending as the section name. This name is visible in the UI.

In the Components region, enter the following information: − Sequence = 1 − Component Name = Quarterly IT Spending − Presentation Style = Radio Group − Default Value = 0K to 10K

12. Click (I) Save.

13. Click (T) Templates.

14. In the Template region, enter a name for your template. This name is visible in the UI.

15. In the Sections region, enter 1 in the Sequence field and use the Name LOV to add the Planned Spending section you created.

16. Click (I) Save. Your template and template mappings are saved.

17. Log in to the Quoting HTML UI.

18. Select a quote and navigate to the Sales Supplement page. Use the drop-down to view your template.



Practice - Setting Up a Sales Supplement Template

Overview

This practice teaches users how to set up a sales supplement template.

Assumptions




Tasks

Setting Up a Sales Supplement Template

Log in to Oracle Forms as the Quoting Sales Manager, to set up sales supplement templates.



Solution – Setting Up a Sales Supplement Template

Setting Up a Sales Supplement

Responsibility = Customer Support, Vision Enterprises

1. Set the appropriate profile options: − ASO: Enable Sales Supplement is set to Yes

2. Log in to Oracle Forms using the login you created earlier.

3. Navigate to the Sales Supplement Setup Form.

• (N) Quoting > Setup > Sales Supplements.

4. Click (T) Responses.

5. In the Response Name field, enter the following responses on separate lines: − 0K to 10K − 10K to 50K − 50K to 100K − 100K or more

6. Click (I) Save.

Note: You must save your work in each tab of the Sales Supplement Setup Form before proceeding to the next step.

7. Click (T) Components. In the Components region, enter the following information (you must scroll to the right to view all fields):

− Name = Quarterly IT Spending − Component Type = Question − Response Type = Predefined − Instruction = How much money does the customer plan to spend IT this quarter?

The Name and the Instructions you enter appear in the UI.

8. Place your cursor in the Sequence field of the Responses region. The sequence field determines the display order of your Reponses. You must manually enter the sequence and use the LOV to enter your predetermined responses.

Enter the following information on separate lines: − Sequence = 1; Response = 0K to 10K − Sequence = 2; Response = 10K to 50K − Sequence = 3; Response = 50K to 100K − Sequence = 4; Response = 100K or more



9. Click (I) Save.

10. Click (T) Sections.

In the Section region, enter Planned Spending as the section name. This name is visible in the UI.

In the Components region, enter the following information: − Sequence = 1 − Component Name = Quarterly IT Spending − Presentation Style = Radio Group − Default Value = 0K to 10K

11. Click (I) Save.

12. Click (T) Templates.

In the Template region, enter XXPlannedSpending as the name for your template. This name is visible in the UI.

In the Sections region, enter 1 in the Sequence field and use the Name LOV to add the Planned Spending section you created.

13. Click (I) Save. Your template and template mappings are saved.

14. Log into the Quoting HTML UI.

15. Select a quote and navigate to the Sales Supplement page. Use the drop-down to view your template.





The following profiles options must be set for sales supplements:

ASO: Enable Sales Supplement

ASO: Default Sales Supplement Template


ASO: Enable Sales Supplement Default: No Setting this profile option to Yes enables use of Sales Supplement. It can be set at the site and application levels. ASO: Default Sales Supplement Template Default: <none> This profile option determines the default template that will be used by the Quoting (HTML) application. It can be set at all levels. You can use the procedure “Disabling Sidebar Menu Functionality” to remove the Sales Supplement link from the UI. The sidebar menu in the HTML UI is not dynamically rendered. To disable optional functionality, the related profile must be set to No. You can then remove the relevant links from the sidebar menu. Disabling of functionality is global and will affect all users. You must log out and bounce the web server for the changes to take effect.



Summary

Summary

In this module, you should have learned how to:• Describe the purpose of sales supplements• Explain sales supplement template structure• List profile options related to sales supplement

functionality• Create and view a sales supplement template


Setting Up Print Quote Chapter 16 - Page 1

Setting Up Print Quote Chapter 16



Setting Up Print Quote





Objectives

Objectives

After completing this module, you should be able to do the following:• Describe printed quote format options, layout, and

contents• List print quote setup tasks and related profile

options• Describe customizations and personalizations that

can be done to print quote reports• Add a new print quote report template to Quoting

lookups• Add a company logo to a print quote report



Print Quote Overview


Printed (hardcopy) quotes are often required when customers need to physically sign the quote to make the agreement legally binding.


Sales supplement (HTML UI) data is not printed.



Formats and Layout

Formats and Layout

• Quoting can generate the following printable file formats:– Adobe Portable Document Format (PDF)– Rich Text Format (RTF)

• The seeded page layout is landscape orientation (US letter and A4).

Formats and Layouts

The quote printout is similar in layout and content regardless whether initiated from the Forms or HTML UI – the exception being that you can print Header Attachments from HTML and you can print both Header and Line attachments from Forms. Oracle Reports Server can provide XML output for print quote data; however, XML applications that receive this output must be custom built.



Printed Quote Content


Printed versions of a quote include the following content:

Charges

Attachments

Quote and Customer information

Line information

Configurations for model products

Service Products

Pricing information


Quote Information – quote number, revision, date, expiration date, header level payment terms Customer information – Customer name, address, email address, and phone number; ship-to customer name, address and phone number; bill-to customer name, address, and phone number Pricing Agreement Information – Agreement name number, revision, and revision date Line information – Product number, description, UOM, QTY, Unit Net Price, Total Net Price, Sales Tax, Total price for model products. Attachments – Text type header attachments that are associated with the document category Miscellaneous Configurations for model products – Line number, product and description, UOM, Quantity are printed for each component. Charges – Quote line level charges and a summary of charges for entire quote Service products – Start date, end date, period, duration, service item reference information A quote is executable if there is a valid transition from the current status to “Order Submitted” status.



What information is available in a non-executable Quote? The non-executable Print Quote report displays key information available to you in the Oracle Quoting – HTML UI in addition to a customized disclaimer.

• Quote information • Customer information • Pricing Agreement Information • Line information • Attachments • An executable Quote has the following additional information: • Contract Information • Signature Block

For more information see the Oracle Quoting User Guide.



Executable vs. Non-executable


A quote is executable if there a valid transition from the current status to the status Order Submitted. If a quote is executable, the following additional information is printed:• Contract Information• Signature Block


If a quote is non-executable, you have the option to include a customizable disclaimer.





Print quote set up involves the following tasks:• Designate a value for the profile option ICX: Report

Server.• Set the profile ASO: Print Quote Reports Directory to

<content of $ASO_TOP>/reports specifying the absolute path rather than the variable.

• Set the variable REPSRV_NAME=Rep60_<SID> in your report server startup script (adrepctt.sh).

• Set other print quote related profile options.• Stop/Restart the web server.


A valid file with a standard file name, cgicmd.dat, is located in the ORACLE_ HOME\REPORT60 directory on the Web server machine. This file contains a key map defined to simply or hide parameters in your URL request. Enter this key as profile value of ICX: Report Server. For more information, see Oracle Reports Developer - Publishing Reports.



Setting Print Quote Related Profiles

Setting Print Quote Related Profiles

The print quote profile options determine where the print quote report is located and what appears on the report.

Print Quote Profiles

ASO: Company Report Logo Default: <None> Specifies the location of the gif file used for the company logo. This file is stored as an attachment or “document” that is uploaded to the file system and retrieved at runtime. Consequently, the “document” is assigned a document ID when uploaded. The value of this document ID is used to set this profile option. You can set this profile at the site, application, and responsibility levels. Finding the document ID for the document: 1. From the Help menu, select Diagnostics > Examine. 2. In the Examine Field and Variable Value form, enter DOCUMENT_HEADER for the Block and DOCUMENT_ID for the Field. 3. Record the value returned in the Value field. ASO: Print Quote Reports Directory Default: <None>



Specifies the directory location for the report source files. This value is a fully qualified file path that points to a .rpt file. The .rpt file contains processing, layout, and data retrieval instructions for the report. Oracle Reports Server uses this report definition to create the report at runtime. You can set this profile at the site level. ASO: Print Quote Show Attachments Default: Yes Determines if attachments associated with the quote may be printed during the print quote process. If null, then a value of Yes is assumed. Only text attachments can be printed. You can set this profile at the site level. ASO: Show Line Level Tax Details Default Value: No This profile must be set in order to print line-level tax information. Aggregated header-level tax information is printed by default.



Customizing and Personalizing the Print Quote Report


You may want to customize or personalize printed quote reports based on business requirements.Some customizations include:• Specifying quote data to be retrieved and printed• Modifying page layout

Personalizations include:• Adding a company logo• Modifying header or footer information


The seeded report is called FXREPORT. Company logos are stored as attachments to provide better efficiency. These attachments are assigned a document ID and retrieved at runtime. You will need to know the document ID for the logo in order to set the ASO: Company Report Logo profile option.



Guided Demonstration - Customizing the Print Quote Report


1. Log in to Oracle Forms (ebusiness/welcome) with the Quoting Sales Manager responsibility.

2. Navigate to the Documents form.

• (N) Setup > Documents

3. Select PrintQuote from the Category LOV.

4. Select File from the Source Data Type LOV.

5. Browse for your file and select (B) OK.

A window displays asking if your file uploaded successfully. Click (B) Yes.

6. Click (I) Save.

7. Find the Document ID for the document. − Select (M) Help > Diagnostics > Examine. − In the Examine field and Variable Value form, enter DOCUMENT_HEADER for

the Block and DOCUMENT_ID for the field. − Note the value returned in the Value field.

8. Use this value to set the profile option ASO: Company Logo at the appropriate level. You logo will be displayed on the printed quote report.

9. Customize the report title.

Two customizable FND messages are registered for the print quote report, one for non-executable quotes and one for executable quotes.

− ASO_PQUOTE_EXEC_TITLE − ASO_PQUOTE_NONEXEC_TITLE

Note to instructor: Change the responsibility to Application Developer (N) Application > Messages, and search for ASO_PQUOTE%.

10. Customize the disclaimer.

If the quote is non-executable, you can customize the disclaimer printed on the bottom of the quote by changing the name of the ASO_PQUOTE_DISCLAIMER message.



Adding New Print Quote Templates to Quoting Lookups (Quick Codes)


If you create new print quote templates, then you must add them to the ASO_PQUOTE_TEMPLATES lookup so that the reports appear in a template LOV option for sales reps.


The seeded print quote template is called Default Print Layout. You can disable this report, if necessary.



Guided Demonstration - Adding a Print Quote Template to the Quoting Lookup



2. Navigate to the Quick Codes form.

• (N) Setup > Quick Codes


4. Enter ASO_PQUOTE_TEMPLATES in the Type field.


6. Select a new line. In the Code field, enter the report file name you created in Oracle Reports Builder (exclude the file extension).

7. In the Meaning field, enter the description of the report that you want to appear in the Templates LOV.

8. In the Description field, enter a description of the template that distinguishes it from others. (This is for administrative purposes and will not be displayed in the Quoting UI.)

9. Ensure that the Enabled box is checked.

10. Click (I) Save.

11. Bounce the web server. Your new PrintQuote report template is now a template LOV option in the PrintQuote screen of the Quoting UI.



Personalizing Print Quote

Personalizing Print Quote

Printed quote reports can be personalized to include a company logo and to modify any header or footer text that is printed.



Guided Demonstration - Adding a Logo to the Print Quote Report



2. Navigate to the Document Categories form.

• (N) Setup > Document Category.

3. Enter PrintQuote in the Category field.

4. Enter Image in the Default Datatype field.

5. Save your changes and close the form.

6. Navigate to the Documents form.

• (N) Setup > Documents

7. In the Documents form, select PrintQuote from the Category LOV.

8. From the Source Data Type LOV, select File.

9. From the File Upload form, browse for your image file and select OK .

10. A window displays asking if your file uploaded successfully. Select (B) Yes.

11. Click (I) Save. The document is saved to the database.



Summary

Summary

In this module, you should have learned how to:• Describe printed quote format options, layout, and

contents• List print quote setup tasks and related profile

options• Describe customizations and personalizations that

can be done to print quote reports• Add a new print quote report template to Quoting

lookups• A company logo to a print quote report


Integrating Quoting and Oracle Sales Online Chapter 17 - Page 1

Integrating Quoting and Oracle Sales Online Chapter 17



Integrating Quoting and Oracle Sales Online

Integrating Quoting and Oracle Sales Online



Objectives

Objectives

After completing this module, you should be able to:• Describe the functionality available when OSO and

Quoting are integrated• Determine which Quoting UI integrates with Oracle

Sales Online• Identify the profile options related to OSO/Quoting

integration• Create a Sales Online/Quoting User



OSO and Quoting Functionality Overview


Create a new quoteCreate a quote from an existing opportunity

Convert a quote to an orderMaintain quote details

Negotiate pricing

Check product availabilityAssign sales credits

Enter shipping and billing information

Approve quotes online

Print quotesApply manual pricing overridesSelect pricing agreementsConfigure quote lines


Oracle Quoting automates the creation and management of accurate, consistent customer quotes across all sales and interaction channels. A Quoting/OSO integration delivers the following benefits:

• Reduces sales cycles and cost by automating the quoting and approval process • Increases order value with automated cross-sell and up-sell recommendations • Improves management visibility into deals and orders, facilitating understanding and

decision making



OSO/Quoting Integration Functional Flow


Select / Create Opportunity

Opportunity

QuoteEnter

Payment Info Request Quote

Approval Approve

Quote Print

Quote Convert to Order

OSO Opportunity tab

Add Products and Services

Add Billing and Shipping Info

Create Quote

Quote

OSO Quote tab

OSO Quote tab


A Create Quote button is available in the OSO Opportunity tab . This button allows the sales representative to create a quote from a new or existing sales opportunity. Once the Create Quote button is selected, the sales representative is shifted to the Quote tab within OSO. Here, the sales representative can create, approve, print, and ultimately convert the quote into an order. When integrating OSO and Quoting, the two main business flows are campaign-to-order and quote-to-order:

• Campaign to order: You begin in Sales Online to fulfil the campaign to opportunity work flow. To create a quote as part of a sales campaign or to conclude a campaign, click the Quote tab in Sales Online. You then create a quote within Sales Online, and submit the quote as an order if you have the permission to do so.

• Quote to order: You create quotes for customers. You can also submit the quote as an order if you have the permission to do so.



Quoting interfaces with Telesales and Oracle Sales Online


Oracle Sales Online (OSO)

Oracle Quoting - HTML Interface

Oracle Telesales (OTS)

Oracle Quoting – Forms Interface

Oracle Sales Online uses the HTML interface. Oracle TeleSales uses the Forms interface. Oracle Sales Online provides sales representatives with a complete customer overview at each stage of the sales process, in both Business to Business and Business to Customer environments. Before contacting a customer, a sales person can review customer information including: products installed, outstanding service requests, payment history, key relationships, open opportunities, and interaction history-customer touch points. Comprehensive customer information allows salespeople to better manage their customers and to plan each customer interaction more efficiently.



OSO and Quoting Integration Interface

OSO and Quoting Integration Interface

Using OSO integrated with Oracle Quoting, Sales Representatives can create opportunities

and quotes from those opportunities without delay.

OSO’s Opportunity Tab



Integrating Oracle Sales Online and Oracle Quoting (HTML)

Integrating Oracle Sales Online and Oracle Quoting (HTML)

Assign OSO responsibilities

Import CRM Resource

Set OSO Profile Options

Set Quoting Profile Options

Create a new user

1 2 3

4 5 6

Create a new employee

Integrating Oracle Sales Online and Oracle Quoting (HTML UI)

1. Create a new employee 2. Create a new user 3. Assign responsibilities The Seeded Sales Online Responsibilities are:

• Sales Online Representative • Sales Online Manager • Sales Online Administrator

The seeded Oracle Quoting Responsibilities are: • Quoting Sales Agent (Access to Forms UI) • Quoting Sales Manager (Access to Forms + HTML UI) • Oracle HTML Quoting Sales Agent (Access to HTML UI)

Once you assign your user responsibilities, be sure to set the following JTF profiles for the user:

• JTF_PROFILE_DEFAULT_APPLICATION (change to 522)



• JTF_PROFILE_DEFAULT_RESPONSIBILITY (22477 for Administrator, 22406 for Manager, 22405 for user)

4. Import CRM Resource 5. Set OSO Profile Options 6. Set Quoting Profile Options



Guided Demonstration - Setting Up and Enabling Sales Online Quoting Integration

Set Quoting and OSO Profile Options


1. Log in to Oracle Forms (sysadmin/sysadmin) with the system administrator responsibility.



3. In the Profile field, enter OSO%Enable Quotes%.

4. Select (B) Find.

5. Set the profile OSO: Enable Quotes to Yes at the Site level.

6. Navigate back to the Find System Profile Values form.

7. In the Profile field, enter ASO%Enable OSO%.

8. Select (B) Find.

9. Set the profile ASO: Enable OSO Integration to Yes at the Site level.

Create an Employee


10. Log in to Oracle Forms (operations/welcome ) using the HRMS Management responsibility.

11. Navigate to the People form

• (N) HRMS Manager > People > Enter and Maintain









18. Enter a date in the Date of Birth field.








24. Navigate to the Define Users form.

• (N) Security > Users > Define





− Sales Online User − Quoting Sales Manager − Oracle HTML Quoting Sales Agent



Import Resources




















Set the JTF Profile Options

Responsibility = CRM Support, Visions Enterprises

47. Log in to Forms (ebusiness/welcome) or if already logged in, select (M) File > Switch Responsibility.



• (N) Security > Profile > Personal.

50. Place your cursor in the profile field and search for the following seeded profiles. Once you find them, change to the following suggested values.

− JTF_PROFILE_DEFAULT_APPLICATION (change to 522) − JTF_PROFILE_DEFAULT_RESPONSIBILITY (22405 for Agent)



Log In to Oracle Sales Online

Responsibility = Sales Online User

51. Login with your new user to the CRM HTML login page.

52. Select the Quoting tab. If Quoting is enabled and your user is set up properly, you can view the Quoting UI in this tab.



Practice - Setting Up a Sales Online and Quoting User

Overview

This practice teaches users how to set up an OTS/Quoting user.

Assumptions


• HRMS Management




Tasks

Create an Employee

Log in to Oracle Forms using the HRMS Management responsibility to create employees.


Use the System Administrator responsibility to create a User ID for your employee and assign OSO and Quoting responsibilities to the User ID.

Import Resource



You must set the JTF profile options for your user. This ensures that the user has the appropriate default application and responsibilities.



Solution - Creating an Employee

Create an Employee





• (N) HRMS Manager > People > Enter and Maintain.







10. In the Personal tab, enter a date of birth (use the format: DD-MMM-YY).









• (N) Security > User > Define.







− Sales Online User − Oracle HTML Quoting Sales Agent



Import Resources














35. Select (T) Roles.

36. In the Role field, enter Sales. In the Role Type field, enter Sales Representative.

37. Select (T) Groups.



38. In the Groups section, enter Sales. In the corresponding line in the Group Member Roles section, enter Sales Representative.







43. Navigate to the Personal Profile Values form.

• (N) Profile > Personal

44. Place your cursor in the profile field and select View > Query By Example > Enter.

45. Enter JTF_PROFILE_DEFAULT% and select View > Query By Example > Run.

46. Change the following profiles to the values suggested: − JTF_PROFILE_DEFAULT_APPLICATION (change to 522) − JTF_PROFILE_DEFAULT_RESPONSIBILITY (22405 for Agent)

47. Save your work and close the form.

Log In to Quoting

Responsibility = Sales Online User

48. Login to Quoting using the CRM HTML Login link. At the login page, enter the username and password for your new user.

49. Select (T) Opportunity.

50. Enter XX Test Opportunity in the Opportunity Name field.

51. Enter Business% in the Customer field and click Go.

52. Select the Business World entry with the address 2391 L Street San Jose Santa Clara CA 95106 and click Select.

53. Select Desktop from the Product Category drop-down menu.

54. Enter 20 in the Quantity field.

55. Enter $20,000 in the Amount field and click Create.



56. In the Opportunity page, scroll down to the Purchase Items section.

57. On the line with the Product Category Desktop, enter the product: AS54888.

58. Click Create Quote. The Create Quote From Opportunity page opens.

59. Leave the information as is and click Apply.

The new quote appears in the Quoting UI. You are directed to the Lines page, where you should see the product AS54888 with a quantity of 20.





The following Quoting profile options pertain to Quoting/OSO integration:

ASO: Enable OSO Integration

OSO: Default Sales Group and Role

OSO: Enable Quotes


ASO: Enable OSO Integration If set to Yes, customer, contact, and address are displayed as hyperlinks to OSO. If set to No, integration with OSO is not enabled.This profile is mandatory if the HTML UI is accessed through OSO. OSO: Default Sales Group and Role Default value: <none> A value for this profile option is mandatory if Quoting is accessed through Oracle Sales Online. You can set this profile at the user level. OSO: Enable Quotes Enables the Create Quote button on the Opportunity Details page.



Summary

Summary

In this module, you should have learned how to:• Describe the functionality available when OSO and


Sales Online• Identify the profile options related to OSO/Quoting

integration• Create a Sales Online/Quoting User


Integrating Oracle Quoting and Oracle TeleSales Chapter 18 - Page 1

Integrating Oracle Quoting and Oracle TeleSales Chapter 18



Integrating Oracle Quoting and Oracle Telesales




Objectives

Objectives

After completing this module, you should be able to:• Describe the functionality available when OTS and


TeleSales• Identify the profile options related to OTS/Quoting

integration• Create a TeleSales/Quoting User



OTS and Quoting Integration Functionality Overview

OTS and Quoting Integration Functionality OverviewCreate a new quote

Create a quote from an existing opportunityConvert a quote to an order

Maintain quote details

Negotiate pricing

Check product availabilityAssign sales credits

Enter shipping and billing information

Approve quotes online

Print quotesApply manual pricing overridesSelect pricing agreementsConfigure quote lines

Oracle Quoting automates the creation and management of accurate, consistent customer quotes across all sales and interaction channels. A Quoting/OTS integration delivers the following benefits:

• Reduces sales cycles and cost by automating the quoting and approval process • Increases order value with automated cross-sell and up-sell recommendations • Improves management visibility into deals and orders, facilitating understanding and

decision making





Oracle Telesales (OTS)

Oracle Quoting – Forms Interface

Oracle TeleSales uses a Forms interface Oracle TeleSales is a call center-enabled application designed for internal sales representatives, distributors, resellers, and sales executives. With TeleSales they can track, manage, and execute sales in the customer sales cycle. Oracle TeleSales exploits Forms - Quoting and order submission functionality as part of this process. For example, if a customer contacts a sales organization by telephone, the Sales Representative can access the TeleSales application to generate the lead, qualify the prospects, access existing customer information and submit a quote.



OTS/Forms Quoting Interface

OTS/Forms Quoting Interface

Using OTS integrated with Oracle Quoting, Sales Representatives can create quotes from the

Opportunity Center.





1

Create a new employee

2

Create a new user

3

Assign OTS and Quoting

responsibilities

4

Import CRM resource

5

Set OTS profile options

Integrating Oracle Quoting and Oracle TeleSales

Step 1: Create a New Employee Step 2: Create a New User Step 3: Assign Responsibilities Telesales Seeded Responsibilities:

• TeleSales Agent • TeleSales Marketing Agent • TeleSales Manager • TeleSales Administrator

Oracle Quoting Seeded Responsibilities: • Quoting Sales Agent (Access to Forms UI) • Quoting Sales Manager (Access to Forms + HTML UI) • Oracle HTML Quoting Sales Agent (Access to HTML UI)

Once you assign your user responsibilities, be sure to set the following JTF profiles for the user:



• JTF_PROFILE_DEFAULT_APPLICATION (change to 690) • JTF_PROFILE_DEFAULT_RESPONSIBILITY (21841 for Manager)

Step 4: Import CRM Resource Step 5: Set OTS Profile Options



Guided Demonstration - Setting Up and Enabling OTS/Quoting Integration

Create an Employee



2. Navigate to the People form.

• (N) HRMS Management > People > Enter and Maintain







9. Enter a birth date for the employee in the Personal tab.















− TeleSales Agent − Quoting Sales Agent − Quoting Sales Manager



Import Resources















35. Select (T) Roles. Assign the following role type. − Role Type = Sales



− Role = Sales Manager









• (N) Profile > Personal.

42. Place your cursor in the profile field and search for the following seeded profiles. Once you find them, change to the following suggested values at the User level (for the user you created).

− JTF_PROFILE_DEFAULT_APPLICATION (change to 690) − JTF_PROFILE_DEFAULT_RESPONSIBILITY (21841 for Manager)

Log In to Quoting

Responsibility = TeleSales Agent

43. Login to Forms with your new user and select the TeleSales Agent responsibility.



45. Select Find.

46. Select Organization from the drop-down menu.

47. Enter Business World in the Customer field and click search.

48. Highlight Business World and select OK.

49. Navigate to the Opportunity tab and select New. Create an opportunity with the following information:

− Opportunity Name = XXTestOpp − Interest Type = Desktop



− Primary = Sentinel − Secondary = Sentinel Standard Desktop − Inventory Item = AS54888 − Item Description = Sentinel Standard Desktop − UOM = Ea − Quantity = 50 − Amount = $500,000

50. Click (I) Save.


Explain that you can change certain information on this form: − Quote Name − Expiration Date − Order Type − Agreement − Price List − Currency − Contact Template − Salesperson − Sales Group − Sales Channel − Source Name − Account − Contact

52. Click Create Quote.

The new quote appears in the Quoting UI.



Practice - Setting Up an OTS and Quoting User

Overview

This practice teaches users how to set up an OTS/Quoting user.

Assumptions


• HRMS Management




Tasks

Create an Employee

Log in to Oracle Forms using the HRME Management responsibility to create employees.


Use the System Administrator responsibility to create a User ID for your employee and assign responsibilities to the User ID.

Import Resource



You must set the JTF profile options for your user. This ensures that the user has the appropriate default application and responsibilities.



Solution - Creating an Employee

Create an Employee

Responsibility = Human Resources, Vision Operations




• (N) People > Enter and Maintain.







10. In the Personal tab, enter a date of birth.









• (N) Security > User > Define.







− TeleSales Agent − Quoting Sales Agent − Quoting Sales Manager



Import Resources















36. Select (T) Roles. Assign the following role type. − Role = Sales



− Role Type = Sales Manager

37. Select (T) Groups. Assign the following group and role. − Group = Sales − Role = Sales Manager









43. Place your cursor in the profile field and search for the following seeded profiles. Once you find them, change to the following suggested values.

− JTF_PROFILE_DEFAULT_APPLICATION (change to 690) − JTF_PROFILE_DEFAULT_RESPONSIBILITY (21841 for Manager)

Log In to Quoting

Responsibility = CRM Support, Vision Enterprises

44. Login to Forms with your new user and select the TeleSales Administrator responsibility.



46. Select Find.

47. Select Organization from the drop-down menu.

48. Enter Business World in the Customer field and click search.

49. Navigate to the Opportunity tab and create an opportunity with the following information: − Opportunity Name = XXTestOpp − Interest Type = Desktop − Primary = Sentinel − Secondary = Sentinel Standard Desktop



− Inventory Item = AS54888 − Item Description = Sentinel Standard Desktop − UOM = Ea − Quantity = 50 − Amount = $500,000

50. Click (I) Save.


52. Optionally, select an account number for the customer.

53. Click Create Quote.

The new quote appears in the Quoting UI.





The following profile options pertain to OTS/Quoting integration:

ASO: Default E-Business Order ScreenASO: Default E-Business Quote ScreenOTS: Default User Role and Sales Group


ASO: Default E-Business Order Screen Default Value: Order Organizer Specifies the default Sales for Communications order form launched when the user selected the Details button while viewing Orders in the Quote/Order tab of the Oracle TeleSales E-Business form. You can set this profile at the site and responsibility levels. ASO: Default E-Business Quote Screen Default Value: Quoting Specifies the defaults Sales for Communications quote form launched when the user selects the Details button while viewing quotes in the Quote/Order tab of the Oracle TeleSales E-Business form. You can set this profile at the site and responsibility levels. OTS: Default User Role and Sales Group Default value: <none> A value for this profile option is mandatory if Quoting is accessed through Oracle TeleSales. You can set this profile at the user level.



Summary

Summary

In this module, you should have learned how to:• Describe the functionality available when OTS and


TeleSales• Identify the profile options related to OTS/Quoting

integration• Create a TeleSales/Quoting User


Integrating Quoting and Oracle Sales Contracts Chapter 19 - Page 1

Integrating Quoting and Oracle Sales Contracts Chapter 19



Integrating Oracle Quoting and Oracle Sales Contracts

Integrating Oracle Quoting and Oracle Sales Contracts



Quoting and Contracts Integration Functionality

Quoting and Contracts Integration Functionality

• The objective of Quoting/Contracts integration is to automate the creation and delivery of quotes with default or negotiated terms.

• The goal is to share information between all parties involved (customer, sales rep, contract administrator) in the creation or modification of a quote.

Quoting and Contracts Integration

Oracle Contracts for Sales — Enables users to include standard and non-default contracts with quotes. The aim of a Contracts/Quoting integration is to share the information between all parties involved in the creation / modification of a quote with non default terms and conditions. NOTE: Sales Contracts is no longer on the Oracle price list. Therefore, this lesson applies only to users that have Sales Contracts implemented.



Contracts for Sales Quoting Integration Functionality Overview

Contracts for Sales Quoting IntegrationFunctionality Overview

Request contract specialist assistance to create or modify

Create of quotes with default Ts & Cs

Print a quote with Terms & Conditions

View contract reference and info

summary

Contracts for Sales/Quoting Functionality Overview

With Contracts integration, Quoting provides the following functionality: • Automatic creation of quotes with default terms and conditions • Ability to request contract specialist assistance to create or modify standard contracts • Print quote with or without terms and conditions • View contract reference information and summary



Contracts and Quoting Functional Flow


Create Quote

Non-Default Terms and Conditions

Default Terms and Conditions

Contract Creation Process

Contract Specialist

Authors Contract

Contract approval process Final Contract

Submitted

Quote Converted to

Order

Order is Placed

Contract is created with

standard T & C


If your customer is satisfied with the standard terms and conditions attached to a quote, the contract is created when the quote is submitted as an order. If the contract does not meet your customer’s needs, you can initiate the contract creation process. A contract specialist authors the contract and once the new contract is satisfactory, it is approved.



Integrating Oracle Contracts and Oracle Quoting

Integrating Oracle Contracts and Oracle Quoting

• Step 1: Set Oracle Quoting profile options• Step 2: Set Contracts profile values• Step 3: Set an Independent Condition• Step 4: Run background processes • Step 5: Set up workflow notification mailer• Step 6: Set up notification recipients

Integrating Oracle Sales Online and Oracle Quoting

Step 1: Set Oracle Quoting profile options You must set the profile ASO: Enable Use Contracts to Yes if you want to use contracts. Step 2: Set Contracts profile values You must set specific Oracle Contracts Core profile options in order to user Oracle Contracts with Oracle Quoting. OKC: Contract Template for Standard Terms and Conditions Determines the contract template for standard terms and conditions. Mandatory if ASO: Enable Use Contracts is set to Yes. Default value: <none> Set at Site, Application, Responsibility levels. OKC: Default Contract Administrator for Notifications Determines which contract administrator receives notification when a sales representative requests contract creation from a quote.



Default value: <none> Set at Site, Application, and Responsibility levels Step 3: Set an Independent condition To enable the quote status change to Contract Canceled, when its associated contract is canceled, you must set up an independent condition in Contracts. Step 4: Run background processes You must run the workflow background process if integrating Quoting and Contracts. Step 5: Set up workflow notification mailer The Workflow Notification Mailer must be running to enable:

• Contract alerts to be sent • Contract Approval process

Step 6: Set up notification recipients To send notifications to sales representatives when a customer disagrees with standard terms and conditions or when terms and conditions are changed and ready for approval, you must set up notification recipients functionality.



Guided Demonstration - Setting Up an Independent Condition

Responsibility: Contracts Manager, Vision Enterprises

1. Log in to Oracle Forms with the Contracts Administrator responsibility.

2. Navigate to the Define Independent Conditions form.

• (N) Contract Events > Define Independent Condition.

3. Enter XXContractCanceled in the Name field.

4. Select Contract Status Change From LOV from the Action LOV.

5. In the Expression tab, select CONTRACT CURRENT STATUS CODE from the Left Value LOV.

6. Select = from the Operator LOV.

7. Select CANCELED from the Right Value LOV.

8. In the Notifications tab, select Notify Sales Rep from the Outcomes LOV.

9. Select (B) Parameters.

10. Holding down the control key, select the following three parameters:

P_CONTRACT ID

P_CONTRACT STATUS

P_API_VERSION

11. In the Parameters form, set the selected parameters as follows:

P_CONTRACT ID = CONTRACT ID

P_CONTRACT STATUS = CONTRACT CURRENT STATUS CODE

P_API_VERSION = 1

12. Click OK.

13. Click (I) Save.



Related Quoting Profile Options


The following profile options apply to Quoting/Contracts integration:

• ASO: Enable Use Contracts • ASO: Enable To Instantiate Contract When Default

Terms and Conditions Needed


ASO: Enable Use Contracts Default value: No Enables Quoting integration with Oracle Contracts. Must be set to Yes to use Contracts. ASO: Enable to Instantiate Contract When Default Terms and Conditions Needed Default value: No Determines if a new contract is created at the time of order placement, if none exists. This profile can be set at the site and application levels.



Summary

Summary

In this module, you should have learned how to:• Outline the Contract process• Distinguish between a standard and non-standard

contract• Set up and enable Contracts• Identify related profile options


Resources Chapter 20 - Page 1

Resources Chapter 20



Resources

Resources



Resources

Resources

• Technical Documentation• AppsNet• Oracle Support Services• Oracle MetaLink

Resources

Technical Documentation The following documents are relevant to Quoting:

• Oracle Quoting User Guide • Oracle Quoting Implementation Guide • Oracle Sales Online User Guide • Oracle Sales Online Implementation Guide • Oracle Applications System Administrator’s Guide, Release 11i • Implementing Oracle CRM: ERP Functional Checklist, Release 11i • Oracle Order Management User’s Guide. • Oracle Inventory User’s Guide • Order Management Suite Implementation Manual.

Portable Document Format (PDF) versions of these documents can be found on the Oracle Applications 11i Documentation CD or downloaded from Oracle MetaLink. AppsNet



Oracle AppsNet is a key information portal for the E-Business Suite. Presentations, documentation, e-Seminars, chat, articles, demonstrations, and other application related information can be found at http://www.oracle.com/appsnet/index.htm. Oracle Support Services Contact Oracle Support services for self-service support requests, troubleshooting tips, and technical support issues. Oracle MetaLink Go to Oracle MetaLink for the latest information, downloads, and eTRM access.