Enterprise Data Management with SAP NetWeaver MDM

Bonn � Boston

Andrew LeBlanc

Enterprise Data Management with SAP® NetWeaver MDMBuild Foundations for Continual Improvements with SAP NetWeaver MDM

00____EnterpriseSAP_115.book Seite 3 Dienstag, 6. November 2007 6:09 18

Contents at a Glance

1 The Importance of an EDM Strategy .................................. 31

2 Challenges and Approaches to Your EDM Strategy ........... 61

3 The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture ........................... 79

4 EDM Assessment Scorecard ............................................... 103

5 Company Business Strategy Integration ............................ 121

6 Data Quality Management ................................................. 169

7 Design: Data Architecture .................................................. 223

8 Design: Data Standards ...................................................... 275

9 Governance Organization ................................................... 305

10 Governance Processes ........................................................ 327

11 Realization: Deployment .................................................... 349

12 Realization: Technology ...................................................... 385

13 Building an EDM Program .................................................. 479

14 EDM for Materials .............................................................. 503

15 EDM for a Large ERP or Enterprise Application Project ..... 527

16 Globalization Within an EDM Strategy .............................. 543

17 The Future of Enterprise Data Management ...................... 557

A References ........................................................................... 565

B Glossary .............................................................................. 567

C Author Biography ................................................................ 575


www.sappressbooks.com

7

Contents

Acknowledgments ..................................................................................... 21

Preface ...................................................................................................... 23

SECTION I

1 The Importance of an EDM Strategy ................................... 31

1.1 The Many Facets of Master Data ............................................ 331.1.1 A Simple Definition .................................................... 331.1.2 Principle or Primary Objects: SPACE ........................... 341.1.3 DNA of Decision Making ........................................... 341.1.4 What Master Data Is Not ........................................... 35

1.2 The Consequences of Haphazard Management of Enterprise Data ............................................. 361.2.1 Lack of Accurate Knowledge of Your Own Business .... 371.2.2 Supply Chain and Internal Operational Inefficiencies... 371.2.3 Cost Avoidance .......................................................... 381.2.4 Data Security Breaches ............................................... 39

1.3 The History of Master Data ..................................................... 401.3.1 The Growth of Packaged Enterprise Applications ........ 401.3.2 The Development of Component & Supplier

Management (CSM) ................................................... 401.3.3 The Push Toward Upgrades and Conversions for Y2K.... 411.3.4 The Rise of Master Data Management as a Function ... 411.3.5 Online Marketplaces, Catalog Management,

Buy-Side, Sell-Side, and Maintenance Repair and Operations (MRO) Materials ............................... 42

1.3.6 The Post-Internet Commerce Boom ........................... 421.3.7 SAP’s Holistic Approach to Master Data

Management (MDM) ................................................. 431.3.8 Moving Forward to Enterprise Information

Management (EIM) .................................................... 441.4 Classification of Data .............................................................. 441.5 Master Data Versus Enterprise Data ....................................... 461.6 EDM Scenarios ....................................................................... 48

1.6.1 MDM IT Scenarios ..................................................... 481.6.2 MDM Business Scenarios ........................................... 511.6.3 Other Business Value Problems .................................. 53



Contents

8

1.7 Joint ASUG\EDM Survey: The Need for a Comprehensive Data Management Approach ......................... 55

1.8 EDM Framework .................................................................... 561.9 Summary ................................................................................ 58

2 Challenges and Approaches to Your EDM Strategy ............ 61

2.1 Factors to Consider When Developing an EDM Project ........... 612.1.1 Project Design ........................................................... 622.1.2 Organization .............................................................. 622.1.3 Resource Constraints .................................................. 632.1.4 External Drivers .......................................................... 64

2.2 Typical Approaches or Compelling Events ............................... 642.3 Common Pitfalls in EDM ........................................................ 66

2.3.1 Company Business Strategy Integration ...................... 672.3.2 Data Quality Management ......................................... 692.3.3 Design: Data Architecture and Data Standards ............ 712.3.4 Governance Organization and Governance Process ..... 732.3.5 Realization: Deployment and Technology ................... 74

2.4 Summary ............................................................................... 76

3 The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture ................... 79

3.1 Benefits of Enterprise SOA ...................................................... 793.2 Basics of Enterprise SOA ......................................................... 813.3 Interaction of Enterprise SOA and Master Data ...................... 813.4 Basic Requirements for Enterprise Services ............................. 833.5 Business Objects in Enterprise SOA ........................................ 853.6 Anatomy of an Enterprise Service ........................................... 863.7 The Enterprise SOA Metamodel .............................................. 873.8 GDTs in Enterprise SOA .......................................................... 933.9 Business Object Structures in Enterprise SOA ......................... 953.10 Other Critical Enterprise Data Issues ....................................... 97

3.10.1 Decoupling Layers in Enterprise SOA ......................... 983.10.2 Increased Requirements for Business Object

Design Governance .................................................... 983.10.3 Designing Business Object States ............................... 993.10.4 System of Record (SOR) Management ........................ 993.10.5 Managing Metadata ................................................... 99



Contents

9

3.11 Recommendations for Managing Enterprise Data in Preparation for Enterprise SOA ............................................... 100

3.12 Summary ................................................................................ 102

4 EDM Assessment Scorecard ................................................. 103

4.1 Assessment Benefits ............................................................... 1034.1.1 General Benefits of an EDM Assessment .................... 1034.1.2 Benefits of Enterprise Application Implementation

Projects ...................................................................... 1044.1.3 Benefits for Overall Corporate Knowledge

and Enterprise Architecture ........................................ 1044.2 As-Is EDM Assessment Process ............................................... 1054.3 Preparing for the Assessment .................................................. 106

4.3.1 Standard Interview Questions .................................... 1064.3.2 Requests for Information ............................................ 1074.3.3 Cataloging Documents ............................................... 1084.3.4 Gathering Findings ..................................................... 1094.3.5 General Guidelines on EDM Assessment Meetings...... 1104.3.6 Guidelines for Assessments ........................................ 111

4.4 EDM Best Practices ................................................................ 1124.5 Scoring Your Company Against EDM Strategy Best Practices ... 1144.6 Sample Summary Results ........................................................ 1154.7 Detailed Assessment Results ................................................... 1164.8 Summary ................................................................................ 117

SECTION II

5 Company Business Strategy Integration ............................. 121

5.1 Company Business Strategy Basics .......................................... 1215.1.1 Corporate Strategy Inputs to an EDM Program............ 1225.1.2 Components of the Company Business

Strategy Integration ................................................... 1235.2 The EDM Program Charter ...................................................... 123

5.2.1 Vision ........................................................................ 1255.2.2 Mission ...................................................................... 1255.2.3 Strategic Objectives ................................................... 125

5.3 The EDM Program Business Case ............................................ 1265.3.1 Definition of a Business Case ...................................... 127



Contents

10

5.3.2 Pain Points: Examples of Issues for the Current Situation ............................................ 129

5.3.3 Business Benefits in a Business Case ........................... 1305.3.4 Qualitative Benefits .................................................... 1315.3.5 Quantitative Benefits ................................................. 1345.3.6 Building a Financial Model ......................................... 1395.3.7 Putting it Together: Building Your Story ..................... 145

5.4 EDM Program Design Guidelines ............................................ 1505.4.1 Sample Design Rules .................................................. 1515.4.2 Strategic Direction ..................................................... 1535.4.3 Executive Intent ......................................................... 1545.4.4 Principles to Determine Program Scope ..................... 1545.4.5 Domain-Specific Guidelines ....................................... 155

5.5 EDM Program Scope .............................................................. 1565.5.1 Domains in Scope ...................................................... 1575.5.2 Objects in Scope ........................................................ 1575.5.3 Attributes in Scope .................................................... 1585.5.4 Other Scoping ............................................................ 1585.5.5 Grouping Objects in Scope

into Primary and Secondary Objects ........................... 1595.6 EDM Program Policy .............................................................. 161

5.6.1 A Sample EDM Policy Guideline ................................. 1615.6.2 Security and Compliance ............................................ 1665.6.3 Training and Awareness ............................................. 167

5.7 Summary ................................................................................ 167

6 Data Quality Management .................................................. 169

6.1 Introduction to Six Sigma Quality Management ...................... 1706.1.1 The Term Sigma in Statistics ....................................... 1706.1.2 The Six Sigma Quality Management

Program Definition .................................................... 1716.1.3 Important Foundation Concepts for Six Sigma............. 1716.1.4 Five Standard Steps of Six Sigma ................................ 1726.1.5 The Most-Used Tools Within a Six Sigma

Quality Management Program ................................... 1736.1.6 Classifying Data Quality Defects ................................. 174

6.2 The Elements of the Data Quality Management Dimension .... 1756.3 Define .................................................................................... 177

6.3.1 Leveraging Other Dimensions for the Define Component ......................................... 177

6.3.2 Requirements for Good Quality Data ......................... 178



Contents

11

6.3.3 Determining Good Data Quality Rules ....................... 1806.3.4 General Requirements for Developing Metrics ............ 1816.3.5 Scoping: Selecting Where to Measure ........................ 183

