76618056 BI Building Blocks of SD AR AP

© 2008 Wellesley Information Services. All rights reserved.

Get the Most Out of Order-to-Cash and Requisition-to-Pay Reporting and Analytics Functionality in SAP NetWeaver BIDon WelkerClarkston Consulting

2

In This Session ...

• We will discuss leveraging SAP NetWeaver® Business Intelligence (SAP NetWeaver BI) for Order-to-Cash (OTC) and Requisition-to-Pay (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, andtheir relationship to SAP NetWeaver BI DataStore Objects and InfoCubes

• We will address incorporating SAP NetWeaver BI within an Enterprise Data Warehouse (EDW) framework

3

What We’ll Cover …

• 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

• Functional AreasCustomer Relationship ManagementCustomer ServiceSales Administration and Field SalesDistributionBrand MarketingAccounts Receivable and Credit Management 44

Master Data Sales Order

CreationDelivery

ProcessingWM Pick, Pack,Transportation

ReceivePayment

InvoiceCustomer

Bill

SAP

Finance

WM = Warehouse Management

Requisition-to-Pay Process

5

Master Data Purchase Order

CreationGoodsReceipt

Inventory VendorPayment

InvoiceReceipt

Bill

SAP

• Functional AreasSupply Chain ManagementPurchasingReceivingInventory ManagementDemand PlanningAccounts Payable

Finance

6




SAP Best Practices for Business Intelligence

• SAP Best Practices is the foundation for prepackaged ready-to-use SAP NetWeaver BI solutions

• SAP Best Practices covers well-proven, industry-specific business processes and supports to exploit the potentials of SAP ERP, SAP CRM, SAP SCM, SAP SRM, and SAP NetWeaver BI

7

• 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

http://help.sap.com/bp_biv270/index.htm

Preconfigured Scenarios

• Comprehensive set of scenarios across a broad spectrum of processes

FinancialsCustomer Relationship ManagementSupply Chain ManagementProduct Lifecycle ManagementHuman Capital ManagementSAP xApp Analytics

8

SAP Best Practices Scenario Implementation Steps

1. Establish BI Connectivity and General Settings for BI Integration2. Activate business content in Sandbox or Dev environment3. Review SAP ERP configuration and customizations to

understand customer implementation and identify potential areas for risk

4. Gather and analyze business requirements to identify gaps5. Prioritize gaps and estimate required work effort to resolve6. Establish overall implementation approach and finalize scope

for phase

9

10

SAP Best Practices Scenario Implementation Steps (cont.)

7. Establish conformed dimensions across functional areas to support an Enterprise Data Warehouse (EDW) framework

8. Enhance DataSources/Extractors as necessary9. Enhance or create InfoObjects as necessary10. Enhance DataStore Objects (DSOs), and InfoCubes to resolve

gaps and take into account performance considerations11. Develop process chains to automate loading processes12. Develop baseline queries and publish to Web portal

11


• Sales Analysis Scenario• Purchasing Analysis Scenario• Inventory Analysis Scenario• Financial Accounting Analysis Scenario

Sales Analysis Scenario

• 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

12

BI Connectivity

General Settings for BI Integration

Basic Configuration – Sales Analytics

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

General Settings for BI Integration – InfoObject DataSources

• Logistics GeneralLO-IO Logistics Master Data

• Sales and DistributionSD-IO Sales Master Data

• Materials ManagementMM-IO Materials Management Master Data

• Financial AccountingAC-IO Accounting: General Master DataFI-IO Financial Accounting: General Master DataFI-AP-IO Financial Accounting: Vendors Master DataFI-AR-IO Financial Accounting: Customers Master Data

• PI Basis0CA-GD-IO General DataSources Master Data

13

Activating all corresponding InfoObject (IO) DataSources initially will save time in the long run if you are installing multiple SAP Best Practices scenarios

T-Codes on SAP ERP System•SBIW•RSA3•RSA5•RSA6

General Settings for BI Integration – Activate BI Content

• 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

Check error logs and resolve issuesActivate 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

Check error logs and resolve issuesActivate DSOs or InfoCubes “In Data Flow After” to define MultiProviders, Queries, Query Views, and Workbooks

Check error logs and resolve issuesCreate and/or execute InfoPackages to load master and transaction data

141 Applicable to SAP NetWeaver BI 7.0 DataSources2 Applicable to SAP BW 3.x DataSources

General Settings for BI Integration – Activation Steps

15

Select Objects and Transfer

5

Gather Dependent Objects 1

3

5

24

16

SD Transaction DataSources

• Sales and Distribution2LIS_11_VAHDR Sales Order Header2LIS_11_VAITM Sales Order Item2LIS_11_VAKON Order Conditions2LIS_11_VASCL Sales Order Schedule Line2LIS_11_VASTH Sales Order Header Status2LIS_11_VASTI Sales Document Item Status2LIS_11_V_SSL Sales Order Delivery2LIS_12_VCHDR Delivery Header2LIS_12_VCITM Delivery Item2LIS_12_VCSCL Schedule Line Delivery2LIS_13_VDHDR Billing Header2LIS_13_VDITM Billing Item

SD – Sales Order Tables

17

SD – Sales Order Tables (cont.)

18


19


20


21

SD – Sales Delivery Tables

22

SD – Sales Delivery Tables (cont.)

23

SD – Sales Billing Tables

24

SD – Sales Billing Tables (cont.)

25

26

Sales Analysis Data Flow – Sales Analysis and Offers/Orders• Inconsistent Use of DSOs and MultiProviders

27

Sales Analysis Data Flow – Delivery Service Analysis

• Inconsistent Use of DSOs and MultiProviders

SD Transaction DataStore Objects (DSOs)

• Delivery Service Analysis0SD_O01 – Order Items0SD_O02 – Returns Items0SD_O03 – Orders0SD_O04 – Open Request Schedule Line0SD_O05 – Order Condition Data0SD_006 – Billing: Condition Data

28

2LIS_11_VAHDR2LIS_11_V_SSL2LIS_11_VASTH

2LIS_11_VAKON2LIS_13_VDKON

SD Transaction InfoCubes and MultiProviders

• Sales Analysis0SD_C03 – Sales Overview0SD_C10 – Incoming Orders per Sales Employee0SD_C15 – Condition Value0SD_MC01 – Conditions: Order and Billing Document

• Offers/Orders0SC_C05 – Offers/Orders

• Delivery Service Analysis0SD_C11 – Service Level - Order Quantities 0SD_C12 – Service Level: Order Items 0SD_C13 – Service Level: Orders 0SC_C14 – Backorders

29

2LIS_11_VAITM2LIS_12_VCITM2LIS_13_VDITM

2LIS_11_VAHDR2LIS_11_VAITM

0SD_O01 – Order Items0SD_O02 – Returns Items0SD_O03 – Orders0SD_O04 – Open Request Schedule Line

Sales Overview Data Model

30

Time

Organization

Customer

Material

Document Classification

Sales Area

Category/Brand

SD Document Category

Unit

Sales OverviewCost in statistics currencyNo. of docsNumber of Document ItemsGross weight in kilogramsNumber of EmployeesNet value in statistics currencyNet weight in kilogramsOpen orders Qty in base units Net value of open orders in statisticQty in base units Subtotal 1Subtotal 2Subtotal 3Subtotal 4Subtotal 5Subtotal 6Volume

Version

Value Type

• 0SD_C03 – Sales Overview

Incoming Orders per Sales Employee Data Model

31

Time

Sales EmployeeEmployee » Country Grouping » Controlling Area » Employee Group » Employee Subgroup » Employee Subgrp Group » Master Cost Center » Organizational Unit » Payroll Area » Pay Scale Area » Pay Scale Group » Pay Scale Level » Pay Scale Type » Personnel Area » Personnel Subarea Sales Representative Sales Organization

Unit

Sales Overview

Number of EmployeesNet Price

• 0SD_C10 – Incoming Orders per Sales Employee

Sales Analysis – Condition Value Data Model

32

Time

Organization

Customer

Material

Condition

Sales Area

Unit

Condition Value

Cumulative Order QtyCondition Value (Local)

• 0SD_C15– Condition Value

Sales Analysis Scenario Queries

• Sales OverviewIncoming Orders DeliveriesBilling

• Delivery Service AnalysisOrders Confirmed as RequestedOpen Order Qty for Last WeekBackordersDelivery OverviewService Level – QuantitiesService Level – Item Level (per Half-Year)Service Level – Item LevelService Level – Order LevelDelivery Delays per Sold-to Party

33

34

Offers/Orders

Time

Organization

Customer

Material

SD Document Category

Value Type

Unit

Offers/Orders

Cost in statistics currencyNo. of docsNumber 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 3Condition Subtotal 4 Condition Subtotal 5 Condition Subtotal 6 Volume in cubic decimeters

• 0SD_C05 – Offers/OrdersValue Type

VersionSales Area

Validity

Status

35

Service-Level Order Quantities

Time

Organization

Customer

Material

ForwardingAgent

Unit

Service Level Order Quantities

Confirmed Qty Confirmed value Qty delivered early Req Del Date Qty Delivered Early Schl Line DateQty delivered late Req Del Date Qty delivered late Schl Line DAte Value delivered early Req Del DateValue delivered early Schl Line Date Value of late deliveries Req Del DateValue of late deliveries Schl Line DateActual Qty delivered Actual Delivered Value Qty Confirmed as Requested Completely Delivered Qty Return Quantities Desired Delivery Qty Requested Delivery Value Value of Completely Delivered Value of Returns Value Confirmed as Requested

• 0SD_C11 – Service-Level Order QuantitiesCategory/

Brand

Sales Area

Order

Batch

36

Service-Level Order Items

Time

Organization

Customer

Material

ForwardingAgent

Unit

Service Level Order Items

Cumulated Order Processing Time for Al Delivered early/late according to req. Delivered early/late according to schedule Delivered early acc. req. delivery dateDelivered early acc. schedule line dateDelivered 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. Value of early/late deliveries acc. sc Value delivered early acc. req. delivery Value of early deliveries acc. schedule Value of late deliveries acc. req. del Value of late deliveries acc. schedule Value Delivered more Than Requested Less then Requested Delivery Value Delivery Within 24 Hours Actual Delivered Value Number of Document Items Confirmed as Requested Delivery from Warehouse Net value of the order item in documentRequested Delivery Value Value with Delivery Within 24 Hours Value Confirmed as Requested Value with Delivery from Warehouse

• 0SD_C12 – Service-Level Order Items

Sales Area

Order

Batch

37

Service-Level Orders

Time

Organization

CustomerUnit

Service Level Orders

ReturnsDelivered early/late according to req. delivery dateDelivered early/late according to schedule line dateDelivered early acc. req. delivery dateDelivered early acc. schedule line dateDelivered late acc. req. delivery dateDelivered late acc. schedule line dateMore Delivered than RequestedLess Delivered than RequestedValue delivered early/ late acc. req. delivery dateValue of early/late deliveries acc. schedule line dateValue delivered early acc. req. delivery dateValue of early deliveries acc. schedule line dateValue of late deliveries acc. req. delivery dateValue of late deliveries acc. schedule line dateValue Delivered more Than RequestedLess then Requested Delivery ValueDelivery Within 24 Hours

• 0SD_C13 – Service-Level Orders

Sales Area

Order

38

Backorders

Time

Organization

Customer

Material

ForwardingAgent

Unit

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

• 0SD_C14 – Backorders

Sales Area

Pricing Procedures and Subtotal Key Figures

• Six subtotal key figures included by default• SAP Best Practice – Leverage subtotal key figures to align with

Finance/ControllingSuggested Retail ValueGross SalesProduct-Related DiscountsCustomer-Related AllowancesReturnsFreight and HandlingAccrualsNet Sales

• See SAP Note 155012 in order to add additional subtotal fields 39

Subtotal fields should include components to get from Gross to Net Sales

Pricing Procedures and Subtotal Key Figures (cont.)

• Six subtotal key figures included by default• SAP Best Practice

Suggested Retail ValueGross SalesProduct-Related DiscountsCustomer-Related AllowancesReturnsFreight and HandlingNet Sales

40

Discounts, Allowances, and Returns are typically negative so Net Sales is calculated by adding the key figures

By default, Subtotal 1 represents Gross Sales, however it includes Returns

Provides ability to compare sales values with external/syndicated Point of Sale (POS) data

Net Sales is included in the standard DataSources as an independent field and not a subtotal value

Slowly Changing Dimensions

• Dynamic/Current View vs. Historical View• Navigational Attributes

Provides attribute of characteristic at current point in time (Dynamic View)

• Dimension CharacteristicsProvides characteristic at transaction point in time

41

Material Group – Historic ViewMaterial Type – Dynamic ViewProduct Hierarchy – Historic and Dynamic View

• Time-Dependent AttributesProvides ability to report on attributes at any point in timeVery flexible, however also has significant performance impacts

>> Denotes InfoObject as Navigational Attribute

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-TimeConversion in Transformation or Update Rules (3.x)

Using Translation TypesUsing User Defined Routines

Custom ABAP in DataSourcesSAP Enhancement RSAP001Function Modules

EXIT_SAPLRSAP_001READ_EXCHANGE_RATEBAPI_EXCHANGERATE_GETDETAIL 42

Currency Conversion Using Translation Types

• Transaction RSCUR• Define Exchange Rate Type

Preconfigured TypesFrom VariableFrom InfoObject

• Define Source and Target CurrenciesFixedFrom VariableFrom InfoObject

• Define Appropriate Time ReferenceFixedVariable

43

Exchange rates must be loaded from source system on a regular basis

44



Purchasing Analysis Scenario

• The Scenario Documentation provides a high-level summary of the applicable queries and the end-user procedural steps for query execution


45

BI Connectivity


Basic Configuration –Purchasing Analytics

Purchasing Group

Purchasing Data

Vendor Evaluation


46

Purchasing Analysis Transaction DataSources

• Materials ManagementPurchasing

2LIS_02_CGR Delivery Confirmations2LIS_02_HDR Purchasing Header2LIS_02_ITM Purchasing Line Item2LIS_02_S013 Vendor Evaluation2LIS_02_SCL Purchasing Schedule Line2LIS_02_SCN Schedule Line

Confirmation2LIS_02_SGR Schedule Line Delivery

MM – Purchasing/Inventory Analysis SAP ERP Tables

47

Purchasing Data Analysis Data Flow

• Lots of queries, but no use of DSOs or MultiProviders• Only subset of available DataSources leveraged

48

Purchasing Group Analysis and Vendor Evaluation Data Flow• Limited # of queries• No use of DSOs or MultiProviders• Only subset of available DataSources leveraged

49

Purchasing InfoCubes

• 0PUR_C01 – Purchasing Data• 0PUR_C02 – Vendor Evaluation• 0PUR_C04 – Purchasing Groups

50

Purchasing Data

51Time

PurchasingOrganization

Material

Vendor

Purchasing Info Record Category

Purchasing Info Record

Unit

Purchasing Data# of deliveriesDelivery Date Variance 1-5Delivery Qty variance 1-5Invoice amount: ReturnsWeighted total delivery timeEffective order value of returnsValue of goods receivedGoods receipt value Invoice Receipt Qty Invoice Amount Actual goods receipt QtyGoods receipt Qty of returnsGoods receipt Qty in base unitGR value: ReturnsInvoiced amountInvoice receipt Returns QtyIR Qty: ReturnsIR value: ReturnsInvoice receipt QtyEffective PO valueTarget delivery QtyOrder Qty (returns)# of contract items# of sched agrmt schedule lines# of PO schedule lines# of PO itemsOrder Qty# of quotation items# of request for quotation items# of scheduling agreement itemsTotal delivery time in days

• 0PUR_C01 – Purchasing Data

Plant

Material Group

Version/ Value Type

Contracts

Process Characteristics

Country

Indicator

Vendor Evaluation

52Time


Material

Vendor

Purchasing Info Record Category

Purchasing Info Record

Unit

Vendor Evaluation

Score 1: on-time delivery performanceScore 2: on-time delivery performanceScore 1: quality auditScore 2: quality auditScore 1: quantity reliabilityScore 2: quantity reliabilityScore 1: shipping notificationScore 2: shipping notificationScore 1: shipping instructionsScore 2: shipping instructionsScore 1: quality of service provisionScore 2: quality of service provisionScore 1: service timelinessScore 2: service timelinessScore 1: shipping notification varianceScore 2: shipping notification variance

• 0PUR_C02 – Vendor Evaluation

Plant

Version/ Value Type

Indicator

Purchasing Groups

53

Time


PurchasingGroup

Cancellation

ValueType

Version

Unit

Purchasing Groups

Contracts Contract items Deliveries Scheduling AgreementsInvoiced Amount Purchase Orders Quotation Requests Purchase Order ValuePO Schedule LinesPO Items Quotation Items Request for Quotation Scheduling Agreements

• 0PUR_C04 – Purchasing Groups

Vendor

54



Inventory Analysis Scenario



55

BI Connectivity


Material Movements Slow Moving Items


56

Inventory Analysis Transaction DataSources

• Materials ManagementInventory Management

2LIS_03_BF Goods Movement2LIS_03_BX Stock Initialization2LIS_03_UM Revaluation

Inventory Analysis SAP ERP Activation and Setup

• LBWEActivate Extract Structures

• BF11Set BW Application Active

• SBIWDetermine Industry SectorDelete Contents of Setup TablesPost Stocks

• Replicate Data Sources• Activate Business Content *

57* May have been previously completed

Inventory Analysis Data Flow

• Unlike the majority of other scenarios, Inventory Analysis leverages non-cumulative key figures

• Requires “different”kind of compression

58

How To… Handle Inventory Management Scenarios in BW•www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328

59



Financial Accounting Analysis Scenario



60


BI Connectivity


Basic Configuration –Financial Accounting Analytics

ARAnalysis

AssetAnalysis

APAnalysis

GLAnalysis

Accounts Receivable (A/R) Transaction DataSources

• Financial Accounting – Customers0FI_AR_4 Customers: Line Items with Delta Extraction 0FI_AR_5 Customers Payment History0FI_AR_6 Customer Sales Figures

61

FI – Accounts Receivable Tables

62

All

FI

docu

men

ts

Closed items

Open Items

Closed items

Closed items

Open Items

Open Items

Duplicate Invoices

VBLNR

LFC1(Vendor master (transaction figures))Vendor (LIFNR)Company Code (BUKRS)Fiscal Year (GJAHR)

KNC1(Customer master (trans figures))Customer (KUNNR)Company Code (BUKRS)Fiscal Year (GJAHR)

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)

