1. Online Help
  2. Before You Begin

Before You Begin

To access the Reconciliation Workbench Dashboard and fetch error counts for your desired integration type, you need to set the configurations in WMS and OIC.

WMS Configurations for SCM Reconciliation Workbench

Configure Modules in WMS

Add the following modules to your respective group menu before accessing the SCM Reconciliation Workbench interface.

  • Reconciliation Workbench UI (ReconciliationDashboardView)
  • Inventory Discrepancy UI (InventoryDiscrepanciesView)
  • ERP Inventory Summary (ErpInventorySummaryView)
  • WMS Inventory Summary UI (WmsInventorySummaryView)

Configure OIC-CLOUD and ERP-CLOUD in the SAAS App UI

In the Reconciliation Workbench, all errors from WMS, Fusion Inventory and, OIC are fetched and displayed in a user-friendly dashboard. To investigate further and improve error handling, you're directed to OIC and ERP error screens for more information.

The SaaS App Configuration UI includes the following options and parameters in the App Name drop-down list:

  • OIC-Cloud
  • ERP-Cloud SaaS App Config

Base URL Field: You're required to define the Base URL for the relevant application and create records. This URL redirects/access data from other application.

To display errors in the Workbench from WMS, ERP, and OIC, you need to configure OIC and ERP apps in the SaaS App Configuration UI.
  1. Go to the SaaS App Configuration UI.
  2. Click Create (+) and select either OIC-CLOUD or ERP-CLOUD from the Apps Name drop-down list.
  3. Select Company and Facility from the drop-down lists.

    You can either choose * to select all companies/facilities or a specific one.

  4. Define the Base URL for the relevant application and create records:
    1. After you select OIC-CLOUD, the parameter fields are labeled as “App parm3”, “App parm4,” and so on.
      IMPORTANT NOTE: These field names don't indicate their purpose within the SaaS App Configuration screen. Please see the following table for each parameter’s representation and format required. If you need extra information to complete the following fields, contact, Oracle Product Support via an SR.

      SaaS App Fields

      Field Name Description Sample Format
      Base URL

      Base URL defines the relevant application and create records. This URL will redirect users to the respective applications.

      For more information on the Base URL (Design-time URL) – see Using Integrations in Oracle Integration 3      		 sample: https://design-xxxxx-integration-xxxx-xxxxx-xx.xxxxxxxxxx.us-xx-1.oxx.oc-test.com
      App parm3

      Enter the Integration Instance.

      You can find the Oracle Integration (OIC) runtime URL in the Oracle Cloud Infrastructure (OCI) Console by navigating to the specific OIC Integration instance’s details page and look for the “Runtime URL”.

      Alternatively, if you have the instance name, the general format is:

      sample: https://[instance-name].integration.[region].ocp.oraclecloud.com

      with the full runtime path following the base URL.” The “instance-name” is provided in the OIC “About Box”.

      For more information on the App parm 3 URL (Runtime URL) – see Using Integrations in Oracle Integration 3      		 sample: https://[instance-name].integration.[region].ocp.oraclecloud.com
      App parm4

      Enter the Scope

      You need to go to your OIC-integrated application’s Oauth configuration in your respective OCI domain to fetch this App parameter.

      		 sample: https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.integration.us-xxxxxxx-1.ocp.oc-test.com:443xxx:oxx:resource:consumer::all
      App parm5

      Enter the Access Token URL

      The Oracle Cloud Infrastructure (OCI) Identity Cloud Service (IDCS) token URL is the base IDCS URL with /oauth2/v1/token appended. You can find your specific IDCS base URL by logging into the Oracle Cloud Console, and it will look like:

      sample: https://{your_tenant}.identity.oraclecloud.com/

      The full URL to obtain a token would then be:

      https://{your_tenant}.identity.oraclecloud.com/oauth2/v1/token

      		 sample: https://{your_tenant}.identity.oraclecloud.com/oauth2/v1/token
      App parm6 Enter the Client ID

      In your OCI Instance follow the path “Identity and Security” --> Domains --> select the domain that hosts the OIC instance. From the Domain screen, click “Oracle Cloud Services” tab. Search or browse to your OIC application, click to open

      		 Click “Oauth Configuration”. You’ll find the details needed for App parm6 under General Information, in the Client ID field.
      App parm7 Disabled NA
      App parm8

      Enter the Client Secret

      In your OCI Instance follow the path “Identity and Security” --> Domains --> select the domain that hosts the OIC instance. From the Domain screen, click the “Oracle Cloud Services” tab. Search or browse to your OIC application, click to open.

      Click “Oauth Configuration”. You’ll find the details needed for App parm8 under General Information, in the Client Secret field.
    2. On selecting ERP-CLOUD, configure your environment with the following field information:

      Configurations Fields for ERP Cloud

      Field Name Description Sample Format
      Base URL Base URL defines the relevant application and create records. This URL will redirect users to the respective applications. sample: https://xxxxxxxxx.fusionapps.xxx.xx-test.com
      App parm3 Enter the user name (Basic Oauth authentication is used) User001
      App parm4 Blank NA
      App parm5 Blank NA
      App parm6 Blank Na
      App parm7 Blank NA
      App parm8 ERP Credentials 1x2x6x4x-xx27-4xx9-9991-27xxxx48xxxx
  5. Click Save.

