Functional Specification: ASAP Implementation Methodology

You might also like

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 21

ASAP Implementation Methodology

FUNCTIONAL SPECIFICATION
SCENARIO (SALES REGISTER REPORT): <NAME>
BUSINESS PROCESS: < SALES PROCESS >

PROJECT IDENTIFICATION

Project Name

Customer Name
Mrs. Bector’s Food
YASH Project Manager Customer Project Manager
Satish Singh Mr. Gurdeep Sindhu

Author Document Location (repository/path/name)

Version Status Date (YYYY-MM-DD)


1.0 WIP / Final

REVISION HISTORY

Version Date Description


1.0
2.0

REVIEW AND APPROVAL

1 of 21
ASAP Implementation Methodology

Name : N.K.Gupta Date (YYYY-MM-DD)


Customer Project Manager

Name: Lalit Joshi Date (YYYY-MM-DD)


SAP Project Manager

Name Date (YYYY-MM-DD)


Key Stakeholder

Name Date (YYYY-MM-DD)


Key Stakeholder

2 of 21
ASAP Implementation Methodology

TABLE OF CONTENT

1. PURPOSE OF THIS DOCUMENT 4


2. GENERAL OBJECT OVERVIEW 5
2.1 Process Requirements Reference 6
2.2 Generic WRICEF Descriptions 6
3. OBJECT SPECIFIC DESIGN 8
3.1 Reporting (operational and analytical) 8
3.2 Interfaces 12
3.3 Data Conversion / Historical Data 15
3.4 Enhancements 17
3.5 Output (e.g. forms) 18
3.6 Workflow 20
4. Test Conditions 21

3 of 21
ASAP Implementation Methodology

1. Purpose of this document

4 of 21
ASAP Implementation Methodology

2. General Object Overview

Object Overview

Business
Object ID
Process

ECC 6.0 SAP Sales & Distribution


SAP Release
Module
(√ ) Report
( ) Interface
( ) Conversion
Object Type ( ) Enhancement
( ) Form
( ) Workflow

Object Title Sales Register

Object Description Sales Register

Mock Up ID / Name

Required
Cycle of Testing / C1 / C2 / C3 / C4 Development
Sprint Cycle
Completion Date

Complexity of Object Medium Priority High

SAP Transaction Z SAP Program


Name Name

Similar SAP Similar SAP


Transaction Program

FS CONTROL

<Customer>
Functional Consultant
Process Owner
– Author and Phone
and Phone
Number
Number

Planned Date of FS Actual Date of FS


Completion Completion

FS Approved By FS Approval date

Other Contact and Other Contact and


Phone Number Phone Number

5 of 21
ASAP Implementation Methodology

2.1 Process Requirements Reference


Process Reference
Requirement ID
Requirement
Description
Gap to be addressed
Alternative SAP
Standard Solution

2.2 Generic WRICEF Descriptions


Justification

FUNCTIONAL DESCRIPTION / DESIGN

TRANSACTION VOLUME

6 of 21
ASAP Implementation Methodology

FREQUENCY & TIMING

DEPENDENCIES

AUTHORIZATION REQUIREMENTS

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING


REPORT, ETC)

7 of 21
ASAP Implementation Methodology

3. Object Specific Design


3.1 Reporting (operational and analytical)

Reporting
WRICEF- Description Report Type Data Elements Relevant KPI Owner
ID (ABAP, BI,
BOBJ)
XX-xx-
R001

Selection Criteria

1. Please Refer to the attached Excel file for details.

Table/ Field Name Format Default Table Select Mandatory Field


Structure Value Value/ Option or or Labels
Name Checkbox/ Parameter Optional
Radio
Button/
Radio
Button
Group

8 of 21
ASAP Implementation Methodology

Functional Design, Validation and Variants

9 of 21
ASAP Implementation Methodology

Report Output

Output Method

Example:
Saved to File / Sent to print / Send to email account / Download to excel

Main Heading

Example:
The main report heading will be: Contracts Nearing Expiry

Sub Heading

Example:
There will be a sub section under the main contract information detailing the date and time the report
was executed and the users username

LAYOUT
Table/Structure Field Format Default Value Column Name Translation Rule
Name Name (ie
decimal
places)

10 of 21
ASAP Implementation Methodology

DRILLDOWN REQUIREMENTS

TOTALING

Example:
Number of contracts matching user selection criteria to be displayed at the bottom of the report

Any page-break requirements?

SORTING

Example:
Users will be able to sort on contract type and vendor. Default sort sequence will be by contract type.

Any page-break requirements?

PAGE BREAK

Example:
Page breaks will be used where necessary to prevent overflow of retrieved data

