Andrew LeBlanc
Enterprise Data Management with SAP® NetWeaver MDM
Build Foundations for Continual Improvements with SAP NetWeaver MDM
Bonn
Boston
Contents at a Glance
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 A B C The Importance of an EDM Strategy .................................. 31 Challenges and Approaches to Your EDM Strategy ........... 61 The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture ........................... 79 EDM Assessment Scorecard ............................................... 103 Company Business Strategy Integration ............................ 121 Data Quality Management ................................................. 169 Design: Data Architecture .................................................. 223 Design: Data Standards ...................................................... 275 Governance Organization ................................................... 305 Governance Processes ........................................................ 327 Realization: Deployment .................................................... 349 Realization: Technology ...................................................... 385 Building an EDM Program .................................................. 479 EDM for Materials .............................................................. 503 EDM for a Large ERP or Enterprise Application Project ..... 527 Globalization Within an EDM Strategy .............................. 543 The Future of Enterprise Data Management ...................... 557 References ........................................................................... 565 Glossary .............................................................................. 567 Author Biography ................................................................ 575
Contents
Acknowledgments ..................................................................................... Preface ...................................................................................................... 21 23
SECTION I
1 The Importance of an EDM Strategy ................................... 31
1.1 The Many Facets of Master Data ............................................ 1.1.1 A Simple Definition .................................................... 1.1.2 Principle or Primary Objects: SPACE ........................... 1.1.3 DNA of Decision Making ........................................... 1.1.4 What Master Data Is Not ........................................... The Consequences of Haphazard Management of Enterprise Data ............................................. 1.2.1 Lack of Accurate Knowledge of Your Own Business .... 1.2.2 Supply Chain and Internal Operational Inefficiencies ... 1.2.3 Cost Avoidance .......................................................... 1.2.4 Data Security Breaches ............................................... The History of Master Data ..................................................... 1.3.1 The Growth of Packaged Enterprise Applications ........ 1.3.2 The Development of Component & Supplier Management (CSM) ................................................... 1.3.3 The Push Toward Upgrades and Conversions for Y2K.... 1.3.4 The Rise of Master Data Management as a Function ... 1.3.5 Online Marketplaces, Catalog Management, Buy-Side, Sell-Side, and Maintenance Repair and Operations (MRO) Materials ............................... 1.3.6 The Post-Internet Commerce Boom ........................... 1.3.7 SAP’s Holistic Approach to Master Data Management (MDM) ................................................. 1.3.8 Moving Forward to Enterprise Information Management (EIM) .................................................... Classification of Data .............................................................. Master Data Versus Enterprise Data ....................................... EDM Scenarios ....................................................................... 1.6.1 MDM IT Scenarios ..................................................... 1.6.2 MDM Business Scenarios ........................................... 1.6.3 Other Business Value Problems .................................. 33 33 34 34 35 36 37 37 38 39 40 40 40 41 41
1.2
1.3
42 42 43 44 44 46 48 48 51 53 7
1.4 1.5 1.6
Contents
1.7 1.8 1.9
Joint ASUG\EDM Survey: The Need for a Comprehensive Data Management Approach ......................... EDM Framework .................................................................... Summary ................................................................................
55 56 58
2
Challenges and Approaches to Your EDM Strategy ............ 61
2.1 Factors to Consider When Developing an EDM Project ........... 2.1.1 Project Design ........................................................... 2.1.2 Organization .............................................................. 2.1.3 Resource Constraints .................................................. 2.1.4 External Drivers .......................................................... Typical Approaches or Compelling Events ............................... Common Pitfalls in EDM ........................................................ 2.3.1 Company Business Strategy Integration ...................... 2.3.2 Data Quality Management ......................................... 2.3.3 Design: Data Architecture and Data Standards ............ 2.3.4 Governance Organization and Governance Process ..... 2.3.5 Realization: Deployment and Technology ................... Summary ............................................................................... 61 62 62 63 64 64 66 67 69 71 73 74 76
2.2 2.3
2.4
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture ................... 79
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 Benefits of Enterprise SOA ...................................................... Basics of Enterprise SOA ......................................................... Interaction of Enterprise SOA and Master Data ...................... Basic Requirements for Enterprise Services ............................. Business Objects in Enterprise SOA ........................................ Anatomy of an Enterprise Service ........................................... The Enterprise SOA Metamodel .............................................. GDTs in Enterprise SOA .......................................................... Business Object Structures in Enterprise SOA ......................... Other Critical Enterprise Data Issues ....................................... 3.10.1 Decoupling Layers in Enterprise SOA ......................... 3.10.2 Increased Requirements for Business Object Design Governance .................................................... 3.10.3 Designing Business Object States ............................... 3.10.4 System of Record (SOR) Management ........................ 3.10.5 Managing Metadata ................................................... 79 81 81 83 85 86 87 93 95 97 98 98 99 99 99
8
Contents
3.11 3.12
Recommendations for Managing Enterprise Data in Preparation for Enterprise SOA ............................................... 100 Summary ................................................................................ 102
4
EDM Assessment Scorecard ................................................. 103
4.1 Assessment Benefits ............................................................... 4.1.1 General Benefits of an EDM Assessment .................... 4.1.2 Benefits of Enterprise Application Implementation Projects ...................................................................... 4.1.3 Benefits for Overall Corporate Knowledge and Enterprise Architecture ........................................ As-Is EDM Assessment Process ............................................... Preparing for the Assessment .................................................. 4.3.1 Standard Interview Questions .................................... 4.3.2 Requests for Information ............................................ 4.3.3 Cataloging Documents ............................................... 4.3.4 Gathering Findings ..................................................... 4.3.5 General Guidelines on EDM Assessment Meetings...... 4.3.6 Guidelines for Assessments ........................................ EDM Best Practices ................................................................ Scoring Your Company Against EDM Strategy Best Practices ... Sample Summary Results ........................................................ Detailed Assessment Results ................................................... Summary ................................................................................ 103 103 104 104 105 106 106 107 108 109 110 111 112 114 115 116 117
4.2 4.3
4.4 4.5 4.6 4.7 4.8
SECTION II
5 Company Business Strategy Integration ............................. 121
5.1 Company Business Strategy Basics .......................................... 5.1.1 Corporate Strategy Inputs to an EDM Program............ 5.1.2 Components of the Company Business Strategy Integration ................................................... The EDM Program Charter ...................................................... 5.2.1 Vision ........................................................................ 5.2.2 Mission ...................................................................... 5.2.3 Strategic Objectives ................................................... The EDM Program Business Case ............................................ 5.3.1 Definition of a Business Case ...................................... 121 122 123 123 125 125 125 126 127
5.2
5.3
9
Contents
5.4
5.5
5.6
5.7
Pain Points: Examples of Issues for the Current Situation ............................................ 5.3.3 Business Benefits in a Business Case ........................... 5.3.4 Qualitative Benefits .................................................... 5.3.5 Quantitative Benefits ................................................. 5.3.6 Building a Financial Model ......................................... 5.3.7 Putting it Together: Building Your Story ..................... EDM Program Design Guidelines ............................................ 5.4.1 Sample Design Rules .................................................. 5.4.2 Strategic Direction ..................................................... 5.4.3 Executive Intent ......................................................... 5.4.4 Principles to Determine Program Scope ..................... 5.4.5 Domain-Specific Guidelines ....................................... EDM Program Scope .............................................................. 5.5.1 Domains in Scope ...................................................... 5.5.2 Objects in Scope ........................................................ 5.5.3 Attributes in Scope .................................................... 5.5.4 Other Scoping ............................................................ 5.5.5 Grouping Objects in Scope into Primary and Secondary Objects ........................... EDM Program Policy .............................................................. 5.6.1 A Sample EDM Policy Guideline ................................. 5.6.2 Security and Compliance ............................................ 5.6.3 Training and Awareness ............................................. Summary ................................................................................
5.3.2
129 130 131 134 139 145 150 151 153 154 154 155 156 157 157 158 158 159 161 161 166 167 167
6
Data Quality Management .................................................. 169
6.1 Introduction to Six Sigma Quality Management ...................... 6.1.1 The Term Sigma in Statistics ....................................... 6.1.2 The Six Sigma Quality Management Program Definition .................................................... 6.1.3 Important Foundation Concepts for Six Sigma............. 6.1.4 Five Standard Steps of Six Sigma ................................ 6.1.5 The Most-Used Tools Within a Six Sigma Quality Management Program ................................... 6.1.6 Classifying Data Quality Defects ................................. The Elements of the Data Quality Management Dimension .... Define .................................................................................... 6.3.1 Leveraging Other Dimensions for the Define Component ......................................... 6.3.2 Requirements for Good Quality Data ......................... 170 170 171 171 172 173 174 175 177 177 178
6.2 6.3
10
Contents
6.4
6.5
6.6
6.7
6.8
6.3.3 Determining Good Data Quality Rules ....................... 6.3.4 General Requirements for Developing Metrics ............ 6.3.5 Scoping: Selecting Where to Measure ........................ Measure ................................................................................. 6.4.1 Column Property Analysis .......................................... 6.4.2 Data Profiling ............................................................. 6.4.3 Link to Data Standard ................................................ 6.4.4 Data Analysis Test Plan .............................................. 6.4.5 Testing General Rules ................................................. 6.4.6 Testing Complex Rules ............................................... 6.4.7 Testing Style Rules ..................................................... Analyze .................................................................................. 6.5.1 Data Quality Reports ................................................. 6.5.2 Sample Data Quality Metrics ...................................... 6.5.3 Relating Data Quality Metrics to Business Metrics....... 6.5.4 Data Quality Scorecard .............................................. 6.5.5 Tools for the Analyze Step for the Data Quality Management Program ............................................... 6.5.6 Determining Where to Focus ..................................... 6.5.7 Determining Root Causes ........................................... Improve .................................................................................. 6.6.1 Steps Involved During the Improve Phase .................. 6.6.2 Tools and Other Options to Fix Quality Defects .......... Control ................................................................................... 6.7.1 Control for Common Issues ........................................ 6.7.2 Understanding External Requirements and Regulations ................................... 6.7.3 Developing the Controls Framework .......................... 6.7.4 Determining Applicable Technology Controls ............. 6.7.5 Identifying Additional Control Needs ......................... 6.7.6 Creating Plans to Address Control Needs ................... Summary ................................................................................
180 181 183 187 188 189 190 190 191 192 192 193 193 195 202 205 209 210 211 212 212 213 214 215 216 216 219 220 220 220
7
Design: Data Architecture .................................................... 223
7.1 General Enterprise Architecture .............................................. 7.1.1 Elements of All Enterprise Architectures ..................... 7.1.2 Common Enterprise Architecture Frameworks (EAFs).... Components of the Data Architecture EDM Dimension .......... Business Process Integration ................................................... 7.3.1 Benefits of Business Process Integration ..................... 223 224 225 229 230 234
7.2 7.3
11
Contents
7.4
7.5
7.6
7.7
7.8
7.9
Creating and Maintaining the Business Process Integration ............................... Enterprise Data Distribution Approach ................................... 7.4.1 General Factors to Consider When Developing and Choosing an Enterprise Data Distribution Approach.... 7.4.2 Sample Specific Company Enterprise Data Distribution Approach Requirements ................. 7.4.3 Other Technical Considerations .................................. Enterprise Data Model ............................................................ 7.5.1 The Enterprise Data Model Structure ......................... 7.5.2 Data Domains, Attributes, Elements, and Values......... 7.5.3 Business Value of the Enterprise Data Model ............. 7.5.4 Existing Enterprise Conceptual Data Model ................ Logical Data Model (LDM) ..................................................... 7.6.1 Business Value of the Domain Logical Data Model...... 7.6.2 Workforce Logical Data Modeling Process ................. 7.6.3 Material Master for Parts Logical Data Model ............. Application Architecture ......................................................... 7.7.1 Assumptions .............................................................. 7.7.2 Example Company Vision for Workforce Management Master Data ......................................... 7.7.3 Example Technical Releases for a Domain .................. 7.7.4 Sample Workforce Management Application Architecture Project Releases ..................................... Source and Target Mapping Model ......................................... 7.8.1 Business Value of Source and Target Mapping............. 7.8.2 Alternative Source and Target Mapping Model formats ............................................ Summary ................................................................................
7.3.2
235 237 242 243 244 245 245 246 248 250 252 254 255 259 260 262 263 264 266 268 271 271 273
8
Design: Data Standards ....................................................... 275
8.1 8.2 8.3 The Concept of Global Data Types .......................................... Data Standards EDM Dimension Components ....................... Business Object Definitions .................................................... 8.3.1 Sample Format of the Business Object Definition ........ 8.3.2 Using the Business Object Definition .......................... Data Dictionary ...................................................................... 8.4.1 Process to Develop Data Standards ............................ 8.4.2 Sample Data Standard Format .................................... 8.4.3 Data Dictionary from Standard SAP ............................ 8.4.4 Using the Data Dictionary .......................................... 275 277 278 278 280 280 281 282 283 285
8.4
12
Contents
8.5
8.6
8.7
Schema Standards .................................................................. 8.5.1 Schema or Hierarchy Basics ........................................ 8.5.2 Defining Schema Standards in Relation to EDM .......... 8.5.3 Schema Business Value .............................................. 8.5.4 Sample Organization Schema Standard ...................... 8.5.5 Applying a Schema Strategy ....................................... System of Record (SOR) .......................................................... 8.6.1 Purpose of the SOR Component ................................ 8.6.2 Creating the SOR ...................................................... 8.6.3 Sample SOR ............................................................... 8.6.4 Recommended SORs for Schemas .............................. 8.6.5 Business Value of the SOR ......................................... Summary ................................................................................
285 285 288 289 290 296 297 297 298 299 301 303 303
9
Governance Organization ..................................................... 305
9.1 Organization Structure Concepts ............................................ 9.1.1 SAP Organization Structure Terminology .................... 9.1.2 Key Concepts of Organization Design ........................ 9.1.3 Considerations when Establishing a Governance Organization Structure ......................... Components of the Governance Organization ......................... Enterprise Data Governance Organization ............................... 9.3.1 Standard Enterprise Data Governance Organization Roles ..................................................... 9.3.2 Enterprise Data Governance Organization Structure .... 9.3.3 Enterprise Data Governance Position Descriptions ...... Business Data Organization .................................................... 9.4.1 Business Data Organization Roles .............................. 9.4.2 Central versus Decentralized Business Data Organization Structure ......................... 9.4.3 Business Data Organization Structures ....................... 9.4.4 Business Data Organization Position Descriptions ....... Summary ................................................................................ 305 305 307 307 308 310 310 311 315 315 317 318 320 324 324
9.2 9.3
9.4
9.5
10 Governance Processes .......................................................... 327
10.1 10.2 10.3 SAP Process Decomposition ................................................... EDM Governance Process Types ............................................. Business Data Processes ......................................................... 10.3.1 Standard Elements of Business Data Processes ............ 327 329 330 331
13
Contents
10.4
10.5
10.3.2 Examples of Business Data Processes .......................... 10.3.3 Additional Considerations for Business Data Processes ............................................. Enterprise Data Governance Processes .................................... 10.4.1 Standard EDM Services .............................................. 10.4.2 Enterprise Data Governance Change Request Process ............................................. Summary ................................................................................
333 338 338 339 344 347
11 Realization: Deployment ...................................................... 349
11.1 EDM and ASAP Implementation Methodology ....................... 11.1.1 ASAP Basics ............................................................... 11.1.2 Typical Data Issues with ASAP Projects ...................... Elements of the Deployment EDM Dimension ........................ Change Management .............................................................. 11.3.1 Overview ................................................................... 11.3.2 A Model for Organization Transformation .................. 11.3.3 Transforming the Organization ................................... 11.3.4 Suggestions for Creating and Communicating the Message .............................................................. 11.3.5 Relating Change Management to Your EDM Program ............................................................ Standard Project Plans ............................................................ 11.4.1 EDM Strategy Development ....................................... 11.4.2 MDM Tool Data Repository Implementation ............. 11.4.3 MDM Roadmap Development Plan ........................... 11.4.4 Data Migration and Cleansing Implementation Plan.... Data Migration and Cleansing ................................................. 11.5.1 Common Terminology ................................................ 11.5.2 Process Overview ....................................................... 11.5.3 Approach ................................................................... 11.5.4 Outsourcing versus In-House Data Migration and Cleansing .................................... Managing EDM Data Design Documents ................................ 11.6.1 Design Document Style Guide .................................... 11.6.2 Design Document Repository in SAP Solution Manager ........................................... EDM-Related Business Standards ............................................ 11.7.1 SAP Current Approach for Business Standards ............. 11.7.2 Benefits and Business Value of Adopting Business Standards ..................................................... 350 350 350 353 354 354 355 356 357 358 359 359 360 361 362 363 363 365 366 368 370 370 370 372 373 373
11.2 11.3
11.4
11.5
11.6
11.7
14
Contents
11.8
11.9
Special Deployment Issues ...................................................... 11.8.1 Integration to Business Intelligence (BI) Strategy ......... 11.8.2 Globalization ............................................................. 11.8.3 Regulatory Considerations .......................................... 11.8.4 Security Plan Requirements ........................................ Summary ...............................................................................
374 374 377 377 380 384
12 Realization: Technology ....................................................... 385
12.1 12.2 12.3 12.4 EDM Reference Technical Architecture ................................... Components of the Realization: Technology EDM Dimension .................................................. EDM-Related Technology Functions Reference List ................ EDM-Related Applications Inventory ...................................... 12.4.1 SAP ERP and Other Enterprise Applications ............... 12.4.2 Reverse Business Engineer (RBE) ................................ 12.4.3 Legacy System Migration Workbench (LSMW) ............ 12.4.4 SAP NetWeaver Process Integration (PI) .................... 12.4.5 SAP Composition Environment (CE) ........................... 12.4.6 SAP Solution Manager ............................................... 12.4.7 SAP NetWeaver System Landscape Directory (SLD)..... 12.4.8 ARIS for NetWeaver and Other Enterprise Architecture Tools .................................... 12.4.9 SAP Solution Composer ............................................. 12.4.10 Business Object Repository (BOR) Browser ................ 12.4.11 Enterprise Services Workplace (ESW) ......................... 12.4.12 SAP NetWeaver Business Intelligence (BI) ................. 12.4.13 SAP Enterprise Services Repository (ESR) ................... Data Profiling Requirements and Evaluation .......................... 12.5.1 Basic Features of a Data Profiling Tool ....................... 12.5.2 Standard Analyses for Data Profiling Tools ................. 12.5.3 Analytical Methods for Data Profiling ......................... 12.5.4 SAP and Other Data Profiling Tools ............................ EDR Requirements and Evaluation .......................................... 12.6.1 General Capabilities Recommended for an SAP EDR ... 12.6.2 Capabilities Not Recommended for Use for the Company EDR ................................................ 12.6.3 Important Factors to Consider When Developing and Choosing EDR Options ........................................ 12.6.4 Standard Features of an EDR ...................................... 12.6.5 Options for an EDR ................................................... 386 388 389 394 395 396 398 400 401 403 405 407 410 412 414 415 417 419 419 420 421 422 422 423 425 427 428 430
12.5
12.6
15
Contents
SAP NetWeaver MDM Basics ................................................. 12.7.1 Basic Modules of the SAP NetWeaver MDM Tool ....... 12.7.2 EDR Specifically in SAP NetWeaver MDM .................. 12.7.3 The MDM Console Main Functions ............................ 12.7.4 Functions of the MDM Repository ............................. 12.7.5 MDM Data Manager Modes ...................................... 12.7.6 MDM Data Field Types .............................................. 12.7.7 Basics of Taxonomies and Attributes .......................... 12.7.8 SAP NetWeaver MDM Repository Table Types ........... 12.8 EDR Modeling Using an SAP NetWeaver MDM Repository .... 12.8.1 Designing LDMs with SAP NetWeaver MDM ............. 12.8.2 Sample LDM Using SAP NetWeaver MDM ................ 12.8.3 Checking Rules in SAP NetWeaver MDM: Validations ................................................................. 12.8.4 Designing a Taxonomy ............................................... 12.8.5 Leveraging SAP-Supplied Repositories for ERP and Other Enterprise Application Integration ....... 12.9 SAP NetWeaver MDM Advanced Technical Infrastructure Topics ............................................................... 12.9.1 Sizing SAP NetWeaver MDM ..................................... 12.9.2 Master and Slave Repositories .................................... 12.9.3 Solution Landscape for SAP NetWeaver MDM ............ 12.9.4 Building Workflow for SAP NetWeaver MDM Processes ......................................................... 12.9.5 SAP NetWeaver MDM Backups and Archiving ............ 12.9.6 Portal Integration ....................................................... 12.9.7 SAP NetWeaver BI Integration ................................... 12.9.8 Users and Authorization ............................................. 12.9.9 Collaboration Through Locking and Version Control.... 12.9.10 Security in SAP NetWeaver MDM .............................. 12.10 Technology Recommendations for EDM Dimensions and Components ........................................................................... 12.11 Summary ...............................................................................
12.7
433 434 437 439 439 441 441 443 443 445 446 453 457 458 460 464 464 465 466 469 470 471 472 472 473 473 475 475
SECTION III
13 Building an EDM Program ................................................... 479
13.1 13.2 Common Approaches for EDM Projects .................................. 479 Beginning with the End in Mind ............................................. 480 13.2.1 Ideal Sequence for Applying the EDM Methodology ... 482
16
Contents
13.3
13.4
13.5
13.6
13.7
13.8
13.2.2 Expectations of an EDM Strategy Project ................... 13.2.3 Enterprise-wide versus Domain-Specific Deliverables...................................... 13.2.4 Sequence of Successive Projects to Achieve a Sustainable EDM Program ..................... MDM Roadmap Program Plan ................................................ 13.3.1 Project Team Organization ......................................... 13.3.2 Project Roles and Responsibilities .............................. 13.3.3 Special Considerations for Project Deliverables ........... 13.3.4 Watch Items .............................................................. Independent EDM Strategy Projects ....................................... 13.4.1 Project Team Organization ......................................... 13.4.2 Project Roles and Responsibilities .............................. 13.4.3 Project Team Communications ................................... 13.4.4 Special Considerations for Deliverables ...................... 13.4.5 Watch Items .............................................................. Support Large Enterprise Application Implementation ............ 13.5.1 Project Team Organization ......................................... 13.5.2 Project Roles and Responsibilities .............................. 13.5.3 Special Consideration for Deliverables in Blueprinting ........................................................... 13.5.4 Watch Items .............................................................. Focused Internal Business Objective ....................................... 13.6.1 Project Team Organization ......................................... 13.6.2 Project Roles and Responsibilities .............................. 13.6.3 Special Considerations for Deliverables ...................... 13.6.4 Watch Items .............................................................. Commercial Initiatives ............................................................ 13.7.1 Project Team Organization ......................................... 13.7.2 Project Roles and Responsibilities .............................. 13.7.3 Special Considerations for Deliverables ...................... 13.7.4 Watch Items .............................................................. Summary ...............................................................................
483 483 486 486 487 488 488 489 489 490 491 492 492 493 494 494 495 496 496 497 497 498 499 499 500 500 501 501 501 501
14 EDM for Materials ................................................................ 503
14.1 Introduction to Direct Materials ............................................. 14.1.1 Definition and Variants in Industry ............................. 14.1.2 Types of Direct Materials ........................................... 14.1.3 Typical Products and Their Metrics ............................. 14.1.4 Leverage of Product Design ....................................... 504 504 504 507 508
17
Contents
14.2 14.3 14.4 14.5
14.6
14.7
Major Roles in Direct Materials .............................................. Typical Product Development Process .................................... General MRO Items versus Direct Materials ............................ Defining World-Class Direct Materials Content ....................... 14.5.1 Required Content Features ......................................... 14.5.2 Should Have Content Features ................................... 14.5.3 Nice to Have Content Features ................................... Bottlenecks to Efficient Materials Management ...................... 14.6.1 Synchronizing Catalog Items to the Solid Model and to Specification Documents.... 14.6.2 Mapping Engineering Specifications to the Manufacturer and to the Supplier ........................ 14.6.3 Seamless Guided Searching from Individual out to Open Internet ................................................. 14.6.4 Product Data Interoperability ..................................... 14.6.5 Coordinating the Manufacturing and Design BOMs .... 14.6.6 Part Renumbering ...................................................... 14.6.7 Managing Direct Materials Data Structures ................ Summary ................................................................................
508 510 512 514 514 515 516 517 517 518 519 520 521 522 524 525
15 EDM for a Large ERP or Enterprise Application Project ...... 527
15.1 Case Study Background Information ....................................... 15.1.1 Case Study Company .................................................. 15.1.2 Project Objective ....................................................... 15.1.3 EDM Involvement ...................................................... ERP Project Organization ........................................................ Interfacing with Vertical Workstreams .................................... 15.3.1 Vertical Workstream Coordinator Role ....................... 15.3.2 Information Collected by Vertical Workstream Coordinators .............................................................. 15.3.3 EDM Team Assignments: EDM Core Team to Vertical Workstreams ............................................. 15.3.4 Responsibilities Between the Horizontal EDM Team and Vertical Workstreams .......................................... 15.3.5 Involvement of Vertical Workstreams by Master Data Object ............................................... EDM Project Deliverables ....................................................... 15.4.1 Shared Deliverables ................................................... 15.4.2 EDM Team Deliverables ............................................ EDM Team Involvement in ERP Project Workshops ................ 527 527 528 528 528 530 530 531 532 533 535 536 536 537 538
15.2 15.3
15.4
15.5
18
Contents
15.6 15.7
15.5.1 Assumptions and Preparation ..................................... 15.5.2 Grouping the ERP Implementation Workshops in Terms of EDM Impact ............................................ 15.5.3 Mapping Deliverables to Cycles ................................. Conclusion and Recommendations ......................................... Summary ................................................................................
539 539 540 541 542
16 Globalization Within an EDM Strategy ............................... 543
16.1 16.2 16.3 Issues to Consider ................................................................... Types of Globalization Conversions ......................................... Language Master Data in SAP Applications ............................. 16.3.1 Attributes to Consider When Examining Globalization 16.3.2 Master Data Language Limitations in SAP tools........... 16.3.3 Employee Master Data Example ................................. 16.3.4 Example of Language-Dependent Objects in SAP Applications ............................................................... Typical Options for Globalization and Language ..................... 16.4.1 Best Practices for Localization .................................... 16.4.2 Globalization Strategy ................................................ Conclusion and General Recommendations ............................ Summary ................................................................................ 543 544 545 545 546 546 547 548 550 551 554 555
16.4
16.5 16.6
17 The Future of Enterprise Data Management ....................... 557
17.1 17.2 17.3 17.4 17.5 17.6 17.7 17.8 Business and Technology Drivers ............................................ Increased Mergers, Acquisitions, and Partnerships .................. Increased Scorecards and Metrics ........................................... Increased Awareness of the Impact of Data Quality ................ Enterprise Service-Oriented Architectures ............................... Enterprise Architecture ........................................................... Business Process Management (BPM) ..................................... Summary ................................................................................ 557 558 558 559 559 560 561 561
Appendix .................................................................................... 563
A B C References ........................................................................................ 565 Glossary ............................................................................................ 567 Author Biography .............................................................................. 575
Index ......................................................................................................... 577
19
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 (enterprise SOA). In this chapter, we will briefly cover enterprise SOA and the following concepts 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 of Record (SORs) First, let’s examine the benefits of enterprise SOA, balancing the ability to be agile with continuous innovation while controlling costs.
3.1
Benefits of Enterprise SOA
The vision of enterprise SOA is to help your company both innovate and react quickly to market forces while still controlling costs. Traditional methods provide many benefits, but to separate yourself from the competition in the future, you can take advantage of these benefits. Enterprise SOA is one way for you to achieve that goal for innovation, faster reaction time, and controlling technology costs. Figure 3.1 shows a general diagram of an enterprise SOA application.
79
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
Analytics Composite Applications
Enterprise Services Repository
SAP NetWeaver Business Process Platform
Partner Partner
SAP SAP
Legacy Legacy 3rd 3rd
Party
SAP SAP R/3 R/3
Platform Platform Process Components Process Components
Figure 3.1 General Diagram of an Enterprise SOA Application
The following are some external drivers motivating companies like yours to pursue enterprise SOA:
Need to differentiate
To compete and remain profitable, competing on cost is not enough. You must continually differentiate your business by focusing on your core competencies.
Total customer offering requirement
Providing a standalone product is not enough. Customers require a total experience with your product, including services for the product. When Apple developed the iPod, they not only thought about the music player, but the entire value chain of services around it.
Information overload
You have a lot of data in your company. It is important to aggregate disparate information and to be able find the right information to determine trends and react more quickly.
80
Interaction of Enterprise SOA and Master Data
3.3
Growing domestic and international regulatory compliance mandates
Businesses must increasingly meet additional regulations for security, privacy, and financial practices. In addition to meeting the standards, you must prove how you derived the results and that you provide controls to ensure that you will meet the standards going forward. These are some of the business pressures and opportunities that a company must face. Enterprise SOA provides tools and techniques to respond to those challenges while keeping costs under control.
3.2
Basics of Enterprise SOA
Enterprise SOA is how SAP does Web services. SAP has designed enterprise SOA to be compatible with the industry SOA standards, but went beyond this to develop an architecture that allows you to leverage your existing infrastructure and allows you to truly scale SOA in an orderly way. Figure 3.2 illustrates business process management with enterprise SOA. Enterprise SOA is a standard SOA architecture with Enterprise Services rather than just building Web services from the ground up. Also, enterprise SOA is designed to leverage complex landscapes with a mix of packaged applications, 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 you can see the increased requirements for harmonized master data. Enterprise data needs to be shared across applications and Enterprise Services. In addition, scaling enterprise SOA requires a logical and even possibly physical decoupling of master data from the applications. Referring to Figure 3.3, you can see one landscape comprised of two applications. One business scenario crosses the two applications and transactions or business documents are being passed from one application to another. For the business documents or transactions to be understood or have proper context, the master data in both systems must be semantically and possibly even structurally equivalent. As a result, the master data in both applications must be harmonized. It is even more efficient if there is just one SOR for each master data BO. This single SOR is preferred for all business data objects.
81
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
Analyze and Discover
2
1
Manage and Optimize
Model and Build
3
Enterprise Service Repository Compose and Orchestrate
5
Integrate and Deploy
4
1
• 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
2
• Design and model business objects (BOs) • Implement new business logic • Model and build UIs • Create new services reusing existing assets and publish to ESR
3
• Compose views by reusing implemented services and BOs • Compose and orchestrate services and views to form new business process
4
• Package and deploy application • Configure runtime (adapt to IT landscape) • Test and validate application • Execute application
5
• Manage change & maintain version (governance) • Monitor service execution (e.g. performance, availability, process progress, events)
Figure 3.2 Business Process Management with Enterprise SOA
82
Basic Requirements for Enterprise Services
3.4
By decoupling the applications from the BOs, you can manage the master data and their metadata centrally. With the addition of Enterprise Services, this requirement for standardized master data and enterprise data is even more imperative.
System Landscape System A A System Business scenario System B B System
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
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 of functionality. The following are a few of examples of possible Enterprise Services 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 service, which we call an “Enterprise Service" in the context of enterprise SOA.
83
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
SAP’s literature for enterprise SOA provides the following explanation and descriptions for Enterprise Services: Enterprise Services have all of the characteristics of Web services plus additional requirements, and the following characteristics differentiate Enterprise Services from regular Web services:
Business semantics
Enterprise Services are structured according to a harmonized enterprise model based on process components, BOs and global data types (GDTs). Quality and stability: Enterprise Services ensure a stable interface for future versions, providing backward compatibility. Their behavior, prerequisites, dependencies of usage, and configuration possibilities are well documented.
Standards
Enterprise services are based on open standards. The interfaces are described according to the Web Services Description Language (WSDL). WSDL is the industry standard for defining Web services. They are created by using GDTs, which are based on the United Nations CEFACT standards organization Core Component Technical Specification (CCTS) standard. SAP literature recommends that large enterprise customers adopt the current release of the SAP ECC ERP application. Midsize customers should start with an SAP All-in-One solution. The SAP NetWeaver platform powers both solutions. An enterprise SOA-compatible landscape enables customers to extend their business solutions quickly and easily to meet their unique needs. Customers will still rely on the existing and stable functionality provided by SAP solutions. To fulfill a specific industry requirement or business need, you could take advantage of Enterprise Services provided by SAP or strategic business partners through the Enterprise Services Workplace (ESW), as shown in Figure 3.4. With these Enterprise Services, customers can rapidly enhance their existing business processes or develop and deploy new applications to handle specific business processes. This extends and increases the value of SAP solutions. An example of packages of Enterprise Services is the electronic bill presentment and payment (EBPP) Enterprise Services bundle. It bundles Enterprise Services that support authorization with settlement processes that are used to communicate with credit card processors. Any company that handles business-to-consumer interactions that require credit card authorization and payments can take advantage of these Enterprise Services.
84
Business Objects in Enterprise SOA
3.5
ESR
Enterprise Architect •ES Packages •Enterprise Services •Education Wiki )
Business Process Expert
E S Workplac e
Applications, e.g. Enhancement Packages for SAP ERP ECC
Hosted System on SDN
Figure 3.4 Discovering Enterprise Services in the Enterprise Services Workplace (ESW)
For More Information
If you are an SAP customer, you can find information about service-enabled scenarios 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 Enterprise Services Wiki (www.sdn.sap.com/irj/sdn/share-bp), along with detailed documentation of the services offered for specific scenarios. Because the Enterprise Services Wiki allows users to add and edit content collectively, it promotes content sharing among a community of SAP developers, customers, and partners using Enterprise Services to integrate, compose, and deploy applications.
3.5
Business Objects in Enterprise SOA
In enterprise SOA, a BO represents a specific view on well-defined business content. This business content is generally accepted and well known in the business world. At the highest level in enterprise SOA, BOs are classified into two groups:
85
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
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 stored in the Enterprise Services Repository (ESR), and implemented free of redundancies. BO governance process, guidelines, and rules are defined in the ESR. Examples of BOs include sales order, supplier invoice, or outbound delivery. Internal application system tables are not considered BOs. Now, let’s examine the structure of an Enterprise Service, focusing on the enterprise data or BOs.
3.6
Anatomy of an Enterprise Service
All Enterprise Services have a standard repeatable pattern or structure. This pattern or structure supports uniformity and a foundation for governance. Following are the standard rules that govern all Enterprise Services:
BO encapsulation
A BO is defined only once. Also, there is no duplication of BOs.
BO relationship to process components
A process component contains a set of semantically related BOs.
Integration scenarios
Integration scenarios model the interaction between process components.
Service operation
A service operation belongs to exactly one BO. One BO has multiple operations.
Service interface
A service interface groups service operations together.
Global data type (GDT)
GDTs are reusable elements stored in a common dictionary. Several GDTs form message types. An Enterprise Service is a callable entity that provides business functionality and is published by SAP in the ESR. Enterprise Services are structured according to a harmonized enterprise model based on GDTs, process components, and BOs. They are well documented, guarantee quality and stability, and are based on open standards. The following are additional requirements for an Enterprise Service over a Web service:
86
The Enterprise SOA Metamodel
3.7
Structured according to harmonized enterprise model (process components, 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 of Enterprise Services make life easier for service consumers, such as business process experts, when they may be designing a new business process for your company. SAP has already put many product and process standards into place that also apply to Enterprise Services. For Enterprise Services, additional design guidelines and patterns exist on different 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 look at the pattern or metamodel of enterprise SOA. This describes how Enterprise Services and enterprise data work within enterprise SOA.
3.7
The Enterprise SOA Metamodel
The enterprise SOA metamodel is the consistent relationship or pattern of processes, services, and BOs. BOs are at the heart of this model. You should also understand several other key entities so that you can grasp the standard
87
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
pattern of enterprise SOA, and, as a result, the impact of BOs on enterprise SOA. They include service operations, service interfaces, process components, and BOs, as shown in Figure 3.5.
Modular, context independent, reusable pieces of software that expose their functionalities as services. Contains, at least,one business object. e.g. Price Master Data Management Process Component 1 1..* Process Component Specific view on well-defined and outlined business content. e.g. Sales Price Information 0..1 0..1 1..* 1..* Service Description based on WSDL & XSD
Business Object Model Service * 1 Service Interface 1 1..* Operation * 1..* Data Type (Message Type) Definition: XML Schema * references 1
Global Data Types
Figure 3.5 The Enterprise SOA Metamodel
Service operations logically belong to service interfaces, and service interfaces belong to process components. Service interfaces adhere to a certain pattern, which makes it more intuitive to quickly find and identify Enterprise Services. A manage-type interface typically incorporates create, read, update and delete types of service operations. For instance, the Create Sales Order service operation belongs to the Manage Sales Order service interface, and the Manage Sales Order service interface belongs to the Sales Order Processing process component.
88
The Enterprise SOA Metamodel
3.7
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 logical deployment units to process components to BOs with service interfaces and service interfaces to service operations, as illustrated in Figure 3.6. Let’s look in more detail at the concept of logical deployment units.
Deployment unit – level one
Due It em em Process ing Due It Process ing
Due Due Payment Payment approved approved Trade Trade Rec eivables Rec eivables Payables ... Payables ... Process component –level two (drilldown in detailed model)
approved approved
Trade Trade Receivables Receivables Payables.. Payables....
approved approved
Due Due Clearing Clearing approved approved
Business object – level three
VAT VAT Declaration Declaration
new new
approved
Figure 3.6 Basic Entities of an Application
Logical Deployment Units A logical deployment unit is a set of process components that can be operated on a separate system, isolated from other process components. Important things 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 can be broader.
89
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
With regard to characteristics, in a given customer landscape, the following 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 connected to multiple instances of other logical deployment units. A deployment unit can be ignored in an application configuration (if inactive in the current system).
Process Components Process components can be seen as the building blocks of each enterprise SOA solution. They are modular, context independent, reusable pieces of software that expose their functionalities as services (see Figure 3.7). A process component contains at least one BO.
Process Component
Supplier Invoice Processing
Supplier Invoice Business Object Service Interface Service Operation Supplier_Invoicing_In Create Supplier Invoice Cancel Supplier Invoice
Message Type
Supplier Invoice Cancellation Execution Request
derived from
Invoice Accounting Cancellation Request Message Type
derived from
Global Data Types
Figure 3.7 Drilling Down on the Details of a Process Component
90
The Enterprise SOA Metamodel
3.7
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 reuse element in integration scenarios Fit into a typical customer organization Belong to exactly one deployment unit (discussed in more detail in the next section)
BOs BOs are logical objects of significance to the business. They represent a class of entities with common characteristics and common behaviors describing well-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 of BOs: BO purchase order BO template: maximal template of product with all attributes, unavailable for use in the Logical Deployment Unit (LDU) Dependent object: substructure of BO to be reused in another BO address Business foundation object: BO in foundation layer and business partner BO identification and all BO models and data types run through a governance process, including review, final approval, and released documentation BOs are encapsulated by a process component. In an application, a BO is defined only once in one process component. A process component can define one or more BOs.
91
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
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. Consequently, the BO sales order, for example, describes the category of all sales orders and not a single sales order instance.
Service Interfaces A service interface is a named grouping of operations. The service interface patterns commonly used are Read, Create, Update, Manage, and Delete.
Service Operations The highest granularity of an entity type is the service operation. When it comes to the implementation of a composite application, the business process expert or the software architect should have the desired single Enterprise Service operations and the orchestration in mind. This is where the developer needs detailed technical information to orchestrate and compose the Enterprise Services. You can browse the ESW to help you find a particular service operation. To do so, find and display the WSDL for a particular service operation, for our example, the Create Sales Order service operation. From the list of the process components in ERP, select the Sales Order Processing process component. This results in a list of Enterprise Service interfaces that support this process component.
Global Data Type (GDT) A GDT is an SAP system-wide defined data type with meaning, structure, and values oriented on industry standards, where available. Referring to the enterprise SOA metamodel shown in Figure 3.8, you can see how process components, service interfaces, service operations, and GDTs are related. Let’s now look at GDTs, and later on BOs, in more detail with reference to enterprise SOA.
92
GDTs in Enterprise SOA
3.8
Credit Management Credit Management Credit Agency Report approved Credit Agency Identifier Credit Management Account approved
Deployment unit
Drilldown from BO map to BO model
Business object model
approved
Business object
approved
Process component
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 with business content. They are defined in accordance to industry standards and offer customers a way to use one common data structure. Figure 3.9 shows an example of a GDT. GDTs are elemental data structures that are used to build up more complex BOs. For the example, there is at SAP-defined GDT called Price, 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 real number. The following are standard characteristics for GDTs in enterprise SOA: Conform to the following open standards: ISO 15000-5 and UN/CEFACT CCTS Defined in the ESR SAP sytem-wide approved with reference to the governance process for Process Integration Content (SAP PIC Process)
93
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
Semantic building blocks for service definition and interfaces for reuse ESR-provided functionality to define CCTS data types to allow for customer-specific GDTs or to extend or adapt SAP’s GDTs
1 1..*
Global Data Type (SAP) 1..* 1 Core Data Type (CCTS) 1..*
Example: Price
Example: Currency
1 Primitive Data Example: float, string, Type (XSD) token, binary
Figure 3.9 Example of a GDT
UN/CEFACT CCTS, shown in Figure 3.10, is a methodology for developing a common set of semantic building blocks that represents the general types of business 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 other aggregated GDTs or of so-called core data types — the smallest unit of this type of modeling approach. Currently, more than 20 core data types are defined. The following two are the most prominent:
Code
Represents a definitive value, a method or a property description in an abbreviated or language-independent form. The possible values are defined by a code list. Examples are currency code or country code.
Identifier
Represents BO node instances. The possible values are given by keys of BO node instances. From primitive GDTs, you will build up more complex BO data structures.
94
Business Object Structures in Enterprise SOA
3.9
Business Object • PurchaseOrder 1 n Business Object Node • PurchaseOrderParty 1 • PurchaseOrder DeliveryTerms 1 Node Data Type • PurchaseOrderParty Elements • PurchaseOrder DeliveryTerms Elements n
B2B / A2A - Interface / Service Operation n 1 Semantic Structure global Usage specific Data Typing • PurchaseOrdering_In • PurchaseOrdering_Out
Message Type n • PurchaseOrderRequest • PurchaseOrder ChangeRequest
1 B2B / A2A Message Data Type n • PurchaseOrderMessage • Invoice Message
Global Data Type n • • • • • • • • • • Amount Binary Object Code Date Time Identifier Indicator Measure Numeric Quantity Text 1 CCTS Core Data Type n 1 W3C Data Type
• Delivery Terms • Address • ProductID
• float • string
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, providing the major portion of application business logic. Although there are exceptions (technical objects such as Workflow Item, for instance), a BO is commonly understood to be an independently viable business entity with unique, identifiable instances. This entity includes state and behavior and is accessible from other BOs or service implementations exclusively through its core services.
no Business Semantics
Business Semantics
95
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
BO nodes can also have additional identifiers called alternative keys. Alternative keys are defined by data structures included in the elements data type of the BO node. Alternative keys can be used to create foreign key associations between BOs. The underlying elements data type of a BO node is not permitted to be arbitrarily complex. It must be essentially flat, which means it cannot contain table-like substructures. This ensures that the BO node’s set of attributes can always be mapped to a structure composed solely of scalar data types. More complex BO structures may be constructed using the composition mechanism for BO nodes as shown in Figure 3.11. A BO’s tree of nodes is defined in ESR by compositional associations (compositions for short) between the respective parent and child nodes. In Figure 3.11, SalesOrderItem is a child node of SalesOrder. A compositional association represents a strong semantic relationship: One or more instances of the child node depend on the existence of one instance of the parent node. One instance of a parent node may have zero, one, or multiple associated instances of a corresponding child node. In general, semantic relationships between BO nodes are defined in the Enterprise Services Inventory (ESI) by unidirectional, binary, named associations. Inside a BO, an arbitrary number of associations between the different nodes are possible in addition to the (BO internal) compositional associations, which must be present to build the BO’s tree of nodes. Relations between different BOs can be established only on the node level and only by using associations between their nodes as shown in Figure 3.11. Very often, an association between nodes is a “foreign key relation” in the sense that one or more attributes of the source node completely identify the associated target node instances. ESR offers corresponding modeling and execution capabilities.
Note
The Enterprise Services Inventory (ESI) is object-based, not object-oriented. ESI is a directory that will contain all of the Enterprise Services and variants for use in your company. It deals with the concepts of BOs, nodes, and instances but does not represent these concepts in a one-to-one correspondence with object-oriented classes and instances. As a result, not all object-oriented concepts are available 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 is structurally defined by one underlying GDT, the so-called elements data type. BO nodes and their corresponding elements data type are depicted as identical entities because this more closely reflects the common understanding. Each BO node implicitly inherits one technical identifier represented by the generic GDT NodeID.
96
Other Critical Enterprise Data Issues
3.10
“
Each business object is modeled as a hierarchical structure of nodes and each business object node is made up of data fields. BO CustomerInvoice Customer Invoice Item Item Product
BO Material Material
BO Service Service Product
Taxation Terms
Customer Party BO Customer Customer
Figure 3.11 Conceptual Version of BO Nodes
Now that you understand the general principles of BOs, the following section 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 for enterprise SOA. They are important, even if you choose to not implement a SOA strategy such as enterprise SOA. They become critical as you try to scale enterprise SOA and extract the business benefits from enterprise SOA. The challenges 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 enterprise SOA and how that affects the design of enterprise data, such as BOs.
97
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
3.10.1 Decoupling Layers in Enterprise SOA
A major benefit of enterprise SOA is decoupling the layers. BOs are one of the most important layers to manage. Generally, as you move farther down the architecture, the dependencies grow, and changes are much more critical. Changes to BOs have a lot of leverage to services, applications, and eventually 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 existing entities on each layer, especially impacts on the BOs.
Role 1
COMPOSITE APPLICATION
Role 2
Workcenter Composite Process Actions
Step 1
Step 2
Step 3
Step 4
UI
UI
UI
Action -UI Business Objects, Services
Remote Services
Business Objects Local Remote
Local Services
Exchange Infrastructure Services CRM Services BW Services ERP Service Enablement Systems
BACKEND
DB
Services Actions BO model
DB
Database
DB
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 designing Enterprise Services called the Process Integration Content (PIC) process. PIC is the main process for the design and governance of Enterprise Services.
98
Other Critical Enterprise Data Issues
3.10
The four steps for the PIC process are PIC 0, PIC 1, PIC 2, and PIC 3, as shown in Figure 3.13. The first step, PIC 0, is the most critical scoping impact step to semantically 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 the design of the BO nodes, GDTs within the BO node diagram, and finally the service operations and messages data types that are used to access the BOs within the process components. Next, let’s look at designing BO states, SOR management, and managing metadata.
PIC 0: Business Objects and Operations Identification Semantically harmonized definitions cross solutions Pic 1 Pic 2 Pic 3 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 “How to ” guidelines GDT: Global Data Types Name, Definition, Structure,Value Ranges
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 clearly defining the BO states, tracking process sequence is less important. Defining the states and their links across domains, such as sales, design, manufacturing, and so on, is important as well. Figure 3.14 shows the lifecycle of a material including the services and when they are available for that BO. At each of the points where services are available there are major state changes for the material.
3.10.4 System of Record (SOR) Management
The ESR may help with this challenge. You need to track the preferred SOR or main reference location for the BOs.
3.10.5 Managing Metadata
Metadata needs to be managed so that it is readily accessible and uniform across the enterprise. There are many types of metadata, such as attribute
99
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
definitions, business rules, service definitions, schemas, mappings, and so on. Reusability of Enterprise Services and BOs will rely on standardized metadata. These are just a few additional enterprise data issues that you should consider as you prepare your company for enterprise SOA.
• HTS Compliance Services for Materials • EH&S Compliance • Approval • Tracking • On-Going Reporting • Preference Management • Engineering • Procurement • Spend Analysis
Lifespan of Services
Pre-Launch
Inactive
• New Part Introduction • Define Specification • Request and Evaluate • Issue Intern. Part Number • Design Buy • Build\Acquire Math Model
• Reuse & Subscribe • Reliability & Testing • Find Replacements • Find Other Sources • Mfg Part Change Notices
• Where Used Analysis • End of Life Mgmt. • EOL Notices • BOM Validation • End of Life Predictability • EOL Buy • Final Inventory • DFM-Reengineering • Regenotiate • Int. Channel Mgmt.
Launch
Growth
Maturity
• Maintain Available to Purchase Catalogs • User Searches • Maintain Approved Supplies
• In-Service Management • Tracking • Field Notices • Maintenance\Replacement • Synchronize Part Data with ERP • Synchronize Part Data with PLM • View Comprehensive Part History
Change of Object State
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 SOA metamodel and process components are designed to manage BOs. These BOs are constructed using GDTs or standard definitions for the elements within the BO for attributes, such as a date, purchase order ID, or address. These GDTs are used in one or more BOs and messages used to access these BOs. As a result, when you are developing an EDM Program, you should consider the following to lay a foundation for future enterprise SOA:
100
Recommendations for Managing Enterprise Data in Preparation for Enterprise SOA
3.11
Architect each type or domain of enterprise data independently.
Each domain will have different business requirements, application landscapes, and data flow diagrams. Try to have a preferred method for the creation and distribution of enterprise data, but be prepared to pragmatically design each differently.
Continually decouple enterprise data from applications.
Enterprise SOA and other SOA strategies take advantage of the loose coupling of the layers. Loose coupling of BOs will be important to scaling and leveraging the business benefits of enterprise SOA.
Start to introduce BO node diagrams when modeling BOs.
Using some form of entity relationship diagramming is common when modeling your enterprise data objects. Start to introduce and design your Logical Data Models (LDMs) using the BO node diagrams as defined in the UN\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. New tools 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 the object states across domains and how they are linked together. To maintain flexibility in Enterprise Services, BO actions and states must be clearly defined. By defining states, process sequence tracking becomes less important 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 business strategy. This company business strategy will drive requirements for business processes and Enterprise Services. The selection of Enteprise Services will require that you design the related BOs.
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 align business processes, or when you have many business process variants so that it is difficult to come up with one set of global processes. Aligning the enterprise data will help you begin to align those business processes without having to standardize on one process.
Resist the desire to create one repository for all metadata.
Metadata is more important, including metadata for BO definitions, serv-
101
3
The Strategic Role of Enterprise Data in an Enterprise Service-Oriented Architecture
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 to maintain that metadata. When trying to aggregate all metadata, you lose the business or technical context of the metadata.
3.12
Summary
This chapter provided you with a brief explanation of enterprise SOA and the issues around enterprise data that you should consider to prepare your company for this future architecture. Preparing for enterprise SOA is especially important if your EDM Program is partially supported.
Note
This chapter is not meant to replace detailed design text on enterprise SOA. You need to learn many more details to fully understand enterprise SOA. Refer to www.sdn.sap.com/irj/ sdn/enterprisesoa for more information.
Now that we have looked into the future requirements for your enterprise data, let’s get back to your immediate needs to build a business case for EDM. In Chapter 4, you will see the components of a business case, including many EDM examples.
102
Index
A
A2i 43 ABAP 398 Accelerated SAP 349 ACORD 373 Ad-hoc reporting 390 Aerospace and Defense 503 AIAG 373 Alternative keys 96 Application Architecture 229, 260, 423 Application-to-application data delivery 392 Approved Vendor List 524 ARIS for NetWeaver 236, 390, 391, 393, 407 ASAP 494, 496, 527 Blueprint phase 539 Blueprint workshops 539 Data issues 350 Project 372 Aspect development 41 Assertion testing 421 ASUG\EDM survey 103, 559 Attributes versus fields 449 Automotive 503 Roles 317 Structure 320 Variant scenarios 321 Business data processes 230, 330, 470, 495 Examples 333 Business driver 557 Business Intelligence strategy 374 Business logic 426 Business maps 410 Business object 85, 91, 95, 278, 559 Design governance 98 Encapsulation 86 Lifecycle 559 Models 415 Node diagram 99, 101 Nodes 96 States 99 Structures 95 Template 91 Business object definition 277, 278 How to use 280 Sample format 278 Business Object Repository (BOR) 412 Browser 412 Business process Management 230, 561 Objects 86 Repository 404 Business Process Integration 229 Uses 234 Business scenario 328 Group 328 Maps 410 Business strategy 32, 560 Business strategy integration 57, 67, 390, 482 Components 123
B
BAPI 398, 412 Basics of taxonomy 443 Batch profiling 419 Benchmarking study metrics 138 BI 415 Bill of Materials (BOM) 506, 521 BPM 561 Business case 127 Case studies 139 Management 390 Business Data Organization 309, 315, 495 Centralized versus decentralized 318 Positions 324
C
CAD 40, 520 Cadis 41
577
Index
Catalog search 429 Catalog search functionality 392 CCTS 84, 93 CE 401 CEFACT 84 Central MDM 467 Change management 353, 354 Chemicals 503 CIDX 373 Classification 363, 438 Classification of data 44 Cleansing 363 Client system 458 COBIT 216 Column Property Analysis 396, 420 Common Information Model 405 Company business strategy Basics 121 Integration 121 Compelling events 486 Complex configured items 506 Complex Data Rule Analysis 421 Complex entities 159, 423 Component & Supplier Management 41 Composite Application Framework 401 Conditional master data 396, 452 Configuration data 45 Configured-to-order 504, 505 Consolidated MDM 467 Consumer products 503 Control Chart 173 Control objectives 217 Controls Access 219 Configuration 219 Monitoring 220 Procedural 220 Core Component Technical Specification 84, 275, 373 Core Data Type 93 Cost avoidance 36 Cost containment 497 Cost of goods sold 504 Cross-functional team 494, 498 Cross-Industry Solution Maps 410 CRUD Matrix 230 CSM 41 Customer data integration 53, 500
D
DARPA RaDEO 508 Data Acquisition 415 Architecture 58, 71, 482, 501 Attributes 246 Champion 164 Cleansing and harmonization 392 Custodian 165 Distribution 416 Domains 246, 248 Elements 247 Entities 246 Fields 247 Governance processes 425 Mart 393 Modeling 391, 415 Owner 165 Pool 52 Profiling 189, 388, 390, 419 Schematic 272 Subject area 246 Sub-subject area 246 Values 247 Data analysis 184 Complex rules 192 test plan 190 Data defects 174 Defect 174 Error 174 Mistake 174 Released defect 174 Data Dictionary 277, 280, 496 How to use 285 Data Migration and Cleansing 76, 353, 363 Factors to consider 368 Outsourcing versus in-house 368 Process overview 365 Data quality 32 Accessibility 179 Accuracy 178 Availability 179 Committee chair 164 Completeness 178 Consistency 179 Coverage 178
578
Index
Duplicates 179 Guidelines for rules 180 Integrity 178 Metrics 181 Redundancy 179 Relevance 179 Secure 178 Timeliness 178 Validity 178 Data quality management 57, 69, 169, 390, 482, 489 Determining root causes 211 Tools to fix quality defects 213 Data quality management program Analysis tools 209 Where to focus 210 Data Quality Scorecard 205 Data Readiness Report 197 Data security 380 Breaches 37 Plan 382 Data Standards 58, 71, 275, 482, 501 Components 277 Management 390 Data, document, record, and application archiving 393 Decoupled layers in enterprise SOA 98 Decoupling 81 Dependent object 91 Deployment 58, 74 Design BOMs 525 Design document repository 370 Design document style guide 370 Design Engineer 509 Direct materials 503, 504 Roles 508 Discovery 421 Document management 390 Domain Data Model 251 Domains 34 Downgrade 365
E
EDM Best Practices 112 Component 484, 488
core team 69, 490, 529 Data Quality Program 397 Design Document Repository 404 Dimension 484, 488, 489 Extended team 490 Governance processes 329 Manager 312 Methodology 482, 486, 558 Program collaboration 390 Project Manager 491 Scenarios 48 Team 371, 497, 498, 499 EDM Assessment 489 Scorecard 103, 104 Scoring Definitions 114 EDM Component 488 EDM Deliverables Domain-specific 483 Enterprise-wide 483 EDM Program 32, 57, 121, 349, 370, 385, 389, 394, 423, 479, 482, 486, 498, 499 Approaches 64 Business Case 126 Compelling events 64 Design Guidelines 150 Metrics 183 Policy 161 Scope 156, 185 Scorecard 207 EDM Program Charter 123, 124 Mission 124 Objectives 124 Vision 124 EDM Project 62, 403, 482, 483, 486, 491 Commercial Initiative project 500 Communication plan 492 EDM Strategy 32, 489, 492, 503 Development 359 Project 480 EDM-related applications and technologies 388 EDM-related Business Standards 354, 372 EDM-related technology functions reference list 388 EDR 262, 423, 424, 426, 428
579
Index
EIM 44 Electronic Data Interchange 276 Electronics 503 Engineered Finished Good 507 Engineered-to-order 504, 506 Engineering assembly 506 Specification 518 System 507 Enrichment 364 Enterprise attributes 268, 275, 370 business objects 271, 275 Conceptual Data Model 250 data 46, 48, 101 Enterprise architecture 223, 224, 560 As-is state model 225 Components 224 Framework 224 Metamodel 224 Methodology 225, 486 Modeling 390 To-be state model 225 Transition plan 225 Enterprise Data Distribution Architecture 229 Enterprise Data Governance Change request 338, 344 Organization 70 Position descriptions 315 Processes 338, 470 Enterprise data import and conversion 392 Enterprise Data Model 245, 410 Business value 248 Enterprise Data Organization 308 Best Practices 314 Roles 310 Structure 311 Enterprise Data Quality 423 Management 486 Enterprise Data Repository (EDR) 253, 359, 388, 392, 437 Implementation 360 Enterprise Data Syndication 392 Enterprise Data Trustee 312 Enterprise Information Management 43 Enterprise objects 268
Enterprise program and portfolio management 391 Enterprise reporting 391 Enterprise Services 83 Enterprise Services Repository (ESR) 86, 93, 417, 418 Enterprise SOA 81, 225, 386, 424, 559 Metamodel 87 ERP 527 ES Workplace 85, 390, 414 ESI 96 ETL tool 398, 422 Exact duplicate 364 Executive Sponsor 164
F
Federal Enterprise Architecture 224 FERT 421 Financial benefits 134, 140 Finished goods 504 Focused Internal Business Objective 497 Functionally Equivalent 364
G
GDS Console 437 Global Data Synchronization 52, 501 Global data type (GDT) 84, 86, 92, 275, 373, 415, 417, 559 Example 277 Global procurement 146 Global Spend EDM 141 Globalization 543 Best practices 550 Options 548 Governance 391 Governance Organization 58, 73, 305, 307 Dimension 482 Governance process 58, 73, 327 Dimension 482
580
Index
H
Harmonize master data 81, 424, 467 HL7 373 Horizontal workstream 528 HR-XML 373
Lookup tables 447 LSMW 398, 399
M
Main table 444, 447 Managing EDM Data Design Documents 353, 370 Manufacturing Engineer 509 Mapping ASAP deliverables to workshop cycles 540 Mask 441 Master data 33, 45, 46, 396 Cleansing 425 Consolidation 49 Distribution Approach 237, 242 Harmonization 50 Information bus 423 Object 34, 86, 404 Records 33 Master Data Management IT scenarios 48 Master data versus enterprise data 46 Master repositories 465 Material Info Records 34 Material Master 34, 524 MDM Business Scenarios 51 CLIX 436 Console 435 Data Manager 435 Image Manager 436 Publisher 437 Roadmap Program plan 480, 486 Server 434 Workflow 436 Merger and acquisition 558 Metadata 72, 423 Document management 415 Management 393 Verification 422 Metals and Mining 503 Metamodel 429 Metric 558 MRO item 512 MRP application 40 Multichannel syndication 429
I
IDoc 398 Import Manager 436 Import maps 461 Individual program and project management 391 Information asset management 393 Integration Directory 400 Engine 400 Repository 400 Internal Master Data Management 467 International Computex 41 Iterations and backtracking 422 iView 471
J
Java Application Server 401
K
Key mapping 364, 522 KPI 206, 377, 411, 497, 558
L
Landscape description 405 Language and localization 377, 543, 544, 551 Laws of data 127 Legacy System Migration Workbench 398, 422 Logical Data Model 423, 454, 456 Business value 254 Material Master 259 Logical master data 33
581
Index
N
Normalization 364
Q
Qualified lookup 452 Qualified table 447 Qualitative business benefits 133 Quality 169 Quality data 178
O
Object Data Definition 496 Object tables 444 Oil and Gas 503 OPC 373 Operational inefficiencies 36 Organization design and management 391 Organization schema sample Comparison of schema levels 290 Concept drawing 290 Other EDM-related functions 393 Ownership\subscriber management 391
R
RACI diagram 339, 488, 495, 533 Rationalization 364 Realization Deployment 349, 391, 482 Standard project plans 359 Realization Technology 482 Reference data 396, 423 Regulations Environmental 378 Governance 378 Privacy 379 Safety 378 Security and privacy 379 Trade Restrictions 379 Regulatory 377 Relationship 448 Relative design 493 Replacement 364 Requisite Technology 42 Reverse Business Engineer (RBE) 390, 396, 422 Revision control 426 Rich content management 52, 392, 425 Rich master data 438 Root cause analysis 173 RosettaNet 373
P
Pain points 129 papiNet 373 Pareto diagram 173 Part numbering 522 PDM 40, 42, 521 PI 400 PIC 94, 98 PIDX 373 Plant MRO 504 PLM 521 Preferred Parts List 260, 515 Primary objects 34, 159 Print catalog 429 Process component 88, 90 Process Integration Content 98 Process steps 328 Product data interoperability 520 Product development costs 508 Product development process 511 Product relationship 438 Production BOM 525 Professional buyer 510 Profile template 420 Project costs 142 Purchasing process 511
S
S.W.I.F.T. 373 Sample populated schema structure 291 SAP ALE 392 SAP Analytics xApp 390, 391 SAP archiving tools 393 SAP Business Information Warehouse 391 SAP Business Workflow 392
582
Index
SAP Composition Environment 401 SAP cProjects 391 SAP EAF 228, 236 SAP Enterprise Architecture Framework (EAF) 406 SAP Enterprise Architecture Framework for enterprise SOA 228 SAP Enterprise Buyer Professional 42 SAP Enterprise Data Management Framework 56 SAP ERP 392, 393, 395, 431 Data model 414 HCM 391 SAP ERP ECC 34, 157, 423, 425 Asset Management 393 SAP exchange infrastructure 415 SAP Industry Solution Maps 410 SAP Legacy System Migration Workbench 392 SAP NetWeaver 373 SAP NetWeaver Business Intelligence (BI) 262, 390, 393, 415 SAP NetWeaver Knowledge Management 390 SAP NetWeaver MDM 385, 390, 391, 392, 393, 422, 431, 455 Backups and archiving 470 Basic modules 434 BI integration 472 Console 439 Data field type 441 Data Manager mode 441 Portal integration 471 Repository 445 SAP-supplied repositories 460 Security 473 Sizing MDM 464 Solution landscape 466 Transport 468 Workflow 469 SAP NetWeaver Process Integration (PI) 392, 400, 401 SAP NetWeaver System Landscape Directory (SLD) 393, 405 SAP Organization Terms 306 SAP Product Availability Matrix 390 SAP Product Lifecycle Management 239 SAP SEM 390
SAP Solution Composer 236, 390, 410 SAP Solution Manager 370, 390, 391, 403, 404, 410 SAP Strategic Enterprise Management 391 SAP xRPM xApp 391 Sarbanes-Oxley (SOX) Act 216, 378 Schema 285 Examples 288 Standards 278, 288 Types 285 Scorecard 558 Secondary object 160 Security and compliance 166 Service interface 86, 88, 92 Service operation 86, 88, 92 Services-oriented Architecture 79 Services Registry 417 Simple configured item 506 Simple Data Rule Analysis 420 Situation analysis 122 Six Sigma 170 Analyze 176, 193 Control 176, 214 Define 175, 177 DMAIC 171 Five steps 172 Guiding principles 171 Improve 212 Measure 176, 187 Quality Management 169 Slave repositories 465 SOAP 87 Solution Manager 235 Solution Maps 410 Source and Target Mapping 229 Business value 271 Model 268 Model example 271 Sourcing 53 SPACE 34, 157 SPEC2000 373 Special Deployment Issues 354 Special tables 444 Spend analysis 53 SRM 54 Standard component 504, 505
583
Index
Standard EDM Services 338, 339, 344, 470 Standard Project Plans 353 Statistical process control 173 Strategic plan 123 Strategic sourcing 480, 511 Structure Data Analysis 396, 420 Style Rule Analysis 421 Subtables 444 Superceded 364 SWOT Analysis 122 Syndication Manager 436 Syndication maps 461 System of Distribution (SOD) 241, 268, 396, 432 System of Entry (SOE) 241, 268, 396, 431 System of Record (SOR) 72, 75, 81, 99, 241, 268, 297, 423, 424, 431, 560 How to create 298 Sample 299 System tables 445
U
UCCnet 54, 373 UDDI V3 417 UN/CEFACT 93, 275, 276, 373 Core Component Library 277 UNSPC 288 Upgrade 365
V
Validation 364, 457 Expression 457 Value proposition 148 Value Rule Analysis 421 Value tree 135, 144, 147 Vendor list 524 Vertical Workstream 528 Coordinator 528, 530 VICS 373 Virtual pooled inventory 54 Visual inspection 421
T
Taxonomy 286, 410, 443 Basic concepts 286 Basic terminology 286 Management 392 Of data 423 Technology 58, 74 Driver 557 TOGAF Architecture Development Method 225 Total quality management 170 Transactions 45 Transformation 416 Translation 544 Transliteration 544 Transora 54 Triggers 332 TWIST 373
W
Web services 83 Web Services Description Language 84 Wiki 85 Workflow 392 WRICEF 55, 372, 496 WSDL 84
X
XBRL 373
Z
Zachman Framework 225
584