BSIP(Index for vendor validation of double documents)Company Code (BUKRS)Vendor (LIFNR)Currency (WAERS)Document Date (BLDAT)Reference Doc (WRBTR)Amount (WRBTR)Document No (BELNR)Fiscal Year (GJAHR)Line Items (BUZEI)

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)

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)

BVOR(Intercompany posting procedures)Intercompany No (BVORG)Company Code (BUKRS)Fiscal Year (GJAHR)Document No (BELNR)

PAYR(Payment transfer medium file)Paying Company (ZBUKR)House Bank (HBKID)Account (HKTID)Payment Method (ZLSCH)Check No (CHECKT)

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)

BSEG(Accounting document segment)Company Code (BUKRS)Document No (BELNR)Fiscal Year (GJAHR)Line Item (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)

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)

text

0FI_AR_4

Accounts Receivable Data Flow

• Recent SAP NetWeaver BI content updates have replaced older DataSources and added DSOs

63

Accounts Receivable DSOs and InfoCubes

• DataStore Objects0FIAR_O03 – Accounts Receivable Line Item0FIAR_O06 – Accounts Receivable Transaction Data

• InfoCubes0FIAR_C03 – Accounts Receivable Line Item0FIAR_C05 – Accounts Receivable Payment History0FIAR_C02 – Accounts Receivable Transaction Data

