MDF SUPPLEMENTAL SLIDES Employee Central Mastery ©2013. SuccessFactors, Inc., An SAP Company. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without the express written permission of SuccessFactors. This software is commercial computer software developed exclusively at private expense. The software and documentation are provided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in DFARS 252.227.7202-3 or FAR 52.227-19, as applicable. Developer is SuccessFactors, Inc., An SAP Company, 1 Tower Place, Suite 1100, South San Francisco, CA 94080. "Rwiz" is a trademark of Enterprise Information Resources, Inc. The product described herein includes software developed by the Apache Software Foundation (http://www.apache.org/). All other brand and product names that are mentioned herein are the trademarks or registered trademarks of their respective holders. All examples, including the names of people in the examples or screen shots are fictitious. No association with any real person (living or deceased), company (existing currently or in the past), or events should be inferred from any example whatsoever. Information in this document is subject to change without notice and does not represent a commitment on the part of SuccessFactors. SuccessFactors, Inc., an SAP Company SuccessFactors Global Headquarters 1 Tower Place, Suite 1100 South San Francisco, CA 94080 USA www.successfactors.com 2 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Table of Contents OData APIs and MDF MDF and SuccessFactors Reporting Tools Job Profile Builder 3 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Chapter 1: OData API and MDF Chapter 1: Objectives Define the OData API Explain the Odata API’s importance List tasks that can be completed with the Odata API Define what data can be accessed in SuccessFactors using Odata Configure the OData API Define the future of OData API at SuccessFactors 5 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. What is the OData API? The OData API is SuccessFactors new API strategy. OData is a standardized protocol for data APIs. OData is REST based. OData has metadata to represent the API operations and the data schema: Data schema means the entities, relationships between entities and fields. Learn more at http://www.odata.org 6 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Why is OData Important? A standards based protocol eases API support, increases adoption. Customers don’t have to learn proprietary features of SFAPI like SFQL and our custom metadata. OData is an SAP Standard. Powerful query features to pull data from multiple entities (think SQL JOINS). Data can be returned in nested data structures, with choice of XML or JSON formats. Critical to Hana Cloud Extensibility 7 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. What can you do with the OData API? Query to extract data from the system Create (insert) new data in the system Update existing data in the system Delete data from the system Operate on multiple related entities in a single operation Important: the “metadata” operation allows you to view the data schema 8 What are the entities in a customer’s configuration? What are the relationships between these entities? What are the fields and data types of these entities? Lots of other metadata features like field labels, field behaviors, etc. SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. SuccessFactors Module Coverage by OData API What modules and entities can the OData API access? See http://confluence/display/PRODINFO/OData+Entity+Type+Guide The OData API accesses data from: Employee Central Platform MDF application entities – 9 You cannot define new data types or fields using the OData API, you must use the MDF user interface to create new object definitions. But once you do, they will appear in OData API. SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Permissions and Use Cases The OData API requires administrative permissions to access data: Employee Central: Admin Access Required. All MDF Entities require “Manage Generic Objects” permission. Platform User: Requires Employee Import and Export permission. In 1311, the OData API will allow user-based permissions (non-admin) to EC and MDF entities: Allows any user to perform API operations based on their RBP permission access. Necessary to enable application extension use cases (Hana Cloud Extension). 10 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. OData, SFAPI and Boomi The Boomi connector can access both OData and SFAPI entities. OData entities start with SFOData in the Boomi connector. SFOData.User SFOData.Position etc New integrations should prefer OData entities over SFAPI Use of SFAPI is approved if such entity is not available in OData 11 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Long Term Roadmap OData Everywhere: Plans for OData APIs to all modules in the suite. – – – – 12 Will open up our integration capabilities Will launch our extensibility capabilities Critical to a vibrant partner ecosystem Powerful competitive feature SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Summary OData provides: Standard protocol Increased adoption Easier API Better for extensibility Alignment with SAP Standards 13 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Chapter 2: MDF and SuccessFactors Reporting Tools Chapter 2: Objectives Explain the relationship between MDF, Rule Engine, and SuccessFactors Reporting tools List ODS Reporting features supported by rules 15 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. SuccessFactors Reporting Tools Workforce Analytics Youcalc Dashboards Headlines Ad-Hoc Reporting 16 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. As time goes by… ODS Reporting: Features All fields of ALL EC tables are available for ODS reporting Including Custom fields No coding No need to know the data model, just drag-and-drop Search function for fields Field labels are taken from customizing (aka “succession data model”) All active Custom fields are available Advanced mode for individual joins Powerful handling of effective dating Pivot Queries for simple OLAP reporting Report designer Embedding queries into page 17 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. ODS Reporting Workflow Infohrm SFSF UI Report content development Report Pivot Query Application WFA Measures Query DB 18 ODS Golden Gate Replication Service SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. ODS Cube ODS Reporting Workflow As depicted in the previous illustration: 1. The MDF Data is replicated through Oracle’s Golden Gate Replication Service to the ODS Data Warehouse. 2. The ODS Inform system then creates ODS Cubes on top of that Data Warehouse 3. You can then create reports using the MDF Entities can use the ODS Report Designer 4. Using the ODS Report Designer you can drag MDF object or object structures, set suitable joins, where clauses – actually build a Report Query on the fly 5. You can then run the report, preview it and save it for future use. 19 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. ODS Reporting: Features 20 ODS is the tool for flexible and easy-to-use reporting in EC All tables / all fields available out of the box (that is, MDF objects, custom fields) Query definition requires no knowledge of data model. Advanced mode for handling of complex cases Powerful features for handling of Effective Dating Note: your data model will be exposed to customers (that is, key users developing custom reports) SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Chapter 3: Job Profile Builder, Skills Management and MDF Chapter 3: Objectives Define Job Profile Builder Explain MDF is used in Job Profile Builder Explain how MDF is used in Job Profile Builder 22 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. What Is Job Profile Builder? Goal At it’s core, Job Profile Builder is a replacement for existing Families & Roles in addition to a Platform-level replacement for JDM 1.0. However, if fully leveraged, JPB and Skills Management can help answer the question, “Do I have the right person in the right job at the right time?” 23 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. Why Did We Use MDF? COMPLEX PROBLEM: QUICK SOLUTION • To deliver significant new functionality in <3 builds. • Support of multiple content types • Specific import validations and notifications • Complex permissions model SUITE-WIDE INTEGRATION AND ADOPTION • Platform project which requires adoption by suite to show value to our customers FUTURE IN MIND • Based on the overall direction of the SuccessFactors suite, decided to become an early adopter of MDF DEVELOPMENT TOOLS AT NO EXTRA COST • • • • • • • 24 Object Data Model Import/Export with validations and notifications RBP UI Delivered (Consistent UI) Ability to customize UI when appropriate Workflow API SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved. How did we use MDF? To help organize this process: 25 SuccessFactors Proprietary and Confidential © 2013 SuccessFactors, An SAP Company. All rights reserved.
