# Oracle Fusion Cloud SCM Fit Gap Worksheet > Source: https://netray.co/tools/oracle-fusion-scm-fit-gap-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Log each requirement, classify it as standard, configuration, extension or gap, and total the effort and cost before the design workshops end. ## Category oracle ## Erp Oracle Fusion Cloud SCM ## Audience - Oracle Cloud consultant - Solution architect - ERP project manager ## Tool **Kind:** worksheet **Mode:** editable **Currency:** $ **Columns:** #### Requirement **Key:** req **Type:** text #### Module **Key:** module **Type:** select **Options:** - Inventory Management - Order Management - Procurement - Manufacturing - Supply Planning - Cost Management - Product Information Management - Maintenance #### Fit class **Key:** fit **Type:** select **Options:** - Standard - Configuration - Extension (VBCS/OIC) - Gap - process change - Gap - not supported #### Priority **Key:** priority **Type:** select **Options:** - Must - Should - Could #### Effort **Key:** days **Type:** number **Unit:** days #### Day rate **Key:** rate **Type:** number **Format:** currency #### Estimated cost **Key:** cost **Type:** number **Expr:** days * rate **Format:** currency #### Owner **Key:** owner **Type:** text **Rows:** **Req:** Serial genealogy through work order issue and completion **Module:** Manufacturing **Fit:** Configuration **Priority:** Must **Days:** 4 **Rate:** 900 **Owner:** Mfg lead **Req:** Customer specific ship set labels **Module:** Order Management **Fit:** Extension (VBCS/OIC) **Priority:** Should **Days:** 12 **Rate:** 1000 **Owner:** OM lead **Req:** Standard purchase order approval by amount **Module:** Procurement **Fit:** Standard **Priority:** Must **Days:** 1 **Rate:** 900 **Owner:** Proc lead **Req:** Rework routing with separate cost collection **Module:** Cost Management **Fit:** Gap - process change **Priority:** Could **Days:** 3 **Rate:** 950 **Owner:** Finance lead **Req:** Legacy MRP planner code mapping to planner groups **Module:** Supply Planning **Fit:** Configuration **Priority:** Should **Days:** 2 **Rate:** 900 **Owner:** Planning lead **Totals:** #### Total effort **Key:** days **Agg:** sum **Format:** days #### Total estimated cost **Key:** cost **Agg:** sum **Format:** currency #### Requirements logged **Key:** req **Agg:** count **Format:** integer **Summary:** #### Average cost per requirement **Key:** avg_cost **Expr:** sum_cost / count **Format:** currency #### Average effort per requirement **Key:** avg_days **Expr:** sum_days / count **Format:** days **Notes:** Rates and days are examples. Replace them with your own estimates. Export to Excel to filter by fit class or module. ## Content **Intro:** A fit gap log is the working record of an Oracle Fusion Cloud SCM design phase. This worksheet gives you the columns most teams end up building in Excel and totals the effort and cost as you type. **Sections:** #### How to use the worksheet **Body:** Add one row per requirement, not per workshop topic. Pick the module, then classify the fit. Enter effort in days and a day rate, and the cost column calculates itself. Keep the owner column filled so every open row has a name next to it. Export to Excel after each workshop and circulate the file so the business confirms the classification rather than discovering it at user acceptance testing. **Bullets:** - Write requirements as a testable statement - Classify before you estimate - Review Must items with a gap first - Re-export after every workshop #### What the fit classes mean **Body:** Standard means the delivered offering does it with no setup beyond the normal functional setup. Configuration means setup choices in areas like Manufacturing, Inventory or Order Management cover it. Extension means a build outside the core, typically with Visual Builder Studio, Oracle Integration or BI Publisher, so the quarterly update path stays clean. A process change gap means the business adapts. A not supported gap needs an escalation or a workaround agreed in writing. #### Reading the totals **Body:** The totals show effort, cost and the number of requirements. A healthy log has most rows in Standard and Configuration. If extensions outweigh configuration, challenge the requirement wording, because legacy ERP habits often drive custom builds that Fusion handles through setup. Treat the average cost per requirement as a sanity check against your statement of work, not as a quote. #### Common mistakes **Body:** Teams classify as Standard without testing in a sandbox, then reclassify later. They also hide integration work inside module rows. Give integrations their own rows so the cost of connectors, FBDI loads and REST based interfaces is visible. Finally, do not size the same requirement twice across modules; pick the module that owns the transaction. **Cta:** If your requirements live in a legacy ERP, we can help extract and group them from existing reports and customisations before the design phase starts. **Faq:** #### Is a fit gap analysis the same as a gap analysis? **Answer:** Not quite. A fit gap analysis starts from business requirements and checks each against delivered functionality, then classifies the result. A general gap analysis compares current state to target state. In Oracle Fusion projects the fit gap log feeds scope, estimates and the extension backlog. #### How granular should requirements be? **Answer:** Granular enough that one test case can prove or disprove it. A line like 'handle returns' is too broad. 'Return to vendor with debit memo created from the receipt' can be classified, estimated and tested. Aim for one transaction outcome per row. #### Should every gap get an extension? **Answer:** No. Prefer changing the process or using a configuration option, because extensions need regression testing after each quarterly update. Build only when the business value is clear and there is no supported alternative. #### Can I import this into a project tool? **Answer:** Yes. Export to CSV or Excel and import the rows into your project or backlog tool. Keep the requirement text unchanged so traceability to test scripts and design documents is preserved. ## Search terms oracle fusion fit gap analysis template, oracle fusion scm fit gap excel, oracle cloud requirements traceability, fit gap worksheet erp, oracle fusion manufacturing gap list, oracle cloud implementation estimate, oracle fusion extension vs configuration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json