SAP

Technical specification

ERP-14207

371215404.doc Page 1 of 8
Author
Name Department Function/role Signature Date
Aymen SAP Technical ABAP Aymen 09/12/2017

Review
Name Department Function/role Signature Date
Sanyasi SAP Technical ABAP

Approval
Name Dept. Function/role Signature Date

Modification Log
Version Responsible Sections affected Date

Business Process Model Details

Process Description

Related documents
HTTPS://CONFLUENCE.EFI.COM/DISPLAY/IST/ERP-
14207+INCLUDE+FUTURE+DUE+BUCKETS+IN+THE+OUTPUT+OF++ZFIR_CUST_AGING+REPORT

371215404.doc Page 2 of 8
Table of Contents
1 REQUEST REFERENCE...........................................................................................4
2 SOLUTION SHORT DESCRIPTION.........................................................................4
3 REFERENCES...........................................................................................................4
3.1 REFERENCES TO EXISTING PRODUCTS / FUNCTIONS / OTHER..........................................................4
3.2 SIMILAR FUNCTIONS / OBJECTS IN R/3........................................................................................... 4
3.3 OTHER / COMMENTS..................................................................................................................... 4
4 DETAILED SPECIFICATION.....................................................................................5
4.1 KNOWN / PREFERRED TOOLS......................................................................................................... 5
4.2 NEW OBJECTS.............................................................................................................................. 5
4.3 PERFORMANCE REQUIREMENTS FOR NEW OBJECTS........................................................................5
4.4 KNOWN OBJECTS FOR USE............................................................................................................ 5
4.5 INPUTS / OUTPUTS....................................................................................................................... 6
4.6 MESSAGES................................................................................................................................... 6
4.7 INTERFACES................................................................................................................................. 6
4.8 ALGORITHM / LOGIC / RELATIONSHIPS........................................................................................... 7
4.9 SCREEN SEQUENCES.................................................................................................................... 7
4.10 DRILLDOWN / INTERACTIVE............................................................................................................ 7
4.11 OTHER......................................................................................................................................... 7
4.12 UNIT TEST DOCUMENT
...8
4.13 APPENDICES
8

371215404.doc Page 3 of 8
1 Request reference
This section offers an overview about the request and consists of:

o Request name - a name given for clarity and consistency purposes - basically each request
should have a different name;
o Request short description - a short description given to request - e.g.: a report that must display
an account balance in a certain format;

Request name ERP-14207

Request Changes for Customer Aging Report
Request short description
ZFIR_CUST_AGING

2 Solution short description

Include future buckets on all aging reports. Incorporate logic to distribute data based on
future buckets.

3 References
This section intends to give an idea about the desired results and/or working of the request by referencing
other R/3 or non-R/3 products, functions, objects, etc., and is subdivided into 3 subsections:

References to existing products / functions / other (non-R/3);

o
Name - name of product, function, etc.;
Description - description of product, function, etc.;
Location / Comment - location and/or comments about product, function, etc.;
o Similar functions / objects in R/3;
Type - type of a similar function, object, etc. within R/3 - e.g. program, report, transaction,
etc.;
Name - name of the similar function, object, etc. within R/3;
Description - description of the similar function, object, etc. within R/3;
o Other / Comments - other information and/or comments;
3.1 References to existing products / functions / other

Name Description Location / comment

N/A N/A N/A

3.2 Similar functions / objects in R/3

Type Name Description

Request Changes for Customer Aging Report
Report ZFDOPR00_USD
ZFIR_CUST_AGING

3.3 Other / Comments

Other / Comments N/A

371215404.doc Page 4 of 8
4 Detailed Specification
This section provides a detailed technical description of the chosen solution. It is subdivided into 12
subsections:

4.1 Known / preferred tools

In all this template , the term: ID it will be used to uniquely identify an entity - used exclusively only within
this template

Known / preferred tools - there might exist various tools, but is not necessary to use all of them:
o Tool - name of tool should be used for development - e.g. ABAP QUERY;
o Short description - description of indicated tool;
o Reason for use - the reason for why consultant has chosen that tool;

Tool Short description Reason for use

4.2 New objects

