Functional specification

Functional specification
Creation of PO Form
Materials & Management
Creation of New Layout of PO Form
Modification:
Replace previous version : 0.1
Document creation
Version: 0.1
Date : / Status: / Diffusion:
Created by: Muhammad Irfan
Date: / Reviewed by:
Entity:
Date: / Validated by:
Entity:
Date:
Summary:
PO / Materials Report
Comments:

Revision History

Version / Modification Date / Comments
V 0.1 / Document creation
Creation of New layout of PO Form
V 0.2 / Document Reviewed
V.0.4 / Document Reviewed

Contents.

1: General Information

2: Functional requirements

2.1 Required Layout of PO

2.2 Business rules

3: Scope

4: Logics behind the Required Report.

5: Test Plan for Material Report.

1.  General Information

Area (SAP System components): / Date:
Short description: / Maintain Customer Hierarchy Field in Material Listing
Requested by: / Tel no:
Author: / Tel no:
Program Transaction code:
Task ID/Demand Number:
Project Name:
Priority: / High/mandatory Medium/recommended Low/optional
Complexity: / High Medium Low
Volume of data: / Date available from:
Mode: / Online Background
Frequency: / Daily Weekly Monthly Biweekly
Others (Specify) :
Technical information:
1.  Type of Enhancement
2.Module /Submodule Information
3.Data Object (Purchase order/sales order etc.)
4. Dependancy on any object / UserExit BADI Requirement routine
Custom transaction Business transaction event
Substitution & ValidationOthers
Sap Std program modification
Module submodule
General information:
1.  Results if no conversions are created: / Legal requirements not fulfilled
Lack of essential business information
Lack of functions compared to legacy system
Others (Specify):
Approx. duration of development work (in man-days):
Is there an alternative in the standard system? / Yes No
Description of alternative:
Reasons why alternative is not acceptable: / Performance problems Complexity
Others (Specify) :
Reference Document / Any Dev or doc which is of use

2. Functional Requirements

The below is a PO FORM Prinitout which have to modify and bring the layout as below.

To build a required form we need to build field logic for each field to be printed on the PO Form. In the form, names are given to every field for the ease reference.

In the form every field has information in different tables, so to get required information for specific field need to build relationship / links among those table which are directly or indirectly link to that specific field.

For example, Supplier Address field, two tables (LFA1 & ADRC) are associated with this field and to get a required information need to build a links between those tables.

2.1 Required Layout of PO Form

2.2  Business rules

Business Rules / Description
BR-01: / To build up above layout of PO Form. To get the required layout need build field logics for every field.

3: Scope

To get the required Layout of PO, need to build a links between tables those keep the needed information.

4: Logics behind the Required Report.

Here each field / task is assigned a name like W1, W2…

Tasks / Fields / Tables / Logic
W1 / Attachment of Logo (Career Dragon)
W2: Company Code Address / BURKS, ADRNR, ADDRNUMBER / EKKO, T001 AND ADRC / Pass EKKO – BURKS into T001 table and get ADRNR and pass T001-ADRNR to table ADRC and get ADDRNUBER.
In T001 table there is ADRNR field. This ADRNR field corresponds to ADRC-ADDRNUMBER. This is
Applicable to T001.
ie T001-ADRNR = ADRC-ADDRNUMBER. From ADRC table all information / fields can be retrieved. E.g Name, City, Postal code
W3: Page No / INSERT PAGE NUMBER
W4: Date / BEDAT / EKKO / Get the BEDAT value from table EKPO
W5: PO No / EBELN / EKKO / Get the EBELN value from table EKPO
W6: SUPPLIER ADDRESS / ADRNR, ADDRNUMBER / LFA1 & ADRC / In LFA1 table there is ADRNR field. This ADRNR field corresponds to ADRC-ADDRNUMBER.
ie LFA1-ADRNR = ADRC-ADDRNUMBER . From ADRC table all information can be retrieved.
W7: SUPPLIER ADDRESS / ADRNR, ADDRNUMBER / LFA1 & ADRC / In LFA1 table there is ADRNR field. This ADRNR field corresponds to ADRC-ADDRNUMBER.
ie LFA1-ADRNR = ADRC-ADDRNUMBER . From ADRC table all information can be retrieved.
W8: Condition / KSCHL / KONP / Get the KSCHL value from table KONP
W8: Payment Term / ZTERM / T052 / Get the ZTERM value from table T052
W9: DESCRIPTION: / TXZ01 / EKPO / Get the TXZ01 value from table EKPO
W10: QUANTITY / MENGE / EKPO / Get the MENGE value from table EKPO
W11: CODE ARTICLE / EMATN / EKPO / Get the EMATN value from table EKPO
W12: DATE OF DELIVERY: / EINDT / EKET / Get the EINDT value from table EKET
W13: PRICE PER QTY / NET PRICE: NETPR
UNIT PRICE: PEINH / EKPO / Get the NETPR / PEINH value from table EKPO
W14: TOTAL PRICE / SET FORMULA TO GET TOTAL PRICE: NO OF UNIT X TOTAL QTY
W15: SPECIAL CONDITIONS / KSCHC / KONP
STXH - SAPScript Text Header
STXL - SAPScript Text Lines / HELP ME ON THIS

5: Test Plan for Material Report.

Scenario / Expected Result / Comments
1 / Generate a New Layout of PO form, which have the information / output stated in above form. / To get a required PO layout, need to build a links between two tables to get required information. In this case lot of tables are involved and need to link them to get the desired PO layout.

Page 1