|
Oracle® Business Intelligence Applications Installation and Configuration Guide > Checklist for Configuring Oracle Business Analytics Warehouse Applications >
Checklist for Configuring Oracle BI Applications Consumer
This section contains optional configuration points for the Oracle BI Applications Consumer application for Oracle 11i. Checklist for Configuring Oracle BI Applications Consumer for Oracle 11i
This section contains optional configuration points for Oracle BI Applications Consumer that are specific to Oracle 11i: - Including nonbooked lines in the Sales Booking Line fact table. By default, only booked lines are brought over to the Sales Booking Line fact table. You can change this to include Nonbooked Lines. For more information on configuring the handling of Booked and Nonbooked Orders in the Order Lines and Bookings Table, see Configuring Sales Order Lines Data Storage.
- Tracking changes in Booking Lines. By default, only the changes in Order Amount, Quantity, Line ID, and Warehouse are tracked in the Booking Lines table (W_SALES_BOOKING_LINE_F). If you want to track other changes you can do so. For example, you may want to track changes to the sales representative who is handling the order. For more information on viewing the Data Warehouse changes by Salesperson ID, see About Tracking Attribute Changes in Bookings.
- Loading bookings at the Schedule Line Level instead of the Sales Order Line level. You can configure the load process to load bookings at the Sales Schedule Line level instead of the Sales Order Line level. For more information on loading bookings at the Schedule Line level, see Configuring Sales Schedule Lines Data Storage.
- Setting up early and late tolerances for shipping. To define early or late shipments with reference to the scheduled pick date, you need further configurations. For more information on defining early and late tolerances for shipments, see Configuring Early and Late Tolerances for Shipments.
- Including incomplete Sales Invoices. By default, the Siebel Enterprise Sales Analytics application is configured to extract completed sales invoices when performing the Sales Invoice data extract. To extract incomplete sales invoices you would need further configurations. For more information on configuring Sales Invoice Lines data storage, see Configuring Sales Invoice Lines Data Storage.
- Including closed orders for backlog calculations. Be default, only orders with status Open are included in the backlog calculations. To include the closed orders, you would need further configurations. For more information on adding closed orders to backlog calculations, see Configuring Different Types of Backlog Calculations.
- Configuring order types for backlog calculations. By default, all order types are included in the backlog calculations. To exclude certain order types you would need further configurations. For more information on configuring order types for backlog calculations, see Configuring Different Types of Backlog Calculations.
- Configuring the backlog history period date. This configuration allows you to change the default monthly backlog snapshot to a different grain—for example weekly, daily, and so on. For more information on configuring the backlog period date, see Accounting for Negative Values in Orders, Invoices, and Picks.
- Setting the negative sign for the Order and Invoice Lines. By default, the Oracle Business Analytics Warehouse does not use negative values in the quantity or amount columns for the
W_SALES_IVCLNS table or the W_SALES_ORDLNS table. You can configure mapplets to account for negative values. For more information on accounting for negative values for Orders, Invoices, and Picks, see Accounting for Negative Values in Orders, Invoices, and Picks.
- Domain Values. For a list of CSV worksheet files and domain values for Oracle BI Applications Consumer for Oracle 11i, see Domain Values and CSV Worksheet Files for Oracle Order Management and Fulfillment Analytics Option.
- Processing Deletes. If you want to track deletes in a Sales Fact table, create a new subject area and add to that the table(s) using the out of the box sales subject areas as reference. Go to Configuration Tags in the DAC and find "Enterprise Sales Identify and Soft Delete Tasks". Add the subject area that you created. Make sure that the "Inactive Flag" is not checked. Design the subject area and include that in your custom execution plan.
- Post load processing. Oracle EBS has interface programs that update the Order tables with picking/shipping and invoicing information. The out of the box ETL relies on these interface programs to source related data. If you do not run these interface programs in Oracle EBS, you can use the packaged post load ETL steps to update that information from the data available in the various warehouse tables. Create a new subject area and add to that the table(s) using the out of the box sales subject areas as reference. Go to Configuration Tags in the DAC and find "Enterprise Sales PLP Tasks". Add the subject areas that you created. Make sure that the "Inactive Flag" is not checked. Design the subject areas and include them in your custom execution plan.
Checklist for Configuring the Siebel Enterprise Sales Analytics for Post-Load Processing
This section contains optional configuration points for Oracle BI Applications Consumer that are specific to post-load processing.
|
