Difference between revisions of "Glossary"

From SVContheGO Online Manual
Jump to navigation Jump to search
m
m
 
(118 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
{| border="0" cellpadding="1" cellspacing="1" style="width: 1538px;"
 
{| border="0" cellpadding="1" cellspacing="1" style="width: 1538px;"
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customeraccountmanager">&nbsp;</div>  
+
| colspan="1" id="Top" style="width: 1538px;" | <div class="fieldHeader">Glossary</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Account Manager</div>  
+
| <div id="job_acctmanager">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Account Manager</div>
 +
|-
 +
|
 +
    Account managers are responsible for the customer relationship. Account managers are assigned to customers and(or) jobs.
 +
 
 
|-
 
|-
 
| colspan="1" style="width: 1538px;" | <div id="activestatus">&nbsp;</div>  
 
| colspan="1" style="width: 1538px;" | <div id="activestatus">&nbsp;</div>  
Line 12: Line 16:
 
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Active Status</div>  
 
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Active Status</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates that the record can be used to produce results.
 +
 
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div id="customeraddress">&nbsp;</div>  
+
| <div id="AgreementAnnvDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Anniversary Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The date the agreement terms will end.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerbillingcontact">&nbsp;</div>  
+
| <div id="AgreementAutoRenew.25">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Billing Contact</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Auto Renew%</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates the amount percent of increase for the agreement renewal.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customercity">&nbsp;</div>  
+
| <div id="AgreementBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Balance</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The current balance of the contract.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customercountry">&nbsp;</div>  
+
| <div id="agreements_Billable">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Country</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Billable Checkbox</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When checked, indicates that the agreement will be included in the billing process.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customeremail">&nbsp;</div>  
+
| <div id="AgreementBillingTotal">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Billing Total</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The total contract amount for the agreement.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerext">&nbsp;</div>  
+
| <div id="AgreementCommissionRate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Ext</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Commission Rate</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The commission rate that will be used when billing the agreement.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerfacebook">&nbsp;</div>  
+
| <div id="AgreementContact">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Facebook</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Contact</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The person that should be contacted concerning the agreement.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerfax">&nbsp;</div>  
+
| <div id="AgreementMonths">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Fax</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Contact Months</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The number of months covered by the agreement.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerlinkedin">&nbsp;</div>  
+
| <div id="AgreementCoverLabor">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer LinkedIn</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Cover Labor</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates if the agreement covers labor transactions.
 +
 
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div id="Cust_Name">&nbsp;</div>  
+
| <div id="AgreementCoverParts">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Cover Parts</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates if the agreement covers parts transactions.
 +
 
 +
&nbsp;
 +
 
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div id="customer_number">&nbsp;</div>  
+
| <div id="AgreementCurrentContractAmount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Current Contract Amount</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The amount of the contract at the time of creation.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerphone">&nbsp;</div>  
+
| <div id="AgreementDefRevBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Deferred Revenue Balance</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The current balance of deferred revenues for the contract.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerpricelevel">&nbsp;</div>  
+
| <div id="AgreementDefRevenuesTotal">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Price Level</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Deferred Revenues Total</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The total deferred revenues posted to date.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customersalesperson">&nbsp;</div>  
+
| <div id="AgreementEstDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Salesperson</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Established Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The date the agreement was first established
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerstate">&nbsp;</div>  
+
| <div id="AgreementFreeMonths">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Free Months</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The number of months the customer is being provide for free.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customertaxschedule">&nbsp;</div>  
+
| <div id="AgreementFrequency">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Tax Schedule</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Frequency</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The billing frequency. i.e., Annually, Monthly
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customertaxexemptno">&nbsp;</div>  
+
| <div id="AgreementGrossProfitContactBilledtoDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Tax Exempt No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Gross Profit Contact Billed to Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The agreement's gross profit based on billings to date.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>  
+
| <div id="AgreementGrossProfitContractTermtoDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Terms</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Gross Profit Contract Term to Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The agreement's gross profit recorded on the contract to date.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customertwitter">&nbsp;</div>  
+
| <div id="AgreementLaborBudgetBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Twitter</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Balance&nbsp;%</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Percentage of labor budget balance to date.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerzip">&nbsp;</div>  
+
| <div id="AgreementLaborBudgetUsed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer Zip Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Used&nbsp;%</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Percentage of labor budget used to date.
 +
 
 
|-
 
|-
| <div id="site_CloneAddress">&nbsp;</div>  
+
| <div id="AgreementLaborBudgetHoursUsedtoDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Clone From: Customer Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Hours Used to Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The number of budgeted hours billed to date.
 +
 
 
|-
 
|-
| <div id="site_CloneShipTo">&nbsp;</div>  
+
| <div id="AgreementHoursBalance">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Clone From: Ship To</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Hours Balance</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The remainder of the budgeted hours to date.
 +
 
 
|-
 
|-
| <div id="site_Name">&nbsp;</div>  
+
| <div id="AgreementLaborHoursBudget">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Hours Budget</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The number of labor hours budgeted for the contract's term.
 +
 
 
|-
 
|-
| <div id="site_Type">&nbsp;</div>  
+
| <div id="AgreementLastIncrease">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Last Increase</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The increase amount from the last renewal.
 +
 
 
|-
 
|-
| <div id="site_EST">&nbsp;</div>  
+
| <div id="agreements_Number">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Est Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Number</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Agreement numbers are used to identify agreements. On the Job forms it indicates the agreement that may be used to cover transactions. On the PM Schedule form it indicates the agreement that is attached to the schedule.
 +
 
 
|-
 
|-
| <div id="site_Code">&nbsp;</div>  
+
| <div id="AgreementOriginalContractAmount">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Original Contract Amount</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The total price for the contract when started.
 +
 
 
|-
 
|-
| <div id="site_Address">&nbsp;</div>  
+
| <div id="AgreementPartsBilledtoDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Billed to Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The amount billed to date for parts.
 +
 
 
|-
 
|-
| <div id="site_Chain">&nbsp;</div>  
+
| <div id="AgreementPartsBudget">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Chain</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The total amount budgeted for parts on the agreement contract.
 +
 
 
|-
 
|-
| <div id="site_Referral">&nbsp;</div>  
+
| <div id="AgreementPartsBudgetBalance">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Referral Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Balance</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The remainder of the amount budgeted for parts to date after invoicing.
 +
 
 
|-
 
|-
| <div id="site_StoreNo">&nbsp;</div>  
+
| <div id="AgreementPartsBudgetBalance.25">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Store No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Balance&nbsp;%</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Percentage of parts budget balance to date.
 +
 
 
|-
 
|-
| <div id="site_SLA">&nbsp;</div>  
+
| <div id="AgreementPartsBudgetUsed">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site SLA</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Used&nbsp;%</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The amount of the parts budget billed to date.
 +
 
 
|-
 
|-
| <div id="site_StoreType">&nbsp;</div>  
+
| <div id="AgreementPriceLevel">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Store Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Price Level</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The price level that will be used when billing the agreement.
 +
 
 
|-
 
|-
| <div id="site_Priority">&nbsp;</div>  
+
| <div id="agreements_PricingMethod">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Priority</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Pricing Method</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Agreements can be priced based on the different methods. 
 +
        Blanket: One price covers all sites and equipment on the agreement. 
 +
        By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.
 +
 
 
|-
 
|-
| <div id="Priority">&nbsp;</div>  
+
| <div id="AgreementPriority">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Priority</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Priority</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The priority code that would be used for jobs created for agreement coverage.
 +
 
 
|-
 
|-
| <div id="site_Zip">&nbsp;</div>  
+
| <div id="AgreementPurchaseOrder">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Zip</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Purchase Order</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The purchase order provided by the customer for the agreement.
 +
 
 
|-
 
|-
| <div id="site_MapCode">&nbsp;</div>  
+
| <div id="AgreementRenewable">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Map Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewable</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates that the agreement is eligible for renewal. Eligible agreements will be included in the renewal process.
 +
 
 
|-
 
|-
| <div id="site_Branch">&nbsp;</div>  
+
| <div id="AgreementRenewalAmount">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Branch</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Amount</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The amount that will be billed on agreement renewal.
 +
 
 
|-
 
|-
| <div id="site_City">&nbsp;</div>  
+
| <div id="AgreementRenewalMethod">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Method</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    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.
 +
 
 
|-
 
|-
| <div id="site_State">&nbsp;</div>  
+
| <div id="AgreementRenewalMonths">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Months</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The contract months to use on the agreement's renewal.
 +
 
 
|-
 
|-
| <div id="site_PriceLevels">&nbsp;</div>  
+
| <div id="AgreementRenewalText">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Price Level</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Text</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The text that will be displayed on the agreement renewal invoice.
 +
 
 
|-
 
|-
| <div id="site_Lat">&nbsp;</div>  
+
| <div id="AgreementRenewAs">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Latitude</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renew As</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Used to indicate the type of invoice that will be created upon renewal.
 +
 
 
|-
 
|-
| <div id="site_Long">&nbsp;</div>  
+
| <div id="AgreementRevenuesTotal">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Longitude</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Revenues Total</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The total amount billed for the contract to date.
 +
 
 
|-
 
|-
| <div id="site_TaxSchedule">&nbsp;</div>  
+
| <div id="AgreementSalesperson">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Tax Schedule</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Salesperson</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The salesperson that should be assigned to the invoices when billing occurs.
 +
 
 
|-
 
|-
| <div id="site_MainNo">&nbsp;</div>  
+
| <div id="AgreementSLA">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Site Main No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: SLA</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates that the jobs created for this agreement are covered by SLA priority.
 +
 
 
|-
 
|-
| <div id="site_Fax">&nbsp;</div>  
+
| <div id="AgreementStartDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Fax No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Start Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The date the agreement terms will begin.
 +
 
 
|-
 
|-
| <div id="site_Labor1">&nbsp;</div>  
+
| <div id="AgreementStatusCode">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Labor #1</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Status Code</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The status code is used to track the agreements progress through the renewal process.
 +
 
 
|-
 
|-
| <div id="site_Servicer1">&nbsp;</div>  
+
| <div id="AgreementType">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Servicer #1</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Used to organize agreements by type. Agreement types are also used to establish settings for agreements by default.
 +
 
 
|-
 
|-
| <div id="site_PContact">&nbsp;</div>  
+
| <div id="agreeType_Code">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Primary Contact</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Code</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The agreement type code code is used to identify the agreement type.
 +
 
 
|-
 
|-
| <div id="site_Labor2">&nbsp;</div>  
+
| <div id="agreeType_Desc">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Labor #2</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Description</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The description used to identify the agreement type.
 +
 
 
|-
 
|-
| <div id="site_Servicer2">&nbsp;</div>  
+
| <div id="agreeType_coveredMths">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site Site Servicer #2</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Contract Months</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The number of months for new agreements.
 +
 
 
|-
 
|-
| Jobs Move up
+
| <div id="agreeType_coverparts">&nbsp;</div>
 
|-
 
|-
| <div id="job_number">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Parts Checkbox</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Number</div>
+
|  
 +
    When checked, the parts covered by the agreement will have no charge.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_coverLabor">&nbsp;</div>
 
|-
 
|-
| <div id="job_billed">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Labor Checkbox</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Billed Status</div>
+
|  
 +
    When checked, the parts covered by the agreement will have no charge.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_SLA">&nbsp;</div>
 
|-
 
|-
| <div id="job_mainno">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Checkbox</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Main No.</div>
+
|  
 +
    Check this box if the agreement qualifies for SLA service.  
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_SLAPC">&nbsp;</div>
 
|-
 
|-
| <div id="primaryservicer">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Priority Code</div>  
 
|-
 
|-
| <div class="fieldHeader">Primary Servicer</div>
+
|  
 +
    The SLA qualified priority code to use for new agreements.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_Message">&nbsp;</div>
 
|-
 
|-
| <div id="job_contact">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Message</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Contact</div>
+
|  
 +
    This message will appear on the agreement.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_LaborHoursBudget">&nbsp;</div>
 
|-
 
|-
| <div id="job_phone">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Labor Hours Budget</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Phone</div>
+
|  
 +
    The budgeted number of labor hours.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_PartsDollarsBudget">&nbsp;</div>
 
|-
 
|-
| <div id="job_ext">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Parts Dollars Budget</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Ext</div>
+
|  
 +
    The budgeted parts dollars.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_PercentUsed">&nbsp;</div>
 
|-
 
|-
| <div id="job_contactemail">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Percent Used >=</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Contact Email</div>
+
|  
 +
    Percentage of labor budget used.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeType_DollarsUsed">&nbsp;</div>
 
|-
 
|-
| <div id="job_sla">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Dollars Used >=</div>  
 
|-
 
|-
| <div class="fieldHeader">SLA</div>
+
|  
 +
    Percentage of parts dollars used.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_Billable">&nbsp;</div>
 
|-
 
|-
| <div id="job_status">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Auto Number by Type</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Status</div>
+
|  
 +
    When checked, new agreements will auto-number using the value in the Next Number field based on the Agreement Type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_Frequency">&nbsp;</div>
 
|-
 
|-
| <div id="jobType">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Next Number</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Type</div>
+
|  
 +
    Used when auto-numbering agreements.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>
 
|-
 
|-
| <div id="job_acctmanager">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Enforce Defaults</div>  
 
|-
 
|-
| <div class="fieldHeader">Account Manager</div>
+
|  
 +
    When checked, the agreement type defaults cannot be changed on the agreement.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_Billable">&nbsp;</div>
 
|-
 
|-
| <div id="job_receiveddate">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Billable</div>  
 
|-
 
|-
| <div class="fieldHeader">Received Date</div>
+
|  
 +
    When checked, the agreements assigned to the agreement type will be billable by default.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_Frequency">&nbsp;</div>
 
|-
 
|-
| <div id="job_servicetype">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Frequency</div>  
 
|-
 
|-
| <div class="fieldHeader">Service Type</div>
+
|  
 +
    The billing frequency. i.e., Annually, Monthly
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>
 
|-
 
|-
| <div id="job_saleperson">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Tax Class</div>  
 
|-
 
|-
| <div class="fieldHeader">Salesperson</div>
+
|  
 +
    The tax class that should be assigned to the invoice when the agreement is billed.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_Allocation">&nbsp;</div>
 
|-
 
|-
| <div id="job_scheduledate">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Allocation</div>  
 
|-
 
|-
| <div class="fieldHeader">Schedule Date</div>
+
|  
 +
    The allocation that will be assigned when processing agreements. Allocations are used to establish the general ledger posting accounts and amounts.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_DefRev">&nbsp;</div>
 
|-
 
|-
| <div id="job_slaExp">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Deferred Revenues</div>  
 
|-
 
|-
| <div class="fieldHeader">SLA Exp</div>
+
|  
 +
    When checked, new agreements will use the deferred revenue feature during the billing process.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_PricingMethod">&nbsp;</div>
 
|-
 
|-
| <div id="job_pmtmethod">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Pricing Method</div>  
 
|-
 
|-
| <div class="fieldHeader">Payment Method</div>
+
|  
 +
    The pricing method used when processing agreement transactions.
 +
        Blanket: One price covers all sites and equipment on the agreement. 
 +
        By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_IncludeSiteDetailsonInvoice">&nbsp;</div>
 
|-
 
|-
| <div id="job_refno">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Details on Invoice</div>  
 
|-
 
|-
| <div class="fieldHeader">Reference Number</div>
+
|  
 +
    When checked, the site details will appear on agreement invoices.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_IncludeEquipDetailsonInvoice">&nbsp;</div>
 
|-
 
|-
| <div id="job_request">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Details on Invoice</div>  
 
|-
 
|-
| <div class="fieldHeader">Request</div>
+
|  
 +
    When checked, equipment details will appear on agreement invoices.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>
 
|-
 
|-
| <div id="job_solution">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Summary on Invoice</div>  
 
|-
 
|-
| <div class="fieldHeader">Solution</div>
+
|  
 +
    When checked, a site summary will appear on agreement invoices.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>
 
|-
 
|-
| <div id="job_requestnote">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Summary on Invoice</div>  
 
|-
 
|-
| <div class="fieldHeader">Request Notes</div>
+
|  
 +
    When checked, an equipment summary will appear on agreement invoices.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePRO_IncludeSiteDetailsonInvoice">&nbsp;</div>
 
|-
 
|-
| <div id="job_solutionnotes">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewable Checkbox</div>  
 
|-
 
|-
| <div class="fieldHeader">Solution Notes</div>
+
|  
 +
    When checked, the agreement will be marked renewable on creation.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePRO_Months">&nbsp;</div>
 
|-
 
|-
| <div id="job_statusbar">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewal Months</div>  
 
|-
 
|-
| <div class="fieldHeader">Status Bar</div>
+
|  
 +
    The number of default renewal months on new agreements.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePRO_AS">&nbsp;</div>
 
|-
 
|-
| <div id="job_sendtomobile">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renew As</div>  
 
|-
 
|-
| <div class="fieldHeader">Send to Mobile</div>
+
|  
 +
    The default renew as value for new agreements. 
 +
 
 
|-
 
|-
| Desc here
+
| <div id="agreeTypePRO_Include_Site_Details_on_Renewal_Details">&nbsp;</div>
 
|-
 
|-
| Equipment starts here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Details on Invoice</div>
 
|-
 
|-
| <div id="equip_code">&nbsp;</div>
+
|  
 +
    When checked, the site details will appear on renewal invoices.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Equipment Code</div>  
+
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Details on Invoice</div>
 
|-
 
|-
| <div id="equip_item">&nbsp;</div>
+
|  
 +
    When checked, equipment details will appear on renewal invoices.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Equipment Item</div>  
+
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Summary on Invoice</div>
 
|-
 
|-
| <div id="equip_description">&nbsp;</div>
+
|  
 +
    When checked, a site summary will appear on renewal invoices.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Equipment Description</div>  
+
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Summary on Invoice</div>
 
|-
 
|-
| <div id="equip_installdate">&nbsp;</div>
+
|  
 +
    When checked, an equipment summary will appear on renewal invoices.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Install Date</div>  
+
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create a Job for each Equipment</div>
 
|-
 
|-
| <div id="equip_saledate">&nbsp;</div>
+
|  
 +
    When checked, planned maintenance will create a separate job for each equipment record assigned to the schedule.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Sale Date</div>  
+
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create Transactions</div>
 
|-
 
|-
| <div id="equip_serialno">&nbsp;</div>
+
|  
 +
    When checked, planned maintenance will automatically add the transactions to the generated jobs.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Serial No</div>  
+
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Price Transactions</div>
 
|-
 
|-
| <div id="equip_type">&nbsp;</div>
+
|  
 +
    When checked, planned maintenance will add the transactions, with pricing, to the generated jobs.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Equipment Type</div>  
+
| <div id="Allocation">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation</div>
 
|-
 
|-
| <div id="equip_warrlabor">&nbsp;</div>
+
|  
 +
    Allocations are used to distribute the agreement dollars to the required general ledger accounts. 
 +
 
 
|-
 
|-
| <div class="fieldHeader">Labor Warranty</div>  
+
| <div id="alloc_Desc">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Description</div>
 
|-
 
|-
| <div id="equip_warrlaborstart">&nbsp;</div>
+
|  
 +
    The description used to identify the allocation.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Labor Warranty Start</div>  
+
| <div id="alloc_revType">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Revenue Type</div>
 
|-
 
|-
| <div id="equip_warrlaborend">&nbsp;</div>
+
|  
 +
    Indicates if the allocation will be a percentage or fixed amount.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Labor Warranty End</div>  
+
| <div id="alloc_pricingMethod">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Pricing Method</div>
 
|-
 
|-
| <div id="equip_manufacturer">&nbsp;</div>
+
|  
 +
    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 sites and equipment on the agreement. 
 +
        By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Manufacturer</div>  
+
| <div id="alloc_price">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Price</div>
 
|-
 
|-
| <div id="equip_warrparts">&nbsp;</div>
+
|  
 +
    The allocation price. 
 +
        Blanket: One price covers all sites and equipment on the agreement.  Enter the price that will cover the entire contract.
 +
        By Site: The contract amount is a total of all site prices on the agreement. Enter the default price for a site.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Enter the default price for an equipment item.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Parts Warranty</div>  
+
| <div id="alloc_Type">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Type</div>
 
|-
 
|-
| <div id="equip_warrpartsstart">&nbsp;</div>
+
|  
 +
    The type of general ledger entry.
 +
        Deferred Revenue: Posts to a deferred revenue account.
 +
        Revenue: Post to a sales revenue account.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Parts Warranty Start</div>  
+
| <div id="alloc_miscItem">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Miscellaneous Item</div>
 
|-
 
|-
| <div id="equip_warrpartsend">&nbsp;</div>
+
|  
 +
    The miscellaneous item to use when posting to the ERP system.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Parts Warranty End</div>  
+
| <div id="alloc_Account">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Allocations Account</div>
 
|-
 
|-
| <div id="equip_mode">&nbsp;</div>
+
|  
 +
    The account that should be affected by the allocation transaction.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Model</div>  
+
| <div id="alloc_Amount">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Amount</div>
 
|-
 
|-
| <div id="equip_positionLocation">&nbsp;</div>
+
|  
 +
    The amount of the allocation transaction.
 +
 
 
|-
 
|-
| <div class="fieldHeader">EQ Position/Locations</div>  
+
| <div id="boTransEntry_WO">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Work Order</div>
 
|-
 
|-
| <div id="equip_coverageDate">&nbsp;</div>
+
|  
 +
    The transaction will be assigned to the selected work order.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Coverage Date</div>  
+
| <div id="boTransEntry_Stock">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Stock Radio Button</div>
 
|-
 
|-
| <div id="equip_level">&nbsp;</div>
+
|  
 +
    Toggles the Inventory search to include only material items.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Level</div>  
+
| <div id="boTransEntry_Nonstock">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Non-stock Radio Button</div>
 
|-
 
|-
| <div id="equip_comment">&nbsp;</div>
+
|  
 +
    Toggles the Inventory search to include only non-inventory material items.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Equipment Comment</div>  
+
| <div id="boTransEntry_FindCode">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Find by Item Code</div>
 
|-
 
|-
| Company Rep starts here
+
|  
 +
    Used to search for an item by the item's code.
 +
 
 
|-
 
|-
| <div id="corep_repno">&nbsp;</div>  
+
| <div id="boTransEntry_FindDesc">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Find by Item Description</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Used to search for an item by item's description.
 +
 
 
|-
 
|-
| <div id="corep_repname">&nbsp;</div>  
+
| <div id="boTransEntry_Servicer">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Servicer</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The servicer that will be assigned to the transaction. This field controls the warehouse list.
 +
 
 
|-
 
|-
| <div id="corep_reptype">&nbsp;</div>  
+
| <div id="boTransEntry_Agreement">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Agreement</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The agreement assigned to the selected work order.
 +
 
 
|-
 
|-
| <div id="corep_commrate">&nbsp;</div>  
+
| <div id="boTransEntry_Warehouse">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Commission Rate</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Warehouse</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The warehouse from where the item will be allocated.
 +
 
 
|-
 
|-
| <div id="corep_repphone">&nbsp;</div>  
+
| <div id="boTransEntry_CT">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Cost Type</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Used to assign general ledger account allocations.
 +
 
 
|-
 
|-
| <div id="corep_repemail">&nbsp;</div>  
+
| <div id="boTransEntry_EQ">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Equipment</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The equipment assigned to the selected work order.
 +
 
 
|-
 
|-
| <div id="corep_repdivision">&nbsp;</div>  
+
| <div id="boTransEntry_Covered">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Division</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Covered</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Indicates whether or not the transaction should be covered by either warranty or agreement. The software will determine the coverage based on the availably of coverage based on warranty and agreement settings.  If coverage exists, the price will change to 0.
 +
 
 
|-
 
|-
| <div id="corep_repaddress">&nbsp;</div>  
+
| <div id="boTransEntry_ItemCode">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Item Code</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The item code that will be used to identify the item.
 +
 
 
|-
 
|-
| <div id="corep_city">&nbsp;</div>  
+
| <div id="boTransEntry_TransDesc">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Trans Description</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The transaction description that will appear on the invoice. This can be different from the item description.
 +
 
 
|-
 
|-
| <div id="corep_state">&nbsp;</div>  
+
| <div id="boTransEntry_VendorList">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Vendor List</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Used to attach a vendor to the transaction.  Purchase transactions only.
 +
 
 
|-
 
|-
| <div id="corep_zip">&nbsp;</div>  
+
| <div id="boTransEntry_StartDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Zip</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Start Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The date the labor transaction started.  Labor transactions only.
 +
 
 
|-
 
|-
| <div id="corep_country">&nbsp;</div>  
+
| <div id="boTransEntry_TransDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Representative Country</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Trans Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The transaction date.  Inventory and Purchase transactions only.
 +
 
 
|-
 
|-
| Contact Section
+
| <div id="boTransEntry_StartTime">&nbsp;</div>
 
|-
 
|-
| <div id="contact_changeCustomer">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Start Time</div>  
 
|-
 
|-
| <div class="fieldHeader">Change Customer Button</div>
+
|  
 +
    The time the labor transaction started.  Labor transactions only.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_EndDate">&nbsp;</div>
 
|-
 
|-
| <div id="contact_changeSite">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: End Date</div>  
 
|-
 
|-
| <div class="fieldHeader">Change Site Button</div>
+
|  
 +
    The date the labor transaction ended.  Labor transactions only. This field is only available for use when multiple day transactions is on.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_EndTime">&nbsp;</div>
 
|-
 
|-
| <div id="contact_ContactName">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: End Time</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Name</div>
+
|  
 +
    The time the labor transaction ended.  Labor transactions only.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_NoUnits">&nbsp;</div>
 
|-
 
|-
| <div id="contact_Type">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: No Units</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Type</div>
+
|  
 +
    The number of units sold.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_Taxable">&nbsp;</div>
 
|-
 
|-
| <div id="contact_estDate">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Taxable</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Established Date</div>
+
|  
 +
    Checked when the transaction is taxable.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_Price">&nbsp;</div>
 
|-
 
|-
| <div id="contact_Title">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Price</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Title</div>
+
|  
 +
    The price of the item.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_Hidden">&nbsp;</div>
 
|-
 
|-
| <div id="contact_Salutation">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Hidden Line</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Salutation</div>
+
|  
 +
    When checked the item will not display on the invoice. It will be in the invoice total.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_UOM">&nbsp;</div>
 
|-
 
|-
| <div id="contact_address">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: UOM</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Address</div>
+
|  
 +
    The selected item's unit of measure.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_ExtPrice">&nbsp;</div>
 
|-
 
|-
| <div id="contact_firstName">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Ext Price</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact First Name</div>
+
|  
 +
    The unit price multiplied by the number of units.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="boTransEntry_BilledStatus">&nbsp;</div>
 
|-
 
|-
| <div id="contact_lastName">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Billed Status</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Last Name</div>
+
|  
 +
    Indicates the transaction's position in the billing process.
 +
        N = Not billed
 +
        I = On an unposted invoice
 +
        Y = On a posted invoice
 +
 
 
|-
 
|-
| Desc here
+
| <div id="servicetype_AssignedBtn">&nbsp;</div>
 
|-
 
|-
| <div id="contact_City">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Assigned</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact City</div>
+
|  
 +
    When clicked, displays all items assigned to the selected record.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="servicetype_NotAssingedBtn">&nbsp;</div>
 
|-
 
|-
| <div id="contact_state">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Not Assigned</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact State</div>
+
|  
 +
    When clicked, displays all the records not assigned to the selected item.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="callboards_FormName">&nbsp;</div>
 
|-
 
|-
| <div id="contact_zip">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Form Name</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Zip</div>
+
|  
 +
    The board name is used to identify the board.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="callboards_BoardType">&nbsp;</div>
 
|-
 
|-
| <div id="contact_country">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Board Type</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Country</div>
+
|  
 +
    There are three types of boards.  1) Call Central 2) Dispatch 3) Call Center
 +
 
 
