Srini Santhanam, Capgemini US, LLC Integration of Complex SAP and Non-SAP Applications Through SAP BusinessObjects Data Services for the Fortune 500

Srini Santhanam, Capgemini US, LLC

Integration of Complex SAP and Non-SAP Applications Through SAP BusinessObjects Data Services for the Fortune 500 CPG Company

Learning Points

 Integration of SAP and non-SAP sources with different granularity of data

 Flexible realignment for the organization hierarchy changes

 Automated data reconciliation across source systems

 Self-Service reporting

 Master Data harmonization

 Robust Error handling process

Key Business Drivers

 Delivering actionable Information & Insights in the right format, at the right time, to the right people

 Integration of SAP and non-SAP Sources to provide one version of truth for all Financial needs

 Self-Service Reporting

 Flexibility to handle Organizational changes

 Complex business rules managed by Business

 Master data harmonization for Customer and material

Integrated Architecture

SAP ECC

SAP BW

Oracle

Salesforce & Teradata

SAP BOFC SAP ECC Others Transactional Legacy Systems Business rules

Business Mapping Reporting/Analytics

SAP Business Objects Data Services SAP BW/HANA SAP BusinessObjects BI Platform Financial Information Management

Enterprise Data warehouse Transactional

EDW

Consolidation

Corporate Financial Reporting - Integration of SAP and non-SAP systems

Smart Key Flow

SAP Data Services

Smart Key represents Financial characteristics like Organization unit, profit center, etc. that will enable flexible financial reporting based on a organizational changes

Customer Master Data Team

Business COE

Transactional Data Source

Systems

Example: SK03 (Smart Key) -ECCP001C0001 (Smart Key ID) ECC – Source system, P001- Profit center, C001 - Cost center

Smart Key Hierarchy based reporting Reference hierarchy Smart Key Hierarchy Maintenance

Defines the Smart Key units and Organizational Characteristics

with Parent

Add Smart Key ID to Transactional

Data Translates to Smart Key with

Organizational Characteristics

Build a table for hierarchy based on Smart Key,

Smart Key ID

Reporting Based on Smart

Key ID Build Hierarchy Master Data FIM SAP ECC SK02 ECCP001C0001 SK01

Dynamic Account Hierarchy

 All the parent Child

relationships maintained in FIM by business COE

 Rollup of accounts defined in Hierarchy like Gross Revenue, COGS, Deductions, etc.

 Reporting Team should not hardcode any item lower than GL roll-up accounts

 Supports dynamic G/L account structure changes

 Hierarchy nodes number rages are defined based on SAP standard hierarchy ( example: 3 * accounts represent

Revenues) SAP BW Data Services FIM Populate the Parent and Child

Relationships to support BW

hierarchy

Generates the Flat-file

Loads the G/L account for

Reporting

Reports Build based on G/L

account Hierarchies G/L Account Line

Self-Service Reporting Architecture

 Relational DB model to consume in BO Explorer

Master Data Integration

 Integration of Customer and Material Master data across Business organizations

 Enable collaborative authoring of information across business areas  Creating “Golden records” with Key data elements to be used across

Business platforms

 Common core fields standardized and syndicated to downstream systems

 Hierarchies and groupings to support business needs

Integration of customer and material master to support across business functions

Robust Error Handling Process

SAP and Non-SAP Sources Data Services Load Process Mapping, Business and error Rules Business Objects Reporting FIM Manage Business Mappings Business Users SAP BW Error Records Good Records Error Records Error Reporting

Financials - Detail and Summary

Master Data Corrections

Process to

 Handle error records

 Master Data issues

 Transactional Data re-processing

 Notification mechanism on the errors

In Progress

 Workflow to automate the error handling

Infocube

FIM Tool – Business Managed Mapping

Can help your business users

access, map, and load

financial information from disparate sources

The financial information

management application allows data extraction from an SAP EPM application and import it into SAP NetWeaver Business Warehouse

Creation of Mapping

 Run-rate savings by operational efficiencies and automation required to create financial management reports

 Reducing resource intensive processes

 Operational efficiencies

 One source of truth for financial reporting

 Provides access to consistent and certified information

 Input for Financial planning

Return on Investment

 High data volume - ~ 4 billion invoice records/year, ~12 million records for customer master Data

 Report Publications - Allows easy distribution of information (single report or multiple reports) to individuals or groups of users and personalize the information each user or group that receives it

 A lack of report standardization and master data

harmonization result in extensive manual workarounds at high costs to the Finance organization

 Maintenance of Global customer master data across several business units

 Leverage of FIM for mappings to reflect the real-time organizational hierarchy

 Automated Error reconciliation process

 Automatic reconciliation process

 Flexible Business hierarchies through Smart keys

Best Practices

Key Learnings

 Master Data harmonization across different business units

 Created the mockup visualization and aligned with the users in the earlier phase of the project

 Automatic Reconciliation - Make simpler validations from source data to target

 Focused on master data strategy before all the complex transactional business rules built

Stay Informed

Tom Wailgum : @twailgum

Chris Kanaracus : @chriskanaracus Craig Powers : @Powers_ASUG

SESSION CODE

2924