# Infor VISUAL Database Table Reference > Source: https://netray.co/tools/visual-database-table-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A searchable lookup of the main VISUAL Manufacturing tables, what each holds and the usual join keys, for report writers and analysts. ## Category other-erp ## Erp Infor VISUAL ## Industry Discrete Manufacturing ## Audience - VISUAL administrator - Report writer - ERP analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Area **Key:** area **Type:** text #### What it holds **Key:** holds **Type:** text #### Typical key or join **Key:** keys **Type:** text **Rows:** **Table:** PART **Area:** Inventory **Holds:** Part master: description, planning and costing defaults, buy or make flags **Keys:** ID **Table:** PART_SITE **Area:** Inventory **Holds:** Site level part settings in multi site installations **Keys:** PART_ID, SITE_ID **Table:** PART_LOCATION **Area:** Inventory **Holds:** On hand quantity by warehouse and location **Keys:** PART_ID, WAREHOUSE_ID, LOCATION_ID **Table:** WAREHOUSE **Area:** Inventory **Holds:** Warehouse definitions **Keys:** ID **Table:** LOCATION **Area:** Inventory **Holds:** Bin or location definitions inside a warehouse **Keys:** WAREHOUSE_ID, ID **Table:** INVENTORY_TRANS **Area:** Inventory **Holds:** Inventory transaction history for issues, receipts and adjustments **Keys:** PART_ID, WORKORDER_BASE_ID **Table:** WORK_ORDER **Area:** Shop floor **Holds:** Work order header, status, quantities and dates **Keys:** TYPE, BASE_ID, LOT_ID, SPLIT_ID, SUB_ID **Table:** OPERATION **Area:** Shop floor **Holds:** Routing operations on a work order **Keys:** WORKORDER_BASE_ID and sequence number **Table:** REQUIREMENT **Area:** Shop floor **Holds:** Material requirements on a work order operation **Keys:** WORKORDER_BASE_ID, OPERATION_SEQ_NO, PIECE_NO **Table:** LABOR_TICKET **Area:** Shop floor **Holds:** Labor reporting against work orders **Keys:** EMPLOYEE_ID, WORKORDER_BASE_ID **Table:** SHOP_RESOURCE **Area:** Shop floor **Holds:** Machines and work centers used in routings **Keys:** ID **Table:** CUSTOMER **Area:** Sales **Holds:** Customer master **Keys:** ID **Table:** CUSTOMER_ORDER **Area:** Sales **Holds:** Customer order header **Keys:** ID **Table:** CUST_ORDER_LINE **Area:** Sales **Holds:** Customer order lines **Keys:** CUST_ORDER_ID, LINE_NO **Table:** CUST_LINE_DEL **Area:** Sales **Holds:** Scheduled delivery releases for a customer order line **Keys:** CUST_ORDER_ID, CUST_ORDER_LINE_NO **Table:** SHIPPER **Area:** Sales **Holds:** Shipment header **Keys:** PACKLIST_ID **Table:** SHIPPER_LINE **Area:** Sales **Holds:** Shipment lines linked to order lines **Keys:** PACKLIST_ID, LINE_NO **Table:** VENDOR **Area:** Purchasing **Holds:** Vendor master **Keys:** ID **Table:** PURCHASE_ORDER **Area:** Purchasing **Holds:** Purchase order header **Keys:** ID **Table:** PURC_ORDER_LINE **Area:** Purchasing **Holds:** Purchase order lines **Keys:** PURC_ORDER_ID, LINE_NO **Table:** RECEIVER **Area:** Purchasing **Holds:** Receiving document header **Keys:** ID **Table:** DEMAND_SUPPLY_LINK **Area:** Planning **Holds:** Links supply such as work orders and purchase orders to the demand they cover **Keys:** supply and demand base ids **Table:** RECEIVABLE **Area:** Finance **Holds:** Accounts receivable invoices **Keys:** INVOICE_ID **Table:** PAYABLE **Area:** Finance **Holds:** Accounts payable invoices **Keys:** VOUCHER_ID **Notes:** Table names are shown as commonly seen in VISUAL Manufacturing databases. Column sets differ by version and customisation, so confirm names against your own database with a read only login before putting them in a production report. ## Content **Intro:** Anyone writing a Crystal report or SQL query against VISUAL needs to know which table holds what. This reference lists the tables most reports touch, grouped by area, with the usual keys. Search by table name or by topic and export the list. **Sections:** #### How to use the table list **Body:** Type a word such as order, labor or vendor in the search box to narrow the list. The Typical key column shows what you normally join on. Start from the header table for the document you care about, then step down to its lines or operations. Export to Excel if you want to annotate the list with your own custom tables and user defined fields for onboarding a new report writer. **Bullets:** - Search by area to see all shop floor tables together - Check keys before joining to avoid duplicate rows - Add your own notes in the Excel export #### How the shop floor tables fit together **Body:** A work order is identified by a composite of type, base id, lot, split and sub id, which is why joins between WORK_ORDER, OPERATION and REQUIREMENT need several columns. Operations hang off the work order, and material requirements hang off an operation. Labor tickets and inventory transactions point back to the work order base id. Missing a key column in the join is the most common reason a report shows multiplied quantities. #### Common reporting mistakes **Body:** Reports go wrong in a few predictable ways. Joining on the base id alone ignores lot and split, so quantities repeat. Reading a header status without filtering for closed or cancelled documents inflates open counts. Querying live tables with heavy joins during shift hours slows the shop floor, so run large extracts on a replica or off hours. **Bullets:** - Use all key columns for work order joins - Filter by status explicitly - Prefer a read only login - Document user defined fields separately **Cta:** If your team keeps rebuilding the same VISUAL reports, we can set up a read only natural language layer over the database so analysts can ask for them directly. **Faq:** #### Are these the exact names in every VISUAL version? **Answer:** They are the names commonly seen, but versions and customisations differ. Treat the list as a starting map and confirm against your own database with a schema query before relying on a column name in production. #### Where do user defined fields live? **Answer:** VISUAL stores user defined fields in a separate user data structure keyed to the parent record rather than as columns on the table. Check your version documentation for the exact table and how it relates to each parent record. #### Can I write to these tables directly? **Answer:** Avoid it. Direct writes bypass the application business logic, costing and audit trail. Use the application, its supported import tools or the vendor API, and keep reporting logins read only. #### Does this work for Crystal Reports? **Answer:** Yes. Crystal reports connect to the same SQL Server database, so the table names and join keys apply. Use a command object or a view if you want to share a tested join across several reports. ## Search terms visual manufacturing database tables, infor visual table names, visual manufacturing sql tables, visual work_order table, visual customer_order table, visual manufacturing data dictionary, visual crystal reports tables, infor visual schema --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json