OracleFree worksheetPDF, Excel, Word exportOracle E-Business Suite

Oracle EBS Custom Code Inventory Worksheet

Every EBS upgrade, migration or retirement starts with the same question: what have we built? This worksheet gives you a structured inventory of custom reports, interfaces, conversions, extensions and forms, with a disposition and a cost estimate for each, so the plan rests on a list instead of memory.

Download:

Object name	Type	Module	Business owner	Runs per month	Disposition	Effort hours (h)	Rate per hour	Estimated cost
								$3,400
								$1,020
								$0
								$5,100
								$6,800

Total effort

192

Total estimated cost

$16,320

Objects listed

Average cost per object

$3,264

Build the starting list from your own instance, for example custom applications in FND_APPLICATION, programs in FND_CONCURRENT_PROGRAMS, and objects named with your custom prefix in DBA_OBJECTS. Adjust effort by object complexity rather than using one flat estimate.

Review your custom code list

Optional review of your inventory to spot objects that standard features or read-only AI queries could replace.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

List one object per row. Pick the type and module, name a business owner, and enter how often it runs. Choose a disposition: keep, rework, replace with standard functionality or retire. Enter effort hours and a rate to get an estimated cost, and read the totals to size your project. Export to Excel and share it with business owners for sign-off on the retire and replace decisions.

Where the inventory comes from

Query your own instance rather than trusting old documents. Custom applications, concurrent programs, value sets, workflows and database objects with your naming prefix are a good starting set. Add personalizations and OAF extensions, which often hide outside the normal object lists. Compare run frequency from the concurrent request history to find objects nobody uses, since those are the cheapest to retire.

Check FND_CONCURRENT_REQUESTS for actual usage
Look for customisations to seeded forms and packages
Include integrations that live outside the database
Flag objects that touch Oracle seeded tables directly

Common mistakes

Teams undercount personalizations, custom triggers and database links. They also assume every custom report must be rebuilt, when many can be replaced by standard reports or BI Publisher templates. Another mistake is a flat estimate per object. A simple report and a heavy interface with custom validation need different numbers, so use hours per row and review the largest few with the developers.

Frequently Asked Questions

What does RICE mean in Oracle EBS?

RICE stands for reports, interfaces, conversions and extensions. Some teams add forms, workflows and personalizations. It is the common grouping used to inventory and estimate custom work in EBS projects.

How do I find all custom objects in my EBS instance?

Combine several sources: custom application tables, FND programs and value sets, DBA_OBJECTS with your naming prefix, workflows, and personalization listings. No single query catches everything, so validate with the functional owners.

How should I estimate effort for each object?

Use hours per object based on complexity: size of code, number of tables, integration points and testing needs. Review the top ten largest items with the developer who maintains them, since they drive most of the total.

Which custom objects can I retire?

Start with objects that have not run in a year or more, duplicates of standard reports, and one-time conversions. Confirm with the business owner and keep the code archived in case an audit needs it.

If the inventory shows a long tail of custom reports, we can talk about answering those questions from read-only ERP data instead of rebuilding each report.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Back to All Tools