Following is a list of the Reference tables used in the Purchasing/Accounts Payable module. The reference data created in these tables can be used in other reference tables and parameters. Most tables are self explanatory and do not require a separate article. Those that need additional explanation are linked to specific articles.
Table |
Description |
Used by... |
Billing Address |
Defines the various addresses to which vendors should send invoices. Addresses are specific to a campus and a campus can only have one billing address. The Billing Address displays in the Payment Info tab and defaults based on the Delivery Campus aka Campus Parameter. |
|
Capital Asset System State |
Used to indicate if the capital asset purchase will be:
Descriptions of the deliverd codes can be modified; new values require code. |
|
Capital Asset System Type |
Used to indicate if the capital asset purchases will be:
Descriptions of the deliverd codes can be modified; new values require code. |
|
Carrier |
Defines the various freight carriers that can be selected on the Receiving documents. |
|
Delivery Required Date Reason |
Defines the different types of delivery date types that can be used in the PURAP module. Examples might include types of Must Receive or Estimated Date. |
|
Electronic Invoice Item Mapping |
Defines the relationship between vendor invoice fields and the standard Kuali fields for electronic comparison. |
|
Item Reason Added |
Defines possible options to list on a receiving ticket as reasons why an item was received that was not on the original purchase order. |
|
Item Type |
Item Type defines the different descriptive categories that can be applied to requisition or purchase order line items. Examples might include Item, Service, State Tax, or Shipping and Handling. |
|
Method of PO Transmission |
Defines methods for transmitting purchase orders to vendors. You can also decide if a transmission method should display to the user. |
|
Negative Payment Request Approval Limit |
Use to identify exceptions to the Payment Request Auto approval parameter (DEFAULT_POS_APRVL_LMT). Exceptions can be set by account or organization. Setting by organizaiton is hierarchical. The exception will apply to any organizations reporting to the organization specified in this table. For example: POSITIVE_APPROVAL_LIMIT = 5000. If an organization wants to require approval of PREQs lower than this amount, they can add a line to the table, for example $3000. Then any PREQs over 3000 will require approval. Unless, Receiving is also required. If Receiving is required and occurs, the PREQ will be auto approved regardless of the amount. |
|
Organization Parameter |
Defines the APO limit for a specific organization. |
|
Payment Request Auto Approve Exclusions |
Identifies accounts that should be excluded from automated approval. |
|
Purchase Order Contract Language |
Defines text to be included in purchase order contracts. The contract language is defined by campus, allowing variations between campus offices and inclusion of campus-specific language. |
|
Purchase Order Quote Language |
Defines text to be included in purchase order quotes. The quote language is defined by a unique identifier, allowing pre-defined text to be easily added to quotes. |
|
Purchase Order Quote List |
Defines lists of vendors that have been created for a specific commodity and identifies the Contract Manager responsible for that list. |
|
Purchase Order Quote Status |
Defines the status options that may be assigned by a purchasing agent to each vendor in an existing quotation. |
|
Recurring Payment Frequency |
Defines payment frequency periods, such as annually, monthly, or quarterly. |
|
Purchase Order Vendor Choice |
Defines reasons that indicate why a specific vendor was chosen for a purchase. |
|
Receiving Address |
Defines the possible default receiving addresses for each department. |
|
Receiving Threshold |
Used to define criteria that determine when an order will require line-item receiving. |
|
Recurring Payment Type |
Defines different types of recurring payments that can be established for a purchase order. Examples might include Fixed Schedule, Fixed Payment or Fixed Schedule, Variable Amount. |
|
Requisition Source |
Defines the different fund sources that are available to choose from for purchasing documents. This table defines different sources for requisitions that can be imported into the Kuali Purchasing / Accounts Payable documents. |
|
Sensitive Data |
Defines why a Purchase Order document might be restricted from viewing. |
|
Vendor Stipulation |
Defines text to be included in purchase order documents that stipulates order conditions to vendors. |
Comments
0 comments
Please sign in to leave a comment.