Add or Update Profiles

• If you created new connections (except for budgeting connections), you will need to create a new profile.

• If you did not create a new connection or only created a new connection for budgeting, you can use your existing profiles.

• You will need to edit your existing profiles to update them to the new release.

• Follow the instructions below to edit the profile configuration.

• For detailed information on each screen of the profile, refer to the Data Sources section in the Administration and Configuration Guide for the version of Hubble you are installing, as referenced in the Additional Resources section.

• Use that section of the guide to create a new profile if needed.

Update existing Profile(s) to the new version

1. In the Administration Tool, expand the Data Sources node in the left panel.

2. Highlight Profiles. In the right panel, highlight a profile and from the right-click menu, select Edit.

3. A pop-up titled Configure Hubble – Create or Edit an ERP Profile will appear. Follow these steps:

   1. On the Create/Edit ERP Profile Wizard screen, click Next.

   2. On the JDE Connectivity (Main Security, UDC, and Data Dictionary Connections) screen, click Next.

   3. On the Platform screen, confirm your correct JDE version is selected, or change it if needed, then click Next.

   4. On the Module Selection screen, confirm the correct modules are selected, then click Next.

      Note: If you select modules you are not licensed to use in JD Edwards, you will receive errors later in the profile.

   5. On the JDE Connectivity (Data Entry Connection) screen, update your budgeting details if applicable. If you do not use budgeting, leave the Enable Data Entry box unchecked and click Next. If you use budgeting:

      1. In the Connection field, select the new budgeting connection you created.

      2. In the Database/Library field, input the corresponding database or library. For SQL databases, add .dbo at the end of the database name (example, HUB_BUD_24.dbo). For Oracle or DB2 databases, use the database name (example, HUB_BUD_24).

      3. In the Repository Prefix field, leave it as IS for your production connection. For additional profiles, use a different two-digit prefix (e.g., PY for a Test/PY profile).

      4. Do not change the Budgeting Upload Table section unless your JDE connection information has changed.

      5. Click Next when finished.

         

   6. On the Select Additional Tables to Configure screen, click Next if you do not use strategic planning or have custom planning tables.

      If you use strategic planning:

      1. Keep the pop-up open in the new version.

      2. Log into the Administration Tool for your current/old Hubble version.

      3. Edit the same profile and click Next until you reach the Select Additional Tables to Configure screen.

      4. Click Export to save a copy of your current Custom Data Entry table.

      5. Save the file to your desktop, documents, or download folder.

      6. Copy the file to your new Hubble version install path.

      7. Close the old Hubble Admin Tool.

      8. Return to the new version pop-up and click Import.

      9. Import the saved XML file and click Next.

         

   7. On the Table Location screen:

      1. Check the Show All Tables field in the lower left corner.

      2. Click on the Prefixes column to sort by the column.

      3. Gradually scan the Prefixes column for items marked Do not use, <BLANK>, or Please Select.

      4. For these items, use the drop-down menu to see if another prefix can be selected. For example, if the F41171 table is mapped to Do not use, and the drop-down shows JDEData.dbo (used by other data tables), select JDEData.dbo.

      5. If the table type is optional (versus mandatory) and no other option is available, you can leave it as Do not use.

      6. Items marked <BLANK> or Please Select must be changed to another value. If no valid value appears in the drop-down, use Do not use.

      7. Ensure that Do not use is written exactly as shown, with a lowercase "n" in "not" and a lowercase "u" in "use".

      8. Avoid making changes to any prefixes other than those marked Do not use, <BLANK>, or Please Select, assuming all other prefixes were correct in your current Hubble version.

         

   8. On the Data Dictionary screen, click Next.

   9. On the Test the Current Configuration screen, click Run Test. If the status shows SUCCESS, click Next. If it shows FAILED, identify and resolve the failed items, then re-run the test. In the following example:

      1. The F0006 table shows as Failed and is mapped to JDECTL.dbo.

      2. The issue is that F0006 is a data table, not a control table, so it should be mapped to JDEData.dbo.

         

      3. Click Back twice to return to the Table Locations screen.

      4. Update the prefix for the F0006 table to JDEData.dbo.

      5. Return to the Test the Current Configuration screen and click Run Test again.

      6. Notice that the F0006 table is now successfully mapped.

         

      7. If you encounter issues with getting the prefix right for any mandatory items (i.e., achieving a SUCCESS result on the Test the Current Configuration screen), refer to Appendix A at the end of this guide for additional information.

      8. Otherwise, click Next.

   10. On the Environment and Model Business Unit screen, click Next.

   11. On the Options screen, click Finish.

   12. The Updating ERP Profile screen will run through various processes, for example, Setup Standard Templates and Setup Budgeting Repository. If the profile updates without errors, the description column will show green check marks and informational messages. If there are errors (red X) or warnings (yellow triangles), resolve them before proceeding.

       In this case, a message related to table F550902A, which is not being used, can be ignored. Simply click Close twice to exit the message and the profile configuration wizard.

       

       The errors (red X) cannot be ignored. If you are unable to resolve the error, create a support case for assistance.

       

4. Repeat these steps for each profile until all are updated.