Functional Design Form

82744620.doc

Version: 1.0

Assignment in SAP ABAP

Sales Order Interactive Report
Version: 1.0

Functional Design Documents

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

Table of Contents
Functional Design........................................................................................................................................3
Document Information.................................................................................................................................3
Document History........................................................................................................................................3
Change Log.............................................................................................................................................3
Approval/Sign-off......................................................................................................................................3
Overview and Scope....................................................................................................................................4
Functional Description..............................................................................................................................4
Assumptions............................................................................................................................................4
Detailed Functional Requirements...............................................................................................................4
Functional Specification...........................................................................................................................4
Process Flow Diagram.............................................................................................................................5
Extension Layout......................................................................................................................................5
Input and Output......................................................................................................................................5
Required SAP Transactions.................................................................................................................5
Input Parameters..................................................................................................................................5
Method to Retrieve Input Parameters...................................................................................................6
Output Parameters...............................................................................................................................6
Method to Release Output Parameters (Output Type).........................................................................6
Method to Update Existing Run Parameters with Latest Run Information............................................6
Reporting.................................................................................................................................................7
Initial Data Set-Up/Conversion Requirements..........................................................................................7
Existing Sample Program(s)....................................................................................................................8
Process and Operational Considerations.................................................................................................8
Network Integration...............................................................................................................................8
Performance.........................................................................................................................................8
Processing Type...................................................................................................................................8
Re-use Details......................................................................................................................................8
Expected Transaction Volumes............................................................................................................8
Error Handling.......................................................................................................................................8
Security and Authorization....................................................................................................................8
Purge and Archive Considerations.......................................................................................................8
Multi-company, Multi-jurisdiction Considerations..................................................................................8
Other.....................................................................................................................................................8
Change Management Requirements.......................................................................................................8
Testing Requirements..................................................................................................................................9
Key Business Test Conditions.................................................................................................................9
Technical Test Conditions........................................................................................................................9
Testing Considerations/Dependencies ....................................................................................................9
Outstanding Issues......................................................................................................................................9
Appendix......................................................................................................................................................9
Glossary of Terms....................................................................................................................................9
Additional Supporting/Reference Documentation.....................................................................................9
Solution Review Board input........................................................................................................................9

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

Functional Design
Document Information
Extension Name
Functional Area
Functional Designer
Developer

Sales Order Report

RTR

Document History
Change Log
Name

Change

Date

Version

Approval/Sign-off
Name

Role

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Date

Signature

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

Overview and Scope

This document includes functional requirements and some implementation details. It is possible that
some implementation details might be adjusted in the technical design.

Functional Description
The purpose of this development is to display a report of Orders created during a time period. This
enables for weekly & monthly reporting on the Ordering activities. However what are not covered under
the purview of this development is the Order changes that happen during the time period.
Provisions for downloading the report to the desktop and interactive features are some of the additional
requirements from the report for ease of reporting and usage.
Processing within SAP
A custom transaction code, ZORDREP, will be created and linked to an ABAP program
ZCASE0003_Order_Report to display a report of the Sales Orders created during a time period.

Dependencies/Constraints
Assumptions
We assume that Orders pre-exist in SAP prior to running the program.

Detailed Functional Requirements

Functional Specification
Source
The source of Order data comes from different SAP tables. The Output will contain data pertaining to
multiple Order lines.
File specification:
None.
SAP Process
The user logs on the SAP ECC 6.0 and calls the custom transaction ZORDRPT, which prompts the user
to enter restricting values for the report output to be displayed.
This program will have the following fields in the selection screen:
Sales Order Number (VBAK-VBELN) - Select Option.
Sales Order Type (VBAK-AUART) Select Option.
Creation Date (VBAK-ERDAT) - Select Option. By default, the program should be run for the
current Month ie between the starting and ending date of the current month when the program is
run.
Fields entered in selection screen are validated and any errors are reported and processing stopped.
Fields from the following tables need to be displayed in the primary report in the following order:
4
Modified: 1/28/2012 5:18 a1/p1
Last modified by: Bunty Jain SAP
2010 A2Z. All Rights Reserved.
ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

1)
2)
3)
4)
5)
6)

Order Number (VBAK-VBELN),