6.4 Measure ................................................................................. 1876.4.1 Column Property Analysis .......................................... 1886.4.2 Data Profiling ............................................................. 1896.4.3 Link to Data Standard ................................................ 1906.4.4 Data Analysis Test Plan .............................................. 1906.4.5 Testing General Rules ................................................. 1916.4.6 Testing Complex Rules ............................................... 1926.4.7 Testing Style Rules ..................................................... 192

6.5 Analyze .................................................................................. 1936.5.1 Data Quality Reports ................................................. 1936.5.2 Sample Data Quality Metrics ...................................... 1956.5.3 Relating Data Quality Metrics to Business Metrics....... 2026.5.4 Data Quality Scorecard .............................................. 2056.5.5 Tools for the Analyze Step for the Data Quality

Management Program ............................................... 2096.5.6 Determining Where to Focus ..................................... 2106.5.7 Determining Root Causes ........................................... 211

6.6 Improve .................................................................................. 2126.6.1 Steps Involved During the Improve Phase .................. 2126.6.2 Tools and Other Options to Fix Quality Defects .......... 213

6.7 Control ................................................................................... 2146.7.1 Control for Common Issues ........................................ 2156.7.2 Understanding External

Requirements and Regulations ................................... 2166.7.3 Developing the Controls Framework .......................... 2166.7.4 Determining Applicable Technology Controls ............. 2196.7.5 Identifying Additional Control Needs ......................... 2206.7.6 Creating Plans to Address Control Needs ................... 220

6.8 Summary ................................................................................ 220

7 Design: Data Architecture .................................................... 223

7.1 General Enterprise Architecture .............................................. 2237.1.1 Elements of All Enterprise Architectures ..................... 2247.1.2 Common Enterprise Architecture Frameworks (EAFs).... 225

7.2 Components of the Data Architecture EDM Dimension .......... 2297.3 Business Process Integration ................................................... 230

7.3.1 Benefits of Business Process Integration ..................... 234



Contents

12

7.3.2 Creating and Maintaining the Business Process Integration ............................... 235

7.4 Enterprise Data Distribution Approach ................................... 2377.4.1 General Factors to Consider When Developing and

Choosing an Enterprise Data Distribution Approach.... 2427.4.2 Sample Specific Company Enterprise

Data Distribution Approach Requirements ................. 2437.4.3 Other Technical Considerations .................................. 244

7.5 Enterprise Data Model ............................................................ 2457.5.1 The Enterprise Data Model Structure ......................... 2457.5.2 Data Domains, Attributes, Elements, and Values......... 2467.5.3 Business Value of the Enterprise Data Model ............. 2487.5.4 Existing Enterprise Conceptual Data Model ................ 250

7.6 Logical Data Model (LDM) ..................................................... 2527.6.1 Business Value of the Domain Logical Data Model...... 2547.6.2 Workforce Logical Data Modeling Process ................. 2557.6.3 Material Master for Parts Logical Data Model ............. 259

7.7 Application Architecture ......................................................... 2607.7.1 Assumptions .............................................................. 2627.7.2 Example Company Vision for Workforce

Management Master Data ......................................... 2637.7.3 Example Technical Releases for a Domain .................. 2647.7.4 Sample Workforce Management Application

Architecture Project Releases ..................................... 2667.8 Source and Target Mapping Model ......................................... 268

7.8.1 Business Value of Source and Target Mapping............. 2717.8.2 Alternative Source and Target

Mapping Model formats ............................................ 2717.9 Summary ................................................................................ 273

8 Design: Data Standards ....................................................... 275

8.1 The Concept of Global Data Types .......................................... 2758.2 Data Standards EDM Dimension Components ....................... 2778.3 Business Object Definitions .................................................... 278

8.3.1 Sample Format of the Business Object Definition ........ 2788.3.2 Using the Business Object Definition .......................... 280

8.4 Data Dictionary ...................................................................... 2808.4.1 Process to Develop Data Standards ............................ 2818.4.2 Sample Data Standard Format .................................... 2828.4.3 Data Dictionary from Standard SAP ............................ 2838.4.4 Using the Data Dictionary .......................................... 285



Contents

13

8.5 Schema Standards .................................................................. 2858.5.1 Schema or Hierarchy Basics ........................................ 2858.5.2 Defining Schema Standards in Relation to EDM .......... 2888.5.3 Schema Business Value .............................................. 2898.5.4 Sample Organization Schema Standard ...................... 2908.5.5 Applying a Schema Strategy ....................................... 296

8.6 System of Record (SOR) .......................................................... 2978.6.1 Purpose of the SOR Component ................................ 2978.6.2 Creating the SOR ...................................................... 2988.6.3 Sample SOR ............................................................... 2998.6.4 Recommended SORs for Schemas .............................. 3018.6.5 Business Value of the SOR ......................................... 303

8.7 Summary ................................................................................ 303

9 Governance Organization ..................................................... 305

9.1 Organization Structure Concepts ............................................ 3059.1.1 SAP Organization Structure Terminology .................... 3059.1.2 Key Concepts of Organization Design ........................ 3079.1.3 Considerations when Establishing

a Governance Organization Structure ......................... 3079.2 Components of the Governance Organization ......................... 3089.3 Enterprise Data Governance Organization ............................... 310

9.3.1 Standard Enterprise Data Governance Organization Roles ..................................................... 310

9.3.2 Enterprise Data Governance Organization Structure .... 3119.3.3 Enterprise Data Governance Position Descriptions ...... 315

9.4 Business Data Organization .................................................... 3159.4.1 Business Data Organization Roles .............................. 3179.4.2 Central versus Decentralized

Business Data Organization Structure ......................... 3189.4.3 Business Data Organization Structures ....................... 3209.4.4 Business Data Organization Position Descriptions ....... 324

9.5 Summary ................................................................................ 324

10 Governance Processes .......................................................... 327

10.1 SAP Process Decomposition ................................................... 32710.2 EDM Governance Process Types ............................................. 32910.3 Business Data Processes ......................................................... 330

10.3.1 Standard Elements of Business Data Processes ............ 331



Contents

14

10.3.2 Examples of Business Data Processes .......................... 33310.3.3 Additional Considerations for

Business Data Processes ............................................. 33810.4 Enterprise Data Governance Processes .................................... 338

10.4.1 Standard EDM Services .............................................. 33910.4.2 Enterprise Data Governance

Change Request Process ............................................. 34410.5 Summary ................................................................................ 347

11 Realization: Deployment ...................................................... 349

11.1 EDM and ASAP Implementation Methodology ....................... 35011.1.1 ASAP Basics ............................................................... 35011.1.2 Typical Data Issues with ASAP Projects ...................... 350

11.2 Elements of the Deployment EDM Dimension ........................ 35311.3 Change Management .............................................................. 354

11.3.1 Overview ................................................................... 35411.3.2 A Model for Organization Transformation .................. 35511.3.3 Transforming the Organization ................................... 35611.3.4 Suggestions for Creating and Communicating

the Message .............................................................. 35711.3.5 Relating Change Management to Your

EDM Program ............................................................ 35811.4 Standard Project Plans ............................................................ 359

11.4.1 EDM Strategy Development ....................................... 35911.4.2 MDM Tool Data Repository Implementation ............. 36011.4.3 MDM Roadmap Development Plan ........................... 36111.4.4 Data Migration and Cleansing Implementation Plan.... 362

11.5 Data Migration and Cleansing ................................................. 36311.5.1 Common Terminology ................................................ 36311.5.2 Process Overview ....................................................... 36511.5.3 Approach ................................................................... 36611.5.4 Outsourcing versus In-House

Data Migration and Cleansing .................................... 36811.6 Managing EDM Data Design Documents ................................ 370

11.6.1 Design Document Style Guide .................................... 37011.6.2 Design Document Repository

in SAP Solution Manager ........................................... 37011.7 EDM-Related Business Standards ............................................ 372

11.7.1 SAP Current Approach for Business Standards ............. 37311.7.2 Benefits and Business Value of Adopting

Business Standards ..................................................... 373



Contents

15

11.8 Special Deployment Issues ...................................................... 37411.8.1 Integration to Business Intelligence (BI) Strategy......... 37411.8.2 Globalization ............................................................. 37711.8.3 Regulatory Considerations .......................................... 37711.8.4 Security Plan Requirements ........................................ 380

11.9 Summary ............................................................................... 384

12 Realization: Technology ....................................................... 385

12.1 EDM Reference Technical Architecture ................................... 38612.2 Components of the Realization:

Technology EDM Dimension .................................................. 38812.3 EDM-Related Technology Functions Reference List ................ 38912.4 EDM-Related Applications Inventory ...................................... 394

12.4.1 SAP ERP and Other Enterprise Applications ............... 39512.4.2 Reverse Business Engineer (RBE) ................................ 39612.4.3 Legacy System Migration Workbench (LSMW)............ 39812.4.4 SAP NetWeaver Process Integration (PI) .................... 40012.4.5 SAP Composition Environment (CE) ........................... 40112.4.6 SAP Solution Manager ............................................... 40312.4.7 SAP NetWeaver System Landscape Directory (SLD)..... 40512.4.8 ARIS for NetWeaver and Other

Enterprise Architecture Tools .................................... 40712.4.9 SAP Solution Composer ............................................. 41012.4.10 Business Object Repository (BOR) Browser ................ 41212.4.11 Enterprise Services Workplace (ESW) ......................... 41412.4.12 SAP NetWeaver Business Intelligence (BI) ................. 41512.4.13 SAP Enterprise Services Repository (ESR) ................... 417