|-
 
|-
| Desc here
+
| <div id="callboards_Private">&nbsp;</div>
 
|-
 
|-
| <div id="contact_email">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Private</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Email</div>
+
|  
 +
    Private boards will only appear in the list of the user that created the board.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="callboards_Default">&nbsp;</div>
 
|-
 
|-
| <div id="contact_fax">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Default</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Fax Number</div>
+
|  
 +
    The default form will be the top form in the boards form list.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="callboards_PastDuePosition">&nbsp;</div>
 
|-
 
|-
| <div id="contact_WorkPhone">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Past Due Position</div>  
 
|-
 
|-
| <div class="fieldHeader">Contact Phone</div>
+
|  
 +
    If a position is selected from this list, any jobs that are past due will color the cell according to the color settings in the selected position.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="callboards_DueWithinPosition">&nbsp;</div>
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Due Within Position</div>
 
|-
 
|-
| <div id="jobtype_Code">Job Type Management Setup here</div>
+
|  
 +
    If a position is selected from this list, any jobs that match the Due Within setting will color the cell according to the settings in the selected position.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Job Type Code</div>  
+
| <div id="callboards_PriorityPosition">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Priority Code Position</div>
 
|-
 
|-
| <div id="jobtype_Desc">&nbsp;</div>
+
|  
 +
    If a position is selected from this list and the color settings for priority codes are setup, the board will use the color settings in the selected position.
 +
 
 
