System Options

The System Options table provides a set of characteristics that guide accounting activities for the different functional areas in the application on a yearly basis. Each control or option set on System Options is associated with one or more business rules that drive actions throughout the system. However, those business rules do not exist on System Options. This table is just a collection of flags, rules, and controls that guide processes that read these options and controls.

Records on System Options are unique by fiscal year. A year-end process exists to populate the table with values for a coming year so you do not have to enter them manually unless you choose.

Some features of System Options will resemble those in previous versions of CGI Advantage Financial, while many will be new. Although System Options has one page code that is found through the Global Search feature, you will find the single entry leads actually into different pages for different functional areas. These areas are represented on the left-hand menu of the page for easy navigation: Expense, General, Revenue, and Fixed Assets. Instead of separate page codes for each area, they are consolidated into just one.

Certain System Options options are followed by a flag that will allow overrides. Depending on the option, those overrides can be in one or more places. A centrally controlled application will likely have these flags unchecked so that similar settings in other more decentralized areas will not be used. However, the decision to override options is made on an option by option basis usually resulting in a mix of ones overridden and not. If allowed to override, it does not mean that the control has to be defined at the lower level. Application logic will use the lower level if set and if not, the System Options option will be used. More information on where the overrides can be set is detailed in the listing of controls later in this guide.

This topic only contains the options and controls that affect the Procurement area. Refer to the "System Options" topic in the CGI Advantage - Financial Administration User Guide for information on the other options and controls that appear on System Options.

The following table describes the Expense options and controls found on System Options, for the Procurement area:

Option/Control	Description
Require UR Accounting	If this option is selected, then at least one Accounting Line must exist for each Commodity Line on the UR transaction.
Auto Submit From UR	If this option is selected, then when the UR becomes Final, all subsequent transactions will automatically be submitted.

The following table describes the General options and controls found on System Options, for the Procurement area:

Option/Control	Description
Renewal Days	This field is used as the default number of days in advance to alert a buyer that a contract is about to expire. It is used when the Master Agreement does not specify a number of days. The default value is zero.
Commodity Code Registration Level	This option determines at what level of detail vendors may register themselves for commodities. It is also used as the default level of detail for any commodity searches in the system. Valid values are Class, Item, Group and Detail. The default is Item.
Procurement Type ID	This option indicates the type of procurement selected when the procurement was created.
Default Procurement Type	This option indicates the default procurement type when the user does not enter one.
Print Tracked PO Changes Only	If the Track Changes field is selected on the Header tab of the PO under the Modification subsection and the Print Tracked PO Changes Only field is also selected, then when you print the PO, only the changes will be printed instead of the entire transaction.
Matching Level	This field allows you to define the Matching Level at a system-wide level. Valid options are: Transaction, Commodity, and Transaction-Commodity.
Matching Precedence	This field defines the matching precedence at a system-wide level. Valid options are: Transaction or Commodity. The Matching Precedence field must have a value of Transaction or Commodity when the Matching Level has a value of Transaction-Commodity.
Update Vendor Pending Change Table	This field directs the application table to update a Vendor Pending Change table whenever an update is made to the Vendor/Customer table. Such tracking is essential to Financial applications that also use the Vendor Self Service (VSS) application because the Financial to VSS synchronization job reads the table and updates VSS.
Delivery Order Default	This field specifies the Delivery Order transaction code that will be defaulted in the Code field on the Shopper - Checkout page if the contents of the shopping cart are from one vendor on the same Master Agreement or MA Catalog and the USE_DO_PRC_SHOPPER parameter on the Application Parameters page is set to DO. This field contains a pick to the Procurement Transaction Control (PRDOC) table, and only allows you to choose transaction codes with a Transaction Subtype of DO.
Payment Order Default	This field specifies the Payment Request transaction code that will be defaulted in the Code field on the Shopper – Checkout page if the contents of the shopping cart are from one vendor on the same Master Agreement or MA Catalog and the USE_DO_PRC_SHOPPER parameter on the Application Parameters page is set to PRC. This field is also used to determine the Transaction Code that is created when the Universal Requestor transaction has been submitted and the Create Payment check box has been selected for a Commodity Group that references a Master Agreement.
VSS Unit Required	The VSS Unit Required flag defines if a Unit code is required for VSS vendors/customers at a system wide level.
Calculate Legal Name	This flag defines if the Legal Name of a Vendor/Customer should be calculated by the system at a system wide level.
Enable Vendor Types	This flag controls the enforcement of vendor type validation: If Enable Vendor Types is set to Yes, the system will enable the logic for selecting the vendors as service and/or commodity and restrict transactions to use commodity vendors, service vendors, or both. If Enable Vendor Types is set to No, the system will disable the logic for selecting the vendors as service and/or commodity and restrict transactions to use commodity vendors, service vendors, or both.