User Tools

Site Tools


en:handbuch:kapitel_2:2.01.13_basic_-_kontakt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:handbuch:kapitel_2:2.01.13_basic_-_kontakt [2009/11/16 11:34]
192.168.0.76
en:handbuch:kapitel_2:2.01.13_basic_-_kontakt [2019/10/25 14:11] (current)
Line 1: Line 1:
 [[2.01.12_key_-_fahrzeug|{{|previous}}]] [[en:​handbuch:​handbuch|{{|Home}}]] [[2.01.14_basic_-_kampagne|{{|next}}]] [[2.01.12_key_-_fahrzeug|{{|previous}}]] [[en:​handbuch:​handbuch|{{|Home}}]] [[2.01.14_basic_-_kampagne|{{|next}}]]
  
-====== 2.01.13 Customer ======+====== 2.01.12 Customer ======
  
  
-The "​Customer"​ form administers the business contacts. All information about the company of the customer, like the description,​ address and ways of communication are stored and saved here. For a better overview of all the structural business contacts and for better processing, it is possible to save and store information related to the category, the reference, contact type, as well as the corresponding branch. Furthermore,​ the currency and the charge rate can be administered as well. This data is needed for defining[[handbuch:​kapitel_2:​2.02.02_projekt|projects]] in the document type project and is necessary for posting proposals and invoicing into the billing document [[en:​handbuch:​kapitel_2:​2.04_fakturamodul_optional|Billing Module]].+The "​Customer"​ form administers the business contacts. All information about the company of the customer, like the description,​ address and ways of communication are stored and saved here. For a better overview of all the structural business contacts and for better processing, it is possible to save and store information related to the category, the reference, contact type, as well as the corresponding branch. Furthermore,​ the currency and the charge rate can be administered as well. This data is needed for defining [[en:handbuch:​kapitel_2:​2.02.02_projekt|projects]] in the document type project and is necessary for posting proposals and invoicing into the billing document [[en:​handbuch:​kapitel_2:​2.04_fakturamodul_optional|Billing Module]].
  
    
-**Tip:** Further information to this topic can be found in chapter [[en:​handbuch:​kapitel_3:​3.11.04_-_crm Das Kontaktsystem|3.11.04 The Contact System]]. ​+**Tip:** Further information to this topic can be found in chapter [[en:​handbuch:​kapitel_3:​3.11.04_das_kontaktsystem_-_crm |3.11.04 The Contact System]]. ​ 
 + 
 +{{:​en:​handbuch:​kapitel_2:​customer1.1.png|}}
  
 The form contains the following elements: The form contains the following elements:
  
-{{:en:​handbuch:​kapitel_2:​customer.gif?​direct}}+On the "​Master data" tab:
  
-On the "​Master Data List" tab: +    ​* **Number and Abbreviation:​** The element "​Number"​ specifies the exact contact within the system and the Abbreviation can be used for the number range or be used for the quick search. 
-    ​* **Number and Abbreviation:​** The element "​Number"​ specifies the exact contact within the system and the "Abbreviation" ​can be used for the number range or be used for the quick search. +    * **Company Name and Previous Company Name:** These alphanumeric fields describe the current company names and if needed ​the previous company names.
-    * **Company Name and Previous Company Name:** These alphanumeric fields describe the current company names and where applicable ​the previous company names.+
     * **Category:​** In the field "​Category"​ it is possible to define the types of contact (for example: Customer, Interested Party, etc.)and allocate them into "​Collections"​ (see also Administration Guide). ​     * **Category:​** In the field "​Category"​ it is possible to define the types of contact (for example: Customer, Interested Party, etc.)and allocate them into "​Collections"​ (see also Administration Guide). ​
     * **Type:** In the field "​Type"​ it is possible that defined contact types (for example: Company, Network, Association,​ etc.) can be allocated into the "​Collections"​ (see Administration Guide).  ​     * **Type:** In the field "​Type"​ it is possible that defined contact types (for example: Company, Network, Association,​ etc.) can be allocated into the "​Collections"​ (see Administration Guide).  ​
     * **Parent Customer:** The field "​Parent Customer"​ characterises the existence of a superior contact (for example a "​Holding"​) and creates the company'​s structure in Projectile. If this element is not filled, then the contact is itself a superior contact. When applying a subordinate contact then this field will be automatically filled.  ​     * **Parent Customer:** The field "​Parent Customer"​ characterises the existence of a superior contact (for example a "​Holding"​) and creates the company'​s structure in Projectile. If this element is not filled, then the contact is itself a superior contact. When applying a subordinate contact then this field will be automatically filled.  ​
     * **Sub Customer:** This element contains a register of all allocated subordinate contacts. After the definition of "​Subsidiaries",​ they will then be automatically transferred into the subordinate contact.  ​     * **Sub Customer:** This element contains a register of all allocated subordinate contacts. After the definition of "​Subsidiaries",​ they will then be automatically transferred into the subordinate contact.  ​
