Strategic Planning

Strategic Planning takes budgeting to the next level by looking outside the General Ledger and allowing you to create custom data entry tables. Strategic Planning is completely customizable; it enables end users to design an input form which can be joined to any table in JD Edwards or Oracle E-Business Suite and incorporate them with user-defined data collection columns that hold key driver information for robust modeling.

With the inclusion of a license called DX Data Entry (DXE), a DX report can be used as a budget Input Form which can be associated to a budget cycle and submissions can occur. Solutions will often forecast amounts at a deeper level of detail in a data entry table and utilize the Cascade functionality to map the summarized results to a valid Account ID within the General Ledger. The Planning capability in Hubble automates enterprise planning and forecasting and integrates it directly with your ERP, enabling a real- time planning process and eliminating offline spreadsheets.

Strategic Planning Use Cases

• Sales Forecasting – forecast sales by Item, Customer, Sales Representative, etc.
• Production Planning – forecast production quantities by Item, Location, etc.
• Payroll - forecast wages and payroll expenses by Employee, Position, Employee Type, etc.
• Capital Expenditures - forecast Additions and Depreciation by Asset, Asset Grouping, etc.
• Assumptions – store seasonality spreads, growth percentages, or industry indexes to be utilized in Excel Models.

Process Overview

1. Create a Designer Express Input Form that includes a Data Entry Table.
   1. Define the fields and amounts to be collected.
2. Associate the Input Form to a Budgeting Cycle.
3. Enable Enter Budget Mode.
4. Insert rows and submit data into the Data Entry Table.
5. Push results to a General Ledger Account - utilize Model Cascade functionality to push summarized Data Entry Table amounts/results, into a Hubble Ledger within a GL Budgeting Input Form.
6. Finalize, Approve, and Upload submissions where required.

GL Budgeting vs. Strategic Planning

Strategic Planning Input Form

This section explains the required steps to enable a Data Entry Table for Data Entry, utilizing Designer Express Functionality. A DXD (Designer Express Designer) license is required to access the Template Designer. See the User Guide for Designer Express Capability for a more complete description of Designer Express functionality.

Template Designer

1. Open the Designer Express Template Designer. From the backstage view, click New > Designer Express > New Template.
2. Add a Data Entry Table to the template.
3. Select Column Definitions to set the Label and Amount definitions for desired fields.

   

   1. In the Source column, set the default setting for this column:
      • Customer Default (recommended) – setting will apply to all reports using this column.
      • Report Override - setting will only apply to the report you are currently in.
      • Product Default - the default setting that comes from Hubble Default Metadata.
   2. In the Category column, define any numeric columns as a Label or Amount. Input into at least one amount field is required for data entry.
      • Numeric (Label) - These are columns that are numeric, but the numeric value represents a code number rather than a real amount, e.g. Object Account or Business Unit. Unit costs or Rates are normally treated as Numeric Labels, although they represent real amounts, it does not make sense to subtotal them.
      • Numeric (Amount) – These are amount columns and can include non-currency amounts, e.g. Amount and Currency Amount.
      • Amount (Domestic) – These are amount columns in the base company currency. will be prompted for which company field to use. Decimal shifting will be based on the company base currency.
      • Amount (Foreign) – These are foreign currency amounts, e.g. F0414 (RNCDSA - Amount – Foreign Discount Taken). Decimal shifting will be based on the foreign currency specified.
      • Amount (Non-currency) – These are non-currency amounts, e.g. F43121 (PRUORG - Units - Order/Transaction Quantity).
   3. In the Lookup column, you can optionally define a table or fixed list lookup in order to provide filter validation, Query Assist support, and Code & Description feature support to end users:
      • Fixed List - Define a fixed list of valid codes and their associated descriptions for a column. These will display in a Visual Assist and in the inquiry results.
      • Table Lookup - Define a lookup table for a column, which provides the valid codes and their associated descriptions, as displayed in a Visual Assist and in the inquiry results. (This does not have to be a table being used in your template /report.)
   4. Press OK to close Column Definitions.
