Hubble Configuration Form JD Edwards World & EnterpriseOne

Desktop Reporting(Edition 1)

Version 2016.1

Document Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i

Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i

Chapter 1 - Hubble Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Repository - Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Repository - Database Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Repository – Database Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2 - JD Edwards Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Summary Overview of JD Edwards Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . 3 JD Edwards Database Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 JD Edwards – Database Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Database User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Temporary Table Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

DB2 UDB for LUW Only - Temporary Table Prerequisite . . . . . . . . . . . . . . . . . . . . . . .4 JD Edwards Database Configuration Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 JD Edwards Table Locations and Data Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

User Defined Code Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Security Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Data Dictionary Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

JD Edwards Configuration Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Model Business Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Subledger Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 3 - Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Creating Hubble Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Chapter 4 - Designer Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

JD Edwards Database Connectivity – Object Librarian Tables . . . . . . . . . . . . . . . . .10

Chapter 5 - Reconciliation Integrity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

JD Edwards Table Index Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

i

Document Information

Notices

Copyright

Hubble® is a brand name of the insightsoftware.com Group. insightsoftware.com is a registered trademark of insightsoftware.com Limited. Hubble is a registered trademark of insightsoftware.com International Unlimited.

Other product and company names mentioned herein may be the trademarks of their respective owners. The insightsoftware.com Group is the owner or licensee of all intellectual property rights in this document, which are protected by copyright laws around the world. All such rights are reserved.

The information contained in this document represents the current view of insightsoftware.com on the issues discussed as of the date of publication. This document is for informational purposes only. insightsoftware.com makes no representation, guarantee or warranty, expressed or implied, that the content of this document is accurate, complete or up to date.

DisclaimerThis guide is designed to help you to use the Hubble applications effectively and efficiently. All data shown in graphics are provided as examples only. The example companies and calculations herein are fictitious. No association with any real company or organization is intended tor should be inferred.

Version History

Date Revision Software Version Comments

27th June 2016 1.0 2016.1

Customer Support

For more information regarding our products, please contact us at http://gohubble.com/.

For product support including Training, Documentation and Customer Support, visit our Hubble Community at https://community.gohubble.com/.

Chapter 1: Hubble Repository Configuration

Repository - Purpose

This repository will store information for Hubble such as:

● Hubble users● Pre-built templates for each module purchased● Hubble reports created by users

The size of the Object Repository is difficult to estimate because it varies from site to site and is based on the number of users, modules and inquiries that the users generate. Typically the database created to store the Hubble repository is set to 500MB to start with auto growth defined.

Repository backups should be performed according to your company’s backup policy. When using Hubble in a production environment, we recommend following your company policy regarding backup and restore plans for failure recovery. Backups can be performed at the database level or using our backup utility available within the Hubble Administrator application.

Repository - Database Platforms

Create an empty database, library or schema for hosting the Repository component of Hubble. This can be created in SQL Server, Oracle, or AS/400 DB2. If you are using AS/400 DB2, you will need to create the library in iSeries Navigator and ensure the library is created with the SQL Collection Option activated.

Repository – Database Permissions

You will need a user name and password with read/write access to a newly-created database for hosting the Repository; therefore it is necessary to make this user a Database Owner (dbo) of this database\library\schema. The database script will create the user and assign the required privileges. The specific permissions/roles necessary within the dbo authority are:

● Create Table/Index (only needed once when repository is created)● Insert/Update/Select/Delete permissions OR Read/Write permissions

Page 1

Hubble Repository Configuration | Repository – Database Permissions

REPOSITORY – DATABASE INFORMATION

What database vendor will host the repository, e.g. Oracle, AS/400 DB2, SQL Server?

Which version of the database are you running, e.g. SQL Server 2008, Oracle 10g? If AS/400 DB2, which version of the operating system is running, e.g. V5R4?

What is the server name which will host the Repository?

If the database is Oracle, what is the Port Number used to connect?

If the database is Oracle, what is the Service Name (SID Name)?

What is the name of the database/library/schema that will be created for the Repository?

What is the database user account name that you will use to connect to the Repository?

Page 2

Chapter 2: JD Edwards Database Access

Summary Overview of JD Edwards Database Access

Hubble requires access to the following JD Edwards Tables for the purposes outlined below:

1. The Data Tables within JD Edwards – Hubble needs the ability to retrieve data for report writing purposes.

2. The Security Tables within JD Edwards – Hubble reads your JD Edwards Security defined if you select to use JD Edwards Security in the Profile Wizard.

3. The Data Dictionary Table within JD Edwards – Hubble requires the ability to read the Data Dictionary to capture data characteristics for display purposes within the product.

4. The UDC tables within JD Edwards – Hubble will use the UDC Table data primarily for filter visual assist selection; however, this data is also a powerful tool used in building reports.

JD Edwards Database Platforms

Hubble supports the following platforms that host the JD Edwards Database, Library or Schema:

1. DB2 UDB for System i (formerly known as iSeries or OS/400)

2. DB2 UDB for LUW (Linux, Unix, Windows)

3. Oracle 10i

4. SQL Server 2003 and above

5. Attunity Connect 5.3.0 and above (used in OPTIM Integration)