New objects - a list of new mandatory objects should be created - the developer still has the final
choice:
o Type - R/3 type of the new object - e.g. PROG for programs, TABL for tables, etc.;
o Name - the proposed name for the new object;
o Short description - a proposed short description of the new object;
o Use - a detailed description on how the new object should be used;

ID Type Name Short description Use

N/A N/A N/A N/A N/A

4.3 Performance requirements for new objects

Performance requirements for new objects - if some performance criteria applies for the new object
then the following information must be provided:
o Level - level of performance - e.g. minimum of running time;
o Criteria - a criteria used to evaluate the performance;
o Comments - comments on performances;

ID Level Criteria Comments

N/A N/A N/A N/A

4.4 Known objects for use

Known objects for use - an existing object which can/could/must/should be used:
o Type - R/3 type of the known object - e.g. PROG for programs, TABL for tables, etc.;
o Name - the name of the known object - is mandatory;
o Short description - the short description of the known object;
o Use - a detailed description on how to use the known object proposed herein;

ID Type Name Short description Use

ZFDOPR00_U Request Changes for Customer Aging
ERP-14207 Report
SD Report ZFIR_CUST_AGING

4.5 Inputs / Outputs

Inputs / Outputs - defines the inputs and/or outputs if these exist - e.g. selection-screen parameters
for a report, or columns/rows for an output list:

371215404.doc Page 5 of 8
 o Type - type of input/output - e.g. SELECT-OPTION;
o Short description - a short description of the input/output;
o R/3 field mapping - a mapping to a R/3 field, where applies - e.g. T001-BUKRS for a
selection-screen parameter for company codes;
o Use - indications/other about use of the input; could also contain a formula if the i/o is
calculated/lookedup/etc

ID Type Short description R/3 field mapping Use

N/A N/A N/A N/A N/A

4.6 Messages
Messages - defines a list of messages should be used:
o Type - type of message - e.g. "E" for error or "W" for warning;
o Text - the text that message should display in certain circumstances;
o Use - how to use this message;

ID Type Text Use

N/A N/A N/A N/A

4.7 Interfaces
o Interfaces - defines a list of interfaces for objects that need an interface:
Object type - type of the new object for which it is defined the interface - e.g. FUNC for a
function module;
Object ID/name - the ID of the new object for which it is defined the interface;
Type - type of interface member - see table below for a list of possible types;

Type Description

I Import parameter

E Export parameter

C Changing parameter

T Table parameter

X Exception

M Method

P Parameter
o Short description - a short description of the interface member;
o R/3 field mapping - mapping to a R/3 field;
o Use - how to use the interface member;

371215404.doc Page 6 of 8
 Object type Object ID / name
Type Short description R/3 field mapping Use
I N/A N/A N/A
E N/A N/A N/A
C N/A N/A N/A
T N/A N/A N/A
X N/A N/A N/A
M N/A N/A N/A
P N/A N/A N/A

4.8 Algorithm / Logic / Relationships

Algorithm / Logic / Relationship - defines a list of algorithms, logic, relationships which
can/could/must/should be used:
o Description - a detailed description about algorithms, logic, relationships, including if it is
possible diagrams, charts, graphics;

At present there are no future buckets.

After adding future buckets.

4.9 Screen sequences

Screen sequences - defines a list of screen sequences - how screens must appear in different
situations:
o Description - a detailed description about screen sequences, including if it is possible
diagrams, charts, graphics;

ID Description
N/A N/A

4.10 Drilldown / Interactive

Drilldown / Interactive - defines a list of drilldown / interactive functionalities:
o Description - a detailed description about drilldown/interactive, including if it is
possible diagrams, charts, graphics;

ID Description
N/A N/A

4.11 Other
Other - defines a list of other information:
o Description - a detailed description about the other information, including if it is
possible diagrams, charts, graphics;

ID Description
N/A N/A

371215404.doc Page 7 of 8
4.12 Unit Test Document
o Description: steps executed in unit test and with desired test results.

UAT for
ERP-14207.docx
4.13 Appendices
Appendices - a list of appendices - where exist; an appendix could contain for example a detailed
desired layout of an output list, e.g. a Balance Sheet report;
o filename - the filename where the appendix is located;
o Description - a description of the appendix;

Filename Description

371215404.doc Page 8 of 8