Second Test Guide

Last updated
Save as PDF

UndefinedNameError: reference to undefined name 'K12productname' (click for details)

Callstack:
    at (FTL:_Faster_Than_Light_testing_copy/Second_Test_Guide), /content/body/p[1]/span, line 1, column 1

, you have the option to define business rules to control various aspects of Financial Management. For example, you can:

Limit the data specific users are able to view (Basic)
Require approvals before posting can take place (Advanced)
Ensure that budgets are not exceeded (Basic and Advanced)

There are two categories of business rules in

UndefinedNameError: reference to undefined name 'K12productname' (click for details)

Callstack:
    at (FTL:_Faster_Than_Light_testing_copy/Second_Test_Guide), /content/body/p[2]/span, line 1, column 1

: Basic and Advanced. In this section, you'll learn about Basic Business rules. See the link below for Advanced Business rules.

Basic Business Rules

There are four types of basic business rules:

User Access Rules
- Limit a user’s ability to access data in the system.
- For example, User Sue can only access Vendors 1, 2, and 3. When she logs into
  UndefinedNameError: reference to undefined name 'K12productname' (click for details)
```
Callstack:
    at (FTL:_Faster_Than_Light_testing_copy/Second_Test_Guide), /content/body/div[1]/ul/li[1]/ul/li[2]/span, line 1, column 1
```
  , the Vendor list only shows these three records. When she defines a new Purchase Order, she can only select from these three vendors.
Validation Rules
- Define circumstances under which transactions can or cannot be posted.
  - For example, Acme Foundation has granted $100,000, but we can't spend it on any personnel/salary expenses.
- You can define a rule to ensure that Fund ACME cannot be used on a transaction against one of the personnel/salary G/L accounts.
  - For example, you have a dimension for Program and a dimension for Site, and you'd like to ensure that you always record both values.
- You can define a rule that requires a value in the Site dimension anytime you have a value in the Program dimension.
Purchaser Rules
- Determine who handles certain purchase decisions; used most frequently by organizations with a large purchasing document.
- For example, define the name of the purchasing agent for all transactions against Ace Office Supplies.
  - In the Requisition Review page, purchasers can view the transactions assigned to them.
  - With the Global Inbox setting on the User card > Additional Setup Fields, one user can view all transactions, regardless of the purchaser assigned.
Basic Budget Rules
- Ensure that you conform to your budget, triggering either a warning or error message when you are at risk of exceeding your budget.
- For example, you define a budget by G/L account, fund, and Department.
  - For 8620-ACME-PROGRAMS (account-fund-department), you have budgeted $1,000 a month.
  - By May, you have budgeted $5,000 and spent $4,876.22.
  - Your newest transaction for $125 will take you over your budget (by $1.22).
  - You receive an error and cannot post the transaction.

Additional Information

Advanced Business Rules (Workflow Management)