JD Edwards EnterpriseOne System Tables: F0092, F9860, F9861, F983051 and More
This is the list of JD Edwards EnterpriseOne 9.2 system tables that CNC administrators and developers query most: user and environment tables, OCM and data sources, Object Librarian, versions, job control and security. Each row gives the key columns and the practical question the table answers.
| Table | Name | Table class / data source | Key columns | Use it to find |
|---|---|---|---|---|
F0092 | Library Lists - User (user profile) | System | ULUSER | A user's role/group (ULUGRP), address number (ULAN8), user type and fast path flag. Maintained in User Profiles (P0092). |
F00921 | User Display Preferences | System | ULUSER | Language (ULLNGP), date format, decimal and date separators, country and time zone preferences. |
F0093 | Library List Control | System | LLUSER, LLLL | Which environments (library lists) a user or role can sign on to, and their sequence (LLSEQ). |
F0094 | Library List Master File | System | LMLL | Environment list with descriptions (LMDL01). |
F00941 | Environment Detail - One World | System | LMLL | Path code (LMPATHCD) behind each environment, e.g. which path code PY920 uses. |
F00942 | Object Path Master File | System | EMPATHCD | Path codes with release (EMRLS), deployment server share path and the central objects data source (EMDATS). |
F98611 | Data Source Master | System (servers read their copy in Server Map) | OMDATP | Database server, database name, owner and platform of each data source. |
F986101 | Object Configuration Master (OCM) | System (servers read their copy in Server Map) | OMENHV, OMOBNM, OMUGRP, OMSTSO | Which data source an object (table or UBE) maps to for an environment and user or *PUBLIC; active mappings have OMSTSO = AV. |
F9860 | Object Librarian Master Table | Object Librarian | SIOBNM | Object name, description (SIMD), system code (SISY) and object type SIFUNO (APPL application, UBE batch, BSFN business function, TBLE table). The quickest way to get an application's name. |
F9861 | Object Librarian - Status Detail | Object Librarian | SIOBNM, SIMKEY, SIPATHCD | Where an object is checked out or installed: machine (SIMKEY), path code, user, status (SISTCE) and SAR/project. |
F9862 | Object Librarian - Function Detail | Object Librarian | SIOBNM, SIFCTNM | Business function names inside a BSFN source member, with descriptions and data structure template. |
F9865 | Form Information File | Object Librarian | SWFMNM | Form name (e.g. W4210A) to application (SWOBNM) and form description (SWMD). Answers 'which app is this form?' |
F983051 | Versions List | Versions | VRPID, VRVERS | Every interactive and batch version: title (VRJD), last changed and last executed dates, check-out status, processing option data (VRPODATA). |
F98306 | Processing Option Text | Central Objects | Template name, item and language (see your table definition) | Text of processing option tabs and prompts for a template object. The values chosen per version are in F983051.VRPODATA, not here. |
F98950 | User Overrides Table | Central Objects class (check OCM for your mapping) | UOUSER, UOOBNM, UOFMNM, UOIDLST, UOUOTY, UOVERS, UOLNGP, UOSEQ | Saved user overrides such as grid formats and query settings per user, object and form. |
F986110 | Job Control Status Master | System class, mapped to the Server Map data source on enterprise servers | JCEXEHOST, JCJOBNBR | Submitted UBE jobs: user, environment, queue, status (JCJOBSTS), submit date and time, process ID. JCFNDFUF2 usually holds report and version, e.g. R42800_XJDE0001. Status D is done and E is error. |
F00950 | Security Workbench Table | System | FSSETY, FSUSER, FSOBNM, FSDTAI, FSFRDV, FSSY | Every application, action, row, column and processing option security record by user, role or *PUBLIC. Maintained in P00950. |
F95921 | Role Relationships Table | System | RLFRROLE, RLTOROLE, RLEFFDATE | Which roles a user belongs to, with effective (RLEFFDATE) and expiration (RLEXPIRDATE) dates and the default role flag. Maintained in P95921. |
F98OWSEC | One World Security | System | SCUSER | System user mapping (SCSECUSR), password change frequency (SCSECFRQ), last change date, allowed attempts and whether the user is enabled (SCEUSER). Maintained in P98OWSEC. |
F9312 | Security History | System | SHUSER, SHMKEY, SHUPMJ, SHUPMT | Sign-on and security events by user, machine and date/time (event type SHEVTYP, status SHEVSTAT). |
Table class is the object class from the 9.2 table definitions. The actual data source each table reads from is decided by OCM (F986101) for your environment, so always confirm with a query against F986101 before pointing a report at a database. Example: to find which version of R42800 a user ran yesterday, select from F986110 where JCUSER = the user and JCSBMDATE = yesterday's Julian date and read JCFNDFUF2.
Get a read-only CNC query pack
Tell us your tools release and database and we will send tested queries for failed jobs, checked-out objects and OCM mappings.
Optional. The tool and every export work without this. No spam.
How to use it
Start from the question. Need an application's name from a form ID in a log? Use F9865 then F9860. Need to know who has an object checked out? F9861. Need the data source a UBE writes to in PY? F986101 for that environment, object and *PUBLIC, then F98611 for the server and database. Need which version a user ran? F986110. Filter on the key columns shown, and remember that most of these tables sit in the System data source shared by all environments, while F983051 is per path code and F98306 sits with central objects.
Data classes and OCM
Each table belongs to a class: System, Object Librarian, Central Objects or Versions. OCM decides where it physically lives. The System data source holds user, security, environment and OCM tables for the whole installation. Object Librarian tables (F9860 to F9865) are shared by all path codes, which is why F9861 carries the path code. Versions (F983051) and central objects tables live per path code, so DV920 and PD920 each have their own copy. Enterprise and HTML servers read F986101 and F98611 from the Server Map, and the job master F986110 is kept there so all servers see the same job list.
Worked example
A user reports that a nightly R42800 job failed. Query F986110 in the Server Map: WHERE JCUSER = 'JSMITH' AND JCSBMDATE = 126294, ordered by JCSBMTIME. The row with JCJOBSTS = E and JCFNDFUF2 = 'R42800_ZJDE0001' is the failed run; JCEXEHOST and JCJOBNBR identify the log on the enterprise server. Then read F983051 for VRPID = 'R42800' and VRVERS = 'ZJDE0001' to see when the version was last changed and by whom, which is often the real cause.
Gotchas
Do not update these tables with SQL: OCM changes go through the OCM application, security through P00950 and object changes through OMW (P98220), so caches and package builds stay consistent. Julian dates and HHMMSS times apply here too. Column lists change slightly by tools release, so confirm against your own OMW table definition. F98306 contains prompt text only; the values of processing options are stored in a blob in F983051 and are best read through the version itself.
Frequently Asked Questions
What is table F0092 in JD Edwards?
F0092 is Library Lists - User, the user profile table. Keyed by ULUSER, it holds the user's role or group (ULUGRP), address number, user type, menu and fast path settings. Display preferences such as language and date format are in F00921. Both live in the System data source and are maintained in User Profiles (P0092).
What is the F9861 table in JDE?
F9861 is Object Librarian - Status Detail. It has one row per object per machine key and path code, showing who changed it, when, the status code and the SAR or project. CNC admins use it to find where an object is checked out and on which path codes it exists.
Which JDE table has the processing options?
F98306 Processing Option Text stores the prompt text of a processing option template. The values chosen for each version are stored in the processing option data blob (VRPODATA) in the Versions List F983051, keyed by program ID and version. Read values through the version in the application rather than decoding the blob.
Which JDE table has the application name?
F9860 Object Librarian Master holds every object name with its description (SIMD), system code and object type (SIFUNO = APPL for applications). To go from a form name such as W4210A to its application, use F9865 Form Information, where SWFMNM is the form and SWOBNM the application.
If your CNC team wants to ask questions like 'which jobs failed last night and which versions changed' in plain English on your own servers, we can wire that up over these system tables, read only.
Related Tools
JD Edwards Security Tables and Security Types Reference (F00950, F95921, F9312)
The JDE 9.2 security tables with their real columns, plus the Security Workbench security types, what each controls and the precedence rules that trip people up.
OracleJD Edwards EnterpriseOne 9.2 Tools Release History Reference
Tools releases of EnterpriseOne 9.2 with their Release 22 to 26 names, update months, headline tools features and certifications, plus how to check which tools release you run.
OracleJD Edwards CNC Environment Health Check Checklist
A weekly or monthly checklist for JDE CNC admins covering servers, web tier, database, batch processing, security and backups.
OracleJD Edwards UBE Runtime Log Worksheet
Record each UBE run with its version, records processed and runtime, and see throughput per second so slow versions stand out.
More Oracle tools
See all- JD Edwards EnterpriseOne Private AI Layer Blueprint Generator
- JD Edwards EnterpriseOne AI Assistant Sizing and Value Calculator
- JD Edwards F4211 vs F42119 Sales Order Detail and History Columns Reference
- JD Edwards Inventory Tables Reference (F41021, F4111, F4105, F4108, F4100)
- JD Edwards AAI and DMAAI Reference (F0012, F4095)
- JD Edwards AP and AR Ledger Tables Reference (F0411, F0413, F0414, F03B11, F03B13, F03B14)
- JD Edwards Sales Order Status Codes and Order Activity Rules Reference (F40203)
- JD Edwards EnterpriseOne 9.2 Upgrade Retrofit Effort Calculator
- JD Edwards Orchestrator Error Handling and Production Readiness Checklist
Keep exploring
Free tools
- JD Edwards EnterpriseOne Core Table ReferenceSearchable list of the JD Edwards EnterpriseOne tables you query most often, with column prefix and the key fields to filter on.
- JD Edwards System Codes ReferenceLook up what each JD Edwards system code stands for and how it shows up in table, application and UDC names.
- JD Edwards EnterpriseOne AI Assistant Sizing and Value CalculatorEstimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on JD Edwards EnterpriseOne.
ERP fixes and how-tos
- JD Edwards business function (BSFN) errors: how to diagnose themJD Edwards business function errors range from missing package builds to unhandled C exceptions. Here is how to isolate which BSFN failed and why, using jde.log and Object Librarian.
- How to Add a Private AI Layer to JD Edwards EnterpriseOne On-PremAdd a private AI layer to JD Edwards EnterpriseOne: AIS data service, Orchestrator, Security Workbench mapping, a local model and human approval.
- JD Edwards table conversion: how it works and how to run oneWhat a JD Edwards table conversion does to a JDE table's structure and data, when it runs in a package build, and how to run or design one manually.
Runs with your ERP
- RF-SMART and JD Edwards EnterpriseOne: Barcode Scanning and Mobile WMSHow RF-SMART connects barcode scanning to JD Edwards EnterpriseOne and World: integration method, data flows, setup steps, pitfalls and where private AI helps.
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- Oracle CPQ and JD Edwards EnterpriseOne: quote to sales orderHow Oracle CPQ integrates with JD Edwards EnterpriseOne: customer data into quotes, sales orders created from quotes, and status back, with setup and pitfalls.
AI on your ERP
- AI for JD Edwards EnterpriseOne Manufacturing, Without Leaving the F-Tables ExposedGrounded AI over JD Edwards EnterpriseOne Manufacturing: work orders, routings, and Orchestrator data, answered on-prem without sending F-table data to a public model.
- AI for JD Edwards Inventory Management and Shop Floor ManufacturingAI on JD Edwards EnterpriseOne inventory and manufacturing: item ledger, work orders, MRP messages and cost variances, answered in plain English on your own servers.
Integrations
- How to add AI agents to JD Edwards EnterpriseOneHow to add AI agents to JD Edwards EnterpriseOne: Orchestrator and AIS as the tool layer, read-only first, human approval on writes, on-prem models.
- How to add an AI chatbot to JD Edwards EnterpriseOneAdd an AI chatbot to JD Edwards EnterpriseOne: grounded in ERP data via AIS, for planners, buyers and customers, and able to run fully on-prem.