Enterprise S

Enterprise tructure
Structure
LOG-OR-001 / F
LOG-OR-001 I-GL-001
FI-GL-001
JJuly
uly 29, 2
29, 008
2008

LaGov
Version 2.1

Updated: 07/28/2008
 Agenda

 Logistics, Ground Rules & Introduction

 Project Timeline
 Workshop Objectives
 Business Process Review
– Process overview
– AS-IS process flow
– Current system alignment
– Process improvement opportunities
– SAP terms glossary
– SAP concepts & functionality
– Business process flow
– Leading practices
– Enterprise readiness challenges
 Next Steps – Action items
 Questions

2
 Logistics

Before we get started ...

3
 Ground Rules

 Has everybody signed in?

 Everybody participates – blueprint is not a
spectator sport
 Silence means agreement
 Focus is key – please turn off cell phones and
close laptops
 Challenge existing processes and mindsets
 Offer suggestions and ideas
 Think Enterprise
 Ask questions at any time
 One person at a time please
 Timeliness – returning from break
 Creativity, cooperation, and compromise

4
 Introduction

 Roles
 Process Analyst and Functional Consultant – lead and
facilitate the discussions and drive design decisions
 Documenter – take detailed notes to support the formal
meeting minutes to be sent by the Process Analyst to all
participants for review and feedback
 Team Members – provide additional support for process
discussions, address key integration touch points
 Subject Matter Experts – advise team members on the
detailed business process and participate in the decisions
required to design the future state business process

Round the Room Introductions

Name
Position
Agency
5
 Project Phases

 Five Key Phases

Realization

Preparation
Preparation

Business
Blueprint

Support
Go Live
Project

Final

and
• Strategy & Approach Defined • Development & Unit Testing • Go-Live Support
• Project Team Training • Integration Testing • Performance Tuning
• End-User Training Materials

• Business Process Definition • User Acceptance

• Development Requirements • Technical Testing
• End-User Training
• Conversion

6
 Tentative Project Timeline

 Tentative implementation dates are planned as follows:

Functionality Tentative Implementation Date

Budget Prep October 2009
DOTD February 2010
Core Modules All Agencies July 2010
Additional Modules January 2011

May – June 2008 July 2008 August – Dec 2008 January 2009

Project Start-Up
Phased deployment
Blueprint will be
confirmed/updated
before completion
of Blueprint activities!

7
 Project Organization - Functional Teams

Finance Leads Logistics Leads Linear Assets Leads

Beverly Hodges – Finance Lead
Drew Thigpen – Finance Lead
Mary Ramsrud – Consulting Lead
General Ledger
Belinda Rogers – Logistics Lead Mark Suarez – Agile Assets Lead
Jack Ladhur – Logistics Lead Charles Pilson – Consulting Lead
Brad Denham – Consulting Lead
Pat Cane
Kurt Demmerly
Accounts Payable Mary Ramsrud

Accts Receivable
Cash Management
Cost Accounting
Funds Management
Grants Mgt
Project Systems
Asset Accounting

Budget Prep
Grantor
Real Estate Management

8
 Blueprint Objectives

 Review and discuss the current or As-Is business processes

• Which helps to drive out the Business requirements
• As well as the integration points with other processes
 Define Master Data
• Address key integration points
• Support organizational requirements
• Consistent and appropriate use of data fields
 Define Future or To-Be business processes based on:
• Best Practices inherent in SAP
• Intellectual capital from other SAP implementations
• State business requirements
 Identify development requirements
• Which could result in the need for a form, report, interface,
conversion, enhancement, or workflow (FRICE-W)
 Understand and communicate any organizational impacts / Enterprise
Readiness challenges
 Gather system security authorizations and statewide training
requirements

9
 Work Session Objectives

 To define and confirm the preliminary design for the

finance and logistics enterprise structures in SAP to
include:
– FM Area
– CO Area
– Company Code
– Business Area
– Plant
– Storage Location

10
 SAP Glossary

 FM Area - the organizational unit  Plant - An organizational unit

within an institution, used to serving to subdivide an enterprise
represent a closed system for according to production,
funds management, budgeting, and procurement, maintenance, and
budget execution. FM. materials planning aspects. It is a
place where either materials are
 Controlling Area - the
produced or goods and services
organizational unit within an
provided.
institution, used to represent a
closed system for managerial  Storage Location - An
organizational unit facilitating
accounting purposes. CO.
differentiation between the various
 Company Code - represents the stocks of a material within a plant.
highest level at which common A storage location is the place
master data, including chart of where stock is physically kept
accounts, vendors, and customers, within a plant.
will be assigned. FI.
 Business Area - represents lines of
