Checklist Functional Enhancements

Title Sheet

Title of the accelerator

PurposeIn this section indicated the prupose of the accelerator..

Project Identification
I025234: The project identififcation table is optional. It is recommended that this be inculded should it be helpful for the development of the final deliverable.

Project NameProject NumberProject Type

Customer NameCustomer NumberProject Start.Finish

Project SponsorProgram ManagerProject Manager (Customer)

Project Manager Service Partner(s)Project Manager (Service Partner)

WorkflowOpenCloseN/AChecklist for completeness of FS - WorkflowFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerAR

Check Performed By:Review Date:YYYY-MM-DDYYYY-MM-DD

Sl #CategoryCheckCriticalityReview 1Review 2StatusComments1Business ProcessIs the flow chart provided?HighOpenAre the Triggering events mentioned?HighOpenAre the workflow steps defined?LowOpen

2Business ObjectsDoes FS contain the Business Object involved? If not are details sufficient to create a custom business object?HighOpenDoes FS contain methods to be called?MediumOpenDoes FS contain attributes to be used?MediumOpenDoes FS contain Events involved?MediumOpen

3RulesDoes FS contain rules?HighOpen

4AgentsAre all the possible agents mentioned ?HighOpen

5DeadlineDoes FS contain the details about deadline monitoring?HighOpen

6Test dataIs the test data created and specified?MediumOpenAre the test scenarios specified?MediumOpen

&BSAP Confidential&B&DPage &P

ReportsOpenCloseN/AChecklist for completeness of FS - ReportsFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


1Functional Requirement1.1Business process context and the purpose of the development within that context is provided?MediumOpen1.2Is the functional specification understandable?HighOpen1.3Have data dependencies been explainedHighOpen1.4Dependencies on other developments mentioned?HighOpen

2Selection Screen2.1Selection screen fields type informationHighOpen2.2Selection screen fields validation and error handlingMediumOpen2.3Are the mandatory fields identified?HighOpen2.4Are the selection criteria classified into Parameters & Select Options?HighOpen2.5Does the Selection Screen need to be organized into blocks, are the block titles listed in the FS?LowOpen2.6Are match code and F4 details are specified?MediumOpen

3Report Requirement3.1Type of report (ALV, Classical etc.)HighOpen3.2Performance requirement been given MediumOpen3.3Report layout HighOpen3.4User commands from report HighOpen3.5Report drill down informationHighOpen3.6Error and exception handling been mentionedHighOpen3.7Translation/Language requirements been mentioned?MediumOpen3.8If code has been given, has an explanation been given of the requirementsHighOpen3.9Is the Report to be run Online/Background?HighOpen3.10Is the title of the report furnished?LowOpen3.11Is the extraction criteria specified?HighOpen3.12What is the data that needs to be extracted?HighOpen3.13Is the processing logic specified?HighOpen3.14Is any standard Report Header to be followed for the list?LowOpen

4Testing Requirement4.1Have User acceptance criteria been enteredMediumOpen4.2Has test data and test cases been added (with step by step instructions)HighOpen

5New Table Requirement5.1Has it been specified whether table will be a configuration table or transactional tableHighOpen5.2Will table be maintainable by users or by function team and data transported to production?HighOpen5.3Has it been specified whether extra authorisation checks required for table data?MediumOpen

6Authorization6.1Authority objects specifiedHighOpen

7Configuration7.1Have configuration dependencies been givenHighOpen7.2Has configuration been createdHighOpen


InterfacesOpenCloseN/AChecklist for completeness of FS - InterfacesFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


