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

Transcription

1 Srini Santhanam, Capgemini US, LLC Integration of Complex SAP and Non-SAP Applications Through SAP BusinessObjects Data Services for the Fortune 500 CPG Company Session # 2924

2 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 Business managed mapping of Master Data through FIM tool

3 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

4 Integrated Architecture Corporate Financial Reporting - Integration of SAP and non-sap systems SAP ECC Transactional SAP BW EDW Business Mapping Reporting/Analytics SAP ECC Transactional Financial Information Management SAP BusinessObjects BI Platform SAP BOFC Oracle Salesforce & Teradata Others Consolidation Legacy Systems Flat Files SAP Business Objects Data Services Business rules SAP BW/HANA Enterprise Data warehouse

5 Smart Key Flow 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 SAP ECC Smart Key Hierarchy Maintenance FIM SK01 SK02 ECCP001C0001 SAP Data Services Master Data Example: SK03 (Smart Key) - ECCP001C0001 (Smart Key ID) ECC Source system, P001- Profit center, C001 - Cost center Business COE Defines the Smart Key units and Organizational Characteristics with Parent Translates to Smart Key with Organizational Characteristics Build a table for hierarchy based on Smart Key, Smart Key ID Build Hierarchy Reference hierarchy Source Systems Transactional Data Add Smart Key ID to Transactional Data Reporting Based on Smart Key ID Smart Key Hierarchy based reporting

6 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) G/L Account Line items Maintenance FIM Populate the Parent and Child Relationships to support BW hierarchy Generates the Flat-file Data Services Loads the G/L account for Reporting SAP BW Reports Build based on G/L account Hierarchies

7 ODB C Self-Service Reporting Architecture Source Systems Universes Transactional Data SAP BW Bex Queries OLAP Connection Business Objects toolsets SAP ECC SAP ECC SAP BW/HANA Transactional Data Power Bex Queries to support most of the Financial needs Relational DB model to consume in BO Explorer Consume relational robust model in SAP Lumira Legends Direct DB OLAP

8 Master Data Integration Integration of customer and material master to support across business functions 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

9 Robust Error Handling Process Business Users FIM Manage Business Mappings Process to Handle error records Master Data issues Transactional Data re-processing Notification mechanism on the errors SAP and Non-SAP Sources Data Services Load Process Mapping, Business and error Rules Good Records DSO SAP BW Infocube Financials - Detail and Summary Business Objects Reporting Master Data Corrections Error Records Error Records Error Reporting In Progress Workflow to automate the error handling

10 FIM Tool Business Managed Mapping Creation of Mapping Can help your business users access, map, and load financial information from disparate sources Mapping Tables The financial information management application allows data extraction from an SAP EPM application and import it into SAP NetWeaver Business Warehouse

11 Return on Investment 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

12 Key Challenges 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

13 Best Practices 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

14 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

15 Stay Informed Follow the ASUGNews team Tom Wailgum Chris Kanaracus Craig Powers

16 SESSION CODE 2924