Functional ALV

Swift SAP Implementation
<Client Logo>

Functional Requirement Specification - Report

1.) FRS_SD_DRR202 (1).doc Page: 1 of 11 23/08/2014

Functional Requirement Specification Report

Object # : DRR202
Object Description : Customer Returns Report


<Client Logo>


CONTENTS

1 Revision History ................................................................................................................ 3
2 About the Report Requester ........................................................................................... 3
3 About the Report ............................................................................................................. 3
4 Technical Specifications .................................................................................................. 4
5 Other Technical Considerations ..................................................................................... 7
6 Report Selection screen Criteria .................................................................................... 8
6.1 Desired screen design layout (selection possibilities): ........................................ 8
6.2 Validation for selection screen .............................................................................. 8
7 Z Table involved in report generation ........................................................................... 9
8 Report Layout Criteria ..................................................................................................... 9
8.1 Desired report layout .............................................................................................. 9
9 Processing Logic ............................................................................................................... 9
10 Required Download ........................................................................................................ 11
11 Performance Criteria ..................................................................................................... 11
12 Usage Frequency ............................................................................................................ 11
13 Security information ...................................................................................................... 11
14 Additional information .................................................................................................. 11
15 Test Data......................................................................................................................... 11


<Client Logo>


1 Revision History

Version
No
Date Change By Brief Description of change
1.0 15-Feb-07 Sachin
Yadav/Sathish
Rajendran
Document Creation

2 About the Report Requester

Requesters Name Dianna Ferguson, Jenniffer Request date 15-Feb-07
Department/Team/
Group/Cost Center
Sales R/3 release for
report development
ECC6.0
Report user if different Signature(s)
Functional consultant Technical
Consultant

E-mail Phone

3 About the Report
Priority or need for this report (check one) High Medium Low
If you answered High,
briefly explain why you set
this priority:

Complexity of this report (check one) High Medium Low
If you answered High,
briefly explain why you set
this priority:

Date report needed by Before
Unit
Testing

<Client Logo>


1 Report name: Enter a suggested name for the report you want.
Note that for custom reports, the assigned name will appear in the system.
CUSTOMER RETURNS REPORT

2 Short description: Enter a short description of the desired report (including the benefit of
the report). Note: For custom reports, the short description is included in the
documentation.
This report once developed will show the details of two types of returns as below.
1. Goods are received in Plant and return delivery is created
2. Goods are not received in Plant and credit memo request is created
Benefit It will be useful to monitor the returns and further processing such as credit for
returns.

3 Business decision: Reports enable business decisions. What decisions might be made after
using this report? Based on this decision, what R/3 System functionality might be directly
used?
This report will be used to view the return order details and will be useful in taking the
decision for giving credit to the customer.

4 Technical Specifications
1 Business data source(s): Enter the name of the application(s) or data area(s) of the
report. Examples: SD-shipping, FI-accounts payable, HR-payroll, and so on.
SD Sales Returns


<Client Logo>



2 Known tables or fields: Specify any known tables or fields in the desired report.
Recommendation: Consult with the report developer or a user who understands the
technical aspects of the application areas.
VBAK Sales Order Header, VBAP Sales Order Item
LIKP Delivery Header, LIPS Delivery Item
VBFA Document Flow
TVAK Sales Document Type
T001W Plant data

3
Similar reports in the R/3 System: List any standard R/3 reports you found that are
similar to the one you have requested. Discuss why the standard report does not fit your
needs. Hint: If you find a report that contains someif not allof the fields, enter its
name below.
Title of the Report Description of report; special
features; features that you do not
want to include
Program name
transaction/oth
er
No Standard Report available which
can list the Return Order and Credit
Memo Request with respective
reference invoice details.


<Client Logo>



4 Reporting tools evaluated: Based on your survey of the reporting tools, indicate:
Which reporting tools (for example, Report Painter, ABAP Query, etc.) have you
considered?
Which reporting tool (if any) do you prefer more than the others?
In your view, are there any tools that are not appropriate for this report?
Use the table on the following page and if necessary, the space below the table.
Reporting tool or
Data collector
Check if
considered?
Preferred tool for this
report
Reasons why
preferred
ABAP Query
LIS Standard Analyses
LIS Flexible Analyses
Report Painter
Report Writer
Drilldown
Business Info Warehouse

ABAP report with ALV Grid Display can best address the client requirement.

5 Other resources: Have you considered any external resources (for example, OSS, ASUG, SAPnet)
to find the report? Include any message numbers you received from these or other sources.
Not Applicable

6 Long description: Enter a detailed description of the report. Include the following information:
Business reason (or requirement) for the report
Layout and screen information (for example, weekly, monthly, or quarterly data; column and
row headings, and document data, etc.)
References to any legacy system reports considered from which this report can be found (with
attachments, listings, or screenshots, if possible)

<Client Logo>


Business Reason: Materials supplied by M/s Swift may be returned back by the customer sometimes
due to Damaged in transit etc and also to issue a credit memo for the pricing mismatch against the
material supplied etc.

