# SAP RICEFW Object Inventory and Tracker (Excel Export) > Source: https://netray.co/tools/sap-ricefw-object-inventory-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A RICEFW inventory with build and test hours, owner and status that totals effort for the whole development backlog. ## Category sap ## Erp SAP S/4HANA ## Audience - ABAP development lead - SAP project manager - Functional consultant ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Object ID **Key:** id **Type:** text #### Name **Key:** name **Type:** text #### Type **Key:** type **Type:** select **Options:** - Report - Interface - Conversion - Enhancement - Form - Workflow #### Complexity **Key:** complexity **Type:** select **Options:** - Low - Medium - High #### Build hours **Key:** build **Type:** number **Unit:** h #### Test hours **Key:** test **Type:** number **Unit:** h #### Total hours **Key:** total **Type:** number **Expr:** build + test **Format:** number #### Developer **Key:** owner **Type:** text #### Status **Key:** status **Type:** select **Options:** - Specified - In build - In test - Done - Deferred **Rows:** #### Open PO aging report **Id:** R-001 **Type:** Report **Complexity:** Medium **Build:** 24 **Test:** 8 **Owner:** RDEV **Status:** In test #### Supplier ASN inbound IDoc **Id:** I-004 **Type:** Interface **Complexity:** High **Build:** 60 **Test:** 24 **Owner:** SDEV **Status:** In build #### Open sales orders load **Id:** C-002 **Type:** Conversion **Complexity:** High **Build:** 48 **Test:** 32 **Owner:** RDEV **Status:** Specified #### Delivery block user exit **Id:** E-009 **Type:** Enhancement **Complexity:** Low **Build:** 8 **Test:** 4 **Owner:** SDEV **Status:** Done #### Packing list form **Id:** F-003 **Type:** Form **Complexity:** Medium **Build:** 20 **Test:** 6 **Owner:** RDEV **Status:** In build **Totals:** #### Build hours **Key:** build **Agg:** sum **Format:** number #### Test hours **Key:** test **Agg:** sum **Format:** number #### Total hours **Key:** total **Agg:** sum **Format:** number #### Objects **Key:** id **Agg:** count **Format:** integer **Summary:** #### Average hours per object **Key:** avg_obj **Expr:** sum_total / count **Format:** number **Primary:** true #### Test share of effort **Key:** test_share **Expr:** sum_test / sum_total * 100 **Format:** percent **Notes:** RICEFW stands for Reports, Interfaces, Conversions, Enhancements, Forms and Workflows. The example hours are illustrative; use your own historic actuals to set values by type and complexity. ## Content **Intro:** Every SAP project keeps a list of custom objects, and the list usually lives in Excel. This tracker keeps type, complexity, hours and status together and totals the backlog so the development lead can see load and progress. **Sections:** #### How to use it **Body:** Add one row per custom object once it is identified during fit-gap. Give it an ID with a type prefix, a complexity rating and build and test hours. Assign a developer and update the status as the work moves. The totals and the test share update as you edit. Export the sheet to Excel for the steering committee, or to CSV to load into a project tool. Keep deferred objects in the list so scope decisions stay visible. **Bullets:** - One row per object - Use consistent type prefixes - Update status weekly - Keep deferred items rather than deleting them #### Rating complexity **Body:** Agree the rating rules before estimating. A common approach: low means a standard list with few tables and no posting, medium means several tables, calculations or a form with multiple layouts, high means posting to the ledger or inventory, external systems, high volumes or complex error handling. Interfaces and conversions rank high more often than reports. Write the rules down so estimates are comparable between developers and so you can recalibrate with actuals. #### Common mistakes **Body:** Teams forget test effort and defect fixing, estimate before the spec is stable, and let the list grow without a change control. Another mistake is leaving out reuse: two objects can share a class. Review the list each sprint, compare actual hours to estimate and adjust rating rules. Cutting custom objects through standard SAP, extensibility or configuration is usually cheaper than building. **Bullets:** - No test effort - Estimates before spec - Scope creep with no change control - Not checking standard alternatives **Cta:** If your RICEFW list is long, we can discuss where AI assistance can shorten specification, build and test cycles under your control. **Faq:** #### What does RICEFW mean? **Answer:** It stands for Reports, Interfaces, Conversions, Enhancements, Forms and Workflows. Some projects write RICEF without workflows, or add Authorizations and Analytics. Use the categories your project uses. #### How do I estimate hours per object? **Answer:** Use your own past actuals by type and complexity. If you have none, start with rough assumptions, review after the first few objects and recalibrate. The effort estimator on this site can help with a first pass. #### Should testing be in the same sheet? **Answer:** Yes, as a column, so that test effort is not forgotten. It is common for test and defect fixing to be a substantial share of total effort, especially for interfaces and conversions. #### Can I use it for S/4HANA projects? **Answer:** Yes. Add a column in your own copy for the extensibility approach (key user, in-app, side-by-side or classic) if your project follows clean core rules. ## Search terms sap ricefw list template, ricefw inventory excel, sap ricef tracker, sap development object list, sap custom development tracker, ricefw estimation template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json