Order Line Item (VBAP-POSNR),
Order Type (VBAK-AUART),
Creation Date (VBAK-ERDAT),
Created by (VBAK-ERNAM),
Header Sold-To (VBPA-KUNNR), (Hint: Retrieve with VBPA-POSNR = 000000 & VBPAPARVW = AG)
7) Customer Group (VBKD-KDGRP) and
8) Any Header Text (Use READ_TEXT FM to retrieve any header text).
Option to SINGLE CLICK on Order Number field to display the corresponding the Order from VA03
transaction.
If the user double clicks on any other field, Order line item details corresponding to the line selected by
the user needs to be displayed with the following fields:
1) Order Number (VBAK-VBELN),
2) Order Line Item (VBAP-POSNR),
3) Material Number (VBAP-MATNR),
4) Material Description (MARA-MAKTX),
5) Line Item Quantity (VBAP-KWMENG),
6) Line Item Sold-To (VBPA-KUNNR), (Hint: Retrieve with VBPA-POSNR = VBAP-POSNR & VBPAPARVW = AG)
7) Schedule Line Number (VBEP-ETENR), (HINT: There can be more than 1 record for every line
item (VBELN & POSNR combination) in this table and hence all records needs to be displayed).
8) Schedule Line Confirmed Quantity (VBEP-BMENG) and
9) Any Line Item Text (Use READ_TEXT FM to retrieve any Item Text).
Log

Process Flow Diagram

Extension Layout
None required

Input and Output

Required SAP Transactions
ZORDREP & SE38.
Input Parameters

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

Input (Parameters) Needed

Order Number (Optional)

Description and Prior Dependency

Order Number to restrict the data displayed in
Output.

Order Type (Optional)

Order Type to restrict the data displayed in

Output.

Creation Date (Mandatory)

Date interval in which the Order was created.

Need to display the starting and ending date of
the current month when the program is
executed by default.

Validation
F4 help needs to
be provided &
Error message if
the Order
Number does not
exist.
F4 help needs to
be provided &
Error message if
the Order Type
does not exist.
F4 help needs to
be provided &
Error message if
the Creation
Date in invalid.

Method to Retrieve Input Parameters

Output Parameters
Output (Parameters) Needed
Screen output of report
Interactive report of line item
display and also navigation to
Order display transaction.
Download report contents to
presentation server

Description and Post Dependency

None
None
None

Method to Release Output Parameters (Output Type)

Program log may be printed or downloaded to file using standard SAP menu:

Method to Update Existing Run Parameters with Latest Run Information

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

The program log should be examined to ensure that the right Orders get displayed in the report. For
further details, please see the Error Handling section.

Reporting
Standard report with Order header details, Secondary list with Line item details and an option to navigate
to the display Order transaction.
Also display a standard report header with Program Name, Run Date, Run Time & Company Name on
both Primary and Secondary lists.
In the report footer displayed in both Primary and Secondary lists, display the Page Count as PAGE: n/m,
where n is the current page number and m is the total pages.

Initial Data Set-Up/Conversion Requirements

No data conversion requirements.

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

Existing Sample Program(s)

No sample program available.

Process and Operational Considerations

Network Integration
No network integration considerations.
Performance
Performance is dependent on the number of records retrieved. Foreground processing of the report
should not exceed time out setting for online processing. Report can also be run in background.
Processing Type
Foreground & Background processing should be possible.
Re-use Details
Rerun the program for the same selection.
Expected Transaction Volumes
This will vary based on the number of Orders created for the processing period.
Error Handling
In case of errors, rerun the program for the same selection.
Security and Authorization
The transaction code should be featured in the same authorization profiles as Report transaction, SE38.
Purge and Archive Considerations
Multi-company, Multi-jurisdiction Considerations
Other

Change Management Requirements

Range of use
Number of Line items
There is no limit to the number of line items that can be present in an Order and displayed in report
output.

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

82744620.doc

Version: 1.0

Testing Requirements
Key Business Test Conditions
ID

Condition

Expected results

Actual
Result

Input field validations for all 3 fields

Primary list displayed.

Secondary List displayed

Error with program execution

Input field validation is done and

standard
field
validation
errors
handled.
Check fields displayed in Primary list
and interactive feature for navigating to
Display transaction and secondary list.
Check fields displayed in secondary
list.
Rerun the program for the same
selection.

Technical Test Conditions

ID

Condition

Expected results

Actual
Result

Testing Considerations/Dependencies

Outstanding Issues
Issue
No

Description

Assigned To

Status

Impact

Resolution

Appendix
Glossary of Terms
Term

Definition

Additional Supporting/Reference Documentation

Solution Review Board input

Modified: 1/28/2012 5:18 a1/p1
2010 A2Z. All Rights Reserved.

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com

Functional Design Form

Input
Technical Details
Estimate

Modified: 1/28/2012 5:18 a1/p1

2010 A2Z. All Rights Reserved.

82744620.doc

Version: 1.0

Comments
This document contains functional requirements and some technical
implementation details. These implementation details are subject to
change in the technical design.
An estimate of work effort needs to be included in the technical
design. The design of this solution should be kept technical simple
and we should encourage users to minimize the use of the upload
process.

10

Last modified by: Bunty Jain SAP

ABAP, Delhi, India, IT Training.
seekbuntyjain@gmail.com