...
The RM-Order Cluster covers approximately XX reports (REP-XXX issues) that provide Resource Management data on library expenditures.
-(later) create a "what have I not paid for this year?" report based on all open orders from the po query and po_line ids that do not exist yet from the invoice query
The purpose of this report is to (purpose)
Data Fields
...
provide details about each purchase order with filtering by date and/or order type.
-use the PO Line ID to connect to the PO Lines table
-on PO Lines table, pull reporting codes, tags, acquisition method (shows firm vs approvals, etc.), description, details (subscription, may show whether subscription or firm order)
-connect from PO lines to Orders table (see po_lines:id description) and then to Order Lines table (see orders:id description)
-from Orders, pull acqUnitids, order type (firm or subscription)
-from Order Lines table, acquisition method, material type, poLineNumber, instanceId, agreementId, purchaseOrderID
-leave funds out for now
Data Fields
MAIN TABLES AND COLUMNS INCLUDED
--
PO_LINES
-purchase order line id
-purchase_order_number from po_lines_id
-tags (data array)
-description
-acquisition method
-subscription from and subscription to (json extract text - see "interesting times" data row)
-material type (derived table)
-instanceid
-agreementid
---
PO_PURCHASE_ORDERS
-order_type
-approval_date
-renewal_date
-workflow-status (filter)
-acquisition_unit_ids (data array)
-updated date and created date (data array from po_purchase_order)
-subtotal
-invoice_id
-invoice_line_number
-po_line_id
(from invoices?)
--
---
Report Criteria
Filters
--
Information Resources
See the Data Dictionary FOLIO Schema Parser for details on data elements
See the ACRL Diagram for tables and fields related to this report cluster
...