12.5 Data Profiling Requirements and Evaluation .......................... 41912.5.1 Basic Features of a Data Profiling Tool ....................... 41912.5.2 Standard Analyses for Data Profiling Tools ................. 42012.5.3 Analytical Methods for Data Profiling ......................... 42112.5.4 SAP and Other Data Profiling Tools ............................ 422

12.6 EDR Requirements and Evaluation .......................................... 42212.6.1 General Capabilities Recommended for an SAP EDR ... 42312.6.2 Capabilities Not Recommended for Use

for the Company EDR ................................................ 42512.6.3 Important Factors to Consider When Developing

and Choosing EDR Options ........................................ 42712.6.4 Standard Features of an EDR ...................................... 42812.6.5 Options for an EDR ................................................... 430



Contents

16

12.7 SAP NetWeaver MDM Basics ................................................. 43312.7.1 Basic Modules of the SAP NetWeaver MDM Tool ....... 43412.7.2 EDR Specifically in SAP NetWeaver MDM .................. 43712.7.3 The MDM Console Main Functions ............................ 43912.7.4 Functions of the MDM Repository ............................. 43912.7.5 MDM Data Manager Modes ...................................... 44112.7.6 MDM Data Field Types .............................................. 44112.7.7 Basics of Taxonomies and Attributes .......................... 44312.7.8 SAP NetWeaver MDM Repository Table Types ........... 443

12.8 EDR Modeling Using an SAP NetWeaver MDM Repository .... 44512.8.1 Designing LDMs with SAP NetWeaver MDM ............. 44612.8.2 Sample LDM Using SAP NetWeaver MDM ................ 45312.8.3 Checking Rules in SAP NetWeaver MDM:

Validations ................................................................. 45712.8.4 Designing a Taxonomy ............................................... 45812.8.5 Leveraging SAP-Supplied Repositories for

ERP and Other Enterprise Application Integration....... 46012.9 SAP NetWeaver MDM Advanced Technical

Infrastructure Topics ............................................................... 46412.9.1 Sizing SAP NetWeaver MDM ..................................... 46412.9.2 Master and Slave Repositories .................................... 46512.9.3 Solution Landscape for SAP NetWeaver MDM............ 46612.9.4 Building Workflow for SAP NetWeaver

MDM Processes ......................................................... 46912.9.5 SAP NetWeaver MDM Backups and Archiving ............ 47012.9.6 Portal Integration ....................................................... 47112.9.7 SAP NetWeaver BI Integration ................................... 47212.9.8 Users and Authorization ............................................. 47212.9.9 Collaboration Through Locking and Version Control.... 47312.9.10 Security in SAP NetWeaver MDM .............................. 473

12.10 Technology Recommendations for EDM Dimensions and Components ........................................................................... 475

12.11 Summary ............................................................................... 475

SECTION III

13 Building an EDM Program ................................................... 479

13.1 Common Approaches for EDM Projects .................................. 47913.2 Beginning with the End in Mind ............................................. 480

13.2.1 Ideal Sequence for Applying the EDM Methodology ... 482



Contents

17

13.2.2 Expectations of an EDM Strategy Project ................... 48313.2.3 Enterprise-wide versus

Domain-Specific Deliverables...................................... 48313.2.4 Sequence of Successive Projects

to Achieve a Sustainable EDM Program ..................... 48613.3 MDM Roadmap Program Plan ................................................ 486

13.3.1 Project Team Organization ......................................... 48713.3.2 Project Roles and Responsibilities .............................. 48813.3.3 Special Considerations for Project Deliverables ........... 48813.3.4 Watch Items .............................................................. 489

13.4 Independent EDM Strategy Projects ....................................... 48913.4.1 Project Team Organization ......................................... 49013.4.2 Project Roles and Responsibilities .............................. 49113.4.3 Project Team Communications ................................... 49213.4.4 Special Considerations for Deliverables ...................... 49213.4.5 Watch Items .............................................................. 493

13.5 Support Large Enterprise Application Implementation ............ 49413.5.1 Project Team Organization ......................................... 49413.5.2 Project Roles and Responsibilities .............................. 49513.5.3 Special Consideration for Deliverables

in Blueprinting ........................................................... 49613.5.4 Watch Items .............................................................. 496

13.6 Focused Internal Business Objective ....................................... 49713.6.1 Project Team Organization ......................................... 49713.6.2 Project Roles and Responsibilities .............................. 49813.6.3 Special Considerations for Deliverables ...................... 49913.6.4 Watch Items .............................................................. 499

13.7 Commercial Initiatives ............................................................ 50013.7.1 Project Team Organization ......................................... 50013.7.2 Project Roles and Responsibilities .............................. 50113.7.3 Special Considerations for Deliverables ...................... 50113.7.4 Watch Items .............................................................. 501

13.8 Summary ............................................................................... 501

14 EDM for Materials ................................................................ 503

14.1 Introduction to Direct Materials ............................................. 50414.1.1 Definition and Variants in Industry ............................. 50414.1.2 Types of Direct Materials ........................................... 50414.1.3 Typical Products and Their Metrics ............................. 50714.1.4 Leverage of Product Design ....................................... 508



Contents

18

14.2 Major Roles in Direct Materials .............................................. 50814.3 Typical Product Development Process .................................... 51014.4 General MRO Items versus Direct Materials ............................ 51214.5 Defining World-Class Direct Materials Content ....................... 514

14.5.1 Required Content Features ......................................... 51414.5.2 Should Have Content Features ................................... 51514.5.3 Nice to Have Content Features ................................... 516

14.6 Bottlenecks to Efficient Materials Management ...................... 51714.6.1 Synchronizing Catalog Items

to the Solid Model and to Specification Documents.... 51714.6.2 Mapping Engineering Specifications to

the Manufacturer and to the Supplier ........................ 51814.6.3 Seamless Guided Searching from Individual

out to Open Internet ................................................. 51914.6.4 Product Data Interoperability ..................................... 52014.6.5 Coordinating the Manufacturing and Design BOMs .... 52114.6.6 Part Renumbering ...................................................... 52214.6.7 Managing Direct Materials Data Structures ................ 524

14.7 Summary ................................................................................ 525

15 EDM for a Large ERP or Enterprise Application Project ...... 527

15.1 Case Study Background Information ....................................... 52715.1.1 Case Study Company .................................................. 52715.1.2 Project Objective ....................................................... 52815.1.3 EDM Involvement ...................................................... 528

15.2 ERP Project Organization ........................................................ 52815.3 Interfacing with Vertical Workstreams .................................... 530

15.3.1 Vertical Workstream Coordinator Role ....................... 53015.3.2 Information Collected by Vertical Workstream

Coordinators .............................................................. 53115.3.3 EDM Team Assignments: EDM Core Team

to Vertical Workstreams ............................................. 53215.3.4 Responsibilities Between the Horizontal EDM Team

and Vertical Workstreams .......................................... 53315.3.5 Involvement of Vertical Workstreams

by Master Data Object ............................................... 53515.4 EDM Project Deliverables ....................................................... 536

15.4.1 Shared Deliverables ................................................... 53615.4.2 EDM Team Deliverables ............................................ 537

15.5 EDM Team Involvement in ERP Project Workshops ................ 538



Contents

19

15.5.1 Assumptions and Preparation ..................................... 53915.5.2 Grouping the ERP Implementation Workshops

in Terms of EDM Impact ............................................ 53915.5.3 Mapping Deliverables to Cycles ................................. 540

15.6 Conclusion and Recommendations ......................................... 54115.7 Summary ................................................................................ 542

16 Globalization Within an EDM Strategy ............................... 543

16.1 Issues to Consider ................................................................... 54316.2 Types of Globalization Conversions ......................................... 54416.3 Language Master Data in SAP Applications ............................. 545

16.3.1 Attributes to Consider When Examining Globalization 54516.3.2 Master Data Language Limitations in SAP tools........... 54616.3.3 Employee Master Data Example ................................. 54616.3.4 Example of Language-Dependent Objects in SAP

Applications ............................................................... 54716.4 Typical Options for Globalization and Language ..................... 548

16.4.1 Best Practices for Localization .................................... 55016.4.2 Globalization Strategy ................................................ 551

16.5 Conclusion and General Recommendations ............................ 55416.6 Summary ................................................................................ 555

17 The Future of Enterprise Data Management ....................... 557

17.1 Business and Technology Drivers ............................................ 55717.2 Increased Mergers, Acquisitions, and Partnerships .................. 55817.3 Increased Scorecards and Metrics ........................................... 55817.4 Increased Awareness of the Impact of Data Quality ................ 55917.5 Enterprise Service-Oriented Architectures ............................... 55917.6 Enterprise Architecture ........................................................... 56017.7 Business Process Management (BPM) ..................................... 56117.8 Summary ................................................................................ 561

Appendix .................................................................................... 563

A References ........................................................................................ 565B Glossary ............................................................................................ 567C Author Biography .............................................................................. 575

Index ......................................................................................................... 577



79

Enterprise data is a critical foundation for mastering and scaling an enterprise service-oriented architecture (enterprise SOA). You must know a few key concepts to prepare for this future architecture.

3 The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture

