TS Checklist
Transcript of TS Checklist
-
8/7/2019 TS Checklist
1/3
Technical Spec QA Check List
GSAP
Date Modified: 06.01.2011 Page 1 of 3
1/21/2011 Page 1 of 3 50002710.docx
Technical Specification QA Check list
TA Anup Kumar INAKWB
RIEFId. INDIA_R2.3CA_FSSR996_CR37293 - CENVATCredit RegisterFiling formST3 (293)
Subject Yes No N/A Comments
GeneralInformation YES
Development Class or Package specified
RevTrac number Provided
Transaction Code specified
Unit Test Plan is taken
Amendment history, version & Date updated
Data flow chart and Psuedocode given for complexlogic
Variable Initialization strategy to be implemented
Data Dictionary YESCustomTable structures mentioned inAppendix Hof the TS
Data element/ Domainproperties specified(Type/Length/Descriptions)
Transaction Code forTable Maintenanceprovided
Table type (Entries Transportable) specified
Technical attributes of custom table
Check tables provided
Buffering allowed ornot on the custom table
Comments
ReportsYes
SelectionScreen details provided
Validation logic provided forSelectionScreenFields
Output format with column headings and header infoprovided
AuthorizationStrategyTable entriesprovided
Performance issue considered/identified
Date, Decimal and Currency Format provided
Data mapping and Calculation logic for all the fields
providedException Handling, errormessages specified
Comments
-
8/7/2019 TS Checklist
2/3
Technical Spec QA Check List
GSAP
Date Modified: 06.01.2011 Page 2 of 3
1/21/2011 Page 2 of 3 50002710.docx
Form SapScripts / Smartforms Not Applicable
Driver Program/Formnamesprovided
Standard Texts/Text Module namesprovided
Coding Logic inForm or Program specified. As
much aspossible, coding logic should be used indriverprogram.
Custom style name provided
Smart form Global definitions provided
Logo/Image names provided
Date, Decimal and Currency Format provided
Language requirements considered
Structures if any tobe created and Interfaceparameters provided forSmart forms
Layout, Font and Window dimensionsprovided
Data mapping for all fields provided
Comments
Interfaces Not Applicable
Custom IDoc structure provided with details offields in each segment
Inbound/Outbound functionmodule names has
provided
Internal table structure for Inbound/Outbound fileuploads provided
ALE settings has beenprovided
Interfacing method hasprovided (session / calltransaction)
Interface strategy implemented
Logical file name provided
Physical file pathprovided (Application server)
Error handlingprovided
Data mapping and Translation rulesprovided
Comment
E
nhancem
entNo
tA
pplicable
User exit Strategy Used
Table entries for UE Strategyprovided
Enhancement Component / User exit name provided
BADI Implementation / Method details provided
When implementing single usebadi make sure allthe standard implementations are copied to thecustom BADI
No Commit statements inside any BADI/Field exit/user exit
-
8/7/2019 TS Checklist
3/3
Technical Spec QA Check List
GSAP
Date Modified: 06.01.2011 Page 3 of 3
1/21/2011 Page 3 of 3 50002710.docx
All database updates to custom tables happens inupdate task
Before using select statement look forbufferedfunctionmodule to read the data for standard SAPtables
While coding in routines and SD exits use own localwork area and in internal tables and update SAPinternal table and work area only when required
Createbuffered functionmodule for custom tables
Make sure that the exportingparameters are filledeven if you are not using this in your logic
Error Handling and errormessages provided
Comments
Only relevant sections needs to be filledandother left blank