Oracle database servers prior to 10.2.0.3 contain a fault which limits how many joins they can handle. This issue has been reported in Oracle [ID412362.1]: ANSI Left Outer Join Returns ORA-1445. Please contact Oracle if you are on database 10.2.0.3 or prior to obtain the hotfix.

Page 3

JD Edwards Database Access | JD Edwards – Database Permissions

JD Edwards – Database Permissions

Database User Identify a user name and password that has at least read access to the following ERP data with the ability to create temporary tables (see Temporary Table Permissions note below):

1. The Data Tables within JD Edwards

2. The Security Tables within JD Edwards

3. The Data Dictionary Table within JD Edwards

4. The UDC Tables within JD Edwards

Temporary Table PermissionsThe user name must have create and write permissions for the Temporary Tables database. Write access is exclusively used for Temporary Tables that supports the below features used within Hubble.

● Hierarchies● Security ● Subledger Joins ● Query Optimization

We do not write to any JD Edwards Tables. (The only exception to this is in Strategic Planning. For more information on Planning, refer to that section of this guide.)

At the very minimum, the user name defined for the JD Edwards Connections MUST have read permissions and create permissions for the Temporary Tables System Database.

DB2 UDB for LUW Only - Temporary Table Prerequisite

As of release 2012.2 SP1, there is a temporary table prerequisite for those using DB2 for LUW (UDB). (Customers with DB2 for iSeries do NOT need to perform this step.)

Creation of a GLISPACE Table Space

Previous versions of our software would automatically create a table space on the UDB database for the purposes of hosting temporary tables. These temporary tables were used for hierarchies, subledger joins and other key functionality.

Due to database security concerns from UDB clients, this table space will no longer be automatically created and therefore needs to be created manually on the client’s UDB database. This table space MUST be named GLISPACE.

After installing Hubble and connecting to JD Edwards Data on a UDB Database, the Profile Wizard will check to ensure that the GLISPACE Table Space has been properly created. If this has not been completed, the Profile Wizard Run Test step will fail and you will not be able to continue with the configuration of the Profile Wizard until the GLISPACE Table Space has been properly created.

Page 4

JD Edwards Database Access | JD Edwards Database Configuration Questions

Creation of a user who has access to the new table space and JD Edwards tables

The user may already exist on the database, in which case the key thing is to grant use of the new table space to the user. The same user must have permissions to both the GLISPACE Table Space and the JD Edwards Tables.

JD Edwards Database Configuration Questions

If all JD Edwards Tables are accessible through one database connection (they reside on the same server and use the same user credentials and permissions), it is only necessary to complete the connection information below for the JD Edwards Data Tables.

Please have the password(s) for the user names(s) available at the time of the installation.

This section is typically completed by a technical user.

JD Edwards Table Locations and Data Access

If you are an existing Hubble customer, you can export your current production profile from the Administrator Application and send it to us so that we can use that information in the profile to retrieve the JD Edwards Table Location and JD Edwards configuration information. If you are a new Hubble customer, please complete the below information.

Data TablesWhat is the name of the location (database/library/schema) to the JD Edwards Data Tables, e.g. F0901? (Standard Location example is PRODDTA.)

What is the database account User ID that will be used to access the data?

What is the name of the server that hosts the JD Edwards Data Tables?

If the database is Oracle, what is the Port Number used to connect?

If the database is Oracle, what is the Service Name (SID Name)?

Page 5

JD Edwards Database Access | JD Edwards Table Locations and Data Access

User Defined Code TablesSKIP SECTION if same as JD Edwards Data Tables above.

What is the name of the location (database/library/schema) to the JD Edwards User Defined Code Tables, e.g. F0005? (Standard Location example is PRODCTL.)

What is the database account User ID that will be used to access the data?

What is the name of the server that hosts the JD Edwards Control Tables?

If the database is Oracle, what is the Port Number used to connect?

If the database is Oracle, what is the Service Name (SID Name)?

Security TablesSKIP SECTION if same as JD Edwards Data Tables above.

What is the name of the location (database/library/schema) to the JD Edwards Security Tables, e.g. F0092? (Standard Location example is JDESY.)

What is the database account user name that will be used to access the data?

What is the name of the server that hosts the JD Edwards Security Tables?

If the database is Oracle, what is the Port Number used to connect?

If the database is Oracle, what is the Service Name (SID Name)?

Page 6

JD Edwards Database Access | JD Edwards Configuration Questions

Data Dictionary TablesSKIP SECTION if same as JD Edwards Data Tables above.

What is the name of the location (database/library/schema) to the JD Edwards Data Dictionary Tables, e.g. F9201 for World or F9210 Enterprise One? (Standard Location example is JDEDD.)

What is the database account user name that is used to access the data?

What is the name of the server that hosts the JD Edwards Data Dictionary Tables?

If the database is Oracle, what is the Port Number used to connect?

If the database is Oracle, what is the Service Name (SID Name)?

JD Edwards Configuration Questions

General Information

Are you a World, EnterpriseOne (OneWorld) or a co-existence site?

