Modeling and PIC Governance

Ralf HerzogAP OP QSPG, SAP AG

Version 1.0.0 November 23, 2005

Modeling andPIC Governance

SAP AG 2005, Modeling and PIC Governance / Ralf Herzog / 2

Revision Log

Date Action

Nov 23, 2005 V1.0.0 confirmed by AP Engineering Management Team, AP OP Process Network

Nov, 2005 Creation and Review of Draft Version with:Ralf Herzog, Anton Dillinger, Nicole Leuchter, Frank Hering, Rolf Schulte-Rebbelmund


Product View

Integration View

Internal Functional View

Models for Product Definition and Implementation

Choreograph messages for each process interaction

Agents, interfaces, message data types

BO Models and ESR Cross-deployment unit process integration

BOs, Nodes, Elements XI messages (A2A/B2B)

Specification/design

Platform map Functional building blocks, F&F

Integration scenario catalog

Deployment units with their BOs

Concept

Processinteraction map

Requirement specification for new platform development

ApplicationPlatform Portfolio

View

BusinessModel View

Implementation View

Detailed Model

High-Level Model


PIL@AP Development Model

Define Phase

Engineer & Develop

Roll-In

Roll-In

Define

High Level Modeling

Functions & Features

Portofolio Cases=

Modeling =

Implementation

Test

Validation

Design (SDD) Detailed Modeling

Specification (SRS) Unittests

Documentation

Configuration Software =

Invent Define Engineer & Develop Deploy


Process Integration Content – Modeling and Governance

Modeling Processes take place early in development Governance processes ensure engineering excellence The Iterative approach covers all externalized aspects of a business object

Change Requests

Platfo

rm P

ortfo

lio

IP

Secure Intellectual Property

Community Process

Alignment:mySAP/A1S/B1

[as of Release 2]

Imp

lemen

tation

and

Ro

llou

tHigh-Level Modeling Detailed Modeling

Change Requests

mySAPconsol.

Business Object PICnodestructure elements

actions,interfaces..

PIC1 PIC2 PIC3

GDT PIC

PIC0

Business ObjectCoordination


Process Gates PIC 0 and PIC 1,2,3

PIC 01 PIC 02 PIC 03

PIC 1 PIC 2 PIC 3

GDTPIC

ESA EntityIdentification

& Cut

IntegrationScenarioStructure

ServiceOrchestration

Identification of BO’s,PC’s, DU’s

(Name and Semantics)

Identification of PC’s and PC

interactions withinIntegration Scenario(Name and Semantics)

Identification andcut of Service

Operations andInterfaces within

PC interaction(Name and Semantics)

Definition of Node Structure of BO

NodeStructure Elements

Actions, Queries,Interfaces

GDT’s

Detailed Definition ofGlobal Data Types

AssignmentGDT’s to BO

nodes

Definition of Actions,Queries, compound

services

PIC 01approval

Required tostart PIC 1

PIC 03

approval of PCIM’s(Interfaces and Serv.Operations) required

to start PIC 3

ChangeRequests

Global Data Type Modeling – GDT PIC

Further Readings

Process Modeling – PIC0

Business Object Modeling – PIC 1-3


From business scope to high quality implementation in a structured and efficient way

Portfolio/Scope Functional Building Blocks Features & Functions Integration Scenario Catalog

BO/DU MapLevel 1: Deployment UnitLevel 2: Process ComponentLevel 3: Business Object

Service OrchestrationProcess Component Model /Process Component Interaction ModelA2A & B2B Services, Process Agents,

Integration Scenario Model “Circuit Diagram”Process Components and their interactions

Sales OrderProcessing

Purchase OrderProcessing at

Customer

Customer InvoiceProcessing

Due Item Processing

Outbound DeliveryProcessing

Step 1. Identification and Structuring

Step 2. Integration Scenario Overview

After SalesService

Cash Sales

DeliverySchedule

Procurement

Make to Stock

PassiveSubcontracting

OpportunityManagement

Period EndClosing

PhysicalInventory

Plan DrivenProcurement

ReturnsManagement

Sales ContractManagement

Self ServiceProcurement

Sell From Stock

Sourcing

ServiceContract &Warrenty

Entitltements

Sell Services

Cost CenterPlanning

SellBuyLogisticsExecution

Service Financials

Stock Transfer

Ad Hoc RequestFrom Stock

?ProfitabilityManagement?

Cash andLiquidity

Management

ServiceProcurement

ExpenseReimbursement

Governance Process PIC0

Content Governance BO Modeling Operation Signature

Modeling

Step 3. Definition of Service Orchestration


BO PIC (1-3)for Integration ScenariosSAP-wide ReviewProcess

Governance Process for Process Integration Modeling

KEY MESSAGE

The BO, PC and DU identification is part of a Governance Process PIC0. Only Objects that have passed the process will be part of the Enterprise Services Repository.

In scope of this Governance Process are Core BOs, Replicated BOs, PCs and DUs.

Other Object Types such as Maximal BO Modeling Templates, Adapted Objects, Dependent Objects, Business View Objects are not subjects of the Governance Process for Object Identification. A dedicated Governance Process for these Objects is currently under discussion.

Developmentprepares

content, coachingby Gov. team

AP ArchitectsReview

AP ManagementReview

Gov. TeamGate

AP ArchitectsGate

AP MgmtGate

AP Mgmtfinal