4. Press OK to exit Template Designer.
5. Complete Input Form Construction:
   1. Define Filters.
   2. Add Label Columns, Including Primary Key field(s), via Columns, Sorting, and Grouping.
   3. Add Amount Columns via Values Filter Box.
6. Save Input Form.
7. Best Practice:

Tip: Utilize Designer Express functionality to join Data Entry Tables to other ERP Tables.

• This will limit the data entry required by end users and ensure consistency with your ERP.
• To ensure only records included in the Data Entry Table appear, include the Data Entry Table in an Outer Join.
• For example, use Employee Number to Join your Data Entry Table to an Employee Detail table within your ERP. Columns from the Employee Detail Table will then be available in your template, and users can easily view details such as Name, Hire Date, Department, etc.

Create a Manage Table Input Form for each Data Entry Table.

• A simple Input Form that only shows the Data Entry Table’s columns, without other Tables, Calculations, or Formatting.

• Allows for easier rollforward, inserting/deleting of rows, etc.

Security and Data Entry Tables

Whenever constructing custom tables for data collection, consider including columns that can automatically inherit and respect ERP security. For example, users should include and write to a custom MCU column in every table so that Business Unit Security can automatically be applied to any reports built over the custom table.

IS_GENERIC Table

This table helps you figure out what fields to add to a custom table.

In your custom table, be sure to define columns as amount columns in order to see them in the amounts filter. Also, if you have set the sequence number field to be the primary key, this field must be in grid when you are entering data (it can be hidden) because it is the primary key.

Strategic Planning Budgeting Entry

Requirements for Entry

The following are required before a user can enable Enter Budget Mode for entry into a Data Entry Table:

1. The form must be created from a DX Template that includes a Data Entry Table.
2. The field(s) defined as the Primary Key of the Data Entry Table are included as Column(s).
   • Added via Columns, Sorting, and Grouping.
3. At least one amount or value column from the Data Entry Table is included.
   • Added via the Values Filter Box.
4. There must be editable cells on the Form.
5. The inquiry must be saved and identified as a Budget Form.
   • The Form must be associated to a Cycle.
   • The Cycle must be Open.
   • The User must be a Contributor in that Cycle’s Activity.
   • The User must have not previously Finalized that Form.
   • The User must not have been Exempted from that Form.
   • If more than one cycle meets the conditions above, the user will be prompted to choose which cycle to use. If there are no input forms that meet the conditions above, the error message displayed is: There are no open budgeting cycles that require submissions for you using this form.
   • In order for a cell to be editable, the following conditions must be met:

• Each Input cell must be a unique combination of the Primary Key and amount field i.e., no duplicate input cells can exist. For example, Budget entry is not possible when an amount column is included twice, or when the Primary Key appears in more than one row.
• Editable cells will not be validated against any defined scope (cycle level or participant level).

Strategic Planning Enter Budget Mode

The Enter Budget Mode interface for Strategic Planning is similar to GL Budgeting, with an emphasis on Inserting new rows to store data and amounts.

1. Click Enter Budget in the Budgeting Menu to enable Enter Budget Mode.
2. Data can only be entered after a record has been inserted into the Data Entry Table.
   1. See Instructions below for Inserting and Deleting Rows.
3. Label Column Validation:
   1. Label Columns will be validated against the Lookup defined in Column Definitions of the Template Designer.
   2. Utilize Query Assist to search and select valid entries.
      1. Right Click on the label field’s input cell, select Query Assist, which will display an assist dialogue.
   3. If the field is filtered for a single selection, its associated Input Cells will not be editable.
   4. Rows that would create a duplicate Primary Key will not be saved. if the row previously existed and the amount fields are cleared, that record may be deleted.
4. Amount Input:
   1. Amounts can be populated via Manual Entry or Modeling.
   2. Rows without input into a least one amount field will not be saved.
