Enterprise Systems Modeling EGN 5620 Enterprise Systems Configuration Professional MSEM Fall, 2012.

transcript

Enterprise Systems Enterprise Systems ModelingModeling

EGN 5620 Enterprise Systems ConfigurationEGN 5620 Enterprise Systems ConfigurationProfessional MSEMProfessional MSEM

Fall, 2012Fall, 2012

Enterprise Systems ModelingEnterprise Systems Modeling

Systems Modeling: Systems Modeling: Concepts and ToolsConcepts and Tools

EGN 5622 Enterprise Systems Integration

Information systems modeling Information systems modeling toolstoolsIDEF

◦IDEF0 (activities)◦IDEF1x (information)◦IDEF2x (dynamics)

OMT◦Functional model◦Object model◦Dynamic model

IDEF Concept (1)IDEF Concept (1)IDEF (ICAM Definition)

◦Developed by the US Air Force Integrated Computer Aided Manufacturing (ICAM) Programs in 1981

ICAM Objective◦To develop structured methods for applying

computer technology to manufacturing and to better understand how best to improve manufacturing productivity

IDEF Concept (2)IDEF Concept (2)IDEF0

◦An activity model of a manufacturing system and environment

IDEF1◦An informational model of the system and

environment

IDEF2◦A dynamic model to describe time-varying

system behavior

IDEF Concept (3)IDEF Concept (3)IDEF Methodology

◦Modeling process and tools, leading to creation of the three IDEF models IDEF0 (activities) IDEF1x (information) IDEF2x (dynamics)

Commercial IDEF software tools◦Design/IDEF by Meta Software Company◦AI0WIN by Knowledge Based Systems Inc.

OMT Concepts (1)OMT Concepts (1)Object modeling technique (OMT)“Object-oriented” means:

◦ Software organized as a collection of discrete objects that incorporate both data structure and behavior, in contrast to conventional programming in which data structure and behavior are only loosely connected.

OMT Methodology (in stages): ◦ system analysis, ◦ system design, ◦ Object (implementation) design, and ◦ implementation.

