Download pdf - CPQ Cloud-Receivables Integration - Oracle Cloud · Credit Check, and AR, but it does not included detailed instructions for how to create each component. Refer to each Integration

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

CPQ Cloud-Accounts Receivable Integration Implementation Overview

Oracle CPQ Cloud Product Management April 2015 Sections 1. Integration Overview 2. CDM Integration 3. Credit Check Integration 4. Accounts Receivable Integration

ACCOUNTS RECEIVABLE

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |

Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

2


CPQ Cloud, Customer Data Management, Credit Check, and Accounts Receivable Integration Overview

3

The sales rep enters a customer company name in CPQ Cloud and then clicks Customer Details. CPQ Cloud checks CDM for customer details based on the company name.

If company name is valid… CDM returns the customer’s Account Number and Bill To Site Number, which are both displayed in the CPQ Cloud user interface. If company name is invalid… CDM returns error messages, which are displayed in the CPQ Cloud user interface, and the CPQ Cloud user cannot proceed with order creation.

CPQ Cloud requests a credit check based on the verified-by-CDM customer company name. Note: Credit Check functionality is a part of Oracle Fusion Financials.

AR receives transaction data and invoice creation begins. If credit check is approved…

An approval message is returned to CPQ Cloud and displayed on the user interface. The sales rep is free to proceed in CPQ Cloud. If credit check is rejected… A rejection message is returned to CPQ Cloud and displayed on the user interface. The sales rep cannot proceed.

When the Transaction is finalized in CPQ Cloud, the sales rep clicks the “Create Invoice” button. Transaction data is then sent to AR.

Start


Preparing CPQ Cloud for Integration

Prerequisites • CPQ Cloud version 2014 R2 or later • Base Reference Application is

deployed on the environment – Customers with QuickStart sites can still

perform the integration, but many integration files will need to be manually modified. Contact CPQ Cloud Product Management for more information.

Integration Dependencies • CDM integration must be

implemented in CPQ Cloud to perform Credit Check integration

• CDM and Credit Check integrations must be implemented in CPQ Cloud to perform AR integration

4

Important Note: This document gives a high-level overview of what must be created in CPQ Cloud to enable integration with CDM, Credit Check, and AR, but it does not included detailed instructions for how to create each component.

Refer to each Integration White Paper (linked to at the end of this document) for detailed administration instructions.


CPQ Cloud-Customer Data Management Integration Implementation Overview

CUSTOMER DATA MANAGEMENT


CDM Requirements • Fusion Sales Cloud Release 9 or

later • Fusion CDM web services that must

be running: – “OrganizationService” operation

“findOrganization” – “CustomerAccountService” operation

“findCustomerAccount”

CPQ Cloud Components to Create for CDM Integration • 4 Attributes • 1 Action • 1 Validation Rule • 4 Library Functions • 1 Step Transition (Document View) • 2 Data Tables

6

Preparing for Integration CPQ CDM


Preparing CPQ Cloud for Integration Attributes

7

Five new attributes must be created in CPQ Cloud to enable integration with CDM:

CPQ CDM

Attribute Description Visible on the CPQ Cloud Layout

Customer Company Name Populated by the sales user, and used to check for customer data in CDM. Yes

Account Number Populated by CDM based on the Customer Company Name. Yes

Bill To Site Number Populated by CDM based on the Customer Company Name. Yes

Party ID Populated by CDM based on the Customer Company Name. No


Preparing CPQ Cloud for Integration Actions

8

One new action must be created to accomplish integration with CDM:

Action Description Visible on the CPQ Cloud Layout

Customer Details Invoked by the CPQ Cloud user. This action begins the process of retrieving customer details from CDM based on the customer company name by triggering the necessary library functions.

Yes

CPQ CDM


Preparing CPQ Cloud for Integration Validation Rule

9

One Validation rule must be created in the Oracle Quote to Order Commerce Process:

CPQ CDM

Validation Rule Name Action Constrained Condition Description

CustomerDetails Submit Account Number and Bill To Site Number are both blank.

The CPQ Cloud user will not be able to click Submit when the Account Number and Bill To Site Number attributes are both blank. A message will be displayed to instruct the CPQ Cloud user to click Customer Details to retrieve the data for these attributes from CDM.

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. | 10

getTemplateLocation

Retrieves the correct XML template file from the File Manager so it can be populated by a Fusion CDM web service.

getUserAttributes

Retrieves a username for CDM.

getPassword

Retrieves a password for CDM.

Four new Library Functions must be created and will run when the CustomerDetails action is fired.

invokeWebService

Invokes the correct Fusion CDM web service to populate the XML template file with CDM customer data.

Preparing CPQ Cloud for Integration Library Functions

CPQ CDM


