Skip to main content

Set Up Budget Connection and Profile

Overview

A Connection stores the information (database type, user name and password) required to connect to your ERP Database(s). In some cases, the existing ERP Data Connection can be used for Budgeting (in order to connect to the database that will be used for the Budget Database), however for enhanced security, you may want to have a separate connection and connection user. This is because in Budgeting, the user who is defined in the connection may require additional permissions, such as read and write permission to the Balances Batch Table (F0902Z1) to upload records to JD Edwards EnterpriseOne.

Once the Budget Database Connection has been created, you can create or edit a Profile to use this Connection. A Profile can be made up of multiple Connections. Additionally, for ease of use, a Connection can also be reused by multiple Profiles.

Note: Often in the ERP Data Connection, the user only has read permissions to the JD Edwards Tables.

Create a New Budgeting Connection

Follow the steps below to create a new database connection:

  1. Within Administrator, log into your repository if you are not logged in already.
  1. Expand the Data Sources node in the left panel.
  2. Right-click on Connections, select New, then Database Connection.
  3. Configure the connection in the Database Connection dialog:

    1. Identification - set a unique Name for this connection (e.g. ‘BUD_21_4’) and, optionally, set a Description.
    2. Data Source Type - specify the Type of database in which your Budget Database is located:
      1. Database Accelerator
      2. Microsoft SQL Server®
      3. Oracle
      4. IBM DB2
    3. Data Source Provider – This will default in based on the Data Source Type.
    4. Click Configure. The Database Provider Configuration dialog is then displayed.
    5. The settings in the Database Provider Configuration dialog will vary depending on the type of source database the connection is located in. The Administrator and Configuration Guide describes the dialog for each type.

Profile Setup