OMT concepts (2) OMT concepts (2) - common themes - common themes Synergy (i.e., shifting focus from coding technique to packaging, based on consistent

◦ identity, ◦ classification, ◦ polymorphism, and ◦ inheritance

Abstraction, Encapsulation, Combining data and behavior, Sharing (inheritance of data structure & behavior among subclasses)

Emphasis on object structure (not procedure structure),

OMT Concepts (3)OMT Concepts (3)- Synergy- Synergy

Identity◦ Data is quantized into discrete, distinguishable entities

called objectsClassification

◦ Objects with the same data structure (attributes) and behavior (operations) are grouped into a class An operation is an action or transformation that an object

performs or is subject to.polymorphism

◦ The same operation may behave differently on different classes. A specific implementation of an operation by a certain class is

called a method. Each operation may have multiple methods implementing it.

inheritance◦ The sharing of attributes and operations among a hierarchy of

object classes

OMT Models (4)OMT Models (4)3 OMT models used to describe a system:

◦Object model describing the objects in the system and their

relationships; ◦Dynamic model

describing the interactions among objects in the system; and

◦Functional model describing the data transformation of the system.

Their relationship◦ The object model describes what changes (or

transforms) before when (dynamic model) or how (functional model) it changes.

OMT Functional Model (5) OMT Functional Model (5)

It describes the data value transformations within a system.

The functional model contains data flow diagrams. ◦A data flow diagram is a graph whose nodes

are processes (activities) and whose arcs are data flows.

OMT Object Model (6) OMT Object Model (6)

It describes the static structure of the objects in a system and their relationships.

The object model contains object diagrams. ◦An object diagram is a graph whose nodes are

object classes and whose arcs are relationships among classes.

OMT Dynamic Model (7) OMT Dynamic Model (7)

It describes the aspects of a system that change over time and is used to specify and implement the control aspects of a system.

The dynamic model contains state diagrams. ◦A state diagram is a graph whose nodes are

states and whose arcs are transitions between states caused by events.

Relationship between the two Relationship between the two techniques & among the three modelstechniques & among the three models IDEF0/functional model

◦ The input to an activity is usually through a user interface for data entry◦ The output from an activity is usually a user interface for a report,

though the output may be a write/update to a database. IDEF0’s◦ ICOM

Material is an input object. Product/process data are output objects. Rules/regulations and SOPs are constraints. Technical precedence is a

constraint Resources/tools and methods are a mechanism.

IDEF1/object model◦ The collection of the ICOM of an IDEF activity model constitutes an

inclusive foundation for the object model. IDEF2/dynamics model

◦ Each object requires a state diagram to define/govern its life-cycle behavior.

◦ A triggering event is associated with each transition from one state to another. One state may transform to multiple states, depending on the triggering event.

SAPSAPSystem Modeling DesignSystem Modeling Design

EGN 5622 Enterprise Systems IntegrationEGN 5622 Enterprise Systems Integration

January 2008January 2008

SAP R/3SAP R/3Enables a company to link it’s business

processesTies together disparate business

functions (integrated business solution)Helps the organization run smoothlyReal-time environmentScalable and flexible

ArchitectureArchitecture Central relational database

◦Oracle, Informix, Microsoft SQL, etc.Client/Server – three-tieredERP Components – Oriented towards common

identifiable business modules: ◦MM, SD, PP, FI, CO, HR, WM, QM, PM

Add-ons: ◦Customer Relationship Mgmt (CRM)◦Supply Chain Mgmt (SCM)◦Product Lifecycle Mgmt (PLM) ◦Business Intelligence (BI)

Relational Database Relational Database Tables: Defines and links a couple of tens

thousands of tables of information (25,000+)

Advantages◦Consistent and accurate data◦Common definitions for terms◦Shared, but restricted usage (e.g., profiles) ◦Eliminates data redundancy

Client/Server Environment Client/Server Environment

Client◦Software/hardware combination that can

make a request for services from a central repository of resources

Server◦Software/hardware combination that can

provide services to a group of clients in a controlled environment

Three-Tier SAP StructureThree-Tier SAP StructureGUI – Graphical User Interface or Web

InterfaceApplication server (one or many)Database server (one single location)

January 2008January 2008© SAP AG - University Alliances and The Rushmore Group, LLC 2008. All rights © SAP AG - University Alliances and The Rushmore Group, LLC 2008. All rights reserved. reserved. 4040

SAP Enterprise System

Database

Application

Presentation

Browser ClientPCs, Laptops, etc.

Network

Application Servers

Database

Internet Transaction Server

Web Server

January 2008January 2008© SAP AG - University Alliances and The Rushmore Group, LLC 2008. All rights © SAP AG - University Alliances and The Rushmore Group, LLC 2008. All rights reserved. reserved. 4141

FIFinancialAccounting

COControlling

PSProjectSystemWF

Workflow

ISIndustrySolutions

MMMaterials Mgmt.

HRHumanResources

SDSales and Distribution

PPProductionPlanning

QMQualityMgmt. PM

Plant Maintenance

SMServiceMgmt.

Client / ServerIntegrated BusinessSolution

ECEnterpriseControlling

AMFixed AssetsMgmt.

SAP ERP Modules

Business ModulesBusiness ModulesCollections of logically related

transactions within identifiable business functions◦MM (“Buy”)◦PP (“Make”)◦SD (“Sell”)◦FI and CO (“Track”)◦HCM (“People”)

SAP R/3 Basics SAP R/3 Basics Instance – each install of the SAP R/3

software on an individual application server

Configurable – each instance can be distinctively configured to fit the needs and desires of the customer (within limits)

Most of the infrastructure decisions, including configuration decisions, occur during project implementation

SAP SAP Business Processes IntegrationBusiness Processes Integration

(Overview)(Overview)

EGN 5622 Enterprise Systems Integration

Business Process Integration (II)Business Process Integration (II)

Master D

Learning ApproachesLearning Approaches◦Cross business functions◦Understand business processes and their relationships to SAP's organizational structure

◦Highlight integration/configuration!!

Learning by Creating a Model Learning by Creating a Model BusinessBusinessUnderstanding business processes and

their integrative natureUnderstanding SAP organizational

structuresCombining business processes and SAP

organizational structure (i.e., configuration)

Test the newly configured systemView system outputs - statistics, reports,

and graphics

PEN, Inc. PEN, Inc. System Modeling DesignSystem Modeling Design

EGN 5622 Enterprise Systems IntegrationEGN 5622 Enterprise Systems Integration

Pen Inc.Pen Inc.Start-up company in the promotional pen

businessInitially buys and re-sells different lines of

promotion pensSells to both wholesale and retail –

procure and distributeLater acquires a production facility to

manufacture its own product – produce and distribute

Pen Incorporated Pen Incorporated Procure for Sales OrderProcure for Sales Order

Pre-Sales Activity

Sales OrderDelivery Billing

General Ledger Accounts

Purchase Requisition

Purchase Order

Goods Receipt

In Inventory

Plant or Warehouse

Invoice Receipt

Availability Check

Goods to Delivery

Goods from Purchase Order

InventoryPostings

AccountsReceivable

AccountsPayable

Pen Inc. Business Module I for Selling Trading products

Pen Inc. Business Module II for Pen Inc. Business Module II for Selling Finished Goods by ProductionSelling Finished Goods by Production

Pre-Sales Activity

Sales Order

Delivery Billing

Planned Order

Production Order

Completion Confirmation

In Inventory

Plant or Warehouse

Availability Check

Goods Issued to Delivery

Goods from Production Order

General Ledger Accounts

InventoryPostings

AccountsReceivable

Issue Goods to Production

Purchase Requisition

Purchase Order

Goods Receipt

Invoice Receipt

AccountsPayable

Exercises:Exercises:1 Display chart account2 Review a listing of the general ledger (G/L) accounts 3 Create general ledger account4& 4A Post transfer of funds to alternate bank account5 Post purchase of operating supplies6 Display general ledger account balance7 Display multiple general ledger account balances8 Display individual items while displaying general ledger account

balances9 Change financial accounting document10 Display change to financial accounting documents11 Create invoice receipt for rent expense12 Display and review general ledger account balances and

individual line items13 Display and review accounts payable balances and individual

line items

Exercises:Exercises:14. Post payment to landlord15. Display and review general ledger account balances and individual line items16. Display and review accounts payable balances and individual line items17. Run balance sheet/profit and loss statements18 Create sales order19 Create delivery note for sales order20 Pick materials on delivery note21 Post goods issue22 Create billing for customer23 Post receipt of customer payment24 Review document flow25 Run balance sheet/profit and loss statements

Enterprise Systems Modeling EGN 5620 Enterprise Systems Configuration Professional MSEM Fall, 2012.

Documents