Add the new Document View to the "Sales Rep" or "Default" Participant Profile unless advised otherwise. This view will hide the new Customer Details action based on the current step.

Action Steps Action is Shown Description

Customer Details Start, In Progress The Customer Details action will be available for the CPQ Cloud sales user to invoke until the Transaction reaches the Approved step.

CPQ CDM Preparing CPQ Cloud for Integration Step Transition (Document View)


A new INT_SYSTEM_TEMPLATES data table will contain links to the TCA-OrgService and TCA-AccService XML template files in the File Manager. This data table will be queried by the new getTemplateLocation Library Function to retrieve the template files so they can be populated with CDM customer data.

A new INT_SYSTEM_DETAILS data table will contain Fusion CDM web service names, usernames, and end points. This data table will be queried by the new CPQ Cloud Library Functions getUserAttributes and invokeWebService to populate the XML template files using table data and Fusion CDM web services.

Preparing CPQ Cloud for Integration Data Tables

12

CPQ CDM

Actions

getTemplateLocation getUserAttributes getPassword

INT_SYSTEM_TEMPLATES

Library Functions

Data Tables INT_SYSTEM_DETAILS

QU

ERY RETU

RN Q

UERY RE

TURN

invokeWebService

INT_SYSTEM_DETAILS

QU

ERY RETU

RN

Customer Details

(Hard Coded)


For detailed instructions on creating the components in CPQ Cloud necessary to enable integration with Fusion CDM, as well as access to additional sample files and resources, see the Implement CPQ-CDM Reference Integration white paper.

13

Next Steps Implement CPQ-CDM Reference Integration

CPQ CDM


CPQ Cloud-Financials Credit Check Integration Implementation Overview


Preparing CPQ Cloud for Integration

15

CPQ CC

CPQ Cloud Components to Create for Credit Check Integration • 1 Attribute • 1 Action • 1 Validation Rule • 6 Formulas • 4 Library Functions • 1 Step Transition (Document View) • 2 Data Tables



16

One new attribute must be created in CPQ Cloud to enable integration with Credit Check:

Attribute Description Visible on the CPQ Cloud Layout

Credit Approval State Displays the Credit Approval status as being either accepted or rejected. Yes

CPQ CC



17

One new action must be created to accomplish integration with Credit Check:


Credit Check Invoked by the CPQ Cloud user. This action begins the process of checking the customer company name’s credit in Financials Credit Check by triggering the necessary library functions.

Yes

CPQ CC



18



Credit Check Validation Create Invoice

Credit Approval State equals “Credit check request is rejected” or is blank.

The CPQ Cloud user will not be able to click Create Invoice when a credit check has not been performed or when a request for a credit check came back as rejected. A message will display to tell the user to request a credit check, or that an invoice cannot be created because the credit check was rejected.

CPQ CC


Preparing CPQ Cloud for Integration Formulas

19

Six formulas must be created in Formula Management to correctly formulate the Total Contract Value, which will be used in the Credit Check:

CPQ CC

Attribute Formula listPrice_l _price_item_price_each

customDiscountAmount_l if( ( customDiscountType_l = "Amount Off" ), customDiscountValue_l,if( ( customDiscountType_l = "Percent Off" ), ( listPrice_l * ( customDiscountValue_l / 100 ) ), if( ( customDiscountType_l = "Price Override" ), ( listPrice_l - customDiscountValue_l ), 0 )))

netPrice_l if( ( customDiscountType_l = "Price Override" ), customDiscountValue_l, ( listPrice_l - customDiscountAmount_l ) )

netAmount_l netPrice_l * requestedQuantity_l

contractValue_l if( ( priceType_l = "One Time" ), netAmount_l,if( ( priceType_l = "Recurring" ), ( netAmount_l * contractedPeriods_l ), 0 ))

totalContractValue_t sum(contractValue_l)


getTemplateLocation

Retrieves the correct XML template file from the File Manager so it can be populated by a Fusion Financials Credit Check web service.

getUserAttributes

Retrieves a username for Credit Check.

getPassword

Retrieves a password for Credit Check.

Four new Library Functions must be created and will run when the Credit Check action is fired.

invokeWebService

Invokes the correct Fusion Financials Credit Check web service to populate the XML template file with accepted or rejected data.


CPQ CC

20


Add the new Document View to the "Sales Rep" or "Default" Participant Profile unless advised otherwise. This view will hide the new Credit Check action based on the current step.

Action Step Action is Shown Description

Credit Check Approved The Credit Check action will be only be available for the CPQ Cloud sales user to invoke when the Transaction has been approved.

Preparing CPQ Cloud for Integration Step Transition (Document View)

CPQ CC


