EIM264 Flexible Governance Govern Your Own Objects in SAP Master Data Governance

Transcription

1 EIM264 Flexible Governance Govern Your Own Objects in SAP Master Data Governance

2 Disclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent SAP AG. All rights reserved. 2

3 SAP Master Data Governance Centrally govern master data on top of SAP Business Suite SAP MDG is a natural extension of the business processes running in SAP Business Suite, providing out-of-the-box, domain-specific master data governance to centrally create, change and distribute master data. Governance Enables governance, compliance and transparency through integrated staging, approval and central audit trail Consistent Data Delivers consistent definition, authorization and replication of key master data entities for SAP. Eliminates error prone manual maintenance processes for master data in multiple systems Integration Re-use Data Quality NW MDM & MDG Native integration with SAP Business Suite and SAP ERP Re-use of SAP data model, UI and existing business logic and configuration for creation and validation of master data Integrates with SAP BusinessObjects Data Services for data quality and data enrichment as well as SAP BusinessObjects Information Steward for data remediation Can complement and extend SAP NetWeaver MDM 2012 SAP AG. All rights reserved. 3

4 SAP Master Data Governance Process flow archetype External Providers External Services Master Data Governance Central maintenance of master data in staging area Re-Use existing business logic Integrate external services Data Enrichment, Address Cleansing, Duplicate Check Maintain Validate Approve Replicate 3rd party systems Collaboration Adaptable Workflow Auditable Change Process Automatic replication to non-sap and SAP systems Business Suite systems 5 Adapt Adaptation / Enrichment in local systems 5 Business Processes 2012 SAP AG. All rights reserved. 4

5 Data maintenance using Change Requests The business process view Governance through Change Requests Act as container for new and changed data Determine process flow and processors Group multiple changes according to business semantic Create Change Request Collect Comments Approve by Business Execute Changes Final Approval Example: Change request for chart of accounts in MDG for Financial Data 2012 SAP AG. All rights reserved. 5

6 Change Request Change Request Handling of active and inactive data To enable the master data governance process MDG separates Active data Ready to be used by applications, can be distributed to client systems Inactive data Not yet approved, currently part of a change request Accordingly there are two separate storage locations Active area Holds the active data Staging Holds the data during the change request processing before approval For optimal integration into SAP Business Suite, MDG allows two modes Re-Use active area (re-use mode) Existing structures (i.e. data base tables) of applications are used. For example, MDG for material makes use of the MARA table in ECC. Generated active area (flex mode) Tables as defined in the MDG data model are used to store active data. Flex Mode New or changed data Re-Use Mode New or changed data Staging Activation Inactive Data MDG Application Foundation Active Area Active Data Staging Inactive Data MDG Application Foundation Activation Active Area Active Data Suite Application 2012 SAP AG. All rights reserved. 6

7 Data modeling & custom objects Use cases & examples Use cases for adding entity types in delivered standard data models: Additional objects in the context of the standard MDG domains (Financials, Supplier, Material) Examples: Subordinate entity types of material that are not (yet) delivered with the data model MM Include fields from customer enhancements into MDG data model, e.g. Z-tables & Fields Use Case: Processing Custom Objects independent from standard objects Governance of object types that are not combined with a delivered standard MDG data model. Examples: Reference data, e.g. Bank Codes. Additional objects from finance or controlling like Activity Type, Statistical Key Figure, etc SAP AG. All rights reserved. 7

8 Fundamental steps to configure a governance scenario 1. Data Model To define the staging area To define the active area (flex mode) To make elementary settings on the change process 2. User Interface To enable users to display and enter data 3. Process To define the change request flow (e.g. steps, transitions between steps, ) To determine processors 4. Checks, Derivations, Validations, 5. Distribution 6. Scope of this session and exercises 2012 SAP AG. All rights reserved. 8

9 MDG Custom Object configuration entry points NWBC Example role provided for this session Transactions Started from NWBC LAUNCH 2012 SAP AG. All rights reserved. 9

10 Fundamental Steps to Configure a Governance Scenario EXERCISE 1 Create data model Create entity type and attribute for Car Manufacturer EXERCISE 2 Create UI configuration Start FPM tools Copy template Link UI configuration to data model Create new form Create Layout EXERCISE 4 Create the user menu Copy template role with PFCG Add search capability Add create and maintain capability EXERCISE 5 Use the newly created scenario Search for manufacturers Create a new manufacturer Use Change Request inbox for processing Observe how processing continues EXERCISE 3 Create process configuration Create Business Activity Create change request type Assign processor to change request steps 2012 SAP AG. All rights reserved. 10

11 Configure Data Model Entry Point 2012 SAP AG. All rights reserved. 11