64

Accounts Receivable Line Item

65

CompanyCode

Payment Data

G/L Account

A/R Line ItemAmount in Local Currency with +/- SignsAmount eligible for cash discount in doc currencyCash discount amount in local currencyForeign currency amount with signs (+/-)Cash discount amount in document currencyCredit amount in foreign currencyCredit amount in local currencyDebit amount in foreign currencyDebit amount in local currencyNet period usedInterest Calculation Numerator Days 1 (Agreed)Interest calculation numerator days 2 (Agreed)Interest Calculation Numerator Net (Agreed)Interest Calculation Numerator Days 1 (Realized)Interest Calculation Numerator Days 2 (Realized)Interest Calculation Numerator Net (Realized)

• 0FIAR_C03 – Accounts Receivable Line Item

Customer

Dunning Data

Due Dates

DocumentData

Time

Unit

Accounts Receivable Payment History

66

CompanyCode

Currency Type

A/R Payment History

Payment Volume w/Cash DiscountPayment Volume w/o Cash DiscountAverage Arrears for Payment w/Cash DiscountAverage Arrears for Payment w/o Cash DiscountNumber of Incoming Payments in the PeriodCustomer

Time

Unit

• 0FIAR_C05 – Accounts Receivable Payment History

Accounts Receivable Transaction Data

