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