HEX
Server: Microsoft-IIS/8.5
System: Windows NT YDAWBH120 6.3 build 9600 (Windows Server 2012 R2 Standard Edition) AMD64
User: tentjecom_web (0)
PHP: 7.4.14
Disabled: NONE
Upload Files
File: D:/HostingSpaces/LHouwen/dokuwiki.logic.nl/wwwroot/data/pages/crm/accounts.txt
====== Accounts ======

===== Addresses =====

By default an Account has 2 addresses:
1. Visit Address
2. Mailing Address

for Accounts where Visit Address is equal to their Mailing Address, you can use the "Copy 2 Mailing Address" button to copy the Visit Address to the Mailing Address.

Larger corporations usually have extra addresses for Shipping and/or Invoicing. We normally find out about their existence when we receive a purchase order. we can keep track of these extra addresses by using the //Addresses// entity. This is accessible from the Ribbon at the top of the screen by clicking the right arrow (>) behind the name of the Account.
A new Menu opens where you can select //Addresses//.

Give the address an easy identifiable Name like "Shipping" or "Invoicing".

These addresses are accessible in Quotes, Orders and Invoices. 

===== Business Unit =====

The name within the organizational structure or the division name for this Account within the corporate hierarchy. 
Most likely, this Account will have a Parent Account.

Set to "HQ" if this is the Corporate Head Quarter (in which case there is no parent account).


===== Credit Limit =====

For //Accounts// where we know that there is a risk for not getting our invoice paid, the accounting department can enter a credit limit in this attribute. In case we receive a Purchase Order with a higher value than the credit limit, approval from management is required to accept the order.


===== Credit Hold =====

When we expect that an //Account// cannot fulfill his payment obligations, or in case there is/were disputes with the //Account//, our accounting department or management can set this attribute to " Yes"  indicating that we cannot accept any Purchase orders unless they are prepaid.

===== CRM4 Link =====
If the //Account// was imported from Microsoft CRM Version 4, you can copy the URL to the original CRM4 record:

  - In the //Account// go to the Tab //CRM4// (located at the bottom of the form).
  - If the //Account// was imported from //CRM4//, then the field //IK// contains a value.
  - When you press the button //ClipBoard//, the URL is copied to the Clipboard.
  - Open CRM4 in the Parallels Client and past the URL in the Internet Explorer's URL bar.
  - Press Enter.
===== Industry =====

Major Vertical Market where this //Account// is operating in. A Mandatory field used for coordinating marketing campaigns.

**Note:** Only use items that start with "_" (underscore).
===== Relationship Type =====
This attribute is used to identify the nature of Account in its relationship with Logic.
It is used for targeted marketing activities. 
Possible values:
//Competitor// : Any Account that sells or markets competing products as a manufacturer, distributor, reseller or sales channel.

//Consultancy// : provides services to OEM's and ODM's (system houses, consultants)

//Customer// : Account that has ordered from Logic now or in the past. This values is set automatically when an Order for this Account is created and the current value is //Prospect//.

//Partner// : Does not purchase from Logic but helps in sales and/or marketing activities. or we combine products/efforts for sales.

//Influencer// : Does not purchase from Logic but is involved in the sales process

//Press// : Marketing contact

//Prospect// : Any new Account in CRM that has not ordered from Logic (yet)

//Reseller// : Purchases products from Logic and sells them to end-customers

//Supplier// : Partner from Logic whose products we distribute.

//Other// : Suppliers or Service providers to Logic, like: cleaning, airco repair center, insurance company, Viking office suppliers etc. 

If you are missing important //Relationship Types// contact your CRM admin to add a new Type.

====== Location Form ======
The //Location Form// can be selected from the //Account Form// dropdown above the //Account name//.

It basically opens a //Bing Map// page with location information specific to the selected //Account//.

The //Map// can be used to view all currently known //Accounts// in CRM within a certain //Radius// and in **the same //Country//**.

By default, the //Radius// is set to 50km. This can be changed in incremental steps to 400km.

Initially the //Map// is empty when you open the Form. Press the //Update Map// button to display the //Accounts// with pushpins.

After loading the //Accounts//, the //Status// field displays the number of records which were loaded, or it shows an error message if something went wrong. A list with the //Account name// and //City// is shown at the right hand side of the map. Use the //Open// link to open the //Account// in CRM.

By default the //Account List// is sorted by //Account Name//. Use the //Sort By// drop down list to select //City//.

The //Clear Map// button can be used to remove all pushpins from the //Map//. Now you can perform a new Search.

By clicking a pushpin, an infobox opens with the Name and City of the //Account//. Click //Open// in the infobox to open an new explorer window for the //Account//.

**Note:**
Only //Accounts// with **valid geocodes** (= actual visit address) and a //Relationship Type// not set to //Other// are listed.

===== Pushpin Colors =====

  * //Blue//: the location of the current //Account//, centered in the //Map//.
  * //Green//: //Account// with //Relationship Type// "Customer", implying that they purchased from Logic in 2019 or later.
  * //Red//: //Account// in urgent need of a Logic Solution :-)
 
===== Notes for Maps =====
  - For accurately displaying information on a map, the //Visit// address needs to be filled in correctly, by means of these //Attributes//:
  * //Address1: Street 1//
  * //Address1: Zip/PostalCode//
  * //Address1: City//
  * //Country1 Name//
   - Only use street names, not PO-boxes because these are not resolved to useful coordinates.
   - If you get an error message when first loading the map, please check if the //Latitude// and //Longitude// fields are properly filled for this //Account//. If not, modify the //Visit Address// and press //Save//. //Latitude// and //Longitude// should now be filled correctly. Now you can press //Update Map// again.