67

CompanyCode

Currency Type

A/R Transaction Data

Sales for the PeriodTotal Debit PostingsCumulative BalanceTotal credit postingsCustomer

Time

Unit

• 0FIAR_C02 – Accounts Receivable Transaction Data

Accounts Receivable Queries

• 0FIAR_C03 – A/R Line ItemDays Overdue AnalysisDue 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 AnalysisOverdue Analysis (Business Partner)Terms OfferedCustomers: OverviewCustomers: Overview (Credit Management)

68

69

Accounts Receivable Queries (cont.)

• 0FIAR_C05 – A/R Payment HistoryCustomers: Payment History (Credit Management)Customers: Payment HistoryTime Series: 12 Periods into PastCustomers: Arrears for Payment w/o Cash Discnt (Credit Mgt)

• 0FIAR_C02 – A/R Transaction DataCustomers: DSO Analysis, Timeline (Credit Management)Time Series: 12 Periods into PastCustomers: DSO Analysis for a Period (Credit Management)Customers: DSO Analysis, current PeriodCustomers: DSO Analysis for a Period (Credit Management)

Accounts Receivable Historical Activity

• 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

Accounts Payable (A/P) Transaction DataSources

• Financial Accounting – Vendors0FI_AP_4 Vendors: Line Items with Delta Extraction0FI_AP_6 Vendor Sales Figures via Delta Extraction

