Professional Documents
Culture Documents
We will discuss leveraging SAP NetWeaver Business Intelligence (SAP NetWeaver BI) for Order-to-Cash (OTC) and Requisition-toPay (RTP) reporting and analysis We will introduce SAP Best Practices for Business Intelligence and evaluate the Sales, Purchasing, and Inventory Analysis scenarios We will focus on the back-end data acquisition and data modeling aspects We will gain an understanding of the applicable standard SAP ERP data sources, extract structures, underlying SAP tables, and their relationship to SAP NetWeaver BI DataStore Objects and InfoCubes We will address incorporating SAP NetWeaver BI within an Enterprise Data Warehouse (EDW) framework
2
Order-to-Cash (OTC) and Requisition-to-Pay (RTP) process overview SAP Best Practices for Business Intelligence Leveraging master data views and conforming dimensions Aligning SAP and non-SAP data Wrap-up
Order-to-Cash Process
Master Data Sales Order Creation Delivery Processing WM Pick, Pack, Transportation Invoice Customer Receive Payment
SAP
Bi l l
Functional Areas Customer Relationship Management Customer Service Sales Administration and Field Sales Finance Distribution Brand Marketing Accounts Receivable and Credit Management
WM = Warehouse Management
Requisition-to-Pay Process
Master Data Purchase Order Goods Receipt Creation Inventory Invoice Receipt Vendor Payment
SAP
Bi l l
Functional Areas Supply Chain Management Purchasing Receiving Inventory Management Demand Planning Accounts Payable
Finance
Order-to-Cash (OTC) and Requisition-to-Pay (RTP) process overview SAP Best Practices for Business Intelligence Leveraging master data views and conforming dimensions Aligning SAP and non-SAP data Wrap-up
SAP Best Practices is the foundation for prepackaged ready-to-use SAP NetWeaver BI solutions SAP Best Practices covers well-proven, industryspecific business processes and supports to exploit the potentials of SAP ERP, SAP CRM, SAP SCM, SAP SRM, and SAP NetWeaver BI Based on flexible building block technology that provides the necessary guidelines and tools to enable content developers to create solutions that follow a common structure f http://help.sap.com/bp_biv270/index.htm
Preconfigured Scenarios
Comprehensive set of scenarios across a broad spectrum of processes Financials Customer Relationship Management Supply Chain Management Product Lifecycle Management Human Capital Management SAP xApp Analytics
4. 5. 6.
Establish BI Connectivity and General Settings for BI Integration Activate business content in Sandbox or Dev environment Review SAP ERP configuration and customizations to understand customer implementation and identify potential areas for risk Gather and analyze business requirements to identify gaps Prioritize gaps and estimate required work effort to resolve Establish overall implementation approach and finalize scope for phase
8. 9. 10.
11. 12.
Establish conformed dimensions across functional areas to support an Enterprise Data Warehouse (EDW) framework Enhance DataSources/Extractors as necessary Enhance or create InfoObjects as necessary Enhance DataStore Objects (DSOs), and InfoCubes to resolve gaps and take into account performance considerations Develop process chains to automate loading processes Develop baseline queries and publish to Web portal
10
Sales Analysis Scenario Purchasing Analysis Scenario Inventory Analysis Scenario Financial Accounting Analysis Scenario
11
The Scenario Documentation provides a high level summary of the applicable queries and the end-user procedural steps for query execution The Scenario Installation identifies the building blocks for implementing the specific scenario
Offers/ Orders Sales Analysis
Delivery Service Analysis
BI Connectivity and General Settings for BI Integration are the base building blocks that are leveraged throughout all SAP Best Practices scenarios
12
Logistics General
Materials Management
Materials Management Master Data Accounting: General Master Data Financial Accounting: General Master Data Financial Accounting: Vendors Master Data Financial Accounting: Customers Master Data General DataSources Master Data
Financial Accounting
PI Basis
Activating all corresponding InfoObject (IO) DataSources initially will save time in the long run if you are installing multiple SAP Best Practices scenarios
13
Transaction RSORBCT (Transfer BI Business Content) Basic BI Content Activation Steps Activate InfoObject Catalogs In Data Flow Before to define InfoAreas and InfoObjects in SAP NetWeaver BI f Check error logs and resolve issues Activate DSOs or InfoCubes In Data Flow Before to define InfoPackages, Transformation Rules1, Data Transfer Processes (DTPs)1, Transfer Rules2, and Update Rules2 in SAP NetWeaver BI f Check error logs and resolve issues Activate DSOs or InfoCubes In Data Flow After to define MultiProviders, Queries, Query Views, and Workbooks f Check error logs and resolve issues Create and/or execute InfoPackages to load master and 1 Applicable to SAP NetWeaver BI 7.0 DataSources transaction data
2
14
3
Select Objects and Transfer
15
SD Transaction DataSources
2LIS_11_VAHDR 2LIS_11_VAITM 2LIS_11_VAKON 2LIS_11_VASCL 2LIS_11_VASTH 2LIS_11_VASTI 2LIS_11_V_SSL 2LIS_12_VCHDR 2LIS_12_VCITM 2LIS_12_VCSCL 2LIS_13_VDHDR 2LIS_13_VDITM
Sales Order Header Sales Order Item Order Conditions Sales Order Schedule Line Sales Order Header Status Sales Document Item Status Sales Order Delivery Delivery Header Delivery Item Schedule Line Delivery Billing Header Billing Item
16
17
18
19
20
21
22
23
24
25
26
27
Delivery Service Analysis 0SD_O01 Order Items 0SD_O02 Returns Items 0SD_O03 Orders 0SD_O04 Open Request Schedule Line 0SD_O05 Order Condition Data 0SD_006 Billing: Condition Data
f f f
f f
28
Sales Analysis
0SD_C03 Sales Overview 0SD_C10 Incoming Orders per Sales Employee 0SD_C15 Condition Value 0SD_MC01 Conditions: Order and Billing Document 0SC_C05 Offers/Orders 0SD_C11 Service Level - Order Quantities 0SD_C12 Service Level: Order Items 0SD_C13 Service Level: Orders 0SC_C14 Backorders
f f f
Offers/Orders
f f
2LIS_11_VAHDR 2LIS_11_VAITM
0SD_O01 Order Items 0SD_O02 Returns Items 0SD_O03 Orders 0SD_O04 Open Request Schedule Line
29
Sales Area
Customer
Material
Unit Time
30
Time
31
Condition
Material Time
Unit
32
Sales Overview Incoming Orders Deliveries Billing Delivery Service Analysis Orders Confirmed as Requested Open Order Qty for Last Week Backorders Delivery Overview Service Level Quantities Service Level Item Level (per Half-Year) Service Level Item Level Service Level Order Level Delivery Delays per Sold-to Party
33
Offers/Orders
0SD_C05 Offers/Orders
Organization Offers/Orders
Cost in statistics currency No. of docs Number of Document Items Gross weight in kilograms Net value order item, Net value of rejected quotation items Net value in statistics currency No. of expired quotations No. of rejected quotation items Net weight in kilograms Order probability of quotation item No. of orders resulting from quotation Qty in base units of measure Condition Subtotal 1 Condition Subtotal 2 Condition Subtotal 3 Condition Subtotal 4 Condition Subtotal 5 Condition Subtotal 6 Volume in cubic decimeters
Value Type
Customer
Material
Validity
Sales Area
Version
SD Document Category
Unit
Time
34
Customer
Material
Order
Sales Area
Unit Time
35
Organization
Customer
Material
Order
Sales Area
Unit Time
36
Service-Level Orders
Organization
Order
Customer
Sales Area
Returns Delivered early/late according to req. delivery date Delivered early/late according to schedule line date Delivered early acc. req. delivery date Delivered early acc. schedule line date Delivered late acc. req. delivery date Delivered late acc. schedule line date More Delivered than Requested Less Delivered than Requested Value delivered early/ late acc. req. delivery date Value of early/late deliveries acc. schedule line date Value delivered early acc. req. delivery date Value of early deliveries acc. schedule line date Value of late deliveries acc. req. delivery date Value of late deliveries acc. schedule line date Value Delivered more Than Requested Less then Requested Delivery Value Delivery Within 24 Hours
Unit
Time
37
Backorders
0SD_C14 Backorders
Organization Backorders
Backorders Backorders in One Day Backorders Within 7 Days Backorders Within 30 Days Backorders: More Than 30 D Open Quantity between Req. Open Quantity between Schedule Open Value between Req. De Open Value between Schedule
Forwarding Agent
Sales Area
Customer
Unit Time
Material
38
Six subtotal key figures included by default SAP Best Practice Leverage subtotal key figures to align with Finance/Controlling Suggested Retail Value Gross Sales Subtotal fields Product-Related Discounts should include components to Customer-Related Allowances get from Gross to Returns Net Sales Freight and Handling Accruals Net Sales
39
Six subtotal key figures included by default Provides ability to compare SAP Best Practice sales values with Suggested Retail Value external/syndicated Point of Sale (POS) data Gross Sales Product-Related Discounts By default, Subtotal 1 represents Gross Sales, Customer-Related Allowances however it includes Returns Returns Discounts, Allowances, and Freight and Handling Returns are typically negative so Net Sales is calculated by Net Sales
adding the key figures Net Sales is included in the standard DataSources as an independent field and not a subtotal value
40
Dynamic/Current View vs. Historical View Navigational Attributes Provides attribute of characteristic at current point in time (Dynamic View) Material Group Historic View Dimension Characteristics Material Type Dynamic View Provides characteristic at Product Hierarchy Historic and transaction point in time
Dynamic View
Time-Dependent Attributes Provides ability to report on attributes at any point in time Very flexible, however also has significant performance impacts
>> Denotes InfoObject as Navigational Attribute
41
Currency Conversion
Default currency for DataSources is typically Document Currency SAP Best Practices scenarios often apply conversion through routines in Update Rules Alternate methods of currency conversion include: Conversion at Query Run-Time Conversion in Transformation or Update Rules (3.x) f Using Translation Types f Using User Defined Routines Custom ABAP in DataSources f SAP Enhancement RSAP001 f Function Modules
42
Transaction RSCUR Define Exchange Rate Type Preconfigured Types From Variable From InfoObject Define Source and Target Currencies Fixed From Variable From InfoObject Define Appropriate Time Reference Fixed Variable
Exchange rates must be loaded from source system on a regular basis 43
Sales Analysis Scenario Purchasing Analysis Scenario Inventory Analysis Scenario Financial Accounting Analysis Scenario
44
The Scenario Documentation provides a highlevel summary of the applicable queries and the end-user procedural steps for query execution The Scenario Installation identifies the building blocks for implementing the specific scenario
Purchasing Group Purchasing Data Vendor Evaluation
BI Connectivity and General Settings for BI Integration are the base building blocks that are leveraged throughout all SAP Best Practices scenarios
45
Materials Management
Purchasing
f f f f f f f
Delivery Confirmations Purchasing Header Purchasing Line Item Vendor Evaluation Purchasing Schedule Line Schedule Line Confirmation Schedule Line Delivery
46
47
Lots of queries, but no use of DSOs or MultiProviders Only subset of available DataSources leveraged
48
Limited # of queries No use of DSOs or MultiProviders Only subset of available DataSources leveraged
49
Purchasing InfoCubes
50
Purchasing Data
Purchasing Data
Purchasing Info Record Purchasing Info Record Category Version/ Value Type Contracts
Material
Material Group
Vendor
Indicator
Time
Unit
51
Vendor Evaluation
Purchasing Organization
Material
Vendor
Indicator
Time
Unit
52
Purchasing Groups
Value Type
Purchasing Group
Cancellation
Vendor
Unit
Time
53
Sales Analysis Scenario Purchasing Analysis Scenario Inventory Analysis Scenario Financial Accounting Analysis Scenario
54
The Scenario Documentation provides a highlevel summary of the applicable queries and the end-user procedural steps for query execution The Scenario Installation identifies the building blocks for implementing the specific scenario
Material Movements Slow Moving Items
BI Connectivity and General Settings for BI Integration are the base building blocks that are leveraged throughout all SAP Best Practices scenarios
55
Materials Management Inventory Management f 2LIS_03_BF Goods Movement f 2LIS_03_BX Stock Initialization f 2LIS_03_UM Revaluation
56
LBWE Activate Extract Structures BF11 Set BW Application Active SBIW Determine Industry Sector Delete Contents of Setup Tables Post Stocks Replicate Data Sources Activate Business Content *
* May
57
58
Sales Analysis Scenario Purchasing Analysis Scenario Inventory Analysis Scenario Financial Accounting Analysis Scenario
59
The Scenario Documentation provides a highlevel summary of the applicable queries and the end-user procedural steps for query execution The Scenario Installation identifies the building blocks for implementing the specific scenario
AR Analysis Asset Analysis AP Analysis GL Analysis
Basic Configuration Financial Accounting Analytics General Settings for BI Integration BI Connectivity
BI Connectivity and General Settings for BI Integration are the base building blocks that are leveraged throughout all SAP Best Practices scenarios
60
Customers: Line Items with Delta Extraction Customers Payment History Customer Sales Figures
61
Duplicate Invoices
0FI_AR_4
BSAD (Accounting: Secondary index for customers (cleared items)) Company Code (BUKRS) Customer (KUNNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
BKPF (Accounting document header) Company Code (BUKRS) Document No (BELNR) Fiscal Year (GJAHR) All FI documents
BSIK (Accounting: Secondary index for vendors) Company Code (BUKRS) Vendor (LIFNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
Closed items
Open Items
text
BSEG (Accounting document segment) Company Code (BUKRS) Document No (BELNR) Fiscal Year (GJAHR) Line Item (BUZEI)
Open Items BSID (Accounting: Secondary index for customers) Company Code (BUKRS) Customer (KUNNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
Closed items
Open Items
Closed items
BSAK (Accounting: Secondary index for vendors (cleared items)) Company Code (BUKRS) Vendor (LIFNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
BSIS Company Code (BUKRS) G/L Account (HKONT) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
BSAS (Accounting: Secondary index for G/L accounts (cleared items)) Company Code (BUKRS) G/L Account (HKONT) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
KNC1 (Customer master (trans figures)) Customer (KUNNR) Company Code (BUKRS) Fiscal Year (GJAHR)
LFC1 (Vendor master (transaction figures)) Vendor (LIFNR) Company Code (BUKRS) Fiscal Year (GJAHR)
62
Recent SAP NetWeaver BI content updates have replaced older DataSources and added DSOs
63
DataStore Objects 0FIAR_O03 Accounts Receivable Line Item 0FIAR_O06 Accounts Receivable Transaction Data InfoCubes 0FIAR_C03 Accounts Receivable Line Item 0FIAR_C05 Accounts Receivable Payment History 0FIAR_C02 Accounts Receivable Transaction Data
64
Customer
Dunning Data
Payment Data
Unit
65
Time
Customer
Unit
66
Time
Customer
Unit
67
0FIAR_C03 A/R Line Item Days Overdue Analysis Due Date for Net Payment Analysis (Credit Management) Overdue Analysis (Credit Management) Analysis of Due Date for Net Payment (Business Partner) Due Date for Net Payment Analysis Overdue Analysis (Business Partner) Terms Offered Customers: Overview Customers: Overview (Credit Management)
68
0FIAR_C05 A/R Payment History Customers: Payment History (Credit Management) Customers: Payment History Time Series: 12 Periods into Past Customers: Arrears for Payment w/o Cash Discnt (Credit Mgt) 0FIAR_C02 A/R Transaction Data Customers: DSO Analysis, Timeline (Credit Management) Time Series: 12 Periods into Past Customers: DSO Analysis for a Period (Credit Management) Customers: DSO Analysis, current Period Customers: DSO Analysis for a Period (Credit Management)
69
Standard InfoCube captures current open A/R plus all cleared A/R After month-end, the Analysis Process Designer (RSANWB) can be used to capture historical Open A/R so that it can be analyzed over periods of time
70
0FI_AP_4 0FI_AP_6
Vendors: Line Items with Delta Extraction Vendor Sales Figures via Delta Extraction
71
0FI_AP_4
BKPF (Accounting document header) Company Code (BUKRS) Document No (BELNR) Closed items Fiscal Year (GJAHR)
All FI docume nts
BSIK (Accounting: Secondary index for vendors) Company Code (BUKRS) Vendor (LIFNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
Open Items
BSID (Accounting: Secondary index for customers) Company Code (BUKRS) Customer (KUNNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
Open Items
BSEG (Accounting document segment) Company Code (BUKRS) Document No (BELNR) Fiscal Year (GJAHR) Line Item (BUZEI)
text BSAK (Accounting: Secondary index for vendors (cleared items)) Company Code (BUKRS) Vendor (LIFNR) Special G/L Trans (UMSKS) Special G/L Ind (UMSKZ) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
Closed items
Open Items
Closed items
BSIS Company Code (BUKRS) G/L Account (HKONT) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
BSAS (Accounting: Secondary index for G/L accounts (cleared items)) Company Code (BUKRS) G/L Account (HKONT) Clearing Date (AUGDT) Clearing Doc (AUGBL) Allocation No (ZUONR) Fiscal Year (GJAHR) Document No (BELNR) Line Items (BUZEI)
KNC1 (Customer master (trans figures)) Customer (KUNNR) Company Code (BUKRS) Fiscal Year (GJAHR)
LFC1 (Vendor master (transaction figures)) Vendor (LIFNR) Company Code (BUKRS) Fiscal Year (GJAHR)
72
Like A/R, recent business content updates have added DSOs, however the A/P scenario solution has much less in terms of pre-built queries
73
InfoCubes 0FIAP_C03 Accounts Payable Line Items 0FIAP_C02 Accounts Payable Transaction Data Queries 0FIAP_C02_Q0001 Vendors Overview
74
G/L Account
Dunning Data
Payment Data
Unit
75
Time
Customer
Unit
76
Order-to-Cash (OTC) and Requisition-to-Pay (RTP) process overview SAP Best Practices for Business Intelligence Leveraging master data views and conforming dimensions Aligning SAP and non-SAP data Wrap-up
77
Basic View
Consistent across all sales areas Example: Name, Address Sales- and shipping-specific information by sales area Example: Price Group, Price List, Shipping Condition Financial information per company Example: Reconciliation Accounting, Payment Terms
78
79
0MATERIAL Basic Data 0MAT_SALES Sales Area Data 0MAT_PLANT Purchasing/Inventory Data Basic View
Consistent across all sales areas Example: Material Group, Material Type, Product Hierarchy Sales and shipping specific information Example: Material Group 15, Product Hierarchy Financial information Example: Controlling Area, Profit Center, Purchasing Group
80
Plant View
81
Primarily used when searching for materials Characteristic values entered into the classes for each material can be searched to identify materials with like attributes Very powerful functionality but requires significant effort to identify and create characteristics and classes and enter the corresponding values
82
Organization
Customer
Time
0COMP_CODE 0SALESORG 0DISTR_CHAN 0DIVISION 0BUS_AREA 0CO_AREA 0C_CTR_AREA 0MATERIAL 0MAT_SALES 0MAT_PLANT
0CUSTOMER 0CUST_SALES 0CUST_COMPC 0SOLD_TO 0SHIP_TO 0BILL_TO 0PAYER 0DOC_TYPE 0DEL_TYPE 0BILL_TYPE 0ORD_REASON Etc
Product
Business Reason
Date
All other dates not in time dimension Syndicated calendar (4-4-5) InfoCube DBMS partitioning (a.k.a., Physical partitioning) must be administered using a characteristic of the Time dimension and 83 only using a characteristic of the Time dimension
Order-to-Cash (OTC) and Requisition-to-Pay (RTP) process overview SAP Best Practices for Business Intelligence Leveraging master data views and conforming dimensions Aligning SAP and non-SAP data Wrap-up
84
There are many ways to integrate non-SAP data into an SAP NetWeaver BI environment DB Connect UD Connect Flat File XML BAPI DB Connect typically provides better performance than UD Connect, however it requires a Windows-based application server in order to connect to Microsoft SQL Server UD Connect offers the flexibility to connect to a wide array of sources including relational data sources, OLE DB for OLAP data sources, and XMLA-capable data providers
85
Activate the full spectrum of InfoObject (IO) DataSources from the beginning to gain understanding of available master data Conform dimensions across InfoCubes Align characteristics prior to loading into SAP NetWeaver BI Consistently leverage DSOs Create distinct DSOs and InfoCubes for non-SAP data Leverage both logical and physical partitioning to enhance loading and query performance Always leverage MultiProviders to provide a consolidated view of homogeneous and heterogeneous InfoProviders
86
Include a Counter InfoObject in all line item DSOs and InfoCubes Include Suggested Retail Value in sales key figures so that its easier to compare amounts with consumption data Leverage a custom Date dimension to account for dates not included in Time dimension and maintain a custom Date characteristic InfoObject to handle special calendars
87
Order-to-Cash (OTC) and Requisition-to-Pay (RTP) process overview SAP Best Practices for Business Intelligence Leveraging master data views and conforming dimensions Aligning SAP and non-SAP data Wrap-up
88
Resources
SAP Best Practices for Business Intelligence v2.7 http://help.sap.com/bp_biv270/index.htm SAP Library http://help.sap.com/saphelp_nw70/helpdata/en/ http://help.sap.com/bp/initial/ NetWeaver Tab SAP NetWeaver 7.0 (Download or Order DVD) SAP NetWeaver BI content www.sdn.sap.com/irj/sdn/nw-informationmanagementww.sd n.sap.com/irj/sdn/nw-informationmanagement?rid=/webcon tent/uuid/9076f97a-50e1-2a10-fc8c-b5c97310c9d5
89
There are a wide range of opportunities to leverage SAP NetWeaver BI to enhance your reporting and analytical capabilities SAP Best Practices for Business Intelligence is an excellent starting point, but not necessarily a production-ready solution Activation of SAP Best Practices scenarios and standard business content in sandbox or a development environment does not mean that it has to move to production Implement DataStore Objects consistently and at the line item level to provide an effective data staging layer
90
Leverage master data views to conform dimensions across subject areas Understand implications of modeling InfoObjects as characteristics of dimensions vs. navigational attributes Leverage pricing procedure subtotal key figures to provide a breakdown from gross to net sales and to ensure alignment with Finance and Controlling (FI/CO)
Your Turn!
Disclaimer
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, 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. Wellesley Information Services is neither owned nor controlled by SAP.
93