Best Practices - for Business Intelligence.doc

SAP BW 3.5

April 2005

English

Best Practices for Business Intelligence

SAP AGNeurottstr. 1669190 WalldorfGermany

Solution Scope

SAP Best Practices Best Practices for Business Intelligence: Solution Scope

Copyright

© Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 17


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Best Practices for Business Intelligence: Solution Scope.............................................................5

1.1 Purpose.............................................................................................................................. 5

2 Functional Scope – Supported Business Processes or Scenarios...............................................5

2.1 Scenario Financial Accounting Analysis.............................................................................5

2.2 Scenario Controlling Analysis.............................................................................................5

2.3 Scenario CO-PA Baseline Analysis....................................................................................7

2.4 Scenario Cost Center Planning..........................................................................................7

2.5 Scenario Sales Analysis.....................................................................................................7

2.6 Scenario Cross-Functional Analysis: Financial and Sales Data.........................................8

2.7 Scenario Booking Billing Backlog Analysis.........................................................................9

2.8 Scenario Work Force Management (WFM)........................................................................9

2.9 Scenario CRM Analytics.....................................................................................................9

2.10 Scenario Sales Planning..................................................................................................10

2.11 Scenario Scheduling Agreements Analysis......................................................................10

2.12 Scenario Purchasing Analysis..........................................................................................10

2.13 Scenario Manufacturing Analysis.....................................................................................11

2.14 Scenario Inventory Analysis.............................................................................................12

2.15 Scenario Demand Planning Analysis...............................................................................12

2.16 Scenario Resource and Operation Data Analysis............................................................13

2.17 Scenario Project System – Controlling and Dates............................................................13

2.18 Scenario cProjects...........................................................................................................13

2.19 Scenario Cross-Application Time Sheet...........................................................................14

2.20 Scenario Time Management – Time and Labor...............................................................15

2.21 Scenario Personnel Development – Qualifications...........................................................15

2.22 Scenario Travel Management – Travel Expenses............................................................16

2.23 Scenario Sales Analysis Cockpit......................................................................................16

2.24 Scenario Credit Management Cockpit..............................................................................17

2.25 Scenario Data Mining - ABC Classification.......................................................................17



1 Best Practices for Business Intelligence: Solution Scope

1.1 PurposeThis Solution Scope provides an overview of the processes and functions covered by SAP Best Practices for Business Intelligence. It describes the functions and explains their business purposes.

Under Functional Scope – Supported Business Processes or Scenarios, you will find a scenario-based view of the functions.

The Solution Scope does not provide technical explanations of how to use the functions. For further information on this topic, see the business process procedure documents.

2 Functional Scope – Supported Business Processes or Scenarios

2.1 Scenario Financial Accounting AnalysisThis scenario enables you to analyze Financial Accounting data from SAP R/3.

InfoCubes Accounts Receivable: Line Items, Payment History, Transaction Data

Accounts Payable: Line Items, Transaction Data

General Ledger: Transaction Figures, Financial Statements

Asset Accounting: Annual Values, Period Values

Accounts Receivable: Line Items, Payment History, Transaction Data

Key Points Analysis of all accounts receivable data (transaction figures, line items, payment history)

Analysis of all accounts payable data (transaction figures, line items)

Analysis of all the transaction data from the general ledger, financial statement items in detail

Analysis of the annual and period values from asset accounting

2.2 Scenario Controlling AnalysisThis scenario enables you to analyze Controlling data from SAP R/3.



InfoCubes CO-OM-CCA: Costs and Allocations - technical name: 0CCA_C11

CO-OM-CCA: Costs and Allocations (by Activity Type)- technical name: 0CCA_C02

CO-OM-CCA: Activity Type Quantities and Prices- technical name: 0CCA_C04

CO-OM-CCA: Statistical Key Figures - technical name: 0CCA_C03

CO-PC-OBJ: Cost Object Controlling - technical name: 0PC_C01