5 Other Technical Considerations
1
Authorizations
Indicate below the level of authorization control you want to exercise:
Should restrictions be placed on who may use this report? Yes No
Should restrictions be placed on who may see the report output? Yes No
Should certain fields be hidden from certain users? Yes No
To get the report developed and approved is there a special
method or procedure that should be used?
Yes No
Other comments or instructions:

2
Upgrades
Are there potential consequences of upgrading this report to a
newer release of the R/3 System? If yes, use space below to
explain.
Yes No
Is the development of this report based on function modules
used in existing reports?
Yes No

3
Development Considerations and Notes
Are there special internal tables that need to be accessed? Yes No
Are there any other key people in the company who could offer
additional information or perspectives on this report?
Yes No

<Client Logo>


Would other divisions in the company need such a report? Yes No
Have other divisions in the company already created the same
(or similar) report?
Yes No

6 Report Selection screen Criteria

Sr.
No
Field Text on Selection
Screen Field Names Table Name Default Value
1 Plant WERKS T001W NA
2 Date AUDAT VBAK NA
3 Order Type AUART VBAK NA
4 Customer KUNNR KNA1 NA
6.1 Desired screen design layout (selection possibilities):
Plant
Customer
Order Type
Date

6.2 Validation for selection screen
Plant (Selection Range) Should exist in T001W (Mandatory field)
Customer (Selection Range) Should exist in KNA1
Order Type (Selection Range) - Check whether Order Type exists in table TVAK and
is of Document Category either H (Return Order) or
K (Credit Memo Request). This can be checked
with table TVAK with field VBTYP.

<Client Logo>


7 Z Table involved in report generation
No Z table is involved in this report.
8 Report Layout Criteria
Sr.
No Field Text on Report layout Field Names Table Name
Total/ Sub Total
field
1 SDC Plant WERKS VBAP NA
2 Customer KUNNR VBAK NA
3 Customer Name NAME1 KNA1 NA
4 Original Invoice VBELV VBFA NA
5 Return Document VBELN VBAK NA
6 Document Type AUART VBAK NA
7 Delivery Number VBELN LIKP NA
8 Material Number MATNR VBAP NA
9 Material Description ARKTX VBAP NA
10 Cases
LFIMG or
KWMENG
LIPS or
VBAP Total
11 Weight /CWM/LFIMG LIPS Total
12 Value NETWR VBAP Total
8.1 Desired report layout
Customer Return Report
SDC
Plant
Customer Customer
Name
Original
Invoice
Return
Document
Document
Type
Delivery
Number
Material Description Cases Weight Value
Total Xxxxx Xxxxx Xxxx

The report should be displayed in ALV Grid format and various buttons such as Total,
Subtotal and Sort should be provided on Report Toolbar.

9 Processing Logic
As specified in the selection criteria select the data from table VBAK, VBAP and KNA1 tables.
Plant is a mandatory field in the selection screen.
Data to be selected
VBAP-WERKS, VBAK-VBELN, VBAK-AUART, VBAK-KUNNR, KNA1-NAME1, VBAP-POSNR,
VBAP-MATNR, VBAP-ARKTX, VBAP-KWMENG, VBAP-NETWR
The selection from the tables should be restricted to
VBAK-AUART = Selected Order Type Range

<Client Logo>


VBAK-AUDAT = Selected Date Range
VBAK-KUNNR = Selected Customer Range
VBAP-WERKS = Selected Plant Range and
KNA1-KUNNR = VBAK-KUNNR.

For each line selected from VBAP Select the Reference Invoice Number (VBFA-VBELV) from table VBFA.
The where clause for the selection from VBFA is
VBFA-VBELN = VBAP-VBELN and
VBFA-POSNN = VBAP-POSNN
Add this Invoice number for each line to the internal table of selected VBAP data.

Now select data from LIKP and LIPS as below.
Data to be selected
LIKP-VEBLN, LIPS-LFIMG, LIPS-/CWM/LFIMG
The selection clause for the above selection is
LIPS-VGBEL = VBAP-VBELN and
LIPS-VGPOS = VBAP-POSNR and
Add this data to corresponding lines in the internal table of VBAP.

There are two possibilities depending on the document type is either of document category K or H.
The quantity i.e. Cases, weight and Value should be printed as given below.
1. Documents Category H (Return Order).
In this case there is a subsequent delivery for each order item therefore the report should show the
data from delivery. The Value always comes from VBAP.
Cases = LIPS-LFIMG
Weight = LIPS-/CWM/LFIMG
Value = VBAP-NETWR
2. Document Category = K (Credit Memo Request)
In this case there will not be any subsequent delivery. Therefore data should be shown from VBAP.
Cases = VBAP-KWMENG
Weight = Blank
Value = VBAP-NETWR

<Client Logo>


10 Required Download
Download option as available in the ALV display can be provided.
11 Performance Criteria
No specific performance Criteria
12 Usage Frequency
Least Weekly Once
Maximum Daily Once
13 Security information
Authorization should be given as decided by the client in the Roles defined.
14 Additional information
Not Applicable.
15 Test Data
Test Data will be provided once the client is available for testing.

* End of the Specification *

Functional ALV

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Functional ALV

Caricato da

Copyright:

Formati disponibili

Swift SAP Implementation

Potrebbero piacerti anche