Sl #Category / CheckCriticalityReview 1Review 2StatusComments1Functional Requirement1.1Business process context and the purpose of the development within that context is provided.MediumOpen1.2Is the functional specification understandable?HighOpen1.3Has data dependencies been explainedHighOpen1.4Dependencies on other developmentsHighOpen2Selection Screen2.1Selection screen fields type informationHighOpen2.2Selection screen fields validation and error handlingMediumOpen2.3Are the mandatory fields identified?HighOpen2.4Are the selection criteria classified into Parameters & Select Options?HighOpen2.5Does the Selection Screen need to be organized into blocks, are the block titles listed in the FS?LowOpen2.6Are match code and F4 details are specified?MediumOpen2.7Is any validation required to check for valid path/file?MediumOpen3Interface Requirement3.1Type of interface been mentioned (Inbound/Outbound/RFC/ALE/File etc)HighOpen3.2Triggering mechanism been givenHighOpen3.3Performance requirement been given MediumOpen3.4Interface layout been given with data formatting information HighOpen3.5If posting to be done has recording been givenHighOpen3.6Error and exception handling been mentionedHighOpen3.7Error/Success report information been givenHighOpen3.8For file interfaces have logical file path information been givenHighOpen3.9For file interfaces, has file name structure been givenHighOpen3.10Has sample files been givenLowOpen3.11Idoc interface has transaction been given that will generate/need to be updated by idocHighOpen3.12Idoc interface has partner profile information been givenHighOpen3.13Translation requirements been mentioned?MediumOpen3.14If code has been given, has an explanation been given of the requirementsHighOpen3.15Will the interface be run in foreground/background?HighOpen3.16What is the frequency of the interface run?MediumOpen3.17Has the expected volume of data been specified in the FS?MediumOpen3.18Rerun approach specified in FSHighOpen3.19Is the file to be picked from Presentation Server/ Application Server or provision kept for both? HighOpen3.20Has the type of the input file been specified? csv, tab limited, ASCI etc?MediumOpen3.21Sufficient mapping and conversion details given on FSMediumOpen3.22Is any validation required for the information in the Input files? MediumOpen3.24Has the output format been specified for the Interface program run? HighOpen3.25Target File Location/Target File name. Are these included in the Selection Screen? HighOpenFor Outbound Interfaces (can be applicable in Inbound also)3.26What is the data that needs to be extracted?HighOpen3.27Is the extraction criteria specified?HighOpen3.28Is any mapping of the data required to be done before uploading data in SAP? HighOpenAre the mapping and conversion rules specified? HighOpenHas the transaction code of the source/target transaction been specified?HighOpenHas the output format been specified for the Interface program run? MediumOpen4Testing Requirement4.1Have User acceptance criteria been enteredMediumOpen4.2Has test data and test cases been added (with step by step instructions)HighOpen5New Table Requirement5.1Has it been specified whether table will be a configuration table or transactional tableHighOpen5.2Will table be maintainable by users or by function team and data transported to production?HighOpen5.3Has it been specified whether extra authorisation checks required for table data?MediumOpen6Authorization6.1Authority objects specifiedHighOpen7Configuration7.1Have configuration dependencies been givenHighOpen7.2Has configuration been createdHighOpen


ConversionOpenCloseN/AChecklist for completeness of FS - ConversionFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


Sl #CategoryCheckCriticalityReview 1Review 2StatusComments1GeneralHas the source of the Migration data been specified?HighOpenHas the expected volume of data been specified in the FS?HighOpen

2Selection ScreenDoes the Program have a Selection Screen? HighOpenAre all the selection criteria well defined?HighOpen

3File InformationSource File Location/Source File name. Are these included in the Selection Screen? HighOpenIs the file to be picked from Presentation Server/ Application Server or provision kept for both? HighOpenAre all the customizing dependencies for the development statedMediumOpenIs any validation required to check for valid path/file?MediumOpenFor program to be run in the background mode, make sure that the file is to be picked from the Application Server only.HighOpenHas the type of the input file been specified? csv, tab limited, ASCI etc?HighOpenIs the file structure clearly defined?HighOpenIs a sample data file attached to the FS?HighOpen

4Valuation & MappingIs any validation required for the selection criteria of the program? MediumOpenAre the validation details specified in the FS?MediumOpenIs any validation required for the information in the Input files? MediumOpenAre these details specified in the FS?MediumOpenIs any mapping of the data required to be done before uploading data in SAP? HighOpenAre the mapping rules specified? HighOpenIs the mapping comprehensive? HighOpen

5Transaction DetailsHas the transaction code for the target transaction been specified?HighOpenHas information been provided in the FS to enable a Developer post a test transaction? HighOpenIs there any preferred method for posting the transaction? BAPI/IDoc etc? If yes, has the relevant information, if available, been furnished?HighOpen