business where complete (or even
partial) financial statements or cost
accounting information is required.
FI.

11
 Funds Management

 Fund Accounting
 Budgetary Controls

FM  Budget Execution
 Budgetary Basis
Reporting
 Commitment
Accounting

12
 Financial Accounting

 General Ledger
 Fixed Assets

FI  Bank Accounting
 Accounts
Receivable
 Accounts Payable

13
 Controlling

 Cost Center Accounting

(CCA)

CO  Cost Element Accounting

(G/L Accounts P&L)
 Internal Orders (IO)
 Allocations, assessments,
and distributions

14
 Core SAP Finance

Main Accounting
Ledger
Financial Accounting
(GAAP) FI (SPL)
Budgetary Costing & Project
Subledger Subledgers

Budgetary Funds & Functions Cost

Accounting Grants/Funded Programs Accounting
& Control & Control

FM CO / PS
Grant Accounting, GM
Control & Billing
Grants Subledger

15
 Accounting Methods

Financial accounting, full financial statements

(full accrual, modified accrual), reconciliation of
Financial Accounting full vs. modified accrual, high level cash

Budgetary accounting, budgeted income and

expenses, reconciliation to full and modified
Funds Management accrual

Cost accounting, operational income and

expenses (primarily full accrual, with limited
Controlling modified accrual support)

Project accounting, income and expenses for

large projects (primarily full accrual, with limited
Project Systems modified accrual support)

Grant accounting, grant related posting,

including overhead calculations, update the GM
Grants Management ledger based on sponsor requirements.

16
 Organizational Elements
Funds Management – FM

FM Area
 A Funds Management Area in ECC is the organizational unit within
an institution, used to represent a closed system for funds
management, budgeting, and budget execution. A Funds
Management Area may include one or more company codes and
one or more controlling areas.
 The Funds Management Area also contains attributes or settings
that impact master data and/or transactions within the FM Area.
 Field Length: 4

17
 Organizational Elements
Controlling – CO

CO Area
 A controlling area in ECC is the organizational unit within an
institution, used to represent a closed system for managerial
accounting purposes. A controlling area may include one or more
company codes, which must use the same operative chart of
accounts as the controlling area.
 The Controlling Area also contains attributes or settings that impact
master data and/or transactions within the CO Area.
 Field Length: 4

18
 Organizational Elements
Financial Accounting – FI

Company Code
 Represents the highest level at which common master data, including
chart of accounts, vendors, and customers, will be assigned
 Company codes are balanced in the general ledger; however, this
balancing is done using inter-company clearing transactions (considered
cash-type clearing postings, even if the transactions are non-cash
items). This means that a true balance sheet cannot be attained if a
company code is managing receivables or payables on behalf of
another company code. Even the split processor will not split
transactions by company code. For many reasons the use of one
company code is recommended.
 Field Length: 4

19
 Enterprise Structure

Controlling Funds Management Financial Accounting

(CO) (FM) (FI)

Controlling Area FM Area Company Code

20
 Financial Accounting - FI

Chart of Accounts
 The Chart of Accounts is a collection of general ledger
accounts. Each company code is assigned to a chart of
accounts, and the controlling area is assigned to the same
chart of accounts.
 Field Length: 4

21
 Organizational Elements
Financial Accounting - FI

Business Area

 Business areas should represent lines of business where

complete (or even partial) financial statements or cost
accounting information is required.
 The business area is the best object for high-level reporting of
revenue and costs across related cost centers, orders and
projects.
 Field Length: 4

22
 Finance Structure

Controlling Funds Management Financial Accounting

(CO) (FM) (FI)

Controlling Area FM Area Company Code

Chart of Accounts

Business Area

23
 Leading Practices

 One FM Area
 One CO Area
 One Company Code
 Business Area balance sheets
 The use of logical numbering
 Business Areas

Business Area Business Area

at the vs. at the
Department Agency
Level Level

Considerations:
Security (tighter security vs. maintenance)
Agency Balance Sheet
Split Processor Volume
Grants/Project Ownership
Plants
Asset Tracking
Investments
Fund Balances/ Cash
Data Conversion Considerations
Business Area requirement on GL postings
 Enterprise Structure
Company Code
State of LA

Chart of Accounts
State of LA

Business Area Business Area Business Area Business Area

355 – DSS Office of 357 – DSS Office of 370 – DSS Office of 374 - DSS
Family Support the Secretary Community Services Rehabilitation Services

Cost Center

Should we use existing agency numbers

Cost Cost
Center Center or renumber the business areas using
logical numbering and groupings?
Cost Cost Cost Cost
Center Center Center Center

