Server Map Tables

Purpose of Document

What tables belong to the "Server Map" data source (where the object owner is SVM910) in EnterpriseOne release 9.1?

This document follows these simplified definitions:

Enterprise Server = Logic Server + Database Server

Logic in EnterpriseOne = Business Functions + Batch Processes

Object Configuration Master (OCM) enables EnterpriseOne to keep track of where data resides and where logic processing occurs with a combination of Logic Server and Database Server. EnterpriseOne enables you to define two different data sources:

In P986115 (Logical Data Sources) with Data Source Using 'SVR'

In P986115 (Database Data Sources) with Data Source Using 'DB'

The list of tables which belong to Server Map are as follows:

Table Name	Table Description	Used for
F986101	Object Configuration Master	The Object Configuration Manager is the piece of the EnterpriseOne architecture that allows data and logic to be distributed without the user being aware. The OCM mappings tell the system where the table being accessed is located. A member of Bootstrap Table To be cached through JDE service start or through reset cache. So whenever you make any change, reset OCM Cache This table sits in two different data sources: one in SVM910 for server and the other is SY910 for client (system) which follows JDE.INI settings for one from local machine and the other from server Review <Document 944015.1> E1: ENV: Frequently Asked Questions on Caching in EnterpriseOne
F98611	F98611 Data Source Master	The purpose of Data Source Master is: Where to find specific data - Which database and table stores the information? Where to execute logic processes - Will my report be processed on the server or my local workstation? How to communicate with each source of data - Which driver is going to translate the database information? There are two types of middleware to deliver a message in Data Source Master. JDEBASE handles any request for data from a database. JDENET handles all message traffic which includes a request for logic. You can think of JDENET loosely as the logic communications. A member of Bootstrap Table To be cached through JDE service start or through reset cache. So whenever you make any change, reset Data Source Cache This table sits in two different data sources: one in SVM910 for server and the other is SY910 for client (system) which follows JDE.INI settings for one from local machine and the other from server
F986110	Job Control Status Master	Record individual job based on job number stored in F986111 so exehost (Execution Host Name) and jobnbr (Server Job Number) combination makes a unique job. Record can be added either through UBE kernel or Call Object Kernel when a certain business function calls jdeLaunchUBEEx() Note: In case you need to debug this file: When job is submitted through P98305 (Batch Version (in Windows Client)) or P98305W (Batch Version - Web Version) turn on logging for UBE kernel When job is submitted through Call Object Kernel (when a certain routine has jdeLaunchUBEEx()) trace Call Object Kernel log If needed turn on logging for Queue Kernel This table sits in two different data sources: one in SVM910 for server and the other is SY910 for client (system) which follows JDE.INI settings for one from local machine and the other from server
F986111	Job Number Master File	Stores next number for UBE Job Number per machine. This table is made up of two columns JOBNBR (Server Job Number) and EXEHOST (Execution Host Name). When a certain batch job is to be executed (simplified routine of UBE kernel can be): Read F983051 to get version information Get Job Queue from attribute from OBJPKGVARS Look for Job Queue from F986130 with Execution Host and Port Number combination Get next Job Number based on machine name and update it after add 1 Write F986110 and update status to record job status cf., Queue definition is sitting in SY910 and message is sent by: runubexml() runube() ube kernel jdeLaunchUBEEx() --> Queue Kernel --> runbatch
F986113	Subsystem Job Master	This record is inserted through API ubeReport_AddSubsystemRecord() then in submitting subsystem version to where job is mapped, UBE kernel handles data like manual submission by sending message to Queue Kernel. Then Queue Kernel checks available queue to handle any waiting job from Subsystem Job Master Table. Subsystem UBEs pose an opportunity in that they do not end after a full processing cycle. Rather these subsystem jobs are initiated and continually ‘wake up’ to check for activity eligible for processing. As a result they occupy a thread in the job queue to which they are assigned (based on process ID assigned by manual submission); this thread remains occupied until the subsystem job is terminated. Therefore, if the job queue to which this subsystem UBE has been assigned is single threaded, any other job that is directed to the same job queue will remain in a ‘wait’ status until the subsystem job has ended. Due to the nature of this type of job, you should consider creating and assigning a unique job queue for this UBE version.
F98DRPCN	Data Replication Pending Change Notifications
F98DRLOG	Data Replication Change Log
F986114	Auditing Information Data Repository	When UBEAuditing is ON the tables F986114/F986114A are to be populated to audit UBE (and TC) submission in server. F986114 is a header file for F986114A (Audit Repository Detail). These data are to be accessed through WSJ (Work With Server)> (Row Exit) Execution Detail (P986114) * In your purging Job Master Files, purge these tables * If you do not have a parameter UBEAuditing in [UBE] section of JDE.INI file it is considered as '1 - Audit'. Do NOT modify this parameter.
F986114A	Audit Repository Detai	Write audit information detail on a certain UBE Job. Currently AUDTYP is made up of, Indicates the type of autit information (AUDTYP). 01= Processing Option Data 02= Data Selection Data 03= Data Sequencing Data 04= Report Interconnect Data 05= Actual SELECT statement issued Note that Processing Option Data (where F986114A.JDAUDTYP='01) contains both processing option text (F98306) and actual value (F983051) however you may not be able to view whole rows through UTB (Universal Table Browser) or through Databrowser.

Table Name

Table Description

Used for

F986101

Object Configuration Master

The Object Configuration Manager is the piece of the EnterpriseOne architecture that allows data and logic to be distributed without the user being aware. The OCM mappings tell the system where the table being accessed is located.
A member of Bootstrap Table
To be cached through JDE service start or through reset cache. So whenever you make any change, reset OCM Cache
This table sits in two different data sources: one in SVM910 for server and the other is SY910 for client (system) which follows JDE.INI settings for one from local machine and the other from server
Review <Document 944015.1> E1: ENV: Frequently Asked Questions on Caching in EnterpriseOne

F98611

F98611 Data Source Master

The purpose of Data Source Master is:

Where to find specific data - Which database and table stores the information?
Where to execute logic processes - Will my report be processed on the server or my local workstation?
How to communicate with each source of data - Which driver is going to translate the database information?

There are two types of middleware to deliver a message in Data Source Master.

JDEBASE handles any request for data from a database.
JDENET handles all message traffic which includes a request for logic. You can think of JDENET loosely as the logic communications.

A member of Bootstrap Table
To be cached through JDE service start or through reset cache. So whenever you make any change, reset Data Source Cache
This table sits in two different data sources: one in SVM910 for server and the other is SY910 for client (system) which follows JDE.INI settings for one from local machine and the other from server

F986110

Job Control Status Master

Record individual job based on job number stored in F986111 so exehost (Execution Host Name) and jobnbr (Server Job Number) combination makes a unique job. Record can be added either through UBE kernel or Call Object Kernel when a certain business function calls jdeLaunchUBEEx()
Note: In case you need to debug this file:

When job is submitted through P98305 (Batch Version (in Windows Client)) or P98305W (Batch Version - Web Version) turn on logging for UBE kernel
When job is submitted through Call Object Kernel (when a certain routine has jdeLaunchUBEEx()) trace Call Object Kernel log
If needed turn on logging for Queue Kernel
This table sits in two different data sources: one in SVM910 for server and the other is SY910 for client (system) which follows JDE.INI settings for one from local machine and the other from server

F986111

Job Number Master File

Stores next number for UBE Job Number per machine. This table is made up of two columns JOBNBR (Server Job Number) and EXEHOST (Execution Host Name). When a certain batch job is to be executed (simplified routine of UBE kernel can be):

Read F983051 to get version information
Get Job Queue from attribute from OBJPKGVARS
Look for Job Queue from F986130 with Execution Host and Port Number combination
Get next Job Number based on machine name and update it after add 1
Write F986110 and update status to record job status

cf., Queue definition is sitting in SY910 and message is sent by:

runubexml()
runube()
ube kernel
jdeLaunchUBEEx()
--> Queue Kernel
--> runbatch

F986113

Subsystem Job Master

This record is inserted through API ubeReport_AddSubsystemRecord() then in submitting subsystem version to where job is mapped, UBE kernel handles data like manual submission by sending message to Queue Kernel. Then Queue Kernel checks available queue to handle any waiting job from Subsystem Job Master Table.

Subsystem UBEs pose an opportunity in that they do not end after a full processing cycle. Rather these subsystem jobs are initiated and continually ‘wake up’ to check for activity eligible for processing. As a result they occupy a thread in the job queue to which they are assigned (based on process ID assigned by manual submission); this thread remains occupied until the subsystem job is terminated. Therefore, if the job queue to which this subsystem UBE has been assigned is single threaded, any other job that is directed to the same job queue will remain in a ‘wait’ status until the subsystem job has ended.

Due to the nature of this type of job, you should consider creating and assigning a unique job queue for this UBE version.

F98DRPCN

Data Replication Pending Change Notifications

F98DRLOG

Data Replication Change Log

F986114

Auditing Information Data Repository

When UBEAuditing is ON the tables F986114/F986114A are to be populated to audit UBE (and TC) submission in server. F986114 is a header file for F986114A (Audit Repository Detail).
These data are to be accessed through WSJ (Work With Server)> (Row Exit) Execution Detail (P986114)

* In your purging Job Master Files, purge these tables
* If you do not have a parameter UBEAuditing in [UBE] section of JDE.INI file it is considered as '1 - Audit'. Do NOT modify this parameter.

F986114A

Audit Repository Detai

Write audit information detail on a certain UBE Job. Currently AUDTYP is made up of,

Indicates the type of autit information (AUDTYP).

01= Processing Option Data
02= Data Selection Data
03= Data Sequencing Data
04= Report Interconnect Data
05= Actual SELECT statement issued

Note that Processing Option Data (where F986114A.JDAUDTYP='01) contains both processing option text (F98306) and actual value (F983051) however you may not be able to view whole rows through UTB (Universal Table Browser) or through Databrowser.

Notes:

This information can be retrieved (for example from an Oracle Database) using:

SQL> select TABLE_NAME from ALL_ALL_TABLES where OWNER = 'SVM920';

JDE.INI settings in Enterprise/Logic server:

[DB SYSTEM SETTINGS]
Default Env=PD920
Default PathCode=PD920
Base Datasource=YourEntSrv - 920 Server Map
Object Owner=SVM920
Server=yourdbsrv
Database=yoursrv910
Use Owner=Y
...

The Datasource can be acquired by existing table name from UTB when you log into J* Environment (Ex: JPD920) (cf., if you log on Non-J* Environment you may get default Data Source as 'System - 920')
Object Owner in Local JDE.INI is SY920

Did you find this document helpful? If so, please provide your feedback and comments on this document in MOS. Your feedback helps us help you.
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the CNC, DB and Operating System - JDE1 Community.
To look at upcoming or archived Advisor Webcasts, please see the Advisor Webcast JD Edwards EnterpriseOne Schedule <Document 1450327.1>. If your topic is not currently scheduled, please suggest it.

Server Map in EnterpriseOne

Purpose of Document