Enterprise Systems Architectures EGN 5620 Enterprise Systems Configuration Fall, 2011.

Enterprise Systems Enterprise Systems ArchitecturesArchitectures

EGN 5620 Enterprise Systems ConfigurationEGN 5620 Enterprise Systems ConfigurationFall, 2011 Fall, 2011

Enterprise Systems Enterprise Systems Architectures Architectures

Theories & ConceptsTheories & Concepts


System architecture, Def.System architecture, Def.

◦ A scheme by which the functional elements of the system are arranged into physical/logical blocks and by which the blocks interact.

Three major enterprise (information Three major enterprise (information reference) architecturesreference) architectures

Generalized enterprise reference architecture (GERA)

Purdue enterprise reference architecture (PERA)

Enterprise architecture framework◦By John Zackman

GERA GERA - - Three scoping/modeling dimensionsThree scoping/modeling dimensions

Life-cycle dimension◦Provides for the controlled modeling process of

enterprise entity according to its life cycleGeneric-ity dimension

◦Provides for the controlled particularization (instantiation) process from generic (or partial) to particular.

View dimension◦Provides for the controlled visualization of

specific views of the enterprise entity

GERA GERA - - Enterprise life-cycle phases (1)Enterprise life-cycle phases (1)

Identification◦ (A set of activities that) identifies the contents of the

enterprise in terms of the nature of its existence, its need and the need for changes.

Concept◦ (A set of activities for) developing the concepts of the

underlying enterprise, including the definition of its mission, vision, values, strategies, objectives, operational concepts, policies, and business plans.

Requirements◦ (A set of activities for) developing descriptions of

operational requirements of the enterprise, its relevant processes, and the collection of all their functional, behavioral, information and capacity needs for both production and mgt, whether by humans or machinery.

GERA GERA - - Enterprise life-cycle phases (2)Enterprise life-cycle phases (2)

Design◦ (A set of activities that) support the specification of the enterprise

with all of its components that satisfy the enterprise requirements. They include the design of all human tasks, all machine tasks, and operational processes (including identification of necessary information and resources for mfg. information, communication, control and other processing technology)

◦ Sub-phases: preliminary (architectural) design and detailed design Implementation

◦ (A set of activities that) define all tasks that must be carried out to build or re-build (manifest) the enterprise. This comprises implementation in the broadest sense, covering Commissioning, purchasing, re-configuring, or developing all

software and hardware resources for services, mfg. and control. Hiring and training personnel, and developing or changing the

human organization. Component testing and validation, system integration,

validation, and testing, and releasing into operation

GERA GERA - - Enterprise life-cycle phases (3)Enterprise life-cycle phases (3) Operation

◦ The activities of the enterprise that are needed during its operation for producing the customers products and service which is its special mission , along with all those tasks needed for monitoring, controlling, and evaluating the operation.

◦ Thus the resources of the enterprise are managed and controlled so as to carry out the processes necessary for the entity to fulfill its mission

◦ Deviations from goals and objectives or any feedback from the environment may lead to requests for change, which includes enterprise re-engineering, continuous improvements of its human and technology resources, its business process, and its organization.

Decommission◦ The activities needed for disbanding, re-missioning, re-training,

redesign, recycling, preservation, transfer, disassembly, or disposal of all or part of the entity at the end of its useful life in operation.

GERA GERA - - Enterprise’s entity types (4)Enterprise’s entity types (4) Type A – strategic management entity

◦ such as an (enterprise) engineering project◦Very short life cycle

Type B – engineering implementation entity◦Entity that creates other enterprise entities

Type C – enterprise entity◦Entity that produces customers goods and services

Type D – product entity◦All products and customers services of enterprise

type C Type E – methodology entity

◦Entity that establishes tasks to support other entities.

GERA GERA - - viewsviews

Entity model contents views◦ Function (model of functions and behaviors of business processes)◦ Information (model)◦ Organization (of responsibilities and authorizations on entities)◦ Resource (model)