12 Data Modeling (selected scope for exercise) Entity Types Fundamental Properties Usage and storage types (SUT) SUT 1: Governance and persistence in MDG SUT 2: Persistence in MDG but no governance SUT 3: Check table (no governance, no persistence in MDG) SUT 4: Dependent (like 1, but can only be maintained together with an entity of type 1) Data Element ID Determines the key of an entity (together with inherited IDs through relationships) Field labels (for use on user interface and generic functions, e.g. mass change) Attributes (for SUT 1 & 4) Data elements determine type, field labels, settings for change documents, F1 & F4 help Search helps can be assigned, can be set as mandatory / not checked for existence Texts Used as description, short, medium, long length Can be language dependent 2012 SAP AG. All rights reserved. 12

13 Entity-types Overview: Storage and usage type Storage type 1 Storage type 2 Storage type 3 Storage type 4 Data storage generated (edition dependent + staging) Can be fully modeled (can hold attributes and references etc.) Maintenance via CR (entry point) Optional assignment of data element (technical properties, F1, UI texts) Check table/domain fix value behind data element are ignored. F4 goes to generated check table. To be used for entity-types which should be maintained in MDG Data storage generated (no edition, no staging) No further modeling possible (only check and text table generated) No maintenance via CR Mandatory assignment of data element (technical properties, F1, UI texts) Check table/domain fix value behind data element are ignored. F4 goes to generated check table. To be used for entity-types which should not be maintained by MDG and which are not available in the system No data storage generated No further modeling possible No maintenance in MDG at all Mandatory assignment of data element (technical properties, F1, UI texts) Check table/domain fix value behind are used F4 goes to check-text table/domain fix value behind data element. None-key fields in check table are ignored To be used for entity-types which should not be maintained by MDG and which are available in the system Data storage generated (edition dependent + staging) Can be (almost) fully modeled (can hold attributes and references etc.) Maintenance via CR (NO entry point, maintenance via owning storage type 1 entity-type) No assignment of data element possible To be used for entity-types which should be maintained in MDG in the context of another (owning) entity-type 2012 SAP AG. All rights reserved. 13

14 Exercise Important Properties of Entity Types Name Storage and Usage Type (SUT) Data Element Text (Description of entity) Description (of entity type) 2012 SAP AG. All rights reserved. 14

15 Demo

16 Logging on 2012 SAP AG. All rights reserved. 18

17 Fundamental Steps to Configure a Governance Scenario EXERCISE 1 Create data model Create entity type and attribute for Car Manufacturer EXERCISE 2 Create UI configuration Start FPM tools Copy template Link UI configuration to data model Create new form Create Layout EXERCISE 4 Create the user menu Copy template role with PFCG Add search capability Add create and maintain capability EXERCISE 5 Use the newly created scenario Search for manufacturers Create a new manufacturer Use Change Request inbox for processing Observe how processing continues EXERCISE 3 Create process configuration Create Business Activity Create change request type Assign processor to change request steps 2012 SAP AG. All rights reserved. 19

18 User Interface Entry Point 2012 SAP AG. All rights reserved. 20

19 UI Configuration In this customizing activity, you manage UI configurations, which the system uses for the definition of the Web user interface for individual processing of an entity: Web Dynpro application USMD_ENTITY_VALUE2 You can create and edit various UI configurations for each data model. Within a UI configuration, you define variants for every entity type, which is changeable via change request. A variant must have exactly the same identification as the entity type for which is used SAP AG. All rights reserved. 21

20 Exercise Used UI Configuration / FPM Components (1) Web Dynpro application USMD_ENTITY_VALUE2 Object Instance Floorplan 2012 SAP AG. All rights reserved. 23

21 Exercise Used UI Configuration / FPM Components (2) Object Instance Floorplan with UI components (here: Form UIBB) 2012 SAP AG. All rights reserved. 24

22 Exercise Used UI Configuration / FPM Components (3) UI Component Form UIBB With UI elements for the exercise 2012 SAP AG. All rights reserved. 25

23 Demo

24 Fundamental Steps to Configure a Governance Scenario EXERCISE 1 Create data model Create entity type and attribute for Car Manufacturer EXERCISE 2 Create UI configuration Start FPM tools Copy template Link UI configuration to data model Create new form Create Layout EXERCISE 4 Create the user menu Copy template role with PFCG Add search capability Add create and maintain capability EXERCISE 5 Use the newly created scenario Search for manufacturers Create a new manufacturer Use Change Request inbox for processing Observe how processing continues EXERCISE 3 Create process configuration Create Business Activity Create change request type Assign processor to change request steps 2012 SAP AG. All rights reserved. 27