|-
 
|-
| <div class="fieldHeader">Job Type Description</div>  
+
| <div id="callboards_JobTypesPosition">&nbsp;</div>  
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Job Type Position</div>
 
|-
 
|-
| <div id="EstHours">&nbsp;</div>  
+
|
 +
    If a position is selected from this list and the color settings for Job Types are setup, the board will use the color settings in the selected position.
 +
 
 +
|-
 +
| <div id="callboards_StatusCodesPosition">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Est Hours</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Status Code Position</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    If a position is selected from this list and the color settings for Status Codes are setup, the board will use the color settings in the selected position.
 +
 
 
|-
 
|-
| <div id="QuotedDollars">&nbsp;</div>  
+
| <div id="chain_Name">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Quoted $s</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Sites can be grouped by chain.
 +
 
 
|-
 
|-
| <div id="Opportunity">&nbsp;</div>  
+
| <div id="chain_Name">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Opportunity</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Name</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The name used to identify the chain.
 +
 
 
|-
 
|-
| <div id="jobtype_allcheckbox">&nbsp;</div>  
+
| <div id="chain_SLA">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Job Type All checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: SLA</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When checked, indicates the chain is an SLA chain. SLA chains have an expiration time for when the work is expected to be started.
 +
 
 
|-
 
|-
| <div id="servicetype_Code">&nbsp;</div>  
+
| <div id="chain_Inbound">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Service Type Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Inbound Path</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The inbound path.
 +
 
 
|-
 
|-
| <div id="servicetype_Desc">&nbsp;</div>  
+
| <div id="chain_Outbound">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Service Type Desc</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Outbound Path</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The outbound path.
 +
 
 
|-
 
|-
| <div id="KPICallCount">&nbsp;</div>  
+
| <div id="chain_storeTypeCode">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">KPI Call Count</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Code</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    Stores can be organized by type.
 +
 
 
|-
 
|-
| <div id="servicetype_AssignedBtn">&nbsp;</div>  
+
| <div id="chain_storeTypeName">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Assigned Button</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Name</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The name used to identify the store type.
 +
 
 
|-
 
|-
| <div id="servicetype_NotAssingedBtn">&nbsp;</div>  
+
| <div id="Classification">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Not Assigned Button</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Classification</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
 +
 
 
|-
 
|-
 
| <div id="servicetype_RemoveallAssnBtn">&nbsp;</div>  
 
| <div id="servicetype_RemoveallAssnBtn">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Remove all Assignments</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Remove all Assignments</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When clicked, removes all assignments from the selected record.
 +
 
 
|-
 
|-
| <div id="costtype_Desc">&nbsp;</div>  
+
| <div id="corep_commrate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Commission Rate</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The amount of commission that is earned when an item is sold.
 +
 
 
|-
 
|-
| <div id="Classification">&nbsp;</div>  
+
| <div id="contact_address">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Classification</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Address</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The contacts mailing address.
 +
 
 
|-
 
|-
| <div id="Subclass">&nbsp;</div>  
+
| <div id="contact_City">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Subclass</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: City</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The city of the contact's mailing address.
 +
 
 
|-
 
|-
| <div id="costtype_LaborCB">&nbsp;</div>  
+
| <div id="ContactbyEmail">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type Labor checkbox&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Email Checkbox</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When checked, indicates the customer would permit contact by email.
 +
 
 
|-
 
|-
| <div id="costtype_InventoryCB">&nbsp;</div>  
+
| <div id="ContactbyFax">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type Inventory checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Fax Checkbox</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When checked, indicates the customer would permit contact by fax.
 +
 
 
|-
 
|-
| <div id="costtype_PurchasesCB">&nbsp;</div>  
+
| <div id="ContactbyMail">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type Purchases checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Mail Checkbox</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When checked, indicates the customer would permit contact by mail.
 +
 
 
|-
 
|-
| <div id="costtype_RevAcct">&nbsp;</div>  
+
| <div id="ContactbyPhone">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Revenue Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Phone Checkbox</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    When checked, indicates the customer would permit contact by telephone.
 +
 
 
|-
 
|-
| <div id="costtype_RevSubacct">&nbsp;</div>  
+
| <div id="contact_country">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Revenue subaccount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Country</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The country of the mailing address.
 +
 
 
|-
 
|-
| <div id="costtype_CostAcct">&nbsp;</div>  
+
| <div id="contact_email">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type Cost Account&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Email</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The contact's email address.
 +
 
 
|-
 
|-
| <div id="costtype_CostSubacct">&nbsp;</div>  
+
| <div id="contact_estDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type Cost subaccount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Established Date</div>  
 
|-
 
|-
| Desc here
+
|  
 +
    The date the contact record was established.
 +
 
 
|-
 
|-
| <div id="inv_ItemType">&nbsp;</div>  
+
| <div id="contact_fax">&nbsp;</div>  
 
|-
 
|-
| Item Maintenance here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Fax Number</div>
 
|-
 
|-
| <div class="fieldHeader">Item Type</div>
+
|  
 +
    The contact's fax number.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_firstName">&nbsp;</div>
 
|-
 
|-
| <div id="inv_ItemCode">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: First Name</div>  
 
|-
 
|-
| <div class="fieldHeader">Item Code</div>
+
|  
 +
    The contact's first name.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_lastName">&nbsp;</div>
 
|-
 
|-
| <div id="inv_ItemDescription">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Last Name</div>  
 
|-
 
|-
| <div class="fieldHeader">Item Description</div>
+
|  
 +
    The contact's last name.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contactLinkedIn">&nbsp;</div>
 
|-
 
|-
| <div id="UseinMobile">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: LinkedIn</div>  
 
|-
 
|-
| <div class="fieldHeader">Use in Mobile</div>
+
|  
 +
    The contact's LinkedIn handle.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_ContactName">&nbsp;</div>
 
|-
 
|-
| <div id="MobileButton">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Name</div>  
 
|-
 
|-
| <div class="fieldHeader">Mobile Button</div>
+
|  
 +
    The contact's full name.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="OptOut">&nbsp;</div>
 
|-
 
|-
| <div id="CostType">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Opt Out Checkbox</div>  
 
|-
 
|-
| <div class="fieldHeader">Cost Type</div>
+
|  
 +
    When checked, indicates that the contact does not want to be contacted for the purpose of marketing.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_WorkPhone">&nbsp;</div>
 
|-
 
|-
| <div id="ProductLine">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Phone</div>  
 
|-
 
|-
| <div class="fieldHeader">Product Line</div>
+
|  
 +
    The contact's telephone number.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_Salutation">&nbsp;</div>
 
|-
 
|-
| <div id="SalesUOM">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Salutation</div>  
 
|-
 
|-
| <div class="fieldHeader">Sales UOM</div>
+
|  
 +
    The salutation that should be used when communicating with the contact.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_state">&nbsp;</div>
 
|-
 
|-
| <div id="TaxClass">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: State</div>  
 
|-
 
|-
| <div class="fieldHeader">Tax Class</div>
+
|  
 +
    The state of the contact's mailing address.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contactTeams">&nbsp;</div>
 
|-
 
|-
| <div id="Warehouse">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Teams</div>  
 
|-
 
|-
| <div class="fieldHeader">Warehouse</div>
+
|  
 +
    The contact's Teams handle.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_Title">&nbsp;</div>
 
|-
 
|-
| <div id="UnitPrice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Title</div>  
 
|-
 
|-
| <div class="fieldHeader">Unit Price</div>
+
|  
 +
    The contact title. ex: Mr., Mrs.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contactTwitter">&nbsp;</div>
 
|-
 
|-
| <div id="TradeDiscount">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Twitter</div>  
 
|-
 
|-
| <div class="fieldHeader">Trade Discount</div>
+
|  
 +
    The contact's Twitter handle.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_Type">&nbsp;</div>
 
|-
 
|-
| <div id="Commissionable">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Type</div>  
 
|-
 
|-
| <div class="fieldHeader">Commissionable</div>
+
|  
 +
    Contact Types can be used to organize contacts.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contactWeb">&nbsp;</div>
 
|-
 
|-
| <div id="SplitCommission">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Web</div>  
 
|-
 
|-
| <div class="fieldHeader">Split Commission</div>
+
|  
 +
    The contact's website address.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="contact_zip">&nbsp;</div>
 
|-
 
|-
| <div id="PriceCode">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Zip</div>  
 
|-
 
|-
| <div class="fieldHeader">Price Code</div>
+
|  
 +
    The postal code of the contact's mailing address.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="CostType">&nbsp;</div>
 
|-
 
|-
| <div id="unitcost">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type</div>  
 
|-
 
|-
| Unit Cost
+
|  
 +
    Cost types are used to manage general ledger sales and cost account allocations on transactions and billings.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costtype_CostAcct">&nbsp;</div>
 
|-
 
|-
| <div id="shordesc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Account</div>  
 
|-
 
|-
| Short Description
+
|  
 +
    The cost account that will be assigned to transactions that match the job type and cost type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costtype_CostSubacct">&nbsp;</div>
 
|-
 
|-
| <div id="EQBuild">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Subaccount</div>  
 
|-
 
|-
| Equipment Build checkbox
+
|  
 +
    The cost sub-account that will be assigned to transactions that match the job type and cost type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costtype_Desc">&nbsp;</div>
 
|-
 
|-
| <div id="itemPrefix">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Description</div>  
 
|-
 
|-
| Inventory Item Prefix
+
|  
 +
    Used to describe the cost type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costtype_InventoryCB">&nbsp;</div>
 
|-
 
|-
| <div id="AgreementType">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Inventory Checkbox</div>  
 
|-
 
|-
| Agreement Type
+
|  
 +
    When checked, indicates that the cost type can be used for inventory transactions.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costtype_LaborCB">&nbsp;</div>
 
|-
 
|-
| <div id="Allocation">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Labor Checkbox</div>  
 
|-
 
|-
| Allocation
+
|  
 +
    When checked, indicates that the cost type can be used for labor transactions.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costtype_PurchasesCB">&nbsp;</div>
 
|-
 
|-
| <div id="ReportingGroups">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Purchases Checkbox</div>  
 
|-
 
|-
| Reporting Groups
+
|  
 +
    When checked, indicates that the cost type can be used for purchase transactions.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="costVisibility">&nbsp;</div>
 
|-
 
|-
| <div id="EQB_comment">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Visibility</div>  
 
|-
 
|-
| Equipment Build Comment
+
|  
 +
    Cost visibility is the ability to hide cost from users.  Cost visibility is set at the user level in Account Management. If the checkbox is marked, the user will be able to view cost.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customeraccountmanager">&nbsp;</div>
 
|-
 
|-
| <div id="PriorityCode">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Account Manager</div>  
 
|-
 
|-
| Priority Code
+
|  
 +
    The company representative that manages the customer's account.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 706px;" | <div id="customeraddress">&nbsp;</div>
 
|-
 
|-
| <div id="">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Address</div>  
 
|-
 
|-
| &nbsp;
+
|  
 +
    The customer's mailing address. 
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerbillingcontact">&nbsp;</div>
 
|-
 
|-
| <div id="prio_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Billing Contact</div>  
 
|-
 
|-
| Priority Code Description
+
|  
 +
    The primary billing contact assigned to the customer.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customercity">&nbsp;</div>
 
|-
 
|-
| <div id="ResponseTime">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: City</div>  
 
|-
 
|-
| Response Time
+
|  
 +
    The customer's mailing address city.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customercountry">&nbsp;</div>
 
|-
 
|-
| <div id="prio_SLA">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Country</div>  
 
|-
 
|-
| SLA
+
|  
 +
    The customer's mailing address country.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customeremail">&nbsp;</div>
 
|-
 