71

FI – Accounts Payable Tables

72

All FI

docume

n ts

Closed items

Open Items

Closed items

Closed items

Open Items

Open Items

Duplicate Invoices

VBLNR

LFC1(Vendor master (transaction figures))Vendor (LIFNR)Company Code (BUKRS)Fiscal Year (GJAHR)

KNC1(Customer master (trans figures))Customer (KUNNR)Company Code (BUKRS)Fiscal Year (GJAHR)

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)

BSIP(Index for vendor validation of double documents)Company Code (BUKRS)Vendor (LIFNR)Currency (WAERS)Document Date (BLDAT)Reference Doc (WRBTR)Amount (WRBTR)Document No (BELNR)Fiscal Year (GJAHR)Line Items (BUZEI)

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)

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)

BVOR(Intercompany posting procedures)Intercompany No (BVORG)Company Code (BUKRS)Fiscal Year (GJAHR)Document No (BELNR)

PAYR(Payment transfer medium file)Paying Company (ZBUKR)House Bank (HBKID)Account (HKTID)Payment Method (ZLSCH)Check No (CHECKT)

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)

BSEG(Accounting document segment)Company Code (BUKRS)Document No (BELNR)Fiscal Year (GJAHR)Line Item (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)

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)

text

0FI_AP_4