ERROR HANDLING

Typical errors include: No data found for given selection criteria.

11 of 21
ASAP Implementation Methodology

3.2 Interfaces
.>

Interface
WRIC Description Interface Applications Data Elements Frequency / Owner
EF-ID Method Volumes
XX-xx-
I001

Interface Process Flow Diagram, incl.Transfer Method/ Network Integration

File Specifics

MAPPING SAP FIELDS TO SOURCE / TARGET

12 of 21
ASAP Implementation Methodology

RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Reporting

Approach

Metrics

Error Handling

13 of 21
ASAP Implementation Methodology

3.3 Data Conversion / Historical Data

Conversions
WWRICE Conversion Source Conversion Conversion # of Objects Owner
F-ID Object Activities Method (manual to be
(e.g. / automated) converted
cleansing)
XX-xx-
C001
1MAPPING SAP FIELDS TO SOURCE / TARGET

RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Reporting

Approach

Metrics

Error Handling

14 of 21
ASAP Implementation Methodology

3.4 Enhancements

enhancements
WRIC Description Data Object Functional Alternative SAP Reason Owner
EF-ID (Sales Order) Gap Standard

Functional Design / Flow, Validation and Variants

Flow

Design

15 of 21
ASAP Implementation Methodology

3.5 Output (e.g. forms)

Output
WRIC Description Data Object Output Type Frequency Volumes Owner
EF-ID (Sales (Form, EDI, etc.)
Order)
XX-xx-
O001

Process Flow Diagram

16 of 21
ASAP Implementation Methodology

1. Top Address:- Sales Office Address (VBRP - VKBUR = TVBUR - VKBUR, Get TVBUR -
ADRNR) ( TVBUR - ADRNR = ADRC - ADDRNUMBER, Get Name 1, Name 2, Street, City, Pin
Code., Ph.No.)
2. TO:- Sold TO Party (VBRK - KUNAG = KNA1 - KUNNR, Get KNA1 - ADRNR. KNA1 - ADRNR
= ADRC - ADRNR, Get Name 1, Name2, Street, Street2, City, Pin.)
3. TinNo. VBRK - KUNAG =J_1IMOCUST – KUNNR, Get J_1IMOCUST - J_1ILSTNO
4. Cst No. VBRK - KUNAG =J_1IMOCUST – KUNNR, Get J_1IMOCUST - J_1ICSTNO
5. Sale Order Reference No. VBRP - AUBEL
6. Delivery No. VBRP - VBGEL
7. Bill No. VBRK - VBELN
8. Despatch Thru – Will be Given Once Transportation is Ready
9. Truck No. – Will be given once Transportation is Ready
10. Weight – Will be given once Transportation is Ready
11. Sl.No.
12. Item Description:- VBRP - ARKTX
13. Quantity:- VBRP - FKIMG
14. Rate:-
1. VBRK - KNUMV = KONV - KNUMV, Get KONV - KSCHL, Pass KONV - KSCHL = ZR00, get KONV -
KBETR.
2. VBRK - KNUMV = KONV - KNUMV, Get KONV - KSCHL, Pass KONV - KSCHL = ZVAT, Get KONV -
KBETR.
3. VBRK - KNUMV = KONV - KNUMV, Get KONV - KSCHL, Pass KONV - KSCHL = ZAVT, Get KONV -
KBETR 4.
VBRK - KNUMV = KONV - KNUMV, Get KONV - KSCHL, Pass KONV - KSCHL = ZCST, Get KONV –
KBETR 5.
VBRK - KNUMV = KONV - KNUMV, Get KONV - KSCHL, Pass KONV - KSCHL = ZTCS, Get KONV -
KBETR

15. Total :- Rate* Quantity


16. Total :- Total of Line Item
17. Amount In Words : - Amount to be in worlds

Form Layout

17 of 21
ASAP Implementation Methodology

Example:

1
Form Title Date: xxxxx
2
User: xxxxx

ID Value Description
3 4 5
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx

18 of 21
ASAP Implementation Methodology

Printer Requirements

Legal Requirements

Existing Sample Forms

19 of 21
ASAP Implementation Methodology

3.6 Workflow

Workflow
WRIC Description Business / Data Object (Sales Engaged Parties Owner
EF-ID Order)
XX-xx-
W001

Process Flow Diagram

Trigger Events

Transactions and Batch Programs that trigger the workflow

Start Conditions

Rules and Determination

Standard Rules

Latest End, Latest Start

20 of 21
ASAP Implementation Methodology

4. Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)

Scenario # Input Selection Criteria Expected Result

21 of 21

You might also like