CO-PC: Product Cost Planning - All Cost Estimates - technical name: 0COPC_C08

CO-PC: Product Cost Planning - Released Cost Estimates - technical name: 0COPC_C09

Transaction Data (Profit Centers) - technical name: 0PCA_C01

Statistical Key Figures (Profit Center) - technical name: 0PCA_C02

Key Points Analysis of full costs on cost centers (plan, target, actual, etc.)

Analysis of information on the origin of the costs (allocation partner such as material number, cost center, and so on)

Analysis of costs broken down into cost components or costs by activity type (fixed and variable costs)

Analysis of activity quantities (plan, actual, target, scheduled activity, capacity)

Analysis of activity prices (plan and actual)

Analysis of statistical key figures on cost centers (plan, actual)

Analysis of transaction that was uploaded from the source system/s data for all product cost collectors and orders.

Analysis of the values of the cost components of the cost component split for all existing material cost estimates, broken down into fixed/variable costs, level/lower-level costs, and costing date

Analysis of the cost components of the cost component split for released material cost estimates in the view relevant to valuation, by fixed and variable costs, level/lower-level costs, and period. Hence it contains only the cost estimates that explain the standard prices of the materials in the particular period analysis of activity quantities (plan, actual, target, scheduled activity, capacity)" Analysis of the cost components of the cost component split for released material cost estimates in the view relevant to valuation, by fixed and variable costs, level/lower-level costs, and period. Hence it contains only the cost estimates that explain the standard prices of the materials in the particular period analysis of activity quantities (plan, actual, target, scheduled activity, capacity)

Analysis of the period totals for profit and loss accounts and balance sheet accounts from Profit Center Accounting (PCA), which were loaded from the affiliated source system(s)

Analysis of all statistical key figures from Profit Center Accounting (PCA), which are loaded from the affiliated source system(s)



2.3 Scenario CO-PA Baseline AnalysisThis scenario contains all activities for a rapid implementation of the CO-PA Analysis in BW.

InfoCubesThis InfoCube allows you to perform a results analysis that is specific to CO-PA of the Baseline Package.

The InfoCube is compatible with the operating concern, which is delivered in the Baseline Package.

Key Points What is unusual about the integration of CO-PA to SAP BW is the fact that CO-PA is an application that generates data but does not deliver any structures or tables. These structures and tables are only defined when the customer-specific operating concern (organizational unit for profitability analysis) is defined in the customizing. To ensure that CO-PA data is analyzed correctly in SAP BW, the structure of the InfoCube should correspond to that of the appropriate operating concern.

2.4 Scenario Cost Center PlanningBusiness Planning and Simulation offers the functionality to plan cost center data in the SAP BW system.

Key Points The responsible person for plan data of the cost center carries out the following steps:

Copies plan data from a reference plan version in SAP BW-BPS

Maintains the new plan data within SAP BW-BPS

The scenario assumes that the person will plan for a time-span of 12 months. The planner is flexible in the choice of plan versions and time-span to copy. With this scenario the planner has the opportunity to create a rolling forecast as well.

The scenario contains the possibility that only selected users are able to conduct the plan functionalities. For example a cost center manager is enabled to plan his assigned cost center only.

2.5 Scenario Sales Analysis This scenario enables you to analyze sales and distribution data from SAP R/3.

InfoCubes

Quotations / Orders (technical name OSD_C05)

Service Level - Order Quantities (technical name: 0SD_C11)

Service Level: Order Items (technical name: 0SD_C12)

Service Level: Orders (technical name: 0SD_C13)

Backorders (technical name: 0SD_C14)



Sales Overview (technical name: 0SD_C03)

Key Points These InfoCubes enable you to view the following information:

Analysis of all transaction data from sales orders, deliveries and billing documents/invoices

Analysis of order fullfillment from R/3 such as: - Delivery Delays per Sold-to Party - Service Level - Order/ Item/ Quantity Level - Item Fulfillment Cycle Time