A new profile can be created, or an existing profile can be edited to configure budgeting. This section outlines the options within the Create/Edit Profile Wizard, which are relevant to configuring Budgeting and Planning. Complete profile setup instructions can be found in the Administrator Guide.

  1. Within Administrator, log into your repository if you are not logged in already.
  1. Expand the Data Sources node in the left panel.
    1. To Create a new profile - Right-click on Profiles, select New, then JDE Profile.
    2. To Edit an existing profile – Right-click on the desired Profile, select Edit.
  2. In the Create/Edit ERP Profile Wizard, click Next, and continue clicking Next, until you reach the Module Selection screen.

    1. Select the Desired Features
      1. Budgeting (BUD) - To use any Budgeting functionality, the Budgeting (BUD) feature must be selected in the Module Selection screen.
      2. DX Data Entry (DXE) -To use Strategic Planning functionality, which allows for the ability to enter data into Input Forms created from Designer Express templates that contain Data Entry Tables, the DX Data Entry (DXE) feature must be selected in the Module Selection screen.
  1. Click Next until you reach the JDE or Oracle Connectivity (Data Entry Connection) screen.

    1. Data Entry Section.
      1. Connection - Identify the connection being used to connect to the Budget Database.
      2. Database / Library - Identify the database/library being used for the Budget Database. If it has already been initialized, it will be listed in the drop-down box; otherwise, the location must be typed in.
        1. For SQL Server, enter the name of the database in SQL Server, followed by a period, followed by the database owner username (typically ‘dbo’).
        2. For DB2 and Oracle, you only need name of the library/schema.
      3. Retain Historical Data (JD Edwards Only) – Check this box to retain a history of all additions and updates to GL Budgeting data. Users can query the history via the GL – Budget History Template or a report made from that template.
      4. Repository Prefix - A repository may contain multiple budgeting repositories. This is controlled on a profile basis. A repository prefix must be added to table names to distinguish them by entering it here or selecting it from the drop-down.
    2. Budgeting Upload Section (JD Edwards EnterpriseOne Only).
      1. Connection - Identify the connection being used to connect to the F0902Z1 Table.
      2. Upload - Define the name of the database and owner or library name where the F0902Z1 Table is located. If it has already been initialized, it will be listed in the drop-down box; otherwise, you must type it in.
        1. For SQL Server, enter the name of the database in SQL Server, followed by a period, followed by the database owner username (typically ‘dbo’).
        2. For DB2 and Oracle, you only need name of the library/schema.
      3. New Connection -If you wish to have a separate Connection to the location of the F0902Z1 Table but have not yet created it, create it by clicking on the New Connection button.
        1. If the Balances Batch Table F0902Z1 that is being used to upload data is located in a different database, library or schema as the JD Edwards Data Connection, the users will NOT be able to see any data stored in the Balances Batch Table F0902Z1 when logged into Hubble using the Profile to which the JD Edwards data is pointing. A separate Profile is needed to point to the data stored in the F0902Z1 Table to enable users to view that data within Hubble using the GL Balances Batch Upload Template. For example, if the Profile is configured to look at a backup environment or test environment and the F0902Z1 Table used in uploading Balances is set up to look in the production environment, then a separate Profile must be created to see the F0902Z1 data stored in production.
        2. The database that the Balances Batch Table F0902Z1 is stored in MUST be the same type of database that stores the rest of the JD Edwards Data Tables in order for the Budgeting Upload to function properly.
  1. Click Next until you reach the Select Additional Tables to Configure screen.

    1. Custom Data Entry Tables - Custom Data Entry tables to be utilized within Strategic Planning are identified on the Select Additional Tables to Configure screen. This step is only required for custom tables and is not required for the tables created automatically by selecting the DXE Feature, such as ISGENERIC or ISBPAYROLL.
    2. Import Custom Data Entry Tables XML – an XML is required to define all data entry tables to be utilized in Hubble Strategic Planning. This selection allows an administrator to Input, Clear, or Export that file. DataEntryTablesExample.xml is included as an example, in the Hubble install path. Note that a table identified in the XML is not required to be chosen in the “Choose Tables” dialogue.
      1. The XML File is required to identify the following special-purpose columns, which are mandatory for data entry.
        1. ContributorId - Identifies that the column is used for storing the Contributor ID (User ID).
        2. CycleId - Identifies that the column is used for storing the Cycle ID.
        3. FormId - Identifies that the column is used for storing the Form ID.
        4. AutoIncrement- specifies the column to be auto incrementing, usually for a primary key or identifying column. Note: If other primary key(s) information is specified, this is not a required column.
      2. Within the XML File you can optionally declare columns that are to capture the information below, or have the specific behavior:
        1. ContributorName - Identifies that the column is used for storing the Contributor Name.
        2. CycleName - Identifies that the column is used for storing the Cycle Name.
        3. MachineName - Identifies that the column is used for storing the Machine Name.
        4. FormName - Identifies that the column is used for storing the Form Name.
        5. SubmissionDate - Identifies that the column is used for storing the Submission Date.
        6. SubmissionTime - Identifies that the column is used for storing the Form Name.
        7. ReadOnly - A Read-Only column that cannot be submitted into
  1. Click Next until Finish is available, Click Finish to save changes and update the Profile.

    This step performs the following actions:

    1. Creates the below Budget Tables when the BUD feature is selected, within the defined Budget Database
      1. ISBudgetCatalog – JD Edwards Only
      2. ISBudgetData4 – JD Edwards Only
      3. ISBudgetData4History – JD Edwards Only
      4. ISBudgetObjects – Oracle E-Business Suite Only
      5. ISBudgetStatus2 – Oracle E-Business Suite Only
      6. ISBUDGETCODECOMBINATIONS – Oracle E-Business Suite Only
      7. ISBUDGETDATA – Oracle E-Business Suite Only
      8. ISBUDGETVERSIONS – Oracle E-Business Suite Only
    2. Creates the below Budget Tables when the DXE feature is selected, within the defined Budget Database
      1. IS_GENERIC – JD Edwards Only
      2. ISBPAYROLL – JD Edwards Only
      3. ISGENERIC - Oracle E-Business Suite Only

