Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
1. Justification
Background Information
1.1 Requirement Summary and Overview of Conceptual Design
Aecon has been Some Fleet groups use serialized GBRA Materials numbers to be able to keep track inspections. SAP
needs to allow them to select the specific plant that will require a serial number when a shipping document needs to be
created. The GBRA logic should have always checked plant and serialized field in order to request the serial number
Description of Service:
Change the code logic so the system would always check specific plant and serialized field in order to request the
serial number.
1.2 Justification
The purpose of this change is to build in a validation checking the specific plant and if the material is serialized the
shipping document would require the information. Once the shipping document gets created a serialized number
will be required and that will help the business tracking the GBRA materials.
1.3 Sample Files
NA
1.4 Solution Options Considered
1. Currently, the program will check the plant or material for serialization, if either one is serialized it will request for
serial no.
1|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
2. Need to check both the plant and material serialization and it should be serialized both from plant and material. If
not it will not request for any serial no. So we need to do a programming change in different places in different
program.
3. We shall add additional condition in J3GH(Shipping document) create/change transaction. Currently we are checking
two conditions –
1. the material is serialized or not and
2. then check whether particular plant is serialized or not.
We need to introduce additional condition in it, when plant is not serialized - check
whether ALL is marked against serialized plant. Value "ALL" will be available in the characteristics value.
(Characteristics values are available in We are validating against it). Please note we need to do this validation while
saving and while showing the popup to capture serial number.
To do this it will be better to get a CR, as it requires detail designing, rigorous, testing.
4. This is my view is keep this object as it is and mark plant/s for serialization based on the business requirement instead
of going for option “ ALL”. This scenario currently working as per business expectation.
5. Additional logic – if plant and material both are marked for serialization then SAP has to ask for serial number during
shipping doc creation else system should allow to create shipping doc. More than that not done any changes.
1.5 Recommendation
NA
1.6 Key Decisions
NA
2. Functional Specification – High Level Requirements
2.1 Functionality
Item #1: That catalog is showing CHAR value as SERILAIZED.
2|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
- Item #2: Check Report /n/AECONGL/SERTL - Small Tools Tracking table
3|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
Item #3: SAP has created shipping doc for sender E156 with Srl# .
We shall add additional condition in J3GH(Shipping document) create/change transaction. Currently we are checking
two conditions –
1. the material is serialized or not and
2. then check whether particular plant is serialized or not.
We need to introduce additional condition in it, when plant is not serialized - check
whether ALL is marked against serialized plant. Value "ALL" will be available in the characteristics value.
(Characteristics values are available in We are validating against it). Please note we need to do this validation while
saving and while showing the popup to capture serial number.
Item #4: Need to check both the plant and material serialization and it should be serialized both from plant and
material. If not it will not request for any serial no. So we need to do a programming change in different places in
different program.
4|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
2.2 Assumptions
2.3 Constraints
N/A
2.4 Performance Criteria
N/A
2.5 Applications Affected
<Identify the Applications impacted whether it is SAP or Non-SAP Systems.>
SAP System Impact/ Change Description
NA
Non- SAP System Impact/ Change Description
3. Functional Specification – Detailed Specifications
5|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
3.1 Specification for Reports & Forms
Note: In case of reports, decision on BI vs SAP ERP should be made prior to writing DS for specific report with
input from reporting Work stream
3.1.1 Specification ( SAP – ECC, SRM, CRM ) see section 3.1.2 for specification of BI (BW) Reports
3.1.1.1 General
SAP Menu Path /n/AECONGL/SERTL
Selection Criteria N/A
Security N/A
File Location and Name NA
Logical File Name NA
Drill Down Requirements NA
Similar Report/Form N/A
Exceptions/Filters N/A
Output Type N/A
Mode of Execution NA
Special Printing/Media Requirements N/A
Sort Criteria N/A
Logo N/A
Bar Codes N/A
6|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
Distribution/Volume N/A
Work Assignment N/A
Frequency Daily
Dependencies N/A
Existing Development Object System : SAP Object Name:
3.1.1.2 Output Layout
3.1.1.3 Required Data
3.1.1.3.1 Input Data
<Tables accessed to provide data for report> Attached is the XL template for the Fields and mapping in
Section 3.2.2
From System Name Structure or Table ID Structure or Table Name
SAP <Insert Structure or <Insert Structure or Table Name>
Table ID>
Field ID Field Format Table Select Mandatory Default Value
Name Value/ Option or /Optional
Checkbox Parameter
/Radio
Button
7|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
3.1.1.3.2 Output Data
<Mention the fields to be displayed in the Output List>
To System Name Structure or Table Structure or Table Location Expected Volume
Name
SAP
Field Name Field Description Format Values
3.1.2 Specification for BI (BW) Reports
Report Name:
Business Purpose/Requirement: <Mention ‘Refer Section 1.1 and 1.2’>
Where does the data come from? SAP Non- SAP SAP + Non SAP
If non-SAP, what is the source system?
Critical High Medium Low
Priority or importance of report: 1-Critical (business can't run w/o) 2-High (deadline will be missed)
3-Medium (work can continue) 4-Low (wait until v2)
Table KPI Metric Charts & Graphs
Report Category (check all that apply):
Other (Short Desc):
Report Type: Detail (Transaction Level) Summary (Aggregated)
Dashboard / Scorecard Ad-hoc
8|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
Refresh Schedule: How current does Real-Time Near Real-Time No more than 1 day old
the data need to be? If Real Time, explain why
1-Real-Time (as it occurs in the system) 2-Near Real Time (< 2 hours old)
Frequency: How often do you run the On-Demand Hourly Daily Weekly Monthly
report? Other (Please Specify):
Viewing Method: In what format will Desktop of the Future Crystal (Fixed Format, Read Only)
the report be viewed? Webi (Ad-Hoc, Interactive) Dashboard/Scorecard HTML
PDF Word / Excel / PowerPoint Mobile
Standard Report: Is there an out of the
box report from BW? If Yes, what is
the BW report name?
SAP Process /Sub Process:
Example
Assumptions: The report should
1. Data is extracted from the ETM module within SAP
incorporate the following
assumptions
Logic/Population of Data: Describe the ExampleData is extracted from ETM module within SAP.
population of the data
Column or Parameter Conditions Prompt (Yes/No) Comments
Name
Conditions for the Report: Example
Report Table Fields Required: Describe the data that is needed for the report. List each field needed. Example
Column Name Report (if more than one In Sections Sub Totals Comments
query or drilldown) (Yes/No) (Yes/No)
9|Page 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
10 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
/AECONGL/SERTL - Small Tool Tracking Table Report.
Additional Details: If this report exists
please attach or include a screen-
shot.
Example
Calculations and Definitions: Describe
the calculated data that is needed
for the report. List each field
needed and any formulas
Example
Field Definitions: Describe the terms
used and their definitions so
common terminology is clearly
understood by development
Example
How is data to be sorted: Describe any
sort sequences, any breaks, etc.
Example
Filters: Describe any filters needed on
the population set
Graph & Chart Requirements: Describe graph requirements Example
Graph Type Example : Bar Chart
Title ( optional) Example: Aging Report…
S.No Axis Column Name Comments
11 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
2 Y # RMA lines
Example
Data Refresh Schedule Details: Provide
schedule and comments
w/timings
Snapshot/Trend Requirements:
How is Report to be Distributed?
Security Requirements: Example
Testing Requirements: Describe the testing requirements <Use cases here>
Role Action or Path Expected Results Expected Cycle
Scenario Step Test Step
Time
12 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
3.2 Specification for Conversions/ Interfaces /Enhancements
3.2.1 General
Conversion / Interfaces / Enhancement
Enhancement:
Inbound/Outbound
Source System SAP
Target System SAP
Trigger NA
Frequency Daily
Volume
Archiving Requirements
Method of Execution Manual
Enhancement/User Exit:
User Exit Name
Processing Logic
Error Handling/Reprocessing Method
Post Execution Notification Details Log with status of completion (25 records selected)
13 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
Transaction Codes NA
Menu Path
Required Screens
Existing Development Object System : SAP Object Name:
3.2.2 Mapping
Interfaces/Enhancements
3.3 Specification for Workflows
3.3.1 General
SAP Transaction(s) that Trigger N/A
Workflows
Batch Program(s) that Trigger N/A
Workflows
Security N/A
Custom Code N/A
Programmer Notes N/A
3.3.2 Flow Diagram
N/A
14 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
3.4 Specification for Custom Application Development
3.4.1 General
3.5 Specification for Mobile Development
3.5.1 General
3.6 Specification for User Interface Development
3.6.1 General
15 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
4. Additional Information
4.1 Test Plan
4.1.1 Related Business Scenario and Business Transactions
4.1.2 Test Data
For Data Conversions, ensure to document any additional Reconciliation Requirements needed
4.2 Backup/ Recovery
4.3 Security Profile & Authorization
NA
4.4 Related/ Referenced Documents
Document Name Version Brief Description
4.5 Cross-Functional Impact
Task Force Team Impact Individual Notified/Date
4.6 Attachments
16 | P a g e 5/21/2018
Development Specification
Work Stream: ETM Sub Module: Report Tables
Title: Prod Test of Serialized GBRA Program NA
Tracking Table Name:
Document Name Version Brief Description
5. Document Control
5.1 Justification Approvals
Name Role Signature Date
JOHN
08/4/2017
STROBEL
5.2 Requirements Approvals
Name Role Signature Date
JOHN STROBEL 08/4/2017
5.3 Specification Approvals
Name Role Signature Date
5.4 Change Log
Version Date Change Description/ Reason Author
1.0 08/03/2018 Initial Document Satya Reddy.M.V
17 | P a g e 5/21/2018