You can also track average delivery processing times, such as time elapsed between the material availability date and the date on which the goods arrive at the customer.

Analysis of general figures for quotations including: - Number of quotations created - Net and gross values of the quotations - Number of quotations rejected

You can also calculate the success rate of quotations by comparing quotation and order quantities. Information about the quotation success rate includes: - Comparisons with order probability - Orders that result from quotations

Note:Although you can see whether the order resulted from a quotation, you cannot see whether a quotation led to an order.

2.6 Scenario Cross-Functional Analysis: Financial and Sales Data

The scenario Cross-Functional Analysis: Financial and Sales Data describes all the necessary activities to built up a report that analyzes data from financial accounting and sales and distribution. With the detailed description easy enhancement of the report according to individual customer requierements is possible, for example: include more or other characteristics, other key figures, break down in other intervals, and so on.

Key Points Analyzing financials key figures

Drilling down key figures from sales to the level of the followig characteristics: Sales Organization, Distribution Channel, Division, Sold-to Party, Bill-to Party, Billing Document Number, Sales Group, Sales Employee, Sales District., Sales Office

Analyzing the structure of receivables

Revenue for the current year broken down by due date for net payment in intervals: already paid items, total balance of open items, already overdue items, intervals 16 - 30 days, 31 - 45 days, 46 - 60 days, 61 - 90 days, 91 -120 days, > 120 days



2.7 Scenario Booking Billing Backlog Analysis

Key Points Combination of various information from different sales documents for a complete overview

on open sales orders and deliveries

Analyzing values and quantities backlog in sales orders and deliveries with goods issues posted

Drill down of analysis to the level of single sales order items, materials, customers, shipping points as well as sales organisation, distribution channel and division

2.8 Scenario Work Force Management (WFM)This scenario enables you to analyze different Work Force Management (WFM) data from SAP CRM.

InfoCubes WFM Availability of all employees (Technical Name: 0WFM_C01)

WFM Assignments for cProjects (Technical Name: 0WFM_C02)

Key Points The Employees' Availability report shows the Working Time and Projects (planned ,

booked). A drill down per WBS element and Calendar Year/week is also possible.

The Availability and Projects Assignments report shows the actual and basic start/finish dates. Additionally you can drill down per Calendar Year/Week.

2.9 Scenario CRM Analytics

The scenario CRM Analytics enables you to analyze data from SAP CRM in SAP Business

Information Warehouse.

Key Points

The following types of analyses can be carried out:

CRM Lead Analysis

CRM Activities Analysis

Customer Interaction Center (CIC)

Opportunities Analysis

Sales Order Complaints Analysis

Service Qualtiy Analysis



2.10 Scenario Sales PlanningThe sales planner has the possibility to plan the sales quantity of materials per customer. To support the planning, the sales quantity from the comparison month of the last year is displayed.

Key Points Upload of the sales historical data from SAP R/3

Planning layout which shows the historical data per customer and material

Planning layout with easy navigation

2.11 Scenario Scheduling Agreements AnalysisThis scenario enables you to analyze scheduling agreements from SAP R/3.

As this scenario is meant as example for scheduling agreements analysis, it evaluates forecast delivery schedules only. Neither JIT nor planning delivery schedules are evaluated. However, the scenario can easily be adapted to evaluate JIT or planning delivery schedules.

Key Points Creation of a table view and data source for scheduling agreements data in SAP R/3

Data modelling: Creation of transfer rules, update rules and ODS-Objects in SAP BW

Procedures for loading data

Caution: As in R/3 data is stored only for the current forecast delivery schedule (per scheduling agreement) it must be ensured that data is loaded into BW before a new forecast delivery schedule is inserted into the database. Otherwise the data is lost.

Creation of queries for evaluation forecast delivery schedule:

Display of forecast delivery schedule quantities by the following characteristics: Material, customer (sold-to party), scheduling agreement (order number), schedule line date and delivery schedule date