6Error HandlingHas the error handling for the input validations (for the data in the file) been specified in the FS? HighOpenHow should the error records be handled? HighOpenShould the program still continue with the posting of the OK records? Or should the program allow posting only when all the errors have been corrected in the input file?HighOpenHas the format for error reporting been specified? MediumOpenShould the error be reported in a list or should a separate file be generated for the error recordsMediumOpen

7Program OutputHas the output format been specified for the Interface program run? MediumOpenIs any standard Report Header to be followed for the list?MediumIs any language specific reporting required?MediumOpen 8Test DataIs the Test data created & specified?HighOpenAre the test scenarios specified?HighOpen


EnhancementsOpenCloseN/AChecklist for completeness of FS - EnhancementsFS Deliverable CodePSC_E_06FS TitleNetwork NumberSAP ComponentFS Check list IDFS AuthorGreg PetersProject ManagerDelivery Manager

Check Performed By:GPETERSReview Date:8/25/09YYYY-MM-DD

Sl #Category / CheckCriticalityReview 1Review 2StatusComments1Functional Requirement1.1Business process context and the purpose of the development within that context is provided.MediumYOpen1.2Is the functional specification understandable?HighYOpen1.3Have data dependencies been explainedHighYOpen1.4Dependencies on other developmentsHighNAOpen1.5Incase of modification, has the reason for modifying Standard SAP specified?NA

2Enhancement Requirement2.1Has transaction information been givenHighYOpen2.2Type of enhancement been given (Module Pool/User Exit/BADI etc.)MediumYOpen2.3Is the information enough to find the EXIT / BADI?HighYOpen2.4Is the expected output format from the enhancement specified?HighYOpen2.5Are assumptions (if any) specified?LowYOpen2.6Are tran/business process, affected by the EXIT/BADI specified?MediumYOpen2.7Is the triggering point mentioned? (Header Level / Item Level)HighYOpen2.8Are the data flow between the modules clearly statedHighYOpen2.9Incase of Module Pool, is the screen layout clearly documentedHighNAOpen2.10Are upgrade requirements and constraints clearly statedMediumYOpen2.11Are there any language dependencies. If, Yes whether details provided in FSMediumNOpen2.12What is the data that needs to be extracted?HighYOpen2.13Is the extraction criteria specified?HighYOpen2.14Is the processing logic specified?HighYOpen

3Testing Requirement3.1Have User acceptance criteria been enteredMediumYOpen3.2Has test data and test cases been added (with step by step instructions)HighNOpen

4New Table Requirement4.1Has it been specified whether table will be a configuration table or transactional tableHighNAOpen4.2Will table be maintainable by users or by function team and data transported to production?HighNAOpen4.3Has it been specified whether extra authorisation checks required for table data?MediumNAOpen

5Authorization5.1Authority objects specifiedHighNAOpen

6Configuration6.1Have configuration dependencies been givenHighNAOpen6.2Has configuration been createdHighNAOpen


FormsOpenCloseN/AChecklist for completeness of FS - FormsFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


Sl #Category / CheckCriticalityReview 1Review 2StatusComments1Functional RequirementOpen1.1Business process context and the purpose of the development within that context is provided.MediumOpen1.2Is the functional specification understandable?HighOpen1.3Has data dependencies been explainedHighOpen1.4Dependencies on other developmentsHighOpen2Selection Screen2.1Selection screen fields type informationHighOpen2.2Selection screen fields validation and error handlingMediumOpen2.3Are the mandatory fields identified?HighOpen2.4Are the selection criteria classified into Parameters & Select Options?HighOpen2.5Does the Selection Screen need to be organized into blocks, are the block titles listed in the FS?LowOpen2.6Are match code and F4 details are specified?MediumOpen3Form Requirement3.1Transactions involved been givenHighOpen3.2Triggering mechanism been givenHighOpen3.3Data layout and formatting been given MediumOpen3.4Any new logo required been included HighOpen3.5Type of form been given (Label/Sapscript/Smartform/Interactive)HighOpen3.6Output medium is specified Printer/ Fax/ Mail.HighOpen3.7Will be using pre-printer stationary? Exact specification or copy of stationary providedHighOpen3.8Page format to be used example A4, Letter, LandscapeHighOpen3.9Printer information been givenLowOpen3.10Label printing requirements example Bar One software and zebra printersHighOpen3.11Language/Translation requirements been mentioned?MediumOpen3.12If code has been given, has an explanation been given of the requirementsHighOpen3.13What is the data that needs to be extracted?HighOpen3.14Is the extraction criteria specified?HighOpen3.15Is the processing logic specified?HighOpen3.16Is printout style mentioned (duplex/single)?HighOpen3.17Is sample printout given with dimensions?HighOpen4Testing Requirement4.1Have User acceptance criteria been enteredMediumOpen4.2Has test data and test cases been added (with step by step instructions)HighOpen5New Table Requirement5.1Has it been specified whether table will be a configuration table or transactional tableHighOpen5.2Will table be maintainable by users or by function team and data transported to production?HighOpen5.3Has it been specified whether extra authorisation checks required for table data?MediumOpen6Authorization6.1Authority objects specifiedHighOpen7Configuration7.1Have configuration dependencies been givenHighOpen7.2Has configuration been createdHighOpen