Well-managed enterprise data is critical to Service Oriented Architecture(SOA) strategies such as enterprise service-oriented architecture (enterpriseSOA). In this chapter, we will briefly cover enterprise SOA and the followingconcepts that you must know to begin to prepare for enterprise SOA:

� Enterprise Services basics focusing in on data

� Anatomy of a business object (BO) for enterprise SOA

� Importance of global data types

� Other concepts, such as BO lifecycle status, and managing Systems ofRecord (SORs)

First, let’s examine the benefits of enterprise SOA, balancing the ability to beagile with continuous innovation while controlling costs.

3.1 Benefits of Enterprise SOA

The vision of enterprise SOA is to help your company both innovate andreact quickly to market forces while still controlling costs. Traditional meth-ods provide many benefits, but to separate yourself from the competition inthe future, you can take advantage of these benefits. Enterprise SOA is oneway for you to achieve that goal for innovation, faster reaction time, andcontrolling technology costs. Figure 3.1 shows a general diagram of an enter-prise SOA application.



The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture3

80

Figure 3.1 General Diagram of an Enterprise SOA Application

The following are some external drivers motivating companies like yours topursue enterprise SOA:

� Need to differentiateTo compete and remain profitable, competing on cost is not enough. Youmust continually differentiate your business by focusing on your corecompetencies.

� Total customer offering requirementProviding a standalone product is not enough. Customers require a totalexperience with your product, including services for the product. WhenApple developed the iPod, they not only thought about the music player,but the entire value chain of services around it.

� Information overloadYou have a lot of data in your company. It is important to aggregatedisparate information and to be able find the right information todetermine trends and react more quickly.

Legacy3rd

Legacy3rd

Party

SAP NetWeaverBusiness Process Platform

PlatformProcess Components

PlatformProcess Components

Composite Applications

PartnerPartner SAPSAP

SAPR/3SAPR/3

EnterpriseServices

Repository

Analytics



Interaction of Enterprise SOA and Master Data 3.3

81

� Growing domestic and international regulatory compliance mandatesBusinesses must increasingly meet additional regulations for security, pri-vacy, and financial practices. In addition to meeting the standards, youmust prove how you derived the results and that you provide controls toensure that you will meet the standards going forward.

These are some of the business pressures and opportunities that a companymust face. Enterprise SOA provides tools and techniques to respond to thosechallenges while keeping costs under control.

3.2 Basics of Enterprise SOA

Enterprise SOA is how SAP does Web services. SAP has designed enterpriseSOA to be compatible with the industry SOA standards, but went beyondthis to develop an architecture that allows you to leverage your existinginfrastructure and allows you to truly scale SOA in an orderly way. Figure3.2 illustrates business process management with enterprise SOA.

Enterprise SOA is a standard SOA architecture with Enterprise Servicesrather than just building Web services from the ground up. Also, enterpriseSOA is designed to leverage complex landscapes with a mix of packagedapplications, internally developed applications, and Enterprise Services.

3.3 Interaction of Enterprise SOA and Master Data

By referring to the simple model of enterprise SOA shown in Figure 3.3 youcan see the increased requirements for harmonized master data. Enterprisedata needs to be shared across applications and Enterprise Services. In addi-tion, scaling enterprise SOA requires a logical and even possibly physicaldecoupling of master data from the applications. Referring to Figure 3.3, youcan see one landscape comprised of two applications. One business scenariocrosses the two applications and transactions or business documents arebeing passed from one application to another.

For the business documents or transactions to be understood or have propercontext, the master data in both systems must be semantically and possiblyeven structurally equivalent. As a result, the master data in both applicationsmust be harmonized. It is even more efficient if there is just one SOR foreach master data BO. This single SOR is preferred for all business dataobjects.




82

Figure 3.2 Business Process Management with Enterprise SOA

Compose and

Orchestrate

Manage and

Optimize

Integrate and

Deploy

Model and Build

Analyze and

Discover

Enterprise Service

Repository

1

2

3

4

5

1 2

3 4

5

• Analyze business requirements • Identify needed business objects, services, and views • Discover available enterprise services in ESR for reuse • Identify missing services for new business logic

• Compose views by reusing implemented services and BOs• Compose and orchestrate services and views to form new business process

• Manage change & maintain version (governance)• Monitor service execution (e.g. performance, availability, process progress, events)

• Design and model business objects (BOs) • Implement new business logic • Model and build UIs • Create new services reusing existing assets and publish to ESR

• Package and deploy application • Configure runtime (adapt to IT landscape) • Test and validate application • Execute application



Basic Requirements for Enterprise Services 3.4

83

By decoupling the applications from the BOs, you can manage the masterdata and their metadata centrally. With the addition of Enterprise Services,this requirement for standardized master data and enterprise data is evenmore imperative.

Figure 3.3 One Scenario, Two Applications, and Master Data in Enterprise SOA

3.4 Basic Requirements for Enterprise Services

Enterprise Services are Web services with an enterprise-level business value.They are a combination of single Web services combined with business logic.In contrast, Web services are used mainly to work with specific pieces offunctionality. The following are a few of examples of possible EnterpriseServices for Sales Order Processing:

� Read sales order item

� Create sales order

� Change sales order

� Find sales order by buyer and basic data

From a business perspective, “order cancellation” is represented as a Web serv-ice, which we call an “Enterprise Service" in the context of enterprise SOA.

System Landscape

System ASystem A System BSystem B

Business scenario

A business scenario is represented as a flow of business documents (transactional data)

Many business documents reference master data

Business scenarios that are carried out beyond system boundaries need to reference the same master data representations through the process




84

SAP’s literature for enterprise SOA provides the following explanation anddescriptions for Enterprise Services:

Enterprise Services have all of the characteristics of Web services plus addi-tional requirements, and the following characteristics differentiate Enter-prise Services from regular Web services:

� Business semanticsEnterprise Services are structured according to a harmonized enterprisemodel based on process components, BOs and global data types (GDTs).Quality and stability: Enterprise Services ensure a stable interface forfuture versions, providing backward compatibility. Their behavior, pre-requisites, dependencies of usage, and configuration possibilities are welldocumented.

� StandardsEnterprise services are based on open standards. The interfaces aredescribed according to the Web Services Description Language (WSDL).WSDL is the industry standard for defining Web services. They are createdby using GDTs, which are based on the United Nations CEFACT standardsorganization Core Component Technical Specification (CCTS) standard.

SAP literature recommends that large enterprise customers adopt the currentrelease of the SAP ECC ERP application. Midsize customers should start withan SAP All-in-One solution. The SAP NetWeaver platform powers both solu-tions.

An enterprise SOA-compatible landscape enables customers to extend theirbusiness solutions quickly and easily to meet their unique needs. Customerswill still rely on the existing and stable functionality provided by SAP solutions.To fulfill a specific industry requirement or business need, you could takeadvantage of Enterprise Services provided by SAP or strategic business part-ners through the Enterprise Services Workplace (ESW), as shown in Figure 3.4.With these Enterprise Services, customers can rapidly enhance their existingbusiness processes or develop and deploy new applications to handle specificbusiness processes. This extends and increases the value of SAP solutions.

An example of packages of Enterprise Services is the electronic bill present-ment and payment (EBPP) Enterprise Services bundle. It bundles EnterpriseServices that support authorization with settlement processes that are usedto communicate with credit card processors. Any company that handles busi-ness-to-consumer interactions that require credit card authorization and pay-ments can take advantage of these Enterprise Services.



Business Objects in Enterprise SOA 3.5

85

Figure 3.4 Discovering Enterprise Services in the Enterprise Services Workplace (ESW)

3.5 Business Objects in Enterprise SOA

In enterprise SOA, a BO represents a specific view on well-defined businesscontent. This business content is generally accepted and well known in thebusiness world. At the highest level in enterprise SOA, BOs are classified intotwo groups:

For More Information

If you are an SAP customer, you can find information about service-enabled sce-narios on the ESW and on an interactive Wiki, which are both hosted on SDN(www.sdn.sap.com). For more information on ESW, see “What Is ES Workplace?”General information about service-enabled scenarios is available on the EnterpriseServices Wiki (www.sdn.sap.com/irj/sdn/share-bp), along with detailed documen-tation of the services offered for specific scenarios. Because the Enterprise ServicesWiki allows users to add and edit content collectively, it promotes content sharingamong a community of SAP developers, customers, and partners using EnterpriseServices to integrate, compose, and deploy applications.

Enterprise Architect

Wiki)

Business Process Expert

Applications, e.g.Enhancement Packages

for SAP ERP ECC Hosted System

on SDN

ESR

E S Workplace

•ES Packages •Enterprise Services•Education




86

� Business Process Objects (BPOs)Transactional BOs (time point related).

� Master Data Objects (MDOs)BOs with mainly master data character (time span related).

BO definitions are driven by business relevance. BOs are defined, and storedin the Enterprise Services Repository (ESR), and implemented free of redun-dancies. BO governance process, guidelines, and rules are defined in theESR. Examples of BOs include sales order, supplier invoice, or outbounddelivery. Internal application system tables are not considered BOs. Now,let’s examine the structure of an Enterprise Service, focusing on the enter-prise data or BOs.

3.6 Anatomy of an Enterprise Service