Display of forecast delivery schedule quantities according to scheduling horizon by scheduling agreement number and delivery schedule date

2.12 Scenario Purchasing AnalysisThis scenario enables you to analyze purchasing data from SAP R/3.

InfoCubes Purchasing Data (technical name: 0PUR _C01)

Vendor Evaluation (technical name: 0PUR_C02)

Purchasing Groups (technical name: 0PUR_C04)



Key Points Analysis of material groups, vendors, and materials. This data enables you to find answers

to the following questions, for example: - Which materials and how much of each material have been ordered from a certain vendor? - How many PO items are there for a certain material group?

Display of scores from the vendor evaluation facility within Purchasing. On the basis of this data, you can compare your vendors with each other and also check whether a certain vendor delivers a material punctually and in the desired quantity for example. Since the scores from the previous period are available in addition to the current score, you can also check whether your vendors' performance is improving or deteriorating.

Analysis of the purchasing activities of your purchasing (buyer) groups. Data on effective order values, invoiced amounts, and number of deliveries is available to you for this purpose. Furthermore, you can obtain an overview of how many documents, document items, and (if applicable) document schedule lines have been created by the purchasing group.

2.13 Scenario Manufacturing Analysis This scenario enables you to analyze production process transaction data in order to be able to carry out the following types of analysis:

Plan/actual comparison

Production period-specific analysis

Capacity analysis

Status analysis

InfoCubes Plan/Actual Comparison Order/Material View (technical name 0PP_C01)

Plan/Actual Comparison Operation/Work Center View (technical name 0PP_C03)

Plan/Actual Comparison Material Consumption (technical name 0PP_C05)

Period-Specific Order/Material View (technical name 0PP_C02)

Period-Specific Operation/Work Center View (technical name 0PP_C04))

Period-Specific Material Consumption (technical name 0PP_C06)

Capacity Load Utilization (technical name 0PP_C13)

Status of Manufacturing Orders (technical name 0PP_C10)

Key Points Analysis of production process transaction data related to the order header and item

Analysis of production process transaction data related to order operations

Analysis of period-specific order/material quantity evaluations



Analysis of period-specific operation/work center quantity evaluations

Analysis of material consumptions of the production

Comparison of the available capacity with the target capacity requirements for the operation segments Process, Setup and Teardown

Status of manufacturing orders

2.14 Scenario Inventory AnalysisThis scenario enables you to analyze stock data from SAP R/3 and to evaluate materials for which no movement has occured.

InfoCubes Material Movements (technical name 0IC_C03)

Slow-Moving Items (technical name 0IC_MC01)

Key Points Stock overview

Valuated Stock Analysis

Blocked Stock Analysis

Slow Moving items Analysis

2.15 Scenario Demand Planning AnalysisThe scenario Demand Planning Analysis in SAP Business Information Warehouse enables you to support the demand planning analysis process in a company. It helps to make the planned / actual sales data comparison.

InfoCubes Plan/Actual Comparison of Sales Quantities (0APO_MC02)

Key Points Plan/Actual Data Comparison

Predefined Query

Web Reporting for this plan/actual data comparison

2.16 Scenario Resource and Operation Data AnalysisThe scenario SCM Resource and Operation Data Analysis enables you to analyze the operations, resource capacity and schedule situation data of the Production Planning / Detailed Planning area of SAP SCM in SAP Business Information Warehouse.



InfoCubesThe analysis is carried out in the Resource/Operation Data query created on the InfoCube APO Resource and Operation Data (technical name: 0APO_C01).

Key Points The Resource and Operation Data InfoCube is provided with the following standard queries for analysis:

Resource: Capacity/Requirements of a Planning Version

Resource: Req. Setup/Processing of Several Planning Versions

Resource: Required Set Up/Processing of a Planning Version

2.17 Scenario Project System – Controlling and DatesThis scenario enables you to analyze project and time data from SAP R/3.

