To backup a table:

create table tablename_backupdate as select * from existingtablename

To hold queues:
UPDATE SY920.F986130 SET QCQUSTS='02';

To hold queue in particular server:

update SY920.F986130 SET QCQUSTS = '02' where QCEXEHOST in ('ljdeente2');

To limit the number of rows(ex 10) in a particlar table(F0911) in particluar

data(PRODDTA)
SELECT * FROM PRODDTA.F0911 WHERE ROWNUM <= 10;

Below are SQL statements that can be used to Pause and Resume the E1 Job Scheduler:
--*** PAUSE SCHEDULER ***
update sy900.f91300 set SJSCHCTCD01='011' where sjschjbnm='*SCHEDULER'
--*** RESUME SCHEDULER ***
update sy900.f91300 set SJSCHCTCD01='111' where sjschjbnm='*SCHEDULER';

SQL to get a list of E1 Roles and their descriptions:

SELECT AUUSER, AUROLEDESC FROM SY900.F00926

To redeploy a full package and all the update packages associated with the
pathcode. So, I used the SQL below to do the job:
update sy900.f98825 set upinpkst=20 where upmkey='DEV_CLIENT_NAME' and
uppathcd='PATHCODE' and upjdepkgnm 'PACKAGE_NAME'

Following SQL can be used to add an JDE EnterpriseOne environment to every role or
group in your installation:
INSERT INTO SY910/F0093 (LLUSER,LLLL,LLSEQ,LLMNI) SELECT ULUSER, `PD910`,`1.00`,'
FROM SY910/F0092

INSERT INTO SY900/F986101( OMENHV, OMOBNM, OMDATP, OMUGRP,OMOAPP, OMDATM, OMSY,

OMSTSO, OMPID, OMFUNO, OMUSER, OMJOBN, OMOCM2, OMUPMJ, OMUPMT) (SELECT OMENHV, '',
OMDATP, OMUGRP, OMOAPP, OMDATM, OMSY, OMSTSO, 'SQL', OMFUNO, '', '', OMOCM2,
<6DIGITDATE>, <6DIGITTIME> FROM SY900/F986101 WHERE OMOBNM='')

When using this SQL you will need to replace the following:
– The target object to which you would like to copy the records.
– (optional) The UserID that you would like to credit making this change.
<6DIGITDATE> & <6DIGITTIME> – (optional) The JDE Date and Time that you are making
the change.
– The ObjectID of the OCM record that you wish to copy.

This method can also be used to copy OCM records from one environment to another by
setting the environment in the select statement and where clause.

Add Environments To User Or Group Using SQL

insert into sy900/f0093 values('48APINQ','JDV900','3.00','')

Find out all checked out objects using SQL

select * from ol900/f9861 where sistce=3
Recently we encountered an error "Terminal Server Not Authorized" and was unable to
design in OMW on deployment server (Citrix). All services to Terminal server got
disabled.

After some research found that under [Debug] in jde INI file there should be a
entry
OWDeveloper=TRUE.

After adding above entry all the OMW buttons like "Get", "Design" were enabled
back.

Path Code
Question1: In which format EnterpriseOne Specs get stored for a path code?
Answer1: Prior to 8.12, specs were stored in TAM (Table Access Management) format.
In the 8.12 release and later, this metadata is now stored in XML format in an XML
schema in the relational database. This change allows all servers to view and match
their code up to one central source.

Question2: How to create central objects for custom path code?

Answer2: One can create using either of the two methods:

1- Using Platform Pack Installation: Installing the platform pack selecting only
the EnterpriseOne DB components. Once done with the platform pack, one need to
create F983051 manually and need to update the table with the name of your
Deployment server and path code name.

2- Runing R98403, version XJDE0019.This is automatically copy F983051 and updates

the table with the name of your Deployment server and path code name.

Question3: How to create check-in location for custom path code?

Answer3: Check-in location can be created in two ways:

1- Manually copying the directory structure on your deployment server and create a
folder with the same name as your custom path code under EnterpriseOneE812. Copy
the contents depending on whether you creating the path code at all new or copying
it from existing one. In case of copy, make sure to copy it from Pristine.

2- Running the UBE R9800942, Version XJDE0001. Please run the UBE LOCALLY.

Question4: In 8.12, why copying path code will not copy the packages?
Answer4: This is because specifications for packages are now stored in the XML
format in the database. The names of the tables are same as the name of the
package.

Question5: Is there any UBE or method to create the path code in the Enterprise
Server automatically?
Answer5: The only way to get a path code onto the enterprise server is by manual
copy the path code and updates the spec.ini. This file tells the server where to
look for the XML specifications.

Question6: How to delete a Path Code?

Answer6: To delete a path code, you need to perform the following:

1. Delete the record from the table F00942.

2. Delete the central object tables.
3. Manually delete the check-in location on the deployment and path code directory
on enterprise servers.