XI

Checklist for completeness of FS - XIFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


Sl #CategoryCheckCriticalityReview 1Review 2StatusCommentsGeneral 1Solution manager document correct document typeHighOpen2Solution manager document ApprovedHighOpen3Is project/release code given?MediumOpen4Business process context and the purpose of the development within that context is provided.MediumOpenDesign Related5Is the functional specification understandable?HighOpen6Process and Scope of XI clearly definedHighOpen7Mode of communication mentioned(Sync/Async)HighOpen8Mapping logic (Transformation rules) is clearHighOpen9Cardinality of source and target structure is defined or can be derived easilyHighOpen10Requirement of value mapping, if any, has been mentionedMediumOpen11Is any decision making involved in XIMediumOpen12Has the mechanism for triggering of interface articulatedMediumOpenConfiguration Related13Is the source/target systems definedHighOpen14Has protocol for sender and receiver definedMediumOpen15Is the routing logic (if applicable) definedMediumOpen16In case of file adapter, is archiving strategy definedLowOpen17Has acknowledgement strategy definedMediumOpen18Connection detailes specified for the adaptersLowOpenInterface Requirement19Execution frequency of the interface specified.MediumOpen20Business criticality has been specifiedHas test data and test cases been added (with step by step instructions)MediumOpen21Has the expected volume/peak volume/average file size per message been specifiedHighOpen22In file communication, is the maximum size of the file specifiedMediumOpen23Error handling specifiedMediumOpen24Monitoring and restart requirements documentedLowOpen

CRM - UI

Checklist for completeness of FS - CRMFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


Sl #CategoryCheckCriticalityReview 1Review 2StatusCommentsGeneral 1Solution manager document follow the correct naming conventionHighOpen2Solution manager document correct document typeHighOpen3Solution manager document ApprovedHighOpen4Is project/release code given?HighOpenFunctional Requirement 5Business process context and the purpose of the development within that context is provided.MediumOpen6Is the functional specification understandable?HighOpen7Has data dependencies been explainedHighOpen8Dependencies on other developmentsHighOpen9Has the fields required specifiedHas the fileds required specifiedHighOpen10Has look and feel of the application explainedHas look and feel of the application explainedHighOpen11What is the business happening in this page?what is the business happening in this pageHighOpen12What is the expected number of users?what is the expected number of usersHighOpen13What is the expected response time?what is the expected response timeMediumOpen14All customizing dependencies are specifiedAll customizing dependencies are specifiedHighOpen15Has the expected volume of data been specified in the FS?Has the expected volume of data been specified in the FS?MediumOpen16Return and navigation of the screen specified?Return and navigation of the screen specified?HighOpen17Any other file type need to be handled or loaded (example adobe, excel)Any other file type need to be handled or loaded (example adobe, excel)HighOpen18Test Run details providedTest Run details providedMediumOpen19Is a sample screen shot attached.Is a sample screen shot attached.MediumOpenLayout20Are the User Interface elements been properly mentioned in a layout form and mockup?Are the User Interface elements been properly mentioned in a layout formHighOpen21Are the mandatory fields identified?Are the mandatory fields identified?MediumOpen22Are the SAP reference field mentioned ?Are the SAP reference field mentioned ?MediumOpen23Are the corresponding Input fields shown as Enabled/Disabled ?Are the corresponding Input fields shown as Enabled/Disabled ?HighOpenNavigation Flow24Selection screen fields type informationMediumOpen25Selection screen fields validation and error handlingMediumOpenSecurity26what sort of security expected at the portal page.MediumOpenValidations27what all fields are validated.what all fields are validated.MediumOpen28Are the validation details specified in the FS?Are the validation details specified in the FS?MediumOpenExtraction Logic29What is the data that needs to be extracted?What is the data that needs to be extracted?MediumOpen30Is the date period criteria specified?Is the date period criteria specified?MediumOpen31Is the processing logic specified?Is the processing logic specified?MediumOpen32Have the Default drop down values been mentioned ?Have the Default drop down values been mentioned ?MediumOpenTesting Requirements 33Have User acceptance criteria been enteredMediumOpen34Has test data and test cases been added (with step by step instructions)HighOpen35Contact information been given for 3rd party to allow testingHighOpenNew table requirement 36Has it been specified whether table will be a configuration table or transactional tableHighOpen37Will table be maintainable by users or by function team and data transported to production?HighOpen38Has it been specified wether extra authorisation checks required for table data?MediumOpenConfiguration39Have configuration dependencies been givenHighOpen40Has configuration been createdHighOpen