|-
| <div id="prio_SLAExp">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Email</div>  
 
|-
 
|-
| SLA Expiration
+
|  
 +
    The email address for the primary customer contact.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerext">&nbsp;</div>
 
|-
 
|-
| <div id="prio_dow">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Ext</div>  
 
|-
 
|-
| Day of the Week
+
|  
 +
    The main telephone numbers extension.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerfacebook">&nbsp;</div>
 
|-
 
|-
| <div id="prio_starttime">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Facebook</div>  
 
|-
 
|-
| Priority Start Time
+
|  
 +
    Link to the customer's Facebook account.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerfax">&nbsp;</div>
 
|-
 
|-
| <div id="prio_endtime">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Fax</div>  
 
|-
 
|-
| Priority End Time
+
|  
 +
    The customer's contact fax number.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerlinkedin">&nbsp;</div>
 
|-
 
|-
| <div id="Manu_Code">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: LinkedIn</div>  
 
|-
 
|-
| Manufacturer Code
+
|  
 +
    The customer's linked in account handle.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 706px;" | <div id="Cust_Name">&nbsp;</div>
 
|-
 
|-
| <div id="Manu_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Name</div>  
 
|-
 
|-
| Manufacturer Description
+
|  
 +
    The name of the organization that will be billed.  Jobs can be created without a customer assignment, but not billed.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 706px;" | <div id="customer_number">&nbsp;</div>
 
|-
 
|-
| <div id="Manu_Prefix">&nbsp;</div>  
+
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Number</div>  
 
|-
 
|-
| Manufacturer Prefix
+
|  
 +
    Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerpricelevel">&nbsp;</div>
 
|-
 
|-
| <div id="model_Code">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Price Level</div>  
 
|-
 
|-
| Model Code
+
|  
 +
    The customer's price level.  Price level requirement is based on ERP settings.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerphone">&nbsp;</div>
 
|-
 
|-
| <div id="model_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Phone</div>  
 
|-
 
|-
| Model Description
+
|  
 +
    The customer's business telephone number.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customersalesperson">&nbsp;</div>
 
|-
 
|-
| <div id="model_prefix">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Salesperson</div>  
 
|-
 
|-
| Model Prefix
+
|  
 +
    The salesperson assigned to the customer's account.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerstate">&nbsp;</div>
 
|-
 
|-
| <div id="level_Code">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: State</div>  
 
|-
 
|-
| Level Code
+
|  
 +
    The customer's address state.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customertwitter">&nbsp;</div>
 
|-
 
|-
| <div id="level_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Twitter</div>  
 
|-
 
|-
| Level Description
+
|  
 +
    The customer's twitter handle.
 +
 
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div id="customerzip">&nbsp;</div>
 
|-
 
|-
| <div id="level_prefix">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Zip Code</div>  
 
|-
 
|-
| Level Prefix
+
|  
 +
    The customer's address zip code.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="DispatchCardNumber">&nbsp;</div>
 
|-
 
|-
| <div id="levelType">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Card Number</div>  
 
|-
 
|-
| Level Type
+
|  
 +
    Dispatch cards are numbered from 0 up.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="Dispatch_Number">&nbsp;</div>
 
|-
 
|-
| <div id="EQType_CODE">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Number</div>  
 
|-
 
|-
| Equipment Type Code
+
|  
 +
    The number used to identify the dispatch card.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="DispatchCardPriority">&nbsp;</div>
 
|-
 
|-
| <div id="EQType_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Priority</div>  
 
|-
 
|-
| Equipment Type Description
+
|  
 +
    The priority assigned to the dispatch card.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="PrimaryDispatchCard">&nbsp;</div>
 
|-
 
|-
| <div id="EQType_Prefix">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Primary Dispatch Card</div>  
 
|-
 
|-
| Equipment Type Prefix
+
|  
 +
    Once a job is created, the primary dispatch card is created. Users can also generate additional dispatch cards.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="DispatchCardScheduleDate">&nbsp;</div>
 
|-
 
|-
| <div id="Location">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Schedule Date</div>  
 
|-
 
|-
| Location
+
|  
 +
    The dispatch card's schedule date.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="DispatchCardScheduleTime">&nbsp;</div>
 
|-
 
|-
| <div id="sitetype_Code">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Schedule Time</div>  
 
|-
 
|-
| Site Type Code
+
|  
 +
    The dispatch card's schedule time.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="Servicer">&nbsp;</div>
 
|-
 
|-
| <div id="sitetype_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Servicer</div>  
 
|-
 
|-
| Site Type Description
+
|  
 +
    The servicer that is assigned the work. 
 +
 
 
|-
 
|-
| Desc here
+
| <div id="DispatchCardStatus">&nbsp;</div>
 
|-
 
|-
| <div id="sitetype_Message">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Status</div>  
 
|-
 
|-
| Site Type Message
+
|  
 +
    The status assigned to the individual dispatch card.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_code">&nbsp;</div>
 
|-
 
|-
| <div id="chain_Name">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Code</div>  
 
|-
 
|-
| Chain Name
+
|  
 +
    Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_comment">&nbsp;</div>
 
|-
 
|-
| <div id="chain_SLA">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Comments</div>  
 
|-
 
|-
| Chain SLA
+
|  
 +
    Comments related to the equipment record. 
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_coverageDate">&nbsp;</div>
 
|-
 
|-
| <div id="chain_Inbound">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Coverage Date</div>  
 
|-
 
|-
| Inbound Path
+
|  
 +
    The date coverage begins for the equipment record.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_description">&nbsp;</div>
 
|-
 
|-
| <div id="chain_Outbound">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Description</div>  
 
|-
 
|-
| Outbound Path
+
|  
 +
    Used to describe the equipment.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_item">&nbsp;</div>
 
|-
 
|-
| <div id="chain_storeTypeCode">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Item</div>  
 
|-
 
|-
| Store Type Code
+
|  
 +
    Equipment records that are also inventory items will have the Item Code in this field.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_installdate">&nbsp;</div>
 
|-
 
|-
| <div id="chain_storeTypeName">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Install Date</div>  
 
|-
 
|-
| Store Type Name
+
|  
 +
    The date the equipment was installed on site.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_warrlabor">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_Code">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Checkbox</div>  
 
|-
 
|-
| Agreement Type Code
+
|  
 +
    When checked, indicates the equipment is covered by a labor warranty.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_warrlaborend">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty End</div>  
 
|-
 
|-
| Agreement Type Description
+
|  
 +
    The date the labor warranty ends.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_warrlaborstart">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_coveredMths">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Start</div>  
 
|-
 
|-
| Agreement Contract Months
+
|  
 +
    The date the labor warranty begins.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_level">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_coverparts">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Level</div>  
 
|-
 
|-
| Agreement Cover Parts
+
|  
 +
    Levels are linked to models.  If the level does not appear in the Level drop-list, check the selected model’s setup.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_manufacturer">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_coverLabor">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Manufacturer</div>  
 
|-
 
|-
| Agreement Cover Labor
+
|  
 +
    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.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_mode">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_SLA">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Model</div>  
 
|-
 
|-
| SLA
+
|  
 +
    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.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_warrparts">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_SLAPC">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Checkbox</div>  
 
|-
 
|-
| SLA Priority
+
|  
 +
    When checked, indicates the equipment is covered by a parts warranty.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_warrpartsend">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_Message">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty End</div>  
 
|-
 
|-
| Agreement Message
+
|  
 +
    The date the parts warranty ends.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_warrpartsstart">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_LaborHoursBudget">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Start</div>  
 
|-
 
|-
| Labor Hours Budget
+
|  
 +
    The date the parts warranty begins.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_saledate">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_PartsDollarsBudget">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Sale Date</div>  
 
|-
 
|-
| Parts Dollars Budget
+
|  
 +
    The date the equipment was sold to the customer.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_serialno">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_PercentUsed">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Serial Number</div>  
 
|-
 
|-
| Agreement Type Percent >=
+
|  
 +
    The equipment's serial number.  This is not required. 
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_type">&nbsp;</div>
 
|-
 
|-
| <div id="agreeType_DollarsUsed">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Type</div>  
 
|-
 
|-
| Agreement Type Dollars >=
+
|  
 +
    Equipment types are used to organize equipment.  Manufacturers are assigned by equipment type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="equip_positionLocation">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_Billable">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Position/Locations</div>  
 
|-
 
|-
| Agreement Type PIO Billable
+
|  
 +
    Indicates the equipment's physical location.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="EQType_CODE">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_Frequency">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type</div>  
 
|-
 
|-
| Agreement Type PIO Frequency
+
|  
 +
    Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="EQType_CODE">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Code</div>  
 
|-
 
|-
| Agreement Type PIO Tax Class
+
|  
 +
    The code that identifies the equipment type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="EQType_Desc">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_Allocation">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Description</div>  
 
|-
 
|-
| Agreement Type PIO Allocation
+
|  
 +
    The description used to identify the equipment type.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="EQType_Prefix">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_DefRev">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Prefix</div>  
 
|-
 
|-
| Agreement Type PIO Deferred Revenues
+
|  
 +
    The three digit prefix to use when auto-numbering new equipment records.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="estDollars">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_PricingMethod">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Estimated Dollars</div>  
 
|-
 
|-
| Agreement Type PIO Pricing Method
+
|  
 +
    The estimated billing amount required to complete the work.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="estHours">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_Price">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Estimated Hours</div>  
 
|-
 
|-
| Agreement Type PIO Pricing
+
|  
 +
    The hours estimated to complete the work.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="ftpServer">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">FTP Server</div>  
 
|-
 
|-
| Agreement Type PIO Include Site Details on Invoice
+
|  
 +
    The server address required to log into your ftp server account.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="ftpuser">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_IncludeEquipDetailsonInvoice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">FTP Username</div>  
 
|-
 
|-
| Agreement Type PIO Include Equipment Details on Invoice
+
|  
 +
    The server username required to log into your ftp server account.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="ftppassword">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">FTP Password</div>  
 
|-
 
|-
| Agreement Type PIO Include Site Summary on Invoice
+
|  
 +
    The server password that is required to log into your ftp server account.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="hiddenCheckbox">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Hidden Checkbox</div>  
 
|-
 
|-
| Agreement Type PIO Include Equipment Summary on Invoice
+
|  
 +
    When checked, the item to which the checkbox is assigned will be hidden on invoices.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="Commissionable">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commissionable</div>  
 
|-
 
|-
| Agreement Renewable
+
|  
 +
    When checked the item is commissionable.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="EQBuild">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_Months">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">&nbsp;</div> Inventory: Equipment Build Checkbox
 
|-
 
|-
| Agreement Renewal Months
+
|  
 +
    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.
 +
        [[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]]
 +
 
 
|-
 
|-
| Desc here
+
| <div id="inv_ItemCode">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_AS">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Code</div>  
 
|-
 
|-
| Agreement Renew As
+
|  
 +
    Used to identify the item.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="inv_ItemDescription">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_Include_Site_Details_on_Renewal_Details">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Description</div>  
 
|-
 
|-
| Agreement Type PRO Include Site Details on Invoice
+
|  
 +
    Describes the item. This information comes from the ERP system.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="inv_ItemType">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Type</div>  
 
|-
 
|-
| Agreement Type PRO Include Equipment Details on Invoice
+
|  
 +
    Indicates the type of Item.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="itemPrefix">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Prefix</div>  
 
|-
 
|-
| Agreement Type PRO Include Site Summary on Invoice
+
|  
 +
    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.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="PriceCode">&nbsp;</div>
 
|-
 
|-
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Price Code</div>  
 
|-
 
|-
| Agreement Type PRO Include Equipment Summary on Invoice
+
|  
 +
    The item's price code. The price code is used when calculating transaction pricing.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="ProductLine">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_Desc">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Product Line</div>  
 
|-
 
|-
| Allocations Description
+
|  
 +
    The item's product line.   
 +
 
 
|-
 
|-
| Desc here
+
| <div id="SalesUOM">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_revType">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Sales UOM</div>  
 
|-
 
|-
| Allocations Revenue Type
+
|  
 +
    The item's unit of measure.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="MobileButton">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_pricingMethod">&nbsp;</div>  
+
| <div class="fieldHeader">Inventory: Servicer Mobile Button</div>  
 
|-
 
|-
| Allocations Pricing Method
+
|  
 +
    When checked, a mobile button will be made available in mobile for quick entry.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="shordesc">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_price">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Short Description</div>  
 
|-
 
|-
| Allocations Price
+
|  
 +
    A short description for the item. This description may be limited by ERP systems.  Users can set the size of this field. When changed the software will replace the existing short description with a new short description using the number of characters stored in this field.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="SplitCommission">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_Type">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Split Commission</div>  
 
|-
 
|-
| Allocations Type
+
|  
 +
    When checked, commission on the item can be slit.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="TradeDiscount">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_miscItem">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Trade Discount</div>  
 
|-
 
|-
| Allocations Miscellaneous Item
+
|  
 +
    When checked, discounts are allowed. 
 +
 
 
|-
 
|-
| Desc here
+
| <div id="unitcost">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_Account">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Cost</div>  
 
|-
 
|-
| Allocations Account
+
|  
 +
    The item's cost.   
 +
 
 
|-
 
|-
| Desc here
+
| <div id="UnitPrice">&nbsp;</div>
 
|-
 
|-
| <div id="alloc_Amount">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Price</div>  
 
|-
 
|-
| Allocations Amount
+
|  
 +
    The price for the item when added to a transaction.
 +
 
 
|-
 
|-
| Desc here
+
| <div id="UseinMobile">&nbsp;</div>
 
|-
 
|-
| Servicers Start Here
+
| <div class="fieldHeader">Inventory: Use in Mobile</div>
 
|-
 