Question7: Is there any business function to retrieve the path code?

Answer7: The business function B989400 “Get Pathcode for an Environment” can be
used to retrieve the path code.

Question8: Can multiples Data Dictionaries be used for a single path codes?
Answer8: GCS do not recommend setting up separate data dictionaries.
Please refer to the solution for further details: E1: DD: Use of multiple DD for
single path code Note 631426.1

Data Sources
Question1: What are data sources and where definition gets stored?
Answer1: The data sources define where the database tables reside and where the
software runs logic objects for the enterprise. Data source definitions are stored
in the Data Source Master table (F98611). Workstations use a Common table F98611,
which generally resides in the system data source on the enterprise server.
Oracle’s JD Edwards

EnterpriseOne servers that process logic and request data require their own unique
definitions for data sources; therefore, they have their own table F98611 in the
server map data source.

Note: EnterpriseOne having two types of data sources: Database Data Sources and
Logic Machine Data Sources. First DB and second one by SVR are marked in the OMOCM1
column of the table F98611.

Question2: Are all data sources Unicode complaint?

Answer2: EnterpriseOne now ships with all data sources in Unicode except for
Business Data and Control tables. These data sources can be converted to Unicode on
an upgrade.

Note: There are 12 primary types of data sources that can be configured with
EnterpriseOne. There are more than 4500 tables within a normal installation of
EnterpriseOne (8.12) that qualify as business data.

Question3: Would you need to add new data dictionary, object librarian, system,
server, server map, local, or logic data sources?
Answer3: No. These data sources are all shared data sources throughout the
EnterpriseOne implementation. Because of this, under a normal EnterpriseOne
configuration, these data sources contain data that is shared among all the
environments.

Question4: What do you mean by ‘OCM Data Source flag’?

Answer4: It indicates that the data source contains atleast F98611 and F986101
tables. The system and all server map data sources use this flag. This flag
determines whether the data source is shown in the Machine Search_Select form of
the P986115 application.

Question5: What do you mean by ‘Data Class’ while defining the data source?
Answer5: This defines the type of data that will be held in the data source being
defined. This new field helps provide better data selection for Universal Batch
Engines (UBEs) and servers to further identify what kind of data a data source is
referencing.

Note: The classes of data available are: Business Data, Central Objects, Data
Dictionary, Logic, Host Server Map, Local, Object Librarian, Installation Planner,
System, Control Tables, and Versions.
Question6: Are tables with identical name within the same database is supported by
EnterpriseOne?
Answer6: Only two of the four supported RDBMSs support table owners (SQL Server and
Oracle). These databases allow you to have tables with identical names within the
same database differentiated by the owner. Use of this system allows you to keep
multiple copies of some tables (such as F986101 OCM) in the exact same location.

Note: The Object Owner ID field indicates the table owner for that specific data
source. You can have multiple data sources with identical table owners, depending
on your specific setup. This field is used when EnterpriseOne structures the SQL
statements that return data to the EnterpriseOne applications.

Question7: How to split business data in multiple data sources?

Answer7: The data class is at the center of automatic OCM generation. It
categorizes the type of data stored in data sources and tables. For example,
Business Data is data class ’B’ and System is data class ’S’. If you want to split
business data into multiple data sources, you need to create a new data class,
modify the data source template (so Environment Director or Installation Planner
prompts for a data source) and assign tables and GT objects to that data class. OCM
will be created based on the information provided previously.

You can create a new data class by adding a value to the H96/DU UDC for data
sources and H96/CL UDC for table and GT objects.

Note. Modifying the data class does not affect existing OCM mappings; the data
class is only used when creating mappings for a new environment.

OCM
Question1: What are the parameters comprise the primary, unique index to the OCM?
Answer1: Here are the parameters:
Environment
User, which is either a specific User ID / Role or *PUBLIC.
Object name
Database path
Question2: How to delete OCM and how deletion comes into effect?
Answer2: While in Work with object mappings, highlight the desired OCM record and
click the Delete button on the toolbar. This will remove this record from the
F986101 table.

Note: If you remove a mapping from the system data source, your client machines
will need to log out and back into E1 before they will be able to see the change.
If you change a server map F986101 entry, you will need to stop and start your host
services to ensure that the mapping takes effect. You will also need to clear the
cache for the HTML clients via SAW/Server Manager (8.97) or by stopping and
restarting the Web Services (WebSphere or OAS).

Question3: Is it possible that different batch servers’ points to the same F986110
so that WSJ can show all the jobs submitted to different servers?
Answer3: Yes, by keeping the object owner different for all the server map data
source, so that all point to table object_owner.F986110.

