Integrate DiCentral with Oracle Fusion Cloud SCM
Integrate DiCentral with Oracle Fusion Cloud SCM
Use this recipe to create forecast and sales orders in Oracle Fusion Cloud Supply Chain & Manufacturing (SCM) for original equipment manufacturer (OEM) initiated Electronic Data Interchange (EDI) releases from DiCentral.
Note: This recipe is available as DiCentral — Oracle Fusion Cloud SCM | Manage OEM Releases in the Integration Store. Oracle provides this recipe as a sample only. The recipe is meant only for guidance, and is not warranted to be error-free. No support is provided for this recipe.
Overview
This recipe integrates Oracle Fusion Cloud SCM with DiCentral (a third-party application). It uses DiCentral’s OEM initiated EDI capabilities to gather forecast and firm order information, and complements it with Oracle Fusion Cloud SCM’s supply chain management capabilities to provide release cumulative management.
To use the recipe, you must install the recipe package and configure the connections and other resources within the package. When forecast and sales order information is generated in DiCentral, a REST request is sent to Oracle Integration with the necessary data to create the corresponding forecast and sales order in Oracle Fusion Cloud SCM. Also, when the shipment and invoice for the sales order is generated in Oracle Fusion Cloud SCM, Oracle Integration sends this information back to DiCentral. Additionally, the sales order creation response is also sent back to DiCentral.
The recipe package contains four integration flows. Initially a REST request (with necessary data) from DiCentral triggers the following two integration flows of the recipe.
Oracle DiCentral SCM Forecast Create: This flow receives the EDI forecast from DiCentral and sends the forecast data to Oracle Fusion Cloud SCM for forecast creation.
Oracle DiCentral SCM SalesOrder Create: This flow receives EDI firm orders from DiCentral and invokes Oracle Fusion Cloud SCM to create sales orders. Upon successful order creation, response is sent back to DiCentral.
When the shipment and invoice are fulfilled on the sales orders in Oracle Fusion Cloud SCM, the following two integration flows of the recipe are triggered:
Oracle SCM DiCentral Order Shipment: This flow receives the shipment information from Oracle Fusion Cloud SCM and sends it to DiCentral. When a shipment is created, Collaborative Messaging Framework (CMK) is used to trigger this integration from Oracle Fusion Cloud SCM.
Oracle ERP DiCentral Order Invoice: This integration flow receives the invoice information from Oracle Enterprise Resource Planning (ERP) Cloud when invoice is created for successful shipments and sends it to DiCentral. When an invoice is created, CMK is used to trigger this integration from Oracle ERP Cloud.
System and Access Requirements
Oracle Integration, Version 22.1.3.0.0 or higher
An account on Oracle Integration with the Service Invoker role to configure the recipe
Oracle Fusion Cloud SCM and Oracle ERP Cloud, Version 21D or higher
An account on Oracle Fusion Cloud SCM and Oracle ERP Cloud with the Administrator role
DiCentral
Assumptions
You have installed the REST — Oracle Fusion Applications | Invoke Pop-Up Notifications recipe on your Oracle Integration instance.
You’ll require this recipe to send the notification information to Oracle Fusion Cloud SCM.
To install this recipe, see Invoke Pop-Up Notifications for Events in Oracle Fusion Applications.
Before You Install the Recipe
You must perform the following configuration tasks on your Oracle Fusion Cloud SCM and DiCentral instances to successfully run the recipe.
Configure Oracle Fusion Cloud SCM
To access Oracle Fusion Cloud SCM from Oracle Integration, create forecast and sales orders, and send back sales order response as well as shipment & invoice response, you’ll need to perform the following configuration tasks on your Oracle Fusion Cloud SCM instance.
Perform all the base configurations in Oracle Fusion Cloud SCM, including setting up security, access roles, inventory, order management, receivables and supply chain planning setups.
Configure order management fulfillment line and header extensible flex fields to capture OEM firm order reference information. Receivables invoice lines DFF also need to be configured to maintain the OEM firm order references so that the same information can be sent back to DiCentral via the integration.
Refer to Order management to AR Mapping as per support note 2446740.1.
Configure the Collaboration Messaging Framework (CMK) to establish B2B message exchange for sending shipment and invoice information to DiCentral.
Create a reference/template sales order with a custom order type to reference sales order information.
Create a custom editable measure
EDI Shipments Forecast
to receive forecast data from DiCentral.Create a user account for Oracle Integration on Oracle Fusion Cloud SCM.
Log in to the Oracle Fusion Cloud SCM instance as an Administrator and perform the following tasks.
To access Oracle Fusion Cloud SCM from Oracle Integration, you must create a user account for Oracle Integration. Note the user name and password of the account, as you’ll use these credentials to connect to Oracle Fusion Cloud SCM from Oracle Integration, using the Oracle ERP Cloud adapter.
Assign the required roles to the user account. See Assign Required Roles to an Integration User.
In addition to the above roles, also assign the following roles and privileges to the account:
Accounts Receivable Manager
Demand and Supply Planner
Employee
IT Security Manager
Human Capital Management Integration Specialist
Order Manager
Sales Administrator
Shipping Manager
Integration Specialist
View_All_HCM_Integration_Specialist
AttachmentsUser
SOAOperator
FND_MANAGE_CATALOG_SERVICE_PRIV
Customer Relationship Management Application Administrator
Obtain the Collaboration Messaging Framework (CMK) WSDL. See Overview of Collaboration Messaging Web Services.
Note that you have to download theCollaborationMessageV2Service
WSDL.
Configure DiCentral
To access DiCentral from Oracle Integration, you’ll need to perform the following configuration tasks on your DiCentral instance.
Configure the outbound payloads from DiCentral.
To configure the outbound payloads, you’ll require the following information from the Oracle Fusion Cloud SCM instance. This will be cross referenced from the request coming in from DiCentral to Oracle Fusion Cloud SCM.Customer
Customer Product Number
Product Number
Ordered UOM Code
Bill to Party Number
Bill to Site Identifier
Ship to Party Number
Ship to Site Identifier
Supplier Organization Code
Obtain the endpoint URL for Sales Order response, and Shipment & Invoice response to be sent to DiCentral from Oracle Integration. You’ll require this while configuring connection from Oracle Integration.
Obtain the API key associated with your Dicentral instance. You’ll require this while configuring connection from Oracle Integration.
Install and Configure the Recipe
On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.
On the Oracle Integration home page, scroll to the Accelerators & Recipes section.
Click Search All.
Find the recipe package that you want to install.
Select the package, and then click the Install
icon.
After the package is installed, click the Configure
icon on the recipe card to configure the resources deployed by the package.
The Configuration Editor page opens, displaying all the resources of the recipe package. Configure the following resources before you activate and run the recipe.
Configure the Oracle REST OIC API Connection
On the Configuration Editor page, select Oracle REST OIC API Connection, then click Edit
.
The connection configuration page appears.In the Connection Properties section, enter the following details.
Field Information to Enter Connection Type Leave REST API Base URL selected. Connection URL Enter the host name of your Oracle Integration instance. In the Security section, enter the following details.
Field Information to Enter Security Policy Select Basic Authentication. Username Enter the username of the Oracle Integration user account with the Service Invoker role. See System and Access Requirements. Password Enter the password of the Oracle Integration user account with the Service Invoker role. Click Save. If prompted, click Save for a second time.
Click Test to ensure that your connection is successfully configured. In the resulting dialog, click Test again.
A confirmation message is displayed if your test is successful.Click Back
to return to the Configuration Editor page. Click Save again if prompted.
Configure the Oracle ERP Cloud Connection DiCentral
On the Configuration Editor page, select Oracle ERP Cloud Connection DiCentral then click Edit
.
The connection configuration page appears.In the Connection Properties section, enter the Oracle Fusion Cloud SCM host name.
For example,https://your_domain_name.fa.DC.oraclecloud.com
.In the Security section, enter the following details.
Field Information to Enter Security Policy Select Username Password Token. User Name Enter the username of the user account created for Oracle Integration on Oracle Fusion Cloud SCM. See Configure Oracle Fusion Cloud SCM. Password Enter the password of the user account created for Oracle Integration on Oracle Fusion Cloud SCM. Click Save. If prompted, click Save for a second time.
Click Test to ensure that your connection is successfully configured. In the resulting dialog, click Test again.
A confirmation message is displayed if your test is successful.Click Back
to return to the Configuration Editor page. Click Save again if prompted.
Configure the Oracle REST DiCentral Sales Order Connection
On the Configuration Editor page, select Oracle REST DiCentral Sales Order Connection, then click Edit
.
The connection configuration page appears.In the Connection Properties section, enter the following details.
Field Information to Enter Connection Type Leave REST API Base URL selected. Connection URL Enter the Sales Order Response endpoint you obtained from DiCentral. See Configure DiCentral. In the Security section, enter the following details.
Field Information to Enter Security Policy Select API Key Based Authentication. API Key Enter the API key you obtained from DiCentral. See Configure DiCentral. API Key Usage Ensure that the following is configured:
-H Authorization: Bearer ${api-key}
Click Save. If prompted, click Save for a second time.
Click Test to ensure that your connection is successfully configured. In the resulting dialog, click Test again.
A confirmation message is displayed if your test is successful.Click Back
to return to the Configuration Editor page. Click Save again if prompted.
Configure the Oracle REST DiCentral Shipment Invoice
On the Configuration Editor page, select Oracle REST DiCentral Shipment Invoice, then click Edit
.
The connection configuration page appears.In the Connection Properties section, enter the following details.
Field Information to Enter Connection Type Leave REST API Base URL selected. Connection URL Enter the Shipment and Invoice endpoint you obtained from DiCentral. See Configure DiCentral. In the Security section, enter the following details.
Field Information to Enter Security Policy Select API Key Based Authentication. API Key Enter the API key you obtained from DiCentral. See Configure DiCentral. API Key Usage Ensure that the following is configured:
-H Authorization: Bearer ${api-key}
Click Save. If prompted, click Save for a second time.
Click Test to ensure that your connection is successfully configured. In the resulting dialog, click Test again.
A confirmation message is displayed if your test is successful.Click Back
to return to the Configuration Editor page. Click Save again if prompted.
Configure the Oracle SOAP OIC Connection
On the Configuration Editor page, select Oracle SOAP OIC Connection, then click Edit
.
The connection configuration page appears.In the WSDL URL field of the Connection Properties section, upload the WSDL file that you downloaded from your Oracle Fusion Cloud SCM instance. See Configure Oracle Fusion Cloud SCM.
In the Security field, select Basic Authentication.
Click Save. If prompted, click Save for a second time.
Click Test to ensure that your connection is successfully configured. In the resulting dialog, click Test again.
A confirmation message is displayed if your test is successful.Click Back
to return to the Con
Configure the Lookup Table
Edit the lookup table, and enter the necessary values. On the Configuration Editor page, select the lookup table, and click Edit.
This recipe package contains the following lookup table.
Oracle-BRT-SCM_DiCentral_Configuration
This lookup table contains the information needed to create a sales order in Oracle Fusion Cloud SCM. The following table provides the description for each parameter:
Name | Description |
---|---|
SourceTransactionSystem | Transaction source system identify the source of transactions that you import into Oracle Fusion Cloud Cloud SCM. Example value: DIC
|
MeasureName | Measure name to import sales forecasts to Oracle ERP Cloud. Example value: EDI Shipments Forecast
|
Currency | Currency used for sales order transaction. Example value: USD
|
DeletePreviousForecast | Flag to delete the previous imported forecasts. Example value: No
|
EmailNotification | Notify the end user if any error occurs in the integration process.
|
OrderTemplateName | A sales order to provide the value for sales order transaction in Oracle Fusion Cloud SCM. Example value: DIC_TEMPLATE_ORDER
|
EffContextCodeVO | The VO ContextCode defined for FlexFields as per Oracle Fusion Cloud SCM. Example value: FulfillLineEffBEDI_Release_InformationprivateVO
|
SalesOrder_Notification_User | User name of the fusion user who receives the Fusion pop-up notifications. This value is case sensitive. Example value: Robert.James
|
SalesForecasts_Notification_User | User name of the fusion user who receives the Fusion pop-up notifications. This value is case sensitive. Example value: jack.wells
|
TaskCreatorForNotificationUser | Name of the task creator which is displayed in the Fusion pop-up notification. Example value: DiAutomotive
|
ContextCodeName | The EFF ContextCode defined for FlexFields as per Fusion configuration. Example value: EDI Release Information
|
Activate and Run the Recipe
After you’ve configured the connections and the lookup table, activate the recipe package and run it.
On the Configuration Editor page, click Activate in the title bar. In the Activate Package dialog, click Activate again.
A confirmation message is displayed informing that the integration has been submitted for activation. Refresh the page to view the updated status of the integration.Run the recipe.
Obtain the endpoint URLs for the trigger integration flows, namely Oracle DiCentral SCM Forecast Create and Oracle DiCentral SCM SalesOrder Create.
On the Configuration Editor page of Oracle Integration, select an integration flow and click Run
.
On the resulting pop-up dialog, click the Metadata URL link.
From the new tab that opens, copy the Endpoint URL value.
Log in to your DiCentral instance and configure it to perform the following actions to send forecast and firm orders.
Send a
POST
EDI forecast request to the Oracle DiCentral SCM Forecast Create endpoint URL (obtained in the previous step) along with the forecast data.Send a
POST
EDI firm order request to the Oracle DiCentral SCM SalesOrder Create endpoint URL (obtained in the previous step) along with the firm order data.
When the recipe receives these
POST
requests it will send the forecast or firm order requests to Oracle Fusion Cloud SCM.Obtain the endpoint URLs for the integration flows, namely Oracle SCM DiCentral Order Shipment and Oracle ERP DiCentral Order Invoice.
On the Configuration Editor page, select an integration flow and click Run
.
On the resulting pop-up dialog, click the WSDL URL link.
From the new tab that opens, copy the WSDL URL value. Leave out ?wsdl from the URL, and note the URL.
Log in to Fusion Applications, and configure the shipment and invoice endpoints in Fusion CMK, so that when a shipment or invoice is created in Oracle Fusion Cloud SCM, the recipe sends the information to DiCentral.
Navigate to Collaboration Messaging under Tools. Click Tasks, then click Service Providers, and then select Manage Collaboration Messaging Service Providers.
Open the service provider that you had set up as part of Fusion CMK configuration.
Note: If not already configured, you can configure Web Services as delivery method for both shipment and invoice outbound CMK messages.
Update the service provider using the WSDL URLs you have obtained in the previous step.
Update Shipment Provider:
Field Information to Enter Name Name of your Shipment Out delivery method. For example, SHIPMENT_OUT. Delivery Method Type Web Service Service Name CollaborationMessageV2.process End Point Endpoint URL of the shipment webservice. User Name Enter the username of the Oracle Integration user account with the Service Invoker role. See System and Access Requirements. Password Enter the password of the Oracle Integration user account with the Service Invoker role. Update Invoice Provider:
Field Information to Enter Name Name of your Invoice Out delivery method. For example, INVOICE_OUT. Delivery Method Type Web Service Service Name CollaborationMessageV2.process End point Endpoint URL of the shipment webservice. User Name Enter the username of the Oracle Integration user account with the Service Invoker role. See System and Access Requirements. Password Enter the password of the Oracle Integration user account with the Service Invoker role.
Log in to your Oracle Fusion Cloud SCM as Supply Chain Planner and check if the forecast is created.
Click the Tools tab on the home page, and then select Scheduled Processes. Ensure that the collection requests have been completed.
Click Supply Chain Planning, and then select Demand and Supply Planning.
Open the plan that you created and run the plan with the following options.
Refresh with Current Data: Yes
Forecast Shipments: Yes
When the execution is complete, you can review the plan including exceptions.
Log in to Oracle Fusion Cloud SCM as the Order and Shipping Clerk, and check for the new order. After the order is fulfilled, ship the order fulfilment line and generate the invoice.
Check if a new sales order is created and view its details.
Click the Bell icon on the top-right corner to view the order creation notifications.
Copy the Document Reference Number from the notification message.
Search for the new order with the Document Reference Number. The new order is displayed with information such as customer name, quantity, and so on.
Note the order number. You’ll use it later to ship the order.Click Additional Information in the header to view the OEM specific firm order information received from DiCentral.
Select the fulfillment line with earliest shipment date. Observe the order status. It should show Awaiting Shipping.
Click Additional Information on the right for the selected fulfilment line and view the additional flex fields.
To ship the selected fulfilment line, click Supply Chain Management and then click Inventory Management.
Select Show Tasks: Shipments and search for the order with the order number you noted down earlier.
Select the fulfillment line with earliest ship date. Enter the same Shipped Quantity as Requested Quantity and click Save.
Note: The recipe doesn’t support split lines.
Click AutoCreate Shipment.
Click the shipment you just created. Click Actions, and then click Pick Release. Click Actions again and click Pack Automatically.
Click Ship Confirm.
When the order is shipped, the integration Oracle SCM DiCentral Order Shipment is triggered, and it sends the shipment information to DiCentral.
To generate an invoice for the shipment, click the Tools tab on the home page, and then select Scheduled Processes.
- Schedule a new process for Import AutoInvoice. Run the process for the order you shipped.
Once the process completes, an invoice is generated.
When the invoicing process completes, the integration Oracle ERP DiCentral Order Invoice is triggered, and it sends the invoice information to DiCentral.
- Schedule a new process for Import AutoInvoice. Run the process for the order you shipped.
If the request from DiCentral contains updates to existing orders, you should see the updates in the order. Updates could be for the quantity or dates.
At any stage while running the recipe, you can monitor the execution of the integration flows in Oracle Integration.
On the Configuration Editor page, select any integration flow.
Click Run
, then click Track Instances.
On the Track Instances page, you’ll see the integration flows of the recipe being triggered and executing successfully.
Finally, log in to your DiCentral instance and verify if the order creation response, and the shipment and invoice information have been received.
To verify if the order creation response is received:
Navigate to Customer Demand Mgt and then Firm Orders.
Filter the records using trading partner you have used for sending the request to Oracle Fusion Cloud SCM.
The orders created with Oracle Fusion Cloud SCM are displayed. The External Reference Number shows the order key for each order created in Oracle Fusion Cloud SCM.Search for the required record and click it to view details. Check if the record details match with the order created in Oracle Fusion Cloud SCM.
To verify if the shipment information is received:
Navigate to Customer Shipments and then Shipments.
Filter the records using trading partner you have used for sending the request to Oracle Fusion Cloud SCM. Search will display records with individual ship IDs.
Click the record for which you want to view details. Check if the shipment record details match with the shipment created in Oracle Fusion Cloud SCM.
To verify if the invoice information is received:
Navigate to Customer Financing and then Invoice.
Filter the invoices using trading partner you have used for sending the request to Oracle Fusion Cloud SCM. Invoice records are displayed.
Click the required invoice record, and view its summary in the General tab. Check if the invoice record details match with the invoice generated for the shipment in Oracle Fusion Cloud SCM.
To view the comparison between Requested, Shipped, and Invoice Quantity, click the Details tab.
Related Documentation
- Using the REST Adapter with Oracle Integration
- Using the Oracle ERP Cloud Adapter with Oracle Integration
Integrate DiCentral with Oracle Fusion Cloud SCM
F58575-01
June 2022
Copyright © 2022, Oracle and/or its affiliates.
Primary Author: Oracle Corporation