5. To cancel Enter Budget Mode (thus losing any input you have done since last saving), click Cancel.

6. To save the input data while staying in Enter Budget Mode, click Save and Continue.

7. To save the input data and exit out of Enter Budget Mode, click Finish.

   

Important:

• Rows that would create a duplicate primary key will not be saved.
• Rows without input into at least one amount field will not be saved, if the row previously existed and the amount fields are cleared, that record may be deleted. When saving a form that contains rows without amounts, the above message will displayed.

Insert New Row

1. Click Enter Budget from the Budgeting Menu to enable Enter Budget Mode.
2. Click Insert New Row from the Enter Budget Menu, or right click on an existing line and select Insert New Row.

3. A new row will display each time Insert New Row is selected.

Insert from Clipboard

1. Click Enter Budget from the Budgeting Menu to enable Enter Budget Mode.
   1. Copy the Data that is to be inserted into the Data Entry Table.
   2. Data can be copied from an Excel Spreadsheet, a Hubble Report, or many other places.
2. Right Click on an existing row and select Insert from Clipboard.
3. The appropriate number of rows will be inserted, containing the data that was copied into your clipboard.

Deleting Rows

1. Click Enter Budget from the Budgeting Menu to enable Enter Budget Mode.
2. To delete a row from a Data Entry Table, highlight the row and click on Delete/Clear Row either by right-clicking or by going to the Enter Budget Menu and selecting Delete/Clear Row.

Errors

“It was not possible to identify any valid budgeting input cells on the current report.”

• Verify the Input Form contains a Hubble Ledger that is associated to an Open Cycle.
• Verify the Input Form contains a valid amount column, cumulative periods and calculations are not editable

“It was not possible to identify any valid budgeting input cells on the current report. This budgeting cycle contains a scope which may be excluding all cells.”

• Verify Participant Scope and Cycle Scope are not restricting access to all cells in the Input Form.
• An example of why you would receive this error is that a scope might be set to look at the current fiscal year, e.g. 2018, yet the Hubble ledgers columns are looking at the NEXT fiscal year (2019).
• This occurs because budget mode is not possible on any hierarchy node which is a range or list total (not expanded) unless the option to Allow submissions without a valid Account ID is checked (shown when you edit a form). As soon as a range or list total is present, Hubble is not able to determine conclusively whether the node represents a single account ID or multiple accounts. Therefore, it does not allow data entry unless the checkbox Allow submissions without a valid Account ID is checked.
• Assuming amounts have not been entered on this form already and you wish to enter summary level information, go to the Budgeting tab > Forms and edit the form. Uncheck Allow submissions without a valid Account ID.
• Do not change the Allow submissions without a valid Account ID option on an existing form that you have been using as it will create duplicate records in the Hubble Budget Table (ISBudgetData4 Table). The duplicate record will have one field (GBHIREPT) populated differently.
  • GBHIREPT = 1 indicates the account is valid
  • GBHIREPT = 2 indicates the account is not valid

If the record in the table has a 1 in this field and $100.00, instead of updating that $100.00 amount, a new record will be created with a 2 in that field and NULL in the GBAID field.

Ultimately, amounts will be overstated and the fix is not easy! This is why it is important not to change the Allow submissions without a valid Account ID option mid-stream.

“It was not possible to identify any valid budgeting input cells on the current report. This may be caused either by the scope in effect or a lack of leaf nodes on the current hierarchy.”

• On the Scope tab of the budget cycle associated with your form, edit any existing scopes and check to see if they are excluding all data from showing. When checking, bear in mind that the end user receiving the error may have security set to prevent them from seeing all companies, business units, etc.
• On the Scope tab of the budget cycle associated with your form, take out the checkmark in the Restrict entry to only the lowest level items of the hierarchy option if you want to enter amounts into roll-up accounts. For example, unchecking this would allow you to enter into a hierarchy roll-up named ‘Bank Accounts’ whereas having it checked would force you to enter amounts into each bank account individually.