-    * **Contact ​Person:** This field specifies the contact person from the customer (see also "Contact ​Person"​ form).+    * **Contact:​** This field specifies the contact person from the customer (see also [[en:​handbuch:​kapitel_2:​2.01.21_basic_-_ansprechpartner|Contact]]).
     ​     ​
-{{:​en:​handbuch:​kapitel_2:​customer2.gif?direct}}+{{:​en:​handbuch:​kapitel_2:​customer2.1.png|}}
  
-On the "Information" tab (implementation example):+On the "Marketing" tab (implementation example):
  
     * **Branch and Establishment:​** Here is where the branches of the contact and the date of the establishment can be stored and saved. The branch can be defined in "​Collections"​ (see also Administration Guide) ​     * **Branch and Establishment:​** Here is where the branches of the contact and the date of the establishment can be stored and saved. The branch can be defined in "​Collections"​ (see also Administration Guide) ​
Line 32: Line 33:
     * **Partner (and possible Commission):​** Here is where the sales partner, with the respective commission, can be entered. ​     * **Partner (and possible Commission):​** Here is where the sales partner, with the respective commission, can be entered. ​
     * **Arranger and Representative:​** Here is where the customer service agent can be entered. This/these employee(s) are responsible for the contact.     * **Arranger and Representative:​** Here is where the customer service agent can be entered. This/these employee(s) are responsible for the contact.
-    ​ 
- 
-{{:​en:​handbuch:​kapitel_2:​customer3.gif?​direct}} 
  
 +{{:​en:​handbuch:​kapitel_2:​customer3.1.png|}}
  
 On the tab "​Sales"​ (implementation example): On the tab "​Sales"​ (implementation example):
Line 43: Line 42:
     * **Order Value and Invoice Value:** Here is where the system lists the sum of all order confirmations as the "Order Value" and the sum of all complete bills from all of the projects of the customer as "​Invoice Value"​.  ​     * **Order Value and Invoice Value:** Here is where the system lists the sum of all order confirmations as the "Order Value" and the sum of all complete bills from all of the projects of the customer as "​Invoice Value"​.  ​
     * **Projected and estimated Order Value:** The projected order value will be directly out of the form "Sales Outlet"​ defined, the estimated order value will be, in respect to the possible order probability,​ defined.     * **Projected and estimated Order Value:** The projected order value will be directly out of the form "Sales Outlet"​ defined, the estimated order value will be, in respect to the possible order probability,​ defined.
-    ​ 
  
- +{{:​en:​handbuch:​kapitel_2:​customer4.2.png|}}
-{{:​en:​handbuch:​kapitel_2:​customer4.gif?direct}}+
  
 On the tab "​Address":​ On the tab "​Address":​
Line 55: Line 52:
     * **Further Addresses:​** Further customer addresses can be entered here. If the billing address/​delivery address differs from the company address, it can be specified here. These addresses will be managed here.      * **Further Addresses:​** Further customer addresses can be entered here. If the billing address/​delivery address differs from the company address, it can be specified here. These addresses will be managed here. 
  
