text
stringlengths 65
20k
|
|---|
3.Configure the adapter in the Adapter Endpoint Configuration Wizard.4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints. |
4.Drag an initial Oracle ERP Cloud Adapter into the integration canvas as an invoke connection.Chapter 4 Invoke an Endpoint Dynamically 4-55.Configure it to use the crmRestApp service application, the Account object (business resource), and the get operation.The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link. |
The response of the first invoke connection contains a collection of HATEOS links, each pointing to a child object such as Primary Address .6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter. |
6.In the mapper between the trigger adapter connection and the Oracle ERP Cloud Adapter invoke connection, map source elements to target elements.For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties . |
For this example, a PartyNumber source element is passed to an id target element.7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request. |
7.Add a for-each action to iterate between the HATEOS links.The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions. |
The value in the Repeating Element field is from the response object.8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes. |
8.Add a switch action to get the HATEOS link corresponding to the Primary Address object.9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored. |
9.Drag the Oracle ERP Cloud Adapter into the switch action as the second invoke connection.10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element. |
10.Configure it to use the crmRestApp service application, the Primary Address object (business resource), and the getAll operation.This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties . |
This object uses dynamic REST endpoint support.The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration. |
The Primary Address is a collection of links.The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element. |
The getAll operation is selected for getting all the HATEOS links.Chapter 4 Invoke an Endpoint Dynamically 4-611.In the mapper immediately before the second Oracle ERP Cloud Adapter invoke connection, expand RestApi under ConnectivityProperties in the target section.12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value. |
12.From the source section, map href to AbsoluteEndpointURI under ConnectivityProperties .The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?. |
The ConnectivityProperties schema element supports dynamic REST endpoints.The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value. |
The href element points to the Primary Address object link.The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL. |
The href element is invoked by the Oracle ERP Cloud Adapter.13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL. |
13.If necessary, map other nodes under ConnectivityProperties .The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS. |
The runtime values provided by these mappings dynamically configure the request.You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL. |
You can also hover the cursor over these properties for brief descriptions.Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL. |
Element Description AbsoluteEndpointURI Represents the absolute endpoint URL that the REST Adapter invokes.Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?. |
Empty values are ignored.To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL. |
To route the request to an endpoint URL determined at runtime, provide a mapping for this element.AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?. |
AbsoluteEndpointURI takes first precedence among other URL-related properties under ConnectivityProperties .BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL. |
BaseUri The equivalent of the base URL provided during connection configuration.To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters. |
To substitute only the base URI and retain the rest of the URL, provide a mapping for this element.The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false. |
The mapping is ignored if AbsoluteEndpointURI has a nonempty runtime value.RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters. |
RelativeUri Forms the part of the endpoint URI between BaseUri and ?.The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true. |
The mapping has no effect if BaseUri has an empty runtime value or AbsoluteEndpointURI has a nonempty runtime value.The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false. |
The runtime value must start with a /.Chapter 4 Invoke an Endpoint Dynamically 4-7Element Description Uri Use the various elements under this node to substitute runtime values for the specific parts of an endpoint URL.Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded . |
Scheme Provide a mapping to change only the scheme of the endpoint URL.Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set. |
Supported values are HTTP and HTTPS.Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server. |
Host Provide a mapping to change only the Host portion of the endpoint URL Port Provide a mapping to change only the port of the endpoint URL.Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details. |
Query Provide a mapping to change only the query portion of the endpoint URL.A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration. |
A query portion follows the ?.Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime. |
Path Provide a mapping to change only the path portion of the endpoint URL.A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section. |
A Path is the part of a URI between the hostname and ?.Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import. |
Plugin The various properties under this node impact the way the REST Adapter invokes the endpoint URL.PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes. |
PostQueryString When the runtime value is true and the HTTP verb is POST, the query string parameters are sent using POST as form parameters.The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process. |
The default is false.UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs. |
UseFormUrlEncoding When the runtime value is false, the REST Adapter uses RFC 3986-compliant encoding to encode the query parameters.The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard. |
The default is true.This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page . |
This is the equivalent of setting the custom header x-ics-use-x-www-form-urlencoded to false.See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard. |
See section RFC 3986 Support for Encoding Query Parameters for more information on x-ics-use-x-www-form- urlencoded .x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page . |
x-ics-use-x-www-form- urlencoded takes precedence when both are set.14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page. |
14.Drag an FTP Adapter to the switch action for writing the Primary Address object response to a file on an FTP server.15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box. |
15.In the mapper between the Oracle ERP Cloud Adapter and the FTP Adapter, map the Primary Address object details.16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes. |
16.When complete, integration design looks as follows: Chapter 4 Invoke an Endpoint Dynamically 4-8 17.Activate and invoke the integration.The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event. |
The Oracle ERP Cloud Adapter invokes the endpoint URI determined at runtime.Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields. |
Invoke a File-Based Data Import (FBDI) Job To invoke an FBDI job, follow the steps described in this section.An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used. |
An FBDI job invocation works as follows: Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-9 1.Oracle Integration calls Oracle Fusion Applications to perform the bulk import.2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters. |
2.Oracle Fusion Applications uses a business event to return to Oracle Integration in a separate callback integration.Chapter 4 Invoke a File-Based Data Import (FBDI) Job 4-103.The callback integration subscribes to the business event for the import job and is triggered when the import job completes.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section. |
1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process. |
See Financials File-Based Data Imports for a list of FBDI jobs.2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports . |
2.To invoke and configure an FBDI job, select Import Bulk Data into Oracle ERP Cloud on the Actions page of the Adapter Endpoint Configuration Wizard.See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager). |
See Invoke Actions Page .3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort. |
3.Go to the Operations page of the wizard.See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest. |
See Invoke Operations Page .4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job. |
4.Go to the Response page.The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status. |
The following functionality is provided: For new integrations based on the ErpImportBulkDataEvent event: Select the Enable Callback check box.The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source. |
The Oracle ERP Cloud Adapter has been enhanced to enable raising the ErpImportBulkDataEvent event on the Oracle ERP Cloud application when the import job completes.The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter. |
The Integration Flow Identifier and Version fields have been removed because the callback integration now subscribes to the ErpImportBulkDataEvent event.For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories. |
For older, existing callback-based integrations: Select the Enable Callback check box and continue to manually specify details in the Integration Flow Identifier and Version fields.The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import. |
The ErpImportBulkDataEvent event is not used.5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations. |
5.To invoke the FBDI job, you need a ZIP file consisting of a data file in CSV format and a manifest/properties file that has job details such as job name and its parameters.The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory. |
The following documentation provides additional information: Fusion Applications Security Requirements blog (Oracle Fusion Applications security requirements of the user used in the connection) ERP Integration Callback Implementation in Oracle Integration blog (Callback) Using External Data Integration Services for Oracle ERP Cloud Video Invoke a Non-File-Based Data Import (FBDI) Job To invoke a non-FBDI job, follow the steps described in this section.1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration . |
1.Determine whether the job is an FBDI process.See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event . |
See Financials File-Based Data Imports .2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload. |
2.If the job is non-FBDI, perform the following steps: a.Generate the data file based on the template and upload it to Oracle WebCenter Content (Universal Content Manager).Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data. |
Use either ERPIntegrationService::uploadFileToUCM or the Universal Content Manager API / fscmService/GenericSoapPort.b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name. |
b.Invoke ERPIntegrationService::submitEssJobRequest.c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection. |
c.Invoke ERPIntegrationService::getEssJobStatus to get the status of the job.You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper. |
You may need to invoke it multiple times to get the final status.d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration. |
d.Invoke ERPIntegrationService::downloadEssJobExecutionDetails for the logs.Chapter 4 Invoke a Non-File-Based Data Import (FBDI) Job 4-11Use Multiple Callback Integrations for the Same FBDI Job You may have a use case in which you have multiple data sources and require different callbacks for each data source.This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration. |
This use case can be implemented in the Oracle ERP Cloud Adapter.For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection. |
For example, assume you need to create journals from multiple sources and put the log files into the respective source system directories.For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name. |
For source A, you have integration INTA For source B, you have integration INTB, which loads journals using an FBDI bulk import.A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response . |
A callback is enabled for both integrations.The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample. |
The callback log file must placed in the respective source systems directory.Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper . |
Configure a trigger Oracle ERP Cloud Adapter connection as follows: 1.While configuring a callback trigger on the Request page, select Receive Business Events raised within ERP Cloud instead of Receive Callback Message upon Completion of FBDI bulk Import Job submitted via another Integration .2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON . |
2.Select the event ERP Integration Inbound event .3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample. |
3.Configure a filter expression on this event based on the document name in the event payload.Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON . |
Ensure that the document name has a particular format that identifies the source of the data.These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection. |
These actions enable multiple callbacks to be configured depending on the document name.Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details. |
Select Extensible and Descriptive Flexfields in an Integration You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle ERP Cloud Adapter invoke connection.You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name. |
You can then map the EFFs and DFFs in the mapper.The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information . |
The following use case provides an overview of how to design this type of integration.1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list. |
1.Create an orchestrated integration.2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource. |
2.Add a REST Adapter as a trigger connection.3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields. |
3.Enter the following details: a.On the Basic Info page, enter a name.b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts. |
b.On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response .c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields. |
c.On the Request page, select the following: i.Select JSON sample as the request payload and enter the JSON sample.ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields. |
ii.From the Element list, select request-wrapper .iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration. |
iii.For the media type of the request body, select JSON .d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime. |
d.On the Response page, select the following: i.Select JSON sample as the response payload and enter the JSON sample.ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime.10.Activate the integration.Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-145 Troubleshoot the Oracle ERP Cloud Adapter Review the following topics to learn about troubleshooting issues with the Oracle ERP Cloud Adapter. |
ii.From the Element list, select response-wrapper .Chapter 4 Use Multiple Callback Integrations for the Same FBDI Job 4-12iii.For the media type of the response body, select JSON .4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime.10.Activate the integration.Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-145 Troubleshoot the Oracle ERP Cloud Adapter Review the following topics to learn about troubleshooting issues with the Oracle ERP Cloud Adapter.Topics: Bulk Import Troubleshooting Issues Business Event Troubleshooting Issues Failed Messages Are Not Automatically Resubmitted Exception Error Received While Parsing the REST Application Catalog fscmRestApp Oracle ERP Cloud Adapter Error Messages Reactivate Integrations when the Connection URL is Modified Use a Unique File Name for the Upload Request Payload When using PGP Encryption Import Payables Invoice Report Job is Not Triggered Oracle ERP Cloud Callback Not Received in Oracle Integration Error When Discovering REST Services or SOAP Services through the Oracle ERP Cloud Adapter Oracle Universal Content Management (UCM) File Upload Failure Additional integration troubleshooting information is provided. |
4.Add an Oracle ERP Cloud Adapter as an invoke connection.5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime.10.Activate the integration.Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-145 Troubleshoot the Oracle ERP Cloud Adapter Review the following topics to learn about troubleshooting issues with the Oracle ERP Cloud Adapter.Topics: Bulk Import Troubleshooting Issues Business Event Troubleshooting Issues Failed Messages Are Not Automatically Resubmitted Exception Error Received While Parsing the REST Application Catalog fscmRestApp Oracle ERP Cloud Adapter Error Messages Reactivate Integrations when the Connection URL is Modified Use a Unique File Name for the Upload Request Payload When using PGP Encryption Import Payables Invoice Report Job is Not Triggered Oracle ERP Cloud Callback Not Received in Oracle Integration Error When Discovering REST Services or SOAP Services through the Oracle ERP Cloud Adapter Oracle Universal Content Management (UCM) File Upload Failure Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center. |
5.Enter the following details.a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime.10.Activate the integration.Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-145 Troubleshoot the Oracle ERP Cloud Adapter Review the following topics to learn about troubleshooting issues with the Oracle ERP Cloud Adapter.Topics: Bulk Import Troubleshooting Issues Business Event Troubleshooting Issues Failed Messages Are Not Automatically Resubmitted Exception Error Received While Parsing the REST Application Catalog fscmRestApp Oracle ERP Cloud Adapter Error Messages Reactivate Integrations when the Connection URL is Modified Use a Unique File Name for the Upload Request Payload When using PGP Encryption Import Payables Invoice Report Job is Not Triggered Oracle ERP Cloud Callback Not Received in Oracle Integration Error When Discovering REST Services or SOAP Services through the Oracle ERP Cloud Adapter Oracle Universal Content Management (UCM) File Upload Failure Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Bulk Import Troubleshooting Issues This section describes bulk import troubleshooting issues. |
a.On the Basic Info page, enter a name.b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime.10.Activate the integration.Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-145 Troubleshoot the Oracle ERP Cloud Adapter Review the following topics to learn about troubleshooting issues with the Oracle ERP Cloud Adapter.Topics: Bulk Import Troubleshooting Issues Business Event Troubleshooting Issues Failed Messages Are Not Automatically Resubmitted Exception Error Received While Parsing the REST Application Catalog fscmRestApp Oracle ERP Cloud Adapter Error Messages Reactivate Integrations when the Connection URL is Modified Use a Unique File Name for the Upload Request Payload When using PGP Encryption Import Payables Invoice Report Job is Not Triggered Oracle ERP Cloud Callback Not Received in Oracle Integration Error When Discovering REST Services or SOAP Services through the Oracle ERP Cloud Adapter Oracle Universal Content Management (UCM) File Upload Failure Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Bulk Import Troubleshooting Issues This section describes bulk import troubleshooting issues.Topics: How to Pass an Interface Request ID to an Import Job in a Bulk Import Process Bulk Data Import Implementation Recommendations Create a Job Property File for the importBulkData Operation Error Response Received When Invoking a Bulk Import with the Oracle ERP Integration WSDL Import Bulk Data into ERP Cloud Application Option Must Be Reselected in an Imported Integration Jobs Not Appearing in the Import Jobs List on the Operations Page Receive a Callback from an ExportBulkData Operation Configure the Callback for the ExportBulkData Operation Oracle ERP Cloud Callback About the Bulk Import Issue 5-1How to Pass an Interface Request ID to an Import Job in a Bulk Import Process To add a request ID ( {req_id} ) as a parameter in the manifest file/properties file, pass the request ID in a parameter list as {req_id} . |
b.On the Actions page, select Query, Create, Update, or Delete Information .c.On the Operations page, select Business (REST) Resources from the Browse by list.d.Select an appropriate business resource and operation to perform on the resource.e.On the Child Resources page, select child resources with extensible or descriptive flexfields.f.On the Descriptive and Extensible page, select a specific flexfield and associated contexts.6.In the request mapper between the two adapters, map appropriate source and target flexfields.For example: Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-13 7.In the response mapper after the Oracle ERP Cloud Adapter, map appropriate source and target flexfields.For example: 8.Save the integration.9.Create business identifiers for tracking the integration during runtime.10.Activate the integration.Chapter 4 Select Extensible and Descriptive Flexfields in an Integration 4-145 Troubleshoot the Oracle ERP Cloud Adapter Review the following topics to learn about troubleshooting issues with the Oracle ERP Cloud Adapter.Topics: Bulk Import Troubleshooting Issues Business Event Troubleshooting Issues Failed Messages Are Not Automatically Resubmitted Exception Error Received While Parsing the REST Application Catalog fscmRestApp Oracle ERP Cloud Adapter Error Messages Reactivate Integrations when the Connection URL is Modified Use a Unique File Name for the Upload Request Payload When using PGP Encryption Import Payables Invoice Report Job is Not Triggered Oracle ERP Cloud Callback Not Received in Oracle Integration Error When Discovering REST Services or SOAP Services through the Oracle ERP Cloud Adapter Oracle Universal Content Management (UCM) File Upload Failure Additional integration troubleshooting information is provided.See Troubleshoot Oracle Integration in Using Integrations in Oracle Integration Generation 2 and the Oracle Integration Troubleshooting page in the Oracle Help Center.Bulk Import Troubleshooting Issues This section describes bulk import troubleshooting issues.Topics: How to Pass an Interface Request ID to an Import Job in a Bulk Import Process Bulk Data Import Implementation Recommendations Create a Job Property File for the importBulkData Operation Error Response Received When Invoking a Bulk Import with the Oracle ERP Integration WSDL Import Bulk Data into ERP Cloud Application Option Must Be Reselected in an Imported Integration Jobs Not Appearing in the Import Jobs List on the Operations Page Receive a Callback from an ExportBulkData Operation Configure the Callback for the ExportBulkData Operation Oracle ERP Cloud Callback About the Bulk Import Issue 5-1How to Pass an Interface Request ID to an Import Job in a Bulk Import Process To add a request ID ( {req_id} ) as a parameter in the manifest file/properties file, pass the request ID in a parameter list as {req_id} .This dynamically retrieves the load request ID in Oracle ERP Cloud and enables the import process to continue. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.