Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Checklist for Configuring Siebel Customer-Centric Enterprise Warehouse Applications >

Checklist for Configuring the Siebel Enterprise Sales Analytics

This section contains the mandatory and optional configuration points for the Siebel Enterprise Sales Analytics application for SAP R/3, Oracle 11i, and post-load processing.

Checklist for Configuring the Siebel Enterprise Sales Analytics for SAP R/3

This section contains optional Siebel Enterprise Sales Analytics application configuration points that are specific to SAP R/3:

• Configuring the Booking Flag Calculation in the Sales Order Lines Table. To configure the booking flag calculation in the Sales Order Lines table, see Configuring the Booking Flag Calculation in the Sales Order Lines Table.
• Tracking multiple attribute changes in Booking Lines. If you want to track changes based on more than one attribute, in the SQL statement you must concatenate the attribute column IDs in the VAR_BOOKING_ID column. For more information on tracking multiple attribute changes in Booking Lines, see Tracking Multiple Attribute Changes in Bookings.
• Configuring the Booking Flag calculation in the Sales Schedule Lines Level. To configure bookings at the Sales Schedule Lines level, see Configuring the Booking Flag Calculation in the Sales Schedule Lines Level.
• 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 configuring 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 the Sales Invoice Extract.
• Configuring Order Types for Backlog calculations. To edit the Backlog flag, see Configuring Order Types for Backlog Calculations.
• Setting the negative sign for the Order and Invoice Lines. By default, the Siebel Customer-Centric Enterprise Warehouse does not use negative values in the quantity or amount columns for the IA_SALES_IVCLNS table or the IA_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 Siebel Enterprise Sales Analytics for SAP R/3, see Domain Values and CSV Worksheet Files for Siebel Enterprise Sales Analytics.

Checklist for Configuring the Siebel Enterprise Sales Analytics for Oracle 11i

This section contains optional Siebel Enterprise Sales Analytics application configuration points 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 (IA_SALES_BKGLNS). 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.
• Tracking changes to dimensional attributes in Booking Lines. If you want additional lines to be created to track changes to other dimensional attributes, you would need further configurations. For more information on how to track dimensional attribute changes in bookings, see Tracking Multiple Attribute Changes in Bookings.
• Tracking hold information. This step must be done in case you want to track holds. The configuration procedure requires that you map your source values to the set of domain values to translate the values. The Siebel Customer-Centric Enterprise Warehouse supports storage of up to nine different types of hold. For more information on assigning Sales Order hold types, see Configuring Sales Schedule Lines Data Storage.
• 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 Configuring Order Types for Backlog Calculations.
• Setting the negative sign for the Order and Invoice Lines. By default, the Siebel Customer-Centric Enterprise Warehouse does not use negative values in the quantity or amount columns for the IA_SALES_IVCLNS table or the IA_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 Siebel Enterprise Sales Analytics for Oracle 11i, see Domain Values and CSV Worksheet Files for Siebel Enterprise Sales Analytics.

Checklist for Configuring the Siebel Enterprise Sales Analytics for post-load processing

This section contains optional Siebel Enterprise Sales Analytics configuration points that are specific to post-load processing.

• Aggregating Siebel Enterprise Sales Analytics tables. To aggregate the Sales Invoice Lines and Sales Order Lines tables, see Process of Aggregating Siebel Enterprise Sales Analytics Tables.
• Tracking multiple products sold as one package. This configuration allows the user to set up the Order Line Key ID to reference all products sold in a bundle. For more information on tracking multiple products sold as one package, see About Tracking Multiple Products for Siebel Enterprise Sales Analytics.
• Adding dates to the Order Cycle Time table. To add more dates, you need to understand how the Order Cycle Times table is populated. For more information on adding dates to the Cycle Time table load, see Adding Dates to the Order Cycle Time Table for Post-Load Processing.