The Target system configuration dialog: Oracle Financials Cloud
Use these settings to configure the Oracle Financials Cloud integration.
To access this dialog: Select a Services node in the administration tree-view on the partner level or customer level, select Target system, select Oracle Financials Cloud and click Configuration.
The settings that appear here vary, depending on the target system, version and current account level. Use these settings to specify settings for the target service:
| Output image format | Determines the format of the output invoices.
If you change the output format, the change only applies to invoices that you upload after the change was made. Invoices that are already in the system at the time of the change are not affected. |
| TEST | |
| Checks if the integration can connect to Oracle Financials Cloud using the connection settings. | |
| CONNECTION | |
| System URL | The URL that you use to connect to the Oracle Financials Cloud system. |
| User name | The user name to use to connect to Oracle Financials Cloud. The user you specify must have privileges to perform many functions in Oracle Financials Cloud, such as creating invoices, reading suppliers and purchase orders etc. |
| Password | The password of the Oracle Financials Cloud user. |
| INTEGRATION | |
| Default distribution combination | The distribution combination to use by default. |
| Distribution combination template | A
data template that determines the format of distribution combinations. Default value:
%$BuyerExternalId%-%AccountCode% |
| Automatically insert net amount lines | Adds net amount lines to invoices that are missing line-item tables. |
| Default payment method code | Determines the default payment method code if none is specified during verification. |
| Header field mapping |
The data template to use when mapping Kofax AP Essentials data to payables header fields in Oracle. Use this setting if you need to map additional fields or information that are not already provided by the default field mappings. You can also use this setting to override default field mappings. Separate multiple field mappings using semicolons. |
| Line-item field mapping |
The data template to use when mapping Kofax AP Essentials data to payables line-item fields in Oracle. Use this setting if you need to map additional fields or information that are not already provided by the default field mappings. You can also use this setting to override default field mappings. Separate multiple field mappings using semicolons.
Mapping is not supported for net amount and freight line-item fields.
|
| Descriptive flexfield template |
The data template to use when mapping Kofax AP Essentials data to payables descriptive flexfields in Oracle. Separate multiple field mappings using semicolons. |
| Line-item descriptive flexfield template |
The data template to use when mapping Kofax AP Essentials data to line-item descriptive flexfields in Oracle. Mapping is not supported for net amount and freight line-item fields.
|
| Link to invoice images in Kofax AP Essentials storage |
Saves space in Oracle Financials Cloud by linking to invoice images in Kofax AP Essentials storage instead of sending invoice images to Oracle. The link to the invoice image is added to the invoice as an attachment in Oracle. When viewing invoice information in Oracle, you can click the link to open the invoice image in your web browser. This setting is only visible if the Storage service is enabled. To use this feature, Create image link must be selected in the Storage settings. |
| Document and purchase order currencies must match | If the currency on the document differs from the currency, an information message appears. |
| Document and purchase order suppliers must match | If the supplier on the document differs from the supplier of the purchase order, an information message appears. |
| Document and purchase order supplier sites must match | If the supplier site on the document differs from the supplier site of the purchase order, an information message appears. |
| Normalize supplier sites | Removes the supplier number and dash from the supplier site field before sending the invoice to Oracle. |
| Map buyers to legal entities | Enables the mapping of buyers in
Kofax AP Essentials
to legal entities in Oracle. Selecting this setting also displays the
Business unit name setting.
When this setting is not selected, buyers in Kofax AP Essentials are mapped to the business units in Oracle where the buyer name matches the business unit name. The external ID of the buyer is also used to specify the coding segment value. When this setting is selected, you specify the business unit name of the legal entity you want to map to, and the external ID of the buyer specifies the a legal entity ID or legal entity name in Oracle. You can use the Buyer-specific settings to map individual buyers to legal entities. |
| Business unit name |
Specifies which buyers in Kofax AP Essentials correspond to a business units in Oracle. You must select Map buyers to legal entities to display this setting. Use the Buyer-specific settings to specify business units for individual buyers. When testing the integration settings, by clicking TEST, if any errors are detected in the Buyer-specific settings, this setting is highlighted in this view, but you must click Buyer-specific settings to correct any highlighted settings in the buyer-specific settings view. |
| SUPPLIERS | |
| Synchronize default payment methods | Retrieves default payment methods during supplier master data synchronization. |
| Create a supplier for each supplier site | Creates a supplier in Kofax AP Essentials for each supplier site in Oracle. |
| Filter supplier types | When importing supplier master data, only suppliers that match the supplier types you specify here
are imported. Separate multiple supplier types with commas.
Example: Supplier, Contractor, Sub-Contractor Leave this setting blank to import all suppliers. |
| Exclude inactive supplier sites | Excludes inactive supplier sites during master-data synchronization, so only active supplier sites are imported to Kofax AP Essentials. |
| PURCHASE ORDERS | |
| Import received quantities from purchase order | Automatically populates line-item received quantities in Kofax AP Essentials using PO data from Oracle. |
| Import invoiced quantities from purchase order | Automatically populates line-item invoiced quantities in Kofax AP Essentials using PO data from Oracle. |
| Additional PO statuses | A comma-separated list of extra purchase-order statuses that you want to synchronize in addition
to "OPEN" and "CLOSED FOR RECEIVING".
"OPEN" and "CLOSED FOR RECEIVING" PO statuses are synchronized by default, so you do not need to specify them here.
Not all statuses are available to the
Additional PO statuses setting by default.
Contact
support if you want to import purchase orders
with a status that is not available.
|
| GENERAL LEDGER ACCOUNTS | |
| Synchronize master data using Oracle reports |
Determines whether data from coding combination reports are synchronized automatically from Oracle reports. We recommend using the Synchronize master data using Oracle REST API setting below instead. Using the Oracle REST API requires the least amount of setup. Optionally, you can import accounting data manually by exporting the coding combination reports and using the Master-data import app for Microsoft Excel to import the data to Kofax AP Essentials.
You cannot select
Synchronize master data using Oracle reports
and
Synchronize master data using Oracle REST API
at the same time. Choose one or the other, but not both.
|
| Report job path | The path to the report job for accounting master data. |
| Report job name | The name of the report job for accounting master data. |
| Account type | The type of entries the in job report for GL accounts. |
| Coding field types | A comma-separated list of the type of entries in the job report for coding segments. |
| Synchronize master data using Oracle REST API | Determines whether master data is synchronized automatically using the Oracle REST API. This is the
recommended method which requires the least amount of setup compared to
Synchronize master data using Oracle reports.
You cannot select
Synchronize master data using Oracle reports
and
Synchronize master data using Oracle REST API
at the same time. Choose one or the other, but not both.
|
| GL-account segment | The coding segment API name for GL accounts. |
| Other coding segments | A comma-separated list of the coding segment API names. |
| TAX HANDLING | |
| Synchronize tax classification | Retrieves tax-classification master data from Oracle, which you can use for field suggestions during verification. |
| Synchronize ship-to location | Retrieves location master data from Oracle, which you can use for field suggestions during verification. |
| ITEMS | |
| Inventory organization code |
Determines what item master data is imported. The inventory organization code is simply called "Organization" or "OrganizationId" in Oracle; it is not the "Organization Name". When you specify an inventory organization code here, only items from that organization are imported as master data. You can click Buyer-specific settings to specify inventory organization codes on the buyer level. When testing the integration settings, by clicking TEST, if any errors are detected in the Buyer-specific settings, this setting is highlighted in this view, but you must click Buyer-specific settings to correct any highlighted settings in the buyer-specific settings view. |
If you have network restrictions on IP addresses, Kofax AP Essentials uses these IP addresses to connect to Oracle:
| Europe |
|
| US |
|
| Australia |
|