EP

Checklist for completeness of FS - EPFS Deliverable CodeFS TitleSAP ComponentFS Check list IDFS AuthorProject ManagerDelivery Manager


Sl #Category / CheckCriticalityReview 1Review 2StatusComments

General 1Has the objective of the Application been spelt out?HighOpen2Is the title of the Application furnished?Is the title of the Application furnished?HighOpen3Is report type mentioned (WebDynpro Views / Adobe Forms)?Is report type mentioned (WebDynpro Views / Adobe Forms)?HighOpen2Has the fields required specifiedHas the fileds required specifiedHighOpen3Has look and feel of the application explainedHas look and feel of the application explainedHighOpen4what is the business happening in this pagewhat is the business happening in this pageHighOpen3what is the expected number of userswhat is the expected number of usersHighOpen4what is the expected response timewhat is the expected response timeMediumOpen5All customizing dependencies are specifiedAll customizing dependencies are specifiedHighOpen4Has the expected volume of data been specified in the FS?Has the expected volume of data been specified in the FS?MediumOpen5Return and navigation of the screen specified?Return and navigation of the screen specified?HighOpen6Any other file type need to be handled or loaded (example adobe, excel)Any other file type need to be handled or loaded (example adobe, excel)HighOpen5Test Run details providedTest Run details providedMediumOpen6Is a sample screen shot attached.Is a sample screen shot attached.MediumOpenLayout7Are the User Interface elements been properly mentioned in a layout form and mockup?Are the User Interface elements been properly mentioned in a layout formHighOpen8Are the mandatory fields identified?Are the mandatory fields identified?MediumOpen9Are the SAP reference field mentioned ?Are the SAP reference field mentioned ?MediumOpen10Are the corresponding Input fields shown as Enabled/Disabled ?Are the corresponding Input fields shown as Enabled/Disabled ?HighOpenNavigation Flow11Selection screen fields type informationMediumOpen12Selection screen fields validation and error handlingMediumOpenSecurity13what sort of security expected at the portal page.MediumOpenValidations14what all fields are validated.what all fields are validated.MediumOpen15Are the validation details specified in the FS?Are the validation details specified in the FS?MediumOpenExtraction Logic16What is the data that needs to be extracted?What is the data that needs to be extracted?MediumOpen17Is the date period criteria specified?Is the date period criteria specified?MediumOpen18Is the processing logic specified?Is the processing logic specified?MediumOpen19Have the Default drop down values been mentioned ?Have the Default drop down values been mentioned ?MediumOpenTest Data20Is the Test data created & specified?Is the Test data created & specified?HighOpen21Are the test scenarios specified?Are the test scenarios specified?MediumOpenProgram Output22Has the output format been specified? MediumOpen

Checklist Functional Enhancements

Documents

Transcript of Checklist Functional Enhancements