# ABAP RICEFW Estimation Worksheet: Effort and Cost by Object > Source: https://netray.co/tools/abap-ricefw-estimation-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer List each report, interface, conversion, enhancement, form and workflow, enter hours and risk, and get totals and cost. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP project manager - ABAP developer - SAP technical lead ## Tool **Kind:** worksheet **Mode:** editable **Currency:** $ **Columns:** #### Object **Key:** obj **Type:** text #### Type **Key:** kind **Type:** select **Options:** - Report - Interface - Conversion - Enhancement - Form - Workflow #### Complexity **Key:** cx **Type:** select **Options:** - Low - Medium - High #### Spec hours **Key:** spec_h **Type:** number **Unit:** h #### Build hours **Key:** build_h **Type:** number **Unit:** h #### Unit test hours **Key:** test_h **Type:** number **Unit:** h #### Risk uplift **Key:** risk **Type:** number **Unit:** % #### Hourly rate **Key:** rate **Type:** number **Format:** currency #### Total hours **Key:** total_h **Type:** number **Expr:** (spec_h + build_h + test_h) * (1 + risk / 100) **Format:** number #### Cost **Key:** cost **Type:** number **Expr:** total_h * rate **Format:** currency **Rows:** **Obj:** ZSD_OPEN_ORDERS_REPORT **Kind:** Report **Cx:** Medium **Spec h:** 8 **Build h:** 24 **Test h:** 8 **Risk:** 15 **Rate:** 85 **Obj:** ZMM_SUPPLIER_ASN_INBOUND **Kind:** Interface **Cx:** High **Spec h:** 16 **Build h:** 56 **Test h:** 24 **Risk:** 25 **Rate:** 85 **Obj:** ZFI_OPEN_ITEM_CONVERSION **Kind:** Conversion **Cx:** Medium **Spec h:** 12 **Build h:** 32 **Test h:** 16 **Risk:** 20 **Rate:** 85 **Obj:** ZMM_PO_RELEASE_EXIT **Kind:** Enhancement **Cx:** Low **Spec h:** 4 **Build h:** 10 **Test h:** 4 **Risk:** 10 **Rate:** 85 **Obj:** ZSD_DELIVERY_NOTE_FORM **Kind:** Form **Cx:** Medium **Spec h:** 6 **Build h:** 20 **Test h:** 6 **Risk:** 15 **Rate:** 85 **Obj:** ZPM_NOTIFICATION_APPROVAL **Kind:** Workflow **Cx:** High **Spec h:** 12 **Build h:** 40 **Test h:** 16 **Risk:** 25 **Rate:** 85 **Totals:** #### Spec hours **Key:** spec_h **Agg:** sum **Format:** number #### Build hours **Key:** build_h **Agg:** sum **Format:** number #### Total hours **Key:** total_h **Agg:** sum **Format:** number #### Total cost **Key:** cost **Agg:** sum **Format:** currency **Summary:** #### Average hours per object **Key:** avg_obj_h **Expr:** sum_total_h / count **Format:** number #### Specification share of effort **Key:** spec_share **Expr:** sum_spec_h / sum_total_h * 100 **Format:** percent **Description:** Rough, as risk uplift is excluded from the numerator. #### Elapsed days for a team of three **Key:** days_team **Expr:** sum_total_h / 3 / 8 **Format:** days **Notes:** Replace the example rows with your own inventory. Calibrate hours per type and complexity from completed objects, and keep the risk uplift for unknowns such as unclear specs or unstable interface partners. ## Content **Intro:** RICEFW stands for reports, interfaces, conversions, enhancements, forms and workflows, the custom objects that make up most SAP development effort. This worksheet gives you one editable list with hours, risk and cost per line and totals for the plan. **Sections:** #### How to use the worksheet **Body:** Add one row per object. Choose the type and complexity, then enter specification, build and unit test hours. Add a risk uplift for objects with unclear requirements, new interface partners or fragile data. The sheet computes total hours with the uplift and the cost at the rate you enter. Totals and summary lines update as you edit. Export to Excel to share with the project manager, or to build a resource plan by team member. **Bullets:** - One row per deliverable, not per task - Estimate spec, build and test separately - Keep a consistent definition of Low, Medium and High #### Method and calibration **Body:** Total hours equal spec plus build plus unit test, multiplied by one plus the risk uplift. Cost equals total hours times the rate. Good estimates come from your own history, so after each project compare estimated against actual hours by type and complexity, and update your averages. Many teams define a complexity by the number of tables, interface fields, business rules and test scenarios. Integration testing, data validation by the business and cutover are usually planned outside this list. **Bullets:** - Define complexity by measurable drivers - Update averages after each project - Estimate integration test and cutover separately #### Common mistakes **Body:** The most common mistake is estimating only build time. Specifications, reviews, unit testing, transports and defect fixing during later test cycles often add as much again. Another is treating all interfaces as equal, when a file drop and a real-time IDoc or API integration with error handling differ by a large factor. Finally, estimates usually miss the stability of the source requirement. If the business has not agreed the process, raise the risk uplift or hold the object until it is stable. **Bullets:** - Include defect fixing and transports - Split interfaces by pattern and error handling - Raise risk for unsettled requirements **Cta:** If you want a second opinion on a RICEFW list before it goes into a statement of work, Netray can review it and flag objects that look underestimated. **Faq:** #### What does RICEFW mean? **Answer:** Reports, Interfaces, Conversions, Enhancements, Forms and Workflows. Some teams write RICEF without workflow, or add a W for widgets or workflow. It is a classification of custom development objects in SAP projects. #### How do I estimate complexity? **Answer:** Use measurable drivers such as number of source tables, fields mapped, business rules, volumes and test scenarios. Agree on thresholds with the team so Low, Medium and High mean the same thing to everyone. #### What risk uplift is reasonable? **Answer:** Ten to thirty percent covers most objects. Use more for objects with unclear scope, unfamiliar technology or external partners you do not control. Document the reason for every high uplift. #### Does this include functional configuration? **Answer:** No. It covers custom development objects. Configuration, training, cutover and integration testing are typically estimated in separate workstreams. ## Search terms ricefw estimation template, sap ricefw list excel, abap development effort estimate, sap object estimation worksheet, ricef inventory template, sap technical estimate template, sap development estimate by complexity, abap project estimate excel --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json