Oracle® Business Intelligence Applications Installation and Configuration Guide > Configuring Metadata for Analytics Applications > Analytics Metadata Requirements for Oracle's Siebel Industry Applications >

Oracle's Siebel Consumer Sector Data Requirements


The data requirements for the Consumer Sector-specific portion of the data model are detailed in Table 120. This includes the fund, promotion, performance and retail audit schema.

.
Table 120. Data Requirements for Consumer Sector Schema
Page
Function

Funds

Trade Fund Management Analytics incorporates the latest Trade fund functionality including aggregation of approved adjustments, transfers, deal allocations, and payments at all statuses.

Promotion

In the transactional database, fund allocations and product movement (incremental volumes) can be assigned to a promotion at the promotion or the promoted product level. The ETL transfers this information at the promoted product level only. If you allocate funds at the promotion level and assign product detail such as shipment quantities at the promoted product level, the fund allocation data needs to be pushed to the promoted product level to be accurately stored in the Oracle Business Analytics Warehouse.

Performance

Sales Performance Analytics is used primarily in conjunction with the category product hierarchy as defined by Oracle's Siebel Sales Volume Planning. To create the category-product hierarchy, the SVP adopt flag must be selected in order to aggregate product data up the category product hierarchy. This flag can be found by navigating to Catalog Administration > SVP Category Details View > Products list.

The data warehouse and all prebuilt analyses are built from the end date of a period. To make sure data is accurate, the periods in the transactional database tables must be of a single duration. If they are different, inaccurate data could be stored in the data warehouse. For example, if a week and a month end on the same date, the actual shipped quantities are combined during the building of the data warehouse.

Retail Audit

The Last Audit Flag is set during the ETL process. The flag is set to Yes for the most recent record for a product at an account and merchandising location. All other audit records for that combination of product, account, and merchandising location are set to No.

The observation date is used to sort the retail audit records to determine which is the last audit. The observation date is populated when the status of a retail audit activity is changed to Done. The field observation date does not show up in the transactional database user interface and does not have to be the same as the activity date.

Oracle® Business Intelligence Applications Installation and Configuration Guide Copyright © 2007, Oracle. All rights reserved.