MRO Storeroom & Search

The “Google for MRO parts” in JD Edwards - cross-table full-text search across Item Master, Item Branch and Item Location, with relevance ranking and millisecond response

Maintenance, Repair and Operations storerooms in JD Edwards grow organically over years - and so do the problems. The same physical part exists under three slightly different item numbers. Descriptions are inconsistent. JDE’s built-in search matches exactly, one field at a time, with no relevance ranking and no way to intelligently weight and combine signals from multiple tables in a single query. Technicians spend hours every week hunting for parts they already own.

MRO Storeroom & Search fixes that. It builds a continuously-refreshed full-text index across standard or custom Item Master/Branch/Location and Purchase Orders - every description, every class code (SRP1...SRP9, SRP0), every search-text field, every UDC translation. Type the words you remember; the answers come back in milliseconds, ranked by relevance, with all the JDE context attached.

It installs in minutes, makes zero changes to your JDE configuration, and runs alongside your existing JDE servers without disturbing anything.

Current version: 1.0

  • Product Brief
  • For Storeroom Teams
  • For Procurement
  • For Plant Managers
  • For IT & CNC
  • System Requirements
  • Licensing

The problem. JDE has a wonderful structured database, but its built-in search is rudimentary - exact, case-sensitive matches against a single field at a time, with no relevance ranking and no way to combine signals from standard or custom Item Master/Branch/Location and Purchase Orders in one query. Three users searching for the same part in three slightly different ways will get three disappointing results, even though the right item is sitting in the catalogue.

The solution. MRO Storeroom & Search adds a modern, cross-table full-text search layer on top of JDE, without changing JDE. It continuously indexes standard or custom Item Master/Branch/Location and Purchase Orders.

All these are unified into a single ranked result set, so a query like “Siemens contactor 24V Branch 30” uses all words at once - something JDE’s native search simply cannot do.

The experience. Open a browser, type the words you remember - a description fragment, a supplier name, a class code - and get matching items in seconds, ranked by relevance, with their JDE context and available quantity. Click through to JDE for the full record.

Scope, honestly. This is a Phase 1 release with a deliberately tight scope: it is a literal-text search engine over JDE structured tables. It finds the words you typed, anywhere those words appear in the indexed fields. It does not, on its own, equate 1/2″ with 0.5″, or 3/4″ with 19 mm - it indexes the strings JDE stores. And it does not yet index the content inside Media Object attachments (PDFs, drawings, RTF notes); that is on the Phase 2 roadmap - see the “For IT & CNC” tab.

Why it matters. Customers immediately see three measurable wins:

  1. Faster repairs: technicians find parts in seconds, not minutes - directly reducing unplanned downtime.
  2. Lower inventory: duplicate item creation drops sharply when buyers can find what they already own - especially when the original description used different word order, or the distinguishing detail sits in an SRP class code or UDC translation that JDE’s native search never includes into a single query.
  3. Better data hygiene: the act of indexing itself surfaces inconsistencies that quietly accumulated for years - and our reports help you clean them.

For Storeroom & Maintenance Teams

You know the part. You can describe it. You just can’t find it in JDE.

Maybe the description sits in one table with the words in a different order from the way you searched. Maybe the manufacturer is in different table and the bin is in a yet another table, and JDE’s native search can’t consider all of them at once. Maybe the part exists under three slightly different item numbers, and the one you need isn’t the one you first picked. Standard JDE search can’t help with any of that.

MRO Storeroom & Search lets your technicians:

  • Search across everything that’s indexed in one query - loose phrases, partial part numbers, supplier names, class codes, UDC descriptions - wherever those terms appear in the indexed fields across the database.
  • Get relevance-ranked results - the most likely match comes first, not just the first one alphabetically.
  • See on-hand quantity and bin location instantly - no need to flip to another JDE program.
  • Search from anywhere - PC, tablet, shop-floor kiosk, mobile.

It is a literal-text search engine: searching for 0.5″ finds records that contain 0.5″, not records that say 1/2″. The shared-vocabulary discipline that any storeroom benefits from still applies - this product rewards it by combining every indexed field into a single ranked query, which JDE’s native search simply does not do.

The net effect: a technician who used to spend half a shift each week hunting for parts gets that time back - and an asset that was about to be rebought from a supplier turns up on Shelf B-3 in Branch 30.

For Procurement & Finance

