Difference between revisions of "Glossary"

From SVContheGO Online Manual
Jump to navigation Jump to search
m
m
Line 82: Line 82:
 
     |-
 
     |-
 
     |  
 
     |  
     The agreement frequency indicates the frequency used when billing the agreement.  
+
     The billing frequency.
  
  
Line 327: Line 327:
 
     |  
 
     |  
 
     The status code is used to track the agreements progress through the renewal process.
 
     The status code is used to track the agreements progress through the renewal process.
 +
 
     |-
 
     |-
 
     | <div id="AgreementType">&nbsp;</div>  
 
     | <div id="AgreementType">&nbsp;</div>  
 
     |-
 
     |-
     | Agreement Type
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type</div>   
 
     |-
 
     |-
 
     |  
 
     |  
 
     Used to organize agreements by type.  Agreement types are also used to establish setting for agreements by default.  
 
     Used to organize agreements by type.  Agreement types are also used to establish setting for agreements by default.  
 
     |-
 
     |-
     | <div id="Allocation">&nbsp;</div>  
+
     | <div id="agreeType_Code">&nbsp;</div>  
 
     |-
 
     |-
     | Allocation
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Code</div>   
 
     |-
 
     |-
 
     |  
 
     |  
     Displays the allocation assigned to the selected agreement type.  
+
     The code used to identify the agreement type.
 
     |-
 
     |-
     | <div id="servicetype_AssignedBtn">&nbsp;</div>  
+
     | <div id="agreeType_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Assigned</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Description</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     When clicked, displays all items assigned to the selected record.
+
     The description used to identify the agreement type.
 
     |-
 
     |-
     | <div id="servicetype_NotAssingedBtn">&nbsp;</div>  
+
     | <div id="agreeType_coveredMths">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Not Assigned</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Contract Months</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     When clicked, displays all the records not assigned to the selected item.
+
     The number of months for new agreements.
 
 
 
 
 
     |-
 
     |-
     | <div id="chain_Name">&nbsp;</div>  
+
     | <div id="agreeType_coverparts">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Parts Checkbox</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Sites can grouped by chain.
+
     When checked, the parts covered by the agreement will have no charge.
 
     |-
 
     |-
     | <div id="chain_Name">&nbsp;</div>  
+
     | <div id="agreeType_coverLabor">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Name</div>      
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Labor Checkbox</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The name used to identify the chain.
+
     When checked, the parts covered by the agreement will have no charge.
 
     |-
 
     |-
     | <div id="chain_SLA">&nbsp;</div>  
+
     | <div id="agreeType_SLA">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: SLA</div>        
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Checkbox</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates the chain is an SLA chain. SLA chains have a expiration time for when the work is expected to be completed.
+
     Check this box, if the agreement qualifies for SLA service.  
 
     |-
 
     |-
     | <div id="chain_Inbound">&nbsp;</div>  
+
     | <div id="agreeType_SLAPC">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Inbound Path</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Priority Code</div>    
 
     |-
 
     |-
 
     |  
 
     |  
 
+
    The SLA qualified priority code to use for new agreements.
 
     |-
 
     |-
     | <div id="chain_Outbound">&nbsp;</div>  
+
     | <div id="agreeType_Message">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Outbound Path</div>      
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type:Message </div>    
 
     |-
 
     |-
 
     |  
 
     |  
 
+
    This message will appear on the agreement.
 
     |-
 
     |-
     | <div id="chain_storeTypeCode">&nbsp;</div>  
+
     | <div id="agreeType_LaborHoursBudget">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Code</div>      
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Labor Hours Budget</div>    
    | Store Type Code
 
 
     |-
 
     |-
     | Desc here
+
     |  
 +
    The budgeted number of labor hours.
 
     |-
 
     |-
     | <div id="chain_storeTypeName">&nbsp;</div>  
+
     | <div id="agreeType_PartsDollarsBudget">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Name</div>      
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Parts Dollars Budget</div>    
    | Store Type Name
 
 
     |-
 
     |-
     | Desc here
+
     |  
 
+
    The budgeted parts dollars.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="Classification">&nbsp;</div>  
+
     | <div id="agreeType_PercentUsed">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Classification</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Percent Used >=</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
+
     Percentage of labor budget used.
       
 
 
 
 
     |-
 
     |-
     | <div id="servicetype_RemoveallAssnBtn">&nbsp;</div>  
+
     | <div id="agreeType_DollarsUsed">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Remove all Assignments</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Dollars Used >=</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     When clicked, removes all assignments from the selected record.
+
     Percentage of parts dollars used.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_address">&nbsp;</div>  
+
     | <div id="agreeTypePIO_Billable">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Address</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Auto Number by Type</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     The contacts mailing address.
+
     When checked, new agreements will auto-number using the value int he Next Number field.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_City">&nbsp;</div>  
+
     | <div id="agreeTypePIO_Frequency">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: City</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Next Number</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The city of the mailing address.
+
     Used when auto-numbering agreements.  
 
 
 
     |-
 
     |-
     | <div id="contact_country">&nbsp;</div>  
+
     | <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Country</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Enforce Defaults</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The country of the mailing address.
+
     When checked, the agreement type defaults cannot be changed on the agreement.
 
 
 
     |-
 
     |-
     | <div id="contact_email">&nbsp;</div>  
+
     | <div id="agreeTypePIO_Billable">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Email</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Billable</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     The contact's email address.
+
     When checked, the agreements assigned to the agreement type will be billable by default.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_estDate">&nbsp;</div>  
+
     | <div id="agreeTypePIO_Frequency">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Established Date</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Frequency</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The date the contact record was established.
+
     The billing frequency.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_fax">&nbsp;</div>  
+
     | <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Fax Number</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Tax Class</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The contact's fax number.
+
     The tax class assigned to invoice billing invoices.
 
 
 
     |-
 
     |-
     | <div id="contact_firstName">&nbsp;</div>  
+
     | <div id="agreeTypePIO_Allocation">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: First Name</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Allocation</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The contact's first name.  
+
     The allocation that will be assigned used when processing agreements.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_lastName">&nbsp;</div>  
+
     | <div id="agreeTypePIO_DefRev">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Last Name</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Deferred Revenues</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     The contact's last name.
+
     When checked, new agreements will use the deferred revenue feature.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_ContactName">&nbsp;</div>  
+
     | <div id="agreeTypePIO_PricingMethod">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Name</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Pricing Method</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The contacts full name.
+
     The pricing method used when processing agreement transactions.  
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_WorkPhone">&nbsp;</div>  
+
     | <div id="agreeTypePIO_Price">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Phone</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Pricing</div>     
 
     |-
 
     |-
     |  
+
     | Agreement Type
    The contact's telephone number.
+
        Blanket: One price covers all items on the agreement.
 
+
        By Site: Each site can have a different price.
 
+
        By Equipment: Each equipment record can have a different price.
 
     |-
 
     |-
     | <div id="contact_Salutation">&nbsp;</div>  
+
     | <div id="agreeTypePIO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Salutation</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Details on Invoice</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The salutation that should be used when communicating with the contact.
+
     When checked, the site details will appear on agreement invoices.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_state">&nbsp;</div>  
+
     | <div id="agreeTypePIO_IncludeEquipDetailsonInvoice">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: State</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Details on Invoice</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The state of the mailing address.
+
     When checked, equipment details will appear on agreement invoices.
 
 
 
     |-
 
     |-
     | <div id="contact_Title">&nbsp;</div>  
+
     | <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Title</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Summary on Invoice</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The contact title. ex: Mr., Mrs.
+
     When checked, a site summary will appear on agreement invoices.
 
+
     |-
 
+
     | <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
     |-
 
     | <div id="contact_Type">&nbsp;</div>  
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Summary on Invoice</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Types can be used to organize contacts.
+
     When checked, an equipment summary will appear on agreement invoices.
 
 
 
 
 
     |-
 
     |-
     | <div id="contact_zip">&nbsp;</div>  
+
     | <div id="agreeTypePRO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Zip</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewable Checkbox</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The postal code of the mailing address.
+
     When checked, the agreement will be marked renewable on creation.
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="CostType">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Months">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewal Months</div>
 
     |-
 
     |-
 
     |  
 
     |  
     Cost types are used to manage general ledger sales and cost account allocations on transactions and billing.
+
     The number of default renewal months on new agreements.
 
 
 
 
 
     |-
 
     |-
     | <div id="costtype_CostAcct">&nbsp;</div>  
+
     | <div id="agreeTypePRO_AS">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Account</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renew As</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The cost account that will be assigned to transactions assigned this job type and cost type.  
+
     The default renew as value for new agreements.
 
 
 
     |-
 
     |-
     | <div id="costtype_CostSubacct">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Include_Site_Details_on_Renewal_Details">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Subaccount</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Details on Invoice</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The cost sub-account that will be assigned to transactions assigned this job type and cost type.  
+
     When checked, the site details will appear on renewal invoices.
 
 
 
     |-
 
     |-
     | <div id="costtype_Desc">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Description</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Details on Invoice</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Used to describe the cost type.  
+
     When checked, equipment details will appear on renewal invoices.
 
+
    |-
 
+
    | <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Summary on Invoice</div> 
 +
    |-
 +
    |
 +
    When checked, a site summary will appear on renewal invoices.
 
     |-
 
     |-
     | <div id="costtype_InventoryCB">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Inventory Checkbox</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Summary on Invoice</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates that the cost type can be used for inventory transactions.  
+
     When checked, an equipment summary will appear on renewal invoices.
 +
 
 +
 
  
  
 
     |-
 
     |-
     | <div id="costtype_LaborCB">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Labor Checkbox</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create a Job for each Equipment</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates that the cost type can be used for labor transactions.  
+
     When checked, planned maintenance will create a separate job for each equipment record assigned to the schedule.
 
 
 
 
 
     |-
 
     |-
     | <div id="costtype_PurchasesCB">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Purchases Checkbox</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create Transactions</div>
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates that the cost type can be used for purchase transactions.  
+
     When checked, planned maintenance will automatically add the transactions to the generated jobs.
 
 
 
 
 
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customeraccountmanager">&nbsp;</div>  
+
     | <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Account Manager</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Price Transactions</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The company representative that manages the customer's account.
+
     When checked, planned maintenance will add the transactions, with pricing, to the generated jobs.
  
  
 
     |-
 
     |-
     | colspan="1" style="width: 706px;" | <div id="customeraddress">&nbsp;</div>  
+
     | <div id="Allocation">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Address</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's mailing address.   
+
     Allocations are used to distribute the agreement dollars to the required general ledger accounts.   
 
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerbillingcontact">&nbsp;</div>  
+
     | <div id="alloc_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Billing Contact</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Description</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The primary billing contact assigned to the customer.  
+
     The description used to identify the allocation.
 
 
 
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customercity">&nbsp;</div>  
+
     | <div id="alloc_revType">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: City</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Revenue Type</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's mailing address city.
+
     Indicates if the allocation will be a percentage or fixed amount.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customercountry">&nbsp;</div>  
+
     | <div id="alloc_pricingMethod">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Country</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Pricing Method</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's mailing address country.
+
     Agreements can be priced based on the different methods. Allocations define the price method the can be assigned in agreement types.
 +
        Blanket: One price covers all items on the agreement. 
 +
        By Site: Each site can have a different price.
 +
        By Equipment: Each equipment record can have a different price.  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customeremail">&nbsp;</div>  
+
     | <div id="alloc_price">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Email</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Price</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The email address for the primary customer contact.
+
     The allocation price. 
 +
        Blanket - Enter one price for the entire contract.
 +
        By Site - Enter the price for each site.
 +
        By Equipment - Enter ethe price for each equipment.  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerext">&nbsp;</div>  
+
     | <div id="alloc_Type">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Ext</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Type</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The main telephone numbers extension.
+
     The type of general ledger entry.
 +
        Deferred Revenue: Posts to a deferred revenue account.
 +
        Revenue: Post to a sales revenue account.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerfacebook">&nbsp;</div>  
+
     | <div id="alloc_miscItem">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Facebook</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Miscellaneous Item</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Link to the customer's Facebook account.
+
     The miscellaneous item to use when posting to the ERP system.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerfax">&nbsp;</div>  
+
     | <div id="alloc_Account">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Fax</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Allocations Account</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's contact fax number.
+
     The account that should be affected by the allocation transaction.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerlinkedin">&nbsp;</div>  
+
     | <div id="alloc_Amount">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: LinkedIn</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Amount</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's linked in accounnt handle.
+
     The amount of the allocation transaction.
 +
 
 
     |-
 
     |-
     | colspan="1" style="width: 706px;" | <div id="Cust_Name">&nbsp;</div>  
+
     | <div id="servicetype_AssignedBtn">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Name</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Assigned</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The name of the organization that will be billed.  Jobs can be created without a customer assignmnet, but not billed.  
+
     When clicked, displays all items assigned to the selected record.
 
     |-
 
     |-
     | colspan="1" style="width: 706px;" | <div id="customer_number">&nbsp;</div>  
+
     | <div id="servicetype_NotAssingedBtn">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Not Assigned</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
+
     When clicked, displays all the records not assigned to the selected item.
 +
 
 +
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerpricelevel">&nbsp;</div>  
+
     | <div id="chain_Name">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Price Level</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's price level.  Price level requirement is based on ERP settings.
+
     Sites can grouped by chain.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerphone">&nbsp;</div>  
+
     | <div id="chain_Name">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Phone</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Name</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's business telephone number.
+
     The name used to identify the chain.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customersalesperson">&nbsp;</div>  
+
     | <div id="chain_SLA">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Salesperson</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: SLA</div>        
 
     |-
 
     |-
 
     |  
 
     |  
     The salesperson assigned to the customer's account.  
+
     When checked, indicates the chain is an SLA chain. SLA chains have a expiration time for when the work is expected to be completed.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerstate">&nbsp;</div>  
+
     | <div id="chain_Inbound">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: State</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Inbound Path</div>    
 
     |-
 
     |-
 
     |  
 
     |  
    The customers address state.
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customertwitter">&nbsp;</div>  
+
     | <div id="chain_Outbound">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Twitter</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Outbound Path</div>      
 
     |-
 
     |-
 
     |  
 
     |  
    The customer's twitter handle.
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerzip">&nbsp;</div>  
+
     | <div id="chain_storeTypeCode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Zip Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Code</div>      
 +
    | Store Type Code
 
     |-
 
     |-
     |  
+
     | Desc here
    The customer's address zip code.
 
 
     |-
 
     |-
     | <div id="equip_code">&nbsp;</div>  
