Configuring PM Company Parameters

PM Company Parameters sets company-level Project Management controls before any PM processing. One record per HQ company that will run PM. Options govern which PM forms are used, how they behave, and what updates Job Cost, Job Billing, Subcontract Ledger, Inventory, Material Sales, and Requisitions. Restrict this form to the system administrator.

Help title is PM Company Parameters Form (field-def intro sometimes mislabels it “PR”). There is no separate numbered setup procedure — configure the form and field definitions.

Before you start

• PM Company already exists in HQ Companies.
• Understand each option’s impact before changing it after go-live (stored data / processing can be affected). Contact Support if impact on existing data is unclear.
• Related masters exist as needed: add-ons, status IDs, document types, Create & Send templates, firms — maintained on their own forms, not invented here.
• Workflow tab only if Workflow / Process Workflow is in use.

Steps

1. Open PM Company Parameters for the HQ company.
2. Set module interfaces and linked companies (Info / header fields).
3. Configure SL / PO / MO numbering.
4. Set document status defaults, Document Templates, and Workflow (if used).
5. Set Audit and Document History options.
6. Complete Job / SL / material cost-type and projection options.
7. Save. Repeat for each PM company before processing.

Interfaces / linked companies

Option	Role
AP In Use / AP Co#	AP company updated by PM Interface; validates vendors. Clear if AP not used.
SL In Use	SL company = same as AP Co# (no separate SL company field).
PO In Use	PO company = same AP Co#. PO Requisitions In Use enables Material Type R-Requisition on Non-Interfaced.
IN In Use / IN Co#	Inventory company for PM Interface; validates locations/materials.
MS In Use / MS Co#	Material Sales company for PM Interface.
PR In Use / PR Co#	PR company used to initialize “Our Firm” contacts in PM Firm Contacts. Other PR defaults in PM use the JC company’s PR company.
EM In Use / EM Co#	EM company updated by PM Interface.
Our Firm #	PM firm that represents this company (PM Firms).
Allow Update from AP	PM Firm changes update AP Vendors only for firms linked via Vendor. Typically also enable Allow Add from PM and Allow Update from AP on AP Company Parameters Audit Options.
Lock down ACO Items after Interface	After PM Interface creates the JC Change Order, ACO items cannot be edited and new items cannot be added on that interfaced ACO. Edits otherwise do not auto-update JC — rerun PM Interface. Amount changes need a new ACO.

SL / PO / MO numbering

• SL Number Type: Project/Sequence or Project/Vendor.
• PO Number Type: Project/Seq, Project/Vendor, or Auto-Number (requires PO Company Parameters Automatically Generate PO #s and a Last Used PO #).
• MO Number Type: Project/Seq or Auto-Number (requires IN Company Parameters Auto Generate MO #s and Last Used MO #).
• Significant part of job (SL and PO): checked = only first N job characters must match so items can land on an existing subcontract/PO for the same vendor; unchecked = entire job must match.
• Character limits (dashes kept; read project left-to-right): SL Project Characters ≤ 10; SL project+sequence ≤ 30; SL Vendor Characters 1–8 and project+vendor ≤ 18. PO Vendor Characters 1–9 (vendor digits right-to-left). MO project+sequence ≤ 10.
• Starting sequence is per project, not company-wide. Same project + same vendor merges items onto one subcontract/PO.
• Add items to approved POs/MOs not interfaced: checked = init can add to approved non-interfaced docs (else creates new); unchecked = only non-approved non-interfaced. MO grouping also follows Group materials by location when initializing.

Document defaults, templates, workflow

• Default Beginning Status (PCOs, PCO items, submittals, CORs, other; blank → first Beginning status for the type), Default Final Status (PCO approval / ACO / SubCOs / POCOs; Final type only), Default RFI Beginning Status.
• Document Tracking View default (blank = standard; override via Options → Change Document Tracking View).
• Document Templates: Document Type + Default Template (Create & Send). Company templates apply to all projects; project templates always override company templates.
• Workflow: one process per document type (PO or SL); Active applies when new POs/subcontracts are created; overridable per project. Assigned workflows land on WF Workflow Process Assigned Companies as module JC (not PM) and override HQ Company Setup workflow.

Audit, history, job/SL links, projections

• HQ Master Audit: Company Parameters always audited. Optional audit for daily logs, add-ons, locations, markups, firms, notes, meeting minutes, subcontract/material detail, issues, budgets, etc.
• Document History Options create history on add/change/delete for listed document types — they do not control whether PM Document Tracking tracks the category.
• SL/material: default item description from phase description; SL/Material Cost Type 1/2; Auto-Add Cost Type From Subcontract/Material (No / With Estimates / With No Estimates); Show CT Column 1–10 on PM Project Phases.
• Company add-ons inherit to new projects and copy onto PCOs (PM Company Add-ons).
• Projections do not sync with JC Company Parameters. Projection Method: Actual Costs vs Actual + Committed Costs (overridable at entry). Also min projection %, inactive phases/CTs, forecast posting, multiple open projections in a month, detail feature, revenue projections, remaining units/unit cost, columns, spread. Legacy = JC Cost Projections before 6.8; enhanced = PM Cost Projections from 6.8.

Hard rules

• Required before processing for each PM company.
• Interfaced ACO edits do not update JC until PM Interface reruns (unless lock-down — then issue a new ACO).
• Using Review Workflow Notifier Queries: checked without queries set up → no PO/SL review notifications; unchecked while using queries → both system and notifier emails (PMDocumentApprovalList, PMReviewedDocumentList).
• Allow adding new subcontract item during subcontract change order entry is intended for Australian pre-billing of SL change orders; US/Canada generally leave it off. When on, new items can be added on an Open subcontract from a pending/approved CO at 0.00 for invoice before SL interface.
• Attach batch reports to HQ Batch Control uses DM Attachment Options; export failure aborts posting.

Notes

• Related: PM Company Add-ons, PM Document Types, PM Status IDs, PM Firms / Firm Contacts, PM Create & Send Templates, PM Projects / Project Phases, PCOs / ACOs, PM Interface, PM Cost Projections, WF Workflow Process, HQ/JC/AP/PO/IN Company Parameters.