CDF_ABAP Estimator_V2.1

Document Control & InstructionsSAP-ABAP RICEF EstimatorVersionDateAuthorChange Description1.030-Jun-08Sangram ChowdhuryInitial1.128-Aug-08Sangram ChowdhuryFew Formula errors fixed1.211-Dec-08Sangram ChowdhuryScores Adjusted & Additional set of custom criteria included1.305-Apr-09Sangram ChowdhuryFixed error associated with reduction percentage1.416-Dec-09Sangram ChowdhuryRICEF Estimates reduced, Scope of change section finetuned.1.505-Jul-09Sangram ChowdhuryAdded separate section for ADOBE Print Forms1.631-Jul-11Sangram ChowdhuryIncluded ABAP WebDynpro1.714-Oct-11Somenath BanerjeeCR Complexity and Point Assignment1.801-Jul-12Somenath BanerjeePoint Calculation1.901-Aug-12Somenath BanerjeeFunctional Effort Adder2.001-Oct-12Somenath BanerjeeOSS Note CDFINSTRUCTIONS :1. Go to the second tab of the excel named "CDF".2. Select the Development Type in Cell "B1". See Screenshot below.3. Click the button named:4. Select appropriate option for each parameter from drop-down lists5. Change scope of change in Cell "J5". By default it is "New Program":6. After selecting options for all relevant parameters, see the RESULTS under column "H"& "J":7. To clear all selections, click the button:8. Save the CDF using "File->Save As" menu path and give name "CDF_.xls"Note: The "Calculation" tab is read only and the User/CDF preparer do not need to refer to it.