All Enterprise Services have a standard repeatable pattern or structure. Thispattern or structure supports uniformity and a foundation for governance.Following are the standard rules that govern all Enterprise Services:

� BO encapsulationA BO is defined only once. Also, there is no duplication of BOs.

� BO relationship to process componentsA process component contains a set of semantically related BOs.

� Integration scenariosIntegration scenarios model the interaction between process components.

� Service operationA service operation belongs to exactly one BO. One BO has multiple oper-ations.

� Service interfaceA service interface groups service operations together.

� Global data type (GDT)GDTs are reusable elements stored in a common dictionary. Several GDTsform message types.

An Enterprise Service is a callable entity that provides business functionalityand is published by SAP in the ESR. Enterprise Services are structuredaccording to a harmonized enterprise model based on GDTs, process compo-nents, and BOs. They are well documented, guarantee quality and stability,and are based on open standards. The following are additional requirementsfor an Enterprise Service over a Web service:



The Enterprise SOA Metamodel 3.7

87

� Structured according to harmonized enterprise model (process compo-nents, BOs, interface patterns, and GDTs)

� Published in the ESR

� Guaranteed interface stability

� Well-documented contract and behavior

� Based on open standards (WSDL, XML, SOAP, and so on)

Additional usability requirements should be available for Enterprise Services:

� Easy to discover (have a harmonized classification scheme)

� Easy to understand (business language)

� Easy to invoke (based on open standards)

� Have a stable interface and stable behavior (well-defined lifecycle)

Common guidelines and patterns for modeling and implementation ofEnterprise Services make life easier for service consumers, such as businessprocess experts, when they may be designing a new business process foryour company. SAP has already put many product and process standardsinto place that also apply to Enterprise Services.

For Enterprise Services, additional design guidelines and patterns exist ondifferent levels, as follows:

� Map of process components and BOs

� Well-defined service interfaces and service operations per BO

� Structure of message types (signature of service operations)

� Common set of reusable data types

� Transactional behavior at runtime

� Service implementation (business application code)

Now that you have seen the characteristics of Enterprise Services, let’s lookat the pattern or metamodel of enterprise SOA. This describes how Enter-prise Services and enterprise data work within enterprise SOA.

3.7 The Enterprise SOA Metamodel

The enterprise SOA metamodel is the consistent relationship or pattern ofprocesses, services, and BOs. BOs are at the heart of this model. You shouldalso understand several other key entities so that you can grasp the standard




88

pattern of enterprise SOA, and, as a result, the impact of BOs on enterpriseSOA. They include service operations, service interfaces, process compo-nents, and BOs, as shown in Figure 3.5.

Figure 3.5 The Enterprise SOA Metamodel

Service operations logically belong to service interfaces, and service inter-faces belong to process components. Service interfaces adhere to a certainpattern, which makes it more intuitive to quickly find and identify Enter-prise Services. A manage-type interface typically incorporates create, read,update and delete types of service operations. For instance, the Create SalesOrder service operation belongs to the Manage Sales Order service interface,and the Manage Sales Order service interface belongs to the Sales OrderProcessing process component.

Modular, context independent, reusable pieces of software that expose their functionalities as services. Contains, at least,one business object.

Business ObjectModel

1

1..*

0..1

0..1

1..*

1..*1

1..*

*

1..*

*

1references

*

1

Service Description basedon WSDL & XSD

e.g. Sales Price Information

Service

ServiceInterface

Operation

Data Type(Message Type)

Definition:XML Schema

Global Data Types

ProcessComponent

ProcessComponent

e.g. Price MasterData Management

Specific view on well-defined and outlined business content.




89

As a result, the navigation hierarchy is as follows:

� Process components have one or more service interfaces

� Service interfaces have one or more service operations

In enterprise SOA, an application has a logical decomposition to logicaldeployment units to process components to BOs with service interfaces andservice interfaces to service operations, as illustrated in Figure 3.6. Let’s lookin more detail at the concept of logical deployment units.

Figure 3.6 Basic Entities of an Application

Logical Deployment Units

A logical deployment unit is a set of process components that can be operatedon a separate system, isolated from other process components. Importantthings to know about deployment units include the following:

� Different deployment units can be instantiated on different physical systems.

� The deployment unit is not equivalent to the installable entity, which canbe broader.

approved

Due Item Process ing

Due Payment

approved

TradeReceivablesPayables ...

approved

Due Clearing

approved

VATDeclaration

new

TradeReceivablesPayables.. .

approved

Due Item Process ing

Due Payment

approved


approved

Due Clearing

approved

VATDeclaration

new


approved

Due Payment


DueClearing

VATDeclaration


Process component–level two

(drilldown in detailed model)

Business object –

level three

Deployment unit –

level one




90

� With regard to characteristics, in a given customer landscape, the follow-ing can be true about a deployment unit:

� Other software can replace a deployment unit.

� A deployment unit can run in multiple instances and can be connectedto multiple instances of other logical deployment units.

� A deployment unit can be ignored in an application configuration (ifinactive in the current system).

Process Components

Process components can be seen as the building blocks of each enterpriseSOA solution. They are modular, context independent, reusable pieces ofsoftware that expose their functionalities as services (see Figure 3.7). A proc-ess component contains at least one BO.

Figure 3.7 Drilling Down on the Details of a Process Component

derived from derived from Message

Type

Supplier Invoice Cancellation Execution Request

Accounting Cancellation

Request

Invoice

Supplier Invoice Processing

Supplier Invoice

Create Supplier Invoice

Supplier_Invoicing_In

Cancel Supplier Invoice

Global Data

Types

Service Interface

Business Object

Process Component

Service Operation

Message Type




91

The following are typical characteristics of process components:

� Structuring and modeling constructs

� Not tangible entities in the development environment

� Group of BOs at the granularity of a business process to be used as a reuseelement in integration scenarios

� Fit into a typical customer organization

� Belong to exactly one deployment unit (discussed in more detail in thenext section)

BOs

BOs are logical objects of significance to the business. They represent a classof entities with common characteristics and common behaviors describingwell-defined business semantics. BOs are used to model a business process,for example, sales order. The following are characteristics of BOs:

� BOs represent a specific view of well-defined and outlined business content.

� The BO definition is driven by business relevance and SAP experience.

� BO guidelines and rules are defined, including the following key types ofBOs:

� BO purchase order

� BO template: maximal template of product with all attributes, unavail-able for use in the Logical Deployment Unit (LDU)

� Dependent object: substructure of BO to be reused in another BOaddress

� Business foundation object: BO in foundation layer and business partner

� BO identification and all BO models and data types run through a govern-ance process, including review, final approval, and released documenta-tion

� BOs are encapsulated by a process component. In an application, a BO isdefined only once in one process component. A process component candefine one or more BOs.




92

Service Interfaces

A service interface is a named grouping of operations. The service interfacepatterns commonly used are Read, Create, Update, Manage, and Delete.

Service Operations

The highest granularity of an entity type is the service operation. When itcomes to the implementation of a composite application, the business proc-ess expert or the software architect should have the desired single EnterpriseService operations and the orchestration in mind. This is where the devel-oper needs detailed technical information to orchestrate and compose theEnterprise Services.

You can browse the ESW to help you find a particular service operation. Todo so, find and display the WSDL for a particular service operation, for ourexample, the Create Sales Order service operation. From the list of the proc-ess components in ERP, select the Sales Order Processing process compo-nent. This results in a list of Enterprise Service interfaces that support thisprocess component.

Global Data Type (GDT)

A GDT is an SAP system-wide defined data type with meaning, structure, andvalues oriented on industry standards, where available. Referring to theenterprise SOA metamodel shown in Figure 3.8, you can see how processcomponents, service interfaces, service operations, and GDTs are related.

Let’s now look at GDTs, and later on BOs, in more detail with reference toenterprise SOA.

Note

In contrast to the general notion of “object” in an object-oriented sense, the term“business object” is used here to describe the type and not the instance level. Con-sequently, the BO sales order, for example, describes the category of all salesorders and not a single sales order instance.



GDTs in Enterprise SOA 3.8

93

Figure 3.8 Enterprise SOA Metamodel Defining Entities and Relationships

3.8 GDTs in Enterprise SOA

As mentioned previously, GDTs are SAP system-wide defined data types withbusiness content. They are defined in accordance to industry standards andoffer customers a way to use one common data structure. Figure 3.9 shows anexample of a GDT. GDTs are elemental data structures that are used to buildup more complex BOs. For the example, there is at SAP-defined GDT calledPrice, which is an extension of the CCTS Core Data Type of Currency. Finally,the Currency Core Data Type references the Primitive Data Type for a float realnumber.

The following are standard characteristics for GDTs in enterprise SOA:

� Conform to the following open standards: ISO 15000-5 and UN/CEFACTCCTS

� Defined in the ESR

� SAP sytem-wide approved with reference to the governance process forProcess Integration Content (SAP PIC Process)

approved

Credit Management

approved

Credit Management

approved

Credit Management

CreditManagement

Account

approved

Credit AgencyIdentifier

Credit AgencyReport

approved

CreditManagement

Account

approved

Credit AgencyIdentifier

Credit AgencyReport

approved

Deployment unit

Processcomponent

Business object model

Drilldown from BO map toBO model

Businessobject




94

� Semantic building blocks for service definition and interfaces for reuse