|-
| <div id="servicer_Number">&nbsp;</div>
+
|  
 +
    When checked, the item will be available for use in mobile.
 +
 
 
|-
 
|-
| Service Number
+
| <div id="Warehouse">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Warehouse</div>
 
|-
 
|-
| <div id="servicer_employee">&nbsp;</div>
+
|  
 +
    The item's default warehouse.
 +
 
 
|-
 
|-
| Employee Number
+
| <div id="job_billed">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Billed Status</div>
 
|-
 
|-
| <div id="servicer_subcontractor">&nbsp;</div>
+
|  
 +
    Indicates where the job is in the billing process.
 +
 
 
|-
 
|-
| Subcontractor
+
| <div id="job_contact">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact</div>
 
|-
 
|-
| <div id="svr_Name">&nbsp;</div>
+
|  
 +
    The site or customer contact assigned to the job.
 +
 
 
|-
 
|-
| Servicer Name
+
| <div id="job_contactemail">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact Email</div>
 
|-
 
|-
| <div id="svr_Vendor">&nbsp;</div>
+
|  
 +
    The email address for the job contact.
 +
 
 
|-
 
|-
| Vendor
+
| <div id="job_ext">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Extension</div>
 
|-
 
|-
| <div id="svr_Address">&nbsp;</div>
+
|  
 +
    The extension number for the contact telephone number
 +
 
 
|-
 
|-
| Servicer Address
+
| <div id="jobtype_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Job Type Code</div>
 
|-
 
|-
| <div id="svr_BillingRate">&nbsp;</div>
+
|  
 +
    Used to recognize the job type.
 +
 
 
|-
 
|-
| Servicer Billing Rate
+
| <div id="job_mainno">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Main Number</div>
 
|-
 
|-
| <div id="svr_PORequired">&nbsp;</div>
+
|  
 +
    The job's main contact telephone number
 +
 
 
|-
 
|-
| Servicer PO Required
+
| <div id="job_notes">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Notes</div>
 
|-
 
|-
| <div id="svr_HrlyCost">&nbsp;</div>
+
|  
 +
    Job notes are unlimited and can be printed on documents. 
 +
 
 
|-
 
|-
| Servicer Hourly Cost
+
| <div id="job_number">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Number</div>
 
|-
 
|-
| <div id="svr_InsCert">&nbsp;</div>
+
|  
 +
    Used to identify the job.
 +
 
 
|-
 
|-
| Insurance Certificate on File
+
| <div id="job_pmtmethod">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Payment Method</div>
 
|-
 
|-
| <div id="svr_burden">&nbsp;</div>
+
|  
 +
    The default payment method.
 +
 
 
|-
 
|-
| Servicer Burden
+
| <div id="job_phone">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Phone</div>
 
|-
 
|-
| <div id="svr_certFile">&nbsp;</div>
+
|  
 +
    The contact telephone number for the job.
 +
 
 
|-
 
|-
| Certificate File Name
+
| <div id="primaryservicer">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Primary Servicer</div>
 
|-
 
|-
| <div id="svr_city">&nbsp;</div>
+
|  
 +
    The primary servicer for the job. New jobs will automatically use the primary servicer. Set up on the site level servicer #1
 +
 
 
|-
 
|-
| Servicer City
+
| <div id="job_receiveddate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Date</div>
 
|-
 
|-
| <div id="svr_warehouse">&nbsp;</div>
+
|  
 +
    The date the job was entered into the system by a user.
 +
 
 
|-
 
|-
| Servicer Warehouse
+
| <div id="job_receivedtime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Time</div>
 
|-
 
|-
| <div id="svr_terms">&nbsp;</div>
+
|  
 +
    The time the job was received from the customer.   
 +
 
 
|-
 
|-
| Servicer Terms
+
| <div id="job_refno">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Reference Number</div>
 
|-
 
|-
| <div id="svr_State">&nbsp;</div>
+
|  
 +
    The default payment reference number.
 +
 
 
|-
 
|-
| Servicer State
+
| <div id="job_saleperson">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Salesperson</div>
 
|-
 
|-
| <div id="svr_Zip">&nbsp;</div>
+
|  
 +
    The salesperson for the job.  *Certain ERP systems require a salesperson.
 +
 
 
|-
 
|-
| Servicer Zip
+
| <div id="job_servicetype">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Service Type</div>
 
|-
 
|-
| <div id="svr_Email">&nbsp;</div>
+
|  
 +
    Service types are used to organize and recognize jobs.  Service types are organized by job type.
 +
 
 
|-
 
|-
| Servicer Email
+
| <div id="job_sla">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Checkbox</div>
 
|-
 
|-
| <div id="svr_Mobile">&nbsp;</div>
+
|  
 +
    Check this box if the job qualifies for SLA service. This defaults from the site.
 +
 
 
|-
 
|-
| Servicer Mobile checkbox
+
| <div id="job_slaExp">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Date</div>
 
|-
 
|-
| <div id="svr_country">&nbsp;</div>
+
|  
 +
    The date the technician must start the work to meet the SLA criteria.
 +
 
 
|-
 
|-
| Servicer Country
+
| <div id="job_slaExpTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Time</div>
 
|-
 
|-
| <div id="svr_estDate">&nbsp;</div>
+
|  
 +
    The time the technician must start the work to meet the SLA criteria.
 +
 
 
|-
 
|-
| Servicer Established Date
+
| <div id="job_status">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Status</div>
 
|-
 
|-
| <div id="svr_userList">&nbsp;</div>
+
|  
 +
    Status codes are used to determine the job's position in the work process.
 +
 
 
|-
 
|-
| Servicer User List
+
| <div id="job_statusbar">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Job: Status Bar</div>
 
|-
 
|-
| <div id="svr_phone">&nbsp;</div>
+
|  
 +
    The status bar indicates the job's status progress.
 +
 
 
|-
 
|-
| Servicer Phone
+
| <div id="jobtype_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Description</div>
 
|-
 
|-
| <div id="svr_imgFile">&nbsp;</div>
+
|  
 +
    Used to describe the job type.
 +
 
 
|-
 
|-
| Servicer Image File
+
| <div id="EstHours">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Estimated Hours</div>
 
|-
 
|-
| <div id="svr_dispatchBatch">&nbsp;</div>
+
|  
 +
    The hours estimated to complete the job.
 +
 
 
|-
 
|-
| Service Dispatch Batch
+
| <div id="jobType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type</div>
 
|-
 
|-
| <div id="svr_tomtom">&nbsp;</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.
 +
 
 
|-
 
|-
| Servicer Tom Tom ID
+
| <div id="KPICallCount">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: KPI Call Count Checkbox</div>
 
|-
 
|-
| <div id="svr_userMapPin">&nbsp;</div>
+
|  
 +
    When checked the jobs assigned the job type will be counted in the KPI analytics.
 +
 
 
|-
 
|-
| Servicer User Map Pin
+
| <div id="Opportunity">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Opportunity</div>
 
|-
 
|-
| <div id="sd_overridejobno">&nbsp;</div>
+
|  
 +
    Marks the job type as a job opportunity.
 +
 
 
|-
 
|-
| Override Job Number
+
| <div id="jt_QuotedDollars">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Quoted $s</div>
 
|-
 
|-
| <div id="sd_sendjobemail">&nbsp;</div>
+
|  
 +
    The dollars quoted for the job.
 +
 
 
|-
 
|-
| Send Job Email
+
| <div id="kpi">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI</div>
 
|-
 
|-
| <div id="sd_jobNextNo">&nbsp;</div>
+
|  
 +
    KPI fields are indicators of job profit and profitability.
 +
 
 
|-
 
|-
| Job Next Number
+
| <div id="DepartureDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Date</div>
 
|-
 
|-
| <div id="sd_jobnumLength">&nbsp;</div>
+
|  
 +
    The date the job was changed to the departed status code.
 +
 
 
|-
 
|-
| Job Number Length
+
| <div id="DepartureTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Time</div>
 
|-
 
|-
| <div id="sd_jobnumLeadingChar">&nbsp;</div>
+
|  
 +
    The time the job was changed to the departed status code.
 +
 
 
|-
 
|-
| Job Number Leading Characters
+
| <div id="JobStartDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Date</div>
 
|-
 
|-
| <div id="sd_sc_new">&nbsp;</div>
+
|  
 +
    The date the job started.
 +
 
 
|-
 
|-
| Default Code - New
+
| <div id="JobStartTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Time</div>
 
|-
 
|-
| <div id="sd_sc_dispatched">&nbsp;</div>
+
|  
 +
    The time the job started.
 +
 
 
|-
 
|-
| Default Code - Dispatched
+
| <div id="JobCompleteDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Date</div>
 
|-
 
|-
| <div id="sd_sc_departure">&nbsp;</div>
+
|  
 +
    The date the job was marked complete.
 +
 
 
|-
 
|-
| Default Code - Departure
+
| <div id="JobCompleteTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Time</div>
 
|-
 
|-
| <div id="sd_sc_arrival">&nbsp;</div>
+
|  
 +
    The time the job was marked complete.
 +
 
 
|-
 
|-
| Default Code - Arrival
+
| <div id="JobRevenue">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Revenues</div>
 
|-
 
|-
| <div id="sd_sc_FC">&nbsp;</div>
+
|  
 +
    The total revenues to date.
 +
 
 
|-
 
|-
| Default Code - Field Completed
+
| <div id="JobElapseTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Elapse Time</div>
 
|-
 
|-
| <div id="sd_sc_cancelled">&nbsp;</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.
 +
 
 
|-
 
|-
| Default Code - Cancelled
+
| <div id="JobRepairTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Repair Time</div>
 
|-
 
|-
| <div id="sd_sc_onHold">&nbsp;</div>
+
|  
 +
    The labor hours posted to date.
 +
 
 
|-
 
|-
| Default Code - On Hold
+
| <div id="JobResponseTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Response Time</div>
 
|-
 
|-
| <div id="sd_sc_boCompleted">&nbsp;</div>
+
|  
 +
    The time between the received date/time and the arrival date/time.
 +
 
 
|-
 
|-
| Default Code - Back Office Completed
+
| <div id="JobProfit">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Profit</div>
 
|-
 
|-
| <div id="sd_ed_warrantyBasedOn">&nbsp;</div>
+
|  
 +
    The job's profit to date.
 +
 
 
|-
 
|-
| Setup Equipment Defaults Warranty Based On
+
| <div id="Jobbilledstatus">&nbsp;</div>
 
|-
 
|-
| Sales Date or Invoice Date
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Invoice Status</div>
 
|-
 
|-
| <div id="sd_ed_allocationBasedOn">&nbsp;</div>
+
|  
 +
    The job's billing status.
 +
 
 
|-
 
|-
| Setup Allocation Based On
+
| <div id="JobinvoiceDate">&nbsp;</div>
 
|-
 
|-
| Inventory Item or Model
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Invoice Date</div>
 
|-
 
|-
| <div id="taxOnCustomer">&nbsp;</div>
+
|  
 +
    The date the job was first invoiced.
 +
 
 
|-
 
|-
| Tax on Customer
+
| <div id="level_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels</div>
 
|-
 
|-
| <div id="multiBranch">&nbsp;</div>
+
|  
 +
    Models can be grouped by levels. Levels can be grouped by type.
 +
 
 
|-
 
|-
| Multi-Branch
+
| <div id="level_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Code</div>
 
|-
 
|-
| <div id="multiBranchSegment">&nbsp;</div>
+
|  
 +
    The code used to identify the level.
 +
 
 
|-
 
|-
| Mutli-Branch Segment
+
| <div id="level_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Description</div>
 
|-
 
|-
| <div id="salesAcct">&nbsp;</div>
+
|  
 +
    The description that identifies the level.
 +
 
 
|-
 
|-
| Sales Account
+
| <div id="level_prefix">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Prefix</div>
 
|-
 
|-
| <div id="costAcct">&nbsp;</div>
+
|  
 +
    The three digit prefix to use when auto-numbering new equipment records.
 +
 
 
|-
 
|-
| Cost Account
+
| <div id="levelType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Type</div>
 
|-
 
|-
| <div id="sd_Invoice_RequireSalesTax">&nbsp;</div>
+
|  
 +
    Level types are used to group levels.
 +
 
 
|-
 
|-
| Require Sales Tax
+
| <div id="Location">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Location</div>
 
|-
 
|-
| <div id="sd_Invoice_Non-TaxSchedule">&nbsp;</div>
+
|  
 +
    Indicates the physical location of a piece of equipment at a site.
 +
 
 
|-
 
|-
| Non-Tax Schedule
+
| <div id="Manufacturer">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer</div>
 
|-
 
|-
| <div id="sd_Invoice_IncludeRequest">&nbsp;</div>
+
|  
 +
    The manufacturer is assigned to equipment records.  The manufacturer is assigned models. 
 +
 
 
|-
 
|-
| Include Request
+
| <div id="Manu_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Code</div>
 
|-
 
|-
| <div id="sd_Invoice_IncludeRequestNotes">&nbsp;</div>
+
|  
 +
    The code used to identify the manufacturer. 
 +
 
 
|-
 
|-
| Include Request Notes
+
| <div id="Manu_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Description</div>
 
|-
 
|-
| <div id="sd_Invoice_IncludeSolution">&nbsp;</div>
+
|  
 +
    The description that identifies the manufacturer.
 +
 
 
|-
 
|-
| Include Solution
+
| <div id="Manu_Prefix">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Prefix</div>
 
|-
 
|-
| <div id="sd_Invoice_IncludeSolutionNotes">&nbsp;</div>
+
|  
 +
    The three digit prefix to use when auto-numbering new equipment records.
 +
 
 
|-
 
|-
| Include Solution Notes
+
| <div id="Message_TargetType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Target Type</div>
 
|-
 