A new INT_SYSTEM_TEMPLATES data table will contain a links to the CreditCheck XML template file in the File Manager. This data table will be queried by the new getTemplateLocation Library Function to retrieve the template file so it can be populated with accepted or rejected data.

A new INT_SYSTEM_DETAILS data table will contain the Fusion Financials Credit Check web service name, username, and end point. This data table will be queried by the new CPQ Cloud Library Functions getUserAttributes and invokeWebService to populate the XML template files using table data and Fusion Financials Credit Check web service.


22

Actions

getTemplateLocation getUserAttributes getPassword


Library Functions


QU

ERY RETU

RN Q

UERY RE

TURN

invokeWebService

INT_SYSTEM_DETAILS

QU

ERY RETU

RN

Credit Check

(Hard Coded)

CPQ CC


For detailed instructions on creating the components in CPQ Cloud necessary to enable integration with Fusion Financials Credit Check, as well as access to additional sample files and resources, see the White Paper on CPQ-Credit Check Integration.

23

Next Steps White Paper on CPQ-Credit Check Integration

CPQ CC


CPQ Cloud-Accounts Receivable Integration Implementation Overview

ACCOUNTS RECEIVABLE


CDM Requirements • Fusion Sales Cloud Release 9 or

later • Fusion AR web service that must be

running: – “InvoiceService” operation

“processInterfaceLine”

CPQ Cloud Components to Create for AR Integration • 36 Attributes • 3 Actions • 1 Validation Rule • 6 Library Functions • 3 Step Transitions (Document Views) • 2 Data Tables

25

Preparing for Integration CPQ AR



26

In order for CPQ Cloud to give all necessary Transaction data to Fusion AR for order creation, 36 new attributes must be created in the Oracle Quote to Order Commerce Process:

• 2 customer company attributes populated by CDM

• 6 line-item/order attributes

• 17 contract and billing attributes

• 8 general transaction attributes

• 3 additional attributes populated by AR – Invoice Date – Invoice Number – AR Line GUID

CPQ AR



27

Three new actions must be created to accomplish integration with Fusion AR:


Create Invoice Invoked by the CPQ Cloud user. This action sends Transaction data to Fusion AR by triggering the necessary library functions to begin the process of creating an invoice. Yes

Cancel Invoice Invoked by the CPQ Cloud user. This action sends a request to cancel an in-flight order to Fusion AR. Yes

Cancel Line Invoked by the CPQ Cloud user. This action sends a request to cancel a line item off of an in-flight order to Fusion AR. Yes (line-level)

CPQ AR



28



No Line Validation Create Invoice No line items are present on the Transaction

The CPQ Cloud user will not be able to click Create Invoice on a Transaction that des not have any line items.

CPQ AR


Retrieves the correct XML template file from the File Manager so it can be populated by Fusion AR web services.

Six new Library Functions must be created and will run when either the Create Invoice, Cancel Invoice, or Cancel Line actions are fired.


getTemplateLocation getUserAttributes getPassword invokeWebService getMaxLines invokeARInvoice

Retrieves a username for Fusion AR.

Retrieves a password for Fusion AR.

Invokes Fusion AR web services to populate the XML template file.

Limits how many line items are sent in one invoice request according to an AR limit. If the number of line items on a Transaction exceeds this limit, multiple requests are sent to AR.

Sends the request (either to create an invoice or to cancel an invoice) to AR.

CPQ AR


INT_SYSTEM_DETAILS

QU

ERY RETU

RN

getCancelRequest invokeARInvoice

A new INT_SYSTEM_TEMPLATES data table will contain links to Fusion Financials XML template files in the File Manager. This data table will be queried by the new getTemplateLocation Library Function to retrieve the template files so they can be populated with AR invoice data.

A new INT_SYSTEM_DETAILS data table will contain Fusion Financials web service names, usernames, and end points. This data table will be queried by the new CPQ Cloud Library Functions getUserAttributes and invokeWebService to populate the XML template files using table data and Fusion Financials web services.


30

Actions


Library Functions


QU

ERY RETU

RN

(Hard Coded)

Create Invoice OR Cancel Invoice OR Cancel Line

getTemplateLocation getUserAttributes getPassword invokeWebService getMaxLines

QU

ERY RETU

RN

CPQ AR

(Hard Coded)

INT_SYSTEM_DETAILS

QU

ERY RETU

RN


For detailed instructions on creating the components in CPQ Cloud necessary to enable integration with Fusion AR, as well as access to additional sample files and resources, see the Implement CPQ-Receivables Integration white paper.

31

Next Steps Implement CPQ-Receivables Integration

CPQ AR


CPQ Cloud-AR Integration White Papers CPQ AR

ACCOUNTS RECEIVABLE CUSTOMER DATA MANAGEMENT