Integrating Oracle® Sales Cloud, Release 9 with

December 2014
Integrating Oracle® Sales
Cloud, Release 9 with JD
Edwards EnterpriseOne
release 9.1
Implementation Guide
Doc version 1.0
Copyright © 2005, 2014 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use
and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license
agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit,
distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you
find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf
of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs
installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial
computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any
operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be
subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a
risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to
take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation
and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous
applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used
under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD
logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a
registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
1
Introduction.................................................................................................................... 7
Overview .............................................................................................................................. 7
Integration Component Architecture ............................................................................. 8
Integration Services ............................................................................................................ 9
Integration Process Flows ................................................................................................. 10
Customer Data Matching with JDE EnterpriseOne ............................................... 10
Sales Order and Sales Quote Creation in JDE EnterpriseOne ............................. 12
Importing JDE EnterpriseOne Items to Oracle Sales Cloud Catalog ................. 14
Viewing Reports in JDE EnterpriseOne .................................................................... 14
Configuration Roadmap ................................................................................................. 15
2
JDE EnterpriseOne Configuration............................................................................. 19
Software Requirements for JDE EnterpriseOne ............................................................ 19
Upgrading to JDE Tools Release 9.1.4.7......................................................................... 20
Setting the Default Branch Plant Value ........................................................................ 21
3
Oracle Sales Cloud Configuration ........................................................................... 25
Before You Configure Oracle Sales Cloud ................................................................... 25
Software Requirements for Oracle Sales Cloud........................................................... 25
Creating References to JDE EnterpriseOne.................................................................. 25
Creating Web Service References .......................................................................... 25
Using Sandboxes ............................................................................................................... 26
Creating Sandboxes .................................................................................................. 27
Validating Sandboxes ................................................................................................ 27
Publishing Sandboxes ................................................................................................ 27
Creating Functions............................................................................................................ 27
Creating Global Functions ........................................................................................ 28
Creating Object Functions........................................................................................ 29
Creating Validation Rules ................................................................................................ 30
Creating Custom Objects ............................................................................................... 30
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
3
Contents
Creating a Custom Object .......................................................................................30
Adding Fields to a Custom Object ..........................................................................31
Creating Pages for a Custom Object .....................................................................31
Defining Security Policies for a Custom Object .....................................................32
Creating the Integration Configuration Custom Object ............................................ 32
Creating the Object ...................................................................................................32
Creating Fields .............................................................................................................33
Creating Pages ...........................................................................................................33
Defining Security Policies ...........................................................................................34
Creating the Validation Rule ....................................................................................35
Creating Global Functions ........................................................................................35
Validating and Publishing the Sandbox ..................................................................35
Creating the XREF Custom Object ................................................................................. 35
Creating the Object ...................................................................................................35
Creating Fields .............................................................................................................36
Defining Security Policies ...........................................................................................37
Creating Global Functions ........................................................................................37
Validating and Publishing the Sandbox ..................................................................37
Creating the JDE Match Child Object .......................................................................... 37
Creating the Child Object.........................................................................................38
Adding Fields to the Child Object............................................................................38
Defining Security Policies ...........................................................................................42
Customizing Standard Objects ....................................................................................... 42
Adding Fields to a Standard Object ........................................................................43
Adding Actions and Links to an Object ..................................................................43
Creating Triggers for an Object ................................................................................43
Customizing the Account Standard Object ................................................................. 44
Adding Fields ...............................................................................................................44
Creating Global Functions ........................................................................................45
Creating Object Functions ........................................................................................45
Creating the Action ....................................................................................................46
Creating the Validation Rule ....................................................................................46
Creating the Triggers ..................................................................................................46
Customizing Desktop Pages ......................................................................................46
Customizing the JDE Match Child Object..................................................................... 47
Creating the Object Function ..................................................................................47
Adding an Action to the Child Object....................................................................47
Validating and Publishing the Sandbox ..................................................................48
4
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Introduction
▪ Overview
Customizing Account Object Simplified Pages ........................................................... 48
Customizing the Sales Account Standard Object ...................................................... 50
Creating Object Functions........................................................................................ 50
Customizing Desktop Pages ..................................................................................... 50
Customizing the Opportunity Standard Object........................................................... 52
Adding Fields ............................................................................................................... 52
Creating Object Functions........................................................................................ 52
Creating Actions ........................................................................................................ 53
Customizing Desktop Pages ..................................................................................... 53
Customizing Simplified Pages ................................................................................... 54
Validating and Publishing the Sandbox ................................................................. 56
Connecting Oracle Sales Cloud to JDE EnterpriseOne.............................................. 56
Creating One View Report IDs........................................................................................ 57
4
Postconfiguration Tasks .............................................................................................. 63
Importing Products............................................................................................................ 63
Configuring Encoding in the JDE EnterpriseOne Application ............................. 63
Creating a JDE EnterpriseOne Catalog.................................................................. 64
Performing JDE EnterpriseOne Item Export ............................................................ 65
Performing Initial Import of JDE EnterpriseOne Items from the XML Import
File ................................................................................................................................. 66
Importing Updates of JDE EnterpriseOne Items from the XML Import File ........ 68
Troubleshooting the Import of All Items into the JDE Catalog Product
Group ........................................................................................................................... 68
Creating the Customer Matching Admin Role ............................................................ 69
Creating the New Role .............................................................................................. 69
Granting Privileges to the New Role ........................................................................ 70
Associating Users with the New Role ....................................................................... 70
5
Validating the Integration ......................................................................................... 73
Integration Validation Checklist ..................................................................................... 73
6
Appendix. Required Files ........................................................................................... 77
Groovy Files ........................................................................................................................ 77
Global Functions ......................................................................................................... 77
Batch Scripts ................................................................................................................ 77
Integration Configuration Custom Object ............................................................. 78
XREF Custom Object .................................................................................................. 78
JDE Match Child Object............................................................................................ 78
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
5
Contents
Account Object ..........................................................................................................78
Sales Account Standard Object ..............................................................................79
Opportunity Standard Object ..................................................................................79
6
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
1
Introduction
Overview
This document outlines the implementation and configuration steps that are required to
integrate customer- and opportunity-management processes in Oracle Sales Cloud with
business processes in JD Edwards EnterpriseOne.
NOTE: This document assumes a familiarity with Oracle Sales Cloud Application
Composer, and JD Edwards Business Services. For information on JDE Business Services,
see: https://support.oracle.com/epmos/faces/DocumentDisplay?id=967281.1.
For information on Oracle Sales Cloud Application Composer and customizations, see
http://docs.oracle.com/cloud/latest/salescs_gs/salescs_customize.htm.
The integration is designed to support customers who wish to take advantage of the
latest capabilities of the Oracle Sales Cloud application, but still leverage their existing
investment in an on-premise enterprise resource planning (ERP) system that provides
pricing and discount information, and quote and sales order processing. In the
integration, JDE EnterpriseOne quotes can be created from Oracle Sales Cloud
opportunities. The JDE EnterpriseOne Sales Order Entry UI which is used to enter and
update sales orders and sales quotes is embedded within a tab in the Opportunity
Detail screen in Oracle Sales Cloud (Figure 1).
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
7
Introduction
▪ Integration Component Architecture
Figure 1. JDE EnterpriseOne Sales Order Entry UI Embedded Within Oracle Sales Cloud
This integration document is designed to be used as a template. It is a starting point that
shows how Oracle Sales Cloud and JDE EnterpriseOne can be connected to create a
value-added business process and user experience. An implementer must enter the
documented configurations and install the required JDE EnterpriseOne Electronic
Software Update (ESU) JM16431. For more information on installing the ESU, see Applying
the JDE EnterpriseOne Electronic Software Update (ESU).
However, it is not a turnkey solution. Each customer’s implementation of Oracle Sales
Cloud and JDE EnterpriseOne is unique, and each customer has different needs that
have led them to implement application customizations that support their unique
business requirements. While the steps in this document describe how to connect a noncustomized Oracle Sales Cloud instance to a non-customized JDE EnterpriseOne
instance, they can be combined with customizations that have already been applied to
a customer’s instances.
Integration Component Architecture
Figure 2 shows the components of the integration between Oracle Sales Cloud and JDE
EnterpriseOne and their relationship with each other. The components are the following:
•
Oracle Sales Cloud standard objects. Standard objects in the Sales, Common, and
Customer Center applications are customized by adding fields, object functions,
triggers, and validations, and by customizing UI pages.
•
Oracle Sales Cloud custom objects. Custom objects are created for the integration,
and fields, pages, functions, and so on are added to the objects.
•
Groovy functions. Groovy scripts create functions, triggers, and validations that
modify the behavior of Oracle Sales Cloud objects.
8
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Introduction
▪ Integration Services
•
JDE EnterpriseOne web services. Oracle Sales Cloud calls JDE EnterpriseOne web
services directly. For more information on these web services, see Integration
Services.
•
JDE EnterpriseOne Sales Order Entry Program. Opportunities in the Sales application
in Oracle Sales Cloud are integrated with the Sales Order Entry Program in JDE
EnterpriseOne.
Figure 2. Integration Component Architecture
Integration Services
The following JDE EnterpriseOne web services are used in the integration:
•
CustomerManager Service. This web service manages customer records and is used
in the customer synchronization process between Oracle Sales Cloud and JDE
EnterpriseOne by searching for matching customers in JDE EnterpriseOne as well as
creating new customers if no suitable match is found.
•
SalesOrderManager Service. This web service manages order and quote records
and is used to create new quotes and orders in JDE EnterpriseOne based on Oracle
Sales Cloud opportunities.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
9
Introduction
▪ Integration Process Flows
Integration Process Flows
The integration supports five main process flows:
•
Matching customer data between Oracle Sales Cloud and JDE EnterpriseOne
•
Creating sales orders and sales quotes in JDE EnterpriseOne from Oracle Sales Cloud
opportunities
•
Importing JDE EnterpriseOne Items into Oracle Sales Cloud Catalog
•
Viewing reports in JDE EnterpriseOne from Oracle Sales Cloud opportunities
Customer Data Matching with JDE EnterpriseOne
This process allows you to match customer records in Oracle Sales Cloud with JDE
EnterpriseOne. During the customer synchronization process, existing JDE EnterpriseOne
customer records are searched in order to find suitable matches.
If the customer record exists in JDE EnterpriseOne and there is only one match, then the
process saves a cross-reference in Oracle Sales Cloud to the JD Edwards customer
record. The cross-reference contains the local identification in Oracle Sales Cloud and
the remote identification in JD Edwards. The integration can be configured, as shown in
this chapter, to disable automatic matching when one exact match is found, thus
activating the manual matching process described in the following paragraph.
Automatic matching is controlled by the "enableAutoModeForSingleMatch" integration
configuration parameter. For more information on configuring this parameter, see
Connecting Oracle Sales Cloud to JDE EnterpriseOne.
If the customer record exists in JDE EnterpriseOne and has multiple potential matches,
then the user is presented with a UI where the potential matches are displayed. The user
selects the candidate match. The process then associates the record in JDE
EnterpriseOne with the record in Oracle Sales Cloud by saving the cross-reference. If
none of the returned matches is suitable the user also has the option to create a new
customer in JDE EnterpriseOne.
If the customer record does not exist in JDE EnterpriseOne, then a new customer record
is created in JDE EnterpriseOne. The process then saves a cross-reference in Oracle Sales
Cloud with the local identification in Oracle Sales Cloud and the remote identification in
JDE EnterpriseOne.
Detailed Customer Data Matching Process
Figure 3 details the sequence of customer data matching.
10
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Introduction
▪ Integration Process Flows
Figure 3. Customer Data Matching Sequence Diagram
When a sales representative performs a customer matching operation in Oracle Sales
Cloud:
The process checks the current Account synchronization status in Oracle Sales Cloud.
If the Account is not synchronized then the process calls the CustomerManager
published web service which calls the getcustomerv3 method to perform a customer
search in JDE EnterpriseOne. The customer search returns a list of matching customer
records which are then stored in the customer matches object in Oracle Sales Cloud.
If there is no matching record, then the CustomerManager published web service calls
the processcustomer method which returns the remote customer identification for the
new customer created.
If there was one exact match, or a new customer was created in JDE EnterpriseOne, the
process creates an XREF custom object record in Oracle Sales Cloud using the local
identification in Oracle Sales Cloud and the remote identification from JDE
EnterpriseOne.
The Groovy logic invoked by the user when the Perform Sync button is pressed sets the
synchronization status to Synchronized.
For additional information about the getcustomerv3 and processcustomer web services
used to process customer information, see the Customer Master Data chapter in the JD
Edwards EnterpriseOne Applications Business Interface Implementation Guide. You can
access this guide on the Cross-Product tab of the JD Edwards EnterpriseOne
Applications Documentation Library, located at:
http://docs.oracle.com/cd/E16582_01/index.htm.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
11
Introduction
▪ Integration Process Flows
Sales Order and Sales Quote Creation in JDE EnterpriseOne
This process allows you to create sales quote and sales order records in JDE
EnterpriseOne based on opportunities created in Oracle Sales Cloud. After the customer
record is created in Oracle Sales Cloud and synchronized with JDE EnterpriseOne, you
can access the JD Edwards Sales Order Entry program to enter sales quotes and sales
orders.
This embedded Sales Order Entry program UI allows the user to take advantage of JDE
EnterpriseOne directly in Oracle Sales Cloud. All of the product, pricing, and
configuration details associated with the sales quote and sales order are captured in
JDE EnterpriseOne. The process also maps revenue line items in opportunity records in
Oracle Sales Cloud to quote line items in JDE EnterpriseOne.
Note that the user will be able to access JDE Enterprise One Quotes and Orders from
both the Opportunity UI as well as the Account UI in Oracle Sales Cloud. This is
accomplished by embedding portions of the JDE Enterprise One UI inside Oracle Sales
Cloud. The Sales Order and Quote Creation process described below is used when
creating Quotes or Orders directly in the Oracle Sales Cloud Opportunity UI based on
the Opportunity Revenue Lines.
Detailed Sales Order and Sales Quote Creation Process
Figure 4 details the sequence of sales order and sales quote creation.
12
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Introduction
▪ Integration Process Flows
Figure 4. Quote Creation Sequence Diagram
When a sales representative clicks Create Quote/Order on an Opportunity page in
Oracle Sales Cloud:
1. The process returns the Account associated with the opportunity in Oracle Sales
Cloud, and determines the synchronization status.
2. If the Account is synchronized, then the process reads the remote contact
identification from the XREF object. If the Account is not synchronized, then an error
is returned.
3. The quote/order creation process collects opportunity details such as revenue line
items from the Opportunity Revenue object.
4. The quote/order creation process synchronizes all the revenue lines using Product
Groups imported from JDE EnterpriseOne Items to the quote/order being created. If
the integration is configured to map all revenue lines and if at least one does not
map then an error is returned.
Revenue mapping is controlled by the "enforceRevenueLineMapping" integration
configuration parameter. For more information on configuring this parameter, see
Connecting Oracle Sales Cloud to JDE EnterpriseOne.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
13
Introduction
▪ Integration Process Flows
5. The quote/order creation process calls the SalesOrderManager published business
service which calls the processSalesOrderV5 method. The method returns the new
quote/order number from JDE EnterpriseOne.
6. The quote/order creation status, which includes the quote/order number, is updated
in the Opportunity. This status does not persist with the Opportunity.
For additional information about quote and sales order configuration and processing
in the EnterpriseOne system, see the JD Edwards EnterpriseOne Applications Sales
Order Management Implementation Guide. You can access this guide on the SCM
and MFG tab of the JD Edwards EnterpriseOne Applications Documentation Library,
located at: http://docs.oracle.com/cd/E16582_01/index.htm.
Importing JDE EnterpriseOne Items to Oracle Sales Cloud Catalog
To allow you to take advantage of the Oracle Sales Cloud opportunity to JDE
EnterpriseOne quote and order integration, you must first import all JDE EnterpriseOne
Items into the Oracle Sales Cloud Catalog. These imported Items will then be used when
creating revenue lines in Oracle Sales Cloud opportunities.
For additional information about the Item Batch Outbound program (R4101ZO) used to
create the item XML file, see the Item Master chapter in the JD Edwards EnterpriseOne
Applications Business Interface Implementation Guide. You can access this guide on the
Cross-Product tab of the JD Edwards EnterpriseOne Applications Documentation Library,
located at: http://docs.oracle.com/cd/E16582_01/index.htm.
Detailed Item Import Process
When a user first exports a JDE EnterpriseOne items list to XML:
1. The user processes the export XML file using a provided script to transform the file to
the format expected by the Oracle Sales Cloud File Import process.
2. The user creates a new top level JDE EnterpriseOne Catalog Product Group in
Oracle Sales Cloud. All JDE EnterpriseOne items included in the XML file will be
imported into this product group.
NOTE: This step only needs to be performed only once during the initial import.
3. The user starts a new Product Group file import using the XML file generated in step 1.
You can repeat this process as needed to import changes to JDE EnterpriseOne
items into Oracle Sales Cloud product catalog.
JDE EnterpriseOne item export is done using UTF-8 character encoding.
For more information on how to complete these steps, see Postconfiguration Tasks.
Viewing Reports in JDE EnterpriseOne
The integration also exposes two JDE EnterpriseOne One View Reporting (OVR) reports
which are called Open Sales Analysis and Sales by Opportunity. These reports are
generated using the Oracle Sales Cloud customer context. They are accessed from
within the Oracle Sales Cloud Account Details screen once the Account has been
14
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Introduction
▪ Configuration Roadmap
synchronized with JDE EnterpriseOne and show specific data, similar to that shown in the
following graphic.
For additional information about the One View reports used to view sales opportunity
information, see the One View Reporting for Sales Order Management chapter in the JD
Edwards EnterpriseOne Applications One View Reporting User Guide. You can access
this guide on the One View tab of the JD Edwards EnterpriseOne Applications
Documentation Library, located at: http://docs.oracle.com/cd/E16582_01/index.htm.
Configuration Roadmap
To leverage this integration, application artifacts must be configured in Oracle Sales
Cloud and the required ESU updates applied in JDE EnterpriseOne. In the Oracle Sales
Cloud instance, custom Groovy logic must be added to the system, custom objects
created, and standard objects enhanced. These steps must be executed in order,
because many of them rely on the successful completion of previous steps. Figure 5
shows a high-level overview of the configuration sequence.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
15
Introduction
▪ Configuration Roadmap
Figure 5. High-level Overview of the Configuration Sequence
Many of the Oracle Sales Cloud configuration steps in Chapter 3 have several
component procedures, such as creating sandboxes, creating or augmenting objects,
defining fields, defining business logic with functions, defining rules or triggers, and
defining user interface changes. These component procedures are used in many
different configuration steps, but not all procedures are used in all steps. For example,
the procedure to create an object or the process to define a trigger is the same from
one step to the next, but the names and details of the objects or triggers will change
from step to step.
In this document, the general process for each component procedure is listed before
the specific objects that are to be created or customized. The topics for the specific
16
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Introduction
▪ Configuration Roadmap
objects provide details on each of the configuration steps, and which component
procedures and details are required in each step.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
17
2
JDE EnterpriseOne Configuration
This chapter details the steps required for configuring JDE EnterpriseOne to enable the
Oracle Sales Cloud to JDE EnterpriseOne integration.
NOTE: You must have administrative access to JDE EnterpriseOne to configure it.
Software Requirements for JDE EnterpriseOne
The supported release level for this integration is JD Edwards EnterpriseOne Applications
release 9.1 with JD Edwards EnterpriseOne Tools release 9.1.2.0 or higher.
For the list of supported web browsers for JD Edwards EnterpriseOne release 9.1, see
Certification for JD Edwards EnterpriseOne Web Client for Release 9.1.2.0 on My Oracle
Support.
Applying the JDE EnterpriseOne Electronic Software Update (ESU)
Install the required JDE EnterpriseOne Electronic Software Updates from JD Edwards
EnterpriseOne Update Center. Make sure you build and deploy the BSSV package with
JAX-WS option ONLY.
To apply the JDE EnterpriseOne Electronic Software Update
1. Access the JDE EnterpriseOne Update Center is at the following location:
https://updatecenter.oracle.com/apps/WebSearch/updatecenter.jsp?
2. Perform a search for the following required updates which you must apply:
A. Perform a search for an ESU which contains Bug 17848773 (Electronic Software
Updates type on the Update Center)
B. Perform a search for an ESU which contains Bug 18862946 (One View
Reporting|E1 Pages type on the Update Center)
An example an ESU search result is show in Figure 6.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
19
JDE EnterpriseOne Configuration
▪ Upgrading to JDE Tools Release 9.1.4.7
Figure 6. Example of ESU Search Results for Bug 17848773
Figure 7. Example of ESU Search Results for Bug 18862946
Upgrading to JDE Tools Release 9.1.4.7
It is recommended that you upgrade your JDE Tools version to version 9.1.4.7 to resolve
known issues with the embedded UI. You can upgrade your tools maintenance pack by
navigating to EnterpriseOne Tools Releases on My Oracle Support:
https://updatecenter.oracle.com/apps/WebSearch/updatecenter.jsp?action=news
&pkgType=06
If you do not want to upgrade your JDE Tools pack, verify the expiration against the
Tools release version you are currently using. If you are using a supported release,
contact JDE support for an engineered fix (POC) for the following bugs:
18186551,18451145, and 18186594.
NOTE: You should apply this POC if you are using Internet Explorer 9 or above, or any
supported release of Firefox, or Chrome browser.
20
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
JDE EnterpriseOne Configuration
▪ Setting the Default Branch Plant Value
Setting the Default Branch Plant Value
You must set the default branch plant for JDE EnterpriseOne Sales Order Entry, and One
View Report processing applications.
Before you begin configuring Oracle Sales Cloud for the integration, you must set the
following processing option values in the JDE EnterpriseOne system.
To set JDE EnterpriseOne processing option values
1. Set the Default Branch/Plant option in the Sales Order Entry program (P4210) as
shown below.
In the Default Branch/Plant option on the Default tab of the Sales Order Entry (P4210)
processing options. For additional information about these processing options, see
Setting Processing Options for Sales Order Entry (P4210) in the JD Edwards
EnterpriseOne Applications Sales Order Management Implementation Guide. You
can access this guide on the SCM and MFG tab of the JD Edwards EnterpriseOne
Applications Documentation Library, located at:
http://docs.oracle.com/cd/E16582_01/index.htm.
Figure 8. Sales Order Entry Program Default Branch/Plant option
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
21
JDE EnterpriseOne Configuration
▪ Setting the Default Branch Plant Value
2. Set the Branch Plant – Detail and the Order Company (Order Number) options on
both the Open Sales Inquiry program (P42270), and the One View Sales To Date
program (P42272) as shown below.
For additional information about the One View report processing options, see the
One View Reporting for Sales Order Management chapter in the JD Edwards
EnterpriseOne Applications One View Reporting User Guide. You can access this
guide on the One View tab of the JD Edwards EnterpriseOne Applications
22
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
JDE EnterpriseOne Configuration
▪ Setting the Default Branch Plant Value
Documentation Library, located at:
http://docs.oracle.com/cd/E16582_01/index.htm.
Figure 9. Branch Plant – Detail and Order Company (Order Number)
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
23
3
Oracle Sales Cloud
Configuration
This chapter details the steps required for configuring Oracle Sales Cloud to enable the
Oracle Sales Cloud to JDE EnterpriseOne integration.
Before You Configure Oracle Sales Cloud
Before configuring Oracle Sales Cloud, you must ensure you have fulfilled the software
requirements listed in Software Requirements for JDE EnterpriseOne.
Software Requirements for Oracle Sales Cloud
The integration is designed to work with Oracle Sales Cloud Release 8.
For the list of supported web browsers for Oracle Sales Cloud, see:
http://www.oracle.com/us/products/system-requirements/overview/index.html
Creating References to JDE EnterpriseOne
You must create Sales Cloud references to the JDE EnterpriseOne web services required
for the integration. This is performed in the Application Composer.
When registering the first web service reference in Oracle Sales Cloud, you must create
a new credential key, which Oracle Sales Cloud will use to authenticate the web service
calls to JDE EnterpriseOne. Choose a JDE EnterpriseOne administrative user account. All
web service calls will be executed by authenticating as this user.
Creating Web Service References
You must create web service references using the Sales application. You create web
service references in the Application Composer after choosing the Sales application.
To create Web service references for the Sales application
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Sales from the Application drop-down menu.
3. Click Web Services on the Overview page.
4. Click the Create Web Service Reference icon on the Web Service page.
5. Enter the name and WSDL for the CustomerManager web service reference as
shown, then click Read WSDL.
Field
Value
Name
O_INT_JDE_CustomerManager
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
25
Oracle Sales Cloud Configuration
▪ Using Sandboxes
Field
Value
WSDL
https:// <host>:<port>/<server>/CustomerManager?wsdl
6. Fill in or confirm the following fields, then click Save and Close.
Field
Value
Service
CustomerManagerService
Port
CustomerManagerPort
Security Scheme
Invoke with separate user credentials over SSL
Credential Key
JDE_<username>_KEY
Disable timestamp
verification
Select the checkbox.
7. Repeat steps 4 through 6 for the following web service reference:
A. SalesOrderManager
Field
Value
Name
O_INT_JDE_SalesOrderManager
WSDL
https://<host>:<port>/<server>/SalesOrderManager?wsdl
Service
SalesOrderManagerService
Port
SalesOrderManagerPort
Security Scheme
Invoke with separate user credentials over SSL
Credential Key
JDE_<username>_KEY
Disable timestamp
verification
Select the checkbox.
Using Sandboxes
Sandboxes in Oracle Fusion Applications provide functionality to help isolate and control
customization efforts without impacting other users’ configuration environments or the
production environment. Subsequent configuration steps in the Oracle Sales Cloud to
JDE EnterpriseOne integration require the use of sandboxes to test configurations before
publishing them. For more information on using sandboxes, see Article ID 1484889.1 on
My Oracle Support.
26
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating Functions
Creating Sandboxes
You create sandboxes under the Administration menu at the top right of the screen.
To create a sandbox
1. Navigate to Manage Sandboxes by doing the following:
A. In the top right corner of the screen beside your login name, click the dropdown list.
B. Under Administration, select Manage Sandboxes.
2. Click the New icon.
3. In the Create Sandbox dialog, name the new sandbox, and then click Save and
Close.
4. After you see the newly created sandbox in the list, click in the sandbox row (not on
the name link), and then click Set as Active.
This activates the new sandbox.
5. Log out, then log back in to start using the sandbox.
Validating Sandboxes
To validate changes made in a sandbox, test them by using the added Oracle Sales
Cloud functionality.
Publishing Sandboxes
To publish a sandbox
1. Make sure the sandbox is currently active.
2. Click the sandbox link.
The Sandbox Details window appears.
3. Click Publish.
4. Log out, then log back in.
The changes in the sandbox are published so that they are viewable by all users.
Creating Functions
There are two types of functions:
•
Global Functions. Global functions work in all applications in Oracle Sales Cloud that
have extensibility enabled. They are created under the Common Setup section in
the Application Composer.
•
Object Functions. Object functions are attached to a specific object. They are
created in the Object Functions tab of the Server Scripts section of the object
definition in the Application Composer.
Each function for the Oracle Sales Cloud to JDE EnterpriseOne integration is defined in a
Groovy script file. At the top of each file, a set of comments lists, in the following order:
•
Function name
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
27
Oracle Sales Cloud Configuration
▪ Creating Functions
•
Function return type
•
Function parameters (one per line)
Following the comments, the body of the function is listed.
Creating Global Functions
The global functions for the integration are defined in the following Groovy script files:
•
O_INT_ApplyFilter.groovy
•
O_INT_AddMultiValueCriteriaItem.groovy
•
O_INT_Debug.groovy
•
O_INT_Error.groovy
•
O_INT_FindRowByKey.groovy
•
O_INT_GetLogMsg.groovy
•
O_INT_GetRecordCount.groovy
•
O_INT_GetRecords.groovy
•
O_INT_GetSysParam.groovy
•
O_INT_Info.groovy
•
O_INT_JDE_ConstructErrorPageURL
•
O_INT_JDE_GetLogMsg.groovy
•
O_INT_JDE_GetSysParam.groovy
•
O_INT_JDE_LogWithException
•
O_INT_Log.groovy
•
O_INT_LogMessage.groovy
•
O_INT_Warn.groovy
The content of the Groovy files must be entered into Oracle Sales Cloud using the
Application Composer. Before setting up global functions, create a sandbox and
activate it. For more information, see Creating Sandboxes.
To create a global function
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. In the Overview window, click Global Functions.
3. For each Groovy script file:
A. Select the row, then click the Action drop-down list, and select Add.
The Create Global Function window appears.
B. In the Function Name field, enter the function name from the first comment in
the Groovy file.
C. From the Returns drop-down menu, select the return type specified in the
second comment in the Groovy file.
D. In the Parameters list, click the Action drop-down list, then click the Add icon.
28
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating Functions
E. Enter the name and type for the first parameter listed in the comments in the
Groovy file.
F. Repeat steps D and E for the remaining parameters.
G. Copy the Groovy code from the file into the Function Body window.
H. Click Validate to validate the function.
NOTE: When validating, certain functions will trigger a warning. This is expected; you
can click OK to continue. However, if an error is generated, then contact Oracle
Global Customer Support.
I.
Click Save and Close.
Creating Object Functions
The object functions for the integration are defined in Groovy script files. These files are
listed under the specific objects to be created or customized. Use the following general
procedure to create object functions.
To create an object function
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select the application from the Application drop-down menu.
3. Under the Objects menu, expand the Standard Objects or Custom Objects node,
expand the object for which you want to create a function, and then click Server
Scripts.
4. In the Server Scripts window, click the Object Functions tab.
5. For each Groovy script file:
A. Click the Action drop-down list, and select Add.
The Create Object Function window appears.
B. In the Function Name field, enter the function name from the first comment in
the Groovy file.
C. From the Returns drop-down menu, select the return type specified in the
second comment in the Groovy file.
D. In the Parameters list, click the Add Parameter icon.
E. Enter the name and type for the first parameter listed in the comments in the
Groovy file.
F. Repeat for the remaining parameters.
G. Copy the Groovy code from the file into the Function Body window.
H. Click Validate to validate the function.
NOTE: When validating, certain functions will trigger a warning. This is expected; you
can click OK to continue. However, if an error is thrown, then contact Oracle Global
Customer Support.
I.
Click Save and Close.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
29
Oracle Sales Cloud Configuration
▪ Creating Validation Rules
Creating Validation Rules
Validation rules are created in the Object Functions tab of the Server Scripts section of
the object definition in the Application Composer.
Validation rules for the Oracle Sales Cloud to JDE EnterpriseOne integration are defined
in Groovy script files. At the top of each file, a set of comments lists, in the following
order:
•
Name
•
Description
•
Error message
Following the comments, the body of the rule is listed.
The Groovy files are listed under the rules to be created for specific objects. Use the
following general procedure to create validation rules for objects.
To create an object validation rule
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select the application from the Application drop-down menu.
3. Under the Objects menu, expand the Standard Objects or Custom Objects node,
expand the object for which you want to create a validation rule, and then click
Server Scripts.
In the Server Scripts window, the Validation Rules tab is shown by default.
4. Under Object Rules, click the Add a new validation rule icon.
The Create Object Validation Rule window appears.
5. Under Name, enter the rule name and description from the comments in the Groovy
file.
6. Under Error Message, enter the error message from the comments in the Groovy file.
7. Copy the Groovy code from the file into the Rule Definition window.
8. Click Save and Close.
Creating Custom Objects
Create a sandbox for each custom object. After creating each custom object, validate
the object and publish the sandbox before moving on to the next custom object. Only
create a new sandbox after publishing the previous one. Never have two sandboxes
active at the same time.
Creating a Custom Object
You create the custom object in the Application Composer.
To create the custom object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
30
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating Custom Objects
2. Select the application from the Application drop-down menu.
3. Click Custom Objects in the Overview window.
4. In the Custom Objects list, click the Create a New Object icon.
5. In the Create Custom Object dialog, enter the object information, and then click
OK.
The custom object appears in the Custom Objects list under the Objects menu.
Adding Fields to a Custom Object
You add fields using the Fields link under the custom object in the Application
Composer.
To add a field to a custom object
1. Expand the custom object’s node in the Custom Objects list under the Object menu.
2. Click Fields.
3. On the Fields page, click the Create a custom field icon.
4. In the Select Field Type dialog, click the appropriate radio button for the field type,
and then click OK.
5. In the Create Object_Type Field window, enter the parameters, and then click OK.
6. Repeat steps 3 through 5 for other fields as necessary.
Creating Pages for a Custom Object
After you create a custom object and add fields to it, you create pages expose the
new object and fields to users. Every top-level Oracle Sales Cloud object has an
overview page, a creation page, and a details page. These pages make up a work
area. You use an object’s Desktop Pages tab in the Application Composer to create
pages.
To create pages
1. Expand the custom object’s node in the Custom Objects list under the Object menu.
2. Click Pages.
3. On the Object_Name: Pages page, click the Create Work Area link on the Desktop
Pages tab.
4. In the Create Navigator Menu and Regional Search window:
A. Select the menu category from the drop-down menu.
B. Enter the menu item display label in the field.
C. Under Configure Regional Search, deselect the Enable checkbox.
D. Click Next.
5. In the Configure Search window, select the fields to appear in the local search, then
click Next.
6. In the Configure Overview and Creation Pages window:
A. Under Configure Summary Table, select the drilldown column for the summary
table and the fields you want to appear as columns in the summary table.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
31
Oracle Sales Cloud Configuration
▪ Creating the Integration Configuration Custom Object
B. Under Configure Summary Table: Buttons and Actions, select the appropriate
checkboxes.
C. Under Configure Creation Page, select the fields to appear on the creation
page.
D. Click Next.
7. In the Configure Details Page Summary window:
A. Under Configure Default Summary, select the fields to appear in the default
summary.
B. Under Configure Detailed Summary, select the fields to appear in the detailed
summary.
C. Click Save and Close.
Defining Security Policies for a Custom Object
Sales representatives are the primary users who access application areas such as
Customer Center and Sales, and use the features provided in this integration. To allow
sales representatives access to the features of this integration, you must grant the
necessary privileges to the Sales Representative Duty role using the Application
Composer. The privileges to be granted are listed under the specific objects to be
created or customized.
NOTE: You must log in as a user with the Customer Relationship Management
Application Administrator role to define security policies.
To define security policies for a custom object
1. Expand the custom object’s node in the Custom Objects list under the Object menu.
2. Click Security.
3. On the Define Policies: Object_Name page, locate the Sales Representative Duty
role.
4. Select the appropriate check boxes for the privileges you wish the role to have for
the object, then click Save and Close.
Creating the Integration Configuration Custom Object
You create the Integration Configuration custom object in the Common application.
Use a new sandbox for the Integration Configuration object.
Creating the Object
Fill in the parameters shown in Table 1 for the Integration Configuration custom object,
using the procedure in Creating a Custom Object.
Table 1. Parameters for the Integration Configuration Custom Object
Parameter
Value
32
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating the Integration Configuration Custom Object
Parameter
Value
Display Label
Integration Configuration
Plural Label
Integration Configuration
Record Name Label
Integration Configuration ID
Record Name Data Type
Select Automatically Generated Sequence
from the drop-down menu.
Sequence Format
{000000000000000} (15 zeroes inside braces)
Object Name
O_INT_IntegrationConfig
Description
Leave blank.
Creating Fields
Create the fields shown in Table 2 for the Integration Configuration custom object, using
the procedure in Adding Fields to a Custom Object.
Table 2. Fields in the Integration Configuration Custom Object
Field
Parameter
Key
RemoteSystemID
Value
Field Type
Text
Text
Text
Display Label
Key
Remote System
Value
Name
Key
RemoteSystemID
Value
Display Width
20
20
50
Display Type
Simple Text Box
Simple Text Box
Simple Text Box
Constraints
•
Required
•
Required
•
Required
•
Updateable
•
Updateable
•
Updateable
•
Searchable
•
Searchable
•
Searchable
•
Indexed
•
Indexed
Maximum Length
100
80
500
Creating Pages
Create the pages shown in Table 3 under the Desktop Pages tab in the Application
Composer, using the procedure in Creating Pages for a Custom Object.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
33
Oracle Sales Cloud Configuration
▪ Creating the Integration Configuration Custom Object
Table 3. Pages in the Integration Configuration Custom Object
Page
Item
Value
Configure Navigator Menu
and Regional Search
Menu Category
Tools
Menu Item Display Label
Integration Configuration
Enabled
Deselect the checkbox.
Selected Fields
Remote System
Configure Search
Configure Overview and Creation Pages
Configure Summary Table
Drill Down Column
Remote System
Selected Fields
•
Remote System
•
Key
•
Value
Buttons and Actions
Configure Creation Page
Selected Fields
Select the checkboxes for:
•
Show Create
•
Show Edit
•
Show Delete
•
Integration
Configuration ID
•
Remote System
•
Key
•
Value
•
Remote System
•
Key
•
Value
•
Integration
Configuration ID
•
LastUpdateBy
•
LastUpdateDate
Configure Details Page Summary
Configure Default Summary
Configure Detailed
Summary
Selected Fields
Selected Fields
Defining Security Policies
Assign the following privileges for the Integration Configuration custom object to the
Sales Representative Duty role, using the procedure in Defining Security Policies for a
Custom Object:
34
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
•
View
•
View All
▪ Creating the XREF Custom Object
Creating the Validation Rule
Create the object validation rule from the UniqueKey.groovy file, using the procedure in
Creating Validation Rules.
Creating Global Functions
Create global functions from the following Groovy files, using the procedure in Creating
Global Functions:
•
O_INT_GetIntegConfigParameter.groovy (returns a specific parameter for a
category)
•
O_INT_GetIntegConfigParameters.groovy (returns all parameters for a category)
NOTE: These global functions depend on the Integration Configuration custom object
being created, so they were not created previously in Creating Global Functions.
Validating and Publishing the Sandbox
Validate and publish the sandbox for the Integration Configuration custom object, using
the procedures in Using Sandboxes.
Creating the XREF Custom Object
You create the XREF custom object in the Common application. Use a new sandbox for
the XREF custom object.
Creating the Object
Fill in the parameters shown in Table 4 for the Integration Configuration custom object,
using the procedure in Creating a Custom Object.
Table 4. Parameters for the XREF Custom Object
Parameter
Value
Display Label
Plural Label
XREF
XREF
Record Name Label
XREF ID
Record Name Data
Type
Select Automatically Generated Sequence
from the drop-down menu.
Sequence Format
{000000000000000} (15 zeroes inside braces)
Object Name
O_INT_XREF
Description
Leave blank.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
35
Oracle Sales Cloud Configuration
▪ Creating the XREF Custom Object
Creating Fields
Create the fields shown in Table 5 and Table 6 for the XREF custom object, using the
procedure in Adding Fields to a Custom Object.
Table 5. Fields in the XREF Custom Object
Field
Parameter
FusionObjectType
FusionRecordID
RemoteObjectType
Field Type
Text
Text
Text
Display Label
Fusion Object Type
Fusion Record ID
Remote Object Type
Name
FusionObjectType
FusionRecordID
RemoteObjectType
Display Width
20
20
20
Display Type
Simple Text Box
Simple Text Box
Simple Text Box
Constraints
•
Required
•
Required
•
Required
•
Updateable
•
Updateable
•
Updateable
•
Searchable
•
Searchable
•
Searchable
•
Indexed
•
Indexed
•
Indexed
Maximum Length
100
50
100
Table 6. More Fields in the XREF Custom Object
Field
Parameter
RemoteRecordID
RemoteSystemID
Field Type
Text
Text
Display Label
Remote Record ID
Remote System
Name
RemoteRecordID
RemoteSystemID
Display Width
20
20
Display Type
Simple Text Box
Simple Text Box
Constraints
•
Required
•
Required
•
Updateable
•
Updateable
•
Searchable
•
Searchable
•
Indexed
•
Indexed
36
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating the JDE Match Child Object
Field
Parameter
RemoteRecordID
RemoteSystemID
Maximum Length
50
80
Defining Security Policies
Assign the following privileges for the XREF custom object to the Sales Representative
Duty role, using the procedure in Defining Security Policies for a Custom Object:
•
View
•
View All
•
Update
•
Update All
•
Delete
•
Create
Creating Global Functions
Create global functions from the following Groovy files, using the procedure in Creating
Global Functions:
•
O_INT_CreateXREF.groovy
•
O_INT_GetAllXREF.groovy
•
O_INT_GetXREF.groovy
•
O_INT_UpdateXREF.groovy
NOTE: These global functions depend on the XREF custom object being created, so
they were not created previously in Creating Global Functions.
Validating and Publishing the Sandbox
Validate and publish the sandbox for the XREF custom object, using the procedures in
Using Sandboxes.
Creating the JDE Match Child Object
You create JDE Match as a child object of the Account standard object.
NOTE: You perform the Customizing the Account Standard Object, and Customizing
the JDE Match Child Object procedures in the same sandbox, validate the
customizations, and then publish the sandbox. For more information, see Using
Sandboxes.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
37
Oracle Sales Cloud Configuration
▪ Creating the JDE Match Child Object
Creating the Child Object
Use the following procedure to create the JDE Match child object. Creating a child
object is similar to Creating a Custom Object, but you also complete the Child
Collection Name field to specify the internal name for the set of child object records.
To create the JDE Match child object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Common from the Application drop-down menu.
3. Under the Objects menu, expand the Standard Objects node, and then select
Account.
The Account: Overview page appears.
4. Under Child Objects in the Account: Overview window, click Create Child Object.
5. In the Create Custom Child Object dialog, enter the object information shown in
Table 7, and then click OK.
Table 7. Parameters for the JDE Match Child Object
Parameter
Value
Display Label
Plural Label
JDE Match
JDE Match
Record Name Label
JDE Match ID
Record Name Data Type
Select Automatically Generated Sequence
from the drop-down menu.
Sequence Format
{000000000000000} (15 zeroes inside braces)
Object Name
O_INT_JDE_Match
Description
Leave blank.
Child Collection Name
O_INT_JDE_MatchCollection
Adding Fields to the Child Object
Create the fields shown in Table 8 through Table 12 for the JDE Match child object, using
the following procedure.
To add a field to the JDE Match child object
1. In the Application Composer, expand the Account node in the Standard Objects list
under the Object menu.
2. Click JDE Match under Child Objects in the Account: Overview window, then
expand the JDE Match node under the Custom Objects list.
3. Click Fields.
38
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating the JDE Match Child Object
4. On the Fields page, click the Create a custom field icon.
5. In the Select Field Type dialog, click the appropriate radio button for the field type,
and then click OK.
6. In the Create Object_Type Field window, enter the parameters, and then click OK.
7. Repeat steps 4 through 6 for other fields as necessary.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
39
Oracle Sales Cloud Configuration
▪ Creating the JDE Match Child Object
Table 8. Fields in the JDE Match Child Object
Field
Parameter
Address1
City
State
Province
Field Type
Text
Text
Text
Text
Display Label
Address Line 1
City
State
Province
Name
Address1
City
State
Province
Display Width
20
20
20
20
Display Type
Simple Text Box
Simple Text Box
Simple Text Box
Simple Text Box
Constraints
•
Updateable
•
Updateable
•
Updateable
•
Updateable
•
Searchable
•
Searchable
•
Searchable
•
Searchable
Maximum Length
80
80
80
80
Table 9.More Fields in the JDE Match Child Object
Parameter
PostalCode
Country
Selected
Field Type
Text
Text
Checkbox
Display Label
Postal Code
Country
Selected
Name
PostalCode
Country
Selected
Display Width
8
20
Not applicable.
Display Type
Simple Text Box
Simple Text Box
Not applicable.
Constraints
•
Updateable
•
Updateable
•
Searchable
•
Searchable
Maximum
Length
15
80
•
Updateable (Adding
the Constraint
Expression for the
Selected Check Box)
•
Searchable
Not applicable.
40
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating the JDE Match Child Object
Table 10. Still More Fields in the JDE Match Child Object
Parameter
Field
PartyName
PartyID
PartyType
Field Type
Text
Text
Text
Display Label
Party Name
Party ID
Party Type
Name
PartyName
PartyID
PartyType
Display Width
100
20
20
Display Type
Simple Text Box
Simple Text Box
Simple Text Box
Constraints
•
Updateable
•
Updateable
•
Updateable
•
Searchable
•
Searchable
•
Searchable
Maximum Length
200
80
80
Table 11. Yet More Fields in the JDE Match Child Object
Field
Parameter
IndustryClassification
PrimaryPhoneAreaCode
Field Type
Text
Text
Display Label
Industry Classification
Primary Phone Area Code
Name
IndustryClassification
PrimaryPhoneAreaCode
Display Width
10
20
Display Type
Simple Text Box
Simple Text Box
Constraints
•
Updateable
•
Updateable
•
Searchable
•
Searchable
Maximum Length
80
80
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
41
Oracle Sales Cloud Configuration
▪ Customizing Standard Objects
Table 12. Final Fields in the JDE Match Child Object
Field
Parameter
PrimaryPhoneNumber
PrimaryEmail
Field Type
Text
Text
Display Label
Primary Phone Number
Primary Email
Name
PrimaryPhoneNumber
PrimaryEmail
Display Width
20
20
Display Type
Simple Text Box
Simple Text Box
Constraints
•
Updateable
•
Updateable
•
Searchable
•
Searchable
Maximum Length
80
80
Adding the Constraint Expression for the Selected Check Box
After creating and saving the Selected check box, you edit it to add an expression to
the Updateable constraint.
To add an expression to the Updateable constraint for the Selected check box
1. After adding fields to the JDE Match Child object, click the link for the Selected
check box on the Fields page.
2. In the Edit Checkbox Field: Selected window, click the Expression Builder icon next to
the Updateable check box under Constraints.
The Expression Builder appears, with the Functions tab displayed by default.
3. In the expression window, enter the following text:
Selected_c == null || Selected_c == 'N'
4. Click OK.
5. In the Edit Checkbox Field: Selected window, click Save and Close.
Defining Security Policies
Assign the following privileges for the JDE Match custom object to the Sales
Representative Duty role, (revoke any other privileges which may have already been
assigned) using the procedure in Defining Security Policies for a Custom Object:
•
Create
Customizing Standard Objects
You customize standard objects in the Application Composer.
42
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing Standard Objects
Adding Fields to a Standard Object
Adding fields to a standard object is very similar to Adding Fields to a Custom Object.
To add a field to a standard object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select the application from the Application drop-down menu.
3. Expand the object’s node in the Standard Objects list under the Object menu.
4. Click Fields.
5. On the Fields page, click the Create a custom field icon.
6. In the Select Field Type dialog, select the appropriate radio button for the field type,
and then click OK.
7. In the Create Object_Type Field window, enter the parameters, and then click OK.
8. Repeat steps 5 through 7 for other fields as necessary.
Adding Actions and Links to an Object
Use the following procedure to add actions and links to an object.
To add an action or link to an object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select the application from the Application drop-down menu.
3. Expand the object’s node in the Standard Objects or Custom Objects list under the
Object menu.
4. Click Actions and Links.
5. On the Object_Name: Actions and Links page, click the Create icon.
6. Enter the display label, name, and description.
7. Select the type, Action or Link.
8. Select the source:
•
•
Script. Select a method name, or click the New icon to enter a new object
function.
URL. Define a URL expression.
9. Click Save.
10. Repeat steps 5 through 9 to add other actions or links as necessary.
Creating Triggers for an Object
Triggers are created in the Triggers tab of the Server Scripts section of the object
definition in the Application Composer.
Triggers for the Oracle Sales Cloud to JDE EnterpriseOne integration are generally
defined in Groovy script files. At the top of each file, a set of comments lists, in the
following order:
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
43
Oracle Sales Cloud Configuration
•
Type (object or field)
•
Trigger
•
Name
•
Error message
▪ Customizing the Account Standard Object
Following the comments, the trigger definition is listed.
The Groovy files are listed under the triggers to be created for specific objects. Use the
following general procedure to create triggers for objects.
To create a trigger
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select the application from the Application drop-down menu.
3. Under the Objects menu, expand the Standard Objects or Custom Objects node,
expand the object for which you want to create a trigger, and then click Server
Scripts.
4. In the Server Scripts window, click the Triggers tab.
5. Click the Add a new Trigger icon under either Object Triggers or Field Triggers.
The Create Object Trigger or Create Field Trigger window appears.
6. Under Trigger, select the trigger from the drop-down menu, and then enter the
name.
The trigger and name come from the second and third comments in the Groovy file,
respectively.
7. Under Error Message, enter the error message, if any is provided.
8. Copy or enter the Groovy code from the file into the Trigger Definition window.
9. Click Save and Close.
Customizing the Account Standard Object
You make changes to the Account object under the Common application.
Adding Fields
Add the fields shown in Table 13 to the Account standard object, using the procedure in
Adding Fields to a Standard Object.
Table 13. Fields Added to the Account Object
Field
Parameter
JDE Sync Status
Field Type
Text
Display Label
JDE Sync Status
44
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing the Account Standard Object
Field
Parameter
JDE Sync Status
Name
O_INT_JDE_Sync_Status
Display Width
Leave blank.
Display Type
Simple Text Box
Constraints
Updateable (Constraint
Expression: false)
Maximum Length
25
Default Value
Fixed Value =
Not Synchronized
Creating Global Functions
Create functions from the following Groovy files, using the procedure in Creating Global
Functions:
•
O_INT_JDE_GetBaseURL.groovy
•
O_INT_JDE_GenerateSalesDocumentURL.groovy
Creating Object Functions
Create functions from the following Groovy files, using the procedure in Creating Object
Functions:
•
O_INT_JDE_CheckMatch.groovy
•
O_INT_JDE_CleanupMatches.groovy
•
O_INT_JDE_CreateCustomer.groovy
•
O_INT_JDE_CustomerOrderURL.groovy
•
O_INT_JDE_CustomerQuoteURL.groovy
•
O_INT_JDE_CustomerReportURL.groovy
•
O_INT_JDE_CustomerSalesDocumentURL.groovy
•
O_INT_JDE_CustomerSync.groovy
•
O_INT_JDE_GetSearchCriteria.groovy
•
O_INT_JDE_OpenSalesAnalysisURL.groovy
•
O_INT_JDE_PopulateMatches.groovy
•
O_INT_JDE_SalesByOpportunityURL.groovy
•
O_INT_JDE_SearchCustomer.groovy
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
45
Oracle Sales Cloud Configuration
▪ Customizing the Account Standard Object
Creating the Action
Add the Perform JDE Sync action shown in Table 14 to the Account object, using the
procedure in Adding Actions and Links to an Object.
Table 14. Action for the Account Object
Parameter
Value
Display Label
Perform JDE Sync
Name
Perform_JDE_Sync
Type
Action
Description
Leave blank.
Source
Script
Method Name
O_INT_JDE_CustomerSync
Creating the Validation Rule
Create a validation rule from the O_INT_JDE_MatchSelectRule.groovy file, using the
procedure Creating Validation Rules, and the information from the following table.
Table 15. Validation Rule Information for Sales Account Object
Parameter
Value
Rule Name
O_INT_JDE_MatchSelectRule
Error Message
Only one JDE customer record should be marked as
selected after manual matching.
Rule Definition
O_INT_JDE_MatchSelectRule.groovy
Creating the Triggers
Create a trigger called “After Changes Posted in Database” from the
O_INT_JDE_CleanupMatchesTrigger.groovy file, using the procedure in Creating Triggers
for an Object.
Customizing Desktop Pages
You modify desktop pages on the Desktop Pages table for the Sales Account standard
object in the Application Composer.
46
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing the JDE Match Child Object
To customize desktop pages for the Account standard object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Common from the Application drop-down menu.
3. Expand the Account node in the Standard Objects list under the Object menu.
4. Click Pages.
The Desktop Pages tab is shown by default.
5. On the Desktop Pages tab, click Edit Organization Details Region under the Details
Page area.
A. Under Configure Default Summary, move JDE Sync Status to the Selected Fields
list.
B. Under Configure Detail Form: Buttons and Actions, move Perform JDE Sync to the
Selected Buttons list.
C. Click Save and Close.
Customizing the JDE Match Child Object
After customizing the Sales Account object, you finish customizing the JDE Match child
object.
Creating the Object Function
Create object functions from the O_INT_JDE_ForceCreateNewCustomer.groovy file using
the procedure in Creating Object Functions.
Adding an Action to the Child Object
Add the Create New JDE Customer action shown in Adding Actions and Links to an
Object to the JDE Match child object, using the procedure in Adding Actions and Links
to an Object.
Table 16. Action for the JDE Match Child Object
Parameter
Value
Display Label
Create New JDE Customer
Name
Force_Create_New_Customer
Type
Action
Description
Leave blank.
Source
Script
Method Name
O_INT_JDE_ForceCreateNewCustomer
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
47
Oracle Sales Cloud Configuration
▪ Customizing Account Object Simplified Pages
Validating and Publishing the Sandbox
Validate and publish the sandbox for the JDE Match and Sales Account objects, using
the procedures in Using Sandboxes.
Customizing Account Object Simplified Pages
You modify simplified pages on the Simplified Pages tab for the Account standard
object in Application Composer.
Add the subtabs shown in Table 17 through Table 20 using the following procedure.
To customize simplified pages for the Sales Account standard object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Common from the Application drop-down menu.
3. Expand the Account node in the Standard Objects list under the Objects menu.
4. Click Pages.
5. Click the Simplified Pages tab.
6. Under Details Page Layouts, select Default Layout, then click the Edit Layout (pencil)
icon.
A. Under Subtabs Region, click the Subtab Profile icon.
B. In the Summary area, click the pencil icon to view the Configure Detail form.
C. Under Configure Detail Form, move JDE Sync Status to the Selected Fields list.
D. Click Save and Close.
7. Click the pencil icon next to the Actions and Save and Close button to view the
Configure Detail Form: Buttons and Actions page
A. Under the Available Actions, move Perform JDE Sync to the Selected Actions list.
B. Click Save and Close.
8. In the Subtabs Region area of the Edit Simplified Details Page, click the green Add
button (+ sign) in the bottom left of the area to add a new subtab.
9. In the Create Subtab page, select Web Content and click Next.
10. In the Create Subtab: Web Content page, enter the parameters listed in each of the
following tables, click Save and Close after creating each subtab, then return to
steps 7 through 9.
Table 17. Account Subtab JDE Quotes
Parameter
Value
Display Label
JDE Quotes
Source
URL
URL Definition
O_INT_JDE_CustomerQuoteURL()
48
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing Account Object Simplified Pages
Parameter
Value
Display Icon
Choose your preferred icon
Table 18. Account Subtab JDE Orders
Parameter
Value
Display Label
JDE Orders
Source
URL
URL Definition
O_INT_JDE_CustomerOrderURL()
Display Icon
Choose your preferred icon
Table 19. Account Subtab Open Sales Analysis
Parameter
Value
Display Label
Open Sales Analysis
Source
URL
URL Definition
O_INT_JDE_OpenSalesAnalysisURL()
Display Icon
Choose your preferred icon
Table 20. Account Subtab Sales by Opportunity
Parameter
Value
Display Label
Sales By Opportunity
Source
URL
URL Definition
O_INT_JDE_SalesByOpportunityURL()
Display Icon
Choose your preferred icon
11. In the Subtabs Region area of the Edit Simplified Details Page, click the green Add
button (+ sign) in the bottom left of the area to create a new child object.
12. In the Create Subtab page, select Child or related object and click Next.
13. In the Create Subtab: Child or Related Object page, enter the information shown in
the following table:
Table 21. Account Data Object Parameters
Parameter
Value
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
49
Oracle Sales Cloud Configuration
▪ Customizing the Sales Account Standard Object
Parameter
Value
Data Object
JDE Match
Display Label
JDE Customer Matches
Display Icon
Choose your preferred icon
14. In the Configure Summary Table area, move Selected, Party Name, Party ID, Address
Line 1, City, State, Postal Code, Country, and JDE Match ID to the Selected Fields list.
15. Under Configure Summary Table: Buttons and Actions, make sure the Show Edit
checkbox is selected, and unselect the Show Create and Show Delete checkboxes,
and move Create New JDE Customer to the Selected Buttons list, then click Save and
Close.
Customizing the Sales Account Standard Object
You make changes to the Sales Account object under the Customer application.
Creating Object Functions
Create functions from the following Groovy files, using the procedure in Creating Object
Functions:
•
O_INT_JDE_AccountOpenSalesAnalysisURL.groovy
•
O_INT_JDE_AccountOrderURL.groovy
•
O_INT_JDE_AccountQuoteURL.groovy
•
O_INT_JDE_AccountSalesByOpportunityURL.groovy
Customizing Desktop Pages
You modify desktop pages on the Desktop Pages table for the Sales Account standard
object in the Application Composer.
NOTE: The Customer Center tree nodes entered here will only be visible for Accounts of
type Customer. If an Account is of type Sales Prospect, then that Account will only be
visible in the Simplified UI in Oracle Sales Cloud.
To customize desktop pages for the Sales Account standard object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Customer Center from the Application drop-down menu.
3. Expand the Sales Account node in the Standard Objects list under the Object menu.
4. Click Pages.
The Desktop Pages tab is shown by default.
5. Click the Create icon under Tree Nodes.
A. On the Create Tree Node page, select Web content, then click Next.
50
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing the Sales Account Standard Object
B. On the Create Tree Node: Web Content page, enter the information in Table
22, click Save and Close after creating each entry, then repeat step 5 for all
tables Table 23 through Table 25.
Table 22. Account Data Object Parameters
Parameter
Value
Category
Sales
Tree Node Label
Quotes
Source
URL
URL Definition
O_INT_JDE_AccountQuoteURL()
6. Repeat step 5 and add information for each of the following tables:
Table 23. Account Data Object Parameters
Parameter
Value
Category
Sales
Tree Node Label
Orders
Source
URL
URL Definition
O_INT_JDE_AccountOrderURL()
Table 24. Account Data Object Parameters
Parameter
Value
Category
Sales
Tree Node Label
Open Sales Analysis
Source
URL
URL Definition
O_INT_JDE_AccountOpenSalesAnalysisURL()
Table 25. Account Data Object Parameters
Parameter
Value
Category
Sales
Tree Node Label
Sales By Opportunity
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
51
Oracle Sales Cloud Configuration
▪ Customizing the Opportunity Standard Object
Parameter
Value
Source
URL
URL Definition
O_INT_JDE_AccountSalesByOpportunityURL()
Customizing the Opportunity Standard Object
Create a new sandbox for customizing the Opportunity standard object, using the
procedure in Creating Sandboxes. You make the customizations under the Sales
application.
Adding Fields
Add the fields shown in Table 26 to the Opportunity standard object, using the
procedure in Adding Fields to a Standard Object.
Table 26. Fields Added to the Opportunity Object
Parameter
Sales Document Status Field
Field Type
Text
Display Label
Sales Document Status
Display Type
Simple Text Box
Name
O_INT_SalesDocumentStatus
Constraints
Updateable (Constraint Expression:
false)
Maximum
Length
80
Default Value
None
Creating Object Functions
Create functions from the following Groovy files, using the procedure in Creating Object
Functions:
•
O_INT_JDE_CreateOrder
•
O_INT_JDE_CreateQuote
•
O_INT_JDE_CreateSalesDocument
•
O_INT_JDE_OpptyOrderURL.groovy
52
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing the Opportunity Standard Object
•
O_INT_JDE_OpptyQuoteURL.groovy
•
O_INT_JDE_OpptySalesDocumentURL.groovy
Creating Actions
Add the actions shown in Table 27 and Table 28 to the Opportunity object, using the
procedure in Adding Actions and Links to an Object.
Table 27. Create_Opportunity_In_JDE Action
Parameter
Value
Display Label
Create Quote
Name
O_INT_JDE_CreateQuote
Type
Action
Description
Leave blank.
Source
Script
Method Name
O_INT_JDE_CreateQuote
Table 28. Create_Order_In_JDE Action
Parameter
Value
Display Label
Create Order
Name
O_INT_JDE_CreateOrder
Type
Action
Description
Leave blank.
Source
Script
Method Name
O_INT_JDE_CreateOrder
Customizing Desktop Pages
You modify desktop pages on the Desktop Pages tab for the Opportunity standard
object in the Application Composer.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
53
Oracle Sales Cloud Configuration
▪ Customizing the Opportunity Standard Object
To customize desktop pages for the Opportunity standard object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Sales from the Application drop-down menu.
3. Expand the Opportunity node in the Standard Objects list under the Objects menu.
4. Click Pages.
The Desktop Pages tab is shown by default.
5. On the Desktop Pages tab, click the Create icon under Opportunity Detail Tab.
6. On the Create Subtab page, select Web content, and then click Next.
7. On the Create Subtab: Web Content page, enter the information from the following
table, and then click Save and Close.
Parameter
Value
Display Label
Quotes
Source
URL
URL Definition
O_INT_JDE_OpptyQuoteURL()
8. Repeat steps 5 through 7 using the information from the following table.
Parameter
Value
Display Label
Orders
Source
URL
URL Definition
O_INT_JDE_OpptyOrderURL()
9. In the Opportunity: Pages screen, click Edit Summary Form under Details Page.
10. On the Edit Details Page Summary Form page:
A. Under Configure Detail Form: Buttons and Actions, move Create_Quote and
Create_Order to the Selected Buttons list.
B. Click Save and Close.
11. In the Opportunity: Pages screen, click Edit Summary Form under Details Page.
12. On the Edit Details Page Summary Form page:
A. Under Configure Default Summary, move Sales Document Status to the
Selected Fields list.
B. Click Save and Close.
Customizing Simplified Pages
You modify simplified pages on the Simplified Pages tab for the Opportunity standard
object in Application Composer.
Add the subtabs shown in Table 29 and Table 30 using the following procedure.
54
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Customizing the Opportunity Standard Object
To customize simplified pages for the Opportunity standard object
1. Navigate to Navigator, Tools, click Customization, and then select Application
Composer.
2. Select Sales from the Application drop-down menu.
3. Expand the Opportunity node in the Standard Objects list under the Objects menu.
4. Click Pages.
5. Click the Simplified Pages tab.
6. Under Details Page Layouts, select Default Layout, then click the Edit Layout (pencil)
icon.
7. On the Edit Simplified Details Page, below the Done button, click the Edit (pencil)
icon.
8. Move Create Quote and Create Order to the Selected Actions list, and click Save
and Close.
9. On the Edit Simplified Details Page, under the Subtabs Region, in the Summary area,
click the Edit (pencil) icon.
10. Under Configure Detail Form, move Sales Document Status to the Selected Fields list,
then click Save and Close.
11. On the Edit Simplified Details Page, in the Subtabs Region area, click the green Add
button (+ sign) in the bottom left of the area to add a new subtab.
12. In the Create Subtab page, select Web Content and click Next.
13. In the Create Subtab: Web Content page, enter the parameters, and then click
Save and Close.
14. Repeat steps 11 through 12 for each subtab.
Table 29. Opportunity Subtab JDE Quotes
Parameter
Value
Display Label
JDE Quotes
Source
URL
URL Definition
O_INT_JDE_OpptyQuoteURL()
Display Icon
Choose your preferred icon
Table 30. Opportunity Subtab JDE Orders
Parameter
Value
Display Label
JDE Orders
Source
URL
URL Definition
O_INT_JDE_OpptyOrderURL()
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
55
Oracle Sales Cloud Configuration
▪ Connecting Oracle Sales Cloud to JDE EnterpriseOne
Parameter
Value
Display Icon
Choose your preferred icon
Validating and Publishing the Sandbox
Validate and publish the sandbox for the Opportunity standard object, using the
procedures in Using Sandboxes.
Connecting Oracle Sales Cloud to JDE EnterpriseOne
You use the Integration Configuration page to allow Oracle Sales Cloud to exchange
data with JDE EnterpriseOne. This example uses JDE_9.1 as the name of the JDE
EnterpriseOne instance; yours might have a different name.
To connect Oracle Sales Cloud to JDE EnterpriseOne
1. Navigate to Navigator, Tools, and then Integration Configuration.
2. On the Integration Configuration page, click the Create icon.
3. On the Create Integration page, enter the information for the first key-value pair in
Table 31, and then click Save and Close.
4. Repeat steps 2 and 3 for the remaining key-value pairs in Table 31.
Table 31. Key-Value Pairs for the Integration
Remote
System
Key
Value
JDE_9.1
host
Host name of your JDE EnterpriseOne
instance, for example:
myJDE_server.example.com
port
HTTPS port of your JDE EnterpriseOne
instance, for example: 443
protocol
https
jdeQuoteVersion
Enter the version of the Sales Order
Entry application (P4210) that is used
to enter quotes. For example:
ZJDE0003
jdeOrderVersion
Enter the version of the Sales Order
Entry application (P4210) that is used
to enter sales orders. For example:
ZJDE0001
JDE_9.1
JDE_9.1
JDE_9.1
JDE_9.1
56
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
Remote
System
Key
Value
jdeCustomerVersion
Enter the version of Work with
Customer Master application (P03013)
that is used to enter customer
information. For example: ZJDE0001
enableAutoModeForSingleMatch
Enable this feature (Y/N)
oneViewReportIdOpenSales
To create this value, see Creating One
View Report IDs.
JDE_9.1
JDE_9.1
JDE_9.1
JDE_9.1
JDE_9.1
▪ Creating One View Report IDs
oneViewReportIdSalesByOpty
To create this value, see Creating One
View Report IDs.
enforceRevenueLineMapping
Enable this feature (Y/N)
Creating One View Report IDs
You must now retrieve One View Report (OVR) report IDs from the JDE EnterpriseOne
applications listed below. For additional information about the One View Reports used
to view sales opportunity information, see the One View Reporting for Sales Order
Management chapter in the JD Edwards EnterpriseOne Applications One View
Reporting User Guide. You can access this guide on the One View tab of the JD
Edwards EnterpriseOne Applications Documentation Library, located at:
http://docs.oracle.com/cd/E16582_01/index.htm.
For viewing the report IDs for OVR applications, perform the following:
To access the Open Sales by Opportunity OVR report ID
1. From the JDE EnterpriseOne application, in the Fast Path field, enter p42272.
2. Click in the Item Number field, then click the Search icon, and in the Item Search &
Select window, enter 210 in the Item Number field, and then click the Find icon.
3. Click OneView, then Manage Reports, and then select Sales By Opportunity from the
drop-down list.
4. In the Layout view, to the right of the screen, click the Information (i) button, shown
below:
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
57
Oracle Sales Cloud Configuration
▪ Creating One View Report IDs
5. The About window opens, as shown below:
Make a note of the ID value under One View Report Information.
To access the Open Sales OVR report ID
1. From the JDE EnterpriseOne application, in the Fast Path field, enter p42272.
2. Click in the Item Number field, then click the Search icon, and in the Item Search &
Select window, enter 210 in the Item Number field, and then click the Find icon.
3. Click OneView and select Sales By Opportunity in the drop-down list.
4. Click OneView, then Manage Reports, and then select Open Sales Analysis from the
drop-down list.
5. In the Layout view, to the right of the screen, click the Information (i) button, shown
below:
58
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating One View Report IDs
6. The About window opens, as shown below:
Make a note of the ID value under One View Report Information.
To create OVR report IDs
1. From the JDE EnterpriseOne application, click the One View menu.
2. From the drop-down menu, select Open sales analysis.
3. Click the Layout tab, then from the Layout Edit screen click the Information (i) button
shown below to open the About popup window.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
59
Oracle Sales Cloud Configuration
▪ Creating One View Report IDs
4. In the About popup window, under One View Report Information, make a note of
the ID number.
60
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Oracle Sales Cloud Configuration
▪ Creating One View Report IDs
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
61
4
Postconfiguration Tasks
This chapter details further tasks that you must perform, after configuring JDE
EnterpriseOne and Oracle Sales Cloud, for the integration to work correctly.
The Oracle Sales Cloud and JDE EnterpriseOne integration supports mapping items
from JDE EnterpriseOne to either product groups or product items in Oracle Sales
Cloud. Choose the mapping and steps below that best suit your implementation of
Oracle Sales Cloud.
Importing Products
For the Oracle Sales Cloud to JDE EnterpriseOne integration to be able to populate new
quotes with quote line items from come from the revenue lines on associated
opportunities, you must create mappings to associated products from the front office
Sales application to the back office ERP system. Use the following steps to create the
mappings.
Configuring Encoding in the JDE EnterpriseOne Application
Prior to creating a catalog, you must configure character encoding in the JD Edwards
Unicode Flat File Encoding Configuration program (P93801).
To configure character encoding
1. In the JD Edwards Unicode Flat File Encoding Configuration program, enter the
values listed in the following table:
Table 32. Opportunity Subtab JDE Quotes
Parameter
Value
User/Role
Public. For all users. This can be configured
for a specific user ID if necessary.
Environment
The name of your environment.
Program ID
UBE name: R4101ZO.
Version
Enter the version name. The default value is
ZJDE0001.
Encoding Name
UTF-8.
Status
Active.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
63
Postconfiguration Tasks
▪ Importing Products
Creating a JDE EnterpriseOne Catalog
Use this topic to create a JDE EnterpriseOne catalog to enable you to import products.
To create a JDE EnterpriseOne catalog
1. Navigate to Navigator, Tools, click Setup and Maintenance.
2. In the Search: Tasks area, search for Manage Product Groups.
3. In the Search Results pane, select the Manage Product Groups task, then click the
Go to Task icon.
4. In the Manage Product Groups view, search for JDE Catalog to ensure one is not
already created.
5. Click the Create icon, and in the Create Product Group dialog box, enter the
information from the following table:
Field
Value
Name
JDE Catalog
Display
JDE Catalog
Effective from Date
The current date
Active
Click the check box to
enable
Allow Duplicate Children
Uncheck the check box to
disable
Root Catalog
Check the check box to
enable
6. Click Save and Close to publish the new product group.
You will then add the JDE EnterpriseOne catalog as a child of the root catalog.
7. In the Manage Product Groups search box, search for Master Rollup.
8. In the Product Group view, click the Lock button.
9. Click the Subgroups tab, then click the Select and Add icon.
10. Search for JDE Catalog, then select it, and click OK.
11. In the Product Group view, click Publish.
12. In the Manage Product Groups view, click View, Columns, then make sure Reference
Number is checked.
13. Note the reference number for the JDE Catalog.
You will use the reference number value when preparing the JDE Item export file for
import into Oracle Sales Cloud.
64
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Postconfiguration Tasks
▪ Importing Products
Performing JDE EnterpriseOne Item Export
Use this topic to export JDE EnterpriseOne items to Oracle Sales Cloud.
For additional information about the Item Batch Outbound program (R4101ZO) used to
create the item XML file, see the Item Master chapter in the JD Edwards EnterpriseOne
Applications Business Interface Implementation Guide. You can access this guide on the
Cross-Product tab of the JD Edwards EnterpriseOne Applications Documentation Library,
located at: http://docs.oracle.com/cd/E16582_01/index.htm.
To import JDE EnterpriseOne items
1. Export JDE items using the batch process.
When you submit Item Batch Outbound program (R4101ZO) for exporting items into
XML, the printer selection window appears as shown below:
In the printer selection window, then click the Document Setup tab, and click the OSA
Interface Name checkbox, and enter XMLPOSA in the text box beneath the check box.
2. Submit the batch and review the submitted jobs. After the job is completed, a status
of “Done” is displayed.
3. Select the row, then from the Row menu, select View OSA, as shown below, to
download XML to your local directory.
4. Use the included processing script to prepare the XML file created in Step 1.
NOTE: Of the two included scripts, use the script appropriate to your operating system.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
65
Postconfiguration Tasks
•
•
▪ Importing Products
Linux: prepareImportItems.sh
Windows: prepareImportItems.ps1
5. Right-click Powershell and select Run as administrator.
6. Execute the command: Get-ExecutionPolicy.
If the returned value is Restricted, you will receive an error. In this case, note the
current value, and execute the command: Set-ExecutionPolicy RemoteSigned.
7. From the \OSC - JDE Integration R9v1.1\batch_scripts folder, run the following script
to retrieve the necessary XML file:
Windows: .\prepareImportItems.ps1 .\<jde items xml file> <OSC Jde
Catalog Reference Number>
Linux: sh prepareImportItems.sh <jde items xml file> <OSC Jde Catalog
Reference Number>
8. Re-institute the execution policy to the value from Step 6: Set-ExecutionPolicy
Restricted.
A new XML files is created: import_<XML_filename>.
Performing Initial Import of JDE EnterpriseOne Items from the XML Import File
You use the standard Oracle Sales Cloud File Import process to import JDE EnterpriseOne
items into Oracle Sales Cloud Product Groups.
NOTE: This import action will import all JDE EnterpriseOne items to the XML import file.
In certain circumstances however, it may only add only the first item as a subgroup to
the parent JDE Catalog Product Group. If this occurs after you have performed the
steps in this task, perform the tasks shown in Troubleshooting the Import of All Items into
the JDE Catalog Product Group.
To perform initial import of JDE EnterpriseOne items from an XML import file
1. Navigate to Navigator, Tools, click Setup and Maintenance.
2. In the Search: Tasks area, search for Manage File Import Activities.
3. In the Search Results pane, select the Manage File Import Activities task, then click
the Go to Task icon.
4. In the Manage Import Activities view, click the Create icon.
5. In the Create Import Activity: Enter Import Options view, enter the information from
the following table:
Field
Value
Name
JDE Import
Object
Product Group
File Type
XML
File Selection
Specific file
66
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Postconfiguration Tasks
▪ Importing Products
Field
Value
Upload From
Click the Desktop button
File Name
Select the XML file generated by the processing
script in Performing JDE EnterpriseOne Item
Export.
6. Click Next, then enter a new mapping using the following details:
Column Header
Target Object
Target Attribute
AllowDupContentFlag
ProductGroupBulkImport
AllowDupContentFlag
Catalog
ProductGroupBulkImport
ProdGroupDescText
Description1_ID10
ProductGroupBulkImport
ProdGroupName
ItemID_ID1
ProductGroupBulkImport
PgRefNumber
ItemProduct_ID4
ProductGroupBulkImport
PgInternalName
Language
ProductGroupBulkImport
Language
SourceLangFlag
ProductGroupBulkImport
SourceLangFlag
SourceObjectType
ProductGroupBulkImport
SourceObjectType
ItemRel.RelActiveFlag
ProductGroupRelationBulkImport
ActiveFlag
ItemRel.ItemID_ID1
ProductGroupRelationBulkImport
PgRelChildRefNumber
ItemRel.RelLanguage
ProductGroupRelationBulkImport
Language
ItemRel.RelSourceLangFlag
ProductGroupRelationBulkImport
SourceLangFlag
ItemRel.RelationTypeCode
ProductGroupRelationBulkImport
RelationTypeCode
7. Click Next, then click Next again, and then click Activate.
The process begins. To monitor progress, click Refresh.
8. Once the process shows a status of Completed, click Done to close File Import.
A. If there were errors, click the Completed with Errors link on the Status column
and review the errors.
B. Once you have reviewed and corrected the errors in the import file, return to
Step 7 and run the file import operation over again.
9. If necessary, perform the steps in Troubleshooting the Import of All Items into the JDE
Catalog Product Group.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
67
Postconfiguration Tasks
▪ Importing Products
Importing Updates of JDE EnterpriseOne Items from the XML Import File
Use this topic to import updates of your JDE EnterpriseOne items.
To perform import updates of JDE EnterpriseOne items from an XML import file
1. Navigate to Navigator, Tools, click Setup and Maintenance.
2. In the Search: Tasks area, search for Manage File Import Activities.
3. In the Search Results pane, select the Manage File Import Activities task, then click
the Go to Task icon.
4. In the Manage Import Activities view, locate the JDE Import file and click on it.
5. Make a note of the Import Mapping name and time stamp of the import file.
6. Click the Update button next to the file name, then browse for the new import file,
select it, and click OK.
7. Reselect the previously selected Import Mapping.
8. Click Next.
9. Review the mapping to ensure that it matches the table from Performing Initial
Import of JDE EnterpriseOne Items from the XML Import File.
10. Click Next, then click Next again, and then click Activate.
The process begins. To monitor progress, click Refresh.
11. Once the process shows a status of Completed, click Done to close File Import.
A. If there were errors, click the Completed with Errors link on the Status column
and review the errors.
B. Once you have reviewed and corrected the errors in the import file, return to
Step 9 and run the file import operation over again.
12. If necessary, perform the steps in Troubleshooting the Import of All Items into the JDE
Catalog Product Group.
Troubleshooting the Import of All Items into the JDE Catalog Product Group
In certain circumstances, following the import process, only the first item from the XML
item list will appear in the JDE Catalog Product Group subgroup rather than the
intended result of all items appearing. If you see only one item in the subgroup list, use
the following task to add all remaining items into the subgroup.
To import all items into the JDE Catalog Product Group subgroup
1. Navigate to Navigator, Tools, click Setup and Maintenance.
2. In the Search: Tasks area, search for Manage Product Groups.
3. In the Search Results pane, select the Manage Product Groups task, then click the
Go to Task icon.
4. In the Manage Product Groups view, search for JDE Catalog and click the Lock
button.
5. In the Product Group: JDE Catalog view, click the Subgroups tab, and then click the
Select and Add button.
68
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Postconfiguration Tasks
▪ Creating the Customer Matching Admin Role
You should see only one product group in the Subgroups list prior to clicking Select
and Add.
6. In the Select and Add: Product Groups pop up window, click the Advanced button.
7. Click the Add Fields button and select Description.
8. In the Description field, enter JDE_Catalog, and click Search.
The entire list of JDE EnterpriseOne items appears.
9. Select one item in the list, then select all the records (CTRL + A).
10. The status bar at the bottom of the screen will show Rows Selected equal to All.
11. Click OK.
There may be a slight delay to allow the import of all the items.
12. Once the pop up window closes, verify that all items appear in the Subgroups list.
13. Click the Publish button to publish the changes.
Creating the Customer Matching Admin Role
To perform manual matching of Oracle Sales Cloud customers to JDE EnterpriseOne
customers, we recommend the creation of a separate role. You perform the following
steps to create the Customer Matching Admin role:
1. Creating the New Role
2. Granting Privileges to the New Role
3. Associating Users with the New Role
Creating the New Role
You create the Customer Matching Admin role in Authorization Policy Manager (APM)
on the Oracle Entitlements Server.
NOTE: You must be logged in as a user with system administrator privileges.
To create the Customer Matching Admin role
1. Navigate to Navigator, Tools, and then Setup and Maintenance.
2. On the Overview page, click the All Tasks tab.
3. Select Task Lists and Tasks from the drop-down menu under Search, if it is not already
selected.
4. Enter Manage Role Templates in the Name field, and then click Search.
5. Under Search Results, click Go to Task in the Manage Role Templates row.
The Authorization Management screen appears.
6. Under Application Name on the Home tab, select crm.
7. Under Application Roles, click New.
8. Fill in the following fields, and then click Apply.
Parameter
Value
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
69
Postconfiguration Tasks
▪ Creating the Customer Matching Admin Role
Parameter
Value
Display Name
Customer Matching Admin
Role Name
INT_Customer_Matching_Admin
Description
Gates access to the customer matching screen
Role Category
CRM_ENTERPRISE_DUTY
9. Log out.
After you log back in, the Customer Matching Admin role will be available for granting
privileges and associating users.
Granting Privileges to the New Role
Grant the following privileges to the Customer Matching Admin role for the JDE Match
child object, using the procedure in Defining Security Policies for a Custom Object:
•
Create
•
View
•
Update
•
Delete
•
View All
•
Update All
Associating Users with the New Role
To associate users with the new Customer Matching Admin role, you have the following
options:
•
Assigning the Role to a Specific User. This allows individual users who have this role
assigned to perform customer matching.
•
Assigning the Role to an Existing Role Hierarchy. This allows a group of users who have
the role hierarchy to perform customer matching.
Assigning the Role to a Specific User
You associate a user with the Customer Matching Admin role in Authorization Policy
Manager (APM) on the Oracle Entitlements Server.
NOTE: You must have administrator privileges in APM to perform the following steps.
To associate a user with the Customer Matching Admin role
1. Navigate to Navigator, Tools, and then Setup and Maintenance.
2. On the Overview page, click the All Tasks tab.
3. Select Task Lists and Tasks from the drop-down menu under Search, if it is not already
selected.
70
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Postconfiguration Tasks
▪ Creating the Customer Matching Admin Role
4. Enter Manage Role Templates in the Name field, and then click Search.
5. Under Search Results, click Go to Task in the Manage Role Templates row.
The Authorization Management screen appears.
6. Under Application Name on the Home tab, select crm.
7. Under Search, select Users from the For drop-down menu.
8. Enter the user name in the search field, then click the Search icon (arrow).
9. Select the user name in the search results, then click the View icon (folder).
10. On the User Name tab, click the Application Role Assignments subtab.
11. Click Map.
12. In the Map Application Roles to User dialog:
A. Select crm from the Application Name drop-down menu.
B.
Select Contains from the drop-down menu next to Display Name, enter
Matching in the Display Name field, and then click Search.
C. Select Customer Matching Admin in the search results, then click Map Roles.
The role is mapped for the user under crm.
Assigning the Role to an Existing Role Hierarchy
Roles can be structured in a hierarchy using role inheritance. The parent role can do
anything that the child role can do (in addition to the parent role’s own privileges). This is
performed in APM.
To assign the Customer Matching Admin role to an existing role hierarchy
1. Navigate to Navigator, Tools, and then Setup and Maintenance.
2. On the Overview page, click the All Tasks tab.
3. Select Task Lists and Tasks from the drop-down menu under Search, if it is not already
selected.
4. Enter Manage Role Templates in the Name field, and then click Search.
5. Under Search Results, click Go to Task in the Manage Role Templates row.
The Authorization Management screen appears.
6. Under Application Name on the Home tab, select crm.
7. Under Search, select Applications Roles from the For drop-down menu.
8. Enter the Sales Representative Duty in the search field, then click the Search icon
(arrow).
9. Select Sales Representative Duty in the search results, then click the Open icon
(folder).
10. On the Sales Representative Duty tab, click the Application Role Hierarchy subtab.
11. Click Add.
12. In the Add a Role dialog:
A. Enter Customer Matching in the Role Display Name field, make sure that Starts
With is selected from the drop-down menu, and then click Search.
B. Select Customer Matching Admin in the search results, then click Add.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
71
Postconfiguration Tasks
▪ Creating the Customer Matching Admin Role
The role is added to the Application Role Hierarchy list.
72
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
5
Validating the Integration
To verify that the integration is functioning properly, perform the steps listed in this
chapter.
NOTE: It is the implementer’s responsibility to ensure that the domain values for
attributes in Oracle Sales Cloud match the domain values for corresponding attributes
in JD Edwards EnterpriseOne (or domain values are properly transformed from one
system to the other in the integration). For example, if Oracle Sales Cloud uses the
string “California” to represent the US state of California in an address and the JD
Edwards EnterpriseOne system uses the two letter code CA, then errors may result in
the integration. Please be sure that the values, transformations, and any
customizations you have previously applied to your Sales Cloud and JD Edwards
EnterpriseOne systems have been accounted for when implementing this Sales Cloud
and JD Edwards EnterpriseOne integration.
Integration Validation Checklist
To verify that your integration is functioning properly, see the following checklist.
To perform validation of the integration
1. Following successful import JDE EnterpriseOne items.
For more information, see Importing JDE EnterpriseOne Items to Oracle Sales Cloud
Catalog.
2. Choose one customer record and perform a synchronization operation.
For more information, see Customer Data Matching with JDE EnterpriseOne. Perform
all scenarios listed in the topic.
3. Using the same customer record from Step 2 create an Oracle Sales Cloud
opportunity using imported JDE EnterpriseOne items.
4. Using the opportunity you created in Step 3, create a new quote and a new order.
For more information, see Sales Order and Sales Quote Creation in JDE
EnterpriseOne.
5. Review the newly created quote and order records in the JDE EnterpriseOne UI
mashup.
6. Navigate to customer details and access the Quotes and Orders JDE UI mashup and
review the created quotes and orders from the previous steps also appear in this UI.
7. Using the quote and order records created in Step 4, review the OVR reports. For
more information, see Viewing Reports in JDE EnterpriseOne.
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
73
Validating the Integration
▪
74
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Validating the Integration
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
75
▪
6
Appendix. Required Files
The following files are required for the Oracle Sales Cloud to JDE EnterpriseOne
integration.
Groovy Files
The following Groovy script files are required for the integration.
Global Functions
O_INT_ApplyFilter.groovy
O_INT_AddMultiValueCriteriaItem.groovy
O_INT_Debug.groovy
O_INT_Error.groovy
O_INT_FindRowByKey.groovy
O_INT_GetLogMsg.groovy
O_INT_GetRecordCount.groovy
O_INT_GetRecords.groovy
O_INT_GetSysParam.groovy
O_INT_Info.groovy
O_INT_JDE_ConstructErrorPageURL
O_INT_JDE_GetLogMsg.groovy
O_INT_JDE_LogWithException
O_INT_JDE_GetSysParam.groovy
O_INT_Log.groovy
O_INT_LogMessage.groovy
O_INT_Warn.groovy
Batch Scripts
prepareImportItems.ps1
prepareImportItems.sh
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
77
Appendix. Required Files
▪ Groovy Files
Integration Configuration Custom Object
Validation Rule
UniqueKey.groovy
Global Functions
O_INT_GetIntegConfigParameter.groovy
O_INT_GetIntegConfigParameters.groovy
XREF Custom Object
Global Functions
O_INT_CreateXREF.groovy
O_INT_GetAllXREF.groovy
O_INT_GetXREF.groovy
O_INT_UpdateXREF.groovy
JDE Match Child Object
Object Function
O_INT_JDE_ForceCreateNewCustomer.groovy
Account Object
Global Function
O_INT_JDE_GetBaseURL.groovy
O_INT_JDE_GenerateSalesDocumentURL.groovy
Object Function
O_INT_JDE_GetSearchCriteria.groovy
O_INT_JDE_CheckMatch.groovy
O_INT_JDE_CleanupMatches.groovy
O_INT_JDE_CreateCustomer.groovy
O_INT_JDE_CustomerOrderURL.groovy
O_INT_JDE_CustomerQuoteURL.groovy
O_INT_JDE_CustomerReportURL.groovy
O_INT_JDE_CustomerSalesDocumentURL.groovy
O_INT_JDE_CustomerSync.groovy
O_INT_JDE_OpenSalesAnalysisURL.groovy
78
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne
release 9.1 Implementation Guide
Appendix. Required Files
▪ Groovy Files
O_INT_JDE_PopulateMatches.groovy
O_INT_JDE_SearchCustomer.groovy
O_INT_JDE_SalesByOpportunityURL.groovy
Triggers
O_INT_JDE_CleanupMatchesTrigger.groovy
Validations
O_INT_JDE_MatchSelectRule.groovy
Sales Account Standard Object
Object Functions
O_INT_JDE_AccountOpenSalesAnalysisURL.groovy
O_INT_JDE_AccountOrderURL.groovy
O_INT_JDE_AccountQuoteURL.groovy
O_INT_JDE_AccountSalesByOpportunityURL.groovy
Opportunity Standard Object
Object Functions
O_INT_JDE_CreateOrder
O_INT_JDE_CreateQuote
O_INT_JDE_CreateSalesDocument
O_INT_JDE_OpptyOrderURL.groovy
O_INT_JDE_OpptyQuoteURL.groovy
O_INT_JDE_OpptySalesDocumentURL.groovy
Integrating Oracle® Sales Cloud, Release 9 with JD Edwards EnterpriseOne release 9.1
Implementation Guide
79