InfoCubes Controlling (Technical Name: 0PS_C04)

Dates (Technical Name: 0PS_C02)

Key Points Overview Report: Using this query you receive an overview of the development status of the

projects you select. The query compares actual and planned costs, actual and planned work, and actual and planned revenues for the selected projects.

Hierarchical Project Overview / Residual Order Plan: With this query you receive the residual order plan for each object, calculated for the network, network activity, activity element, order, and rolled up to the WBS element and project. The system displays the values in a hierarchical way for projects or WBS elements. The fiscal year variant (0FISCVARNT) is necessary as a filter because different variants can have different valuations.

Reports about Project Dates like Milestones, Start- and End date of the Project as well as planed dates.

2.18 Scenario cProjectsThis scenario enables you to analyze different cProjects data from SAP CRM.

InfoCubes Assigned Work and Staffed Required Capacity (Technical Name: 0CPR_C01)

Actual/Planned: Work, Required Capacity, and Dates (Technical Name: 0CPR_C02)

Key Points The Effort and Actual Work report shows different start/finish dates and efforts. A drill down

per project is also possible.



The Assignment of Tasks and Project Role Assignment report shows the employees staffed and assigned to different Projects. You can also drill down per Assignment.

2.19 Scenario Cross-Application Time SheetThis scenario enables you to analyze different Cross Application Time Sheet data from SAP R/3.

InfoCubes Time Sheet (Technical Name: 0CATS_1)

Time Sheet Approved (Technical Name: 0CATS_C01)

Time Sheet for Approval (Technical Name: 0CATS_C02)

Key Points Actual Times on Internal Orders: This query determines the actual times recorded in the

Cross-Application Time Sheet that employees worked on particular internal orders in one quarter.

Actual Hours: This query is used to determine the number of hours recorded by an employee or group of employees. Managers can use the query to check their employees' utilization and therefore determine whether they have free capacity. Consultants can use the query to check the number of hours they have available.

Actual Times on Network Activities: This query determines the actual times recorded in the Cross-Application Time Sheet that employees worked on particular network activities in one quarter.

Tasks: This query displays the sum of working times for any organizational unit. The sum of working times is displayed according to task type and as a total sum for each organizational unit. When you start the query, you can enter an organizational unit as the starting point. The query then not only displays the sum of working times for the specified organizational unit, but also the sum of working times for all subordinate organizational units. However this is dependent on your authorizations. This query can also display employees' organizational reassignment.

2.20 Scenario Time Management – Time and LaborThis scenario enables you to analyze different time management data from SAP R/3.

InfoCubes Time and Labor Data (Technical Name: 0PT_C01)

Key Points Monthly View of Selected Time and Labor Data: This query is used to present selected time

and labor data of one year broken down into months. Quarterly and annual summarizations



can also be calculated by choosing the appropriate line characteristics. Selection areas available are personnel area and calendar year/month.

Time and Labor in Units of Full-Time Equivalents (FTE): This query is used to compare planned time, productive time, and overtime of a year with the values of the previous year. The times are represented in units of full-time equivalents (FTE), in which the number of hours is based on the annual working time of a FTE. The default value of 2000 hours is stored as the annual working time of a FTE in the Business Information Warehouse. If the annual working time of a FTE is 2000 hours, then a planned time of 1,800 hours results in a value of 0.9 in units of FTE.

Compare Overview of Time and Labor to Previous Year: This query is used to assign time and labor data from one year according to time types, and then based on the relation to planned time, compare time and labor from the previous year.

Time and Labor Data with Debited Cost Information: This query is used to compare selected time and labor data from one year with times from the previous year. A hierarchy can be assigned as the only line characteristic to the cost center debited with the corresponding personnel costs.

2.21 Scenario Personnel Development – QualificationsThis scenario enables you to analyze different time management data from SAP R/3.

InfoCubes This scenario enables you to analyze employee qualification data from SAP R/3.