Back Up Budget Database

Include your organization’s Database Administrator when discussing and scheduling the backup of the Budget Database. We highly suggest routine backups of both the Budget Database as well as the standard Hubble Object Repository. If significant changes are being made on a frequent basis, this could be as often as a daily backup. Remember to save the backup files to a network location that is included with your regular disaster recovery services.

Remember, the Budget Database includes all Budgeting Tables and Data Entry Tables. These budget tables include the definitions of Activities, Cycles, and Hubble Ledgers as well as the list of Budget Forms (only their names, locations, and relationships are stored in the Budget Database). They also include the status of each Cycle, Contributor/Form (submitted, finalized, etc.) and the data submitted by contributors.

The Budget Database backup does not include Table Definitions, Excel Models or the inquiries which have been defined as Budget Forms; those are stored in the Object Repository along with all the other inquiries that have been created.

Suggested Backup Methods

  • Manual Backup via Hubble Administrator
  • Note: When upgrading to a new release, it will be necessary to have a Hubble backup to restore from.
  • Database Administrator Backup – arranged and managed by your DBA
  • Scheduled Backup via Accelerator REST API Backup - Accelerator Database Only

Manual Backup via Hubble Administrator

You can use the Hubble Administrator to perform routine backups of your Budget Database, and a user who belongs to the Administrators User Group has the ability to do so. It is much easier to restore from a Hubble backup than it is to restore from a full nightly tape backup of your entire database. With this method, a routine backup process cannot be scheduled, so designate a responsible party to perform this function within Administrator.

This is also very convenient when upgrading your version of Hubble. You can easily back up the Budget database and then restore it into the new Administrator version after you have set up your new Budget Database.

Backup

  1. Within Administrator, expand Data Sources.
  2. Highlight and right-click on the specific Profile that has the Budget Database defined that you wish to back up.
  1. Select Backup Budget Database.

  1. Windows Explorer will prompt you to save the Budget Database in a location that you specify. The Budget Database file will be saved with a .bdb file extension.
  2. Once completed, you are prompted with an Information dialog notifying you that your Budget Database has been successfully backed up.

Restore

  1. Within Administrator, expand Data Sources.
  2. Highlight and right-click on the specific Profile that is defined with the Budget Database that needs to be restored.
  3. Select Restore Budget Database.
  4. A Question dialog will display, asking if you are sure you want to restore your Budget Database. You are also notified that “All existing budgeting data for this profile and other profiles that use this budgeting upload database will be deleted.”
  1. Select Yes if you wish to restore.
  2. Using Windows Explorer, navigate to your Budget Database backup.
  3. Select Open once you have highlighted the Budget Database backup you wish to restore.
  4. An Information dialog will display, notifying you that your backup has been successfully restored.
  5. If the budgeting DB is stored on a different Schema than the Hubble reporting schema then the Select permissions will need to be reapplied at the DB level to allow Hubble to read the data. Failing to do so will result in a DB error e.g. “ORA-01031: insufficient privileges”.
  6. You can now launch Hubble and open any input form to verify your budget data has been restored as expected.

Database Administrator Backup

Many clients utilize a variety of database management tools to perform routine database level backups, which are then stored in a secure location. Discuss these options with your database administrator and verify the scope of the backup includes the Budget Database. Note, these backups can be used for database recovery, if needed.

Accelerator REST API

The backup process has a public REST API which can be called using a scheduling tool which allows a URL to be called using the POST Method. More information can be found in the Hubble Suite Supplementary Deployment Topics. There is widespread guidance online regarding the use of these tools - Hubble cannot provide specific support for them.

Customer PK Configuration

The primary key of a Data Entry Table can be defined or overridden via a CustomerPK configuration XML file. The file, CustomerPK.xml, can be imported, exported and cleared. Right-click on Profiles and select CustomerPK Configuration:

Note: After the CustomerPK configuration file has been imported or cleared, you must run the profile wizard to use of the changes in each profile.