Professional Documents
Culture Documents
Using Oracle Erp Cloud Adapter
Using Oracle Erp Cloud Adapter
Using Oracle Erp Cloud Adapter
Release 18.3
E66641-21
September 2019
Oracle Cloud Using the Oracle ERP Cloud Adapter, Release 18.3
E66641-21
Copyright © 2015, 2019, 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, then 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 about 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 unless otherwise
set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
Audience vi
Documentation Accessibility vi
Related Resources vi
Conventions vi
iii
Configuring Connection Security 2-14
Testing the Connection 2-14
Editing a Connection 2-15
Cloning a Connection 2-16
Deleting a Connection 2-16
Refreshing Integration Metadata 2-17
3 Creating an Integration
6 Administering Integrations
iv
Import Payables Invoice Report Job is Not Triggered from an Import Payables
Invoice 7-2
Data Uploaded in the Oracle ERP Cloud Interface Tables Is Not Uploaded in the
Base Tables 7-2
Oracle ERP Cloud Callback About the Bulk Import Issue 7-2
Jobs Not Appearing in the Import Jobs List on the Operations Page 7-3
Oracle ERP Cloud Callback Not Received in Oracle Integration Cloud Service 7-3
Business Events Being Sent to Deactivated Integrations 7-6
v
Preface
Preface
Using the Oracle ERP Cloud Adapter describes how to configure the Oracle ERP
Cloud Adapter as a connection in an integration in Oracle Integration Cloud Service.
Topics
• Audience
• Documentation Accessibility
• Related Resources
• Conventions
Audience
Using the Oracle ERP Cloud Adapter is intended for developers who want to use the
Oracle ERP Cloud Adapter in integrations in Oracle Integration Cloud Service.
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.
Related Resources
See these Oracle resources:
• Oracle Cloud
http://cloud.oracle.com
• Using Oracle Integration Cloud Service
• Using the Oracle Mapper
Conventions
The following text conventions are used in this document:
vi
Preface
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
vii
1
Getting Started with the Oracle ERP Cloud
Adapter
Review the following conceptual topics to learn about the Oracle ERP Cloud Adapter
and how to use it as a connection in integrations in Oracle Integration Cloud Service. A
typical workflow of adapter and integration tasks is also provided.
Topics
• Oracle ERP Cloud Adapter Capabilities
• What Application Version Is Supported?
• About Oracle Integration Cloud Service
• About Oracle Integration Cloud Service Connections
• About Oracle Integration Cloud Service Integrations
• About Oracle ERP Cloud Adapter Use Cases
• Typical Workflow for Creating and Including an Adapter Connection in an
Integration
Note:
Ensure that you have reviewed the Oracle HCM Cloud Adapter Capabilities
for supported SOAP services in Oracle HCM Cloud.
The Oracle ERP Cloud Adapter enables you to easily integrate on-premises or SaaS
applications with Oracle ERP Cloud without having to know about the specific details
involved in the integration. The Oracle ERP Cloud Adapter provides the following
benefits:
• Integrates easily with the Oracle ERP Cloud application’s WSDL file to produce a
simplified, integration-centric WSDL.
• Generates automatic mapping to the exposed business object or event
subscription that you select during adapter configuration:
– Business object: Represents a self-contained business document that can be
acted upon by the integration. An integration can send requests to create a
new record for that business object. They can send a request either to update
or delete an existing record for a business object. Integrations can also send
requests to retrieve information about one or more records representing that
business object.
1-1
Chapter 1
Oracle ERP Cloud Adapter Capabilities
Note:
Create the UCM URL by appending the host and port of the service
catalog with the following URI: /idcws/GenericSoapPort.
1-2
Chapter 1
Oracle ERP Cloud Adapter Capabilities
Note:
Video
1-3
Chapter 1
Oracle ERP Cloud Adapter Capabilities
1-4
Chapter 1
Oracle ERP Cloud Adapter Capabilities
1-5
Chapter 1
Oracle ERP Cloud Adapter Capabilities
1-6
Chapter 1
Oracle ERP Cloud Adapter Capabilities
1-7
Chapter 1
What Application Version Is Supported?
1-8
Chapter 1
About Oracle Integration Cloud Service
Video
1-9
Chapter 1
About Oracle ERP Cloud Adapter Use Cases
connections. This can include defining the type of operations to perform on the data,
the business objects and fields against which to perform those operations, required
schemas, and so on. To make this easier, the most complex configuration tasks are
handled by Oracle Integration Cloud Service. Once your trigger (source) and invoke
(target) connections are configured, the mappers between the two are enabled so you
can define how the information is transferred between the trigger (source) and invoke
(target) data structures for both the request and response messages.
Video
Video
1-10
Chapter 1
About Oracle ERP Cloud Adapter Use Cases
1-11
Chapter 1
Typical Workflow for Creating and Including an Adapter Connection in an Integration
1-12
2
Creating an Oracle ERP Cloud Adapter
Connection
A connection is based on an adapter. You define connections to the specific cloud
applications that you want to integrate. The following topics describe how to define
connections.
Topics
• Prerequisites for Creating a Connection
• Uploading an SSL Certificate
• Creating a Connection
• Editing a Connection
• Cloning a Connection
• Deleting a Connection
• Refreshing Integration Metadata
2-1
Chapter 2
Prerequisites for Creating a Connection
The following sections describe how to obtain the service catalog service WSDL and
event catalog URL:
• For Fusion Applications Releases 10 Through 12
• For Fusion Applications Releases 13 and Later
2-2
Chapter 2
Prerequisites for Creating a Connection
This section describes how to derive the external virtual host and port for a tokenized
service catalog service WSDL. The topology information in the Topology Registration
setup task contains the external virtual host and port for the domains and applications.
The following instructions describe the steps for deriving the values using the service
catalog service WSDL URL as an example: https://atf_server:port/
fndAppCoreServices/ServiceCatalogService.
2-3
Chapter 2
Prerequisites for Creating a Connection
5. Map the token name for the service path value to the domain name in the
Topology Manager:
6. Expand the domain name and select any external virtual host and port for the
J2EE applications that are deployed on the domain. In the sample window, the
values for this particular instance are fs-your-cloud-hostname and 443,
respectively.
2-4
Chapter 2
Prerequisites for Creating a Connection
https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome
https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/
ServiceCatalogService?WSDL
https://acme.fs.us2.oraclecloud.com/
2-5
Chapter 2
Prerequisites for Creating a Connection
https://acme.fin.us2.oraclecloud.com/soa-infra
The event catalog URL https://host/soa-infra is a partial URL and must only be
provided on the Connections page. Do not open this URL with a browser. If you do,
you receive a Page not found error. The adapter does not access this URL directly.
Instead, it automatically appends the required resource path to make the URL fully
valid (when it needs to access the event catalog).
To check the public events defined in the catalog, enter the following complete URL in
a browser:
https://host:port/soa-infra/PublicEvent/catalog
https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome
Where acme is the system name and us6 is the data center.
2. Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/
ServiceCatalogService?WSDL. For example:
https://acme.fs.us2.oraclecloud.com/fscmService/ServiceCatalogService?
WSDL
https://systemName.fa.dcsn.oraclecloud.com/...
You must switch to the consolidated endpoint immediately after upgrading to Release
13. Newly provisioned instances using Release 13 only have the consolidated
endpoint available. In Release 13, multiple domains are consolidated. You must
specify the domain in the URL. For example, if specifying the fa domain, the URL
looks as follows:
2-6
Chapter 2
Prerequisites for Creating a Connection
https://acme.fa.us6.oraclecloud.com/
https://acme.fa.us6.oraclecloud.com/soa-infra
Associating the Integration User with the Following Roles and Privileges
You associate the user with the following roles and privileges.
Role Description
ALL_INTEGRATION_POINTS_ALL_DATA Starting with release 12, this role is no longer
supported. When existing customers upgrade
to release 12, users with this role continue
using it, although it is hidden from the Security
Console. If you create a new integration user
in release 12 or later, you cannot assign this
role.
Integration Specialist This is a job role and does not include data
roles. Assign the Integration Specialist role
that inherits Oracle ERP Cloud roles. This role
applies to Releases 12 and 13.
Oracle ERP Cloud-specific data access to You must specify the specific data access
the integration user roles based on the objects you want to
integrate. This role applies to Releases 12 and
13. See Managing Data Access for Users:
Explained of Cloud Securing Oracle ERP
Cloud.
AttachmentsUser Provides access to the Attachments security
group to download the log file or the output file
with the ERP Integration Service. Starting with
Release 12, this role is automatically shipped.
You must verify that this role is automatically
assigned to the user.
SOAOperator The SOA operator role.
FND_MANAGE_CATALOG_SERVICE_PRIV The role to manage the web services catalog.
Customer Relationship Management See Job Role: Customer Relationship
Application Administrator (for Oracle CRM Management Application Administrator of
Cloud implementations) Cloud Security Reference for Oracle Sales
Cloud.
2-7
Chapter 2
Prerequisites for Creating a Connection
See Using the Security Console of Cloud Securing Oracle ERP Cloud.
Note:
Ensure that you specify the following information correctly when creating the CSF key:
• Create the CSF key with a key name that matches the identity domain of the
Oracle Integration Cloud Service instance.
• Create the CSF key with the Oracle Integration Cloud Service user account with
which you log in to Oracle Integration Cloud Service and not the user name
created when you subscribed to Oracle ERP Cloud.
• Ensure that the CSF key password has not expired.
2-8
Chapter 2
Prerequisites for Creating a Connection
1. Log in to Oracle SOA Composer with a user that has the SOA administrator role.
Obtain the hostname and port from your administrator.
For example, in Release 12:
http://ERP_domain_URL:port/soa/composer
https://acme.fa.us6.oraclecloud.com/soa/composer
5. Click Register.
2-9
Chapter 2
Prerequisites for Creating a Connection
Uploading Files in Bulk and Inserting Data into Oracle ERP Cloud
Application Tables
You must satisfy the following prerequisites for the upload of files in bulk and the
insertion of data into Oracle ERP Cloud application tables.
Note:
Only file-based data import (FBDI)-compliant jobs are supported for
callbacks.
• Satisfy the following prerequisites for the bulk upload of files and the insertion of
data into Oracle ERP Cloud application tables. This is only required for an ERP
Cloud callback upon job completion.
1. Create a user similar to the ERP Cloud Adapter connection user in the My
Service Page. This user is linked to the Oracle Integration Cloud Service
WebLogic security realm. The user name must exactly match the Oracle ERP
Cloud user name. The password and email address can be anything. Ensure
that you select the correct roles for the Oracle ERP Cloud user in the Oracle
ERP Cloud application. The user must have the SOAOperator and Integration
roles.
2. Import the following certificates:
– In your browser, enter Service Catalog URL:
For Release 12:
https://hostname:port/fndAppCoreServices/ServiceCatalogService?
WSDL
https://hostname:port/fscmService/ServiceCatalogService?WSDL
2-10
Chapter 2
Uploading an SSL Certificate
– Copy the second certificate to a file. You have two certificate files (for
example, erp_cert1.cer and erp_cert2.cer).
– In the Upload Certificate dialog in Oracle Integration Cloud Service, import
both certificates as Message Protection Certificate types and enter
unique alias names. See Uploading an SSL Certificate.
– Satisfy the following manifest file recommendations (that is, the properties
file in the zip file that must be uploaded to Universal Content Management
(UCM)).
* The manifest file expects import process details in the following
format:
For example:
oracle/apps/ess/financials/payables/invoices/
transactions,APXIIMPT,AP,#NULL,#NULL,#NULL,#NULL,#NULL,#NULL,
#NULL,INVOICE
* The manifest file name can be any file name. However, the third value
in the manifest must be the manifest file name.
* Only one job is supported per invoke. You can have multiple entries in
the manifest property file to import data from the interface table to the
applications tables in batches of up to 10 for sequential or up to 5 for
parallel processing. For example, the journal import data file has
records of 10 ledgers. The property file has 10 entries with the unique
ledger name as a parameter. After the data file is loaded in the
interface table, the import process has 10 subprocesses for each
ledger.
• Satisfy the following prerequisites to configure the integration that uses the bulk
import feature:
1. Map the following parameters to the Oracle ERP Cloud Adapter.
– Map parameter ICSFileReference to the File Reference parameter from
the other adapter (for example, the FTP Adapter, the REST Adapter, or
whichever adapter you used that has the ICSFileReference parameter).
– Map the FileName parameter from the source schema to the target
schema (the target schema is the Oracle ERP Cloud bulk import schema).
The FileName must be unique for every request.
2-11
Chapter 2
Uploading an SSL Certificate
1. From the Oracle Integration Cloud Service home page, click the
2-12
Chapter 2
Creating a Connection
Creating a Connection
The first step in creating an integration is to create the connections to the applications
with which you want to share data.
1. In the Oracle Integration Cloud Service home page, click Connections.
2. Click Create.
The Create Connection — Select Adapter dialog is displayed.
3. Select an adapter from the dialog. You can also search for the type of adapter to
use by entering a partial or full name in the Search field, and clicking Search.
The Create New Connection dialog is displayed.
4. Enter the information to describe the connection.
• Enter a meaningful name to help others find your connection when they begin
to create their own integrations. The name you enter is automatically added in
capital letters to the Identifier field. If you modify the identifier name, do not
include a blank space (for example, Sales Opportunity).
• Select the role (direction) in which to use this connection (trigger, invoke, or
both). Only the roles supported by this adapter are displayed for selection.
When you select a role, only the connection properties and security policies
appropriate to that role are displayed on the Connections page. If you select
an adapter that supports both invoke and trigger, but select only one of those
roles, then try to drag the adapter into the section you did not select, you
receive an error (for example, configure an Oracle RightNow Cloud Adapter as
only an invoke, but drag the adapter to the trigger section).
• Enter an optional description of the connection.
2-13
Chapter 2
Creating a Connection
5. Click Create.
Your connection is created and you are now ready to configure connection details,
such as email contact, connection properties, security policies, connection login
credentials, and (for certain connections) agent group.
2-14
Chapter 2
Editing a Connection
Editing a Connection
You can edit connection settings after creating a new connection.
2-15
Chapter 2
Cloning a Connection
Cloning a Connection
You can clone a copy of an existing connection, even if the connection is locked. This
provides a quick way to create a new connection.
1. On the Oracle Integration Cloud Service home page, click Connections.
2. On the Connections page, search for the connection name.
3. Select Clone from the connection Actions menu.
Deleting a Connection
You can delete a connection from the connection menu.
1. On the Oracle Integration Cloud Service home page, click Connections.
2. On the Connections page, search for the connection name.
3. Click Delete from the connection Actions menu.
2-16
Chapter 2
Refreshing Integration Metadata
Note:
The Refresh Metadata menu option is only available with adapters that have
implemented metadata caching.
2-17
3
Creating an Integration
Integrations use the adapter connections you created to your applications, and define
how information is shared between those applications. You can create, import, modify,
or delete integrations; create integrations to publish or subscribe to messages; add
and remove request and response enrichment triggers; and create routing paths for
different invoke endpoints in integrations. Click the following topic for more information:
Topic
• Creating Integrations (in Using Oracle Integration Cloud Service)
3-1
4
Adding the Oracle ERP Cloud Adapter
Connection to an Integration
When you drag the Oracle ERP Cloud Adapter into the trigger and invoke areas of an
integration, the Cloud Endpoint Configuration Wizard is invoked. This wizard guides
you through configuration of the Oracle ERP Cloud Adapter endpoint properties.
The following sections describe the wizard pages that guide you through configuration
of the Oracle ERP Cloud Adapter as a trigger or invoke in an integration.
Topics
• Configuring Basic Information Properties
• Configuring Oracle ERP Cloud Trigger Request Properties
• Configuring Oracle ERP Cloud Trigger Response Properties
• Configuring Oracle ERP Cloud Invoke Operation Properties
• Configuring Oracle ERP Cloud Invoke Response Properties
• Reviewing Configuration Values on the Summary Page
Topics
• What You Can Do from the Basic Info Page
• What You See on the Basic Info Page
4-1
Chapter 4
Configuring Basic Information Properties
Element Description
What do you want to call your endpoint? Provide a meaningful name so that others can
understand the responsibilities of this
connection. You can include English
alphabetic characters, numbers, underscores,
and dashes in the name. You cannot include
the following:
• Blank spaces (for example, My Inbound
Connection)
• Special characters (for example, #;83&
or righ(t)now4)
• Multibyte characters
What does this endpoint do? Enter an optional description of the
connection’s responsibilities. For example:
This connection receives an inbound
request to synchronize account
information with the cloud
application.
4-2
Chapter 4
Configuring Oracle ERP Cloud Trigger Request Properties
Element Description
What actions would you want to perform on Select the action to perform. These options
this endpoint? are only displayed when you are configuring
the Oracle ERP Cloud Adapter as an invoke
connection in an integration.
• Create, Update, Delete, Read Business
Object: Provides the standard
configuration path for selecting a business
object or service. This option displays the
standard Operations and Response
pages. This is the default selection.
• Import Data into Financials Cloud
Application: Provides a scenario for
loading and orchestrating data from a
secure FTP location to Oracle ERP Cloud.
Data is loaded into a selected product
interface table and then imported into the
related main product application tables. A
callback notification may also be
configured to send when the data import
completes. This option also shows a
modified Operations page and a unique
Response page in the Adapter Endpoint
Configuration Wizard for importing data.
Topics
• What You Can Do from the Oracle ERP Cloud Trigger Request Page
• What You See on the Oracle ERP Cloud Trigger Request Page
What You Can Do from the Oracle ERP Cloud Trigger Request Page
You can select the following trigger request values for the Oracle ERP Cloud
application.
Select the specific type to receive as a request from Oracle ERP Cloud. Your ability to
select either a business object or event subscription is based on the content of the
WSDL file (for business objects) or event catalog URL (for event subscriptions) you
specified during Oracle ERP Cloud Adapter configuration.
• Select to receive a business object as a request from the Oracle ERP Cloud
application. This selection invokes the integration.
• Select to receive an event subscription raised by the Oracle ERP Cloud
application as a request from Oracle ERP Cloud. This selection invokes the
integration.
• Select to configure a callback notification response.
4-3
Chapter 4
Configuring Oracle ERP Cloud Trigger Request Properties
Note:
If the options for selecting business objects and events are missing, that
indicates that the event catalog URL was not supplied on the Connection
page.
What You See on the Oracle ERP Cloud Trigger Request Page
The following table describes the key information on the Oracle ERP Cloud trigger
Request page.
Element Description
Configure a Request Select the request type appropriate to your
integration. The fields that are displayed below
are based on the request type that you select.
• With Business Objects: Select to display
a list of business objects.
• With Business Events: Select to display
a list of business events.
• As a Callback: Select to configure a
callback notification response to send
upon completion of the data import into
the Oracle ERP Cloud application.
Select a Business Object Select the business object from the Oracle
(is displayed if With Business Objects is ERP Cloud application to receive as a request
selected) that starts the integration.
Business Event For Subscription Select the event subscription from the Oracle
(is displayed if With Business Events is ERP Cloud application. This event is received
selected) as a request that starts the integration. Only
events that can be subscribed to are
displayed.
4-4
Chapter 4
Configuring Oracle ERP Cloud Trigger Response Properties
Element Description
Filter Expr for Business_Event_Name Enter an event condition filter expression. A
(is displayed if With Business Events is filter expression specifies that the contents
selected) (payload or headers) of a message be
analyzed before any event is sent. For
example, you can apply a filter expression that
specifies that an event be sent only if the
message includes a customer ID. When the
expression logic is satisfied, the event is
accepted for delivery to the integration.
Filter by object name or Filter By Event Type the initial letters of the name to filter the
Name display of business objects or event
subscriptions.
Download Options (is displayed if As a Specify when to download the log files that
Callback is selected) describe the overall status of the Oracle ERP
Cloud import job.
• Always: Always download the logs,
regardless of import job failure or
success.
• On Failure: Only download the logs if the
import job is a failure.
• On Success: Only download the logs if
the import job is successful.
• Never: Never download the logs.
Topics
• What You Can Do from the Oracle ERP Cloud Trigger Response Page
• What You See on the Oracle ERP Cloud Trigger Response Page
What You Can Do from the Oracle ERP Cloud Trigger Response Page
You can configure the operation and business object that comprise the response type
for the Oracle ERP Cloud application.
• Immediate (synchronous) response: A response business object is immediately
returned as output. You select Immediate as the response type on the Response
page and select the business object as part of the response to the client.
• Delayed (asynchronous) response: A callback service to which to route the
callback is exposed. You select Delayed as the response type on the Response
page and select the operation and business object that comprise a successful
callback response, a failed callback response, or both.
• No response is required: You select None on the Response page because a
response is not required.
The Response page looks as follows:
4-5
Chapter 4
Configuring Oracle ERP Cloud Trigger Response Properties
What You See on the Oracle ERP Cloud Trigger Response Page
Select the business object for the integration to send as a response document to the
Oracle ERP Cloud application. The following types of responses are available.
Select the type of response appropriate to your business requirements:
• Immediate: A synchronous response is required (See Table 4-1 for instructions)
• Delayed: An asynchronous response is required (See Table 4-2 for instructions)
• None: No response is required (See Table 4-3 for instructions)
The following table describes the fields available if an immediate (synchronous)
response is required.
Element Description
Response Type Select Immediate for the Oracle ERP Cloud
application to wait until a response is received
from the integration. This is also known as the
request and response message exchange
pattern. This is the default selection.
Filter by object name Enter the initial letters to filter the display of
business objects.
Select a Business Object Select the business object to receive from the
Oracle ERP Cloud application as a response.
A description of the selected business object is
displayed below this list.
Name Displays the name of the selected business
object.
Description Displays the description of the selected
business object.
4-6
Chapter 4
Configuring Oracle ERP Cloud Trigger Response Properties
The following table describes the fields available if a delayed (asynchronous) callback
response is required. You can configure a successful callback response, a failed
callback response, or both.
Element Description
Response Type Select Delayed to configure a successful
callback response, a failed callback response,
or both.
This enables you to configure the operation
and business objects that you want the Oracle
ERP Cloud application to process as part of a
successful callback response, failed callback
response, or both.
Successful Response/Failed Response Select the type of callback to configure. After
configuring one type of callback (for example,
successful), you can configure the other type
(for example, failed).
• Successful Response: Select to
configure the operation and business
objects that you want the Oracle ERP
Cloud application to process as part of a
successful callback response sent by the
integration.
• Failed Response: Select to configure the
operation and business objects that you
want the Oracle ERP Cloud application to
process as part of a failed callback
response sent by the integration.
Select the operation to perform on the Select the operation to perform on the
business object business object.
Life Cycle Displays the current state of the selected
business document. Active indicates the
business document is available for use.
Deprecated indicates the business document
is nearing the end of use and must be used
with caution.
Name Displays the name of the selected business
object.
Description Displays the description of the selected
business object.
Element Description
Response Type Select None.
Select a Business Object If you select None, this section is hidden.
4-7
Chapter 4
Configuring Oracle ERP Cloud Invoke Operation Properties
Topics
• What You Can Do from the Oracle ERP Cloud Invoke Operations Page
• What You See on the Oracle ERP Cloud Invoke Operations Page
What You Can Do from the Oracle ERP Cloud Invoke Operations
Page
You can configure one of the following invoke operation options for the Oracle ERP
Cloud.
• Select the business object or service and the operation to perform on the selected
business object or service.
• Select the job name to import, the job property name, and the type of log data for
Oracle ERP Cloud to extract.
4-8
Chapter 4
Configuring Oracle ERP Cloud Invoke Operation Properties
What You See on the Oracle ERP Cloud Invoke Operations Page
The following table describes the key information on the Oracle ERP Cloud invoke
Operations page.
If you selected Create, Update, Delete, Read Business Object on the Basic Info
page, then provide the following information:
Element Description
Browse by Select to browse by business object or
service. There is a one-to-one correspondence
between the business object and service. The
service acts on the business document.
• Business Objects: Select to browse a list
of available business objects.
• Services: Select to browse a list of
available services.
Filter by object name Type the initial letters to filter the display of
(displayed if Business Objects is selected) business objects or select a specific category:
• All
• Active
• Custom
• Deprecated
• Standard
Select a Business Object Select the business object to use.
(displayed if Business Objects is selected)
Filter by service Type the initial letters to filter the display of
(displayed if Services is selected) services.
If you selected Import Data into Financials Cloud Application on the Basic Info
page, then provide the following information:
4-9
Chapter 4
Configuring Oracle ERP Cloud Invoke Response Properties
Element Description
Import Job Name Select the job name to import. Import jobs are
the background jobs that run on Oracle ERP
Cloud to perform data upload operations. The
job name you select is used to import data.
The list of import jobs is obtained by invoking
ErpIcsIntegrationService in the service
catalog service WSDL. The following
information is obtained with each job:
• Job display name: To be displayed in the
user interface.
• Interface ID: The import job key.
• UCM account: The account with which to
upload the file.
Reuse job property file uploaded Select this check box, then enter the job
separately in respective UCM account property file name (without an extension) that
Oracle ERP Cloud can obtain from the
respective UCM account.
Extract File Select the type of log data for Oracle ERP
Cloud to extract while processing the data file:
• All: All failed records with supporting load
and import process files.
• Error: Records that failed to load and
import.
• Log: Log files for load and import
processes.
• Out: Output files for load and import
processes.
• None: None.
Additional Import Options This field is not currently supported.
Topics
• What You Can Do from the Oracle ERP Cloud Invoke Response Page
• What You See on the Oracle ERP Cloud Invoke Response Page
What You Can Do from the Oracle ERP Cloud Invoke Response Page
You can configure the following invoke operation values for the Oracle ERP Cloud.
• Select an option for being notified of data import completion status.
• Select when to receive a notification about data import status.
• Specify a callback integration in which to receive details about the status of the
outbound Oracle ERP Cloud request flow.
4-10
Chapter 4
Configuring Oracle ERP Cloud Invoke Response Properties
What You See on the Oracle ERP Cloud Invoke Response Page
The following table describes the key information on the Oracle ERP Cloud invoke
Response page.
Element Description
Notification Mode Select an option for being notified of data
import completion status:
• Email & Bell Notification: Select to
receive both email and bell notifications.
• Email notification: Select to receive only
an email notification.
• Bell Notification: Select to receive only a
bell notification.
Occurrence Select when to receive a notification about
data import status:
• Send in any case
• Send on import success
• Send on import failure
Integration Flow Identifier Optionally specify a callback integration in
which to receive details about the status of the
outbound Oracle ERP Cloud request flow
(failed records) (for example, enter
01.00.0000). This is a completely separate
integration that handles callbacks. The name
of the integration is not required. The inbound
integration is expected to handle callbacks
from Oracle ERP Cloud. The integration must
have an Oracle ERP Cloud Adapter configured
in the trigger (inbound) direction. You select
As a Callback on the Request page in the
trigger direction.
Version Enter the integration version in two digits. For
example, enter 01 if the identifier version is
01.00.0000.
4-11
Chapter 4
Reviewing Configuration Values on the Summary Page
Topics
• What You Can Do from the Summary Page
• What You See on the Summary Page
Element Description
Summary Displays a summary of the configuration
values you defined on previous pages of the
wizard.
The information that is displayed can vary by
adapter. For some adapters, the selected
business objects and operation name are
displayed. For adapters for which a generated
XSD file is provided, click the XSD link to view
a read-only version of the file.
To return to a previous page to update any
values, click the appropriate tab in the left
panel or click Back.
4-12
5
Creating Mappings and Lookups in
Integrations
You must map data between trigger (source) connections and invoke (target)
connections in integrations. You can also optionally create lookups in integrations.
Topics
• Mapping Data (in Using Oracle Integration Cloud Service)
• Creating Lookups (in Using Oracle Integration Cloud Service)
5-1
6
Administering Integrations
Oracle Integration Cloud Service provides you with the information and tools required
to activate, monitor, and manage your integrations in the runtime environment.
Topic
• Administering Oracle Integration Cloud Service (in Using Oracle Integration Cloud
Service)
6-1
7
Troubleshooting Oracle ERP Cloud
Adapter
Review the following topics to learn about troubleshooting issues with the Oracle ERP
Cloud Adapter.
Topics
• Reactivate Integrations when the Connection URL is Modified
• Troubleshooting Event Subscription Errors
• Import Payables Invoice Report Job is Not Triggered from an Import Payables
Invoice
• Data Uploaded in the Oracle ERP Cloud Interface Tables Is Not Uploaded in the
Base Tables
• Oracle ERP Cloud Callback About the Bulk Import Issue
• Jobs Not Appearing in the Import Jobs List on the Operations Page
• Oracle ERP Cloud Callback Not Received in Oracle Integration Cloud Service
• Business Events Being Sent to Deactivated Integrations
7-1
Chapter 7
Import Payables Invoice Report Job is Not Triggered from an Import Payables Invoice
Ensure that you carefully following the instructions in Configuring Oracle ERP Cloud
for Event Subscriptions to correctly create the CSF key.
For example:
oracle/apps/ess/financials/payables/invoices/
transactions,APXIIMPT,AP,#NULL,#NULL,#NULL,#NULL,#NULL,#NULL,#NULL,INVOICE
The manifest file name should be a prefix of the actual zip file name if it contains _.
Otherwise, it should just be the name. For example:
• If the zip file name is AP_301.zip, the manifest file name should be AP.properties
and the third value in the manifest should be the manifest file name.
• If the zip file name is AP.zip, the manifest file name should be AP.properties and
the third value in the manifest should be the manifest file name.
See Creating a Job Property File for the ImportBulkData Operation of Using External
Data Integration Services for Oracle ERP Cloud, Release 11 for additional details.
7-2
Chapter 7
Jobs Not Appearing in the Import Jobs List on the Operations Page
• Review the Oracle Integration Cloud Service server diagnostic logs exceptions.
– Security exception related to certificates
7-3
Chapter 7
Oracle ERP Cloud Callback Not Received in Oracle Integration Cloud Service
Solution: The user has not been created in Oracle Integration Cloud Service.
See Uploading Files in Bulk and Inserting Data into Oracle ERP Cloud
Application Tables.
– Exception-related to non-FBDI jobs.
7-4
Chapter 7
Oracle ERP Cloud Callback Not Received in Oracle Integration Cloud Service
Solution: Only FBDI-compliant jobs are supported for bulk import. The FBDI-
complaint jobs are described in File-Based Data Import for Oracle Financials
Cloud.
– No exception in the server diagnostic logs
If there is no exception in the Oracle Integration Cloud Service server
diagnostic logs, verify the following:
1. If the environment is for development, then the certificate must be
imported in the Oracle ERP Cloud application.
2. Verify the certificate. It should be CA authorized as VeriSign Class 3
Public Primary Certification Authority - G5.
3. Check for a connectivity issue between the Oracle ERP Cloud application
and Oracle Integration Cloud Service.
7-5
Chapter 7
Business Events Being Sent to Deactivated Integrations
Download the Oracle ERP Cloud logs or raise a service request to obtain
the logs and look for exceptions such as the following.
[2017-11-17T17:17:38.813+00:00] [FinancialCommonServer_1]
[ERROR] []
[oracle.webservices.jaxws] [tid: pool-34-thread-1] [userId:
HGV_FIN]
[ecid: 005NZ3JJuRhA9T3_RlP5id0002yy000005,1:56507] [APP:
FinancialCommonApp#V2.0]
Raise a service request. Some pointers where the issue may be are as
follows.
* Execute wget endpoint URL from the primary and secondary FIN
common servers and open a CX ticket if needed to troubleshoot.
Check the proxy settings.
$ wget https://icsprod-
a111111.integration.us2.oraclecloud.com/ics/faces/global
• To get subscriptions, use the REST URL and the GET HTTP method:
http://server:port/soa-infra/PublicEvent/subscriptions/
7-6
Chapter 7
Business Events Being Sent to Deactivated Integrations
Sample response:
{
"subscriptions": [
{
"id": 101,
"name":
"{http://xmlns.oracle.com/apps/scm/doo/decomposition/
DooDecompositionOrderStatusUpdateComposite/
AggregatedBusinessEvent}AggregatedBusinessEvent",
"filter": "<xpathExpr
xmlns:ns_2='http://xmlns.oracle.com/apps/scm/doo/common/events/
service/'>$eventPayload/ns_2:SourceOrderSystem = 'LEG'</
xpathExpr>",
"endpointURL":
"http://slc01fqy.us.oracle.com:7001/soa-infra/services/default/
PublicEventSubscriber/subscriberprocess_client_ep"
},
{
"id": 102,
"name":
"{http://schemas.oracle.com/events/edl/
Bpel20EssJobEvents}EssJobRequest",
"filter": "<xpathExpr
xmlns:ns2='http://schemas.oracle.com/events/edl/Bpel20EssJobEvents'>/
ns2:a/ns2:b < 200</xpathExpr>",
"endpointURL": "http://my.service.com:9000/EssJob"
}
]
}
• To get a specific subscription, use the REST URL and the GET HTTP method:
http://server:port/soa-infra/PublicEvent/subscriptions/{id}
For example:
http://server:port/soa-infra/PublicEvent/subscriptions/102
Sample output:
{
"id": 102,
"name":
"{http://schemas.oracle.com/events/edl/
Bpel20EssJobEvents}EssJobRequest",
"filter": "/ns2:a/ns2:b < 200",
"endpointURL": "http://my.service.com:9000/EssJob"
}
7-7
Chapter 7
Business Events Being Sent to Deactivated Integrations
• To manually delete subscriptions, use the REST URL and the DELETE HTTP
method:
http://server:port/soa-infra/PublicEvent/subscriptions/{id}
Sample input:
• To update and activate/deactivate the subscriptions, use the REST URL and the
PUT HTTP method:
http://server:port/soa-infra/PublicEvent/subscriptions/{id}
Sample input:
{
"id": 102,
"name":
"{http://schemas.oracle.com/events/edl/
Bpel20EssJobEvents}EssJobRequest",
"filter": "/ns2:a/ns2:b < 200",
"endpointURL": "http://my.service.com:9000/EssJob",
"state" : true
7-8