26
 Materials Management

 Procurement Process
Management
 Contract Management
MM  Inventory Management
 Distribution
 Vendor Management

27
 Plant Maintenance

 Management of equipment
and technical objects
 Preventive Maintenance
PM  Maintenance Management
 Maintenance history
 Work order history
 Maintenance cost
history
28
 Organizational Elements
Logistics

Plant
 An organizational unit serving to subdivide an enterprise according to
production, procurement, maintenance, and materials planning aspects.
It is a place where either materials are produced or goods and services
provided.
 The business area that is responsible for a plant is determined as a
function of the division. As a rule, a valuation area corresponds to a
plant (e.g., Valuated Inventories are maintained at the Plant level!)
 A plant can be subdivided into storage locations, allowing stocks of
materials to be broken down according to predefined criteria (for
example, location and material planning aspects).
 A plant can be subdivided into locations and operational areas.
Subdivision into locations takes geographical criteria into account,
whereas subdivision into operational areas reflects responsibilities for
maintenance.
 Field Length: 4
29
 Organizational Elements
Logistics

Storage Location
 An organizational unit facilitating differentiation between the various
stocks of a material within a plant.
 A storage location is the place where stock is physically kept within a
plant.
 A storage location has the following attributes:
 There may be one or more storage locations within a plant.
 A storage location has a description and at least one address.
 It is possible to store material data specific to a storage location.
 Physical inventories are carried out at storage location level.
 Storage locations are always created for a plant.
 Field Length: 4

30
 Sample Logistics Structure

NNo
oM aintained*
Maintained*
Company
Company Inventory aat
Inventory t DDepartment
epartment
Code
Code0001
0001 oor
r AAgency
gency LLevel
evel

Plant
Plant Plant
Plant Plant
Plant
A001
A001 B002
B002 C003
C003
Department Level
Storage
Storage Storage
Storage Storage
Storage Agency Level
Location
Location Location
Location Location
Location
A001
A001 B001
B001 C001
C001
Storage
Storage Storage
Storage Storage
Storage
Location
Location Location
Location Location
Location
A002
A002 B002
B002 C002
C002
Storage
StorageStSt Storage
StorageStSt Storage
Storage
Storage SStt
Storage
Storage Storage
Storage Storage
Location
orage Location
orage Location
orage
orage
orage
Location orage
Location Location
LoLocation
A003 cc Lo cation
B003
Lo cc LoLoLocation
C003
L cc
LoLocation
A003
LoLocation ocation
A003
ation
ation A003
ation
ation ation
ation
A003 A003
A003 B003 A003
A003 C003
A003 AA003
A003 A003 003 * Valuated
31
 Sample Logistics Structure

Company
Company
Code
Code0001
0001 InInventory*
ventory* isisM aintained
Maintained
aat
t AAgency
gency LLevel
evel

Department Level

Plant Plant Plant Agency Level

Plant Plant Plant
A001
A001 B002
B002 C003
C003
Storage
Storage Storage
Storage Storage
Storage
Location
Location Location
Location Location
Location
A001
A001 B001
B001 C001
C001
Storage
Storage Storage
Storage Storage
Storage
Location
Location Location
Location Location
Location
A002
A002 B002
B002 C002
C002
Storage
StorageSto Storage
StorageSto Storage
StorageSto
StorageSto Storage Sto
Storage StorageSto
Storage
Location
rage Location
rage Storage
Location
rage
rage rage
Location rage
LoLocation
Location
A003 cc
cation LoLo
Location
B003 cc
cation Lo Location
Lo
Location
C003 cc
cation
Lo
A003 LoA003 LoA003
ation
ation ation
ation ation
ation
A003 A003 B003 A003 C003 A003 * Valuated
A003 A003 A003 A003 A003 A003 32
 Scenario: Less Plants / More Storage Locations
HHeerere……
Plant = Department
Plant = Department
Storage Location = Buildings
Storage Location = Buildings
1 of More Storage
Pros 1 of More StorageLocations
Locations==Agency
Agency Cons
••Single
Singlematerial
materialvaluation
valuation@@Plant
Plant • • Single
Single material
material valuation
valuation @
@ Plant
Plant
Level (i.e., a given material is valuated
Level (i.e., a given material is valuated Level (i.e., a given material is valuated
Level (i.e., a given material is valuated
the
thesame
samefor forall
allStorage
StorageLocations
Locations the
thesame
samefor forall
allStorage
StorageLocations
Locations
assigned to that Plant)
assigned to that Plant) assigned to that Plant)
assigned to that Plant)
••Different
DifferentStorage
StorageLocations
Locationsforforeach
each • •Material
MaterialMRP
MRPattributes
attributesare
arethe
thesame
same
physical
physicallocation
location(e.g.,
(e.g.,street
streetaddress)
address) for
forall
alllocations
locations(min/max,
(min/max,safety
safetystock,
stock,
etc.)
etc.)
••Easier
Easierconfiguration
configurationset-up
set-upand
and
maintenance
maintenance