Accounts Payable Data Flow

• 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

Accounts Payable InfoCubes and Queries

• InfoCubes0FIAP_C03 – Accounts Payable Line Items0FIAP_C02 – Accounts Payable Transaction Data

• Queries0FIAP_C02_Q0001 – Vendors Overview

74

Accounts Payable Line Items

• 0FIAP_C03 – Accounts Payable Line Items

75

CompanyCode

Payment Data

G/L Account

A/P Line Item

Amount in Local Currency with +/- SignsAmount eligible for cash discount in document currencyCash discount amount in local currencyForeign currency amount with signs (+/-)Cash discount amount in document currencyCredit amount in foreign currencyCredit amount in local currencyDebit amount in foreign currencyDebit amount in local currency

Vendor

Dunning Data

Due Dates

DocumentData

Time

Unit

Accounts Payable Transaction Data

• 0FIAP_C02 – Accounts Payable Transaction Data InfoCubes

76

CompanyCode

Currency Type

A/P Transaction Data

Sales for the PeriodTotal Debit PostingsCumulative BalanceTotal credit postingsCustomer

Time

Unit

77




Leveraging Customer Master Views

• 0CUSTOMER• 0CUST_SALES• 0CUST_COMPC

78

• Basic View• Consistent across all sales areas

• Example: Name, Address• Sales Area View

