You are on page 1of 5

FUNCTIONAL SPECIFICATION

Section I: Justification
Area (R/3
Module):

PT2329
SD

Date
(dd/mm/yyyy):

Requested by:
Title:

02.06.2016

Extension:

Changes in ZSUMMARY

Brief description:
Program type:

Conversion

Batch Interface

Online Interface

Form

Enhancement

Extension

Modification
Priority:

High/mandatory

Unknown

Report
Online program

Others

Medium/recommended

Low/optional

Only for Conversion and Interfaces:


Quality of legacy data:

Good

Complexity of legacy data:


3.

Complexity of a manual input:

4.

Number of SAP Screens:

Average

Poor

Simple
complex

Average

Complex

Simple

Average

Complex

Extra-

screens
Only for Interfaces:
Type of interface:

Real-Time

Pseudo-real time

Batch

Direction of interface:

Inbound

Outbound

Both

Frequence:

Daily

Weekly

Monthly

Biweekly

Other:

Only for Reports:


1. The report will be created via:

Report Painter
Query

2. Requested characteristics:

Report Writer

ABAP Program

Info System

Drill-down

Pushbuttons

Entry files

Others:

ABAP

Sort

Generic question:
1. Impact of not creating the program:

Legal requirements will not be fulfilled


Lack of information required for the business
Lose functionality compared to the old system
Others: _________________________

Development labor estimate:

1 day

Is there any alternative in the standard system:

Yes

No

Describe the alternative found:


Reason why this alternative was not acceptable:

Performance problems

Complexity

Others:

Proposed Solution
Program-ZSD_SUMMARY_REPORT
T-code- ZSUMMARY,
Currently system show the sales summary for document category C for, i.e. orders. Business wants to include
Intercompany sales in the same report so as to analyse the difference in PO quantity and the quantity finaly
delivered and invoiced.
Queries-How does he convert amt to AED.?
This logic would work to display IC documents only when the Check box Include IC billing is ticked in the input
screen.
For this, few more input fields to be added in the input screenExisting Document date input field to serve as input for IC PO date (EKKO-BEDAT), and Vendor (EKKO-LIFNR)
mandatory field if Include IC billing is selected. Vendor field to stay greyed out if Include IC billing is
unchecked.
In the output, following new fields to be inserted- IC PO no.(EKPO-EBELN), ICPO Date (EKKO-BEDAT), IC PO
qty (EKPO-MENGE), IC PO Amt (EKPO-NETWR)
1. Pass the Document date from input field to EKKO-BEDAT and vendor from the input field to EKKOLIFNR and fetch EKPO-EBELN.
2. Pass all EKKO-EBELN fetched from step 1 to EKPO-EBELN to fetch EKPO-BUKRS, EKPO-EBELP,
EKPO-MATNR, EKPO-MENGE, EKPO-MEINS, EKPO-NETPR, EKPO-NETWR, where EKPO-LOEKZ
is not equal to X
3. ICPO plant ((EKBO-BUKRS) would be shown in Customer column prefixed by P.
4. Customer name column to include (NAME1) by passing the customer from step1 to customer table.
5. Delivery column to also include delivery qty made against the IC PO. These can be fetched by passing
EKPO-EBELN, EKPO-EBELP and EKPO-MATNR to LIPS-VGBEL, LIPS-VGPOS and EKBE-MATNR
respectively and fetch Cumulative qty LIPS-KCMENG (del qty column) , LIPS MEINS, LIPS-ERDAT
(del date column) update corresponding to the line items fetched in step 2 and (LIPS-KCMENG*NETPR)
to be inserted in (del amt column)
6. Here onwards logic for Invoiced qty and Invoiced Amt to remain same as that exists already for other
deliveries.

7.

8.

For columns where Amt. in LC are required, the corresponding amt values need to be multipled with the
exchange rate from the transaction. For PFI/Order/Delivery Amt in LC, pass VBELN and fetch (exch rate)
VBKD-KURSK. Multiply/divide this value with the value in the amount field based on the +/- values of
exchange rate. For Invoice, pass VBELN and fetch VBRK-KURRF. Multiply/divide this value with the
value in the amount field based on the +/- values of exchange rate. For ICPO Amt in LC, exchange rate to
be fetched from the corresponding billing document VBRK-KURRF. If billing not complete value to
remain blank in this column.
Values in remarks column to be fetched from sales order item text ID. Text ID to be shared soon.

Section II: Detailed Functional Description


Standard SAP Objects Involved ( Tables, Transactions , etc.)
Transaction Code : ZSUMMARY
Output
RevisedZSUMMARY_PT2329.xls

Design of desired report / Layout:

Functional team member signature : Param Sharma Date: 21/05/2015


Approved By : ______ ___________
Date: / /

Section III: Unit Test


Test date:

Program name:
Developer name:

Aditya Sharma

/ /

Extension:

Responsible functional team member for testing:


1.

File(s) used for test (optional):

2.

Does the program comply with the functional specification ?


Yes
No
Note: If the program is OK just sign the form. If necessary include some comments in the appropriate section.

3.

If the answer to question 2 is "No" please describe the problems that were found in the program.

Responsible developer:
4. Describe the solution given to the errors.
Minor Errors- resolved there and then
5.

New delivery date: / /

Comments after new revision: (if the program contained errors previously):
Date: //

General comments:

Names and Signatures:


_______________________________________________________________________________________
Functional Consultant Param Sharma
______________________________________________________________________________________
Developer