Duplicate item creation is the silent tax on every long-lived JDE MRO catalog. Without an effective search, buyers create new items because they genuinely cannot find the existing equivalent. Each duplicate locks up working capital, fragments demand history (so reorder points get worse), and weakens your negotiating position with suppliers.

MRO Storeroom & Search helps procurement and finance:

  • Prevent duplicate item creation - a quick full-text search before adding a new item catches existing equivalents that JDE’s native exact-match search misses (because the original description uses different word order, or because the relevant signal sits in a class code, a UDC translation, or a vendor mapping that JDE’s one-field-at-a-time search never combines).
  • Consolidate demand history - cleaner item master means cleaner forecasts and better reorder economics.
  • Free up working capital - less duplicated stock means lower inventory on the books, without service-level risk.
  • Audit your catalog - built-in reports surface clusters of likely-duplicate items and items with poor descriptive content. Use them to prioritize a cleanup, or just to keep new growth tidy.
  • Lower rush-buy frequency - when stock-outs are caused by “couldn’t find what we had”, fixing search fixes the rush-buy too.

Most customers see meaningful inventory carrying-cost reductions within the first year - with savings that comfortably justify the licence on their own.

For Plant Managers

Every minute of unplanned downtime is lost production. If a technician can’t find the right part, the line stays down. It really is that direct.

The slowest step in many MRO repair workflows isn’t the repair itself - it’s locating the part. Search is the bottleneck. Fix the search, and the repair’s mean time to recovery (MTTR) drops with it.

What MRO Storeroom & Search delivers to plant managers:

  • Lower MTTR - measurably faster “identify part → locate part → pick part” cycle. Often a step-change improvement.
  • Less reliance on tribal knowledge - new technicians become productive faster because the catalog becomes navigable to anyone.
  • Better preventive maintenance compliance - PM tasks that quietly slip because “we couldn’t find the consumable” stop slipping.
  • A clear KPI story - we provide simple metrics (searches, click-through rate, top no-result queries) that let you demonstrate ROI and find the next improvement opportunity.

For most plants, a single avoided hour of line downtime per month covers the cost of MRO Storeroom & Search for a year.

For IT & CNC

MRO Storeroom & Search is engineered to drop into a real JDE environment without drama.

Architecture:

  • Standalone Windows service. No third-party JVM, no external Elasticsearch cluster to operate.
  • Reads JDE tables at native database speed. Read-only.
  • Writes nothing back to JDE. Ever.
  • Per-table watermarking ensures the indexer scans only what changed since the last run - minimal load on the JDE database.
  • The index lives in a local cache, in a dedicated folder on the search server. Backup is a single file.

Deployment:

  • No JDE configuration changes. No data dictionary changes. No new tables in JDE.
  • One Windows service per JDE environment is typical. Production-grade install in a few hours.
  • Sized for catalogs of up to several million items on commodity hardware.

Security:

  • Multiple authentication options to choose from.
  • Optional SSO via our XpreSSO® or ESI JDE SSO Suite.
  • All data stays on your infrastructure - no cloud, no telemetry, no data leaving the building.

Roadmap (Phase 2):

  • Media Object content indexing - extract and index text from RTF, HTML, plain-text and PDF Media Object attachments (spec sheets, supplier letters, work-around notes, drawings with OCR-extractable text). Standalone Phase 1 customers will be able to add this without re-indexing the structured tables.
  • Semantic search via a locally-hosted LLM. Still zero data egress - the model runs on the same Windows server, with no cloud dependency.

OS: Microsoft Windows Server 2016 or later (recommended)
CPU: Modern Intel or AMD x64; 4 cores+ recommended
RAM: 8 GB minimum, 16 GB recommended for catalogs over 500,000 items
Disk: 100 GB free (index typically 5–15% of source data size)
System Type: Physical or Virtual
JDE Releases: E812, E900, E910, E920 (x32 or x64)
JDE Tools Releases: ALL / ANY / Independent
JDE Backend Database Platforms: Oracle, MS SQL Server, DB2 (ODBC)
Browser: Any modern browser (Chrome, Edge, Firefox, Safari) on PC, tablet or shop-floor terminal

This software is licensed as a Subscription.
 
Related products:

For data access & integration:
A proper ODBC driver for JDE - ESI JDE ODBC Driver
Expose JDE business functions (BSFNs) as REST endpoints - EveREST2JDE

For identity & SSO:
Optional sign-on for the MRO Search front-end - XpreSSO

All Maintenance & MRO tools:
Maintenance & MRO tools