Which version of JD Edwards are you running, e.g. A73, A92, B733, E1 8.10, E1 9.0, etc.?

What is the name of the JD Edwards environment you wish to connect to, e.g. PD733, PROD810?

What database platform is JD Edwards running on, e.g. Oracle, AS/400 DB2, SQL Server?

Which version of the database are you running, e.g. SQL Server 2005, Oracle 9g? If AS/400 DB2, which version of the operating system is running, e.g. V5R4?

If you use the AR, SOP or CRM modules, do you use Customer Line of Business Support?

Page 7

JD Edwards Database Access | JD Edwards Configuration Questions

Model Business Units

What are the model business units used for GL?

What are the model business units used for Job Cost?

What are the model business units used for Fixed Assets?

Subledger InformationIndicate if the subledger item is to be included.

Subledger Table Name Table Include:Yes No

A F0101, F0111 Address Book Number

C F0006 Business Unit Number

E F1201 Asset Number

F F1755 Maintenance Request Master

G F1720 Contract Number

I F4101 Item Number

L F1501 Lease Number

O F4201 Order Number

S F0907 Structured Number

U F1507 Unit Number

W F4801 Work Order Number

J, X, Y, Z F0005 User Defined Codes

X* F4461 Homebuilder Options

X** F44H401 Homebuilder Options

* Used for Homebuilder World only

** Used for Homebuilder EnterpriseOne only

If your company is utilizing any of the features listed below, please see the corresponding sections in this document for the additional setup and configuration necessary to complete your installation. • Designer Express• Reconciliation Integrity Reports

Page 8

Chapter 3: Users

Creating Hubble Users

Please attach a list of JD Edwards user names that you wish to access Hubble. If you have additional information such as the user's group or role, this will help when completing the setup.

User Name User’s Role

Page 9

Chapter 4: Designer ExpressOnly complete this section if you are using Designer Express.

For additional information on this capability, please refer to the Hubble User Guide for Designer Users.

Designer does NOT support DB2 for LUW (UDB). DB2 UDB for System i (iSeries, OS/400) is supported with Designer Express, along with SQL Server and Oracle databases.

JD Edwards Database Connectivity – Object Librarian Tables

What is the server name which hosts the JD Edwards Object Librarian tables?

What is the name of the location (database/library/schema) to the JD Edwards Object Librarian Tables, e.g. F9801 for World or F9860 for EnterpriseOne? (Standard location example is JDEOL.)

What is the database account User ID that will be used to access the F9860 (EnterpriseOne) or F9801 (World)?

If the database is Oracle or AS/400 DB2, what is the Port Number?

If the database is Oracle, what is the Service Name (SID Name)?

For which JD Edwards Data Tables do you want to create templates using Designer Express?

Page 10

Chapter 5: Reconciliation Integrity Reports

We strongly advise that indexes are implemented for each Reconciliation inquiry to improve performance. Without indexes, the Reconciliation SQL queries will be doing full table scans over the biggest tables in JD Edwards which will take a long time to return results.

The best scenario for index analysis is to set desired filters in the Reconciliation inquiry and then capture the SQL in Hubble’s View SQL window. Note the SQL captured in Hubble’s View SQL window is not the full SQL as the subqueries associated to certain business logic do not show. Provide the SQL to your database team for processing through the databases query analysis/execution plan. The database analysis/execution plan will need to run the SQL in order for the subqueries that are not seen in the SQL to be executed and analyzed.

Because each client will have a slightly different set up in the Reconciliation inquires and on their databases, specific indexes cannot be recommended. However, below is a MINIMUM JD Edwards table index recommendation.

Reconciliation reports do not support DB2 for LUW (UDB).

DB2 UDB for System i (iSeries, OS/400), along with SQL Server and Oracle databases, is supported for Reconciliation reports.

JD Edwards Table Index Recommendation

The JD Edwards tables used by Reconciliation reports are large in size due to the nature of the volume for the relevant transactions. The primary filter used for Inventory, Accounts Payable, Accounts Receivable and Received Not Vouchered (GRNI) is the GL Date and for Fixed Assets the primary filter is Object Account. In order to avoid a full table scan to retrieve records, it is our recommendation to create the below indexes on the following tables:

1. F0911 – GLDGJ – GL Date (AR, AP, INV and RNV)

2. F0911 - GLOBJ – Object Account (FA)

3. F1202 – FLOBJ – Object Account (FA)

4. F03B11 – RPDGJ – GL Date (E1 AR)

5. F03B14 – RZDGJ – GL Date (E1 AR)

6. F0411 – RPDGJ – GL Date (AP)

7. F0413 – RMDMTJ – GL Date (AP)

8. F0311 – RPDGJ – GL Date (World AR)

9. F3106 –

a. SDICU, SDDGJ,SDDOCO – Batch Number, GL Date, Document Number (INV)b. SDICU, SDICT – Batch Number, Batch Type (INV)

10. F4111 – ILDGL – GL Date (INV)

11. F43121 – PRDGL – GL Date (RNV)

12. F06116 – YTDGL - GL Date (Payroll)

13. F0618 – YTDGL - GL Date (Payroll)

Page 11