CDFDevelopment TypeSAPScript/SmartformsReferenceRESULTShow SectionEstimated Complexity : HighEstimation SectionEstimation ParameterSelectionScoreMeasuresScoreHour(s) : 106YesAssigned Point(s) : 30106Database AccessNumber of Tables/Data Sources accessed (exclude Tables accessed for input validation)5 to 95N/A0R&IYesNew Program100%34Less than 5234YesScope of Change: 40% Changes to Existing Custom program to add New Functionality> 40% Changes to Existing Custom program to add New Functionality70%1510 to 19855Yes0.7 20% to 30% Changes to Copied or Original SAP Standard Program60%Creation of data dictionary items like custom tables, views, structures, lock objects. (Don't consider just Data Element/Domain Creation)2 to 53N/A02YesYes> 30% Changes to Copied or Orginal SAP Standard Program75%Only 12Functional EffortYes2 to 5315Yes6 to 105106YesHighVery LowLowMediumHighVery High10 or more8Yes15FIN66101515Primary Mode of Data Access/SelectionSelect StatementsYes1Select Statements1YesFunction Modules0Function Modules1Yes12P2P4481212Logical Database0Logical Database5YesUse of Normal Class0Use of Normal Class1Yes6P2Y33466Use of Persistence Class0Use of Persistence Class3YesNative SQL0Native SQL5Yes6P2Y-SRM33466Selection Screen (also for Customization involved for Logical Database Selection Screens)Number of Selection-Screens being created/changed (No of multiple TABs in the Selection Screen) ?Only 12N/A0YesOnly 12Yes12OTC44812122 to 33Yes4 or more5Yes12SCIPIO4481212Total Number of Screen Objects (e.g. Parameters, Selection Options) being created/changed considering all Selection Screens ?5 to 103N/A0YesLess than 52Yes5 to 103Yes11 to 205Yes21 or more8YesAt-Selection Screen on Help Request or Value request processing involved ?0No0YesYes3YesCreation of Tabstrips, Function Keys, Pushbutton on the Selection Screen ?0No0YesYes3YesNumber of Selection Screen validations0N/A0Yes1 to 52Yes6 to 104Yes11 or more7YesType of Selection Screen validations0N/A0YesIndependent validation for each individual object2YesIndividual as well group validations for objects4YesScreen manipulations (during At Selection Screen Output) depending on single/Group validations/User Interactions0No0YesYes3YesProgramming LogicSource Program0New ProgramNo 40% Changes to Existing Custom program to add New FunctionalityNo 20% to 30% Changes to Copied or Original SAP Standard ProgramNo> 30% Changes to Copied or Orginal SAP Standard ProgramNoCalculation Steps for majority of calculated components0N/A0YesSingle Step1YesMultiple Step3YesNumber of calculated components in the program0N/A0YesLess than 51Yes6 to 152Yes16 to 305Yes31 or more8YesExtra Functionality like Mail sending, building Application Log/System Log etc.0No0YesYes3YesSpecial processing involved to handle large volume data ( e.g. processing data in parts to prevent timeout )0No0YesYes3YesCreation of Background Jobs from the program0No0YesYes2YesDynamic columns in input file or output listYes3No0YesYes3YesInvolvement of Summary and/or Control (e.g. AT NEW) level custom calculations0No0YesYes3YesTranslation RequirementYes2No1YesYes2YesNo of calls to other programs0N/A0Yes1 or 22Yes3 to 54Yes6 or more7YesNo of calls to C programs or other non-ABAP programs:0N/A0Yes1 or 22Yes3 to 53Yes6 or more5YesInvolvement of parallel processing in different work Processes0No0YesYes3YesProgramatically create F1 or F4 help0No0YesYes3YesData Updation Requirement0No0YesYes3YesNumber of Tables Updated1 or 22N/A0Yes1 or 22Yes3 or more4YesUsage of Macros for Logical Database Processing0N/A0YesNo of Macros to be written: 1-53YesNo of Macros to be written: 5-106YesNo of Macros to be written: more than 1010YesProgramatically accessing Memory Stack at Runtime to access higher level program parameters.0Not required0YesRequired2YesOutput events and event handling0N/A0YesDouble click/Function Key/Pushbutton2YesContext menu2YesDrag & drop4YesExpand collapse4YesPrimary Mode of Data UpdationPlease select all applicable options:0Data Updation not involved0YesUsing UPDATE statement in programYes2Using UPDATE statement in program2YesUsing Call Transaction0Using Call Transaction3YesUsing Batch Input Sessions0Using Batch Input Sessions3YesUsing Direct Input Program0Using Direct Input Program5YesUsing SAP Standard Function Module/BAPI0Using SAP Standard Function Module/BAPI3YesUsing Standard Class0Using Standard Class5YesUsing Asynchronous Updates(parallel updates via background task, wf task,)0Using Asynchronous Updates (parallel updates via background task, WF task)5YesUsing Persistence Class0Using Persistence Class6YesLogical Unit of Work processing / Table locking/unlocking during data update ?0No0YesYes4YesAudit Trail / Change History log tracking ?0No0YesYes3YesError Handling/Error Reporting requirement ?0No0YesYes3YesData Cleansing requirement ?0No0YesYes3YesReport Display (Gereral) OptionsTechnique used to develop Report ?0ALV1NoClassical2NoObject Oriented ALV4NoUse of special output functions like Tree Control, Docking control, Picture control, Text Editor, Hierarchical Output, PDF or HTML output, Custom Download of Output etc.0Single Special Control4NoMultiple Special Control8NoNumber of Drill-down levels in Output0Only 1 level2No2 levels3No3 or more levels7NoALV Report Specific CriteriaALV Report Display (Functions Used)Row/Column Coloring0Row/Column Coloring1NoCell Coloring0Cell Coloring2NoCreation & Use of Layout Variant0Creation & Use of Layout Variant1NoTop-of-Page processing0Top-of-Page processing1NoColumn-specific display characteristics0Column-specific display characteristics2NoProgrammatic filtering or sorting of output0Programmatic filtering or sorting of output1NoDrag & drop0Drag & drop3NoCustom Control involved0Custom Control involved3NoProgrammatic manipulations of the field-catalog0Programmatic manipulations of the field-catalog1NoLayout Management0Layout Management1NoUser Interaction & Event Handling0User Interaction & Event Handling4NoEditing & Saving0Editing & Saving4NoMulti row column heading0Multi row column heading2NoClassical Report Specific CriteriaClassical Report Display (Functions Used)Row/Column/Cell Coloring0Row/Column/Cell Coloring1NoSorting of Output0Sorting of Output2NoColumn-specific display characteristics0Column-specific display characteristics1NoEditing & Saving0Editing & Saving2NoUser Interaction & Event Handling0User Interaction & Event HandlingNoClassical Report lay-out: Number of Columns to be displayed01 to 202No21to 504No51 or more8NoBDC ProcessingNumber of SAP R/3 transactions involved01 to 22No3 or more4NoAverage number of screens involved during data update in each transaction (Inbound Interface & Data Conversion):01 to 32No4 to 74No8 or More6NoTable Control Involved ?0No0NoYes3NoSpecial transaction handling (using CTU_PARAMS structure/ special options of Call Transaction)0No0NoYes2NoBAPI / Function Module ProcessingLocating BAPI/Function Module0Already Known0YesNeed to debug & find3YesParameter mapping0Re-usable code/tips available1YesNeed to map from scratch3YesBAPI/Function Module Documentation0Sufficient documentation with examples1YesInsufficient documentation3YesFile HandlingNumber of Files accessed or genereated01 to 22No3 to 44No5 or More7NoComplexity of File structure0Hierarchy not involved1NoHierarchy maintianed in single file2NoHierarchy maintianed in multiple files3NoSingle record contains both header and line item3NoNumber of columns in the File0Less than 151No15 to 252No25 to 403NoMore than 404NoType of Columns0Fixed1NoDynamic4NoUse of OS level commands for file handling/FTP0No0NoYes4NoField MappingField Mapping Rules0Direct one to one field mapping for 100% of the fields1NoDirect one to one field mapping for > 75% of the fields2NoDirect one to one field mapping for 50% to 75% of the fields3NoDirect one to one field mapping for 25% to 50% of the fields4NoDirect one to one field mapping for only less than 25% of the fields6NoField Mapping specification, that is appicable for majority of the fields0Single field in one system must be sent to a single field in the other system1NoMultiple fields in one system must be concatenated and sent to a single field in the other system2NoSingle field in one system must be parsed as substrings and sent to multiple different field in the other system2NoContains single field on one side mapped to many different fields on other side using qualifiers3NoALE/EDI ProcessingNew Extension required ?0No0NoYes3NoTotal number of Source & Target Systems0Only 22No2 to 33No4 and more4NoNew Basic Type creation ?0No0NoYes5NoNumber of Basic ALE configuration (Partner profiles, distribution model, ports, change pointers, etc. Increment 1 level if logical system / RFC destination also needs to be created) required ?0N/A0NoOnly 11No2 to 32No4 or more4NoNon ALE related configuration like Output types, change documents0N/A0NoOnly 12No2 or more4NoIDOC Extension0N/A0NoLess than 5 segments2No5 10 segments3No11 or more segments5NoIDOC Reduction0N/A0NoLess than 5 segments2NoMore than 5 segments3NoNumber of EXITs to locate and Use. (Not provided in FS)0N/A0NoOnly 12No2 to 43No5 or more5NoCreation of Custom Message Type0No0NoYes2NoSerialization / Linkage of Message types0N/A0NoEither2NoBoth3NoNumber of Events triggered0N/A0NoOnly 12No2 or more4NoComplexity of validation & error processing, including error report , workflow config, etc.0N/A0NoOnly error report / BDC session2NoWorkflow configuration3NoWorkflow config. with creation of methods4NoReal time interfacing requirements (i.e. RFC, BAPI) ?0No0NoYes2NoCreating / Assigning / Maintaining Conversion Rules0N/A0NoUsing SAP conversion rules2NoCreating custom conversion rules4NoNew tool knowledge requirement, analysis and configuration of 3rd party tools etc.?0No0NoYes3NoDeveloping custom Outbound / Inbound ALE function module0N/A0NoEnhancement (User-Exit) of SAP FM with minor changes2NoEnhancement of SAP function module with major changes or copy of SAP FM4NoStandalone programs / Function modules for triggering or processing Idocs/ Handling of change pointers0N/A0NoRequired2NoLSMW Specific CriteriaCustom Direct Input program creation required ?0No0NoYes4NoSpecial Error reporting required ?0No0NoYes4NoLSMW Method Used0BDC3NoDirect Input2NoBAPI3NoIDoc4NoNumber of LSMW objects to be created ?0N/A0NoOnly 12No2 to 33No4 or more5NoNumber of Reusable rule, User defined routine ?0N/A0No1 to 22No3 to 63No7 or more5NoStep loop in LSMW (header-item relations) ?0No0NoYes4NoEnhancement specific criteriaEnhancement Technique used ?Table/Field Enhancement0Table/Field Enhancement1NoFunction ExitYes2Function Exit2NoBAdi0BAdi2NoDirect modification to SAP Standard Program0Direct modification to SAP Standard Program2NoForm Exit0Form Exit2NoField Exit0Field Exit2NoMenu Exit0Menu Exit3NoSearch Help Exit0Search Help Exit3NoScreen Enhancement: Number of Screen: 10Screen Enhancement: Number of Screen: 13NoVOFM Routines0VOFM Routines3NoEnhancement Spots0Enhancement Spots4NoSubstitution Exit0Substitution Exit4NoBTE0BTE5NoScreen Enhancement: Number of Screen > 10Screen Enhancement: Number of Screen > 15NoSAP Transaction Extension (e.g. Material Master Extension, Customer Master Extension)0SAP Transaction Extension (e.g. Material Master Extension, Customer Master Extension)5NoData Transfer/ Coordination through SAP/ABAP Memory between exits ?0No0NoYes2NoNumber of EXITs to locate/Use. (Not provided in FS , Complex or unknown scenarios/modules which requires a lot of research impact the overall estimation)0N/A0NoOnly 12No2 to 43No5 or more5NoImpact of EXIT in different transactions (Sometime it happens that adding a code inside one EXIT could break the other transactions functionality. Is it required to handle this scenario inside the EXIT ?Single Transaction0Single Transaction0NoMultiple Transaction2NoCreation of New Enhancement(in SMOD) or BAdi Definition (in SE18) involved ?0No0NoYes4NoPresence of existing code inside the same Exit and addition of new code having effect on existing code ?Yes2No0NoYes2NoNumber of related objects which must also be modified during modification of Standard Programs0N/A0NoOnly 12No2 to 63No7 or more5NoMultiple implementations involved for Multiple Use Badi or depending on the filter values of Filter Dependent BAdi ?0N/A0NoOnly 22No3 to 53No6 or more5NoSAPScript/Smartforms specific criteriaForm Technique used ?SMARTForms2SAPScript3YesSMARTForms2YesLayout Creation/ModificationH : > 5 New Nodes added0N/A0YesCreation of New Layout3YesModification of Existing Layout2YesRequire Creation of New Layout ?Up to 2 Pages, 5 Windows per Page & 15 Fields2N/A0YesUp to 2 Pages, 5 Windows per Page & 15 Fields2YesMore than criteria above4YesSame Layout/Program is used in more than one development based on Output type ?0No0YesYes2YesTranslation Requirement3 or more Languages3Not required or Single Language0Yes2 Languages2Yes3 or more Languages3YesRequire changes to Existing Layout or Copying and changing another layout ?Addition of new items on a page3N/A0YesMinor changes to text, commenting lines, etc or only Alignment Changes to items on a Page1YesModifying (Moving, Deleting) existing items on a page2YesAddition of new items on a page3YesNumber of Standard Texts/Text-Modules involved ?No. of texts to be created - > 103N/A0YesUse of existing texts1YesNo. of texts to be created - 1-102YesNo. of texts to be created - > 103YesHandling the Standard-Texts (Size of text-contents, Formatting, if any, for the Texts)Dynamic Standard Text Used2N/A0YesDynamic Standard Text Used2YesRun-time formatting of Standard Text required4YesPrinting of LogoN/A0N/A0YesLogo is Static2YesIf Logo change dynamically based on country, plant, etc.3YesCreation of Logo0N/A0YesLogo is available in the system2YesLogo to be created from image file3YesRequirement of New Page Format ?0No0YesYes2YesPrinting of Bar Codes/MICR0N/A0YesUsing an existing font2YesNeed to create new Bar Code font4YesPrinting of Sub-Total without changing the driver program0N/A0YesIn SmartForms1YesIn SAPScript4YesSending output via E-mail/FAX ?0No0YesYes2YesPrinting using Pre-Printed paper ?0No0YesYes3YesLabel printing using Third party s/w such as Bar-one or Bartender ?0No0YesYes3YesCheque Printing Involved ?0No0YesYes2YesPrinting of Address and Date based on specific criteria (e.g. Country) ?0N/A0YesStandard Formatting1YesCustom Formatting2YesStyle Creation involved ?Yes2No0YesYes2YesDynamic Column Creation involved ?0No0YesYes3YesCurrency/Quantity printing ?0N/A0YesWith >=1 Decimals1YesWith No Decimals2YesDoube Byte Character used ?0No0YesYes2YesPrinting of Boxes, Lines, Shading, etc. ?0No0YesYes2YesUse of Scripting Language Formcalc/Java Script0N/A0YesMinor Calculations2YesCalculations using Functions, Validations, Subtotals3YesADOBE Print Forms specific criteriaRequire Creation of New Layout ?0Existing PDF-file/template reused1NoCopy existing layout2NoNew Layout needs to be created3NoMigrated from SMARTFORMS4NoMigrated from SAPScript6NoComplexity of Interface - If existing Interface used0N/A0NoL - Existing Interface with minimal or no changes1NoM - New data-selection as well as moderate amount of data-manipulation/calculation logic involved2NoH - Many new data-selction as well as complex data-manipulation/calculation logic involved4NoComplexity of Interface used - If New Interface required0N/A0NoL - Minimal data-selection logic. Very little or no data-manipulation/calculation logic involved1NoM - New data-selection as well as moderate amount of data-manipulation/calculation logic involved3NoH - Many new data-selction as well as complex data-manipulation/calculation logic involved4NoComplexity of Context-usage0L -Only the elements from Interface used with/without deactivation of portions1NoM - 5 New Nodes added4NoNo. of Master-Pages involved? The Master-pages maybe of different type (A4, Letter, etc), as well as different Layout (Potrait, Landscape)0L : 1 - 21NoM : 32NoH : >34NoNo. of Sub-forms involved (throughout the Form)?0N/A0NoL : 1 - 21NoM : 3 - 42NoH : >43NoNumber of Standard Texts/Text-Modules/Static Images involved ?0N/A0NoL : 1 - 21NoM : 3 - 42NoH : > 43NoTranslation Requirement01 Language2No> 1 language4NoN/A0NoPrinting using Pre-Printed paper ?0Pre-printed stationary in the form of ADOBE File is NOT Available5NoPre-printed stationary in the form of ADOBE File Available2NoN/A0NoHow many different UoM to be displayed on the layout ?0>= 43No 56NoNo. of Elements/View0< 62No6 - 103No> 106NoNo. of Windows0< 22No2 - 45No> 48NoComplexity of Elements involved0Straightforward Text, Layout,Action elements involved1NoComplicated Layout, Action, Selection Elements involved3NoComplex Elements (Table, PhaseIndicator, Roadmap,etc) involved5NoGraphic, Office-Integration, Adobe Elements involved12NoComponent-usage involved012No2 - 45No> 48NoNature of Component usage0Straightforward usage of Methods, Contex-Nodes3NoComplex Data-manipulation logic present in both the Components6NoUsage of Assistance Class0No0NoYes3NoAdditional features involved0Popups3NoCustom-Controllers4NoConfiguration4NoDynamic Context-modification5NoFloor-Plan Manager10NoAdd-ons (Flash,etc.)14NoInteractive ADOBE Form involved0No0NoYes8NoFor ADOBE-Interactive Forms (Online only)0Attachment-handling6NoValidation & Message-handling4NoNo. of Elements on the ADOBE form-layout (Online/Offline)0< 103No10 - 154No> 155NoFor ADOBE Interactive-Forms (Online/Offline)0Straigtforward usage of elements2NoInteractive Elements(Buttons, Drop-Downs,etc.)5NoFor ADOBE Interactive-Forms (Online/Offline), Scripting involved ?0No0NoYes7NoMetadata configuration for static display (SRM)01 - 101No> 102NoMetadata configuration for dynamic display (SRM)01 - 52No> 55NoPreparing Technical Specification (only documentation effort is considered in this section and effort for pseudocode creation is covered within other sections)Documentation CategoryUpdate existing Document1Update existing Document1YesPrepare from Scratch3YesFunctional Specification contains Technical Details ?No3Yes1YesNo3YesTable Access Diagram Required ?0No0YesYes2YesFlow Diagram Required ?0No0YesYes2YesPreparing Unit Test Plan (Unit Testing Effort is covered within other sections and this section mainly focuses on documentation effort)Documentation CategoryPrepare from Scratch3Update existing Document1YesPrepare from Scratch3YesTest Scenarios Specified in the Functional Specification ?Yes1Yes1YesNo4YesNumber of Business Scenarios to be tested (Data Creation is not within scope of Development team. If it is done, should be estimated separately)5 or More4Only 11Yes2 to 42Yes5 or More4YesNo of Test Conditions (Positive + Negative) anticipated ?16 or more5Up to 51Yes6 to 102Yes11 to 153Yes16 or more5YesInvolves Testing & giving Screenshots from Portal (Web GUI)?0No1YesYes2YesValidation MethodRequires reference from multiple database table/transaction values4Directly from program Output2YesRequires reference from multiple database table/transaction values4YesRequires to show calculation4YesCross System validation5YesCross Technology validation7YesAdditional set of Criteria/Reasons specific to the development effecting the overall Estimate (not covered above)Set of specific additional criteria that would INCREASE the Estimate:Specify the overall INCREMENT percentage below:Yes18YesSet of specific additional criteria that would REDUCE the Estimate:Specify the overall REDUCTION percentage below:YesYesDrop-down List for Development TypePlease select Development TypeClassical ReportALV ReportInterface-Outbound (non-ALE)Interface-Inbound (non-ALE)ALE InterfaceConversion (non-LSMW)LSMW ConversionEnhancementSAPScript/SmartformsADOBE Print FormsModule PoolWorkflowABAP Web Dynpro

Sangram: Database AccessSangram: Selection Screen (also for Customization involved for Logical Database Selection Screens)Sangram: Programming logicSangram: Please select Deleopment Type in the next cellSangram: BAPI / Function Module ProcessingSangram: Preparing Technical SpecificationSangram: Preparing Unit Test PlanSangram: Report Display (Gereral) OptionsSangram: ALV Report Specific CriteriaSangram: Classical Report Specific CriteriaSangram: BDC ProcessingSangram: File HandlingSangram: Field MappingSangram: ALE/EDI ProcessingSangram: LSMW Specific CriteriaSangram: Enhancement specific criteriaSangram: Module Pool Specific CriteriaSangram: Workflow Specific CriteriaSangram: Forms specific criteriasangram: ABAP WebDynpro specific criteriaImpacted Functional AreasFinance (FIN)Plan to Produce (P2P)Purchase to Pay (P2Y)e-Requisition (P2Y-SRM)Order to Cash (OTC)Supply Chain Management (SCIPIO)

CalculationRESULTS:Estimation Date:26-Nov-12Development Type Estimated:SAPScript/Smartforms46.0099137931Estimated No. of Hour(s):558.2817844828Complexity:Medium0SAPScript/SmartformsEstimated No. of Day(s):7Classical ReportALV ReportInterface-Outbound (non-ALE)Interface-Inbound (non-ALE)ALE InterfaceConversion (non-LSMW)LSMW ConversionEnhancementSapScript/SmartformsADOBE Print FormsModule PoolWorkflowABAP Web DynproHoursEstimatePercentEstimate for Medium (i.e. 50%) Complexity Development6950%0000000010000Selected ?Development Type Selected :Base LineCurrent EstimationClassical Report610SAPScript/SmartformsSection Applicable ?Baseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageBaseline WeightageApplicable Baseline WeightageBaseline ScoreEffective Baseline ScoreCurrent WeightageCurrent ScoreEffective Current ScoreALV Report610Database AccessYes20%20%30%5%5%5%2%18%20%20%5%5%5%20%142.820%91.8Interface-Outbound (non-ALE)920Selection ScreenYes10%10%5%5%5%5%5%5%5%201.05%50.3Interface-Inbound (non-ALE)920Programming LogicYes15%15%20%20%15%20%8%20%20%20%30%20%20%20%255.020%91.8ALE Interface920Report Display (Gereral) OptionsNo10%10%0%70.00%00.0Conversion (non-LSMW)840ALV Report Specific CriteriaNo20%0%80.00%00.0LSMW Conversion310Classical Report Specific CriteriaNo20%0%90.00%00.0Enhancement610BDC ProcessingNo15%15%10%0%100.00%00.0SAPScript/SmartformsSAPScript840BAPI / Function Module ProcessingYes5%5%5%15%10%15%10%2%5%5%5%5%5%60.30%00.0SAPScript/SmartformsSMARTForms69YFile HandlingNo10%10%10%10%0%140.00%00.0ADOBE Print Forms800Field MappingNo10%10%10%10%0%60.00%00.0Module Pool1070ALE/EDI ProcessingNo40%0%360.00%00.0Workflow910LSMW Specific CriteriaNo30%0%140.00%00.0ABAP Web Dynpro1040Enhancement specific criteriaNo40%0%150.00%40.0SAPScript/Smartforms specific criteriaYes30%30%3811.430%175.1ComplexityFromToADOBE Print Forms specific criteriaNo35%0%250.00%00.0Very Low0.00%20.00%Module Pool Specific CriteriaNo40%0%260.00%00.0Low20.00%40.00%Workflow Specific CriteriaNo50%0%250.00%00.0Medium40.00%60.00%