••Less
Lessdata
datamaintenance
maintenance(since
(sincematerial
material
master
masterrecords
recordsare
aremaintained
maintainedatatthe
the
Plant
PlantLevel)
Level)

••Simplified
Simplifieddesign
design(less
(lesscomplex)
complex)

33
 Scenario: More Plants / Less Storage Locations
HHeerere……

Plant = Agency
Plant = Agency
Storage Location = Buildings
Storag e Location = Buildings
1 of More Storage
Pros 1 of More StorageLocations
Locations==Department
Department Cons
••Material
MaterialMRP
MRPattributes
attributesare
arethe
thesame
same ••Increased
Increasedconfiguration
configurationmaintenance
maintenance
for all locations (min/max, safety stock,
for all locations (min/max, safety stock,
etc,
etc,values
valuescancanbebemaintained
maintainedfor
foreach
each ••Increased
Increasedday-to-day
day-to-daymaintenance
maintenanceofof
‘stockroom’ within a Agency
‘stockroom’ within a Agency master
masterrecords
records(since
(sincemaster
masterrecords
records
independent
independentofofanother
another are tied to the Plant level)
are tied to the Plant level)
stockroom…”Plant-specific
stockroom…”Plant-specificMaterial
Material
Master Data”)
Master Data”) ••Materials
Materialscan
canbe
becreated
createdcentrally
centrallyand
and
‘extended’
‘extended’totomultiple
multipleplants
plantsby
byaacentral
central
••Greater
Greateroverall
overallflexibility
flexibility control group
control group

••More
Morecomplex
complexdesign,
design,especially
especiallyfrom
from
aacentral controlling perspective
central controlling perspective

34
 “Going In” Logistics Structure Approach

Company
Company
Code
Code0001
0001
MMix
ix oof
f the TTwo
the wo LLevels
evels

Plant
Plant
A001
A001 Department Level
Storage
Storage Plant Plant Agency Level
Location
Plant Plant
Location B002 C003
A001
A001 B002 C003
Storage
Storage Storage
Storage Storage
Storage Guiding Principle: If a given organization
maintains inventory AND it wants to track
Location
Location Location
Location Location
Location the financial costs of that inventory at a
A002
A002 B001
B001 C001
C001 given level, then that organizational level =
SAP Plant
Storage
Storage Storage
Storage Storage
Storage
StSt
Storage
Storage
Location
orage Location
Location Location
Location
orage
Location B002 C002
Note: Physical inventory taking
LoLocation
A003
LoLo c
cation B002 C002 Note: Physical inventory taking
(conducting an inventory and
A003 c
ation (conducting an inventory and
cycle counting) takes place at the
ation Storage Storage cycle counting) takes place at the
A003 A003
A003 StorageStSt
Storage Storage
Storage SStt Storage Location level!
Storage Location level!
A003 Storage
Location Storage
Location
orage
orage orage
orage
Lo Location
cation Lo Location
B003
Lo
LoLo cc
cation LoLocation
C003
L cc
ocation
A003
ation A003
ation
ation ation * Valuated
B003 A003
A003 C003
A003 AA003
A003 003 35
 Enterprise Readiness Challenges

 New numbers?
 Where do I get my reports?

36
 Next Steps

 Prepare and send out meeting minutes to

invitees.
 Draft Design Document is prepared.
 Follow up on action items identified during the
workshop.
 Schedule off-line meeting (s) to discuss areas of
special concern
 Plan follow on workshops, as required.
 Plan validation workshop.
 Ensure all to-do’s are appropriately documented
37
 Questions?
? ? ? ?
? ? ? ? ? ? ?
? ? ?
? ? ? ?? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ?
? ?
?
? ? ? ? ? ? ? ? ?
? ? ? ?
? ? ? ? ? ? ? ?
?
? ? ? ? ? ? ? ? ? ?
? ? ? ?
? ? ? ? ?
? ??
? ? ? ? ? ?
? ?
? ?? ? ?? ? ? ? ? ?
? ? ?? ? ? ? ? ? ? ?
? ? ?
? ? ? ? ? ?
? ? ? ?? ? ? ? ?
? ?
? ? ? ?
?