Oracle E-Business Suite Extensions for Oracle Endeca Integration and System Administration Guide Release 12.1 V5 Part Number E37993-08 | ![]() Contents | ![]() Previous | ![]() Next |
This chapter covers the following topics:
You can use Oracle Warehouse Management (WMS) Extensions for Oracle Endeca to search and filter outbound, inventory, and labor (productivity) information from the warehouse. Using the Warehouse Management Endeca pages, you can review and analyze data using key Performance Indicators (KPIs), performance evaluation metrics, charts, graphs, and tables. In addition to the search and filter capabilities, each WMS page contains action-based analytics where you can diagnose an issue and take specific actions.
You can search using Warehouse Management pages and Endeca Information Discovery (EID) design tools. These pages are container pages in WMS and each page, region, and tab calls the respective page from an Endeca environment. In Warehouse Management, the following pages enable search functions using Endeca Information Discovery integration:
Plan Fulfillment page: The Plan Fulfillment page lets you search for and plan the fulfillment batches and waves.
Track Fulfillment page: The Track Fulfillment page lets you track the fulfillment process and react in real-time to changes impacting outbound activities.
Space Utilization page: The Space Utilization page lets you track the fragmentation in the warehouse and suggest material movement to manage fragmentation.
Labor Utilization page: The Labor Utilization page lets you plan and manage labor in the warehouse.
This chapter provides product-specific details required to integrate Endeca Information Discovery (EID) with Oracle E-Business Suite Release 12.1 V5 for the Oracle Warehouse Management Extensions for the Oracle Endeca application. This supplements information provided in Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1 V5 (Doc ID: 1683053.1). You must read this document and make note of the requirements before you begin your installation.
The Plan Fulfillment page lets you plan the fulfillment batches and waves. You can view outbound logistics metrics, charts, and results tables. The following displays the Plan Fulfillment page.
From the Warehouse Manager responsibility, navigate to the Plan Fulfillment page:
(N) Outbound Logistics > Plan Fulfillment
The following describes the Endeca Warehouse Management Plan Fulfillment page regions and components:
Region | Components |
---|---|
Sub Tabs (page links) |
|
Search Box | You can use the Search Box to filter data using user search criteria. |
Filters | You can use Filters to refine the displayed data to only include records that have specified attribute values. |
EBS Links List | The EBS Links List region displays links to associated pages. You can select the Create Wave link to navigate to the Create Wave page. Filters selected on the Plan Fulfillment page are active and the default values on the Create Wave page when you select this link. If multiple filter values are selected for an attribute, then the first selected filter value for that corresponding attribute is active and is the default value in the Create Wave' page. The following message displays in the Create Wave page: "Attribute(s) <<ATTRIBUTE1>>,<<ATTRIBUTE2>> have multiple values. Only first value is defaulted." |
Guided Navigation | You can use the Guided Navigation component to filter data using the following attributes:
|
Metric (metrics bar)
Note: The Metric Components are color coded to highlight warnings and health. |
|
Order Types (tag cloud) | Top Ten Order Types Tag Cloud Component
Note: The Order Types tag cloud component displays the top ten Order Types by frequency of occurrence. |
Items (tag cloud) | Top Ten Items Tag Cloud Component
Note: The Items tag cloud component displays the top ten items by frequency of occurrence. |
Demand (chart)
Note: This chart displays total demand by sale value in the appropriate currency and the primary quantity requested for top and bottom 20. 'Top 20 By Total Value' is the default view. | Total Value by Customer
|
Demand & Availability (chart) | Demand, Reserved, Crossdocked, On-hand by Item
|
Unfulfilled Demand (tabbed component container)
Note: This results table displays relevant attributes for sales order demand and availability. | Unpicked Details (results table)
|
Item Reservations (tabbed component container) | Item Reservations (results table)
|
Waves (tabbed component container)
Note: This results table displays Wave details. | Waves (results table)
|
The Track Fulfillment page lets you track the fulfillment process and react in real-time to changes impacting the outbound activities. You can view outbound logistics metrics, charts, and results tables. The following is a display of the Track Fulfillment page.
From the Warehouse Manager responsibility, navigate to the Track Fulfillment page:
(N) Outbound Logistics > Track Fulfillment
The following describes the Endeca Warehouse Management Track Fulfillment page regions and components:
Region | Components |
---|---|
Filters | You can use Filters to refine the displayed data to only include records that have specified attribute values. |
Guided Navigation | You can use the Guided Navigation component to filter data using the following attributes:
|
Metric (metrics bar)
Note: The Metric Components are color coded to highlight warnings and health. |
|
Delivery Exceptions (tag cloud) | Top Ten Delivery Exceptions Tag Cloud Component
Note: The Delivery Exceptions tag cloud component displays the top ten Delivery Exceptions by frequency of occurrence. |
Items (tag cloud) | Top Ten Items Tag Cloud Component
Note: The Items tag cloud component displays the top ten items by frequency of occurrence. |
Fulfillment Progress (tabbed component container) | Demand (chart) Demand by Value by Customer, Released Status
Task Exceptions (chart) Task Count by Task Exception, Task Owner
Task Status (chart) Time in Hours by Task Status, Task Owner
Fulfillment Progress (results table) Note: The Fulfillment Progress results table component displays the data related to in progress lines and tasks.
|
Delivery Exceptions and Holds (tabbed component container) | Delivery Exceptions (chart) Exceptions by Value by Exception Name, Delivery Name
Holds (chart) Holds by Value by Customer, Delivery Name
Delivery Exceptions (results table) Note: The Delivery Exceptions results table component displays the data related to in-progress lines.
Holds (results table) Note: The Holds results table component displays the data related to in-progress lines.
|
Interface Activity (tabbed component container) | Interface Activity (Chart) Exceptions by Value by Customer, Delivery Name
Interface Activity (results table) Note: The Interface Activity results table component displays the data related to in-progress lines and tasks.
|
The Space Utilization page lets you track the fragmentation in the warehouse and suggest material movement to manage fragmentation. You can view inventory metrics, charts, and results tables. The following displays the Space Utilization page.
From the Warehouse Manager responsibility, navigate to the Space Utilization page:
(N) Inventory Management > Space Utilization
The following describes the Endeca Warehouse Management Space Utilization page regions and components:
Region | Components |
---|---|
Sub Tabs (page links) |
|
Filters | You can use Filters to refine the displayed data to only include records that have specified attribute values. |
Guided Navigation | You can use the Guided Navigation component to filter data using the following attributes:
|
Metric (metrics bar)
Note: The Metric Components are color coded to highlight warnings and health. |
|
Transaction Types (tag cloud) | Top Ten Transaction Types Tag Cloud Component
Note: The Transaction Types tag cloud component displays the top ten Transaction Types by frequency of occurrence. |
Subinventories (tag cloud) | Top Ten Subinventories Tag Cloud Component
Note: The Subinventories tag cloud component displays the top ten Subinventories by frequency of occurrence. |
Items (tabbed component container) | Item fragmentation (scaled) Count by Item, Locator (chart) Note: This chart displays item fragmentation without highlighting the quantity of each item in a locator. For example, each bar represents the item and each stack represents the locators in which this item exists.
Item fragmentation (non scaled) Count, Quantity by Item, Locator (chart) Note: This chart displays item fragmentation and highlights the quantity of each item in a locator. For example, each bar represents the item and each stack represents the quantity of this item in that locator.
Items (results table) Note: The Items results table component displays the data related to item fragmentation.
|
Locators (tabbed component container) | Locator fragmentation (scaled) Count by Locator, Item (chart) Note: This chart displays locator fragmentation without highlighting the quantity of each item in a locator, For Example, each bar represents a locator and each stack represents the items in the locator.
Locator fragmentation (non-scaled) Count, Quantity by Locator, Item (chart) Note: This chart displays locator fragmentation and highlights the quantity of each item in a locator. For example, each bar represents the locator and each stack represents the quantity of an item in that locator.
Locators (results table) Note: The Locators results table component displays the data related to locator fragmentation.
|
Velocity (Count) (tabbed component container) | Item Velocity (Top 1000) Count by Item, Locator (chart) Note: This chart displays item velocity by locator. The metric for the graph is 'transaction count (sum)'/'transaction quantity (sum).
Locator Velocity (Top 1000) Count by Locator, Row (chart) Note: This chart displays locator velocity. The metric for this graph is 'transaction count (sum)'.
Mismatch Distinct Items by Locator, item (chart) Note: This chart displays lot fragmentation and highlights the locators that hold items where item velocity does not match locator velocity.
Items (results table) Note: The Items results table component displays the data related to velocity fragmentation.
|
Velocity (Quantity) (tabbed component container) | Item Velocity (Top 1000) Quantity by Item, Locator (chart) Note: This charts displays item velocity by locator. The metric for the graphs is 'transaction count (sum)'/'transaction quantity (sum).
Locator Velocity (Top 1000) Count by Locator, Row (chart) Note: This chart displays locator velocity. The metric for this graph is 'transaction count (sum)'.
Mismatch Quantity by Locator, Item (chart) Note: This chart displays lot fragmentation and highlights the locators that hold items where item velocity does not match locator velocity.
Items (results table) Note: The Items results table component displays the data related to velocity fragmentation.
|
The Labor Utilization page lets you plan and manage labor in the warehouse. You can view labor metrics, charts, and results tables. The following is a display of the Labor Utilization page.
From the Warehouse Manager responsibility, navigate to the Labor Utilization page:
(N) Labor Management System > Labor Utilization
The following describes the Endeca Warehouse Management Labor Utilization page regions and components:
Region | Components |
---|---|
Range Filters | You can use Range Filters to refine the displayed data to only include records that have attribute values within a specified range. |
Guided Navigation | You can use the Guided Navigation component to filter data using the following attributes:
|
Metric (metrics bar)
Note: The Metric Components are color coded to highlight warnings and health. |
|
Users (tag cloud) | Top Ten Users Tag Cloud Component
Note: The Users tag cloud component displays the top ten Users by frequency of occurrence. |
Task Types (tag cloud) | Top Ten Task Types Tag Cloud Component
Note: The Task Types tag cloud component displays the top ten Task Types by frequency of occurrence. |
Labor by Task Source (chart)
Note: This chart displays labor utilization by different task sources. For example, outbound, inbound, warehousing, cross-dock, and manufacturing. | Total Time (in Hours) by Task Source, Task Owner (chart)
|
Labor by Task Status (chart)
Note: This chart shows labor utilization by in-process task status. For example, pending, queued, dispatched, active, and loaded. | Total Time (in Hours) by Task Status, Task Owner
|
Task Exceptions (chart)
Note: This chart displays labor utilization by different task-based exceptions. | Count by Task Exception, Task Owner
|
Labor Performance (chart)
Note: This displays labor performance as measured by the time spent on completed tasks. | Total Time (in Hours) by Task Owner, Task Source
|
Labor and Tasks (results table)
Note: The Labor and Tasks results table component displays the data related to warehouse labor and related tasks. | Labor and Tasks
|
The Oracle Warehouse Management application configuration and setup must be completed after the installation and common configurations are completed as described in Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1 V5 (Doc ID: 1683053.1).
To set up Oracle Warehouse Management Extensions for Oracle Endeca, you must complete the following steps:
Set Access Control by assigning UMX roles and updating access grants.
Load Warehouse Management data to the Endeca data store by running graphs provided by Warehouse Management.
Schedule Setup for Full Endeca Refresh.
New UMX Roles and a new grant 'WMS Endeca Access Grant' are provided. The 'WMS Endeca Access Grant' is assigned to the Access Roles. In addition, the 'WMS Endeca Access Permission Set' is assigned to the 'WMS Endeca Access Grant'.
As part of the Oracle E-Business Suite-EID integration for the Oracle Warehouse Management application, the following UMX Roles are provided:
UMX Role | Internal Code Name |
---|---|
WMS Plan Fulfillment Endeca Access Role | UMX|WMS_PF_ENDECA_ACCESS_ROLE |
WMS Track Fulfillment Endeca Access Role | UMX|WMS_TF_ENDECA_ACCESS_ROLE |
WMS Space Utilization Endeca Access Role | UMX|WMS_SU_ENDECA_ACCESS_ROLE |
WMS Labor Utilization Endeca Access Role | UMX|WMS_LU_ENDECA_ACCESS_ROLE |
Permission Set | Internal Code Name |
---|---|
WMS Plan Fulfillment Endeca Access Permission Set | WMS_PF_ENDECA_ACCESS_PS |
WMS Track Fulfillment Endeca Access Permission Set | WMS_TF_ENDECA_ACCESS_PS |
WMS Space Utilization Endeca Access Permission Set | WMS_SU_ENDECA_ACCESS_PS |
WMS Labor Utilization Endeca Access Permission Set | WMS_LU_ENDECA_ACCESS_PS |
You must add the new UMX roles to enable Endeca menus for the Warehouse Manager responsibility (or any other custom responsibility which is using the same menu). You must assign the UMX roles to this responsibility. When the UMX roles are assigned to the Warehouse Management responsibility, the Warehouse Management Endeca pages appear.
If you want to use the Endeca-related roles with more than one responsibility, then you must have an additional grant with a security context corresponding to each responsibility. You can add grants for a given role as a separate process instead of while you are adding the role to the responsibility.
Access Grant | Internal Code Name |
---|---|
WMS Plan Fulfillment Endeca Access Grant | WMS_PF_ENDECA_ACCESS_GRANT |
WMS Track Fulfillment Endeca Access Grant | WMS_TF_ENDECA_ACCESS_GRANT |
WMS Space Utilization Endeca Access Grant | WMS_SU_ENDECA_ACCESS_GRANT |
WMS Labor Utilization Endeca Access Grant | WMS_LU_ENDECA_ACCESS_GRANT |
Complete the following steps to enable Endeca Menus in Oracle E-Business Suite (EBS):
Assign a UMX Role to the Responsibility.
Update the WMS Access Grant.
For assigning UMX Roles and Grants, refer to Appendix C in Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1 V5 (Doc ID: 1683053.1).
Clover ETL within Endeca queries WMS Views and does a full data load to the WMS data store in Endeca. After the first data load, full data load or incremental data load can be performed periodically. Incremental data load will update all the records in the Endeca WMS data store which were updated in EBS after the last load. After the data has been loaded in the WMS data store, it can be queried and shown in the WMS pages.
Warehouse Management Data Sources in the WMS Data Store
Data sources are defined in the WMS data store in Endeca and are used to query data for different pages in WMS. These data sources include:
Restricting Data Loaded Into the Endeca Data Store Based on Organizations and Subinventories
The lookup 'Organization Control For WMS and INV Endeca Extensions' restricts data being loaded to the Endeca data store based on Organization in the Plan Fulfillment, Track Fulfillment, Space Utilization, and Labor Utilization pages. The lookup is seeded with 'ALL' as the default lookup code to load data for all Inventory Organizations. If there is a requirement not to load data for all Inventory Organizations, then disable the default lookup code 'ALL and add the lookup code value 'Organization Code'.
The lookup 'Subinventory Control For WMS and INV Endeca Extensions' restricts data being loaded to the Endeca data store based on Subinventories in the Space Utilization page. The lookup is seeded with 'ALL' as the default lookup code to load data for all Subinventories. If there is a requirement not to load data for all Subinventories, then disable the default lookup code 'ALL' and add the lookup code value 'Organization Code' or 'Subinventory Code'.
The initial data upload for Endeca Search is complete when the Full graph is run as described in Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1 V5 (Doc ID: 1683053.1). Full refresh deletes all data from Endeca and repopulates it with a full data extract from the E-Business Suite system. For incremental refresh, you should determine how often the Endeca data should be refreshed from E-Business Suite depending on your organizational requirements.
To schedule ETL on the Integrator Server
Login to Integrator server using your Clover login.
Click the Scheduling tab.
Select the New Schedule link.
Enter a Description for the scheduler.
Select Periodic as the Type.
Select by interval as the Periodicity.
Enter a start date and time in the Not active before date/time field.
Enter an end date and time in the Not active after date/time field.
Enter a value in the Interval (minutes) field.
Ensure you select the Fire misfired event as soon as possible check box.
Select Start a graph from the Task Type list.
Select the graph for schedule to run. I.e. Full.grf/incremental.grf.
Click Create to set the scheduler.
You can load data to the Warehouse Management (WMS) data store by running graphs provided by WMS. There are four data domains for WMS:
inv-pf - Plan Fulfillment page data domain from underlying 'wms-pf' data source
inv-tf - Track Fulfillment page data domain from underlying 'wms-tf' data source
inv-su - Space Utilization page data domain from underlying 'wms-su' data source
nv-lu - Labor Utilization page data domain from underlying 'wms-lu' data source
There are four ETL sandboxes shared between Inventory and WMS. Each file contains Full load and Incremental graphs specific to the data domains 'FullLoadConfig.grf' (Full Load) and 'IncrLoadConfig.grf' (Incremental Load). ETL Sandboxes include:
invpfetl.zip
invtfetl.zip
invsuetl.zip
invluetl.zip
To load data to the WMS data store
Using the URL for the EID Integrator Server, navigate to the Sandboxes page and expand the graph node under WMS.
Graphs to load data include:
FullLoadConfig.grf: Run the FullLoadConfig graph to perform a full data load.
Note: If you are loading data for the first time, then run FullLoadConfig.grf only. You can run other graphs according to your requirements. Run incremental graphs periodically. You can set up this graph from the Scheduling tab.
FullLoadConfig.grf contains the following parameters:
MAX_AGE_OF_ORDERS_PF: Number of Days Old, based on Order Creation Date (For Example: If the Plan Fulfillment page should show only Sales Orders created in the last 90 days, then you should specify MAX_AGE_OF_ORDERS_PF = 90).
MAX_AGE_OF_ORDERS_TF: Number of Days Old, based on Order Creation Date.
MAX_AGE_OF_ONHAND: Number of Days Old, based on On-hand Creation Date.
MAX_AGE_OF_INV_TRANSACTIONS: Number of Days Old, based on Transaction Creation Date.
MAX_AGE_OF_TASKS: Number of Days Old, based on Task Creation Date.
Note: The above parameters must be modified one time in the workspace.prm file under the following sanboxes on the ETL Server:
inv-pf - MAX_AGE_OF_ORDERS_PF
inv-tf - MAX_AGE_OF_ORDERS_TF
inv-su - MAX_AGE_OF_ONHAND and MAX_AGE_OF_INV_TRANSACTIONS
inv-lu - MAX_AGE_OF_TASKS
IncrLoadConfigTF.grf: Run the IncrLoadConfigTF incremental graph to load the incremental Track Fulfillment data.
IncrLoadConfigPF.grf: Run the IncrLoadConfigPF incremental graph to load the incremental Plan Fulfillment data.
IncrLoadConfigSU.grf: Run the IncrLoadConfigSU incremental graph to load the incremental Space Utilization data.
IncrLoadConfigLU.grf: Run the IncrLoadConfigLU incremental graph to load the incremental Labor Utilization data.
Note: If you are loading data for the first time, then run FullLoadConfig.grf only. You can run other graphs according to your requirements. Run Incremental. graphs periodically. You can set up these graphs from the Scheduling tab.
You must set the following profile option:
Profile Option Name | Description |
---|---|
INV: Endeca Display Currency | This profile value determines the currency in which all amounts and values are displayed in the Plan Fulfillment and Track Fulfillment pages. This is a site level profile option. |
The following views are used by the ETL layer in Endeca to load WMS data to the Endeca data store:
View Name | Purpose |
---|---|
INV_EID_UNPICKED_DETAILS_V | Data loaded from this view into “inv-pf” Endeca data store is displayed in the Plan Fulfillment page. |
INV_EID_RESERVATIONS_V | Data loaded from this view into “inv-pf” Endeca data store is displayed the Plan Fulfillment page. |
INV_EID_PICKED_DETAILS_V | Data loaded from this view into “inv-tf” Endeca data store is displayed in the Track Fulfillment page. |
INV_EID_ONHAND_DETAILS_V | Data loaded from this view into “inv-su” Endeca data store is displayed in the Space Utilization page. |
INV_EID_MTL_TRANSACTIONS_V | Data loaded from this view into “inv-su” Endeca data store is displayed in the Space Utilization page. |
INV_EID_TASKS_V | Data loaded from this view into “inv-lu” Endeca data store is displayed in the Labor Utilization page. |
Endeca Warehouse Management integration includes the following user menu functions:
User Function Name | Function Name |
---|---|
WMS Endeca Plan Fulfillment | WMS_PLAN_FULFILLMENT |
WMS Endeca Track Fulfillment | WMS_TRACK_FULFILLMENT |
WMS Endeca Space Utilization | WMS_SPACE_UTILIZATION |
WMS Endeca Labor Utilization | WMS_LABOR_UTILIZATION |
Copyright © 2012, 2014, Oracle and/or its affiliates. All rights reserved.