Configure Output Interface for Integration Type

In order to filter integration-related errors, and display the records on the Reconciliation Workbench Dashboard, you need to configure the integration type in the End point UI.
  1. Go to the End Point UI, create, and enter all the required fields.
  2. From the Integration Name drop-down list, choose to configure relevant integrations from the following options: Integration Name
    • Receipt Confirmation (covers both receipt and putaway confirmation)
    • Shipment Confirmation
    • Inventory Transaction
    • Movement Request Pick Confirmation
    • Movement Request Pick Cancellation
    • Back Order
Note: The column 'Integration name' is displayed on the data grid to show the drop-down list value if configured. By default, this column is disabled and users need to explicitly add this column and can download the record via CSV export.

Set Schedule Jobs to Fetch Error from WMS

The Reconciliation Workbench dashboard gives you a single view of integration errors. To keep this dashboard up to date, dedicated Scheduled Jobs are introduced that automatically fetch error information from various sources.

These scheduled jobs capture error counts for specific integration processes and display them in an easy-to-understand format on the dashboard. The jobs fetch error information from following sources:
  • WMS stage table
  • ERP system
  • OIC (Oracle Integration Cloud)

Configure Schedule Jobs for Integration Recipes

To periodically fetch errors counts, you must schedule the following Job Type for respective Integration Type:

