Business Rules

 

      In addition to the other required data (such as description, delivery information, and additional details), the requisition must have at least one item on the item tab in order to be submitted to Workflow for routing.

      If the chart/org on the requisition does not have a content review routing rule set up, accounts are required before the document can be submitted. If a content review rule exists for the chart/org, the initiator will receive a warning message.

      Account distributions must exist for all item lines on the document before it may leave the content routing stage.

      The following rules apply for allowable accounts to be charged on a REQS. These are the same rules used for the PO. The specific codes for these rules may be specified via parameters.

Only expense (EE, ES or EX object types) or asset (AS object type) object codes are allowed. Asset object codes must be in the INV or OASS object level.

Object codes in the consolidations of Compensation (CMPN), Financial Aid (SCHL), Reserves (RSRX) and Assessments Expenditures (ASEX) are not allowed.

Object codes in the levels of Depreciation (DEPR), Indirect Cost Expense (ICOE), Valuations and Adjustments (VADJ) and Taxes (TAX) are not allowed.

Object codes with a sub-type code for Transfers (TN) are allowed.

      Expired and inactive contracts cannot be used on Requisitions.

      If a debarred vendor is used on a Requisition, a warning will be presented to the user.

      Non-Capital Assets are not allowed on the Capital Asset tab.

      Use Allow Copy Days in the Requisition Source table to control when copy function is allowed on the Requisition.

go-arrow-red   For information about Allow Copy Days, see Requisition Source.

More:

Routing