The steps required to set up a business unit
A business unit identifies a separate SunSystems entity that holds all of the records for a single operating unit. A business unit is identified by a three character code.
Note: The first character of the code cannot be numeric, and it is recommended that 'ZZZ' is not used as this is used internally within SunSystems.
If you define more than one business unit, when you access a SunSystems form you may be asked to select the business unit you require. You are not always asked this because:
- you may have accessed a global function which is not business unit specific, for example Rule Sets.
- a business unit may have been preset to your Operator ID
- you may have used Change Business Unit (CBU) which sets the active business unit.
The following steps are required to define a new business unit:
- Create the business unit using the option from the menu in Business Unit Administration (BUA).
- Set the business unit processing rules using Business Unit Setup. See step 8 for defining ledgers.
- Create the report models for the business unit using Report Models (RMD). This must be carried out in order to run reports for the business unit.
- Create the business unit address and default invoice address using Addresses (ADD).
- Link the business unit name and address details using Business Unit Name (BUN) and Business Unit Addresses Setup.
- If you have installed and attached the PK1 database you must run Filter Data Dictionary Regeneration for the new business unit.
- You must then use Ledger Setup (LES) to specify additional rules about how you would like the financial ledger, within the business unit, to operate.
- Create budget ledgers (ledger B, C, D, etc) using Budget Labels (BLB) first, and then Optional Ledger Tables (OLT). This is an important but optional step. Ledger A is created by default. Assign these ledgers in Business Unit Setup to be the primary budget ledger, purchase commitment ledger, and expected revenue ledger.
After a business unit is created, or any form changes have been made, the forms are automatically compiled at run-time when a function is accessed, and the latest version of the form is displayed.