|-
| <div id="sd_Invoice_IncludeJobNotes">&nbsp;</div>
+
|  
 +
    Defines the type of target audience for the message.
 +
 
 
|-
 
|-
| Include Job Notes
+
| <div id="Message_DefaultTargetType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Default Target Type</div>
 
|-
 
|-
| <div id="sd_Invoice_NextBatchNumber">&nbsp;</div>
+
|  
 +
    Defines the type of target audience for the message as the default value for new messages.
 +
 
 
|-
 
|-
| Next Batch Number
+
| <div id="Message_Target">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Target</div>
 
|-
 
|-
| <div id="sd_PM_IncludeSiteinfoascomment">&nbsp;</div>
+
|  
 +
    Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups.
 +
 
 
|-
 
|-
| PM Defaults Include Site info as comment
+
| <div id="Message_StartDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Start Date</div>
 
|-
 
|-
| <div id="sd_PM_IncludeEquipmentinfoascomment">&nbsp;</div>
+
|  
 +
    The first date active messages are displayed.
 +
 
 
|-
 
|-
| PM Defaults Include Equipment info as comment
+
| <div id="Message_EndDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: End Date</div>
 
|-
 
|-
| <div id="sd_AG_AutoNo">&nbsp;</div>
+
|  
 +
    The last date active messages will be displayed.  Note: All messages are removed after 72 hours.
 
|-
 
|-
| Agreement Setup Auto Number
+
| <div id="Message_MessageText">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Message Text</div>
 
|-
 
|-
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
+
|  
 +
    The content of the message.
 +
 
 
|-
 
|-
| Agreeement Setup Number Length
+
| <div id="Message_FieldComplete">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Field Complete</div>
 
|-
 
|-
| <div id="sd_AG_PB_autoProcess">&nbsp;</div>
+
|  
 +
    When checked an automatic message will generate when jobs are changed to the Field Complete status.
 +
 
 
|-
 
|-
| Planned Billing Auto Process
+
| <div id="Message_AutoShow">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Auto Show Messages</div>
 
|-
 
|-
| <div id="sd_AG_PB_ProcessingDate">&nbsp;</div>
+
|  
 +
    When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 +
 
 
|-
 
|-
| Processing Date
+
| <div id="MLTE_Servicer">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Mobile Transaction Entry: Servicer</div>
 
|-
 
|-
| <div id="sd_AG_DR_autoProcess">&nbsp;</div>
+
|  
 +
    The servicer that should be used when posting the transaction.
 +
 
 
|-
 
|-
| Deferred Revenue Auto Process
+
| <div id="model_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Code</div>
 
|-
 
|-
| <div id="sd_AG_AR_autoProcess">&nbsp;</div>
+
|  
 +
    The code used to identify the model. 
 +
 
 
|-
 
|-
| Agreement Renewals Auto Process
+
| <div id="model_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Description</div>
 
|-
 
|-
| <div id="sd_AG_AR_IncludeSiteDetailsascomment">&nbsp;</div>
+
|  
 +
    The description that identifies the model.
 +
 
 
|-
 
|-
| Agreement Type PRO Include Site Details on Invoice
+
| <div id="model_prefix">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Prefix</div>
 
|-
 
|-
| <div id="sd_AG_AR_IncludeEquipDetailsascomment">&nbsp;</div>
+
|  
 +
    The three digit prefix to use when auto-numbering new equipment records.
 +
 
 
|-
 
|-
| Agreement Type PRO Include Equipment Details on Invoice
+
| <div id="NoteCategory">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Category</div>
 
|-
 
|-
| <div id="sd_AG_AR_IncludeSiteSummaryascomment">&nbsp;</div>
+
|  
 +
    Notes can be organized by category.
 +
 
 
|-
 
|-
| Agreement Type PRO Include Site Summary on Invoice
+
| <div id="NoteContent">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Content</div>
 
|-
 
|-
| <div id="sd_AG_AR_IncludeEquipSummaryascomment">&nbsp;</div>
+
|  
 +
    The note content that will display on the form and print on any documents.
 +
 
 
|-
 
|-
| Agreement Type PRO Include Equipment Summary on Invoice
+
| <div id="NoteInternal">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Internal Note Checkbox</div>
 
|-
 
|-
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
+
|  
 +
    Internal notes do not print on invoices and dispatch cards.
 +
 
 
|-
 
|-
| Deferred Revenue Account
+
| <div id="NotePrintOnTicket">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Print Note on Ticket Checkbox</div>
 
|-
 
|-
| <div id="Item">&nbsp;</div>
+
|  
 +
    When checked, the note will print on the dispatch card.
 +
 
 
|-
 
|-
| Item
+
| <div id="PlannedMaintenanceType">&nbsp;</div>
 
|-
 
|-
| Desc here: What is an item and how is it used in the system.
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Type</div>
 
|-
 
|-
| <div id="TransactionDate">&nbsp;</div>
+
|  
 +
    Planned maintenance types are used to organize schedules and establish default values.
 +
 
 
|-
 
|-
| Transaction Date
+
| <div id="PlannedMaintenanceID">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: ID</div>
 
|-
 
|-
| <div id="TransactionType">&nbsp;</div>
+
|  
 +
    The ID is used to identify the schedule.
 +
 
 
|-
 
|-
| Transaction Type
+
| <div id="PlannedMaintenanceDescription">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Description</div>
 
|-
 
|-
| <div id="TransactionBilledStatus">&nbsp;</div>
+
|  
 +
    Descriptions can also help with identification.
 +
 
 
|-
 
|-
| Transaction Billed Status
+
| <div id="MaterialGroupCode">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Material Group Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Material Group Codes provide the ability to add materials to schedules by grouping.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="PlannedMaintenanceTaskCode">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Task Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    PM task codes are used to organize schedules and establish material group codes.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="Priority">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority</div>
 
|-
 
