1. Product Manager SAP Integration
Richard Foley
Product Manager SAP Integration

3. Understand and Deploy
Business Process

4. Agenda

5. SAP R/3 Integration

6. SAS Accessing SAP R/3 Features Key Benefits
Full access to all data structures
Direct access to SAP metadata.
Key Benefits
Granularity of the data is at the detail level
Ability to access any and all SAP environments
Ability to combine R/3 data with non SAP data
Supports standard SAP logon authorization
SAS/ACCESS to R/3 and BW uses RFC technology to communicate with a SAP R/3 and BW system. SAS/ACCESS to R/3 can be used to access data in SAP BW, since SAP BW is built on top of R/3. The disadvantage is that you would have to implement BW logic to make sense of the extracted table. With Access to BW this logic is extracted from the BW system.
Automatically adheres to existing SAP security rules for user access to data
Unix & Windows platforms
Flexibility for architect

7. Real-Time Data Quality
SAP Client
DFClent
Transactional
Data
DFServer

8. SAS Solution Integration Architecture Example SAP
SAS Solution Adatper
HCM FM
SRM
SAP R/3
Years of working with SAP we are using our intellectual knowledge to help customers come get their SAS solutions up faster. We take the necessary data out of SAP R/3 and load the information into a SAS specific solution. This saves in start up time allowing you to obtain a faster time to intelligence.
ABM
ITM
SPM

9. SAS® Solution Adapters for SAP
Features
SAP data sources are pre-defined
ETLQ routines are pre-defined and customizable
Automates building of data model for corresponding SAS Solution
Ensures decision makers have the information required to make decisions based on real facts
Key Benefits
Fast answers to questions about your customers, suppliers and internal organization.
Quick implementation e.g. weeks not months
Ability to enrich SAP data with non SAP data
SAS/ACCESS to R/3 and BW uses RFC technology to communicate with a SAP R/3 and BW system. SAS/ACCESS to R/3 can be used to access data in SAP BW, since SAP BW is built on top of R/3. The disadvantage is that you would have to implement BW logic to make sense of the extracted table. With Access to BW this logic is extracted from the BW system.

10. SAP BW Integration

11. Infocube to Star Schema
SAP BW Infocubes are built in a Snowflake schema, easier maintanance but hard to report and do analytics on. By extracting out the Infocube and placing it into a Star Schema, a common practice, SAS Data Surveyor automatically extracts out the Infocube and converts it into a Star Schema for you making it easier for reporting. As you can see this is a very complex process and with the data surveyor you save time, resources and money.
Below is a snippet taken from MSFT Best BI Practices
A snowflake schema is very appealing to database administrators, because it normalizes the dimensional relationship. A snowflake design breaks a dimension’s hierarchical levels into separate tables, with foreign key relationships between them. The cleanest designs use surrogate keys for all dimension level tables. The foreign keys ensure referential integrity, guaranteeing that a Product rolls up into one and only one Product Group. Users hate snowflake schemas because they are difficult to navigate, and because query performance in the relational database is degraded relative to the corresponding star schema.
A star schema collapses the multiple tables for a single dimension such as Product into a single flat dimension. Users who query the relational database directly will find a star schema much easier to use, and queries will perform better.
Some practitioners use a snowflake schema to maintain dimensions, and then present users with the same data collapsed into a star

12. SAS Accessing SAP BW Features Key Benefits
Full access to InfoCubes and ODS Objects
Direct access to SAP metadata
Key Benefits
Fast answers to questions about your customers, suppliers and internal organization.
Ability to enrich SAP BW with non SAP data
Automatically adheres to existing SAP security rules for user access to data
Supports SAP BAPIs
Supports standard SAP logon authorization
SAS/ACCESS to R/3 and BW uses RFC technology to communicate with a SAP R/3 and BW system. SAS/ACCESS to R/3 can be used to access data in SAP BW, since SAP BW is built on top of R/3. The disadvantage is that you would have to implement BW logic to make sense of the extracted table. With Access to BW this logic is extracted from the BW system.
Unix & Windows platforms
Flexibility for architect

13. Advanced Analytics integrated with Reporting
Forecasting
Data Mining
Optimization
Design of Experiments
Integrated With MSOffice
So now there is a single version of the truth, and an end to end intelligent platform that works with
Forecasting
Data Mining
Optimization

14. Netweaver Integration

15. SAS Server SAP Netweaver Web Service
SAP XI
Portal
SOAP
HTTP
Web Service
(middle tier Java or .Net code)
IOM
SAS Server
(ie, SAS Stored Process Server or SAS Metadata Server)

16. Case Study – Manufacturing Pro-Active Business Intelligence
What Happens If
What Happened
Why Did It Happen

17. Goals Lower Inventory Overhead Improve Product Quality Control
Improve Global Sales Force Operations

18. US Disparate Data Sources
Challenges
US Disparate Data Sources
Europe ?
Asia Pacific ?
SAP R/3
SAP BW
R/3 System
Only the Sales cube had been populated in SAP BW.
Many end users using BEX for forecasting to determine production quota’s. This causes many problems as multiple “Excel marts” were being created, each with its own business rules and inputs.
Not all data stored in SAP. Legacy data and compliance data was stored in other operational systems.
European offices have not migrated to SAP. Most data is in Excel Spread sheets more “Excel Marts”
Poor data quality from erroneous input or missing values
Needed to forecast over 4000 different products with 24 months of history. Using BEX and Excel this took over 2 days just to download and compile
Compliance System
Other Data Sources
Legacy Data
External Data

19. Intelligent Architecture
Enterprise Data Warehouse
Operational Systems
Cleanse data during ETL integrated with SAS ETLQ
Bring everything under one Metadata repository.
Cleanse Data During ETL
Open Meta Data Repository

20. Intelligent Architecture
Operational Systems or ODS
Analytical Cube
Power User
Statistician
Analyst
Enterprise Data Warehouse
Currently the EDW consists of Three Data marts:
Backorders (shown) –Star Schema shown
Inventory
Sales
As the users build the warehouse what becomes important is the Analytical warehouse were Power users are able to do push their analysis to the business users. Then as users drill down into the data the analytics will update and everyone will have a single version of the truth.
Data Mart
Business Users
Open Meta Data Repository

21. Results Improve Operational Efficiency Decrease Shelf Inventory
Impowered sales force with shelf-life management by predicting parishable products shelf life
Increase production quality with data mining to obtain new 6 Sigma measurements.

22. It’s not SAS or SAP, but SAS and SAP
Kimberly-Clark Europe
Issy Aydiner, Finance Director Supply Chain
“SAS is the industry standard in this area. It’s also easy-to-use and has good reporting capabilities. With SAS at the heart of the solution, we can do all the supply chain modeling, simulation and planning we need. SAS is used for the ‘top down’ part of the process: taking numbers from the General Ledger and breaking these numbers down into unit costs: for example, costs related to storage locations. This data then feeds into the SAS Value Chain Analytics application, along with data from SAP R/3, which covers the ‘bottom up’ part of the process. The combination of the two approaches is unique and provides Kimberly- Clark Europe with accurate and actionable cost information at all levels of the business.

23. Questions