• Sales- and shipping-specific information by sales area

• Example: Price Group, Price List, Shipping Condition

• Company Code View• Financial information per company

• Example: Reconciliation Accounting, Payment Terms

•

Customer Master SAP ERP SAP NetWeaver BI InfoObject Relationship

79

Leveraging Material Master Views

• 0MATERIAL – Basic Data• 0MAT_SALES – Sales Area Data• 0MAT_PLANT – Purchasing/Inventory Data

80

• Basic View• Consistent across all sales areas

• Example: Material Group, Material Type, Product Hierarchy

• Sales Area View• Sales and shipping specific information

• Example: Material Group 1…5, Product Hierarchy

• Plant View• Financial information

• Example: Controlling Area, Profit Center, Purchasing Group

Material Master ERP BI InfoObject Relationship

81

Material Master Classification View

• 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

Conforming Dimensions in EDW Framework

• Organization0COMP_CODE0SALESORG0DISTR_CHAN0DIVISION0BUS_AREA0CO_AREA0C_CTR_AREA

• Product0MATERIAL0MAT_SALES0MAT_PLANT

• Time0CALDAY0CALWEEK0CALMONTH 0CALQUARTER 0CALYEAR 0FISCPER0FISCPER30FISCYEAR 0FISCVARNT

• DateAll other dates not in time dimensionSyndicated calendar (4-4-5)

83

• Customer0CUSTOMER0CUST_SALES0CUST_COMPC0SOLD_TO0SHIP_TO0BILL_TO0PAYER

• Business Reason0DOC_TYPE0DEL_TYPE0BILL_TYPE0ORD_REASON Etc …

InfoCube DBMS partitioning (a.k.a., Physical partitioning) must be administered using a characteristic of the Time dimension and only using a characteristic of the Time dimension

84




85

Aligning SAP and Non-SAP Data

• There are many ways to integrate non-SAP data into an SAP NetWeaver BI environment

DB ConnectUD ConnectFlat FileXMLBAPI

• DB Connect typically providesbetter performance than UDConnect, however it requiresa 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

Top 10 Recommendations Within EDW Framework

• Activate the full spectrum of InfoObject (IO) DataSourcesfrom the beginning to gain understanding of availablemaster 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

* EDW – Enterprise Data Warehouse 86

Top 10 Recommendations Within EDW Framework (cont.)

• Include a “Counter” InfoObject in all line item DSOs and InfoCubes

• Include Suggested Retail Value in sales key figures so that it’s 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

88




89

Resources

• SAP Best Practices for Business Intelligence v2.7http://help.sap.com/bp_biv270/index.htm

• SAP Libraryhttp://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 contentwww.sdn.sap.com/irj/sdn/nw-informationmanagementww.sdn.sap.com/irj/sdn/nw-informationmanagement?rid=/webcontent/uuid/9076f97a-50e1-2a10-fc8c-b5c97310c9d5

90

7 Key Points to Take Home

• 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

7 Key Points to Take Home (cont.)

• 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)

92

Your Turn!

How to contact me:Don Welker

[email protected]

DisclaimerSAP, 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

Documents

76618056 BI Building Blocks of SD AR AP