|-
| <div id="">&nbsp;</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.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="PriorityCode">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Priority codes are used to establish the response time when scheduling jobs.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="prio_dow">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Day of the Week</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, indicates that jobs can be scheduled on that day of the week.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="prio_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Description</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Describe the priority.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="prio_endtime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: End Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Indicates the latest time a job can be scheduled on each day of the week.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ResponseTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Response Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Indicates the number of hours between the received time and the scheduled time.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="prio_SLA">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="prio_SLAExp">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA Expiration</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number of hours that are required to meet the SLA deadline.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="prio_starttime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Start Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Indicated the earliest time a job can be scheduled on each day of the week.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="QuotedDollars">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Quoted Dollars</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The billing amount quoted for the job. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="QuotedHours">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Quoted Hours</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The hours quoted for the job.   
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="PurchaseOrderNumber">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Purchase Order Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The purchase order number issued by the customer for the work. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ReportingGroups">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Reporting Groups</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    A group code can be assigned to a miscellaneous charge code to group like Item codes.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_repaddress">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Address</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The mailing address for the representative.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_city">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: City</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The city for the mailing address
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_country">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Country</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The country for the mailing address.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_repdivision">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Division</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    If division are in use, the representative division can be assigned.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_repemail">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Email</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The email address can be used to contact the representative.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_repname">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Name</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The name of the representative.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_repno">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The representative number can be used to recognize a representative.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_repphone">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Phone</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The telephone number can be used to contact the representative.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_state">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: State</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The mailing address state.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_reptype">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Types are used to organize representatives.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="corep_zip">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Zip</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The postal code for the mailing address.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_request">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Requests are defined using the Request Management feature. The request defines the work requested.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_requestnote">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request Notes</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Request notes are used to further define the work requested.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="costtype_RevAcct">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue Account</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The sales account that will be assigned to transactions that match the job type and cost type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="costtype_RevSubacct">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue subaccount</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The sales sub-account that will be assigned to transactions that match the job type and cost type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="rolemanagement">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Role Management</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    User roles provide access to assigned forms while restricting access to unassigned forms.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_scheduledate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The date the technician is scheduled to do the work.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_scheduletime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The time the technician is scheduled to do the work.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="scheduleTime_ReasonCode">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Reason Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Describe the reason the servicer is not available for work.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="scheduleTime_startdate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Start Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The first date for the time off schedule.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="scheduleTime_enddate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: End Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The last date for the time off schedule.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="scheduleTime_starttime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Start Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The starting time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the start of the day for all dates except the first date.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="scheduleTime_endtime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: End Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The End time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the end of the day for all dates except the last date.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="scheduleTime_replicatetime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Replicate Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The replicate time option is used for date spans.  When checked the time on each day will match the start and end times in the fields.  If not, the first day will use the start time, the last day will use the end time and all days in between will display 24 hours of time.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_sendtomobile">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Send to Mobile Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    On save, if this checkbox is checked, the job will be made available in mobile.   
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicer_Number">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The technician that will perform the work.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicer_Number">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number used to identify the technician.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicer_employee">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Employee Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    If the servicer is also an employee, the employee number can be stored in this field.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicer_subcontractor">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Subcontractor Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, indicates that the servicer is a contracted employee or vendor.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_Name">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Name</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The name of the technician.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_Vendor">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Vendor</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    This field is used when the servicer is a vendor. The vendor is selected from the list and other vendor fields become available for use.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_Address">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Address</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The technician's mailing address.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_BillingRate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Billing Rate</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The technicians hourly labor billing rate.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_PORequired">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: PO Required Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the vendor requires a purchase order for all requested work.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_HrlyCost">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Hourly Cost</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The hourly cost for the technician.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_InsCert">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Insurance Certificate on File Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    For use with vendors or contract employees only. Indicates that a Certificate of Insurance is on file.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_burden">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Burden</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The hourly burden for the technician.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_certFile">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Certificate File Name</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The file name for the Certificate of Insurance.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_city">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: City</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The servicer's mailing address city.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_warehouse">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Warehouse</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The servicer's default warehouse.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_terms">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Terms</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    If the servicer is a vendor or contract employee, the terms for payment.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_State">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: State</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The servicer's mailing address state.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_Zip">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Zip</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The servicer's mailing address postal code.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_Email">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Email</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The servicer's email address.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_Mobile">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Mobile Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the servicer's jobs will appear on the mobile board.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_country">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Country</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The servicer's mailing address country
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_estDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Established Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The date the servicer relationship was established.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_userList">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User List</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Servicers must be assigned to a user login before the user can use the mobile system. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_phone">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Phone</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The telephone number for contacting the servicer.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_imgFile">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Servicer Image File</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The name of the file that contains an image of the technician.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_dispatchBatch">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Service Dispatch Batch</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Mobile jobs can be grouped by batch for posting to the back office.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_tomtom">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Tom Tom ID</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The Tom Tom ID for the servicer. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_userMapPin">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User Map Pin</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Technicians can be mapped using pins. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="svr_userMapPin">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults: New Job Defaults</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The values that will be used by default when adding new jobs.  Some 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#estHours|Est Hours]]
 +
        [[Glossary#ss_JobNextNo|Job Next No]]
 +
        [[Glossary#ss_JobLength|Job Length]]
 +
        [[Glossary#ss_JobLeadingCharacters|Job Leading Characters]]
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_OverrideJobNo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Override Job No Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, users are allowed to alter the job number.  Warning! This could interrupt the job numbering system.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SendJobEmail">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Send Job Email Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the send email form will be displayed when a new job is saved.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_EstHours">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Est Hours</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The hours estimated to complete the job. This value will be added to the primary work order.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_JobNextNo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Next No</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number that will be assigned to the next job.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_JobLength">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Length</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number of characters in the job number.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_JobLeadingCharacters">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Leading Characters</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The character(s) that will lead the job number. Leading characters are not required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_ShortDescSize">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The defaults that affect the inventory feature.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_ShortDescSize">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Short Desc Size</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number of characters to use for the short description for items. This can be changed, and the software will adjust the values of the field.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_ShortDescSize">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Button: Update Item Short Descriptions</div>
 
|-
 
|-
| <div id="">&nbsp;</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.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Status Code Defaults</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Status codes are used to move jobs through the workflow process.  Each status code on this form has a purpose.  Assign a status code to each slot.  *These are required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_ed">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Default values for new equipment records.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_ed_warrantyBasedOn">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Warranty Based On</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Warranties can be set based on the Sale Date or the installation date.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_ed_allocationBasedOn">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Allocation Based On</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    General ledger allocations can be based on the inventory item, or the model.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Auto No/EQ Defaults Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the system will automatically number new equipment records.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Options</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Auto-numbering can be defined using a prefix or a matrix.
 +
    Prefix: The prefix option will create the number using the equipment prefix followed by the next number.
 +
    Matrix: The matrix option allows the user to establish a prefix order from the prefixes assigned to the equipment types, manufacturers and models.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Prefix Missing Grid Column</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number of records that do not contain a prefix for the matrix to work properly.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Defaults values for new sites.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Site Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default site type for new sites.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Tax Schedule</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default tax schedule for new sites. This value is only used if the tax schedule is not filled from the customer record.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Use Customer Name and Address Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the customer’s name and address automatically fill in the site form when adding a new site.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_tad">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The defaults and settings for new transactions.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_tad_Warehouse">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Warehouse</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The warehouse to assign to any transaction for which a warehouse has not been assigned.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="taxOnCustomer">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Tax on Customer Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, invoices will automatically use the customer's tax schedule.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="multiBranch">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Multi-branch Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the multi-branch feature becomes active, and its rules applied.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="multiBranchSegment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Segment</div>
 
|-
 
|-
| <div id="">&nbsp;</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.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="salesAcct">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Sales Account</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The sales account to assign to any transaction for which a sales account has not been assigned. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="costAcct">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Cost Account</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The cost account to assign to any transaction for which a cost account has not been assigned. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="ss_inv">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The defaults and settings for new transactions.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_Invoice_RequireSalesTax">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Require Sales Tax Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, sales tax will be required on all invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_Invoice_Non">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Non-Tax Schedule</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Certain ERP system require a tax schedule on all invoices, even those that are non-tax.  This schedule fills that requirement.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_Invoice_NextBatchNumber">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next Batch Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The next batch to use when invoices are created automatically.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_Invoice_NextNumber">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next No</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The next invoice number.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_Invoice_Length">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Length</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The invoice number length.  This value cannot be shortened.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_Invoice_LeadingCharacters">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Leading Characters</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The leading character for invoice numbers.  Leading characters are not required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_PM">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The defaults and settings for planned maintenance jobs.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_PM_Priority">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Priority</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default priority for new planned maintenance jobs.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_PM_StatusCode">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Status Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The defaults status code for new planned maintenance jobs.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_PM_IncludeSiteinfoascomment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Site info as comment</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the site information will appear on planned maintenance invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_PM_IncludeEquipmentinfoascomment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Equipment info as comment</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the equipment information will appear on planned maintenance invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The settings and defaults for new agreements.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AutoNo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Auto No Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</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.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Next Agreement No</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The next number that will be used when creating agreements.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement No Length</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The maximum length of the agreement numbers.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Default Agreement Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The agreement type that will be automatically assigned to new agreements.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_PB_autoProcess">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Planned Billing Auto Process Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the planned billing nightly auto-processing feature is active.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_PB_ProcessingDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Processing Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Indicates the date to use when processing planned billing. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_DR_autoProcess">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Auto Process</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the deferred revenues nightly auto-renewal feature is active.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AR_autoProcess">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Renewals Auto Process</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the planned billing nightly auto-renewal feature is active.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AR_IncludeSiteDetailsascomment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Details on Invoice</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the site details will appear on the invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AR_IncludeEquipDetailsascomment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Equipment Details on Invoice</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the equipment details will appear on the invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AR_IncludeSiteSummaryascomment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Summary on Invoice</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the site summary information will appear on the invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_AR_IncludeEquipSummaryascomment">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Equipment Summary on Invoice:</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the equipment summary information will appear on the invoices.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Revenue Account</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default revenue account that will be assigned to new allocations.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Account</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default deferred revenue account that will be assigned to new allocations.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="Item">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Item</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default item that will be assigned to new allocations.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicetype">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Service Types are used to organize jobs using a job type, service type relationship.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicetype_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used to identify the service type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="servicetype_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Desc</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used to describe the service type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Address">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Address</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The physical address for the site.  This field is used in dispatching.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Branch">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Branch</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The site branch is required if multi-branching is in use.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Chain">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Chain</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The site's chain.  Chains are not required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_City">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: City</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The address city for the site.  This field is used in dispatching.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_CloneAddress">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Customer Address</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When clicked, this button will clone the customer's address to the site.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_CloneShipTo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Ship To</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When an item is selected, the ship to address will be copied to the site address fields.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The site code can be used to identify the site.  It is not required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_EST">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Established Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The date the site was added.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Fax">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Fax Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The site's Fax number.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Labor1">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Labor #1</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Labor2">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Labor #2</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Lat">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Latitude</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The latitude for the site location.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Long">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Longitude</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The longitude for the site location.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_MainNo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Main Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The main business contact telephone number for the site.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_MapCode">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Map Code</div>
 
|-
 
|-
| <div id="">&nbsp;</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.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Name">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Name</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The name of the site location. This is used to identify the site.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_PriceLevels">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Price Level</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The price level that should be used when billing jobs.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_PContact">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Primary Contact</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The site's primary contact.  Contacts are managed using the Contact Management system.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Referral">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Referral Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The site's referral code.  Referral codes are not required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Servicer1">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Servicer #1</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The default primary servicer.  New jobs will be automatically assigned to this servicer. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Servicer2">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Servicer #2</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The secondary servicer for new jobs.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_SLA">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: SLA</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the site qualifies for SLA service.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_State">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: State</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The address state code for the site.  This field is used in dispatching.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_StoreNo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Store Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The store number for the site.  The store number is directly tied to the Chains feature.
 +
   
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_StoreType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Store Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The store type for the site.  The store number is directly tied to the Chains feature.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Type">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Site types are used to organize sites. Site types are not required.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="site_Zip">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Site: Zip Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The address postal code for the site.  This field is used in dispatching.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sitetype_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Sites can be grouped by site type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sitetype_Code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The code used to identify the site type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sitetype_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Description</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The description used to identify the site type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="sitetype_Message">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Message</div>
 
|-
 
|-
| <div id="">&nbsp;</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.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_solution">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Solutions are defined using the Solution Management feature.  The solution defines the work done to complete the work.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="job_solutionnotes">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution Notes</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Solution notes are used to further define the work performed.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="statuscode_code">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: Code</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The code used to identify the status code.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="statuscode_Desc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: Description</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The description used to identify the status code.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="statuscode_KPI">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: KPI</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When marked the status code will be included in KPI counts.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="statuscode_InProcess">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: In Process</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When marked the jobs assigned to this status code will be considered to be in process.  In process status codes do not appear in the status code list for new jobs.
 +
 
 +
&nbsp;
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="statuscode_AllowInvoicing">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: Allow Invoicing</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Invoicing is only allowed for jobs where the Allow Invoicing is checked.
 +
 
 +
&nbsp;
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="statuscode_All">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: All</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used for the search option.  When checked all status code records will be displayed during a search.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="Subclass">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Subclass</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The sub-classification is used in sales and cost account assignments.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Tasks can be organized by type.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskStatus">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Status</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Tasks can be tracked by status.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskDetails">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Details</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Task details provide a description of the task.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskURL">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: URL</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The URL field is used to store the website related to the task.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskNotes">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Notes</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Notes can be stored for each task.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskDueDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Task can be tracked by due date.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskDueTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Tasks can be tracked by due time.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskAssignmentType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assignment Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Tasks can be assigned to individuals by type.
 +
        Account Manager
 +
        Salesperson
 +
        Servicer
 +
        User
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskAssignedTo">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assigned To</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The individual that will handle the task.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskEmail">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Email</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    An email can be stored with the task.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaskTextPhone">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Text Phone</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    A telephone number for texting can be stored with the task.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TaxClass">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| <div class="fieldHeader">Tax Class</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The item's task class.
 +
 
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div id="customertaxexemptno">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Exempt Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    If the customer is tax exempt, a value must be used in this field. 
 +
 
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div id="customertaxschedule">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Schedule</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The customer's tax schedule.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 +
 
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Terms</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionBilledStatus">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Billed Status</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Indicates the transaction's position in the billing process.
 +
        N = Not billed
 +
        I = On an unposted invoice
 +
        Y = On a posted invoice
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionCovered">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Covered Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the transaction is covered by either a warranty or an agreement.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionDesc">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Description</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The description of the transaction that will appear on the billing documents.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The date the transaction will post to the general ledger.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionEndDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: End Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used in labor transactions only, the date the labor ended. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionEndTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: End Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used in labor transactions only, the time the labor ended. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionExtPrice">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Extended Price</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The price or rate multiplied by the number of units.   
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionUnits">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Number of Units</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number of units to charge on the transaction. 
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionPrice">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Price</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used in non-labor transaction only, the price of the item.   
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionRate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Rate</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used in labor transaction only, the hourly rate.   
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionServicer">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Servicer</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    For labor transactions, the servicer that performed the work.  For other transactions, the servicer that is assigned the warehouse from where the parts originated.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionStartTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Start Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Used in labor transaction only, the time the labor started.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionTaxable">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Taxable Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the transaction will be taxed.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionType">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Type</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The type of transaction.  The type is used to group the transactions by labor, materials, or purchases.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="TransactionVendor">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Vendor</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The vendor from whom the item was purchased.
 +
 
 +
&nbsp;
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="UserTimesetting">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">User Time Setting</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Set the time fields in the software to either military time or AM/PM.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="workorder_agreement">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Agreement</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The agreement that covers the work order's transactions.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderAgreementLabor">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Agreement Labor Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the labor posted to the work order is covered by an agreement.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderAgreementParts">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Agreement Parts Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    When checked, the parts posted to the work order is covered by an agreement.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderCompletedDate">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Completed Date</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The date the work order status changed to the complete status.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WOCompleteTime">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Complete Time</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The time the work order status changed to the complete status.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderDescription">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Description</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The description that is used to identify the work order.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="DollarsEst">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Dollars Estimate</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The total estimated dollars required to complete the work on the work order.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderNumber">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Number</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The number used to identify the work order.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderStatus">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Status</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    The status of the work order.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderwarrLabor">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Warranty Labor Checkbox</div>
 
|-
 
|-
| <div id="">&nbsp;</div>
+
|  
 +
    Checking this checkbox indicates that the labor posted to the work order are covered by a warranty.
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="WorkOrderwarrParts">&nbsp;</div>
 
|-
 
|-
| Desc here
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Warranty Parts Checkbox</div>
 
|-
 
|-
| &nbsp;
+
|  
 +
    Checking this checkbox indicates that the parts posted to the work order are covered by a warranty.
 +
 
 +
----
 +
 
 
|-
 
|-
| &nbsp;
+
| <div id="PMSchedule_coverparts">&nbsp;</div>
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Cover Parts Checkbox</div>
 
|-
 
|-
| &nbsp;
+
|  
|-
+
    Checking this checkbox indicates that the parts posted to the PM are covered by a warranty.
| &nbsp;
+
 
 
|-
 
|-
| &nbsp;
+
| <div id="PMSchedule_coverLabor">&nbsp;</div>
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Cover Labor Checkbox</div>
 
|-
 
|-
| &nbsp;
+
|  
|-
+
    Checking this checkbox indicates that the Labor posted to the PM are covered by a warranty.
| &nbsp;
+
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
 
|-
 
|-
| &nbsp;
+
| colspan="1" | &nbsp;[[Glossary#top|Top]]
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
|-
 
| &nbsp;
 
 
|-
 
|-
 
| &nbsp;
 
| &nbsp;
Line 3,526: Line 4,299:
 
| &nbsp;
 
| &nbsp;
 
|}
 
|}
 
&nbsp;
 

Latest revision as of 10:46, 18 February 2025

Glossary
 
Account Manager
   Account managers are responsible for the customer relationship. Account managers are assigned to customers and(or) jobs.
 
Active Status
   Indicates that the record can be used to produce results.
 
Agreement: Anniversary Date
   The date the agreement terms will end.
 
Agreement: Auto Renew%
   Indicates the amount percent of increase for the agreement renewal.
 
Agreement: Balance
   The current balance of the contract.
 
Agreement: Billable Checkbox
   When checked, indicates that the agreement will be included in the billing process.
 
Agreement: Billing Total
   The total contract amount for the agreement.
 
Agreement: Commission Rate
   The commission rate that will be used when billing the agreement.
 
Agreement: Contact
   The person that should be contacted concerning the agreement.
 
Agreement: Contact Months
   The number of months covered by the agreement.
 
Agreement: Cover Labor
   Indicates if the agreement covers labor transactions.
 
Agreement: Cover Parts
   Indicates if the agreement covers parts transactions.

 

 
Agreement: Current Contract Amount
   The amount of the contract at the time of creation.
 
Agreement: Deferred Revenue Balance
   The current balance of deferred revenues for the contract.
 
Agreement: Deferred Revenues Total
   The total deferred revenues posted to date.
 
Agreement: Established Date
   The date the agreement was first established
 
Agreement: Free Months
   The number of months the customer is being provide for free.
 
Agreement: Frequency
   The billing frequency. i.e., Annually, Monthly
 
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 remainder 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 to identify agreements. On the Job forms it indicates the agreement that may be used to cover transactions. On the PM Schedule form it indicates the agreement that is attached to the schedule.
 
Agreement: Original Contract Amount
   The total price for the contract when started.
 
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 remainder of the amount budgeted for parts to date after invoicing.
 
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 sites and equipment on the agreement.  
       By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price. 
 
Agreement: Priority
   The priority code that would be used for jobs created for agreement coverage.
 
Agreement: Purchase Order
   The purchase order provided by the customer for the agreement.
 
Agreement: Renewable
   Indicates that the agreement is eligible for renewal. Eligible agreements will be included in the renewal process.
 
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 agreement's 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: SLA
   Indicates that the jobs created for this agreement are covered by SLA priority.
 
Agreement: Start Date
   The date the agreement terms will begin.
 
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 settings for agreements by default. 
 
Agreement Type: Code
   The agreement type code code is 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 in the Next Number field based on the Agreement Type.
 
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. i.e., Annually, Monthly
 
Agreement Type Planned Invoice Options: Tax Class
   The tax class that should be assigned to the invoice when the agreement is billed.
 
Agreement Type Planned Invoice Options: Allocation
   The allocation that will be assigned when processing agreements. Allocations are used to establish the general ledger posting accounts and amounts.
 
Agreement Type Planned Invoice Options: Deferred Revenues
   When checked, new agreements will use the deferred revenue feature during the billing process.
 
Agreement Type Planned Invoice Options: Pricing Method
   The pricing method used when processing agreement transactions. 
       Blanket: One price covers all sites and equipment on the agreement.  
       By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. 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 sites and equipment on the agreement.  
       By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price. 
 
Allocation: Price
   The allocation price.  
       Blanket: One price covers all sites and equipment on the agreement.  Enter the price that will cover the entire contract.
       By Site: The contract amount is a total of all site prices on the agreement. Enter the default price for a site. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Enter the default price for an equipment item. 
 
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.
 
Back Office Transaction Entry: Work Order
   The transaction will be assigned to the selected work order. 
 
Back Office Transaction Entry: Stock Radio Button
   Toggles the Inventory search to include only material items.
 
Back Office Transaction Entry: Non-stock Radio Button
   Toggles the Inventory search to include only non-inventory material items.
 
Back Office Transaction Entry: Find by Item Code
   Used to search for an item by the item's code.
 
Back Office Transaction Entry: Find by Item Description
   Used to search for an item by item's description.
 
Back Office Transaction Entry: Servicer
   The servicer that will be assigned to the transaction. This field controls the warehouse list.
 
Back Office Transaction Entry: Agreement
   The agreement assigned to the selected work order.
 
Back Office Transaction Entry: Warehouse
   The warehouse from where the item will be allocated.
 
Back Office Transaction Entry: Cost Type
   Used to assign general ledger account allocations.
 
Back Office Transaction Entry: Equipment
   The equipment assigned to the selected work order.
 
Back Office Transaction Entry: Covered
   Indicates whether or not the transaction should be covered by either warranty or agreement. The software will determine the coverage based on the availably of coverage based on warranty and agreement settings.  If coverage exists, the price will change to 0.
 
Back Office Transaction Entry: Item Code
   The item code that will be used to identify the item. 
 
Back Office Transaction Entry: Trans Description
   The transaction description that will appear on the invoice. This can be different from the item description.
 
Back Office Transaction Entry: Vendor List
   Used to attach a vendor to the transaction.  Purchase transactions only.
 
Back Office Transaction Entry: Start Date
   The date the labor transaction started.  Labor transactions only.
 
Back Office Transaction Entry: Trans Date
   The transaction date.  Inventory and Purchase transactions only.
 
Back Office Transaction Entry: Start Time
   The time the labor transaction started.  Labor transactions only.
 
Back Office Transaction Entry: End Date
   The date the labor transaction ended.  Labor transactions only. This field is only available for use when multiple day transactions is on.
 
Back Office Transaction Entry: End Time
   The time the labor transaction ended.  Labor transactions only. 
 
Back Office Transaction Entry: No Units
   The number of units sold.
 
Back Office Transaction Entry: Taxable
   Checked when the transaction is taxable.
 
Back Office Transaction Entry: Price
   The price of the item.
 
Back Office Transaction Entry: Hidden Line
   When checked the item will not display on the invoice. It will be in the invoice total.
 
Back Office Transaction Entry: UOM
   The selected item's unit of measure. 
 
Back Office Transaction Entry: Ext Price
   The unit price multiplied by the number of units.
 
Back Office Transaction Entry: Billed Status
   Indicates the transaction's position in the billing process.
       N = Not billed
       I = On an unposted invoice
       Y = On a posted invoice
 
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.
 
Call Boards: Form Name
   The board name is used to identify the board.
 
Call Boards: Board Type
   There are three types of boards.  1) Call Central 2) Dispatch 3) Call Center
 
Call Boards: Private
   Private boards will only appear in the list of the user that created the board. 
 
Call Boards: Default
   The default form will be the top form in the boards form list.
 
Call Boards: Past Due Position
   If a position is selected from this list, any jobs that are past due will color the cell according to the color settings in the selected position. 
 
Call Boards: Due Within Position
   If a position is selected from this list, any jobs that match the Due Within setting will color the cell according to the settings in the selected position. 
 
Call Boards: Priority Code Position
   If a position is selected from this list and the color settings for priority codes are setup, the board will use the color settings in the selected position.
 
Call Boards: Job Type Position
   If a position is selected from this list and the color settings for Job Types are setup, the board will use the color settings in the selected position.
 
Call Boards: Status Code Position
   If a position is selected from this list and the color settings for Status Codes are setup, the board will use the color settings in the selected position.
 
Chains
   Sites can be 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 an expiration time for when the work is expected to be started.
 
Chains: Inbound Path
   The inbound path.
 
Chains: Outbound Path
   The outbound path.
 
Chains: Store Type Code
   Stores can be organized by type.
 
Chains: Store Type Name
   The name used to identify the store type.
 
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.
 
Commission Rate
   The amount of commission that is earned when an item is sold. 
 
Contact: Address
   The contacts mailing address.
 
Contact: City
   The city of the contact's mailing address.
 
Contact: Contact by Email Checkbox
   When checked, indicates the customer would permit contact by email.
 
Contact: Contact by Fax Checkbox
   When checked, indicates the customer would permit contact by fax.
 
Contact: Contact by Mail Checkbox
   When checked, indicates the customer would permit contact by mail.
 
Contact: Contact by Phone Checkbox
   When checked, indicates the customer would permit contact by telephone.
 
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: LinkedIn
   The contact's LinkedIn handle.
 
Contact: Name
   The contact's full name.
 
Contact: Opt Out Checkbox
   When checked, indicates that the contact does not want to be contacted for the purpose of marketing.
 
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 contact's mailing address.
 
Contact: Teams
   The contact's Teams handle.
 
Contact: Title
   The contact title. ex: Mr., Mrs.
 
Contact: Twitter
   The contact's Twitter handle.
 
Contact: Type
   Contact Types can be used to organize contacts.
 
Contact: Web
   The contact's website address.
 
Contact: Zip
   The postal code of the contact's mailing address.
 
Cost Type
   Cost types are used to manage general ledger sales and cost account allocations on transactions and billings.
 
Cost Type: Cost Account
   The cost account that will be assigned to transactions that match the job type and cost type. 
 
Cost Type: Cost Subaccount
   The cost sub-account that will be assigned to transactions that match the 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. 
 
Cost Visibility
   Cost visibility is the ability to hide cost from users.  Cost visibility is set at the user level in Account Management. If the checkbox is marked, the user will be able to view cost.
 
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 account handle.
 
Customer: Name
   The name of the organization that will be billed.  Jobs can be created without a customer assignment, 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 customer's address state.
 
Customer: Twitter
   The customer's twitter handle.
 
Customer: Zip Code
   The customer's address zip code.
 
Dispatch: Card Number
   Dispatch cards are numbered from 0 up.
 
Dispatch: Number
   The number used to identify the dispatch card.
 
Dispatch: Priority
   The priority assigned to the dispatch card. 
 
Dispatch: Primary Dispatch Card
   Once a job is created, the primary dispatch card is created. Users can also generate additional dispatch cards.
 
Dispatch: Schedule Date
   The dispatch card's schedule date. 
 
Dispatch: Schedule Time
   The dispatch card's schedule time. 
 
Dispatch: Servicer
   The servicer that is assigned the work.  
 
Dispatch: Status
   The status assigned to the individual dispatch card.
 
Equipment: Code
   Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
 
Equipment: Comments
   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 level does not appear in the Level drop-list, check the selected model’s 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 equipment's 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.
 
Estimated Dollars
   The estimated billing amount required to complete the work. 
 
Estimated Hours
   The hours estimated to complete the work. 
 
FTP Server
   The server address required to log into your ftp server account. 
 
FTP Username
   The server username required to log into your ftp server account. 
 
FTP Password
   The server password that is required to log into your ftp server account. 
 
Hidden Checkbox
   When checked, the item to which the checkbox is assigned will be hidden on invoices. 
 
Inventory: Commissionable
   When checked the item is commissionable.
 
 
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. This description may be limited by ERP systems.  Users can set the size of this field. When changed the software will replace the existing short description with a new short description using the number of characters stored in this field. 
 
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: Notes
   Job notes are unlimited and can be printed on documents.   
 
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. Set up on the site level servicer #1
 
Job: Received Date
   The date the job was entered into the system by a user. 
 
Job: Received Time
   The time 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: Service Type
   Service types are used to organize and recognize jobs.  Service types 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 must start the work to meet the SLA criteria.
 
Job: SLA Expiration Time
   The time the technician must start the work 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 physical 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.
 
Messages: Target Type
   Defines the type of target audience for the message.
 
Messages: Default Target Type
   Defines the type of target audience for the message as the default value for new messages.
 
Messages: Target
   Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups. 
 
Messages: Start Date
   The first date active messages are displayed. 
 
Messages: End Date
   The last date active messages will be displayed.  Note: All messages are removed after 72 hours. 
 
Messages: Message Text
   The content of the message. 
 
Messages: Field Complete
   When checked an automatic message will generate when jobs are changed to the Field Complete status. 
 
Messages: Auto Show Messages
   When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 
Mobile Transaction Entry: Servicer
   The servicer that should be used when posting the transaction.
 
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 with identification.
 
Planned Maintenance: Material Group Code
   Material 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 scheduled 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 scheduled 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.
 
Quoted Dollars
   The billing amount quoted for the job.   
 
Quoted Hours
   The hours quoted for the job.     
 
Purchase Order Number
   The purchase order number issued by the customer for the work.  
 
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 can be 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 can be used to contact the representative.
 
Representative: State
   The mailing address state.
 
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 that match the job type and cost type. 
 
Revenue subaccount
   The sales sub-account that will be assigned to transactions that match the job type and cost type.
 
Role Management
   User roles provide access to assigned forms while restricting access to unassigned forms. 
 
Schedule Date
   The date the technician is scheduled to do the work.
 
Schedule Time
   The time the technician is scheduled to do the work.
 
Scheduling: Reason Code
   Describe the reason the servicer is not available for work.
 
Scheduling: Start Date
   The first date for the time off schedule.
 
Scheduling: End Date
   The last date for the time off schedule.
 
Scheduling: Start Time
   The starting time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the start of the day for all dates except the first date. 
 
Scheduling: End Time
   The End time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the end of the day for all dates except the last date. 
 
Scheduling: Replicate Time
   The replicate time option is used for date spans.  When checked the time on each day will match the start and end times in the fields.  If not, the first day will use the start time, the last day will use the end time and all days in between will display 24 hours of time.
 
Send to Mobile Checkbox
   On save, if this checkbox is checked, the job will be made available in mobile.    
 
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
   This field is used when the servicer is a vendor. The vendor is selected from the list and other vendor fields become available for use.
 
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 assigned to a user login before the user can use the mobile system.  
 
Servicer: Phone
   The telephone number for contacting the servicer.
 
Servicer: Servicer Image File
   The name of the file that contains 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. Leading characters are 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. This can be changed, and the software will adjust the values of the field.
 
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 workflow 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. 
    Prefix: The prefix option will create the number using the equipment prefix followed by the next number.
    Matrix: The matrix option allows the user to establish a prefix order from the prefixes assigned to the equipment types, manufacturers and models.
 
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’s name and address automatically fill in the site form when adding a new site.
 
Software Defaults, Transaction Assignments
   The defaults and settings for new transactions.
 
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 automatically 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 transactions.
 
Software Defaults, Invoicing: Require Sales Tax Checkbox
   When checked, sales tax will be required on all invoices.
 
Software Defaults, Invoicing: Non-Tax Schedule
   Certain 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.  Leading characters are 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 maintenance 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: Agreement 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, Agreements: Agreement 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
   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 managed using the Contact Management 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
   When checked, 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.
 
Status Codes: Code
   The code used to identify the status code.
 
Status Codes: Description
   The description used to identify the status code.
 
Status Codes: KPI
   When marked the status code will be included in KPI counts.
 
Status Codes: In Process
   When marked the jobs assigned to this status code will be considered to be in process.  In process status codes do not appear in the status code list for new jobs.

 

 
Status Codes: Allow Invoicing
   Invoicing is only allowed for jobs where the Allow Invoicing is checked.

 

 
Status Codes: All
   Used for the search option.  When checked all status code records will be displayed during a search.
 
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
   Tasks can be tracked by due time.
 
Tasks: Assignment Type
   Tasks can be assigned to individuals 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: Covered Checkbox
   When checked, the transaction is covered by either a warranty or an agreement. 
 
Transaction: Description
   The description of the transaction that will appear on the billing documents. 
 
Transaction: Date
   The date the transaction will post to the general ledger. 
 
Transaction: End Date
   Used in labor transactions only, the date the labor ended.  
 
Transaction: End Time
   Used in labor transactions only, the time the labor ended.  
 
Transaction: Extended Price
   The price or rate multiplied by the number of units.     
 
Transaction: Number of Units
   The number of units to charge on the transaction.  
 
Transaction: Price
   Used in non-labor transaction only, the price of the item.    
 
Transaction: Rate
   Used in labor transaction only, the hourly rate.     
 
Transaction: Servicer
   For labor transactions, the servicer that performed the work.  For other transactions, the servicer that is assigned the warehouse from where the parts originated.
 
Transaction: Start Time
   Used in labor transaction only, the time the labor started.
 
Transaction: Taxable Checkbox
   When checked, the transaction will be taxed. 
 
Transaction: Type
   The type of transaction.  The type is used to group the transactions by labor, materials, or purchases.
 
Transaction: Vendor
   The vendor from whom the item was purchased.

 

 
User Time Setting
   Set the time fields in the software to either military time or AM/PM.
 
Work Order: Agreement
   The agreement that covers the work order's transactions.
 
Work Order: Agreement Labor Checkbox
   When checked, the labor posted to the work order is covered by an agreement.
 
Work Order: Agreement Parts Checkbox
   When checked, the parts posted to the work order is covered by an agreement.
 
Work Order: Completed Date
   The date the work order status changed to the complete status.
 
Work Order: Complete Time
   The time the work order status changed to the complete status.
 
Work Order: Description
   The description that is used to identify the work order.
 
Work Order: Dollars Estimate
   The total estimated dollars required to complete the work on the work order.
 
Work Order: Number
   The number used to identify the work order.
 
Work Order: Status
   The status of the work order.
 
Work Order: Warranty Labor Checkbox
   Checking this checkbox indicates that the labor posted to the work order are covered by a warranty.
 
Work Order: Warranty Parts Checkbox
   Checking this checkbox indicates that the parts posted to the work order are covered by a warranty.

 
Planned Maintenance: Cover Parts Checkbox
   Checking this checkbox indicates that the parts posted to the PM are covered by a warranty.
 
Planned Maintenance: Cover Labor Checkbox
   Checking this checkbox indicates that the Labor posted to the PM are covered by a warranty.
 Top