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