Professional Documents
Culture Documents
Business Process Library / Business Process Master List (BPML)
Business Process Library / Business Process Master List (BPML)
Depending on the project requirements (project type, size, customer contract), the following sections have to be processed:
responsibilities
GAP analysis
NOTE:
Please delete the supplied sample data before using this template!
Please hide unused columns.
Please refer to the respective project standards for the naming convention for the BPML file.
IMPORTANT: Please do not insert new lines below the process id 999999 !
572561035.xlsx Seite 1 von 23 Seiten All for One Steeb AG
Business Process Library / Business Process Master List (BPML)
Company:
Project Number:
Topic:
Responsible:
Supported by:
Acceptance by:
ocess Library / Business Process Master List (BPML)
Customer name e.g. SUNRISE AG
XXXXX
e.g. Implementation_x000D_
of the SAPTM Industry Solution NN®
Based on the All for One Steeb “Active Prototyping”_x000D_
Implementation Method
Project Manager
Sub-Project Manager
GAP analysis
group description tile description tile description transactio app id app description (en) URL-Link level prerequisites application data & attributes output object composite role single role source of degree of need for action need for action need for
(en) (de) (en) n number per scope item solution functional solution
(e.g. user preferences) (e.g. org. units, masterdata, ordertype, etc.) (e.g. forms, edi, etc.) coverage (description) (classification)
(SAP standard / (priority)
industry solution /
template available)
field
process id
value list
none
field
requirement id
value list
none
field
process category
value list
core business process
management process
support process
field
functional area
value list
none
field
process
value list
none
field
sub-process
value list
none
field
sub-process steps
value list
none
field
process variant
value list
none
field
process variant
value list
none
field
system of execution
value list
n/s
manual
WEB
ERP
field
business process requirements
value list
none
field
report
interface
converion
enhancement
form
value list
none
field
requirement type
value list
global
local
legal
field
location 1;
location 2;
location 3;
location 4;
etc.
value list
Y
N
field
business process owner
value list
PBO 1
PBO 2
PBO 3
PBO 4
field
key user
value list
key user 1
key user 2
key user 3
key user 4
field
consultant
value list
consultant 1
consultant 2
consultant 3
consultant 4
consultant 5
field
scope item id
value list
none
field
scope item description (de);
scope item description (en)
value list
none
field
business process area (scope item)
value list
none
field
main business area (scope item) (en)
value list
none
field
sub business area (scope item) (en)
value list
none
field
scope item step id
value list
none
field
value list
none
field
business process area (scope item
step)
value list
none
field
IT application
value list
n/s
S/4HANA
C/4HANA
ARIBA
EXCEL
EXTERNAL
field
group description (de);
group description (en)
field
tile description (de);
tile description (en)
value list
none
field
transaction
value list
none
field
app id
value list
none
field
app description (en)
value list
none
field
URL-Link
value list
none
field
level number
value list
none
field
prerequisites
value list
none
field
application data & attributes
value list
none
field
output object
value list
none
field
composite role per scope item
(frontend) (SI_FE)
value list
none
field
role frontend (menu) (FLP)
role frontend (ODATA) (FLA)
role authentification (AUT)
value list
none
field
source of solution
value list
SAP standard
industry solution
template
field
degree of functional coverage
value list
no coverage
conditional coverage
full coverage
field
need for action (description)
value list
none
field
need for action (classification)
value list
legal requirement
request based on customer contract
field
need for solution (priority)
value list
critical
important
less important
nice-to-have
field
potential solution approach
(sketch, draft)
value list
none
field
solution type
value list
Customizing
Report
Interface
Conversion
Enhancement
Form
Training
Organizational Change
field
expected benefit
value list
no benefit
minimal benefit, hardly measurable
improvement in sub-areas
significant improvement
field
organizational change
value list
none
low
medium
high
field
effect on sites that are already
productive with the template
value list
no effect
effect still to be analyzed
new functions to be implemented
(redeployment)
field
integration
value list
none
low
medium
high
field
realization
value list
none
low
medium
high
field
migration
value list
none
low
medium
high
field
training
value list
none
low
medium
high
explanation
unique number / id of the process
explanation
explanation
unique number / id of the requirement - only if it originates from a requirement
specification
explanation
explanation
grouping of processes by category
explanation
explanation
brief designation of the functional area
explanation
explanation
brief designation of the process
explanation
explanation
brief designation of the sub-process
explanation
explanation
brief designation of the sub-process steps
explanation
explanation
brief specification of the process variant
explanation
explanation
brief specification of the process variant
explanation
explanation
brief specification of the system of execution
explanation
not specified
action happens manually
action takes place in www
action takes place in ERP-System
explanation
rough and easy-to-understand description of the business requirement
explanation
explanation
specification of the objects currently in use e.g.
report "incoming orders", form "order confirmation", etc.
explanation
explanation
specification of requirement type
explanation
Central function, common usage by all group companies
Functionality used in one country, no legal requirement
Legal requirement - implementation mandatory
explanation
indicates whether a location uses the process
explanation
Yes
No
explanation
name of the business process owner
explanation
explanation
name of the key user
explanation
explanation
name of the consultant
explanation
explanation
unique number of the scope item
explanation
explanation
brief designation of the scope item in german and englisch language
explanation
explanation
key of the business process area
explanation
explanation
short description of the main business area per scope item
explanation
explanation
description of the sub business area per scope item
explanation
explanation
unique number / id of the scope item step
explanation
explanation
brief description of the scope item step in german and englisch language
explanation
explanation
key of the business process area per scope item step
explanation
explanation
brief specification of the IT application
explanation
not specified
action takes place in S/4HANA
action takes place in C/4HANA
action takes place in ARIBA
action takes place in MS EXCEL
action doesn´t takes place in a IT application
explanation
brief description of the group in german and englisch language
explanation
brief description of the tile in german and englisch language
explanation
explanation
transaction code
explanation
explanation
unique number / id of the app
explanation
explanation
brief description of the app in englisch language
explanation
explanation
unique id of the URL-Link
explanation
explanation
number of the level within a Scope Item
explanation
explanation
brief description of the needed prerequisites
explanation
explanation
brief description of the needed application data & attributes
(e.g. org. units, masterdata, ordertype, etc.)
explanation
explanation
brief description of the output object
(e.g. forms, edi, etc.)
explanation
explanation
key of the composite role
explanation
explanation
key of the role
explanation
explanation
classification in which way the solution is provided
explanation
solution is provided by SAP standard
solution is provided by the industry solution
solution ist provided by the template
explanation
classification
explanation
business request is not supported
business requirement is only supported to a limited extent / business requirement can
only be solved with the help of a so-called workaround, i.e. additional expenditure in the
day-to-day business
business requirement is fully supported
explanation
brief description why action is needed
explanation
explanation
classification of the needed action
explanation
legal requirements must be fulfilled
requirements from an existing customer contract must be fulfilled
explanation
priority of the need
explanation
GAP must be closed - show stopper
GAP should be closed to avoid overtime due to workarounds
workaround is acceptable
nice-to-have - can also be implemented at a later date
explanation
rough and easy-to-understand description of the potential solution approach
explanation
explanation
priority of the need
explanation
customizing / delta customizing required
report required
interface required
migration of data required
enhancement required
form required
training required
adjustment of structural and/or process organization required
explanation
dimension of the implementation effort
explanation
no measurable benefit expected
Minimal qualitative improvements in day-to-day business (e.g. information transparency);
benefit cannot, however, be calculated in the form of monetary savings; provision of a
solution (close GAP) is therefore rather a "nice-to-have
Recognisable improvement in day-to-day business, e.g. through automation of previously
manual processes; nevertheless, a monetary benefit can only be determined in partial
areas; provision of a solution (close GAP) is an "uncritical" benefit
explanation
degree of organizational change
explanation
explanation
dimension of the implementation effort
explanation
no effect
before a statement can be made, further analyses are necessary
Due to fundamental design changes, these must also be implemented at already
productive locations.
explanation
degree of integration depending on the number of departments concerned
explanation
explanation
dimension of the implementation effort
explanation
explanation
degree of migration depending on the number of migration objects
explanation
2
3 to 6
more than 6
explanation
degree of migration depending on the number of migration objects
explanation
2
3 to 6
more than 6