Entity purpose views◦ (Customer) service and product views (contents relevant to

operation and its results◦ Management and control views (contents relevant to mgt.)

Entity implementation views◦ Human activities view (of information related to human tasks)◦ Automated activities view (of information related to machine

tasks) Entity physical manifestation views

◦ Software view (information resources capable of performing a task set)

◦ Hardware view (physical resources capable of performing a task set)

PERA Layers (life cycle phases)PERA Layers (life cycle phases) Identification

◦ of the CIM business entity Concept layer

◦ mission, vision, and values Definition layer

◦ functional requirement Specification layers

◦ architectural design Detailed design layer Manifestation layer

◦ Implementation Operations layer

Row Perspective Constraint Model

1 Planner Financial/external Scope (an executive summary of system scope, cost, and how it would perform)

2 Owner Usage/policy Enterprise (business) model (business entities, processes and how they interact)

3 Designer (analyst) Structure/operation System model (data elements and functions that represent business entities and processes)

4 Builder Technology Technology model (adapting information model to the details of programming languages, tools, I/O devices, and others)

5 Subcontractor Implementation Out of context models (detailed specifications given to programmers who code modules)

Zackman’s Enterprise FrameworkZackman’s Enterprise Framework

Data (with entity and relation)

Function (with function and parameter)

Network (with node and link)

Scope (planner) List of things important to the business (entity: class of business thing)

List of processes the business performs (function: class of business processes)

List of location in which the business operates (node: major business location)

Enterprise model (owner)

ENT/REL diagram (business entity, business constraint)

Process flow diagram (business process and resources)

Logistics network (business location, business linkage)

System model (designer)

Data model (data entity and data relationship)

Data flow diagram (application function and user view)

Distributed system architecture (I/S function, and line characteristics)

Technology model (builder)

Data design (segment/row; pointers/key)

Structure chart (computer function and screen/device format)

System architecture (hardware/system software, line specifications)

Components (subcontractor)

Data definition description (field and address)

Program (language statement and control block)

Network architecture (address, protocol)


People (agent, work) Time (time, cycle) Motivation (ends, means)

Scope List of organizations/agents important to the business (major org. unit)

List of events significant to the business (major business event)

List of business goal/strategy (major bus. goal and critical success factor)

Enterprise model Organization chart (org. unit, work product)

Master schedule (business event and bus. cycle)

Business plan (business objective and bus. strategy)

System model Human interface architecture (role, deliverable)

Processing structure (system event and processing cycle)

Knowledge architecture (criterion, option)

Technology model Human/technology interface (user, job)

Control structure (execute, component cycle)

Knowledge design (condition and action)

Components Security architecture (identity, transaction)

Timing definition (interrupt and machine cycle)

Knowledge definition (sub condition, step)


SAP Architecture DesignSAP Architecture Design


SAP Architecture Design SAP Architecture Design RequirementsRequirements

Required data types:

1.Organizational levels (data, elements)

2.Master data

3.Transaction data

Data type: Organizational levelsData type: Organizational levelsDefines the enterprise structure in terms of legal or

business purposes, including legal entities, plants, storage areas, sales organizations, profit centers:

Client (e.g., 700)◦Highest organizational level◦Represents the enterprise consisting of many

companies Company Code (e.g., C101)

◦Identifies legal entities in an enterprise◦Central organizational element in financial accounting

Organizational levels in Logistics◦Plant (e.g. P101)

Represents factory, warehouse, office, distribution center, etc.

◦Storage locations (e.g., 10, 20, 30) A location within a plant where materials are stored

Data Types: Organizational levelsData Types: Organizational levels

Organizational levels in Accounting Client Company code Business area Controlling area Operating concern

Organizational levels in procurement Purchasing organization Purchasing group Plant Storage location

Organizational levels in fulfillment (sales)

Sales organizationsDivisionsDistribution channelSales areasShipping pointPlantStorage location

Organizational levels in PPPlantWork CenterStorage locationShipping Point

Types of Data: Organizational levelsTypes of Data: Organizational levels

SAP Enterprise Structure ExampleSAP Enterprise Structure ExampleFinancial

Client GBI Operating Concern (global) GL##

CA Europe EU##CA North Am. NA## CA Asia AS##

Chart of Accounts (global) GL##

CoA US##

CC US##

CA##

CC

CA

##

CoA DE##

CC DE##

GB##C

C G

B##

AU##

CC

AU

##

JP##

CC

JP##

Business Area – Bicycles BI##

Procurement

Client GBI CC US##

Dallas DL##

Miami MI##

S. DiegoSD##

CA##

TorontoTO##

Shipping Point DL##

Storage Location

RM##

MI## SD## HD## HH##

AU##

PerthPE##

Central Purchasing Organization (global) GL##Purchasing Org. US##

CC DE##

Heidelb.

HD## Hamburg

HH##

SF##

FG##

MI##

TG##

FG##

MI##

TG##

FG##

MI##

TG##

FG##

MI##

RM##

SF##

FG##

MI##

TG##

FG##

MI##

TO##

TG##

FG##

MI##

PE##

CA##

Purchasing Group North America N##

PO DE##

PGr Europe N##

AU##

AsiaAS##

SAP Enterprise Structure ExampleSAP Enterprise Structure Example

Sales and Distribution

Client GBI Credit Control Area (global) GL##

CC US##

SO East UE##

SO West UW##

CC CA##

SO East CE##

SO West CW##

CC DE##

SO South DS##

SO North DN##

CC GB##

SO South GS##

SO North GN##

CC AU##

SO South AS##

SO North AN##

Distribution Channel Wholesale WH

Distribution Channel Internet IN

Div

isio

n B

icyc

les

BI

Div

isio

n A

cces

sori

es A

S

SAP Enterprise Structure ExampleSAP Enterprise Structure Example

Key Concepts in SAPKey Concepts in SAP

◦Long term data that represent entities of: Procurement

◦Vendor◦Material◦ Info records, source list

Fulfillment◦Customer◦Material◦Conditions (pricing, output)

Production◦Bills of material◦Work centers◦Product routings

Financial accounting◦General ledger accounts

Types of Data: Master data


◦Data generated during executing process (steps) combining: Organizational levels Master data Situational data (who, what, when, and where)

◦Example: sales order Organizational levels: customer, company code,

sales area Master data: customer master, material master Situational data: date, time, person, quantities

Types of Data: Transaction data

• The Document concept◦ An electronic record of transactions◦ Each transaction creates document(s)

• Document types◦ Financial accounting documents (FI)◦ Management accounting documents (CO)◦ Material documents (goods movement)◦ Others


Key Concepts in SAPKey Concepts in SAPThe Document Concept: Transaction document

Global Bicycle Incorporated 5215 N. O’Conner Blvd. Dallas, Texas, 75039 Phone: +1.972.555.2000 Fax: +1.972.555.2001

PURCHASE ORDER Purchase Order Number: 4546

THE PURCHASE ORDER NUMBER MUST APPEAR ON ALL RELATED CORRESPONDENCE, SHIPPING PAPERS, AND INVOICES

TO: Olympic Protective Gear 2100 Summit Boulevard Atlanta, GA, 30319

SHIP TO: GBI San Diego Distribution Center 150 Spear Street San Diego, 94105 +1-415-555-7700

Purchase Order # P.O. DATE Delivery Date Shipped VIA F.O.B. Point Payment Terms

4546 July 11, 2009 July 27, 2009 Ground Destination Net 30

Quantity Material # Material Description Unit Type Unit Price Item Total

100 KPAD 2160 Knee Pads Each 37.50 3,750.00

100 EPAD 2130 Elbow Pads Each 37.50 3,750.00

50 OHMT 2220 Off-road Helmets Each 25.00 1,250.00

SUBTOTAL $ 8,750.00

SALES TAX Exempt

SHIPPING & HANDLING Included

OTHER N/A

ORDER TOTAL $ 8,750.00

, Authorized by: __________________________________________________ Purchasing Manager

Date: ____________________

Header

Line items

Key Concepts in SAPKey Concepts in SAPThe Document Concept: Financial Accounting Document

Key Concepts in SAPKey Concepts in SAPThe Document Concept: Material Document

PEN, Inc. PEN, Inc. System Architecture DesignSystem Architecture Design


Company configurationCompany configuration◦Pen Inc. _ _ _US manufacturing Company

Vermillion SD, US◦Facilities:

One manufacturing plant with warehouse in Vermillion (Plant)◦Work Center◦Storage Location

10 for Trading and finished goods 20 for Quality 30 for Raw materials

◦Shipping point◦Sales Organization◦Purchase Organization

The company to be configuredThe company to be configuredCost Center Standard Hierarchy

ADMIN_ _ _ (Cost Center Group)• Acct-Finance • Administration• Purchasing• Information Tech

Sales _ _ _ (Cost Center Group)• Sales • Marketing

Distribution-Production Cost Center _ _ _ (Cost Center Group)• Warehouse • Production

Pen Inc. : The companyPen Inc. : The companyProducts

◦Trading Materials BPEN _ _ _ (Barrel Pen) CPEN _ _ _ (Click Pen) PPEN _ _ _ (Premium Pen) Box _ _ (Pen Box)

◦Finished products EPEN _ _ _ (Executive Pen) ESET _ _ _ (Executive Set)

Pen Inc. : The companyPen Inc. : The companyCustomers

Pen Inc. : The companyPen Inc. : The companySuppliers

Pen Inc.: Key ProcessesPen Inc.: Key Processes◦Fulfillment (sell)◦Procurement (buy)◦Material Planning (plan)◦Production (make)◦Financial Accounting (track)◦Management Accounting (track)◦Inventory and Warehouse Management (store)◦Enterprise Asset Management (maintain)◦Customer Service (service)◦HCM (people)

Pen Inc. : The companyPen Inc. : The company

The IS of the Pen, Inc. will ◦integrate and share all services for all business

functions in the Vermillion Office◦Centralize all ERP functions◦Achieve the primary business objectives:

Reduce Costs Deliver Best-in-Class Technology to all divisions

Information system requirement

Exercises: Due date - 9/26/2011Exercises: Due date - 9/26/201165. Initialize Fiscal Period for Company Code 66. Maintain Plant Parameters for Material

Management67. Activate Materials Requirements Planning68. Define Attribute for Material Types (Only Watch,

and don’t make any changes)71. Define Posting Periods Variant72. Open and Close Posting Periods73. Assign Posting Periods Variant to Company Code

Exercises: due date – 9/26/2011Exercises: due date – 9/26/201174. Create Tolerance Groups for Account Postings75. Setup Payment Program76. Create Tolerance Groups for Accounts Receivable

and Accounts Payable77. Create Financial Accounting (FI) Document

Numbers78. Review Document Types (Only Watch, and

don’t make any changes)79. Post Initial Cash Investment by Owners80. Post Purchase of Operating Supplies81. Display and Review General Ledger Account

Balances and Individual Line Items (Only Watch, and don’t make any changes)

Enterprise Systems Architectures EGN 5620 Enterprise Systems Configuration Fall, 2011.

Documents

enterprise requirements

underlying enterprise

operation slide

set of activities

system architecture

operational concepts

john zackman slide

operational processes