“The following required dimensions are missing from this report: Business Unit (or Object Account or Subsidiary). All required dimensions must be present either as a column, row or single selection in the filters for budgeting to be possible. Alternatively, allowing submissions for invalid accounts would make these dimensions optional.”

• An account number is defined by the business unit, object, and subsidiary. If any of these aren’t showing as a column on the report, Hubble won’t be able to upload the necessary data to the F0902Z1. To take this one step further, the F0902Z1 has the GBAID (account number) as a key field. The GBAID is derived by looking at the BU.OBJ.SUB.
• Do not change the Allow submissions without a valid Account ID on an existing form that you have been using as it will create duplicate records in the Hubble Budget Table (ISBudgetData4 Table). The duplicate record will have one field (GBHIREPT) populated differently.
  • GBHIREPT = 1 indicates the account is valid
  • GBHIREPT = 2 indicates the account is not valid

• If the record in the table has a 1 in this field and $100.00, instead of updating that $100.00 amount, a new record will be created with a 2 in that field and NULL in the GBAID field.
• Ultimately, amounts will be overstated and the fix is not easy! This is why it is important not to change the Allow submissions without a valid Account ID option mid-stream.

“This form is not a part of any currently open budgeting cycle.”

• Check to make sure a valid Hubble Ledger is in the ledger filter.
• Ensure there is a cycle associated with the form and that it is in an Open Cycle status.
• Ensure the user clicking Enter Budget is also set up as a participant for the activity that is associated with the cycle.

“There are no open budgeting cycles that require submissions from you using this form. This usually means all your submissions have been approved and locked.

• Check that your cycle(s) is open.
• It’s possible your form has already been finalized, approved and/or uploaded.
• If using Cascade, check that forms which are set as “Full” or “Update” on Cascade are both part of one or more common cycles (cycles that have both forms). Cascade “Create” does not require a form to be a budgeting form.

“You are not a contributor to any cycle using this form.”

• Confirm you are a contributor for the activity to which the cycle belongs.

“Cannot submit budgeting information, some cells have invalid values… Row X, Column Y: Not a valid code”

• The subledger field should be populated with the subledger type capitalized followed by a period and the appropriate subledger value.
• If custom subledger types (X, Y, Z) are being used, the below information applies. The Description 2 field of UDC 00/ST impacts how information is stored in the database.

• Z, has a C in the first character of Description 2, so in the database the subledger values are stored with leading spaces. Numbers and capitalized alpha characters are accepted. For example, ‘Z.TEST’, ‘Z.123’ or ‘Z.T123’ would be accepted but not ‘Z.test’. In the table, TEST would be stored with 4 leading spaces in the subledger field and show as ‘Z.TEST’ in Hubble.
• Y, has a N in the first character of Description 2, so in the database the subledger values are stored with leading zeros. Numbers and alpha upper and lower case characters are accepted. For example, ‘Y.TEST’, ‘Y.test’, ‘Y.123’, and ‘Y.T123’ are all accepted. In the table, TEST would be stored with 4 leading 0’s in the subledger field and show as ‘Y.0000TEST’ in Hubble.
• X, has an A in the first character of Description 2, so in the database subledger values are stored left justified. Numbers and capitalized alpha characters are accepted. For example, ‘X.TEST’, ‘X.123’ or ‘X.T123’ would be accepted but not ‘X.test’. In the table, TEST would be stored with 4 trailing spaces in the subledger field and show as ‘X.TEST’ in Hubble.
• Note: If the first character in the Description 2 field is changed for any of the above, the functionality will change too. In other words, if Z has N in the first character of Description 2 field, it will function as Y does.

“The following required dimensions are missing from this report: Sequence Number. All required dimensions must be present either as a column, row or single selection in the filters for budgeting to be possible. Alternatively, allowing submissions for invalid accounts would make these dimensions optional.”

• Add the sequence number to the report via Column, Sorting, and Grouping.