25 Process Configuration Entry Point 2012 SAP AG. All rights reserved. 28

26 The Change Request Process CR process defined by Configuration of CR Type Change Request Process Workflow Template Or: configuration of rule-based workflow Change Request Step 0 Submit Change Request Step 1 Initial Approve Change Request Step 2 Process: Enhance Data Part 1 Change Request Step 3 Process: Enhance Data Part 2 Change Request Step 4 Final Approve Assignment of processors to CR steps by configuration Change Request Step Type Change Request Step Type Approve Process 2012 SAP AG. All rights reserved. 29

27 Exercise Used Change Request Process Workflow template WS provides configurable change request process Request Again CR Step 00 Request Submit CR Step 01 Processing Send for Revision Complete Processing CR Step 03 Revision Reject CR Step 02 Final Check Undo Approve Workflow template Change request process END <Action> Legend <Change Request Step> 2012 SAP AG. All rights reserved. 30

28 Exercise Important Properties of Change Request Type CR Type Data Model Description Single Object Main Entity Type Workflow Template 2012 SAP AG. All rights reserved. 31

29 Exercise Important Properties of Change Request Type UI Configuration Entity Type 2012 SAP AG. All rights reserved. 32

30 Exercise Important Properties of Processor Assignment CR Step Processor CRType 2012 SAP AG. All rights reserved. 33

31 Demo

32 Fundamental Steps to Configure a Governance Scenario EXERCISE 1 Create data model Create entity type and attribute for Car Manufacturer EXERCISE 2 Create UI configuration Start FPM tools Copy template Link UI configuration to data model Create new form Create Layout EXERCISE 4 Create the user menu Copy template role with PFCG Add search capability Add create and maintain capability EXERCISE 5 Use the newly created scenario Search for manufacturers Create a new manufacturer Use Change Request inbox for processing Observe how processing continues EXERCISE 3 Create process configuration Create Business Activity Create change request type Assign processor to change request steps 2012 SAP AG. All rights reserved. 35

33 NWBC Menu is defined in transaction PFCG NetWeaver Business Client - Menu Menu defined in TA PFCG 2012 SAP AG. All rights reserved. 36

34 MDG application for search USMD_ENTITY_SEARCH Search object per data model Menu entry for USMD_ENTITY_SEARCH Parameters: PROCESS Business activity, used to determine data model and object 2012 SAP AG. All rights reserved. 37

35 MDG application to create change request and process object USMD_ENTITY_VALUE2 Change Request and object maintenance on one UI Menu entry for USMD_ENTITY_VALUE2 Parameters: PROCESS Business activity, used to determine data model and object IS_CREQ_MODE Flag X to have change request and object on one UI 2012 SAP AG. All rights reserved. 38

36 Demo

37 Fundamental Steps to Configure a Governance Scenario EXERCISE 1 Create data model Create entity type and attribute for Car Manufacturer EXERCISE 2 Create UI configuration Start FPM tools Copy template Link UI configuration to data model Create new form Create Layout EXERCISE 4 Create the user menu Copy template role with PFCG Add search capability Add create and maintain capability EXERCISE 5 Use the newly created scenario Search for manufacturers Create a new manufacturer Use Change Request inbox for processing Observe how processing continues EXERCISE 3 Create process configuration Create Business Activity Create change request type Assign processor to change request steps 2012 SAP AG. All rights reserved. 40

38 Demo

39 What s new in SAP Master Data Governance? SAP MDG 6.1 ramp-up by September 2012 Increased Data Model Coverage for Material, Customer and Supplier Enhanced Application Foundation facilitating integration and configuration Improved Data Quality through seamless analytics and remediation Material Data Model, additional coverage Basic data extension, Plant data, Sales Org / Distribution Channel data, Valuation data, Tax Classification data and Long Texts. Customer Data Model, additional coverage Partner Functions, Dunning Areas, Withholding Tax Types, Sales Area Data, Tax Indicators and Company Code Data Supplier Data Model, additional coverage Partner Functions, Dunning Areas, Withholding Tax Types and Purchasing Org Data 2 Business Partner enhancements Person / Group data (in addition to organizations), Relationships, Contact Partners Integration improvements Inbound processing of Material master data via Enterprise Services for enhanced data model Data quality remediation through integration with Information Steward or other 3 rd party services Support of client maintenance for suppliers via Supplier Lifecycle Collaboration (SLC) Configuration improvements Definition of Governance Scope: remove or add entity types / attributes 2012 SAP AG. All rights reserved. 42

40 Feedback Please complete your session evaluation for EIM264 Thanks for attending this SAP TechEd session.