Question4: While making any changes in OCM, what would be recomendation, log on to
a client machine or deployment server?
Answer4: To add an OCM mapping, log on to a client machine. The reason you are
logging on to a client machine is that it will update the system F986101. When you
log on to the deployment server in the planner environment, it will change the
F986101 contained in the planner MSDE or SSE database. Since this is not the
database accessed by your end users for mappings, you normally do not want to
change your mappings in this database.
Question5: Is it mandatory to make changes in both System and Server Map while
making changes to OCM?
Answer5: Generally, you need to choose a system to change a mapping for your client
workstations. However, if you think changes are required, then changes should be
made to server map.

Note: If you change the mappings for your users in the system data source, but not
the server map data source, you may see different results when running reports
locally compared to reports run on the server.

Question6: What R986101A (Create System Table Mappings) does?

Answer6: This program adds active Object Configuration Manager (OCM) records for a
specified table, user ID, and data source for all environments listed in the
Environment Detail table (F00941). You can use data selection to filter the
environments to which this process adds OCM records.

Question7: How to Create OCM Records for Business Functions using R98640?
Answer7: This batch process (R986140) reads the Object Librarian tables for server
business functions, and then creates Object Configuration Manager records for those
business functions in the target data source that you specify in processing
options. Processing options also enable you to specify the source data source and
environment to use when creating these Object Configuration Manager records.

Please refer to E1: ENV: EnterpriseOne 8.9 OCM Mappings for Business Functions
Invalid <> for further details.

Question8: How many copies of F986101 can exist in EnterpriseOne installation?

Answer8: There can be many copies of this table on an EnterpriseOne system. The
workstations will use one copy, in the system data source, to find their data. The
enterprise and logic servers have their own copy of this table, which is used when
a report is run on an enterprise or logic server.

The F986101 table really only consists of what is called OCM mappings. These
mappings tell the system what data source the table resides in, where to run its
business functions, and how to process its reports.

Question9: How to generate server map for newly created environment?

Answer9: You need to generate server map using the application P9654A.

Please refer to E1: ENV: Created a new environment and have no OCM mappings in the
Server Map <>.

Environment
Question1: What is an Environment?
Answer1: An environment can be described as the framework on which the system
rests. This framework is made up of object configuration mappings and a path code.
These are what tell EnterpriseOne where to find the data and specification files
needed for its applications to run.

Question2: How to delete an Environment?

Answer2: When you are in the Environment Master program, P0094, highlight an
environment and click the Delete button on the toolbar. This will remove the
records for the Environment from F0093, F0094, F00941, and F986101.

Note: When you delete an environment, you are not automatically deleting the data
sources and business data associated with that environment. This will need to be
done as a separate step.
Question3: What is the recommended way of Environment Creation?
Answer3: While Environment Director is a useful tool for creating environments, we
recommended using Installation Planner (P9840) and Installation Workbench (P9841)
to create custom environments.

Question4: What environment director will do?

Answer4: Environment Director performs the following:
Creates OCM if it does not already exist.
Writes F98403 record for the new environment.
Loads business data.
Loads control tables.
Configures enterprise servers.
Creates server map OCM.
Creates server map F98611 records.
Writes F9651 records for enterprise servers.
Configures BSFN and UBE mappings.
Note: you can refer to E1: ENV: How To Create Custom Environment Using Environment
Director (P989400)? (Doc ID 847534.1) for complete process.

Question5: What would be the recommendation: Create custom environment using plan
or Environment Director?
Answer5: It is recommended that you create custom environments from the PSFTPLAN
environment on the deployment server using Environment Director. Doing so creates
the environment in the planner databases and deploys it to the system data source.
The environment must exist in the planner databases to apply software updates to
the environment.

Question6: Can we run Environment Director logging to deployment environment?

Answer6: You cannot run Environment Director from the deployment environment. The
deployment environment exists only on the deployment server. It uses the bootstrap
tables (F98611 and F986101) from the Planner; the remainder of the system tables
are in the system data source. This split will cause inconsistencies between the
planner and system definitions.

All the tables used by Object Management Workbench are located in the SYSTEM data
source (e.g.: System – 810). OMW/OL uses the following tables:

1) F98210 – Logging Header

Contains header information including the project, object type, object name, time
stamps, path codes, data sources, locations and action type.

2) F98211 – Logging Detail

Contains detailed information on the errors and error codes for the projects and
objects included in the F98210.

3) F98220 – Project Master

Detailed information on all newly created projects and all default projects.

4) F98221 – Project Users

Includes information on all the users in the EnterpriseOne software, the projects
they are added to and the role numbers they are assigned with.

5) F98222 – Project Objects

This log details all EnterpriseOne objects that are added to Object Management
Workbench projects. It includes the object name and type, the path code and project
name.

6) F98223 – Allowed Actions

All the allowed actions assigned to user roles in the Object Management
Configuration (OMC) are detailed in this table.

7) F98224 – Status Activity Rules

Details all project status activity rules.

8) F98225 – Transfer Activity Rules

Details all the object transfer activity rules.

9) F98230 – System Settings

Contains all OMC information other than activity rules and notification
subscriptions.

10) F9829 – Notification Subscriptions