Oracle Order Management Command Center Setup
This chapter covers the following topics:
- Setting Up Order Management Command Center
- Setup and Configuration Steps for Order Management Command Center
- Profile Options for Order Management Command Center
- Defining Rules for Assigning Customer Service Representatives to Orders
- Using an API User Hook to Assign CSRs to Orders
- Running the Assign Customer Service Rep Program
- Configuring Descriptive Flexfields for Search
- Loading Order Management Data
- Loading Data for Credit Check Analyzer
- Loading Data for 360 View
- Loading Returns Data
Order Management Command Center Configuration
Setting Up Order Management Command Center
See Order Management Command Center Overview, Oracle Order Management User's Guide.
The Order Management Command Center configuration setup must be completed after the installation and common configurations are completed as described in My Oracle Support Knowledge Document 2495053.1, Installing Oracle Enterprise Command Center Framework, Release 12.2.
Important: If you plan to use the 360 View Dashboard, Oracle Order Management User's Guide of the Order Management Command Center, then you must add the Order Management ECC 360 View Role (UMX|ONT_ECC_360VIEW_ROLE) to the designated command center responsibility, which is typically Order Management, HTML User Interface.
See Setup and Configuration Steps for Order Management Command Center.
Setup and Configuration Steps for Order Management Command Center
See Order Management Command Center Overview, Oracle Order Management User's Guide.
To set up Order Management Command Center:
-
Define rules for assigning customer service representatives to orders.
-
Prerequisite Step: You can sequentially load data for each operating unit using the Operating Unit parameter of the OM Command Center Data Load. Before you run the sequential load, ensure that the FND: ECC Sequential Data Load Per Data Set Language profile option does not contain the OM data sets ont-headers (Orders), ont-lines (Order Lines), or the keyword ALL. This is to avoid loading data sequentially by both operating unit and language, which is not recommended.
-
Load data for Credit Check Analyzer.
Prerequisite Step: To view credit check hold analysis data, the Credit Checking feature must be set up. For more information, see My Oracle Support Knowledge Document 744642.1, Credit Checking Setup in Order Management.
-
Load data to view the supply status of sales orders on the 360 View dashboard.
-
Prerequisite Step: You must set the mandatory profile option OM: ECC Currency for Returns before loading the returns data.
-
To facilitate managing backorders by transferring demand on the Transfer Demand and Search Reservations pages of Oracle Inventory, ensure that users of Orders Dashboard can access the relevant inventory organizations. See Managing Backorders, Oracle Order Management User's Guide and Defining Organization Access, Oracle Inventory User's Guide.
Profile Options for Order Management Command Center
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
The profile category ECC Profiles available in Oracle Order Management stores the following profile options:
| Profile Option Name | Description |
|---|---|
| OM: ECC Bulk Load Size | This site-level profile determines the number of records that the data load programs (OM Command Center Data Load and OM Command Center Returns Data) process in memory at one time. A higher value will yield better performance if your system memory is abundant. |
| OM: ECC Display Currency | This optional site-level profile option controls the conversion of the transaction amounts for all orders into the specified currency. The Orders Dashboard also displays this information as the Currency tip text. If you specify a currency in this optional profile option, then the application converts (if required) the transaction amount for all orders into the specified currency. If a currency is not specified in this profile option, then the application converts (if required) the transaction amounts for all orders into the functional currency of the legal entity.
Note: You can specify a currency in this profile option if you have access to orders created in legal entities with different functional currencies. Once you select a currency, the application converts order amounts to the selected currency at the exchange rate available in Oracle General Ledger tables on the ordered date. If you have access to more than one operating unit, and each operating unit has its own functional currency, then you can set this profile option to the appropriate common currency according to your business requirements. If a currency is not specified in the profile option and there are multiple currencies available, then the tip text displays Currency: Multiple. |
| OM: ECC Currency for Returns | This mandatory site-level profile option controls the conversion of the transaction amounts for the Return % dimension (on the Returns dashboard) into the specified currency. To accurately calculate the Return %, you must set this profile option. Otherwise, the OM Command Center Returns Data Load program ends in error. |
| OM: ECC Days for Full Data Load | This site-level profile option specifies the age of closed orders selected by the Full Load. The application loads all orders closed more recently than the specified number of days. If you do not provide a value, the application uses 90 days. |
| OM: ECC Enable Push Updates OM: ECC Push Time Limit |
These profile options control the push of updated data from Oracle Order Management to the ECC data store to display real-time data on the Orders Dashboard. Push updates occur whenever customer service representatives (CSRs) initiate changes to orders from the dashboard. For information about actions that CSRs can perform from the dashboard, see Orders Dashboard, Oracle Order Management User's Guide. Define these profile options in the following sequence. You can set the profile options at site, application, responsibility, and user levels.
Note: If push updates are pending completion or fail within the time specified in the OM: ECC Push Time Limit profile option, then these windows and pages display a warning message. For information about pages and windows from where push updates occur, see Push Updates from Oracle Order Management to the ECC Data Store. |
| OM: ECC Months of Returns to Load | This optional site-level profile option determines the age of return lines that the OM Command Center Returns Data Load program considers to load the returns data. If the profile value is not set, then the default value of 12 is considered. For example, the profile value is set to 12 and you run the program on 25-November-2021. To load data, the program considers the closed return lines that are not canceled with the last update date (returned date) between 01-November-2020 and 31-October-2021 (current month minus 1). |
| OM: ECC Prefilter by CSR | This profile option determines whether the (CSR) filter is applied by default on the Orders Dashboard.
This profile can be set at the site, application, responsibility, and user levels. |
| OM: ECC Rolling Sales Period | This optional site-level profile option specifies the number of continuous months for the calculation of the average monthly sales in a month. If the profile value is not set, then the default value of 1 is considered. For example, if the profile value is set to 3, then the average monthly sales for the completed month of October 2021 is calculated as: Sales for the months of (August + September + October) divided by 3. |
| OM: Debug Level | This profile option controls which debug messages get written to the debug log based on their assigned level. You can set this profile option at any level during the command center implementation. See Profile Options. Set this profile only when debugging of any issue is required. The following values are applicable to the command center:
When you run the OM: Command Center Data Load concurrent program using the Full Load and Incremental Load options, the program triggers two child requests of the OM: Command Center Data Load program, one for the Order Lines data set and one for the Orders data set. For full and incremental loads, if the profile value is greater than zero, then the debug messages logged by the parent program are written to that program's log and the debug messages logged by the child concurrent programs will be logged to the file in the directory mentioned in the OM: Debug Log Directory profile option. The debug file names are of the format OM_ECC_<parent request_id>_<dataset>.dbg.Examples of file names:
|
| FND: ECC Disable Descriptive Flexfield
Note: This an Application Object Library profile option. |
This profile option enables you to exclude descriptive flexfields from the data load in ECC. If you do not want to load data of DFFs, then set the profile option value to internal names of the descriptive flexfields (DFFs). To exclude the data load of Oracle Order Management DFFs, set the following values. Specify multiple values using a comma-separated list.
Important: If you add or remove OE_HEADER_ATTRIBUTES or OE_LINE_ATTRIBUTES, or both values from the profile option, then you must run the OM Command Center Data Load program with the Load Type parameter set to Full Load. |
| WSH: Days for Full Data Load of Shipped Details
Note: This is an Oracle Shipping Execution profile option. |
This site-level profile option specifies the age of the shipped delivery details selected by the Full Load option of the Delivery Details Data Load program. The application loads all delivery details that were closed (shipped) no earlier than the specified number of days ago. If you do not provide a value, then the application uses zero (0) days, that is, the application loads the details shipped on the day of the load. Open delivery details are always loaded.
Important: To load the delivery details associated with the shipped sales order lines on the 360 View dashboard, the value of the WSH: Days for Full Data Load of Shipped Details profile must be greater than the value of the OM: ECC Days for Full Data Load profile. |
| WIP: Single Organization ECC Dashboard
Note: This is an Oracle Discrete Manufacturing profile option. |
This profile option sets access to single or multiple organizations. The default value is Yes. If the profile is set to Yes, then the Work Order nodes will not be displayed on the 360 View dashboard network viewer.
Important: Set the profile value to No for the Order Management responsibility that is used to access the 360 View dashboard. See 360 View Dashboard, Oracle Order Management User's Guide. |
Push Updates from Oracle Order Management to the ECC Data Store
If the OM: ECC Enable Push Updates and OM: ECC Push Time Limit profile options are set, then push updates occur from Oracle Order Management to the ECC data store.
The following table lists the pages and windows where push updates occur and the actions that initiate push updates.
| Page or Window | Actions that Initiate Push Update |
|---|---|
| Order page |
|
| Line Details page |
|
| Orders page |
|
| Order Lines page |
|
| Sales Orders window |
|
| Order Organizer window |
|
Defining Rules for Assigning Customer Service Representatives to Orders
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
You can use the following methods to define rules for assigning customer service representatives (CSR):
-
Use the Customer Service Rep Assignment page to define rules, which are based on customer and item category. See Using the Customer Service Rep Assignment Page.
-
Use the API user hook OE_CSR_HOOK.CUSTOM_CSR_ID to derive the customer service representatives to be assigned to sales orders. The logic by which a CSR is assigned is to be coded in this hook by implementers. See Using an API User Hook to Assign CSRs to Orders.
Using the Customer Service Rep Assignment Page
Use the Customer Service Rep Assignment page to define CSR assignment rules. The application uses these rules to assign the CSR to an order when the first sales order line is created for the order.
These assignment rules apply to orders created through:
-
The Sales Orders window
-
The Quick Sales Orders window
-
The Order Management HTML User Interface
-
The Process Order API
-
Order Import
Access the Customer Service Rep Assignment page using the standard Order Management responsibility.
(N) Order Management > Setup > Rules > Customer Service Rep Assignment
Customer Service Rep Assignment Page
To define assignment rules
-
Navigate to the Customer Service Rep Assignment page.
-
Select a customer, an item category, and a customer service representative. You can define only one rule for each combination of customer and item category.
How CSR Assignment Rules Work:
When the first line of an order is created, if the customer and item category combination in that line is associated (by a CSR assignment rule) with a particular CSR, then that CSR is assigned. If no rule exists for the customer and item category combination, then the CSR associated with the customer is assigned.
The following CSR assignment rules are used in the examples below.
Rule Customer Item Category Customer Service Rep 1 Company 1 Finished Goods Rep, Mr One 2 Company 1 this field is blank Rep, Ms Two -
If the first line of an order for finished goods is created for Company 1 and Item AS54888 (item category is finished goods), then Mr. One Rep is assigned as the CSR. In this case, the rule with the customer and item category combination exists.
-
If the first line of an order is created for Company 1 and item OM-ATO-Model (item category is not finished goods), then Rep Ms. Two is assigned as the CSR. In this case, the CSR associated with the customer is assigned as no rule exists for the customer and item category combination.
To change the CSR for an order
Sales Order View Page
To add, change, or remove the CSR assigned to a sales order, use the Order Management HTML User Interface page.
Note: The Customer Service Rep field is not shown by default. You must personalize the page to render it.
Updating assignment rules:
After CSRs are assigned to orders, certain business scenarios may require you to change the assignment rules. For example, if the CSR assigned to an order is no longer with your organization, then you need to identify a new CSR for that order. To address such business requirements, you can update existing assignment rules.
To update assignment rules:
-
Navigate to the Customer Service Rep Assignment page.
-
Search for the rule that you want to update.
-
Update the CSR rules as required.
-
What Next:
After updating assignment rules, run these concurrent programs in the following order.
-
Assign Customer Service Rep: This program reassigns CSRs to open sales orders based on the latest assignment rules. See Running the Assign Customer Service Rep Program.
-
OM Command Center Data Load: This program loads CSRs assigned to sales orders into the ECC data store along with other sales order data. See Loading Order Management Data.
Using an API User Hook to Assign CSRs to Orders
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
The API user hook OE_CSR_HOOK.CUSTOM_CSR_ID enables you to write custom logic using customer (sold_to_org_id) and item ID, order, and line attributes to derive a valid customer service representative (CSR). The application uses the custom hook rules to assign the CSR to an order when the first sales order line is created for the order.
Details for the API user hook:
-
Filename: OEXHCSRB.pls
-
Package: OE_CSR_HOOK
-
Function: CUSTOM_CSR_ID
To return a valid CSR user ID (FND user ID), you can write logic based on the IN parameters in the following table or write logic that queries columns from the IN parameters. For example, to write rules based on header details, use the p_header_id IN parameter to query columns from the OE_ORDER_HEADERS_ALL (OE_ORDER_HEADERS) table.
The following table describes the function parameters:
| Parameter Name | IN or RETURN | Description |
|---|---|---|
| p_sold_to_org_id | IN | Customer account ID |
| p_inventory_item_id | IN | Item ID in Oracle Inventory |
| p_header_id | IN | Header ID of the sales order |
| p_first_line_id | IN | ID of the first line of the sales order |
| l_csr_user_id | RETURN | ID of the customer that you want to assign to a sales order |
How the API User Hook Works
When the first line for an order is created, the application calls the OE_CSR_HOOK.CUSTOM_CSR_ID hook. This is how the application assigns a CSR:
-
If the custom hook returns a valid CSR ID (FND user ID), then the CSR is assigned to the order. For that customer and category, if rules are already defined using the Customer Service Rep Assignment page, then the application ignores those rules.
-
If the custom hook returns an invalid user ID or the ID is null, then the Customer Service Rep Assignment page rules are applied.
-
If you do not define assignment rules on the Customer Service Rep Assignment page or in the custom hook, then no CSR is assigned to the sales order.
-
The application also calls the OE_CSR_HOOK.CUSTOM_CSR_ID hook, when the Assign Customer Service Rep concurrent program is submitted.
Sample Script
The following section provides a sample script that you can use to customize the API user hook. For example, if you need to assign a CSR based on the ship-to location and the customer, then you can write conditions to return a valid CSR user ID.
CREATE OR REPLACE PACKAGE BODY oe_csr_hook AS
FUNCTION custom_csr_id (
p_sold_to_org_id IN NUMBER,
p_inventory_item_id IN NUMBER,
p_header_id IN NUMBER,
p_first_line_id IN NUMBER
) RETURN NUMBER IS
l_ship_to_org_id NUMBER;
l_csr_user_id NUMBER := NULL;
l_debug_level CONSTANT NUMBER := oe_debug_pub.g_debug_level;
BEGIN
IF l_debug_level > 0 THEN
oe_debug_pub.add('Entering OE_CSR_HOOK.CUSTOM_CSR_ID ');
END IF;
/*Sample code for getting ship_to_org_id from oe_order_headers using p_header_id */
SELECT
ship_to_org_id
INTO
l_ship_to_org_id
FROM
oe_order_headers
WHERE
header_id = p_header_id;
/* Sample Code for writing conditions using ship to org id, sold to org id */
IF
l_ship_to_org_id = 1425 AND p_sold_to_org_id = 1290
THEN
l_csr_user_id := 2816; -- Michaels,Mr. Douglas
ELSIF
l_ship_to_org_id = 1018 AND p_sold_to_org_id = 1004 THEN
select user_id
into l_csr_user_id
from fnd_user
where user_name = 'OPERATIONS';
END IF;
IF l_debug_level > 0 THEN
oe_debug_pub.add('Exiting OE_CSR_HOOK.CUSTOM_CSR_ID with l_csr_user_id '|| l_csr_user_id);
END IF;
RETURN l_csr_user_id;
EXCEPTION
WHEN OTHERS THEN
IF oe_msg_pub.Check_Msg_Level(oe_msg_pub.G_MSG_LVL_UNEXP_ERROR) THEN
oe_msg_pub.Add_Exc_Msg('OE_CSR_HOOK.CUSTOM_CSR_ID','CUSTOM_CSR_ID');
END IF;
END;
END oe_csr_hook;
/
COMMIT;
EXIT;
Running the Assign Customer Service Rep Program
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
Run the Assign Customer Service Rep program after you update CSR assignment rules in the Customer Service Rep Assignment page. You can use this program to bulk assign or reassign CSRs to multiple orders at a time for given parameters.
Note: This program will not assign CSRs to closed orders.
If you have implemented the API user hook OE_CSR_HOOK.CUSTOM_CSR_ID to derive CSRs, then the application calls this user hook when you submit the Assign Customer Service Rep program. See Using an API User Hook to Assign CSRs to Orders.
Access the program from the standard Order Management responsibility.
(N) Order Management > Reports, Requests > Run Requests
The Assign Customer Service Rep concurrent program is available to the responsibilities that are assigned the request group OM Concurrent Programs.
Run the program from the Submit Request window.
Assign Customer Service Rep Request
To run the Assign Customer Service Rep program:
-
In the Name field, select Assign Customer Service Rep.
-
In the Customer field, select the customer for whom you want to assign CSRs. This field is optional. If you select a customer, then the program assigns or reassigns CSRs to all open sales orders for that particular customer.
-
The Customer Service Rep field is optional. If you select a CSR and Override Existing Assignment is Yes, then the orders assigned to the given CSR are overridden as per the latest CSR assignment rules.
Note: If you leave the Customer and Customer Service Rep fields blank, then the program bulk assigns CSRs based on the latest assignment rules.
-
In the Override Existing Assignment field, select Yes to reassign a CSR as specified in the latest assignment rule. The default value is No. When the override value is No, the concurrent program assigns CSRs to open sales orders (that do not have any CSRs assigned). If you select No in this field after selecting a CSR, then the program will not process any records and ends in an error.
-
Submit the request.
What Next:
Run the OM Command Center Data Load concurrent program. See Loading Order Management Data. CSRs assigned to sales orders will be loaded into the ECC data store along with other sales order data. To access reassigned orders, CSRs can log in to the Orders Dashboard. To view reassigned CSRs for orders, administrators can use the Order Management HTML User Interface page.
Configuring Descriptive Flexfields for Search
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
Enterprise command centers support searching on descriptive flexfield (DFF) attributes. After you configure DFFs, you must run the data load process to make the DFF attributes available in the command center.
Note: To exclude descriptive flexfields from the data load, define the FND: ECC Disable Descriptive Flexfield profile option. See Profile Options for Order Management Command Center.
For additional information about configuring and customizing flexfields, see Oracle E-Business Suite Flexfields Guide and My Oracle Support Knowledge Document 2495053.1, Installing Oracle Enterprise Command Center Framework, Release 12.2.
The following table describes the DFFs that are available in the Orders Dashboard:
| Data Set | DFF Title | DFF Name | DFF Attribute Group Name | Displayed in |
|---|---|---|---|---|
| ont-headers | Additional Header Information | OE_HEADER_ATTRIBUTES | Additional Header Information | Orders results table |
| ont-lines | Additional Header Information | OE_HEADER_ATTRIBUTES | Additional Header Information | Available Refinements, Order Lines results table |
| ont-lines | Additional Line Attribute Information | OE_LINE_ATTRIBUTES | Additional Line Attribute Information | Available Refinements, Order Lines results table |
Loading Order Management Data
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
To process and load data for the Orders Dashboard from Oracle E-Business Suite to the Order Management Command Center, run the concurrent program OM Command Center Data Load, which is located under the standard Order Management responsibility > Reports, Requests > Run Requests.
Run this program from the Submit Request window.
OM Command Center Data Load
To run the OM Command Center Data Load
-
In the Name field, select OM Command Center Data Load.
-
Select the appropriate load type
-
Full Load: Loads all orders data and is required to be run for the first data load. The full data load process also includes metadata load. If you run a full load for subsequent requests, then this program clears all orders data from ECC and loads fresh data.
During a full load all of the open and closed orders (which are closed within the numbers of days specified in the profile option OM:ECC Days for Full Data Load) are considered for processing.
-
Incremental Load: Loads only the data that has been modified since the previous load. Schedule incremental loads to run as often as required to keep the ECC dashboard current. Note that the Reset Data parameter is not applicable to incremental load.
-
Metadata Load: Loads Descriptive Flexfield (DFF) metadata. If there are any changes to the DFF definition, then you must run the program first with the Metadata Load option and then the Full Load option so that the DFF changes are displayed in the command center. The Operating Unit and Reset Data parameters are not applicable to metadata load.
-
-
In the Language Codes field, enter one or more language codes for the output. For multiple language codes, use the format AA,BB,NN. If this field is blank, then the data will be loaded for the base language only (usually US).
-
Select the log level that you want the program to report. The default value is ERROR.
-
Select TRUE to enable SQL trace. Otherwise, select FALSE.
-
Select the operating unit for which you want to load data. You can sequentially load data for each operating unit using this parameter.
The following rules apply to the Operating Unit parameter:
-
If this field is blank, then during a full load, the program loads all of the open and closed orders, which are closed within the numbers of days specified in the OM: ECC Days for Full Data Load profile option.
-
If you select a value in this field and Reset Data is TRUE, then the program deletes the existing orders in the ECC data store and loads the orders of the selected operating unit.
-
If you select a value in this field and Reset Data is FALSE, then the program along with retaining the existing orders, loads the orders of the selected operating unit to the ECC data store.
-
-
Use the Reset Data parameter with caution. The default value is FALSE. If you run full load for the first time or want to reset the data, then set the parameter value to TRUE. If set to TRUE, this action wipes out all the data that was loaded earlier, and loads the new data for the selected operating unit. After the completion of full load, data of only one operating unit will be available in the ECC data store.
-
For subsequent full loads, to append the new data to the data set, set this value to FALSE.
-
For incremental loads, this parameter is not applicable.
-
-
Submit the concurrent request.
-
Review your request using the Requests page.
-
Monitor data loading using the Data Load Tracking page of the ECC Developer responsibility.
Loading Data for Credit Check Analyzer
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
To process and load credit check data for the "Credit Check Hold Analysis" page from Oracle E-Business Suite to the Order Management Command Center, run the concurrent program OM Command Center Credit Check Data Load, which is located under the standard Order Management responsibility > Reports, Requests > Run Requests.
This program extracts the data of sales orders and sales order lines on credit check failure hold and loads the corresponding credit limits, calculated exposure amounts, and credit check rule definitions along with the transaction details.
The OM Command Center Credit Check Data Load program loads data to the following data sets:
| Key | Display Name | Description |
|---|---|---|
| ont-cc-hold-details | Credit Check Hold Details | This data set contains data to display in the following results grids of the Credit Limit and Exposure tab:
|
| ont-cc-rules | Credit Check Rules | This data set contains data to display in the Credit Check Rule tab. |
| ont-cc-exposure | Credit Limits and Exposure | This data set contains data to display in the Credit Limit and Exposure (tab), Overall Credit Limit and Exposure results grid. |
| ont-cc-so-expdetails | Credit Exposure Details from Oracle Order Management | This data set contains data to display in the following results tables of the Exposure Details tabbed region:
|
| ont-cc-ar-expdetails | Credit Exposure Details from Oracle Receivables | This data set contains data to display in the following results tables of the Exposure Details tabbed region:
|
Prerequisite: Before you run the OM Command Center Credit Check Data Load program, ensure that the "Initialize Credit Summaries Table" program is run, which calculates the exposure amounts, based upon the exposure setup for each credit check rule defined and stores them in a summary table.
Recommendation: Run the concurrent program OM Command Center Credit Check Data Load after every successful run of "Initialize Credit Summaries Table" to view the up-to-date credit exposures on the Credit Check Hold Analysis page.
OM Command Center Credit Check Data Load
Run this program from the Submit Request window.
To run the OM Command Center Credit Check Data Load
-
In the Name field, select OM Command Center Credit Check Data Load.
-
Select the appropriate load type.
-
Full Load: Loads all credit check data and is required to be run for the first data load. If you run a full load for subsequent requests, then this program clears all credit check data from ECC and loads fresh data.
-
Incremental Load: Loads only the data that has been modified since the previous load. Schedule incremental loads to run as often as required to keep the ECC dashboard current.
-
-
In the Language Codes field, enter one or more language codes for the output. For multiple language codes, use the format AA,BB,NN. If this field is blank, then the data will be loaded for the base language only (usually US).
-
Select TRUE to enable SQL trace. Otherwise, select FALSE.
-
Select the log level that you want the program to report. The default value is ERROR.
-
Submit the concurrent request.
-
Review your request using the Requests page.
-
Monitor data loading using the Data Load Tracking page of the ECC Developer responsibility.
Loading Data for 360 View
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
The network diagram on the 360 View Dashboard, Oracle Order Management User's Guide displays the following network nodes:
-
Order
-
Order Line
-
Reservation
-
Delivery Detail
-
Delivery
-
Requisition
-
Internal Requisition
-
Drop-Ship Requisition
-
Purchase Order
-
Work Order
-
Payment History
-
Receivables
To display the corresponding product nodes on the 360 View dashboard, you must run the data load concurrent programs listed in the following table.
| Data Set Name (Data Set Key) | Data Load Concurrent Program |
|---|---|
| Reservations (inv-reservations) | Inventory Reservations Data Load See Loading Inventory Management Data - Inventory Reservations, Oracle Inventory User's Guide |
| Shipping Delivery Detail (delivery_details) | Delivery Details Data Load See Load Inventory Management data - Delivery Details, Oracle Inventory User's Guide |
| Work Orders (wip-wodetails) | WIP ECC Data Load See Loading WIP ECC Data, Oracle Work in Process User's Guide |
| Purchase Orders (po-pcc-orders) Requisitions (po-pcc-requisitions) |
PO PCC ECC Data Load See Loading Procurement Data, Oracle Purchasing User's Guide |
| Outstanding Receivables (ar-trx) Payment History (ar-history) |
Receivables Command Center Data Load See Loading Receivables Command Center Data, Oracle Receivables Implementation Guide |
Loading Returns Data
See Order Management Command Center Overview, Oracle Order Management User's Guide and Setup and Configuration Steps for Order Management Command Center.
Prerequisite Step: You must set the mandatory profile option OM: ECC Currency for Returns before loading the returns data.
To process and load data of return lines from Oracle E-Business Suite to the Order Management Command Center, run the OM Command Center Returns Data Load concurrent program, which is located under the standard Order Management responsibility > Reports, Requests > Run Requests.
This program:
-
Loads only the closed return lines that are not canceled. Open lines are not loaded.
-
Calculates the outbound sales for the Returns % dimension. See Returns Dashboard, Oracle Order Management User's Guide.
Run this program from the Submit Request window.
OM Command Center Returns Data Load
To run the OM Command Center Returns Data Load
-
In the Name field, select OM Command Center Returns Data Load.
-
In the Month Returned field, select the month for which you want to load the return lines data. If you do not select a month, then the program loads the return lines data for all the listed months. Note that the OM: ECC Months of Returns to Load profile option value determines the list of values in this field.
-
In the Language Codes field, enter one or more language codes for the output. For multiple language codes, use the format AA,BB,NN. If this field is blank, then the data will be loaded for the base language only (usually US).
-
Select the log level that you want the program to report. The default value is ERROR.
-
Select TRUE to enable SQL trace. Otherwise, select FALSE.
-
Submit the concurrent request.
-
Review your request using the Requests page.
-
Monitor data loading using the Data Load Tracking page of the ECC Developer responsibility.