Before you configure and run the schedule job, refer to Important Key Notes
  1. Go to the Schedule Job UI, select the following Schedule Job from Job Type drop-down list for Integration Type:

    Integration Type

    Schedule Job Integration Type Description Sub-type
    Receipt Advice/ Confirmation Error count Multi Facility Receipt Advice/ Receipt Confirmation

    This job extracts error counts related to receipt advice and receipt confirmation from respective sub-types.

    		 WMS – Fetches stage table error count for PO and ASN.
    WMS – Fetches output interface and inventory history error count for receipt confirmation.
    OIC – Fetches error count for receipt advice and receipt confirmation
    Fusion – Fetches error count for receipt confirmation.
    Inventory Transactions Error Count Multi Facility Inventory Transaction

    This job extracts the error counts related to inventory transaction errors from respective sub-types

    		 WMS – Fetches output interface and inventory history error count for Inventory transactions.
    OIC – Fetches error count for Inventory transaction.
    Fusion – Fetches error count for Inventory transaction.
    Ship Request/Confirmation Error Count Multi Facility Shipment Request/ Shipment Confirmation

    This job extracts the error counts related to inventory transaction errors from respective sub-types

    		 WMS – Fetches stage table error count for Sales Order
    WMS – Fetches output interface (SLS – Load and parcel) error count for Ship confirmation
    OIC – Fetches error count for ship request and ship confirmation
    Fusion – Fetches error count for ship confirmation
    ERP Inventory Summary Error Count Multi Facility ERP Inventory Summary

    This job extracts the error counts related to inventory transaction errors from respective sub-type

    		 WMS – Fetches stage ERP-INV-SUMMARY input interface for the ERP Inventory Summary integration type
    OIC – Fetches error count for ERP Inventory Summary integration type.

    Movement Request/Pick Confirmation Error Count Multi-Facility

    Manufacturing Movement Request

    		 This job extracts error lists about Movement Request (from WMS and OIC) WMS-Movement Request – Fetches errors for WMS-Movement Request stage error list
    WMS Manufacturing Transaction – Fetches errors for Work Order Direct transactions in WMS.
    OIC – Fetches OIC error list corresponding to Movement Request and Work Order Direct transactions.

    Manufacturing Pick Confirm/Cancel

    		 This job extracts respective error lists about Pick Confirm/Cancel (from WMS and OIC). WMS- Inventory History – Fetches errors related to WMS Inventory History
    WMS-IHT – Fetches errors related to IHT
    OIC – Fetches OIC error list corresponding to Pick confirm and Pick Cancel transactions
  2. Select the Schedule type and enter all the required fields.
  3. Define the following common required Job Parameter:
    1. User name: We recommend that the user name provided here must have access to all facilities and companies in a 3PL environment. This is to ensure on not missing any potential error counts for specific facilities due to access limitation.
      Note: If the field is blank, the system displays an error message “Missing required field/fields: %MISSING_FIELDS”.
    2. Facility code: Enter the facility. On specifying * denotes all the facilities that the user is eligible. You can provide multiple facilities with comma separated.
  4. Click Save.

    After configuring the Schedule Job Type, you can run the scheduler per the schedule type to fetch the error periodically.

  5. From the Schedule Job UI, select the Job type and click Enable/Disable button to run the schedule job type.

RECOMMENDATION: WE RECOMMEND SETTING THE SCHEDULE JOB FREQUENCY LESS THAN 24 HOURS. This is to ensure that the error counts captured is displayed on the 24-hours bar graph.

Important Key Notes to Consider before Running the Schedule Job Type:

  • These scheduled job runs might get intensive. Hence, we DON'T allow creating multiple active copies of this job type or schedule the run too often.
  • To limit or restrict users, a 'Prevent copy' mark in the schedule job UI is set to YES/enabled ONLY for these Job type.
    Note: You can create only one active job across facilities. If you try to copy this job type, an error “Duplicate job not allowed, this job is active for facility <FAC_CODE>” is displayed.
  • However, if a job is canceled at a facility, you can create an active job at another facility. But only one job can be active at a time. When a job is active at a facility, you'll not can revive the job in another facility and the same error message as above will be displayed.
  • To limit the schedule job run frequency, the workbench will restrict scheduling the job to run at intervals less than 60 minutes (1 hour). If try, it will display an error “Job interval can't be less than 60 mins (new message)”.
  • Also, when using crontab scheduling, only integer values will be allowed for the minute field to prevent frequent execution. Otherwise, the system displays an error “This job type supports only integer values for minutes”.

Capturing Error Count for Each Integration Recipe

We capture the error count for each integration recipe and show the corresponding error count per schedule job run. To get the errors related to the prebuilt integrations periodically from all user-eligible facilities, we introduce an Intermediatory table to capture these error counts for the integration types of receipt advice, receipt confirmation, ship request, ship confirmation, inventory transactions, and ERP Inventory Summary, etc, per facility and company combinations, so that the Reconciliation workbench displays an appropriate data from the table.