Dataset: Purchase Orders And Contracts

About this Dataset

Purchase Orders And Contracts

Listing of all purchase orders and contracts issued to procure goods and/or services within City-Parish. In the City-Parish, a PO/Contract is made up of two components: a header and one or many detail items that comprise the overarching PO/Contract. The header contains information that pertains to the entire PO/Contract. This includes, but is not limited to, the total amount of the PO/Contract, the department requesting the purchase and the vendor providing the goods or services. The detail item(s) contain information that is specific to the individual item ordered or service procured through the PO/Contract. The item/service description, item/service quantity and the cost of the item is located within the PO/Contract details. There may be one or many detail items on an individual PO/Contract. For example, a Purchase Order for a computer equipment may include three items: the computer, the monitor and the base software package. Both header information and detail item information are included in this dataset in order to provide a comprehensive view of the PO/Contract data. The Record Type field indicates whether the record is a header record (H) or detail item record (D). In the computer purchase example from above, the system would display 4 records – one header record and 3 detail item records. It should be noted header information will be duplicated on all detail items. No detail item information will be displayed on the header record. ***In October of 2017, the City-Parish switched to a new system used to track PO/Contracts. This data contains all PO/Contracts entered in or after October 2017. For prior year data, please see the Legacy Purchase Order dataset https://data.brla.gov/Government/Legacy-Purchase-Orders/54bn-2sqf
Organization: City of Baton Rouge
Last updated: 2020-11-12T14:59:46.178009
Tags: contracts, procurement, purchase-orders, purchasing

Tables

Table 1

@usgov.city_of_baton_rouge_purchase_orders_and_contracts.table_1

27.19 MB
296603 rows
53 columns


CREATE TABLE table_1 (
  "record_type" VARCHAR,
  "document_number" BIGINT,
  "source_document_type" VARCHAR,
  "document_description" VARCHAR,
  "requisition_number" BIGINT,
  "input_date" TIMESTAMP,
  "total_amount" DOUBLE,
  "department_number" DOUBLE,
  "department_name" VARCHAR,
  "cost_center" DOUBLE,
  "cost_center_name" VARCHAR,
  "document_type_code" VARCHAR,
  "document_type_description" VARCHAR,
  "document_status_code" BIGINT,
  "document_status_description" VARCHAR,
  "vouched_amount" DOUBLE,
  "start_date" TIMESTAMP,
  "expiration_date" TIMESTAMP,
  "extension_date" TIMESTAMP,
  "annual_contract" DOUBLE,
  "vendor_name_1" VARCHAR,
  "vendor_name_2" VARCHAR,
  "vendor_city" VARCHAR,
  "vendor_state" VARCHAR,
  "vendor_zip" VARCHAR,
  "vendor_type" VARCHAR,
  "gender" VARCHAR,
  "ethnicity" VARCHAR,
  "status" VARCHAR,
  "class" VARCHAR,
  "geographic_area" VARCHAR,
  "independent_contractor" VARCHAR,
  "minority" VARCHAR,
  "disadvantaged" VARCHAR,
  "disabled_veteran" VARCHAR,
  "sb_disabled_vet" VARCHAR,
  "sb_minority" VARCHAR,
  "sb_minority_woman" VARCHAR,
  "sb_non_minority" VARCHAR,
  "sb_disadvantaged" VARCHAR,
  "sb_veteran" VARCHAR,
  "sb_woman" VARCHAR,
  "total_items" BIGINT,
  "item_number" BIGINT,
  "item_description" VARCHAR,
  "item_quantity_ordered" DOUBLE,
  "item_unit_of_measure" VARCHAR,
  "item_unit_cost" DOUBLE,
  "item_total_cost" DOUBLE,
  "commodity_code" DOUBLE,
  "commodity_description" VARCHAR,
  "expense_type" DOUBLE,
  "expense_type_description" VARCHAR
);