approvalAP Review Process

P2Dsign off

SAP Mgmt


Further Readings




BO PIC Governance

Governance Coaching, Steering, Approval

• Business Objects• Elements • Interfaces / Operations

PIC 1 PIC 3PIC 2

Scoping,

Identification

Definition

Implementation

Structure Elements Final

Goals of the Governance Process for Business Objects (BOs)consistency of semantics across development units

reuse wherever possible

similar treatment of similar objects (customer invoice – supplier invoice)

identical modeling and documentation rules

=> “high quality” Business Process Platform (from a conceptual viewpoint)

DevCloseP2DPIC0


Governance Process for Process Integration Content

Review Part 1

Sign-Off Phase

PIC Meeting

document creation

Escalation

Objections

AP OPS BO Experts Coaching TeamOwner and Integration Expert

SAP wide Review

Review feasible?

Critical Issue?

Review Part 2

Document Accepted?

Final Document created

PIC Final Release

Document Accepted?


Governance Process for Process Integration Content

Review

by experts

Sign-Off Phase

Creation of document according to guidelines

EscalationInform SVP

AP OPS

BO Experts

Coaching Team

Owner and Integration Expert

• Discussion in Q&A document• monitoring by Coaching Team

Inform owner + experts about review details

Every 2 weeks status report to SVPs

PIC Final Release

Owner triggers translation after sign-off and finalization of document

Review feasible?Check by coach

Final BO Document created

Critical Issue?Check by owner

Document Accepted?Check by AP OPS

Translation ok?Check by owner

Document Accepted?Check by AP OPS

7 d

ays

7 d

ays

7 d

ays

7 d

ays

14

da

ys

Bil

ate

ral

Cle

ari

ng

Ph

as

e

Ad

res

s q

ue

stio

ns

in

Q/A

If coaching within 7 days is not feasible BO Owner can start PIC Review without coaching

Rev

iew

an

d S

ign

-Off

Ph

ase

fo

r F

ron

tru

nn

er

II B

Os

on

ly 7

da

ys

o

ver

all

≤ 7

days

SAP wide Review(only PIC 1 + 3)

ConsolidationOpen Issues

PIC MeetingOpen Issues

PIC SchedulingObjections?


PIC Governance Process and Roles for Business Objects

Development

by Project

Integration Experts / Content Owner

Governance & Guidance by

Coaching Team

Business Objects / Nodes / Operations

Data Types

Methodology

Approval by Process Integration

Content Council (PIC)

Business Objects / Nodes / Operations

Data Types

A B C

Methodology Council:Methodology, Design Rules, Procedure Model

D

Organizational structure with roles and tasks (A – D, details see BO Guideline)


Tasks


Further Readings




GDT Overview / Goals

Business objects and operations are hierarchically structured.

Elements of a BO or an operation are uniformly described by data types known as “Global Data Types” (GDT).

Global data types are based on a set of basic types, known as core component types (CCT). Core component types were defined by the UN/CEFACT in the ebXML framework and are based on the XML Schema

If the same semantic subject appears in (leaf) elements, it is always characterized by the same Global Data Type.

GOAL of the GDT PIC-process is to harmonize GDTs SAP-wide


Development

by Project

Integration Experts

Guidance by Coaching Team

Communication

Interfaces

Data Types

PIC Process and Roles

Review by

Process Integration Content Council

(PIC)

Communication,B2B/A2A Interfaces Global Data Types

Coaching and Guiding

Registration at Coaching TeamRegistration at Coaching Team Quality CheckQuality CheckReview of GDTsReview of GDTsCommunication

Review PIC1Communication

Review PIC1

Invent Define Develop Deploy Optimize


GDT PIC Governance

Review by experts

SAP wide review

Design of GDT according to guidelines

Escalationto BOT or DCM

AP OPS

Experts

Coaching Team

GDT Owner

Creation of GDT in X3R

Inform owner + experts about review details

Every 2 weeks status report to SVPs

Update GDT catalogue

Initiate translation of GDT

Review feasible?Check by coach

Final GDT document

Review accepted?

Document Accepted?

If coaching within 7 days is not feasible GDT Owner can start PIC Review without coaching


Further Readings




Further Readings

Process Modeling and PIC0 Guidelines

ESA Modeling Handbook Content Creation Guideline Naming Rules for Operations and Interfaces ARIS Business Designer and Web Designer

Templates Changerequest Template and Change Process

(can also be found in SAP Portal : AP Engineering Process Modelling)

BO Modeling and PIC1 – PIC3 Guidelines:

\\dwdf029\ap_eng\Content_Governance\40_Guidelines\BO_Guidelines

Templates:\\dwdf029\ap_eng\Content_Governance\10_Business_Object_Governance_&_Coaching\40_Template-and-Pattern

GDT Modeling and GDT PIC Guidelines: \\dwdf029\ap_eng\Content_Governance\40_Guidelines\GDT_Guidelines

Templates: \\dwdf029\pic-coaching\100_ESA_BusinessObjects\00_GDT_Templates

Templates can be found also in the AP Portal Quality&Standards Templates


Appendix




AP View of the Taxonomy & Governance Processes

ARISPIC0



PIC1



PIC2



PIC3

Date post:	02-Feb-2016
Category:	Documents
Upload:	marty
View:	36 times
Download:	0 times

Modeling and PIC Governance

Documents