� ESR-provided functionality to define CCTS data types to allow for cus-tomer-specific GDTs or to extend or adapt SAP’s GDTs

Figure 3.9 Example of a GDT

UN/CEFACT CCTS, shown in Figure 3.10, is a methodology for developing acommon set of semantic building blocks that represents the general types ofbusiness data in use today.

At SAP, a governance process driven by the Process Integration Content (PIC)methodology assures that GDTs have the following characteristics:

� High quality

� Standardized across all application areas

� Designed for reuse

� Tailored to comply with open business standards

Technically, a GDT is an aggregated data type, which consists either of otheraggregated GDTs or of so-called core data types — the smallest unit of thistype of modeling approach. Currently, more than 20 core data types aredefined. The following two are the most prominent:

� CodeRepresents a definitive value, a method or a property description in anabbreviated or language-independent form. The possible values aredefined by a code list. Examples are currency code or country code.

� IdentifierRepresents BO node instances. The possible values are given by keys ofBO node instances.

From primitive GDTs, you will build up more complex BO data structures.

1

1..*

1

1..*

1..*1 Global Data

Type (SAP)

Core Data Type (CCTS)

Primitive Data Type (XSD)

Example: Price

Example: Currency

Example: float, string, token, binary



Business Object Structures in Enterprise SOA 3.9

95

Figure 3.10 Detailed Data Model for the UN/CEFACT CCTS GDTs

3.9 Business Object Structures in Enterprise SOA

BOs are the primary structuring elements of enterprise applications, provid-ing the major portion of application business logic. Although there areexceptions (technical objects such as Workflow Item, for instance), a BO iscommonly understood to be an independently viable business entity withunique, identifiable instances. This entity includes state and behavior and isaccessible from other BOs or service implementations exclusively through itscore services.

• PurchaseOrder 1

n

n

1

n

1

n

1

n n

1

1

n

1

• PurchaseOrderParty• PurchaseOrder DeliveryTerms

• Amount• Binary Object• Code• Date Time• Identifier• Indicator• Measure• Numeric• Quantity• Text

• PurchaseOrderParty Elements• PurchaseOrder DeliveryTerms Elements

• PurchaseOrdering_In• PurchaseOrdering_Out

• PurchaseOrderRequest• PurchaseOrder ChangeRequest

• PurchaseOrderMessage• Invoice Message

• Delivery Terms• Address• ProductID

• float• string

Bus

ines

sSe

man

tics

no B

usin

ess

Sem

anti

cs

Usa

ge s

peci

fic

glob

al

Sem

anti

c St

ruct

ure

Dat

a Ty

ping

B2B / A2A - Interface /Service Operation

Message Type

B2B / A2A -Message Data Type

BusinessObject

BusinessObject Node

NodeData Type

Global Data Type

CCTS Core Data Type

W3C Data Type




96

BO nodes can also have additional identifiers called alternative keys. Alterna-tive keys are defined by data structures included in the elements data type ofthe BO node. Alternative keys can be used to create foreign key associationsbetween BOs. The underlying elements data type of a BO node is not permit-ted to be arbitrarily complex. It must be essentially flat, which means it can-not contain table-like substructures. This ensures that the BO node’s set ofattributes can always be mapped to a structure composed solely of scalar datatypes.

More complex BO structures may be constructed using the compositionmechanism for BO nodes as shown in Figure 3.11. A BO’s tree of nodes isdefined in ESR by compositional associations (compositions for short)between the respective parent and child nodes. In Figure 3.11, SalesOrder-Item is a child node of SalesOrder. A compositional association represents astrong semantic relationship: One or more instances of the child nodedepend on the existence of one instance of the parent node. One instance ofa parent node may have zero, one, or multiple associated instances of a cor-responding child node.

In general, semantic relationships between BO nodes are defined in the Enter-prise Services Inventory (ESI) by unidirectional, binary, named associations.Inside a BO, an arbitrary number of associations between the different nodesare possible in addition to the (BO internal) compositional associations, whichmust be present to build the BO’s tree of nodes. Relations between differentBOs can be established only on the node level and only by using associationsbetween their nodes as shown in Figure 3.11. Very often, an associationbetween nodes is a “foreign key relation” in the sense that one or moreattributes of the source node completely identify the associated target nodeinstances. ESR offers corresponding modeling and execution capabilities.

Note

The Enterprise Services Inventory (ESI) is object-based, not object-oriented. ESI isa directory that will contain all of the Enterprise Services and variants for use inyour company. It deals with the concepts of BOs, nodes, and instances but doesnot represent these concepts in a one-to-one correspondence with object-ori-ented classes and instances. As a result, not all object-oriented concepts are avail-able within ESI; for example, inheritance is not available.

In ESI, a BO is defined as a tree of BO nodes with a single root node. Each node isstructurally defined by one underlying GDT, the so-called elements data type. BOnodes and their corresponding elements data type are depicted as identical enti-ties because this more closely reflects the common understanding. Each BO nodeimplicitly inherits one technical identifier represented by the generic GDT NodeID.



Other Critical Enterprise Data Issues 3.10

97

Figure 3.11 Conceptual Version of BO Nodes

Now that you understand the general principles of BOs, the following sec-tion focuses on other critical enterprise data issues for enterprise SOA.

3.10 Other Critical Enterprise Data Issues

Additional challenges remain with respect to managing enterprise data forenterprise SOA. They are important, even if you choose to not implement aSOA strategy such as enterprise SOA. They become critical as you try to scaleenterprise SOA and extract the business benefits from enterprise SOA. Thechallenges include the following:

� Decoupling layers in enterprise SOA

� Increased requirements for enterprise SOA-specific BO governance

� Management of BO states

� SOR management

� Metadata management

First, let’s start with the requirement for decoupling the layers in enterpriseSOA and how that affects the design of enterprise data, such as BOs.

Material Customer Invoice ItemItem

Customer Party

Taxation Terms

Product

BO Material BO CustomerInvoice

Service Product

BO Service

Customer

BO Customer

Each business object is modeled as a hierarchical structure of nodes and each business object node is made up of data fields.“




98

3.10.1 Decoupling Layers in Enterprise SOA

A major benefit of enterprise SOA is decoupling the layers. BOs are one ofthe most important layers to manage. Generally, as you move farther downthe architecture, the dependencies grow, and changes are much more criti-cal. Changes to BOs have a lot of leverage to services, applications, and even-tually processes and UI Workcenters.

You must design each layer horizontally, based on Figure 3.12. In addition,you must look at supported scenarios that cut across the layers vertically.Any potential design change must be weighed against its impact on existingentities on each layer, especially impacts on the BOs.

Figure 3.12 Standard Decoupled Layers in Enterprise SOA

3.10.2 Increased Requirements for Business Object Design Governance

SAP has designed a process to determine impacts on the BOs when designingEnterprise Services called the Process Integration Content (PIC) process. PICis the main process for the design and governance of Enterprise Services.

Services Services Services

CRM BW ERP

UI UI

Workcenter

Composite Process

Actions

Exchange Infrastructure

Service Enablement

Systems

Services Actions

Role 1 Role 2

BA

CK

END

CO

MPO

SITE

APP

LIC

ATI

ON

Step 1 Step 2 Step 3 Step 4

Action -UI

BO model

DB DB DB

Database

UI

Business Objects,ServicesRemote

Services

LocalServices

Business Objects

Local Remote



Other Critical Enterprise Data Issues 3.10

99

The four steps for the PIC process are PIC 0, PIC 1, PIC 2, and PIC 3, as shownin Figure 3.13. The first step, PIC 0, is the most critical scoping impact step tosemantically harmonize the BOs for the new or modified Enterprise Service.As you can see, the rest of the steps in the PIC process center around thedesign of the BO nodes, GDTs within the BO node diagram, and finally theservice operations and messages data types that are used to access the BOswithin the process components. Next, let’s look at designing BO states, SORmanagement, and managing metadata.

Figure 3.13 Summary of the SAP PIC Method for Enterprise SOA BO Design

3.10.3 Designing Business Object States

Managing the lifecycle states of the enterprise BOs is important. By clearlydefining the BO states, tracking process sequence is less important. Definingthe states and their links across domains, such as sales, design, manufactur-ing, and so on, is important as well. Figure 3.14 shows the lifecycle of amaterial including the services and when they are available for that BO. Ateach of the points where services are available there are major state changesfor the material.

3.10.4 System of Record (SOR) Management

The ESR may help with this challenge. You need to track the preferred SORor main reference location for the BOs.

3.10.5 Managing Metadata

Metadata needs to be managed so that it is readily accessible and uniformacross the enterprise. There are many types of metadata, such as attribute

“ How to ” guidelines

PIC 0: Business Objects and Operations Identification Semantically harmonized definitions cross solutions

GDT: Node Structure for Business Objects Node Elements (referring to Global Data Types) Final Definition for Business Objects and Service Interfaces/Operations Detailed signature definition containing all elements and integrity constraints

Global Data TypesName, Definition, Structure,Value Ranges

Pic 1 Pic 2 Pic 3




100

definitions, business rules, service definitions, schemas, mappings, and soon. Reusability of Enterprise Services and BOs will rely on standardizedmetadata.

These are just a few additional enterprise data issues that you should con-sider as you prepare your company for enterprise SOA.

