JDB3100011 - Failed to get location of table F989999 for environment DV900

[jimjung27]

I am running a UBE that imports data from a flatfile into the F0911Z1. For this one file import, I run locally and 50% of the time I get wrong data in some of the fields. The data looks ok but the values don't match the values in the flatfile.

I run the same flatfile import over and over and purge the F0911Z1 after each run. About 50% of the time, I get the wrong field values in 10% of the records. It appears to be some kind of phantom data from I dunno where.

I looked up this log error online and on the Oracle site and everyone is pointing to an OCM setup problem.

Our techinical staff say that this is not the problem and the error that I'm getting is a known error that doesn't relate to my issue.

4672/3356 WRK:Starting jdeCallObject Thu May 17 09:31:12.447002 Jdb_utl1.c12075
JDB9900603 - Failed to open table F989999

4672/3356 WRK:Starting jdeCallObject Thu May 17 09:31:19.384009 Jdb_omp1.c598
JDB9900245 - Failed to find F98611 OneWorld Local - DV900 in cache

4672/3356 WRK:Starting jdeCallObject Thu May 17 09:31:19.385001 Jdb_rq1.c2006
JDB3100011 - Failed to get location of table F989999 for environment DV900

Oracle says:

JDB3100011 - Failed To Get Location Of Table F98752 For Environment

Solution
Verify that you have an active OCM mapping for the table listed in the error. If you do not have an active OCM mapping for table F983051 you will need to add one with the following values:

Parameter Value
Environment Name DEP7333
Object Name F983051
Primary Data Source OneWorld Local
System Role *PUBLIC
Object Type TBLE
Data Source Mode P
Allow QBE 1

After adding the mapping in OCM you will need to bounce OneWorld/EnterpriseOne services.

 

[Adrian_Chimirel]

We need more details on your spooky UBE.
Attach your ER, explain how do you run, what is your configuration (see mine), ... come on Jimmy, you can do it!

 

[jimjung27]

Yes. It is kinda spooky but I re-ran an end-to-end test exporting the data from one environment and then importing the new CSV fomatted flatfile into this environment and it worked fine. The mystery data the shows up maybe from the CSV data. Anyways, I attached the log in the first post. Here's the ER code. Disregard all the Unique key errors in the jde.log. That's just me writing data into a work file over and over again to get a DISTINCT list of EDI batch numbers.

NEW idea! I coded a call to run the R09110Z post after in the END Section. This post updates field values in the F0911Z1 record after the fact. E.G. CRCD, PN, ICU, etc. Is it possible that it is updating the Company Numbers and supplying the mystery data field values. This kinda makes sense because there no funny data. It's all good, just not what's in the CSV formmated file coming in.

 

[jimjung27]

Confirmed early this morning that the R09110Z post was indeed overriding the data in the F0911Z1. This is a data problem and it is off to the Business Analysts. The import UBE works.