1. Copyright © 2010 SAP AG. All rights reserved 1 of 11
ASAP Implementation Methodology
KM DOCUMENT CONTRIBUTION DETAILS
DOCUMENT DETAILS
Name Objective Audience Version Description
<Functional Spec
Title>
Used for reference All Users 1.0 Template to contribute ERP
FS Reusable objects
CHANGE LOG
Version Date Author Description Approved By
1.0 June 09, 2012 <Author name> New Template <reviewer‘s name>
For any info on this document please contact:
Name Email ID Contact No
Xxxxxx xxxxx@sap.com Xxxxxx Extn: xxxx
How to use the Template
Blue text is always intended as instructions, guidelines, explanations, hints, and tips. It has to be removed
when the document is finalized. To provide a consistent representation of this document to the customer,
chapters should not be deleted or inserted. Required additions should be made as sub-chapters to existing chapters.
Chapters that are not relevant should be marked as such (that is, add “not relevant” or “not applicable”).
Be sure to delete these instructions when you have finished!
Instructions:
- Address the localized processes in the newly added section .
- Address the Business process Change requests with appropriate business case and ownership along with impact-
mentioning whether the change is local or global.
- While adding visio’s make sure they are editable.
- Mention the Document version and stakeholders clearly – which helps during the sign off.
- Separate set of documents to be created for India, Bangladesh , China and RAK - Porcelain .
- Follow the naming convention strictly so that documents can be traced back easily.

2. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 2 of 11
BUSINESS PROCESS DESIGN
DOCUMENT
SUB-TITLE (01_TITLE SUBHEADLINE)
SCENARIO (BUSINESS AREA): <NAME>
BUSINESS PROCESS: < NAME >
INDUSTRIES APPLICABLE: <All Industries> etc
POTENTIAL REUSABILITY AREAS:
PROJECT IDENTIFICATION
Delete Project Identification table if not applicable for the document!
Project Name CPI Project Number
<Project Name>
Customer Name Customer Number
<Customer Name>
SAP Project Manager Customer Project Manager
<SAP Project Manager> <Customer Project Manager>
DOCUMENT IDENTIFICATION
Document Identification Instruction:
 Update document location
Location could be Solution Manager or other relevant project repository
 Update Version, Status, and Date
Possible statuses are Draft, Ready for internal review, Released for customer, Final. You can for example number the
appropriate versions as follows:
o Draft
o Ready for internal review
o Ready for internal review (in case of major changes)
o Released for customer
o Final
 Update classification:
Internal means the document is restricted to SAP internal use only. Confidential means that only a defined group of people
(such as a CDP team and their customer) have access to the document.
Be sure to delete these instructions when you have finished!
Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Confidential

3. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 3 of 11
REVISION HISTORY
Delete Revision History section below if not applicable for the document!
Version Date Description
0.1 February 4, 2010 <Text here>
0.2
REVIEW AND APPROVAL
Delete Review and Approval section below if not applicable for the document!
Name
Customer Project Manager
Date (YYYY-MM-DD)
Name
SAP Project Manager
Date (YYYY-MM-DD)
Name
Key Stakeholder
Date (YYYY-MM-DD)
Name
Key Stakeholder
Date (YYYY-MM-DD)

4. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 4 of 11
TABLE OF CONTENT
PROCESS DESCRIPTION......................................................................................................................... 5
1.1 Business Process Description ...................................................................................................... 5
1.2 Business Process Diagrams......................................................................................................... 5
1.3 Process Step Detailed Requirements & Solution.......................................................................... 5
1.4 Locations Where this Business Process is Performed.................................................................. 6
1.5 Key Policies/bOperational Decisions or Logic within the Process................................................. 6
1.6 SOX Considerations..................................................................................................................... 6
1.7 Reference to Key Process Changes and Process KPIs................................................................ 6
1.8 Integration Points ......................................................................................................................... 6
1.9 Potential Future Process Improvements (out of scope for this implementation)............................ 6
1.10 Localization specific to country and Process ................................................................................ 7
2. FUNCTIONAL SOLUTION.................................................................................................................. 7
2.1 Organization Structure Considerations......................................................................................... 7
2.2 Master Data Considerations (including all relevant data relationships) ......................................... 7
2.3 System Configuration Considerations........................................................................................... 7
3. TECHNICAL/DEVELOPMENT RELATED ITEMS (WRICEF)............................................................. 7
3.1 Reporting (operational and analytical) .......................................................................................... 7
3.2 Interfaces ..................................................................................................................................... 8
3.3 Data Conversion / Historical Data................................................................................................. 8
3.4 Enhancements ............................................................................................................................. 8
3.5 Output (e.g. forms) ....................................................................................................................... 9
3.6 Workflow ...................................................................................................................................... 9
4. AUTHORIZATION............................................................................................................................. 10
5. ORGANIZATIONAL CHANGE RELATED ITEMS ............................................................................ 10
5.1 Change Impact Summary........................................................................................................... 10
6. BUSINESS PROCESS CHANGE REQUEST ................................................................................... 11

5. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 5 of 11
Process Description
1.1 Business Process Description
Provide a description of the business process. Please note the variations to the process. If the variations are considerably different
then consider creating a separate document for the other variation.
Process Characteristics
Process Trigger
Process Input
Process Output
Process Owner
Process Volumes
Process Frequencies
1.2 Business Process Diagrams
Refer to ARIS/ Viso diagrams.
1.3 Process Step Detailed Requirements & Solution
This section refers to the ARIS/ Visio model. Process Step Roles, Input and Outputs are captured as part of the process model. This
sections contains a descriptive walk-through of the process. Describe the solution for each step or event and any unique variations to
the step or event and the related design considerations, gaps, configuration and/or development items.
Process Step Description
ID
Process Step
Description
Ref. to
Requirements as
applicable
Measure of
successful
delivery
Solution
Description
GAP Description
(WRICEF ID)
XX-xx-
001
XX-xx-
002
XX-xx-
003

6. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 6 of 11
1.4 Locations Where this Business Process is Performed
List all geographic locations/ offices, plants, warehouses etc., where this process is performed. Refer to To-Be Process Landscape.
Locations
Location Country Function Number of Users Point of Contact
1.5 Key Policies/bOperational Decisions or Logic within the Process
Describe key policies, operational decisions, and logic related to this process.
1.6 SOX Considerations
List company policies and SOX consideration within this business process. E.g. segregation of duties and/or reporting requirements.
1.7 Reference to Key Process Changes and Process KPIs
Refer key process change document on process level.
1.8 Integration Points
List known integration topics/ issues with other SAP modules/ components, etc.
Integration Points
ID Integration Point SAP Component Data Element Contacts
1.9 Potential Future Process Improvements (out of scope for this
implementation)
Summarize future improvements, based on requirements that have been discussed that will NOT be implemented in the project.

7. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 7 of 11
1.10 Localization specific to country and Process
Define the localized processes with respect to country and existing processes.
2. Functional Solution
2.1 Organization Structure Considerations
Document all organizational structure related items that are related to this business process e.g. plants, etc. Note the requirements
and the related design considerations.
2.2 Master Data Considerations (including all relevant data relationships)
Document all relevant master data requirements / implications and all master data relationships. Attach diagrams as necessary for
illustrating any relationships e.g., Results Analysis data relationships, or illustration that shows how work centers, capacities, cost
rates all relate together, or the relationship of key data elements for profitability analysis, etc.)
2.3 System Configuration Considerations
Identify configuration requirements/considerations as they are known at this point. i.e., Order types, billing types, copy routines, item
categories, risk categories, condition types, pricing procedures, settlement rules, etc. This section could be lengthy dependent on the
nature of the solution and the level of detail of design. The more complex the topic the more detail you want to have in this section.
This could be just short of actual configuration notes but you should include special items that you do not want to forget about during
configuration
3. Technical/Development Related Items (WRICEF)
3.1 Reporting (operational and analytical)
This is just a listing. Details for the report in the functional spec. If the reporting will be done out of BW then list the info sources etc.
Reporting
WRICEF
ID
Description
Report Type
(ABAP, BI, BOBJ)
Data Elements Relevant KPI Owner
XX-xx-
R001
XX-xx-
R002
XX-xx-
R003

8. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 8 of 11
3.2 Interfaces
Identify all interfaces required to provide inputs to or outputs from this part of the process. Provide a functional description of the
interfaces including the source and type of data.
Interfaces
WRICEF
ID
Description Interface Method Applications
Frequency /
Volumes
Owner
XX-xx-
I001
XX-xx-
I002
XX-xx-
I003
3.3 Data Conversion / Historical Data
Note all master and transactional data conversion requirements. Please note specific fields that are unique to this design and the
business requirement that drives that design. Note whether manual and automated data conversion requirements. Provide details of
all data required from Legacy Systems (Consider System name, level of detail, time dimension). Identify requirements for historical
data conversion mandatory for the process. This is not meant to be an exhaustive functional spec but a place to list conversions
related to this process.
Conversions
WRICEF
ID
Conversion
Object
Source
Conversion
Activities
(e.g. cleansing)
Conversion
Method
(manual /
automated)
# of Objects to
be converted
Owner
XX-xx-
C001
XX-xx-
C002
XX-xx-
C003
3.4 Enhancements
List the required enhancements based on the proposed gap resolutions listed in the Detailed Requirements and Design documents.
Provide as much detail on the requirements and design considerations as you can. If there is a large enhancement then consider
detailing that in a separate design or functional spec. document.

9. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 9 of 11
Enhancements
WRICEF
ID
Description
Data Object
(Sales Order)
Functional
Gap
Alternative
SAP Standard
Reason Owner
XX-xx-
E001
XX-xx-
E002
XX-xx-
E003
3.5 Output (e.g. forms)
Identify outputs and forms.
Output/ Forms
WRICEF
ID
Description
Data Object
(Sales Order)
Output Type
(Form, EDI,
etc.)
Frequency Volumes Owner
XX-xx-
O001
XX-xx-
O002
XX-xx-
O003
3.6 Workflow
Identify workflow requirements for this process. Provide detailed requirements for the workflow. e.g., purchase order approval
process and authority levels etc.
Workflows
WRICEF
ID
Description
Data Object
(Sales Order)
Engaged Parties Owner
XX-xx-
W001
XX-xx-
W002
XX-xx-
W003

10. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 10 of 11
4. Authorization
Indicate any special authorization requirements associated with this process e.g. Segregation of duties. Identify the groupings or
type of employees that will have access to system functionality for this activity, if applicable.
Authorizations
ID Authorization
Data Objects
(Sales Order / TA code)
Reason # of employees
XX-xx-
A001
XX-xx-
A002
XX-xx-
A003
5. Organizational Change Related Items
5.1 Change Impact Summary
Identify business process changes and the impact to the company and to individual roles.
Organizational Change Impact
Change Impact Summary Old Way New Way
Positive Impacts
To Company
To individual roles
Negative Impacts
To Company
To individual roles
Process Strategy
e.g., Principles How High-level
data flows
Process & Metrics
(focus on key changes to
specific steps and
transactions)
Roles, responsibilities
and organization
(Who’s accountable?
Who’s responsible?
Who’s consulted?
Who’s informed)

11. ASAP Implementation Methodology
Copyright © 2010 SAP AG. All rights reserved 11 of 11
Roles, responsibilities
and organization
(Who’s accountable?
Who’s responsible?
Who’s consulted?
Who’s informed?)
6. Business Process Change Request
All the gaps with respect to Business processes will be detailed in this section along with the relevance and need for change.
This section will also distinguish local gaps or a Gap in the Global template along with Process(s) and module(s) impacted and gap
owner mentioned.