SAP ABAP Assignment - Sales Order Interactive Report

12
Functional Design Form document.doc Version: 1.0 Assignment in SAP ABAP Sales Order Interactive Report Version: 1.0 Functional Design Documents Modified: 8/23/2022 10:12 PM ©2010 A2Z. All Rights Reserved. 1 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

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. SAP ABAP programming

Transcript of SAP ABAP Assignment - Sales Order Interactive Report

Page 1: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

Assignment in SAP ABAPSales Order Interactive Report

Version: 1.0

Functional Design Documents

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

1 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 2: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

Table of Contents

Functional Design........................................................................................................................................ 3Document Information................................................................................................................................. 3Document History........................................................................................................................................ 3

Change Log............................................................................................................................................. 3Approval/Sign-off...................................................................................................................................... 3

Overview and Scope.................................................................................................................................... 4Functional Description.............................................................................................................................. 4Dependencies/Constraints....................................................................................................................... 4Assumptions............................................................................................................................................ 4

Detailed Functional Requirements...............................................................................................................4Functional Specification........................................................................................................................... 4Process Flow Diagram............................................................................................................................. 5Extension Layout...................................................................................................................................... 5Input and Output...................................................................................................................................... 5

Required SAP Transactions................................................................................................................. 5Input Parameters.................................................................................................................................. 5Method to Retrieve Input Parameters...................................................................................................6Output Parameters............................................................................................................................... 6Method to Release Output Parameters (Output Type).........................................................................6Method to Update Existing Run Parameters with Latest Run Information............................................6

Reporting................................................................................................................................................. 6Initial Data Set-Up/Conversion Requirements..........................................................................................6Existing Sample Program(s).................................................................................................................... 7Process and Operational Considerations.................................................................................................7

Network Integration.............................................................................................................................. 7Performance......................................................................................................................................... 7Processing Type................................................................................................................................... 7Re-use Details...................................................................................................................................... 7Expected Transaction Volumes............................................................................................................7Error Handling...................................................................................................................................... 7Security and Authorization....................................................................................................................7Purge and Archive Considerations.......................................................................................................7Multi-company, Multi-jurisdiction Considerations..................................................................................7Other.................................................................................................................................................... 7

Change Management Requirements.......................................................................................................7Testing Requirements.................................................................................................................................. 8

Key Business Test Conditions.................................................................................................................8Technical Test Conditions........................................................................................................................ 8Testing Considerations/Dependencies.....................................................................................................8

Outstanding Issues...................................................................................................................................... 8Appendix...................................................................................................................................................... 8

Glossary of Terms.................................................................................................................................... 8Additional Supporting/Reference Documentation.....................................................................................8

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

2 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 3: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

Functional Design

Document InformationExtension Name Sales Order ReportFunctional Area RTRFunctional DesignerDeveloper

Document History

Change LogName Change Date Version

Approval/Sign-offName Role Date Signature

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

3 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 4: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

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

Functional DescriptionThe 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:

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

4 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 5: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

1) Order Number (VBAK-VBELN),2) Order Line Item (VBAP-POSNR),3) Order Type (VBAK-AUART),4) Creation Date (VBAK-ERDAT),5) Created by (VBAK-ERNAM),6) Header Sold-To (VBPA-KUNNR), (Hint: Retrieve with VBPA-POSNR = ‘000000’ & VBPA-PARVW

= ‘AG’)7) Customer Group (VBKD-KDGRP) and8) 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 & VBPA-

PARVW = ‘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) and9) Any Line Item Text (Use READ_TEXT FM to retrieve any Item Text).

Log

Process Flow Diagram

Extension LayoutNone required

Input and Output

Required SAP Transactions

ZORDREP & SE38.

Input Parameters

Input (Parameters) Needed Description and Prior Dependency ValidationOrder Number (Optional) Order Number to restrict the data displayed in

Output.F4 help needs to be provided & Error message if the Order Number does not exist.

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

5 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 6: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

Order Type (Optional) Order Type to restrict the data displayed in Output.

F4 help needs to be provided & Error message if the Order Type does not exist.

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.

F4 help needs to be provided & Error message if the Creation Date in invalid.

Method to Retrieve Input Parameters

Output Parameters

Output (Parameters) Needed Description and Post DependencyScreen output of report NoneInteractive report of line item display and also navigation to Order display transaction.

None

Download report contents to presentation server

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

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.

ReportingStandard report with Order header details, Secondary list with Line item details and an option to navigate to the display Order transaction.

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

6 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 7: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

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 RequirementsNo data conversion requirements.

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

7 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 8: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.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: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

8 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 9: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

Testing Requirements

Key Business Test Conditions

ID Condition Expected results Actual Result

1 Input field validations for all 3 fields Input field validation is done and standard field validation errors handled.

2 Primary list displayed. Check fields displayed in Primary list and interactive feature for navigating to Display transaction and secondary list.

3 Secondary List displayed Check fields displayed in secondary list.

4 Error with program execution Rerun the program for the same selection.

Technical Test Conditions

ID Condition Expected results Actual Result

Testing Considerations/Dependencies

Outstanding IssuesIssue No

Description Assigned To Status Impact Resolution

Appendix

Glossary of TermsTerm Definition

Additional Supporting/Reference Documentation

Solution Review Board input

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

9 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]

Page 10: SAP ABAP Assignment - Sales Order Interactive Report

Functional Design Form document.doc Version: 1.0

Input CommentsTechnical Details This document contains functional requirements and some technical

implementation details. These implementation details are subject to change in the technical design.

Estimate 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.

Modified: 4/7/2023 6:25 PM©2010 A2Z. All Rights Reserved.

10 Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT Training. [email protected]