Figure 3.14 Sample Lifecycle of a Material

3.11 Recommendations for Managing Enterprise Data in Preparation for Enterprise SOA

As you have seen, BOs are at the heart of enterprise SOA. The enterprise SOAmetamodel and process components are designed to manage BOs. These BOsare constructed using GDTs or standard definitions for the elements withinthe BO for attributes, such as a date, purchase order ID, or address. TheseGDTs are used in one or more BOs and messages used to access these BOs. Asa result, when you are developing an EDM Program, you should consider thefollowing to lay a foundation for future enterprise SOA:

Launch

Pre-Launch Inactive

Growth Maturity

• Reuse & Subscribe • Reliability & Testing • Find Replacements • Find Other Sources • Mfg Part Change Notices

• Where Used Analysis • BOM Validation • End of Life Predictability • DFM-Reengineering • Regenotiate

• Synchronize Part Data with ERP• Synchronize Part Data with PLM• View Comprehensive Part History

• Maintain Available to Purchase Catalogs • User Searches • Maintain Approved Supplies

• New Part Introduction • Define Specification • Request and Evaluate • Issue Intern. Part Number • Design Buy • Build\Acquire Math Model

• HTS Compliance • EH&S Compliance • Approval • Tracking • On-Going Reporting • Preference Management • Engineering • Procurement • Spend Analysis

• End of Life Mgmt. • EOL Notices • EOL Buy • Final Inventory • Int. Channel Mgmt.

• In-Service Management • Tracking • Field Notices • Maintenance\Replacement

Lifespan of Services

Change of Object State

Services for Materials



Recommendations for Managing Enterprise Data in Preparation for Enterprise SOA 3.11

101

� Architect each type or domain of enterprise data independently.Each domain will have different business requirements, application land-scapes, and data flow diagrams. Try to have a preferred method for thecreation and distribution of enterprise data, but be prepared to pragmati-cally design each differently.

� Continually decouple enterprise data from applications.Enterprise SOA and other SOA strategies take advantage of the loose cou-pling of the layers. Loose coupling of BOs will be important to scaling andleveraging the business benefits of enterprise SOA.

� Start to introduce BO node diagrams when modeling BOs.Using some form of entity relationship diagramming is common whenmodeling your enterprise data objects. Start to introduce and design yourLogical Data Models (LDMs) using the BO node diagrams as defined in theUN\CEFACT standard.

� Start to track the SOR for enterprise data BOs.Begin to think about what it would take to track the SOR for all BOs. Newtools like the ESR along with SAP NetWeaver MDM may help with this.

� Enterprise BO states are more important than before.For enterprise data objects, design the object states. Especially include theobject states across domains and how they are linked together. To main-tain flexibility in Enterprise Services, BO actions and states must be clearlydefined. By defining states, process sequence tracking becomes lessimportant or rarely necessary. Start to use diagramming such as UML(Unified Modeling Language) object state diagrams.

� Strategy drives process and process drives enterprise data.Focus on enterprise data that has the most impact for your company busi-ness strategy. This company business strategy will drive requirements forbusiness processes and Enterprise Services. The selection of EntepriseServices will require that you design the related BOs.

� Resist the desire to create one repository for all metadata.Metadata is more important, including metadata for BO definitions, serv-

Exception to the Rule of Process Drives Data Requirements

The exception to the rule is when you are using EDM as “triage” to begin to alignbusiness processes, or when you have many business process variants so that it isdifficult to come up with one set of global processes. Aligning the enterprise datawill help you begin to align those business processes without having to standardizeon one process.




102

ices definitions, reference data definitions, business rules, and others.Each class of metadata is logically maintained in an associated repository.SAP NetWeaver MDM, ESR, SAP NetWeaver XI, and others are used tomaintain that metadata. When trying to aggregate all metadata, you losethe business or technical context of the metadata.

3.12 Summary

This chapter provided you with a brief explanation of enterprise SOA andthe issues around enterprise data that you should consider to prepare yourcompany for this future architecture. Preparing for enterprise SOA is espe-cially important if your EDM Program is partially supported.

Now that we have looked into the future requirements for your enterprisedata, let’s get back to your immediate needs to build a business case forEDM. In Chapter 4, you will see the components of a business case, includ-ing many EDM examples.

Note

This chapter is not meant to replace detailed design text on enterprise SOA. Youneed to learn many more details to fully understand enterprise SOA. Refer towww.sdn.sap.com/irj/ sdn/enterprisesoa for more information.



577

Index

A

A2i 43ABAP 398Accelerated SAP 349ACORD 373Ad-hoc reporting 390Aerospace and Defense 503AIAG 373Alternative keys 96Application Architecture 229, 260, 423Application-to-application data delivery

392Approved Vendor List 524ARIS for NetWeaver 236, 390, 391, 393,

407ASAP 494, 496, 527

Blueprint phase 539Blueprint workshops 539Data issues 350Project 372

Aspect development 41Assertion testing 421ASUG\EDM survey 103, 559Attributes versus fields 449Automotive 503

B

BAPI 398, 412Basics of taxonomy 443Batch profiling 419Benchmarking study metrics 138BI 415Bill of Materials (BOM) 506, 521BPM 561Business case 127

Case studies 139Management 390

Business Data Organization 309, 315, 495Centralized versus decentralized 318Positions 324

Roles 317Structure 320Variant scenarios 321

Business data processes 230, 330, 470, 495Examples 333

Business driver 557Business Intelligence strategy 374Business logic 426Business maps 410Business object 85, 91, 95, 278, 559

Design governance 98Encapsulation 86Lifecycle 559Models 415Node diagram 99, 101Nodes 96States 99Structures 95Template 91

Business object definition 277, 278How to use 280Sample format 278

Business Object Repository (BOR) 412Browser 412

Business processManagement 230, 561Objects 86Repository 404

Business Process Integration 229Uses 234

Business scenario 328Group 328Maps 410

Business strategy 32, 560Business strategy integration 57, 67,

390, 482Components 123

C

CAD 40, 520Cadis 41



578

Index

Catalog search 429Catalog search functionality 392CCTS 84, 93CE 401CEFACT 84Central MDM 467Change management 353, 354Chemicals 503CIDX 373Classification 363, 438Classification of data 44Cleansing 363Client system 458COBIT 216Column Property Analysis 396, 420Common Information Model 405Company business strategy

Basics 121Integration 121

Compelling events 486Complex configured items 506Complex Data Rule Analysis 421Complex entities 159, 423Component & Supplier Management 41Composite Application Framework 401Conditional master data 396, 452Configuration data 45Configured-to-order 504, 505Consolidated MDM 467Consumer products 503Control Chart 173Control objectives 217Controls

Access 219Configuration 219Monitoring 220Procedural 220

Core Component Technical Specifica-tion 84, 275, 373

Core Data Type 93Cost avoidance 36Cost containment 497Cost of goods sold 504Cross-functional team 494, 498Cross-Industry Solution Maps 410CRUD Matrix 230CSM 41Customer data integration 53, 500

D

DARPA RaDEO 508Data

Acquisition 415Architecture 58, 71, 482, 501Attributes 246Champion 164Cleansing and harmonization 392Custodian 165Distribution 416Domains 246, 248Elements 247Entities 246Fields 247Governance processes 425Mart 393Modeling 391, 415Owner 165Pool 52Profiling 189, 388, 390, 419Schematic 272Subject area 246Sub-subject area 246Values 247

Data analysis 184Complex rules 192test plan 190

Data defects 174Defect 174Error 174Mistake 174Released defect 174

Data Dictionary 277, 280, 496How to use 285

Data Migration and Cleansing 76, 353, 363Factors to consider 368Outsourcing versus in-house 368Process overview 365

Data quality 32Accessibility 179Accuracy 178Availability 179Committee chair 164Completeness 178Consistency 179Coverage 178



579

Index

Duplicates 179Guidelines for rules 180Integrity 178Metrics 181Redundancy 179Relevance 179Secure 178Timeliness 178Validity 178

Data quality management 57, 69, 169, 390, 482, 489Determining root causes 211Tools to fix quality defects 213

Data quality management programAnalysis tools 209Where to focus 210

Data Quality Scorecard 205Data Readiness Report 197Data security 380

Breaches 37Plan 382

Data Standards 58, 71, 275, 482, 501Components 277Management 390

Data, document, record, and application archiving 393

Decoupled layers in enterprise SOA 98Decoupling 81Dependent object 91Deployment 58, 74Design BOMs 525Design document repository 370Design document style guide 370Design Engineer 509Direct materials 503, 504

Roles 508Discovery 421Document management 390Domain Data Model 251Domains 34Downgrade 365

E

EDMBest Practices 112Component 484, 488

core team 69, 490, 529Data Quality Program 397Design Document Repository 404Dimension 484, 488, 489Extended team 490Governance processes 329Manager 312Methodology 482, 486, 558Program collaboration 390Project Manager 491Scenarios 48Team 371, 497, 498, 499

EDM Assessment 489Scorecard 103, 104Scoring Definitions 114

EDM Component 488EDM Deliverables

Domain-specific 483Enterprise-wide 483

EDM Program 32, 57, 121, 349, 370, 385, 389, 394, 423, 479, 482, 486, 498, 499Approaches 64Business Case 126Compelling events 64Design Guidelines 150Metrics 183Policy 161Scope 156, 185Scorecard 207