+
     | <div id="chain_storeTypeName">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Name</div>      
 +
    | Store Type Name
 
     |-
 
     |-
     |  
+
     | Desc here
    Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
+
 
     |-
+
 
     | <div id="equip_comment">&nbsp;</div>  
+
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
     |-
 +
     | <div id="Classification">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Comment</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Classification</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Comments related to the equipment record.
+
     The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
 +
       
 +
 
 
     |-
 
     |-
     | <div id="equip_coverageDate">&nbsp;</div>  
+
     | <div id="servicetype_RemoveallAssnBtn">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Coverage Date</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Remove all Assignments</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The date coverage begins for the equipment record.
+
     When clicked, removes all assignments from the selected record.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_description">&nbsp;</div>  
+
     | <div id="contact_address">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Description</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Address</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     Used to describe the equipment.
+
     The contacts mailing address.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_item">&nbsp;</div>  
+
     | <div id="contact_City">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Item</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: City</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     Equipment records that are also inventory items will have the Item Code in this field.  
+
     The city of the mailing address.
 +
 
 
     |-
 
     |-
     | <div id="equip_installdate">&nbsp;</div>  
+
     | <div id="contact_country">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Install Date</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Country</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The date the equipment was installed on site.
+
     The country of the mailing address.
  
 
     |-
 
     |-
     | <div id="equip_warrlabor">&nbsp;</div>  
+
     | <div id="contact_email">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Checkbox</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Email</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates the equipment is covered by a labor warranty.
+
     The contact's email address.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_warrlaborend">&nbsp;</div>  
+
     | <div id="contact_estDate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty End</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Established Date</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The date the labor warranty ends.
+
     The date the contact record was established.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_warrlaborstart">&nbsp;</div>  
+
     | <div id="contact_fax">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Start</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Fax Number</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The date the labor warranty begins.
+
     The contact's fax number.
 +
 
 
     |-
 
     |-
     | <div id="equip_level">&nbsp;</div>  
+
     | <div id="contact_firstName">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Level</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: First Name</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Levels are linked to models.  If the leve does not appear in the Level drop-list, check the selected models setup.
+
     The contact's first name.  
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_manufacturer">&nbsp;</div>  
+
     | <div id="contact_lastName">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Manufacturer</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Last Name</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The equipment's manufacturer.  Manufacturers are linked to the equipment type.  If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type.  
+
     The contact's last name.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_mode">&nbsp;</div>  
+
     | <div id="contact_ContactName">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Model</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Name</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The equipment model. Models are linked to a manufacturer.  If the model does not appear in the model drop-list, check the selected manufacturer's setup.  
+
     The contacts full name.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_warrparts">&nbsp;</div>  
+
     | <div id="contact_WorkPhone">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Checkbox</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Phone</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates the equipment is covered by a parts warranty.
+
     The contact's telephone number.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_warrpartsend">&nbsp;</div>  
+
     | <div id="contact_Salutation">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty End</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Salutation</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The date the parts warranty ends.
+
     The salutation that should be used when communicating with the contact.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_warrpartsstart">&nbsp;</div>  
+
     | <div id="contact_state">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Start</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: State</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The date the parts warranty begins.
+
     The state of the mailing address.
 +
 
 
     |-
 
     |-
     | <div id="equip_saledate">&nbsp;</div>  
+
     | <div id="contact_Title">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Sale Date</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Title</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The date the equipment was sold to the customer.
+
     The contact title. ex: Mr., Mrs.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_serialno">&nbsp;</div>  
+
     | <div id="contact_Type">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Serial Number</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Type</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The equipment's serial number. This is not required. 
+
     Types can be used to organize contacts.
  
  
 +
    |-
 +
    | <div id="contact_zip">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Zip</div>     
 +
    |-
 +
    |
 +
    The postal code of the mailing address.
  
  
  
 
     |-
 
     |-
     | <div id="equip_type">&nbsp;</div>  
+
     | <div id="CostType">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Equipment types are used to organize equipment.  Manufacturers are assigned by equipment type.  
+
     Cost types are used to manage general ledger sales and cost account allocations on transactions and billing.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="equip_positionLocation">&nbsp;</div>  
+
     | <div id="costtype_CostAcct">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Position/Locations</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Account</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Indicates the physical location.
+
     The cost account that will be assigned to transactions assigned this job type and cost type.  
 +
 
 
     |-
 
     |-
     | <div id="EQType_CODE">&nbsp;</div>  
+
     | <div id="costtype_CostSubacct">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Subaccount</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
+
     The cost sub-account that will be assigned to transactions assigned this job type and cost type.  
 +
 
 
     |-
 
     |-
     | <div id="EQType_CODE">&nbsp;</div>  
+
     | <div id="costtype_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Code</div>   
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Description</div>   
 
     |-
 
     |-
 
     |  
 
     |  
     The code that identifies the equipment type.
+
     Used to describe the cost type.  
 +
 
 +
 
 
     |-
 
     |-
     | <div id="EQType_Desc">&nbsp;</div>  
+
     | <div id="costtype_InventoryCB">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Description</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Inventory Checkbox</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The description used to identify the equipment type.  
+
     When checked, indicates that the cost type can be used for inventory transactions.  
 +
 
 +
 
 
     |-
 
     |-
     | <div id="EQType_Prefix">&nbsp;</div>  
+
     | <div id="costtype_LaborCB">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Prefix</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Labor Checkbox</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The three digit prefix to use when auto-numbering new equipment records.
+
     When checked, indicates that the cost type can be used for labor transactions.  
 +
 
 +
 
 
     |-
 
     |-
     | <div id="Commissionable">&nbsp;</div>  
+
     | <div id="costtype_PurchasesCB">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commissionable</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Purchases Checkbox</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     When checked the item is commissionable.
+
     When checked, indicates that the cost type can be used for purchase transactions.  
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="corep_commrate">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customeraccountmanager">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commission Rate</div>      
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Account Manager</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     If the representative is a salesperson, the commision rate is stored in this field.  
+
     The company representative that manages the customer's account.
 
 
  
  
 +
    |-
 +
    | colspan="1" style="width: 706px;" | <div id="customeraddress">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Address</div>
 +
    |-
 +
    |
 +
    The customer's mailing address. 
  
 
     |-
 
     |-
     | <div id="EQBuild">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerbillingcontact">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader"></div>Inventory: Equipment Build Checkbox</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Billing Contact</div>  
 
     |-
 
     |-
     | When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
+
     |  
        Prefix: Used when equipment auto-numbering is activated.
