My Oracle Support Banner

E1: DB: Case Study on JDB9900920 - Failed to find index 1 for table F0101 (Doc ID 2296260.1)

Last updated on MARCH 14, 2022

Applies to:

JD Edwards EnterpriseOne Address Book - Version 9.1 and later
JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.


The purpose of this document is to go through the resolution steps for the error below, 

The Representation of Error

Representation in HTML client

Error File can not be accessed. Warning
A form level error has occurred.
CAUSE: ERROR: File can not be accessed.
Solution. . . Change IBM security or authority using the IBM EDTOBJAUT command.
This file can not be accessed with the current IBM authority
for the User executing this request.
ER Details:
  Form P01012_W01012B
  Event Grid Record is Fetched
  Line No 9
BSFN Details:
  Source File b0100033.c
  Source Line 131
  Error ID 3143



  • Above message can be shown only when you click small yellow color triangle on the right edge of error box. Most of time, BSFN Details give you the direct cause of the issue
  • The description of error is originated from World Software, which may not explain the actual cause of it.
  • The cause of error for this example is different from the generic description which error message reads. So check whether issue is happening globally or against specific user(s).


Representation in JDE.log

: this message appears all types of kernel logs because of the nature of F0101 (Address Book Master)

4512/272 WRK:USERID_075BAB68_ProgramID            Thu Aug 10 12:26:50.583000    JDB_RQ1.C781
    JDB9900920 - Failed to find index 1 for table F0101

4512/272 WRK:USERID_075BAB68_ProgramID            Thu Aug 10 12:26:50.584000    JDB_RQ1.C2518
    JDB3100014 - Failed to load requested index


  • The user ID, and ProgramID are changed
  • Index 1 for table F0101 is the primary key of F0101. So this type of error can cause all applications in E1 fails
  • This type of error can be represented only in JDE.log and JDEDEBUG.log which is tracing routine for call object kernel log because the error is coming when a certain request is made using E1 Business Function(s).



Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 The Representation of Error
 Representation in HTML client
 Representation in JDE.log
Troubleshooting Steps
  Clarify Issue
 Analyze C Function (Optional)
 Log Representation

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.