Key Points Annual Comparison of Qualifications per Employee: This query displays the number of

employees with particular qualifications. The maximum number of employees is equal to the headcount of the enterprise.The evaluation is performed as an annual comparison (last month of previous year compared with current month; with absolute and percentage differences).The query enables you to evaluate how qualifications change over a given period.

Qualifications per Employee by Organizational Unit: This query displays the number of employees with particular qualifications. The maximum number of employees is equal to the headcount of the enterprise.The evaluation is performed on the basis of organizational units for the last posted month of the current calendar year.The query enables you to evaluate the number and kind of qualifications in an organizational unit during a given period.

Proficiency of a Qualification per Employee: This query displays the number of employees with particular qualifications. The maximum number of employees is equal to the headcount of the enterprise.The evaluation is performed according to proficiency per qualification for last posted month of the current calendar year.The query enables you to evaluate the proficiency of existing qualifications in your enterprise during a given period.

2.22 Scenario Travel Management – Travel ExpensesThis scenario enables you to analyze travel expense data from SAP R/3.



InfoCubes Travel Expenses: Totals and Receipts (Technical Name: 0FITV_C01)

Key Points Overview of Travel Expenses: The Overview of travel expenses query can be used primarily

as a control instrument for the costs incurred by business trips. It displays, by trip provision variant, the total costs of all the trips created, the miles/kilometers traveled and the trip duration in days.If you also include the user-defined characteristics Trip country and Settlement status, you can, for example, display the costs incurred for all trips to the USA created with the trip provision variant 01 (Germany) that have already been settled.You can also restrict the display to a specific time frame: Display by calendar year / Display by quarter If you select a filter value, only the data for the quarter or calendar year entered is displayed. To view the values of several quarters or years next to one another for comparison, use the appropriate time characteristic to expand the evaluation.

Flight Bookings by Provider

Hotel Bookings by Provider

Car Rental Bookings by Provider

2.23 Scenario Sales Analysis CockpitThis scenario describes the necessary activities in order to be able to analyze sales data from SAP R/3 in the SAP Business Warehouse in an integrated web cockpit, Sales Analysis Cockpit.

InfoCubes Customer (Technical Name: 0SD _C01 )

Sales: Overview (Technical Name: 0SD_C03 )

Delivery service (Technical Name: 0SD_C04)

Offers/Orders (Technical Name: 0SD_C05 )

Activities, Opportunities, Sales Orders (Technical Name: 0CSALMC01)

FIAR: Transaction Data (Technical Name: 0FIAR_C02)

Key Points Plan/actual sales comparison

Quotation pipeline

Analysis of all accounts payable data (transaction figures)

Sales revenue by sales representative in both chart and table format, overview and detail overview

Alerts on sales decrease and delivery delay

Large variety of reports in sales revenue, delivery service, profitability analysis, and quota arrangement.



2.24 Scenario Credit Management CockpitThis scenario describes the necessary activities in order to be able to analyze customer credit information from SAP R/3 in the SAP Business Warehouse in an integrated web cockpit, Credit Management Cockpit.

InfoCubes FIAR: Transaction Data (Technical Name: 0FIAR_C02)

FIAR: Payment History (Technical Name: 0FIAR_C05)

FIAR: Line Item (Technical Name: 0FIAR_O03)

Key Points List of balances in both chart and table format

Overview and detail view

Alerts on overdue invoices and overdue credit memos

Large varieties of reports in customer detail information, such as due date analysis and open item analysis.

2.25 Scenario Data Mining - ABC ClassificationThis scenario enables you to classify customers into classes according to the sales volume they generate. The data basis is taken from the InfoCube Sales Overview.

InfoCubes Sales Overview (technical name: 0SD_C03) - used as a data basis

Key Points Creation of a data mining model for ABC classification

Creation and execution of an analysis process

Creation of a query to display the results of the analysis process


Documents

Best Practices - for Business Intelligence.doc