-{{:​en:​handbuch:​kapitel_2:​customer5.gif?direct}}+{{:​en:​handbuch:​kapitel_2:​customer5.png|}}
  
 On the "​Communication"​ tab: On the "​Communication"​ tab:
Line 63: Line 60:
     * **Email Address, Web:** These fields define the email addresses and the customer'​s URL (internet address). Clicking on the email address opens the user's standard email program with the registered email address. Clicking on the web field opens the standard browser with the respective URL.     * **Email Address, Web:** These fields define the email addresses and the customer'​s URL (internet address). Clicking on the email address opens the user's standard email program with the registered email address. Clicking on the web field opens the standard browser with the respective URL.
  
- +{{:​en:​handbuch:​kapitel_2:​customer6.png|}}
-{{:​en:​handbuch:​kapitel_2:​customer6.gif?direct}} +
  
 On the "​Financial data" tab: On the "​Financial data" tab:
  
-    * **Debtor number/​Creditor number:** The finance accounting interface (Fibu-Schnittstelle)of the debtor number(customer) and/or creditor number(supplier)can be stored here.+    * **Debtor number/​Creditor number:** The finance accounting interface (Fibu-Schnittstelle) of the debtor number(customer) and/or creditor number(supplier)can be stored here.
     * **Term of Payment, Payment Arrangements:​** This field defines the term of payment and the payment arrangements of the customer.     * **Term of Payment, Payment Arrangements:​** This field defines the term of payment and the payment arrangements of the customer.
     * **Currency:​** This field defines the general currency of the customer. This currency is the standard for all projects for this customer. But, this can be overriden for the project'​s currency. The currency can be defined and modified in the currency mask.     * **Currency:​** This field defines the general currency of the customer. This currency is the standard for all projects for this customer. But, this can be overriden for the project'​s currency. The currency can be defined and modified in the currency mask.
Line 80: Line 75:
     * **Own Supplier number:** Your own supplier number can be defined here. This number can be used when creating the invoice numbers. ​     * **Own Supplier number:** Your own supplier number can be defined here. This number can be used when creating the invoice numbers. ​
  
 +{{:​en:​handbuch:​kapitel_2:​customer7.png|}}
 +
 +On the "​DependentDocuments"​ tab:
  
 +    * **Projects:​**
 +    * **Offers:**
 +    * **Invoices:​**
 +    * **Contracts:​**
 +    * **Travels:​**
 +    * **Tickets:​**
 +    * **Actions:​**
  
-{{:​en:​handbuch:​kapitel_2:​customer7.gif?direct}}+{{:​en:​handbuch:​kapitel_2:​customer8.png|}}
  
 On the "​Misc"​ tab: On the "​Misc"​ tab:
Line 93: Line 98:
     * **Create Staff Records by Customer:** Using this this action, price tables can be defined customer-ralated for the staff (see also Pricing and Staff Records by Customer). ​     * **Create Staff Records by Customer:** Using this this action, price tables can be defined customer-ralated for the staff (see also Pricing and Staff Records by Customer). ​
     * **Create Staff Records by Customer:** With the help of this action all defined staff records will be displayed. ​     * **Create Staff Records by Customer:** With the help of this action all defined staff records will be displayed. ​
-    * **Create Staff Records by Customer:** With the help of this action all price tables for the operations/activiteis ​can be defined client-related (see also Pricing and Customer-based Occupations.)+    * **Create Staff Records by Customer:** With the help of this action all price tables for the operations/activities ​can be defined client-related (see also Pricing and Customer-based Occupations.)
     * **Create Staff Records by Customer:** With the help of this action all defined client-based operations are displayed.     * **Create Staff Records by Customer:** With the help of this action all defined client-based operations are displayed.
en/handbuch/kapitel_2/2.01.13_basic_-_kontakt.1258367648.txt.gz · Last modified: 2019/10/25 14:09 (external edit)