Scribd
Upload
2K views5 pages

Functional Specifications For Purchase Order: 1. Business Requirements

The document outlines functional specifications for generating a purchase order report within a given date range or for a specific purchase order number. It specifies: 1) The user enters a plant and purchase order number or date range. The system checks that the plant and purchase order exist before generating the report. 2) The report displays purchase order details including material, vendor, address, order date, received date, quantity, and net price. 3) It includes test scenarios and expected output for a sample report, as well as assumptions about authorization, partners, and selection criteria fields to generate the report.

Uploaded by

Tom Marks
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2K views5 pages

Functional Specifications For Purchase Order: 1. Business Requirements

The document outlines functional specifications for generating a purchase order report within a given date range or for a specific purchase order number. It specifies: 1) The user enters a plant and purchase order number or date range. The system checks that the plant and purchase order exist before generating the report. 2) The report displays purchase order details including material, vendor, address, order date, received date, quantity, and net price. 3) It includes test scenarios and expected output for a sample report, as well as assumptions about authorization, partners, and selection criteria fields to generate the report.

Uploaded by

Tom Marks
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

FUNCTIONAL SPECIFICATIONS FOR PURCHASE ORDER

1. Business Requirements
Description: A summarized report of Purchase orders within a given Period of time or for a particular Purchase Order (PO) and for a specific plant, for the analysis purpose. A user defined Transaction code (ZPO1) is required to generate the expected report. When the user enters the T. code, a screen (initial screen) with selection criteria needs to be opened, and after entering the relevant data and when he clicks on Execute or F8, report should be displayed.

2. Functional Specification. 2.1 Functional Design


1. Check the entered data (Plant Field) with WERKS in MARC table. If No-- Show an information message that Particular plant is not available. If YesGet the List of Purchase Order Numbers (EBELN) from Table EKKO in the drop down list in the second field. Display an error message Entered Purchase Order number does not exist for this plant. OR If YesIf Purchase Order number is unknown, the user must have the option to enter range of dates during which the Purchase order generated. (Field Name-AEDAT from Table EKKO)

2. Once the user enters the date interval and clicked on Execute or F8, New screen with list of Purchase Orders (EKKO-EBELN) within the range of dates should be displayed. 3. By clicking on the Purchase Order from the list it should display the report as below.

2.2 Test Scenario


Here some inputs are furnished by using these inputs you can check the report. Inputs:Plant: 0001 PO Number: 4500000031 Or Date Intervals: 01-11-12 to 30-11-12

Expected Output:-

Purchase Order Number: 4500000031 Sl. No Material Vendor Vendor Number/Name Name/Number Address 100-400 DG-1000 1234 0000003021 0000001234 0000001024 Orderd Date Material Received Date 27-11-12 25-11-12 Ordered Qty 200KG 100PC Net Price

1 2 3

Hyderabad 20-11-12 Bangalore Delhi 20-11-12 01-11-12

40,000/-rs 1,00,000/-rs

30-11-12 236L 154356/-rs Total Net Price: 294356

3. Authorization
Authorized User: - Purchase Department Head.

3.1 Assumptions
You can get one Plant data at a time. You have to enter the past and present dates only.

3.1.1. Custom Formula


Required Total Net Price (sum of net price values of all the records) must be displayed at the bottom of Net Price (Column number 8).

3.1.2 Partner Logical System


The Purchase Order report should be able to send to a printer for the hard copy.

4. Selection Criteria
INITIAL SCREEN FOR PURCHASE ORDER REPORT

PO Number:

OR

4.1 Form Fields Column 1: Serial no. Column 2: Material number/ name Table: EKPO Field: MATNR Column 3: Vendor number / name Table: LFA1 Field: LIFNR Column 4: Vendor Address Table: LFA1 Field: ADRNR Table: ADDR1_DATA Fields: STREET (street/house no) city2 (City or district supplement) Post_code1/city1 (postal code as part of the address/city name as part of the address) Country (country key) Region (region) Po_box (po box)

post_code2 (Postal code) tel_number (telephone number) Column 5: Ordered date Table: EKKO Field: AEDAT Column 5: Material received date Table: EKBE Field: BLDAT Column 6: Ordered quantity Table: EKPO Field: MENGE Column 7: Net price Table: EKPO Field: NETPR

You might also like