EDM Program Charter 123, 124Mission 124Objectives 124Vision 124

EDM Project 62, 403, 482, 483, 486, 491Commercial Initiative project 500Communication plan 492

EDM Strategy 32, 489, 492, 503Development 359Project 480

EDM-related applications and technolo-gies 388

EDM-related Business Standards 354, 372

EDM-related technology functions refer-ence list 388

EDR 262, 423, 424, 426, 428



580

Index

EIM 44Electronic Data Interchange 276Electronics 503Engineered Finished Good 507Engineered-to-order 504, 506Engineering assembly 506

Specification 518System 507

Enrichment 364Enterprise

attributes 268, 275, 370business objects 271, 275Conceptual Data Model 250data 46, 48, 101

Enterprise architecture 223, 224, 560As-is state model 225Components 224Framework 224Metamodel 224Methodology 225, 486Modeling 390To-be state model 225Transition plan 225

Enterprise Data Distribution Architecture 229

Enterprise Data GovernanceChange request 338, 344Organization 70Position descriptions 315Processes 338, 470

Enterprise data import and conversion 392

Enterprise Data Model 245, 410Business value 248

Enterprise Data Organization 308Best Practices 314Roles 310Structure 311

Enterprise Data Quality 423Management 486

Enterprise Data Repository (EDR) 253, 359, 388, 392, 437Implementation 360

Enterprise Data Syndication 392Enterprise Data Trustee 312Enterprise Information Management 43Enterprise objects 268

Enterprise program and portfolio man-agement 391

Enterprise reporting 391Enterprise Services 83Enterprise Services Repository (ESR) 86,

93, 417, 418Enterprise SOA 81, 225, 386, 424, 559

Metamodel 87ERP 527ES Workplace 85, 390, 414ESI 96ETL tool 398, 422Exact duplicate 364Executive Sponsor 164

F

Federal Enterprise Architecture 224FERT 421Financial benefits 134, 140Finished goods 504Focused Internal Business Objective 497Functionally Equivalent 364

G

GDS Console 437Global Data Synchronization 52, 501Global data type (GDT) 84, 86, 92, 275,

373, 415, 417, 559Example 277

Global procurement 146Global Spend EDM 141Globalization 543

Best practices 550Options 548

Governance 391Governance Organization 58, 73, 305,

307Dimension 482

Governance process 58, 73, 327Dimension 482



581

Index

H

Harmonize master data 81, 424, 467HL7 373Horizontal workstream 528HR-XML 373

I

IDoc 398Import Manager 436Import maps 461Individual program and project manage-

ment 391Information asset management 393Integration

Directory 400Engine 400Repository 400

Internal Master Data Management 467International Computex 41Iterations and backtracking 422iView 471

J

Java Application Server 401

K

Key mapping 364, 522KPI 206, 377, 411, 497, 558

L

Landscape description 405Language and localization 377, 543,

544, 551Laws of data 127Legacy System Migration Workbench

398, 422Logical Data Model 423, 454, 456

Business value 254Material Master 259

Logical master data 33

Lookup tables 447LSMW 398, 399

M

Main table 444, 447Managing EDM Data Design Docu-

ments 353, 370Manufacturing Engineer 509Mapping ASAP deliverables to workshop

cycles 540Mask 441Master data 33, 45, 46, 396

Cleansing 425Consolidation 49Distribution Approach 237, 242Harmonization 50Information bus 423Object 34, 86, 404Records 33

Master Data Management IT scenarios 48

Master data versus enterprise data 46Master repositories 465Material Info Records 34Material Master 34, 524MDM

Business Scenarios 51CLIX 436Console 435Data Manager 435Image Manager 436Publisher 437Roadmap Program plan 480, 486Server 434Workflow 436

Merger and acquisition 558Metadata 72, 423

Document management 415Management 393Verification 422

Metals and Mining 503Metamodel 429Metric 558MRO item 512MRP application 40Multichannel syndication 429



582

Index

N

Normalization 364

O

Object Data Definition 496Object tables 444Oil and Gas 503OPC 373Operational inefficiencies 36Organization design and management

391Organization schema sample

Comparison of schema levels 290Concept drawing 290

Other EDM-related functions 393Ownership\subscriber management 391

P

Pain points 129papiNet 373Pareto diagram 173Part numbering 522PDM 40, 42, 521PI 400PIC 94, 98PIDX 373Plant MRO 504PLM 521Preferred Parts List 260, 515Primary objects 34, 159Print catalog 429Process component 88, 90Process Integration Content 98Process steps 328Product data interoperability 520Product development costs 508Product development process 511Product relationship 438Production BOM 525Professional buyer 510Profile template 420Project costs 142Purchasing process 511

Q

Qualified lookup 452Qualified table 447Qualitative business benefits 133Quality 169Quality data 178

R

RACI diagram 339, 488, 495, 533Rationalization 364Realization Deployment 349, 391, 482

Standard project plans 359Realization Technology 482Reference data 396, 423Regulations

Environmental 378Governance 378Privacy 379Safety 378Security and privacy 379Trade Restrictions 379

Regulatory 377Relationship 448Relative design 493Replacement 364Requisite Technology 42Reverse Business Engineer (RBE) 390,

396, 422Revision control 426Rich content management 52, 392, 425Rich master data 438Root cause analysis 173RosettaNet 373

S

S.W.I.F.T. 373Sample populated schema structure 291SAP ALE 392SAP Analytics xApp 390, 391SAP archiving tools 393SAP Business Information Warehouse

391SAP Business Workflow 392



583

Index

SAP Composition Environment 401SAP cProjects 391SAP EAF 228, 236SAP Enterprise Architecture Framework

(EAF) 406SAP Enterprise Architecture Framework

for enterprise SOA 228SAP Enterprise Buyer Professional 42SAP Enterprise Data Management Frame-

work 56SAP ERP 392, 393, 395, 431

Data model 414HCM 391

SAP ERP ECC 34, 157, 423, 425Asset Management 393

SAP exchange infrastructure 415SAP Industry Solution Maps 410SAP Legacy System Migration Work-

bench 392SAP NetWeaver 373SAP NetWeaver Business Intelligence (BI)

262, 390, 393, 415SAP NetWeaver Knowledge Management

390SAP NetWeaver MDM 385, 390, 391,

392, 393, 422, 431, 455Backups and archiving 470Basic modules 434BI integration 472Console 439Data field type 441Data Manager mode 441Portal integration 471Repository 445SAP-supplied repositories 460Security 473Sizing MDM 464Solution landscape 466Transport 468Workflow 469

SAP NetWeaver Process Integration (PI) 392, 400, 401

SAP NetWeaver System Landscape Direc-tory (SLD) 393, 405

SAP Organization Terms 306SAP Product Availability Matrix 390SAP Product Lifecycle Management 239SAP SEM 390

SAP Solution Composer 236, 390, 410SAP Solution Manager 370, 390, 391,

403, 404, 410SAP Strategic Enterprise Management

391SAP xRPM xApp 391Sarbanes-Oxley (SOX) Act 216, 378Schema 285

Examples 288Standards 278, 288Types 285

Scorecard 558Secondary object 160Security and compliance 166Service interface 86, 88, 92Service operation 86, 88, 92Services-oriented Architecture 79Services Registry 417Simple configured item 506Simple Data Rule Analysis 420Situation analysis 122Six Sigma 170

Analyze 176, 193Control 176, 214Define 175, 177DMAIC 171Five steps 172Guiding principles 171Improve 212Measure 176, 187Quality Management 169

Slave repositories 465SOAP 87Solution Manager 235Solution Maps 410Source and Target Mapping 229

Business value 271Model 268Model example 271

Sourcing 53SPACE 34, 157SPEC2000 373Special Deployment Issues 354Special tables 444Spend analysis 53SRM 54Standard component 504, 505



584

Index

Standard EDM Services 338, 339, 344, 470

Standard Project Plans 353Statistical process control 173Strategic plan 123Strategic sourcing 480, 511Structure Data Analysis 396, 420Style Rule Analysis 421Subtables 444Superceded 364SWOT Analysis 122Syndication Manager 436Syndication maps 461System of Distribution (SOD) 241, 268,

396, 432System of Entry (SOE) 241, 268, 396,

431System of Record (SOR) 72, 75, 81, 99,

241, 268, 297, 423, 424, 431, 560How to create 298Sample 299

System tables 445

T

Taxonomy 286, 410, 443Basic concepts 286Basic terminology 286Management 392Of data 423

Technology 58, 74Driver 557

TOGAF Architecture Development Method 225

Total quality management 170Transactions 45Transformation 416Translation 544Transliteration 544Transora 54Triggers 332TWIST 373

U

UCCnet 54, 373UDDI V3 417UN/CEFACT 93, 275, 276, 373

Core Component Library 277UNSPC 288Upgrade 365

V

Validation 364, 457Expression 457

Value proposition 148Value Rule Analysis 421Value tree 135, 144, 147Vendor list 524Vertical Workstream 528

Coordinator 528, 530VICS 373Virtual pooled inventory 54Visual inspection 421

W

Web services 83Web Services Description Language 84Wiki 85Workflow 392WRICEF 55, 372, 496WSDL 84

X

XBRL 373

Z

Zachman Framework 225