+
    The primary billing contact assigned to the customer.  
        [[Glossary#equip_type|EQ Type]]
+
 
        [[Glossary#equip_mode|Model]]
+
 
        [[Glossary#equip_manufacturer|Manufacturer]]
 
        Labor Warranty Period: The number of months for labor warranty coverage.
 
        Parts Warranty Period: The number of months for parts warranty coverage.
 
        [[Glossary#equip_comment|Comment]]
 
 
     |-
 
     |-
     | <div id="inv_ItemCode">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customercity">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Code</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: City</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Used to identify the item.  
+
     The customer's mailing address city.
 
     |-
 
     |-
     | <div id="inv_ItemDescription">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customercountry">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Description</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Country</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Describes the item. This information comes from the ERP system.
+
     The customer's mailing address country.
 
 
 
 
 
 
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="inv_ItemType">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customeremail">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Type</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Email</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Indicates the type of Item.
+
     The email address for the primary customer contact.
 
     |-
 
     |-
     | <div id="itemPrefix">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerext">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Prefix</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Ext</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Used for equipment auto numbering.  If a matrix is in use that calls for this prefix, the system will use the value in this field.  
+
     The main telephone numbers extension.
 
     |-
 
     |-
     | <div id="PriceCode">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerfacebook">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Price Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Facebook</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The item's price code. The price code is used when calculating transaction pricing.  
+
     Link to the customer's Facebook account.
 
     |-
 
     |-
     | <div id="ProductLine">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerfax">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Product Line</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Fax</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The item's product line.  
+
     The customer's contact fax number.
 
 
 
     |-
 
     |-
     | <div id="SalesUOM">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerlinkedin">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Sales UOM</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: LinkedIn</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The item's unit of measure.
+
     The customer's linked in accounnt handle.
 
     |-
 
     |-
     | <div id="MobileButton">&nbsp;</div>  
+
     | colspan="1" style="width: 706px;" | <div id="Cust_Name">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Inventory: Servicer Mobile Button</div>  
+
     | colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Name</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, a mobile button will be made available in mobile for quick entry.
+
     The name of the organization that will be billed.  Jobs can be created without a customer assignmnet, but not billed.  
 
     |-
 
     |-
     | <div id="shordesc">&nbsp;</div>  
+
     | colspan="1" style="width: 706px;" | <div id="customer_number">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Short Description</div>  
+
     | colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Number</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     A short description for the item.  
+
     Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
 
     |-
 
     |-
     | <div id="SplitCommission">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerpricelevel">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Split Commission</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Price Level</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, commission on the item can be slit.
+
     The customer's price level.  Price level requirement is based on ERP settings.
 
     |-
 
     |-
     | <div id="TradeDiscount">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerphone">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Trade Discount</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Phone</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, discounts are allowed.
+
     The customer's business telephone number.
 
     |-
 
     |-
     | <div id="unitcost">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customersalesperson">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Cost</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Salesperson</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The item's cost.  
+
     The salesperson assigned to the customer's account.  
 
     |-
 
     |-
     | <div id="UnitPrice">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerstate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Price</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: State</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The price for the item when added to a transaction.
+
     The customers address state.
 
     |-
 
     |-
     | <div id="UseinMobile">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customertwitter">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Inventory: Use in Mobile</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Twitter</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, the item will be available for use in mobile.  
+
     The customer's twitter handle.
 
     |-
 
     |-
     | <div id="Warehouse">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div id="customerzip">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Warehouse</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Zip Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The item's default warehouse.
+
     The customer's address zip code.
 
     |-
 
     |-
     | <div id="job_billed">&nbsp;</div>  
+
     | <div id="equip_code">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Billed Status</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Code</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     Indicates where the job is in the billing process.
+
     Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
 
     |-
 
     |-
     | <div id="job_contact">&nbsp;</div>  
+
     | <div id="equip_comment">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Comment</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The site or customer contact assigned to the job.  
+
     Comments related to the equipment record.
 
     |-
 
     |-
     | <div id="job_contactemail">&nbsp;</div>  
+
     | <div id="equip_coverageDate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact Email</div>
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Coverage Date</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The email address for the job contact.
+
     The date coverage begins for the equipment record.
 
     |-
 
     |-
     | <div id="job_ext">&nbsp;</div>  
+
     | <div id="equip_description">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Extension</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Description</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The extension number for the contact telephone number
+
     Used to describe the equipment.
 
     |-
 
     |-
     | <div id="jobtype_Code"></div>  
+
     | <div id="equip_item">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Job Type Code</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Item</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     Used to recognize the job type.
+
     Equipment records that are also inventory items will have the Item Code in this field.  
 
     |-
 
     |-
     | <div id="job_mainno">&nbsp;</div>  
+
     | <div id="equip_installdate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Main Number</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Install Date</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The job's main contact telephone number
+
     The date the equipment was installed on site.
 +
 
 
     |-
 
     |-
     | <div id="job_number">&nbsp;</div>  
+
     | <div id="equip_warrlabor">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Checkbox</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Used to identify the job.
+
     When checked, indicates the equipment is covered by a labor warranty.
 
     |-
 
     |-
     | <div id="job_pmtmethod">&nbsp;</div>  
+
     | <div id="equip_warrlaborend">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Payment Method</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty End</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The default payment method.
+
     The date the labor warranty ends.
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="job_phone">&nbsp;</div>  
+
     | <div id="equip_warrlaborstart">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Phone</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Start</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The contact telephone number for the job.  
+
     The date the labor warranty begins.
 
     |-
 
     |-
     | <div id="primaryservicer">&nbsp;</div>  
+
     | <div id="equip_level">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Primary Servicer</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Level</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The primary servicer for the job. New jobs will automatically use the primary servicer.
+
     Levels are linked to models.  If the leve does not appear in the Level drop-list, check the selected models setup.
 
     |-
 
     |-
     | <div id="job_receiveddate">&nbsp;</div>  
+
     | <div id="equip_manufacturer">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Date</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Manufacturer</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The date the job was received from the customer.  
+
     The equipment's manufacturer.  Manufacturers are linked to the equipment type.  If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type.  
 
     |-
 
     |-
     | <div id="job_refno">&nbsp;</div>  
+
     | <div id="equip_mode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Reference Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Model</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The default payment reference number.
+
     The equipment model. Models are linked to a manufacturer.  If the model does not appear in the model drop-list, check the selected manufacturer's setup.  
 
 
 
 
 
     |-
 
     |-
     | <div id="job_saleperson">&nbsp;</div>  
+
     | <div id="equip_warrparts">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Salesperson</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Checkbox</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The salesperson for the job.  *Certain ERP systems require a salesperson.
+
     When checked, indicates the equipment is covered by a parts warranty.
 
 
 
     |-
 
     |-
     | <div id="job_sendtomobile">&nbsp;</div>  
+
     | <div id="equip_warrpartsend">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Job: Send to Mobile Checkbox</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty End</div>  
 
     |-
 
     |-
     | On save, if this checkbox is checked, the job will be made available in mobile.  
+
     |  
 
+
    The date the parts warranty ends.
 
 
 
     |-
 
     |-
     | <div id="job_servicetype">&nbsp;</div>  
+
     | <div id="equip_warrpartsstart">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Service Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Start</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Service types are used to organize jobs. Service type are organized by job type.
+
     The date the parts warranty begins.
 
 
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="job_sla">&nbsp;</div>  
+
     | <div id="equip_saledate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Checkbox</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Sale Date</div>
 
     |-
 
     |-
 
     |  
 
     |  
     Check this box, if the job qualifies for SLA service. This defaults from the site.
+
     The date the equipment was sold to the customer.
 
     |-
 
     |-
     | <div id="job_slaExp">&nbsp;</div>  
+
     | <div id="equip_serialno">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Date</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Serial Number</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The date the technician has to start the work in order to meet the SLA criteria.
+
     The equipment's serial number. This is not required. 
    |-
+
 
    | <div id="job_slaExpTime">&nbsp;</div>
+
 
    |-
 
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Time</div>
 
    |-
 
    |
 
    The time the technician has to start the work in order to meet the SLA criteria.
 
  
  
  
 
     |-
 
     |-
     | <div id="job_status">&nbsp;</div>  
+
     | <div id="equip_type">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Status</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Type</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Status codes are used to determine the job's position in the work process.  
+
     Equipment types are used to organize equipment.  Manufacturers are assigned by equipment type.  
 
     |-
 
     |-
     | <div id="job_statusbar">&nbsp;</div>  
+
     | <div id="equip_positionLocation">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Job: Status Bar</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Position/Locations</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The status bar indicates the job's status progress.
+
     Indicates the physical location.
   
 
 
 
 
     |-
 
     |-
     | <div id="jobtype_Desc">&nbsp;</div>  
+
     | <div id="EQType_CODE">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Description</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Used to describe the job type.  
+
     Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
 
     |-
 
     |-
     | <div id="EstHours">&nbsp;</div>  
+
     | <div id="EQType_CODE">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Estimated Hours</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The hours estimated to complete the job.  
+
     The code that identifies the equipment type.
 
     |-
 
     |-
     | <div id="jobType">&nbsp;</div>  
+
     | <div id="EQType_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type</div>    
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Description</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions.  
+
     The description used to identify the equipment type.  
 
     |-
 
     |-
     | <div id="KPICallCount">&nbsp;</div>  
+
     | <div id="EQType_Prefix">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: KPI Call Count Checkbox</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Prefix</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     When checked the jobs assigned the job type will be counted in the KPI analytics.
+
     The three digit prefix to use when auto-numbering new equipment records.
 
     |-
 
     |-
     | <div id="Opportunity">&nbsp;</div>  
+
     | <div id="Commissionable">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Opportunity</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commissionable</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Marks the job type as a job opportunity.
+
     When checked the item is commissionable.
 
     |-
 
     |-
     | <div id="QuotedDollars">&nbsp;</div>  
+
     | <div id="corep_commrate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Quoted $s</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commission Rate</div>      
 
     |-
 
     |-
 
     |  
 
     |  
     The dollars quoted for the job.  
+
     If the representative is a salesperson, the commision rate is stored in this field.  
 +
 
 +
 
 +
 
  
 
     |-
 
     |-
     | <div id="level_Code">&nbsp;</div>  
+
     | <div id="EQBuild">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader"></div>Inventory: Equipment Build Checkbox</div>
 
     |-
 
     |-
     |  
+
     | When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
    Models can be grouped by levels. Levels can be grouped by type.
+
        Prefix: Used when equipment auto-numbering is activated.
 +
        [[Glossary#equip_type|EQ Type]]
 +
        [[Glossary#equip_mode|Model]]
 +
        [[Glossary#equip_manufacturer|Manufacturer]]
 +
        Labor Warranty Period: The number of months for labor warranty coverage.
 +
        Parts Warranty Period: The number of months for parts warranty coverage.
 +
        [[Glossary#equip_comment|Comment]]
 
     |-
 
     |-
     | <div id="level_Code">&nbsp;</div>  
+
     | <div id="inv_ItemCode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Code</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The code used to identify the level.  
+
     Used to identify the item.  
 
     |-
 
     |-
     | <div id="level_Desc">&nbsp;</div>  
+
     | <div id="inv_ItemDescription">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Description</div>   
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Description</div>   
 
     |-
 
     |-
 
     |  
 
     |  
     The description that identifies the level.
+
     Describes the item. This information comes from the ERP system.
     |-
+
 
     | <div id="level_prefix">&nbsp;</div>  
+
 
 +
 
 +
 
 +
 
 +
 
 +
     |-
 +
     | <div id="inv_ItemType">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Prefix</div>   
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Type</div>   
 
     |-
 
     |-
 
     |  
 
     |  
     The three digit prefix to use when auto-numbering new equipment records.
+
     Indicates the type of Item.
 
     |-
 
     |-
     | <div id="levelType">&nbsp;</div>  
+
     | <div id="itemPrefix">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Type</div>   
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Prefix</div>   
 
     |-
 
     |-
 
     |  
 
     |  
     Level types are used to group levels.
+
     Used for equipment auto numbering.  If a matrix is in use that calls for this prefix, the system will use the value in this field.  
 
 
 
     |-
 
     |-
     | <div id="Location">&nbsp;</div>  
+
     | <div id="PriceCode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Location</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Price Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Indicates the phusical location of a piece of equipment at a site.
+
     The item's price code. The price code is used when calculating transaction pricing.  
 
 
 
 
 
     |-
 
     |-
     | <div id="Manufacturer">&nbsp;</div>  
+
     | <div id="ProductLine">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Product Line</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The manufacturer is assigned to equipment records. The manufacturer is assigned models. 
+
     The item's product line.  
 +
 
 
     |-
 
     |-
     | <div id="Manu_Code">&nbsp;</div>  
+
     | <div id="SalesUOM">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Sales UOM</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The code used to identify the manufacturer.
+
     The item's unit of measure.
 
     |-
 
     |-
     | <div id="Manu_Desc">&nbsp;</div>  
+
     | <div id="MobileButton">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Description</div>  
+
     | <div class="fieldHeader">Inventory: Servicer Mobile Button</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The description that identifies the manufacturer.
+
     When checked, a mobile button will be made available in mobile for quick entry.
 
     |-
 
     |-
     | <div id="Manu_Prefix">&nbsp;</div>  
+
     | <div id="shordesc">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Prefix</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Short Description</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The three digit prefix to use when auto-numbering new equipment records.
+
     A short description for the item.  
 
 
 
     |-
 
     |-
     | <div id="model_Code">&nbsp;</div>  
+
     | <div id="SplitCommission">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Split Commission</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The code used to identify the model.
+
     When checked, commission on the item can be slit.
 
     |-
 
     |-
     | <div id="model_Desc">&nbsp;</div>  
+
     | <div id="TradeDiscount">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Description</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Trade Discount</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The description that identifies the model.
+
     When checked, discounts are allowed.
 
     |-
 
     |-
     | <div id="model_prefix">&nbsp;</div>  
+
     | <div id="unitcost">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Prefix</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Cost</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     The three digit prefix to use when auto-numbering new equipment records.
+
     The item's cost.  
 
 
 
 
 
 
 
 
 
     |-
 
     |-
     | <div id="Priority">&nbsp;</div>  
+
     | <div id="UnitPrice">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Price</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The default priority that will be used when creating new jobs to establish schedule date and time.  Priorities are assigned to sites as a default for new jobs.  
+
     The price for the item when added to a transaction.
 
 
 
     |-
 
     |-
     | <div id="PriorityCode">&nbsp;</div>  
+
     | <div id="UseinMobile">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Code</div>  
+
     | <div class="fieldHeader">Inventory: Use in Mobile</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Priority codes are used to establish the response time when scheduling jobs.
+
     When checked, the item will be available for use in mobile.  
 
 
 
     |-
 
     |-
     | <div id="prio_dow">&nbsp;</div>  
+
     | <div id="Warehouse">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Day of the Week</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Warehouse</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates that jobs can be schedules on that day of the week.
+
     The item's default warehouse.
 
+
    |-
 +
    | <div id="job_billed">&nbsp;</div>
 
     |-
 
     |-
     | <div id="">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Billed Status</div>  
 
     |-
 
     |-
     | &nbsp;
+
     |  
 +
    Indicates where the job is in the billing process.
 
     |-
 
     |-
     | <div id="prio_Desc">&nbsp;</div>  
+
     | <div id="job_contact">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Description</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact</div>
 
     |-
 
     |-
 
     |  
 
     |  
     Describe the priority.
+
     The site or customer contact assigned to the job.  
 
     |-
 
     |-
     | <div id="prio_endtime">&nbsp;</div>  
+
     | <div id="job_contactemail">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: End Time</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact Email</div>
 
     |-
 
     |-
 
     |  
 
     |  
     Indicates the latest time a job can be scheduled on each day of the week.
+
     The email address for the job contact.
 
     |-
 
     |-
     | <div id="ResponseTime">&nbsp;</div>  
+
     | <div id="job_ext">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Response Time</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Extension</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Indicates the number of hours between the received time and the schedule time.
+
     The extension number for the contact telephone number
 
     |-
 
     |-
     | <div id="prio_SLA">&nbsp;</div>  
+
     | <div id="jobtype_Code"></div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Job Type Code</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
+
     Used to recognize the job type.
 
     |-
 
     |-
     | <div id="prio_SLAExp">&nbsp;</div>  
+
     | <div id="job_mainno">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA Expiration</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Main Number</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The number of hours that are required to meet the SLA deadline.
+
     The job's main contact telephone number
 
     |-
 
     |-
     | <div id="prio_starttime">&nbsp;</div>  
+
     | <div id="job_number">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Start Time</div>     
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Number</div>     
 
     |-
 
     |-
 
     |  
 
     |  
     Indicated the earliest time a job can be scheduled on each day of the week.
+
     Used to identify the job.
 
 
 
     |-
 
     |-
     | <div id="ReportingGroups">&nbsp;</div>  
+
     | <div id="job_pmtmethod">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Reporting Groups</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Payment Method</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     A group code can be assigned to a miscellaneous charge code to group like Item codes.  
+
     The default payment method.
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="corep_repaddress">&nbsp;</div>  
+
     | <div id="job_phone">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Address</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Phone</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The mailing address for the representative.
+
     The contact telephone number for the job.  
 
 
 
     |-
 
     |-
     | <div id="corep_city">&nbsp;</div>  
+
     | <div id="primaryservicer">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: City</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Primary Servicer</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The city for the mailing address
+
     The primary servicer for the job. New jobs will automatically use the primary servicer.
 
     |-
 
     |-
     | <div id="corep_country">&nbsp;</div>  
+
     | <div id="job_receiveddate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Country</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Date</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The country for the mailing address.
+
     The date the job was received from the customer.  
 
 
 
     |-
 
     |-
     | <div id="corep_repdivision">&nbsp;</div>  
+
     | <div id="job_refno">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Division</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Reference Number</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     If division are in use, the representative division can be assigned.
+
     The default payment reference number.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="corep_repemail">&nbsp;</div>  
+
     | <div id="job_saleperson">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Email</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Salesperson</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The email address used to contact the representative.
+
     The salesperson for the job. *Certain ERP systems require a salesperson.
 +
 
 
     |-
 
     |-
     | <div id="corep_repname">&nbsp;</div>  
+
     | <div id="job_sendtomobile">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Name</div>  
+
     | <div class="fieldHeader">Job: Send to Mobile Checkbox</div>  
 
     |-
 
     |-
     |  
+
     | On save, if this checkbox is checked, the job will be made available in mobile.  
    The name of the representative.
+
 
 +
 
 
     |-
 
     |-
     | <div id="corep_repno">&nbsp;</div>  
+
     | <div id="job_servicetype">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Service Type</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The representative number can be used to recognize a representative.
+
     Service types are used to organize jobs. Service type are organized by job type.
 +
 
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="corep_repphone">&nbsp;</div>  
+
     | <div id="job_sla">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Phone</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Checkbox</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The telephone number used to contact the representative.
+
     Check this box, if the job qualifies for SLA service. This defaults from the site.
 
     |-
 
     |-
     | <div id="corep_state">&nbsp;</div>  
+
     | <div id="job_slaExp">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: State</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Date</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The state for the mailing address.
+
     The date the technician has to start the work in order to meet the SLA criteria.
 
     |-
 
     |-
     | <div id="corep_reptype">&nbsp;</div>  
+
     | <div id="job_slaExpTime">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Time</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Types are used to organize representatives.
+
     The time the technician has to start the work in order to meet the SLA criteria.
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="corep_zip">&nbsp;</div>  
+
     | <div id="job_status">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Zip</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Status</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The postal code for the mailing address.
+
     Status codes are used to determine the job's position in the work process.  
 
     |-
 
     |-
     | <div id="job_request">&nbsp;</div>  
+
     | <div id="job_statusbar">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request</div>  
+
     | <div class="fieldHeader">Job: Status Bar</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Requests are defined using the Request Management feature. The request defines the work requested.  
+
     The status bar indicates the job's status progress.
 +
   
 +
 
 
     |-
 
     |-
     | <div id="job_requestnote">&nbsp;</div>  
+
     | <div id="jobtype_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request Notes</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Description</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     Request notes are used to further define the work requested.
+
     Used to describe the job type.  
 
     |-
 
     |-
     | <div id="costtype_RevAcct">&nbsp;</div>  
+
     | <div id="EstHours">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue Account</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Estimated Hours</div>    
 
     |-
 
     |-
 
     |  
 
     |  
     The sales account that will be assigned to transactions assigned this job type and cost type.  
+
     The hours estimated to complete the job.
 +
    |-
 +
    | <div id="jobType">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type</div>     
 +
    |-
 +
    |
 +
    Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions.  
 
     |-
 
     |-
     | <div id="costtype_RevSubacct">&nbsp;</div>  
+
     | <div id="KPICallCount">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue subaccount</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: KPI Call Count Checkbox</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The sales sub-account that will be assigned to transactions assigned this job type and cost type.  
+
     When checked the jobs assigned the job type will be counted in the KPI analytics.
 
     |-
 
     |-
     | <div id="servicetype_Code">&nbsp;</div>  
+
     | <div id="Opportunity">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Opportunity</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Used to identify the service type.
+
     Marks the job type as a job opportunity.
 
     |-
 
     |-
     | <div id="servicetype_Desc">&nbsp;</div>  
+
     | <div id="QuotedDollars">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Desc</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Quoted $s</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Used to describe the service type.
+
     The dollars quoted for the job.  
   
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
   
 
 
 
 
 
 
 
  
  
 
     |-
 
     |-
     | <div id="job_scheduledate">&nbsp;</div>  
+
     | <div id="kpi">&nbsp;</div>  
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI</div>   
 +
    |-
 +
    | KPI fields are indicators of job profit and profitability.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Date</div>  
+
     | <div id="DepartureDate">&nbsp;</div>  
 
     |-
 
     |-
     |  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Date</div>   
    The date the technician is schedule to do the work.
 
 
     |-
 
     |-
     | <div id="job_scheduletime">&nbsp;</div>
+
     | The date the job was changed to the departed status code.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Time</div>  
+
     | <div id="DepartureTime">&nbsp;</div>  
 
     |-
 
     |-
     |  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Time</div>     
    The time the technician is schedule to do the work.
 
 
 
 
 
 
     |-
 
     |-
     | <div id="site_Address">&nbsp;</div>
+
     | The time the job was changed to the departed status code.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Address</div>  
+
     | <div id="JobStartDate">&nbsp;</div>  
 
     |-
 
     |-
     |  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Date</div>     
    The physical address for the site.  This field is used in dispatching.
 
 
     |-
 
     |-
     | <div id="site_Branch">&nbsp;</div>  
+
    | The date the job started.
 +
    |-
 +
     | <div id="JobStartTime">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Branch</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI:Job Start Time </div>  
 
     |-
 
     |-
     |  
+
     | The time the job started.
    The site branch is required if multi-branching is in use.
 
 
     |-
 
     |-
     | <div id="site_Chain">&nbsp;</div>  
+
     | <div id="JobCompleteDate">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Chain</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Date</div>  
 
     |-
 
     |-
     |  
+
     | The date the job was marked complete.
    The site's chain.  Chains are not required.
 
 
     |-
 
     |-
     | <div id="site_City">&nbsp;</div>  
+
     | <div id="JobCompleteTime">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: City</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Time</div>  
 
     |-
 
     |-
     |  
+
     | The time the job was marked complete.
    The address city for the site.  This field is used in dispatching.
 
 
     |-
 
     |-
     | <div id="site_CloneAddress">&nbsp;</div>  
+
     | <div id="JobRevenue">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Customer Address</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Revenues</div>  
 
     |-
 
     |-
     |  
+
     | The total revenues to date.
    When clicked, this button will clone the customer's address to the site.
 
 
     |-
 
     |-
     | <div id="site_CloneShipTo">&nbsp;</div>  
+
     | <div id="JobElapseTime">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Ship To</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Elapse Time</div>  
 
     |-
 
     |-
     |  
+
     | The time between the received date/time and the job close date/time. If the job is not closed the current date is used as the cut-off.  
    When an item is selected, the ship to address will be copied to the site address fields.
 
 
     |-
 
     |-
     | <div id="site_Code">&nbsp;</div>  
+
     | <div id="JobRepairTime">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Repair Time</div>  
 
     |-
 
     |-
     |  
+
     | The labor hours posted to date.
    The site code can be used to identify the site.  It is not required.
 
 
     |-
 
     |-
     | <div id="site_EST">&nbsp;</div>  
+
     | <div id="JobResponseTime">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Established&nbsp;Date</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Response Time</div>  
 
     |-
 
     |-
     |  
+
     | The time between the received date/time and the arrival date/time.
    The date the site was added.
 
 
     |-
 
     |-
     | <div id="site_Fax">&nbsp;</div>  
+
     | <div id="JobProfit">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Fax Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Profit</div>  
 
     |-
 
     |-
     |  
+
     | The job's profit to date.
    The site's Fax number.  
 
 
     |-
 
     |-
     | <div id="site_Labor1">&nbsp;</div>  
+
     | <div id="Jobbilledstatus">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Labor #1</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Invoice Status</div>  
 
     |-
 
     |-
     |  
+
     | The job's billing status.
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
 
 
     |-
 
     |-
     | <div id="site_Labor2">&nbsp;</div>  
+
     | <div id="JobinvoiceDate">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Labor #2</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Invoice Date</div>  
 
     |-
 
     |-
     |  
+
     | The date the job was first invoiced.
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
+
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="site_Lat">&nbsp;</div>  
+
     | <div id="level_Code">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Latitude</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The latitude for the site location.  
+
     Models can be grouped by levels. Levels can be grouped by type.
 
     |-
 
     |-
     | <div id="site_Long">&nbsp;</div>  
+
     | <div id="level_Code">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Longitude</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The longitude for the site location.
+
     The code used to identify the level.  
 
     |-
 
     |-
     | <div id="site_MainNo">&nbsp;</div>  
+
     | <div id="level_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Main Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Description</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The main business contact telephone number for the site.
+
     The description that identifies the level.
 
     |-
 
     |-
     | <div id="site_MapCode">&nbsp;</div>  
+
     | <div id="level_prefix">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Map Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Prefix</div>
 
     |-
 
     |-
 
     |  
 
     |  
     When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page.
+
     The three digit prefix to use when auto-numbering new equipment records.
 
     |-
 
     |-
     | <div id="site_Name">&nbsp;</div>  
+
     | <div id="levelType">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Name</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Type</div>
 
     |-
 
     |-
 
     |  
 
     |  
     The name of the site location. This is used to identify the site.
+
     Level types are used to group levels.
 +
 
 
     |-
 
     |-
     | <div id="site_PriceLevels">&nbsp;</div>  
+
     | <div id="Location">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Price Level</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Location</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The price level that should be used when billing jobs.
+
     Indicates the phusical location of a piece of equipment at a site.
 +
 
 +
 
 
     |-
 
     |-
     | <div id="site_PContact">&nbsp;</div>  
+
     | <div id="Manufacturer">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Primary Contact</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The site's primary contactContacts are management using the Contact Mangement system.  
+
     The manufacturer is assigned to equipment recordsThe manufacturer is assigned models.
 
     |-
 
     |-
     | <div id="site_Referral">&nbsp;</div>  
+
     | <div id="Manu_Code">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Referral Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The site's referral code.  Referral codes are not required.
+
     The code used to identify the manufacturer.   
 
     |-
 
     |-
     | <div id="site_Servicer1">&nbsp;</div>  
+
     | <div id="Manu_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Servicer #1</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Description</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The default primary servicer. New jobs will be automatically assigned to this servicer. 
+
     The description that identifies the manufacturer.
 
     |-
 
     |-
     | <div id="site_Servicer2">&nbsp;</div>  
+
     | <div id="Manu_Prefix">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Servicer #2</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Prefix</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The secondary servicer for new jobs.
+
     The three digit prefix to use when auto-numbering new equipment records.
 +
 
 
     |-
 
     |-
     | <div id="site_SLA">&nbsp;</div>  
+
     | <div id="model_Code">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: SLA</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Check this box, if the site qualifies for SLA service.  
+
     The code used to identify the model.
 
     |-
 
     |-
     | <div id="site_State">&nbsp;</div>  
+
     | <div id="model_Desc">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: State</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Description</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The address state code for the site.  This field is used in dispatching.
+
     The description that identifies the model.
 
     |-
 
     |-
     | <div id="site_StoreNo">&nbsp;</div>  
+
     | <div id="model_prefix">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Store Number</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Prefix</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The store number for the site.  The store number is directly tied to the Chains feature.  
+
     The three digit prefix to use when auto-numbering new equipment records.
   
+
 
 +
 
 +
 
 +
 
 
     |-
 
     |-
     | <div id="site_StoreType">&nbsp;</div>  
+
     | <div id="NoteCategory">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Store Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Category</div>  
 
     |-
 
     |-
     |  
+
     | Notes can be organized by category.
    The store type for the site.  The store number is directly tied to the Chains feature.  
 
 
     |-
 
     |-
     | <div id="site_Type">&nbsp;</div>  
+
     | <div id="NoteContent">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Content</div>  
 
     |-
 
     |-
     |  
+
     | the note content that will display on the form and print on any documents.
    Site types are used to organize sites. Site types are not required.  
 
 
     |-
 
     |-
     | <div id="site_Zip">&nbsp;</div>  
+
     | <div id="NoteInternal">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Site: Zip Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Internal Note Checkbox</div>   
 +
    |-
 +
    | Internal notes do not print on invoices and dispatch cards.
 +
    |-
 +
    | <div id="NotePrintOnTicket">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Print Note on Ticket Checkbox</div>  
 
     |-
 
     |-
     |  
+
     | When checked, the note will print on the dispatch card.
    The address postal code for the site.  This field is used in dispatching.
+
 
  
  
 
     |-
 
     |-
     | <div id="sitetype_Code">&nbsp;</div>  
+
     | <div id="PlannedMaintenanceType">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Type</div>   
 +
    |-
 +
    | Planned maintenance types are used to organize schedules and establish default values.
 +
    |-
 +
    | <div id="PlannedMaintenanceID">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: ID</div>  
 
     |-
 
     |-
     |  
+
     | The ID is used to identify the schedule.
    Sites can be grouped by site type.
 
 
     |-
 
     |-
     | <div id="sitetype_Code">&nbsp;</div>  
+
     | <div id="PlannedMaintenanceDescription">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Code</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Description</div>  
 
     |-
 
     |-
     |  
+
     | Descriptions can also help in identification.
    The code used to identify the site type.
 
 
     |-
 
     |-
     | <div id="sitetype_Desc">&nbsp;</div>  
+
     | <div id="MaterialGroupCode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Description</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Material Group Code</div>  
 
     |-
 
     |-
     |  
+
     | Matieral Group Codes provide the ability to add materials to schedules by grouping.  
    The description used to identify the site type.
 
 
     |-
 
     |-
     | <div id="sitetype_Message">&nbsp;</div>  
+
     | <div id="PlannedMaintenanceTaskCode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Message</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance:Task Code </div>
 
     |-
 
     |-
     |  
+
     | PM task codes are used to organize schedules and establish material group codes.
    The message of the Service Site Type will default into the field or manually type a customer note into the field. If the Service Site Type is changed the message will not change.
 
 
 
 
 
 
 
  
  
Line 1,837: Line 1,861:
  
 
     |-
 
     |-
     | <div id="job_solution">&nbsp;</div>  
+
     | <div id="Priority">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Solutions are defined using the Solution Management featureThe solution defines the work done to complete the work.
+
     The default priority that will be used when creating new jobs to establish schedule date and timePriorities are assigned to sites as a default for new jobs.  
 +
 
 
     |-
 
     |-
     | <div id="job_solutionnotes">&nbsp;</div>  
+
     | <div id="PriorityCode">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution Notes</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Code</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     Solution notes are used to further define the work performed.
+
     Priority codes are used to establish the response time when scheduling jobs.
 +
 
 
     |-
 
     |-
     | <div id="Subclass">&nbsp;</div>  
+
     | <div id="prio_dow">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Subclass</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Day of the Week</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The sub-classification is used in sales and cost account assignments.  
+
     When checked, indicates that jobs can be schedules on that day of the week.
 +
 
 
     |-
 
     |-
     | <div id="TaxClass">&nbsp;</div>  
+
     | <div id="">&nbsp;</div>  
 
     |-
 
     |-
     | <div class="fieldHeader">Tax Class</div>
+
     | &nbsp;
 
     |-
 
     |-
     |  
+
     | <div id="prio_Desc">&nbsp;</div>
    The item's task class.
 
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customertaxexemptno">&nbsp;</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Description</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Exempt Number</div>  
+
    |
 +
    Describe the priority.
 +
    |-
 +
    | <div id="prio_endtime">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: End Time</div>   
 +
    |-
 +
    |
 +
    Indicates the latest time a job can be scheduled on each day of the week.
 +
    |-
 +
    | <div id="ResponseTime">&nbsp;</div>
 +
    |-
 +
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Response Time</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     If the customer is tax exempt, a value must be used in this field.
+
     Indicates the number of hours between the received time and the schedule time.
 +
    |-
 +
    | <div id="prio_SLA">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA</div>   
 +
    |-
 +
    |
 +
    When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customertaxschedule">&nbsp;</div>  
+
     | <div id="prio_SLAExp">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Schedule</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA Expiration</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's tax schedule.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
+
     The number of hours that are required to meet the SLA deadline.  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>  
+
     | <div id="prio_starttime">&nbsp;</div>  
 
     |-
 
     |-
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Terms</div>  
+
     | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Start Time</div>  
 
     |-
 
     |-
 
     |  
 
     |  
     The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
+
    Indicated the earliest time a job can be scheduled on each day of the week.
 +
 
 +
    |-
 +
    | <div id="ReportingGroups">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Reporting Groups</div>   
 +
    |-
 +
    |
 +
    A group code can be assigned to a miscellaneous charge code to group like Item codes.
 +
    |-
 +
    | <div id="corep_repaddress">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Address</div>
 +
    |-
 +
    |
 +
    The mailing address for the representative.
 +
 
 +
    |-
 +
    | <div id="corep_city">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: City</div>
 +
    |-
 +
    |
 +
    The city for the mailing address
 +
    |-
 +
    | <div id="corep_country">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Country</div>
 +
    |-
 +
    |
 +
    The country for the mailing address.
 +
 
 +
    |-
 +
    | <div id="corep_repdivision">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Division</div>
 +
    |-
 +
    |
 +
    If division are in use, the representative division can be assigned.
 +
    |-
 +
    | <div id="corep_repemail">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Email</div>
 +
    |-
 +
    |
 +
    The email address used to contact the representative.
 +
    |-
 +
    | <div id="corep_repname">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Name</div>
 +
    |-
 +
    |
 +
    The name of the representative.
 +
    |-
 +
    | <div id="corep_repno">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Number</div>
 +
    |-
 +
    |
 +
    The representative number can be used to recognize a representative.
 +
    |-
 +
    | <div id="corep_repphone">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Phone</div>
 +
    |-
 +
    |
 +
    The telephone number used to contact the representative.
 +
    |-
 +
    | <div id="corep_state">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: State</div>
 +
    |-
 +
    |
 +
    The state for the mailing address.
 +
    |-
 +
    | <div id="corep_reptype">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Type</div>
 +
    |-
 +
    |
 +
    Types are used to organize representatives.
 +
    |-
 +
    | <div id="corep_zip">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Zip</div>
 +
    |-
 +
    |
 +
    The postal code for the mailing address.
 +
    |-
 +
    | <div id="job_request">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request</div>
 +
    |-
 +
    |
 +
    Requests are defined using the Request Management feature. The request defines the work requested.
 +
    |-
 +
    | <div id="job_requestnote">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request Notes</div>
 +
    |-
 +
    |
 +
    Request notes are used to further define the work requested.
 +
    |-
 +
    | <div id="costtype_RevAcct">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue Account</div>
 +
    |-
 +
    |
 +
    The sales account that will be assigned to transactions assigned this job type and cost type.
 +
    |-
 +
    | <div id="costtype_RevSubacct">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue subaccount</div>
 +
    |-
 +
    |
 +
    The sales sub-account that will be assigned to transactions assigned this job type and cost type.
 +
 
 +
 
 +
    |-
 +
    | <div id="job_scheduledate">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Date</div>
 +
    |-
 +
    |
 +
    The date the technician is schedule to do the work.
 +
    |-
 +
    | <div id="job_scheduletime">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Time</div>
 +
    |-
 +
    |
 +
    The time the technician is schedule to do the work.
 +
 
 +
    |-
 +
    | <div id="servicer_Number">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer</div>   
 +
    |-
 +
    |
 +
    The technician that will perform the work.
 +
    |-
 +
    | <div id="servicer_Number">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Number</div>   
 +
    |-
 +
    |
 +
    The number used to identify the technician.
 +
    |-
 +
    | <div id="servicer_employee">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Employee Number</div>   
 +
    |-
 +
    |
 +
    If the servicer is also an employee, the employee number can be stored in this field.
 +
    |-
 +
    | <div id="servicer_subcontractor">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Subcontractor Checkbox</div>   
 +
    |-
 +
    |
 +
    When checked, indicates that the servicer is a contracted employee or vendor.
 +
    |-
 +
    | <div id="svr_Name">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Name</div>     
 +
    |-
 +
    |
 +
    The name of the technician.
 +
    |-
 +
    | <div id="svr_Vendor">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Vendor</div>   
 +
    |-
 +
    |
 +
    If the servicers is a vendor, the vendor can be recorded on this record. 
 +
    |-
 +
    | <div id="svr_Address">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Address</div>       
 +
    |-
 +
    |
 +
    The technician's mailing address.
 +
    |-
 +
    | <div id="svr_BillingRate">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Billing Rate</div>   
 +
    |-
 +
    |
 +
    The technicians hourly labor billing rate.
 +
    |-
 +
    | <div id="svr_PORequired">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: PO Required Checkbox</div>   
 +
    |-
 +
    |
 +
    When checked, the vendor requires a purchase order for all requested work.
 +
    |-
 +
    | <div id="svr_HrlyCost">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Hourly Cost</div>   
 +
    |-
 +
    |
 +
    The hourly cost for the technician.
 +
    |-
 +
    | <div id="svr_InsCert">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Insurance Certificate on File Checkbox</div>   
 +
    |-
 +
    |
 +
    For use with vendors or contract employees only. Indicates that a Certificate of Insurance is on file.
 +
    |-
 +
    | <div id="svr_burden">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Burden</div>   
 +
    |-
 +
    |
 +
    The hourly burden for the technician.
 +
    |-
 +
    | <div id="svr_certFile">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Certificate File Name</div>   
 +
    |-
 +
    |
 +
    The file name for the Certificate of Insurance.
 +
    |-
 +
    | <div id="svr_city">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: City</div>   
 +
    |-
 +
    |
 +
    The servicer's mailing address city.
 +
    |-
 +
    | <div id="svr_warehouse">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Warehouse</div>   
 +
    |-
 +
    |
 +
     The servicer's default warehouse.
 +
    |-
 +
    | <div id="svr_terms">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Terms</div>   
 +
    |-
 +
    |
 +
    If the servicer is a vendor or contract employee, the terms for payment.
 +
    |-
 +
    | <div id="svr_State">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: State</div>   
 +
    |-
 +
    |
 +
    The servicer's mailing address state.
 +
    |-
 +
    | <div id="svr_Zip">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Zip</div> 
 +
    |-
 +
    |
 +
    The servicer's mailing address postal code.
 +
    |-
 +
    | <div id="svr_Email">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Email</div> 
 +
    |-
 +
    |
 +
    The servicer's email address.
 +
    |-
 +
    | <div id="svr_Mobile">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Mobile Checkbox</div> 
 +
    |-
 +
    |
 +
    When checked, the servicer's jobs will appear on the mobile board.
 +
    |-
 +
    | <div id="svr_country">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Country</div> 
 +
    |-
 +
    |
 +
    The servicer's mailing address country
 +
    |-
 +
    | <div id="svr_estDate">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Established Date</div> 
 +
    |-
 +
    |
 +
    The date the servicer relationship was established.
 +
    |-
 +
    | <div id="svr_userList">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User List</div> 
 +
    |-
 +
    |
 +
    Servicers must be attached to a user login in order to use the mobile system. 
 +
    |-
 +
    | <div id="svr_phone">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Phone</div> 
 +
    |-
 +
    |
 +
    The telephone number for contacting the servicer.
 +
    |-
 +
    | <div id="svr_imgFile">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Servicer Image File</div> 
 +
    |-
 +
    |
 +
    The name of the file that contain an image of the technician.
 +
    |-
 +
    | <div id="svr_dispatchBatch">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Service Dispatch Batch</div> 
 +
    |-
 +
    |
 +
    Mobile jobs can be grouped by batch for posting to the back office.
 +
    |-
 +
    | <div id="svr_tomtom">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Tom Tom ID</div> 
 +
    |-
 +
    |
 +
    The Tom Tom ID for the servicer. 
 +
    |-
 +
    | <div id="svr_userMapPin">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User Map Pin</div>   
 +
    |-
 +
    |
 +
    Technicians can be mapped using pins. 
 +
 
 +
 
 +
    |-
 +
    | <div id="svr_userMapPin">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults: New Job Defaults</div>   
 +
    |-
 +
    |
 +
    The values that will be used by default when adding new jobsSome of these values can be changed at the job level.
 +
        [[Glossary#job_request|Request]]
 +
        [[Glossary#ss_OverrideJobNo|Override Job No]]
 +
        [[Glossary#ss_SendJobEmail|Send Job Email]]
 +
        [[Glossary#jobType|Job Type]]
 +
        [[Glossary#servicetype|Service Type]]
 +
        [[Glossary#Priority|Priority]]
 +
        [[Glossary#ss_EstHours|Est Hours]]
 +
        [[Glossary#ss_JobNextNo|Job Next No]]
 +
        [[Glossary#ss_JobLength|Job Length]]
 +
        [[Glossary#ss_JobLeadingCharacters|Job Leading Characters]]
 +
 
 +
    |-
 +
    | <div id="ss_OverrideJobNo ">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Override Job No Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, users are allowed to alter the job number.  Warning! This could interrupt the job numbering system.
 +
    |-
 +
    | <div id="ss_SendJobEmail ">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Send Job Email Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, the send email form will be displayed when a new job is saved.
 +
    |-
 +
    | <div id="ss_EstHours">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Est Hours</div>
 +
    |-
 +
    |
 +
    The hours estimated to complete the job. This value will be added to the primary work order.
 +
    |-
 +
    | <div id="ss_JobNextNo">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Next No</div>
 +
    |-
 +
    |
 +
    The number that will be assigned to the next job.
 +
    |-
 +
    | <div id="ss_JobLength">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Length</div>
 +
    |-
 +
    |
 +
    The number of characters in the job number.
 +
    |-
 +
    | <div id="ss_JobLeadingCharacters">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Leading Characters</div>
 +
    |-
 +
    |
 +
    The character(s) that will lead the job number. This is not required.
 +
 
 +
 
 +
    |-
 +
    | <div id="ss_ShortDescSize">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults</div>
 +
    |-
 +
    |
 +
    The defaults that affect the inventory feature.
 +
    |-
 +
    | <div id="ss_ShortDescSize">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Short Desc Size</div>
 +
    |-
 +
    |
 +
    The number of characters to use for the short description for items. 
 +
 
 +
    |-
 +
    | <div id="ss_ShortDescSize">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Button: Update Item Short Descriptions</div>
 +
    |-
 +
    |
 +
    When clicked the system will copy the first characters, based on the Short Desc Size field, to the Short Description field for all items. Warning! This cannot be reversed.
 +
 
 +
 
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Status Code Defaults</div>
 +
    |-
 +
    |
 +
    Status codes are used to move jobs through the work flow process.  Each status code on this form has a purpose.  Assign a status code to each slot.  *These are required.
 +
 
 +
 
 +
    |-
 +
    | <div id="ss_ed">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults</div>
 +
    |-
 +
    |
 +
    Default values for new equipment records.
 +
    |-
 +
    | <div id="sd_ed_warrantyBasedOn">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Warranty Based On</div>
 +
    |-
 +
    |
 +
    Warranties can be set based on the Sale Date or the installation date.
 +
    |-
 +
    | <div id="sd_ed_allocationBasedOn">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Allocation Based On</div>
 +
    |-
 +
    |
 +
    General ledger allocations can be based on the inventory item, or the model.
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Auto No/EQ Defaults Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, the system will automatically number new equipment records.
 +
 
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Options</div>
 +
    |-
 +
    |
 +
    Auto-numbering can be defined using a prefix or a matrix.
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Prefix Missing Grid Column</div>
 +
    |-
 +
    |
 +
    The number of records that do not contain a prefix for the matrix to work properly.
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults</div>
 +
    |-
 +
    |
 +
    Defaults values for new sites.
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Site Type</div>
 +
    |-
 +
    |
 +
    The default site type for new sites.
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Tax Schedule</div>
 +
    |-
 +
    |
 +
    The default tax schedule for new sites. This value is only used if the tax schedule is not filled from the customer record.
 +
    |-
 +
    | <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Use Customer Name and Address Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, the customer name and address automatically fills into the site form when adding a new site.
 +
 
 +
 
 +
    |-
 +
    | <div id="ss_tad">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments</div>
 +
    |-
 +
    |
 +
    The defaults and settings for new tranasctions.
 +
    |-
 +
    | <div id="ss_tad_Warehouse">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Warehouse</div>
 +
    |-
 +
    |
 +
    The warehouse to assign to any transaction for which a warehouse has not been assigned.
 +
    |-
 +
    | <div id="taxOnCustomer">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Tax on Customer Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, invoices will autommatically use the customer's tax schedule.
 +
    |-
 +
    | <div id="multiBranch">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Multi-branch Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, the multi-branch feature becomes active and its rules applied.
 +
    |-
 +
    | <div id="multiBranchSegment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Segment</div>
 +
    |-
 +
    |
 +
    When the Multi-Branch checkbox is checked, this field becomes active. Use it to set the default branch segment to use when a branch segment is missing.
 +
    |-
 +
    | <div id="salesAcct">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Sales Account</div>
 +
    |-
 +
    |
 +
    The sales account to assign to any transaction for which a sales account has not been assigned. 
 +
    |-
 +
    | <div id="costAcct">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Cost Account</div>
 +
    |-
 +
    |
 +
    The cost account to assign to any transaction for which a cost account has not been assigned. 
 +
    |-
 +
    | <div id="ss_inv">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing</div>
 +
    |-
 +
    |
 +
    The defaults and settings for new tranasctions.
 +
 
 +
    |-
 +
    | <div id="sd_Invoice_RequireSalesTax">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Require Sales Tax Checkbox</div>
 +
    |-
 +
    |
 +
    When checked, sales tax will be required on all invoices.
 +
    |-
 +
    | <div id="sd_Invoice_Non">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Non-Tax Schedule</div>
 +
    |-
 +
    |
 +
    Certin ERP system require a tax schedule on all invoices, even those that are non-tax.  This schedule fills that requirement.
 +
    |-
 +
    | <div id="sd_Invoice_NextBatchNumber">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next Batch Number</div>
 +
    |-
 +
    |
 +
    The next batch to use when invoices are created automatically.
 +
    |-
 +
    | <div id="sd_Invoice_NextNumber">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next No</div>
 +
    |-
 +
    |
 +
    The next invoice number.
 +
    |-
 +
    | <div id="sd_Invoice_Length">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Length</div>
 +
    |-
 +
    |
 +
    The invoice number length.  This value cannot be shortened.
 +
    |-
 +
    | <div id="sd_Invoice_LeadingCharacters">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Leading Characters</div>
 +
    |-
 +
    |
 +
    The leading character for invoice numbers.  This is not required.
 +
 
 +
    |-
 +
    | <div id="sd_PM">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance</div>
 +
    |-
 +
    |
 +
    The defaults and settings for planned maintenance jobs.
 +
    |-
 +
    | <div id="sd_PM_Priority">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Priority</div>
 +
    |-
 +
    |
 +
    The default priority for new planned maintenance jobs.
 +
    |-
 +
    | <div id="sd_PM_StatusCode">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Status Code</div>
 +
    |-
 +
    |
 +
    The defaults status code for new planned maintenace jobs.
 +
    |-
 +
    | <div id="sd_PM_IncludeSiteinfoascomment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Site info as comment</div>
 +
    |-
 +
    |
 +
    When checked, the site information will appear on planned maintenance invoices.
 +
    |-
 +
    | <div id="sd_PM_IncludeEquipmentinfoascomment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Equipment info as comment</div>
 +
    |-
 +
    |
 +
    When checked, the equipment information will appear on planned maintenance invoices.
 +
 
 +
    |-
 +
    | <div id="sd_AG">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements</div>   
 +
    |-
 +
    | The settings and defaults for new agreements.
 +
    |-
 +
    | <div id="sd_AG_AutoNo">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Auto No Checkbox</div>   
 +
    |-
 +
    | When checked, the system will automatically number any agreements that are created using an agreement type that is not also set to auto number.
 +
    |-
 +
    | <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Next Agreement No</div>   
 +
    |-
 +
    | The next number that will be used when creating agreements.
 +
    |-
 +
    | <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreeement No Length</div>   
 +
    |-
 +
    | The maximum length of the agreement numbers.
 +
 
 +
    |-
 +
    | <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Default Agreement Type</div>   
 +
    |-
 +
    | The agreement type that will be automatically assigned to new agreements.
 +
    |-
 +
    | <div id="sd_AG_PB_autoProcess">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements:Planned Billing Auto Process Checkbox</div> 
 +
    |-
 +
    | When checked, the planned billing nightly auto-processing feature is active.
 +
    |-
 +
    | <div id="sd_AG_PB_ProcessingDate">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Processing Date</div>   
 +
    |-
 +
    | Indicates the date to use when processing planned billing. 
 +
    |-
 +
    | <div id="sd_AG_DR_autoProcess">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Auto Process</div> 
 +
    |-
 +
    | When checked, the deferred revenues nightly auto-renewal feature is active.
 +
    |-
 +
    | <div id="sd_AG_AR_autoProcess">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Renewals Auto Process</div>
 +
    |-
 +
    | When checked, the planned billing nightly auto-renewal feature is active.
 +
    |-
 +
    | <div id="sd_AG_AR_IncludeSiteDetailsascomment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Details on Invoice</div>
 +
    |-
 +
    | When checked, the site details will appear on the invoices.
 +
    |-
 +
    | <div id="sd_AG_AR_IncludeEquipDetailsascomment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements:Agreement Type PRO Include Equipment Details on Invoice </div>
 +
    |-
 +
    | When checked, the equipment details will appear on the invoices.
 +
    |-
 +
    | <div id="sd_AG_AR_IncludeSiteSummaryascomment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Summary on Invoice</div>
 +
    |-
 +
    | When checked, the site summary information will appear on the invoices.
 +
    |-
 +
    | <div id="sd_AG_AR_IncludeEquipSummaryascomment">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, AgreementsAgreement Type PRO Include Equipment Summary on Invoice: </div>
 +
    |-
 +
    | When checked, the equipment summary information will appear on the invoices.
 +
    |-
 +
    | <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Revenue Account</div>
 +
    |-
 +
    | The default revenue account that will be assigned to new allocations.
 +
    |-
 +
    | <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Account</div>
 +
    |-
 +
    | The default deferred revenue account that will be assigned to new allocations.
 +
    |-
 +
    | <div id="Item">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Item</div>
 +
    |-
 +
    | Desc here: The default item that will be assigned to new allocations.
 +
    |-
 +
    | <div id="servicetype">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type</div>
 +
    |-
 +
    |
 +
    Service Types are used to organize jobs using a job type, service type relationship.
 +
    |-
 +
    | <div id="servicetype_Code">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Code</div>
 +
    |-
 +
    |
 +
    Used to identify the service type.
 +
    |-
 +
    | <div id="servicetype_Desc">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Desc</div>
 +
    |-
 +
    |
 +
    Used to describe the service type.
 
      
 
      
 +
 +
 +
    |-
 +
    | <div id="site_Address">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Address</div>
 +
    |-
 +
    |
 +
    The physical address for the site.  This field is used in dispatching.
 +
    |-
 +
    | <div id="site_Branch">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Branch</div>
 +
    |-
 +
    |
 +
    The site branch is required if multi-branching is in use.
 +
    |-
 +
    | <div id="site_Chain">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Chain</div>
 +
    |-
 +
    |
 +
    The site's chain.  Chains are not required.
 +
    |-
 +
    | <div id="site_City">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: City</div>
 +
    |-
 +
    |
 +
    The address city for the site.  This field is used in dispatching.
 +
    |-
 +
    | <div id="site_CloneAddress">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Customer Address</div>
 +
    |-
 +
    |
 +
    When clicked, this button will clone the customer's address to the site.
 +
    |-
 +
    | <div id="site_CloneShipTo">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Ship To</div>
 +
    |-
 +
    |
 +
    When an item is selected, the ship to address will be copied to the site address fields.
 +
    |-
 +
    | <div id="site_Code">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Code</div>
 +
    |-
 +
    |
 +
    The site code can be used to identify the site.  It is not required.
 +
    |-
 +
    | <div id="site_EST">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Established&nbsp;Date</div>
 +
    |-
 +
    |
 +
    The date the site was added.
 +
    |-
 +
    | <div id="site_Fax">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Fax Number</div>
 +
    |-
 +
    |
 +
    The site's Fax number.
 +
    |-
 +
    | <div id="site_Labor1">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Labor #1</div>
 +
    |-
 +
    |
 +
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
 +
    |-
 +
    | <div id="site_Labor2">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Labor #2</div>
 +
    |-
 +
    |
 +
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
 +
    |-
 +
    | <div id="site_Lat">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Latitude</div>
 +
    |-
 +
    |
 +
    The latitude for the site location.
 +
    |-
 +
    | <div id="site_Long">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Longitude</div>
 +
    |-
 +
    |
 +
    The longitude for the site location.
 +
    |-
 +
    | <div id="site_MainNo">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Main Number</div>
 +
    |-
 +
    |
 +
    The main business contact telephone number for the site.
 +
    |-
 +
    | <div id="site_MapCode">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Map Code</div>
 +
    |-
 +
    |
 +
    When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page.
 +
    |-
 +
    | <div id="site_Name">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Name</div>
 +
    |-
 +
    |
 +
    The name of the site location. This is used to identify the site.
 +
    |-
 +
    | <div id="site_PriceLevels">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Price Level</div>
 +
    |-
 +
    |
 +
    The price level that should be used when billing jobs.
 +
    |-
 +
    | <div id="site_PContact">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Primary Contact</div>
 +
    |-
 +
    |
 +
    The site's primary contact.  Contacts are management using the Contact Mangement system.
 +
    |-
 +
    | <div id="site_Referral">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Referral Code</div>
 +
    |-
 +
    |
 +
    The site's referral code.  Referral codes are not required.
 +
    |-
 +
    | <div id="site_Servicer1">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Servicer #1</div>
 +
    |-
 +
    |
 +
    The default primary servicer.  New jobs will be automatically assigned to this servicer. 
 +
    |-
 +
    | <div id="site_Servicer2">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Servicer #2</div>
 +
    |-
 +
    |
 +
    The secondary servicer for new jobs.
 +
    |-
 +
    | <div id="site_SLA">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: SLA</div>
 +
    |-
 +
    |
 +
    Check this box, if the site qualifies for SLA service.
 +
    |-
 +
    | <div id="site_State">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: State</div>
 +
    |-
 +
    |
 +
    The address state code for the site.  This field is used in dispatching.
 +
    |-
 +
    | <div id="site_StoreNo">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Store Number</div>
 +
    |-
 +
    |
 +
    The store number for the site.  The store number is directly tied to the Chains feature.
 +
   
 +
    |-
 +
    | <div id="site_StoreType">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Store Type</div>
 +
    |-
 +
    |
 +
    The store type for the site.  The store number is directly tied to the Chains feature.
 +
    |-
 +
    | <div id="site_Type">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Type</div>
 +
    |-
 +
    |
 +
    Site types are used to organize sites. Site types are not required.
 +
    |-
 +
    | <div id="site_Zip">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Site: Zip Code</div>
 +
    |-
 +
    |
 +
    The address postal code for the site.  This field is used in dispatching.
 +
 +
 +
    |-
 +
    | <div id="sitetype_Code">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type</div>
 +
    |-
 +
    |
 +
    Sites can be grouped by site type.
 +
    |-
 +
    | <div id="sitetype_Code">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Code</div>
 +
    |-
 +
    |
 +
    The code used to identify the site type.
 +
    |-
 +
    | <div id="sitetype_Desc">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Description</div>
 +
    |-
 +
    |
 +
    The description used to identify the site type.
 +
    |-
 +
    | <div id="sitetype_Message">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Message</div>
 +
    |-
 +
    |
 +
    The message of the Service Site Type will default into the field or manually type a customer note into the field. If the Service Site Type is changed the message will not change.
 +
 +
 +
 +
 +
 +
 +
 +
 +
    |-
 +
    | <div id="job_solution">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution</div>
 +
    |-
 +
    |
 +
    Solutions are defined using the Solution Management feature.  The solution defines the work done to complete the work.
 +
    |-
 +
    | <div id="job_solutionnotes">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution Notes</div>
 +
    |-
 +
    |
 +
    Solution notes are used to further define the work performed.
 +
    |-
 +
    | <div id="Subclass">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Subclass</div>
 +
    |-
 +
    |
 +
    The sub-classification is used in sales and cost account assignments.
 +
 +
 +
 +
 +
    |-
 +
    | <div id="TaskType">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Type</div>   
 +
    |-
 +
    | Tasks can be organized by type.
 +
    |-
 +
    | <div id="TaskStatus">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Status</div> 
 +
    |-
 +
    | Tasks can be tracked by status.
 +
    |-
 +
    | <div id="TaskDetails">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Details</div> 
 +
    |-
 +
    | Task details provide a description of the task.
 +
    |-
 +
    | <div id="TaskURL">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: URL</div> 
 +
    |-
 +
    | The URL field is used to store the website related to the task.
 +
    |-
 +
    | <div id="TaskNotes">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Notes</div> 
 +
    |-
 +
    | Notes can be stored for each task.
 +
    |-
 +
    | <div id="TaskDueDate">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Date</div> 
 +
    |-
 +
    | Task can be tracked by due date.
 +
    |-
 +
    | <div id="TaskDueTime">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Time</div> 
 +
    |-
 +
    | Task can be tracked by due time.
 +
    |-
 +
    | <div id="TaskAssignmentType">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assignment Type</div> 
 +
    |-
 +
    | Tasks can be assigned to individual by type.
 +
        Account Manager
 +
        Salesperson
 +
        Servicer
 +
        User
 +
    |-
 +
    | <div id="TaskAssignedTo">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assigned To</div> 
 +
    |-
 +
    | The individual that will handle the task.
 +
    |-
 +
    | <div id="TaskEmail">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Email</div> 
 +
    |-
 +
    | An email can be stored with the task.
 +
    |-
 +
    | <div id="TaskTextPhone">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Text Phone</div> 
 +
    |-
 +
    | A telephone number for texting can be stored with the task.
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
    |-
 +
    | <div id="TaxClass">&nbsp;</div>
 +
    |-
 +
    | <div class="fieldHeader">Tax Class</div>
 +
    |-
 +
    |
 +
    The item's task class.
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div id="customertaxexemptno">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Exempt Number</div>
 +
    |-
 +
    |
 +
    If the customer is tax exempt, a value must be used in this field. 
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div id="customertaxschedule">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Schedule</div>
 +
    |-
 +
    |
 +
    The customer's tax schedule.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Terms</div>
 +
    |-
 +
    |
 +
    The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 +
 +
    |-
 +
    | <div id="TransactionBilledStatus">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction Billed Status</div>     
 +
    |-
 +
    | Indicates the transaction's position in the billing process.
 +
        N = Not billed
 +
        I = On an unposted invoice
 +
        Y = On a posted invoice
 +
    |-
 +
    | <div id="TransactionDate">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction Date</div> 
 +
    |-
 +
    | The date the transaction will post to the general ledger.
 +
 +
    |-
 +
    | <div id="TransactionType">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction Type</div>     
 +
    |-
 +
    | The type of transaction.  The type is used to group the transactions by labor, materials or purchases.
 +
 +
 +
 +
 +
 +
 +
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>
 +
    |-
 +
    | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Est Hours</div>
 +
    |-
 +
    |
 +
    The hours estimated to complete the work order.
  
  

Revision as of 12:24, 27 December 2022

 
Account Manager
   Account managers are responsible for the customer relationship.
 
Active Status
   Indicates that the record can be used to produce results.


 
Agreement: Auto Renew%
   Indicates the amount percent of increase for the renewal.


 
Agreement: Billable Checkbox
   When checked, indicates that the agreement can be billed.


 
Agreement: Billing Total
   The total contract amount.


 
Agreement: Commission Rate
   The commission rate that will be used when billing the agreement.


 
Agreement: Contact
   The customer or site contact that handles the agreement.


 
Agreement: Deferred Revenues Total
   The total deferred revenues posted to date.



 
Agreement: Frequency
   The billing frequency.


 
Agreement: Gross Profit Contact Billed to Date
   The agreement's gross profit based on billings to date.


 
Agreement: Gross Profit Contract Term to Date
   The agreement's gross profit recorded on the contract to date. 


 
Agreement: Labor Budget Balance %
   Percentage of labor budget balance to date. 


 
Agreement: Labor Budget Used %
   Percentage of labor budget used to date.



 
Agreement: Labor Budget Hours Used to Date
   The number of budgeted hours billed to date.


 
Agreement: Labor Hours Balance
   The remainer of the budgeted hours to date.


 
Agreement: Labor Hours Budget
   The number of labor hours budgeted for the contract's term. 



 
Agreement: Last Increase
   The increase amount from the last renewal.



 
Agreement: Number
   Agreement numbers are used the identify agreements.


 
Agreement: Parts Billed to Date
   The amount billed to date for parts.
 
Agreement: Parts Budget
   The total amount budgeted for parts on the agreement contract.


 
Agreement: Parts Budget Balance
   The remainer of the amount budgeted for parts to date.


 
Agreement: Parts Budget Balance %
   Percentage of parts budget balance to date. 


 
Agreement: Parts Budget Used %
   The amount of the parts budget billed to date.



 
Agreement: Price Level
   The price level that will be used when billing the agreement.


 
Agreement: Pricing Method
   Agreements can be priced based on the different methods.  
       Blanket: One price covers all items on the agreement.  
       By Site: Each site can have a different price. 
       By Equipment: Each equipment record can have a different price. 


 
Agreement: Purchase Order
   The purchase order provided by the customer for the agreement.
 
Agreement: Renewable
   Indicates that the agreement is eligible for renewal.


 
Agreement: Renewal Amount
   The amount that will be billed on agreement renewal.



 
Agreement: Renewal Method
   The renewal method field is used when determining the renewal contract amount.  The contract amount can be a fixed amount, or changed based on a change percentage.
       Fixed Amount: The renewal will use the exact amount in this field.
       Change Percent: Increases the contract amount by the percent in the Renewal Amount field.
 
Agreement: Renewal Months
   The contract months to use on the renewal.



 
Agreement: Renewal Text
   The text that will be displayed on the agreement renewal invoice. 
 
Agreement: Renew As
   Used to indicate the type of invoice that will be created upon renewal.
 
Agreement: Revenues Total
   The total amount billed for the contract to date.
 
Agreement: Salesperson
   The salesperson that should be assigned to the invoices when billing occurs.
 
Agreement: Status Code
   The status code is used to track the agreements progress through the renewal process.
 
Agreement Type
   Used to organize agreements by type.  Agreement types are also used to establish setting for agreements by default. 
 
Agreement Type: Code
   The code used to identify the agreement type.
 
Agreement Type: Description
   The description used to identify the agreement type.
 
Agreement Type: Contract Months
   The number of months for new agreements.
 
Agreement Type: Cover Parts Checkbox
   When checked, the parts covered by the agreement will have no charge.
 
Agreement Type: Cover Labor Checkbox
   When checked, the parts covered by the agreement will have no charge.
 
Agreement Type: SLA Checkbox
   Check this box, if the agreement qualifies for SLA service. 
 
Agreement Type: SLA Priority Code
   The SLA qualified priority code to use for new agreements.
 
Agreement Type:Message
   This message will appear on the agreement.
 
Agreement Type: Labor Hours Budget
   The budgeted number of labor hours.
 
Agreement Type: Parts Dollars Budget
   The budgeted parts dollars.
 
Agreement Type: Percent Used >=
   Percentage of labor budget used.
 
Agreement Type: Dollars Used >=
   Percentage of parts dollars used.
 
Agreement Type: Auto Number by Type
   When checked, new agreements will auto-number using the value int he Next Number field.
 
Agreement Type: Next Number
   Used when auto-numbering agreements. 
 
Agreement Type: Enforce Defaults
   When checked, the agreement type defaults cannot be changed on the agreement.
 
Agreement Type Planned Invoice Options: Billable
   When checked, the agreements assigned to the agreement type will be billable by default.
 
Agreement Type Planned Invoice Options: Frequency
   The billing frequency.
 
Agreement Type Planned Invoice Options: Tax Class
   The tax class assigned to invoice billing invoices.
 
Agreement Type Planned Invoice Options: Allocation
   The allocation that will be assigned used when processing agreements.
 
Agreement Type Planned Invoice Options: Deferred Revenues
   When checked, new agreements will use the deferred revenue feature.
 
Agreement Type Planned Invoice Options: Pricing Method
   The pricing method used when processing agreement transactions. 
 
Agreement Type Planned Invoice Options: Pricing
Agreement Type
       Blanket: One price covers all items on the agreement.  
       By Site: Each site can have a different price. 
       By Equipment: Each equipment record can have a different price. 
 
Agreement Type Planned Invoice Options: Include Site Details on Invoice
   When checked, the site details will appear on agreement invoices.
 
Agreement Type Planned Invoice Options: Include Equipment Details on Invoice
   When checked, equipment details will appear on agreement invoices.
 
Agreement Type Planned Invoice Options: Include Site Summary on Invoice
   When checked, a site summary will appear on agreement invoices.
 
Agreement Type Planned Invoice Options: Include Equipment Summary on Invoice
   When checked, an equipment summary will appear on agreement invoices.
 
Agreement Type Planned Renewal Options: Renewable Checkbox
   When checked, the agreement will be marked renewable on creation.
 
Agreement Type Planned Renewal Options: Renewal Months
   The number of default renewal months on new agreements.
 
Agreement Type Planned Renewal Options: Renew As
   The default renew as value for new agreements.  
 
Agreement Type Planned Renewal Options: Include Site Details on Invoice
   When checked, the site details will appear on renewal invoices.
 
Agreement Type Planned Renewal Options: Include Equipment Details on Invoice
   When checked, equipment details will appear on renewal invoices.
 
Agreement Type Planned Renewal Options: Include Site Summary on Invoice
   When checked, a site summary will appear on renewal invoices.
 
Agreement Type Planned Renewal Options: Include Equipment Summary on Invoice
   When checked, an equipment summary will appear on renewal invoices.



 
Agreement Type Planned Maintenance Options: Create a Job for each Equipment
   When checked, planned maintenance will create a separate job for each equipment record assigned to the schedule.
 
Agreement Type Planned Maintenance Options: Create Transactions
   When checked, planned maintenance will automatically add the transactions to the generated jobs.
 
Agreement Type Planned Maintenance Options: Price Transactions
   When checked, planned maintenance will add the transactions, with pricing, to the generated jobs.


 
Allocation
   Allocations are used to distribute the agreement dollars to the required general ledger accounts.  
 
Allocation: Description
   The description used to identify the allocation.
 
Allocation: Revenue Type
   Indicates if the allocation will be a percentage or fixed amount.
 
Allocation: Pricing Method
   Agreements can be priced based on the different methods. Allocations define the price method the can be assigned in agreement types. 
       Blanket: One price covers all items on the agreement.  
       By Site: Each site can have a different price. 
       By Equipment: Each equipment record can have a different price. 
 
Allocation: Price
   The allocation price.  
       Blanket - Enter one price for the entire contract.
       By Site - Enter the price for each site.
       By Equipment - Enter ethe price for each equipment. 
 
Allocation Details: Type
   The type of general ledger entry. 
       Deferred Revenue: Posts to a deferred revenue account.
       Revenue: Post to a sales revenue account.
 
Allocation Details: Miscellaneous Item
   The miscellaneous item to use when posting to the ERP system.
 
Allocation Details: Allocations Account
   The account that should be affected by the allocation transaction.
 
Allocation Details: Amount
   The amount of the allocation transaction.
 
Button: Assigned
   When clicked, displays all items assigned to the selected record.
 
Button: Not Assigned
   When clicked, displays all the records not assigned to the selected item.


 
Chains
   Sites can grouped by chain.
 
Chains: Name
   The name used to identify the chain.
 
Chains: SLA
   When checked, indicates the chain is an SLA chain. SLA chains have a expiration time for when the work is expected to be completed.
 
Chains: Inbound Path
 
Chains: Outbound Path
 
Chains: Store Type Code
Store Type Code
Desc here
 
Chains: Store Type Name
Store Type Name
Desc here





 
Classification
   The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
       
 
Button: Remove all Assignments
   When clicked, removes all assignments from the selected record.





 
Contact: Address
   The contacts mailing address.


 
Contact: City
   The city of the mailing address.
 
Contact: Country
   The country of the mailing address.
 
Contact: Email
   The contact's email address.


 
Contact: Established Date
   The date the contact record was established.


 
Contact: Fax Number
   The contact's fax number.
 
Contact: First Name
   The contact's first name. 


 
Contact: Last Name
   The contact's last name.


 
Contact: Name
   The contacts full name.


 
Contact: Phone
   The contact's telephone number.


 
Contact: Salutation
   The salutation that should be used when communicating with the contact.


 
Contact: State
   The state of the mailing address.
 
Contact: Title
   The contact title. ex: Mr., Mrs.


 
Contact: Type
   Types can be used to organize contacts.


 
Contact: Zip
   The postal code of the mailing address.


 
Cost Type
   Cost types are used to manage general ledger sales and cost account allocations on transactions and billing.


 
Cost Type: Cost Account
   The cost account that will be assigned to transactions assigned this job type and cost type. 
 
Cost Type: Cost Subaccount
   The cost sub-account that will be assigned to transactions assigned this job type and cost type. 
 
Cost Type: Description
   Used to describe the cost type. 


 
Cost Type: Inventory Checkbox
   When checked, indicates that the cost type can be used for inventory transactions. 


 
Cost Type: Labor Checkbox
   When checked, indicates that the cost type can be used for labor transactions. 


 
Cost Type: Purchases Checkbox
   When checked, indicates that the cost type can be used for purchase transactions. 


 
Customer: Account Manager
   The company representative that manages the customer's account.


 
Customer: Address
   The customer's mailing address.  
 
Customer: Billing Contact
   The primary billing contact assigned to the customer. 


 
Customer: City
   The customer's mailing address city.
 
Customer: Country
   The customer's mailing address country.
 
Customer: Email
   The email address for the primary customer contact.
 
Customer: Ext
   The main telephone numbers extension.
 
Customer: Facebook
   Link to the customer's Facebook account.
 
Customer: Fax
   The customer's contact fax number.
 
Customer: LinkedIn
   The customer's linked in accounnt handle.
 
Customer: Name
   The name of the organization that will be billed.  Jobs can be created without a customer assignmnet, but not billed. 
 
Customer: Number
   Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
 
Customer: Price Level
   The customer's price level.  Price level requirement is based on ERP settings.
 
Customer: Phone
   The customer's business telephone number.
 
Customer: Salesperson
   The salesperson assigned to the customer's account. 
 
Customer: State
   The customers address state.
 
Customer: Twitter
   The customer's twitter handle.
 
Customer: Zip Code
   The customer's address zip code.
 
Equipment: Code
   Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
 
Equipment: Comment
   Comments related to the equipment record.  
 
Equipment: Coverage Date
   The date coverage begins for the equipment record.
 
Equipment: Description
   Used to describe the equipment.
 
Equipment: Item
   Equipment records that are also inventory items will have the Item Code in this field. 
 
Equipment: Install Date
   The date the equipment was installed on site.
 
Equipment: Labor Warranty Checkbox
   When checked, indicates the equipment is covered by a labor warranty.
 
Equipment: Labor Warranty End
   The date the labor warranty ends.
 
Equipment: Labor Warranty Start
   The date the labor warranty begins.
 
Equipment: Level
   Levels are linked to models.  If the leve does not appear in the Level drop-list, check the selected models setup.
 
Equipment: Manufacturer
   The equipment's manufacturer.  Manufacturers are linked to the equipment type.  If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type. 
 
Equipment: Model
   The equipment model. Models are linked to a manufacturer.  If the model does not appear in the model drop-list, check the selected manufacturer's setup. 
 
Equipment: Parts Warranty Checkbox
   When checked, indicates the equipment is covered by a parts warranty.
 
Equipment: Parts Warranty End
   The date the parts warranty ends.
 
Equipment: Parts Warranty Start
   The date the parts warranty begins.
 
Equipment: Sale Date
   The date the equipment was sold to the customer.
 
Equipment: Serial Number
   The equipment's serial number.  This is not required.  



 
Equipment: Type
   Equipment types are used to organize equipment.  Manufacturers are assigned by equipment type. 
 
Equipment: Position/Locations
   Indicates the physical location.
 
Equipment Type
   Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
 
Equipment Type: Code
   The code that identifies the equipment type.
 
Equipment Type: Description
   The description used to identify the equipment type. 
 
Equipment Type: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Inventory: Commissionable
   When checked the item is commissionable.
 
Inventory: Commission Rate
   If the representative is a salesperson, the commision rate is stored in this field. 



 
Inventory: Equipment Build Checkbox
When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
       Prefix: Used when equipment auto-numbering is activated.
       EQ Type
       Model
       Manufacturer
       Labor Warranty Period: The number of months for labor warranty coverage.
       Parts Warranty Period: The number of months for parts warranty coverage.
       Comment
 
Inventory: Item Code
   Used to identify the item. 
 
Inventory: Item Description
   Describes the item. This information comes from the ERP system.




 
Inventory: Item Type
   Indicates the type of Item.
 
Inventory: Prefix
   Used for equipment auto numbering.  If a matrix is in use that calls for this prefix, the system will use the value in this field. 
 
Inventory: Price Code
   The item's price code. The price code is used when calculating transaction pricing. 
 
Inventory: Product Line
   The item's product line.    
 
Inventory: Sales UOM
   The item's unit of measure.
 
Inventory: Servicer Mobile Button
   When checked, a mobile button will be made available in mobile for quick entry.
 
Inventory: Short Description
   A short description for the item.   
 
Inventory: Split Commission
   When checked, commission on the item can be slit.
 
Inventory: Trade Discount
   When checked, discounts are allowed.  
 
Inventory: Unit Cost
   The item's cost.    
 
Inventory: Unit Price
   The price for the item when added to a transaction.
 
Inventory: Use in Mobile
   When checked, the item will be available for use in mobile. 
 
Inventory: Warehouse
   The item's default warehouse.
 
Job: Billed Status
   Indicates where the job is in the billing process.
 
Job: Contact
   The site or customer contact assigned to the job. 
 
Job: Contact Email
   The email address for the job contact.
 
Job: Extension
   The extension number for the contact telephone number
Job: Job Type Code
   Used to recognize the job type.
 
Job: Main Number
   The job's main contact telephone number
 
Job: Number
   Used to identify the job.
 
Job: Payment Method
   The default payment method.


 
Job: Phone
   The contact telephone number for the job. 
 
Job: Primary Servicer
   The primary servicer for the job. New jobs will automatically use the primary servicer.
 
Job: Received Date
   The date the job was received from the customer. 
 
Job: Reference Number
   The default payment reference number.


 
Job: Salesperson
   The salesperson for the job.  *Certain ERP systems require a salesperson.
 
Job: Send to Mobile Checkbox
On save, if this checkbox is checked, the job will be made available in mobile.


 
Job: Service Type
   Service types are used to organize jobs.  Service type are organized by job type. 



 
Job: SLA Checkbox
   Check this box, if the job qualifies for SLA service. This defaults from the site.
 
Job: SLA Expiration Date
   The date the technician has to start the work in order to meet the SLA criteria.
 
Job: SLA Expiration Time
   The time the technician has to start the work in order to meet the SLA criteria.


 
Job: Status
   Status codes are used to determine the job's position in the work process. 
 
Job: Status Bar
   The status bar indicates the job's status progress.
   
 
Job Type: Description
   Used to describe the job type. 
 
Job Type: Estimated Hours
   The hours estimated to complete the job. 
 
Job Type
   Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions. 
 
Job Type: KPI Call Count Checkbox
   When checked the jobs assigned the job type will be counted in the KPI analytics.
 
Job Type: Opportunity
   Marks the job type as a job opportunity.
 
Job Type: Quoted $s
   The dollars quoted for the job. 


 
KPI
KPI fields are indicators of job profit and profitability.
 
KPI: Departure Date
The date the job was changed to the departed status code.
 
KPI: Departure Time
The time the job was changed to the departed status code.
 
KPI: Job Start Date
The date the job started.
 
KPI:Job Start Time
The time the job started.
 
KPI: Job Complete Date
The date the job was marked complete.
 
KPI: Job Complete Time
The time the job was marked complete.
 
KPI: Job Revenues
The total revenues to date.
 
KPI: Job Elapse Time
The time between the received date/time and the job close date/time. If the job is not closed the current date is used as the cut-off.
 
KPI: Job Repair Time
The labor hours posted to date.
 
KPI: Job Response Time
The time between the received date/time and the arrival date/time.
 
KPI: Job Profit
The job's profit to date.
 
KPI: Job Invoice Status
The job's billing status.
 
KPI: Invoice Date
The date the job was first invoiced.










 
Levels
   Models can be grouped by levels. Levels can be grouped by type.
 
Levels: Code
   The code used to identify the level. 
 
Levels: Description
   The description that identifies the level.
 
Levels: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Levels: Type
   Level types are used to group levels.
 
Location
   Indicates the phusical location of a piece of equipment at a site.


 
Manufacturer
   The manufacturer is assigned to equipment records.  The manufacturer is assigned models.  
 
Manufacturer: Code
   The code used to identify the manufacturer.  
 
Manufacturer: Description
   The description that identifies the manufacturer.
 
Manufacturer: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Model: Code
   The code used to identify the model.  
 
Model: Description
   The description that identifies the model.
 
Model: Prefix
   The three digit prefix to use when auto-numbering new equipment records.



 
Note: Category
Notes can be organized by category.
 
Note: Content
the note content that will display on the form and print on any documents.
 
Note: Internal Note Checkbox
Internal notes do not print on invoices and dispatch cards.
 
Note: Print Note on Ticket Checkbox
When checked, the note will print on the dispatch card.


 
Planned Maintenance: Type
Planned maintenance types are used to organize schedules and establish default values.
 
Planned Maintenance: ID
The ID is used to identify the schedule.
 
Planned Maintenance: Description
Descriptions can also help in identification.
 
Planned Maintenance: Material Group Code
Matieral Group Codes provide the ability to add materials to schedules by grouping.
 
Planned Maintenance:Task Code
PM task codes are used to organize schedules and establish material group codes.



 
Priority
   The default priority that will be used when creating new jobs to establish schedule date and time.  Priorities are assigned to sites as a default for new jobs. 
 
Priority: Code
   Priority codes are used to establish the response time when scheduling jobs.
 
Priority: Day of the Week
   When checked, indicates that jobs can be schedules on that day of the week.
 
 
 
Priority: Description
   Describe the priority.
 
Priority: End Time
   Indicates the latest time a job can be scheduled on each day of the week.
 
Priority: Response Time
   Indicates the number of hours between the received time and the schedule time. 
 
Priority: SLA
   When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
 
Priority: SLA Expiration
   The number of hours that are required to meet the SLA deadline. 
 
Priority: Start Time
   Indicated the earliest time a job can be scheduled on each day of the week.
 
Reporting Groups
   A group code can be assigned to a miscellaneous charge code to group like Item codes. 
 
Representative: Address
   The mailing address for the representative.
 
Representative: City
   The city for the mailing address
 
Representative: Country
   The country for the mailing address.
 
Representative: Division
   If division are in use, the representative division can be assigned.
 
Representative: Email
   The email address used to contact the representative.
 
Representative: Name
   The name of the representative.
 
Representative: Number
   The representative number can be used to recognize a representative.
 
Representative: Phone
   The telephone number used to contact the representative.
 
Representative: State
   The state for the mailing address.
 
Representative: Type
   Types are used to organize representatives.
 
Representative: Zip
   The postal code for the mailing address.
 
Request
   Requests are defined using the Request Management feature. The request defines the work requested. 
 
Request Notes
   Request notes are used to further define the work requested.
 
Revenue Account
   The sales account that will be assigned to transactions assigned this job type and cost type. 
 
Revenue subaccount
   The sales sub-account that will be assigned to transactions assigned this job type and cost type. 


 
Schedule Date
   The date the technician is schedule to do the work.
 
Schedule Time
   The time the technician is schedule to do the work.
 
Servicer
   The technician that will perform the work.
 
Servicer: Number
   The number used to identify the technician.
 
Servicer: Employee Number
   If the servicer is also an employee, the employee number can be stored in this field. 
 
Servicer: Subcontractor Checkbox
   When checked, indicates that the servicer is a contracted employee or vendor.
 
Servicer: Name
   The name of the technician.
 
Servicer: Vendor
   If the servicers is a vendor, the vendor can be recorded on this record.  
 
Servicer: Address
   The technician's mailing address.
 
Servicer: Billing Rate
   The technicians hourly labor billing rate.
 
Servicer: PO Required Checkbox
   When checked, the vendor requires a purchase order for all requested work.
 
Servicer: Hourly Cost
   The hourly cost for the technician.
 
Servicer: Insurance Certificate on File Checkbox
   For use with vendors or contract employees only. Indicates that a Certificate of Insurance is on file.
 
Servicer: Burden
   The hourly burden for the technician. 
 
Servicer: Certificate File Name
   The file name for the Certificate of Insurance.
 
Servicer: City
   The servicer's mailing address city.
 
Servicer: Warehouse
   The servicer's default warehouse.
 
Servicer: Terms
   If the servicer is a vendor or contract employee, the terms for payment. 
 
Servicer: State
   The servicer's mailing address state.
 
Servicer: Zip
   The servicer's mailing address postal code.
 
Servicer: Email
   The servicer's email address.
 
Servicer: Mobile Checkbox
   When checked, the servicer's jobs will appear on the mobile board.
 
Servicer: Country
   The servicer's mailing address country
 
Servicer: Established Date
   The date the servicer relationship was established.
 
Servicer: User List
   Servicers must be attached to a user login in order to use the mobile system.  
 
Servicer: Phone
   The telephone number for contacting the servicer.
 
Servicer: Servicer Image File
   The name of the file that contain an image of the technician.
 
Servicer: Service Dispatch Batch
   Mobile jobs can be grouped by batch for posting to the back office. 
 
Servicer: Tom Tom ID
   The Tom Tom ID for the servicer.  
 
Servicer: User Map Pin
   Technicians can be mapped using pins.  


 
Software Defaults: New Job Defaults
   The values that will be used by default when adding new jobs.  Some of these values can be changed at the job level. 
       Request
       Override Job No
       Send Job Email
       Job Type
       Service Type
       Priority
       Est Hours
       Job Next No
       Job Length
       Job Leading Characters
 
Software Defaults, New Job Defaults: Override Job No Checkbox
   When checked, users are allowed to alter the job number.  Warning! This could interrupt the job numbering system.
 
Software Defaults, New Job Defaults: Send Job Email Checkbox
   When checked, the send email form will be displayed when a new job is saved.
 
Software Defaults, New Job Defaults: Est Hours
   The hours estimated to complete the job. This value will be added to the primary work order.
 
Software Defaults, New Job Defaults: Job Next No
   The number that will be assigned to the next job. 
 
Software Defaults, New Job Defaults: Job Length
   The number of characters in the job number.
 
Software Defaults, New Job Defaults: Job Leading Characters
   The character(s) that will lead the job number. This is not required.


 
Software Defaults, Inventory Defaults
   The defaults that affect the inventory feature.
 
Software Defaults, Inventory Defaults: Short Desc Size
   The number of characters to use for the short description for items.  
 
Software Defaults, Inventory Defaults: Button: Update Item Short Descriptions
   When clicked the system will copy the first characters, based on the Short Desc Size field, to the Short Description field for all items. Warning! This cannot be reversed.


 
Software Defaults, Status Code Defaults
   Status codes are used to move jobs through the work flow process.  Each status code on this form has a purpose.  Assign a status code to each slot.  *These are required.


 
Software Defaults, Equipment Defaults
   Default values for new equipment records. 
 
Software Defaults, Equipment Defaults: Warranty Based On
   Warranties can be set based on the Sale Date or the installation date.
 
Software Defaults, Equipment Defaults: Allocation Based On
   General ledger allocations can be based on the inventory item, or the model. 
 
Software Defaults, Equipment Defaults: Auto No/EQ Defaults Checkbox
   When checked, the system will automatically number new equipment records.
 
Software Defaults, Equipment Defaults: Options
   Auto-numbering can be defined using a prefix or a matrix. 
 
Software Defaults, Equipment Defaults: Prefix Missing Grid Column
   The number of records that do not contain a prefix for the matrix to work properly.
 
Software Defaults, Site Defaults
   Defaults values for new sites.
 
Software Defaults, Site Defaults: Site Type
   The default site type for new sites.
 
Software Defaults, Site Defaults: Tax Schedule
   The default tax schedule for new sites. This value is only used if the tax schedule is not filled from the customer record.
 
Software Defaults, Site Defaults: Use Customer Name and Address Checkbox
   When checked, the customer name and address automatically fills into the site form when adding a new site.


 
Software Defaults, Transaction Assignments
   The defaults and settings for new tranasctions.
 
Software Defaults, Transaction Assignments: Warehouse
   The warehouse to assign to any transaction for which a warehouse has not been assigned.
 
Software Defaults, Transaction Assignments: Tax on Customer Checkbox
   When checked, invoices will autommatically use the customer's tax schedule.
 
Software Defaults, Transaction Assignments: Multi-branch Checkbox
   When checked, the multi-branch feature becomes active and its rules applied.
 
Software Defaults, Transaction Assignments: Segment
   When the Multi-Branch checkbox is checked, this field becomes active. Use it to set the default branch segment to use when a branch segment is missing.
 
Software Defaults, Transaction Assignments: Default Sales Account
   The sales account to assign to any transaction for which a sales account has not been assigned.  
 
Software Defaults, Transaction Assignments: Default Cost Account
   The cost account to assign to any transaction for which a cost account has not been assigned.  
 
Software Defaults, Invoicing
   The defaults and settings for new tranasctions.
 
Software Defaults, Invoicing: Require Sales Tax Checkbox
   When checked, sales tax will be required on all invoices.
 
Software Defaults, Invoicing: Non-Tax Schedule
   Certin ERP system require a tax schedule on all invoices, even those that are non-tax.  This schedule fills that requirement.
 
Software Defaults, Invoicing: Next Batch Number
   The next batch to use when invoices are created automatically.
 
Software Defaults, Invoicing: Next No
   The next invoice number.
 
Software Defaults, Invoicing: Length
   The invoice number length.  This value cannot be shortened.
 
Software Defaults, Invoicing: Leading Characters
   The leading character for invoice numbers.  This is not required.
 
Software Defaults, Planned Maintenance
   The defaults and settings for planned maintenance jobs.
 
Software Defaults, Planned Maintenance: Priority
   The default priority for new planned maintenance jobs.
 
Software Defaults, Planned Maintenance: Status Code
   The defaults status code for new planned maintenace jobs.
 
Software Defaults, Planned Maintenance: Include Site info as comment
   When checked, the site information will appear on planned maintenance invoices.
 
Software Defaults, Planned Maintenance: Include Equipment info as comment
   When checked, the equipment information will appear on planned maintenance invoices.
 
Software Defaults, Agreements
The settings and defaults for new agreements.
 
Software Defaults, Agreements: Auto No Checkbox
When checked, the system will automatically number any agreements that are created using an agreement type that is not also set to auto number.
 
Software Defaults, Agreements: Next Agreement No
The next number that will be used when creating agreements.
 
Software Defaults, Agreements: Agreeement No Length
The maximum length of the agreement numbers.
 
Software Defaults, Agreements: Default Agreement Type
The agreement type that will be automatically assigned to new agreements.
 
Software Defaults, Agreements:Planned Billing Auto Process Checkbox
When checked, the planned billing nightly auto-processing feature is active.
 
Software Defaults, Agreements: Processing Date
Indicates the date to use when processing planned billing.
 
Software Defaults, Agreements: Deferred Revenue Auto Process
When checked, the deferred revenues nightly auto-renewal feature is active.
 
Software Defaults, Agreements: Agreement Renewals Auto Process
When checked, the planned billing nightly auto-renewal feature is active.
 
Software Defaults, Agreements: Agreement Type PRO Include Site Details on Invoice
When checked, the site details will appear on the invoices.
 
Software Defaults, Agreements:Agreement Type PRO Include Equipment Details on Invoice
When checked, the equipment details will appear on the invoices.
 
Software Defaults, Agreements: Agreement Type PRO Include Site Summary on Invoice
When checked, the site summary information will appear on the invoices.
 
Software Defaults, AgreementsAgreement Type PRO Include Equipment Summary on Invoice:
When checked, the equipment summary information will appear on the invoices.
 
Software Defaults, Agreements: Revenue Account
The default revenue account that will be assigned to new allocations.
 
Software Defaults, Agreements: Deferred Revenue Account
The default deferred revenue account that will be assigned to new allocations.
 
Software Defaults, Agreements: Item
Desc here: The default item that will be assigned to new allocations.
 
Service Type
   Service Types are used to organize jobs using a job type, service type relationship.
 
Service Type: Code
   Used to identify the service type.
 
Service Type: Desc
   Used to describe the service type.
   


 
Site: Address
   The physical address for the site.  This field is used in dispatching.
 
Site: Branch
   The site branch is required if multi-branching is in use.
 
Site: Chain
   The site's chain.  Chains are not required.
 
Site: City
   The address city for the site.  This field is used in dispatching.
 
Site: Clone From Customer Address
   When clicked, this button will clone the customer's address to the site.
 
Site: Clone From Ship To
   When an item is selected, the ship to address will be copied to the site address fields.
 
Site: Code
   The site code can be used to identify the site.  It is not required.
 
Site: Established Date
   The date the site was added.
 
Site: Fax Number
   The site's Fax number. 
 
Site: Labor #1
   Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
 
Site: Labor #2
   Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
 
Site: Latitude
   The latitude for the site location. 
 
Site: Longitude
   The longitude for the site location.
 
Site: Main Number
   The main business contact telephone number for the site.
 
Site: Map Code
   When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page.
 
Site: Name
   The name of the site location. This is used to identify the site.
 
Site: Price Level
   The price level that should be used when billing jobs.
 
Site: Primary Contact
   The site's primary contact.  Contacts are management using the Contact Mangement system. 
 
Site: Referral Code
   The site's referral code.  Referral codes are not required.
 
Site: Servicer #1
   The default primary servicer.  New jobs will be automatically assigned to this servicer.   
 
Site: Servicer #2
   The secondary servicer for new jobs.
 
Site: SLA
   Check this box, if the site qualifies for SLA service. 
 
Site: State
   The address state code for the site.  This field is used in dispatching.
 
Site: Store Number
   The store number for the site.  The store number is directly tied to the Chains feature. 
   
 
Site: Store Type
   The store type for the site.  The store number is directly tied to the Chains feature. 
 
Site: Type
   Site types are used to organize sites. Site types are not required. 
 
Site: Zip Code
   The address postal code for the site.  This field is used in dispatching.


 
Site Type
   Sites can be grouped by site type.
 
Site Type: Code
   The code used to identify the site type.
 
Site Type: Description
   The description used to identify the site type.
 
Site Type: Message
   The message of the Service Site Type will default into the field or manually type a customer note into the field. If the Service Site Type is changed the message will not change.





 
Solution
   Solutions are defined using the Solution Management feature.  The solution defines the work done to complete the work.
 
Solution Notes
   Solution notes are used to further define the work performed.
 
Subclass
   The sub-classification is used in sales and cost account assignments. 



 
Tasks: Type
Tasks can be organized by type.
 
Tasks: Status
Tasks can be tracked by status.
 
Tasks: Details
Task details provide a description of the task.
 
Tasks: URL
The URL field is used to store the website related to the task.
 
Tasks: Notes
Notes can be stored for each task.
 
Tasks: Due Date
Task can be tracked by due date.
 
Tasks: Due Time
Task can be tracked by due time.
 
Tasks: Assignment Type
Tasks can be assigned to individual by type.
       Account Manager
       Salesperson
       Servicer
       User
 
Tasks: Assigned To
The individual that will handle the task.
 
Tasks: Email
An email can be stored with the task.
 
Tasks: Text Phone
A telephone number for texting can be stored with the task.






 
Tax Class
   The item's task class.
 
Tax Exempt Number
   If the customer is tax exempt, a value must be used in this field.  
 
Tax Schedule
   The customer's tax schedule.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 
Terms
   The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 
Transaction Billed Status
Indicates the transaction's position in the billing process.
       N = Not billed
       I = On an unposted invoice
       Y = On a posted invoice
 
Transaction Date
The date the transaction will post to the general ledger.
 
Transaction Type
The type of transaction. The type is used to group the transactions by labor, materials or purchases.




 
Work Order: Est Hours
   The hours estimated to complete the work order.