Brontekst bekijken van Sjabloon:Cliënt (Venster ID-109 V1.0.0)

[[en:Client (Window ID-109)]]
[[ar:Client (نافذة ID-109)]]
[[bg:Клиент (прозорец ID-109)]]
[[da:Client (Vindue ID-109)]]
[[de:Mandant (Fenster ID-109)]]
[[el:Εταιρία (παράθυρο ID-109)]]
[[es:Grupo Empresarial (Ventana ID-109)]]
[[fr:Société (Fenêtre ID-109)]]
[[hu:Vállalat (Aablak ID-109)]]
[[id:Client (jendela ID-109)]]
[[it:Azienda (Client) (finestra ID-109)]]
[[ja:クライアント (ウィンドウ ID-109)]]
[[ms:Klien (tetingkap ID-109)]]
[[nl:Cliënt (Venster ID-109)]]
[[pl:Firma (nasza) (Okno ID-109)]]
[[pt:Empresas (Janela ID-109)]]
[[ro:Societate (fereastră ID-109)]]
[[ru:Клиенты (окно ID-109)]]
[[sr:Клијент (прозор ID-109)]]
[[sv:Klient (Fönster ID-109)]]
[[th:บริษัท (หน้าต่าง ID-109)]]
[[tr:Client (pencere ID-109)]]
[[zh:客户 (窗口 ID-109)]]
 


== Venster: Cliënt ==

'''Beschrijving:''' Beheer Cliënten

'''Help:''' De Cliënt is het hoogte niveau van een onafhankelijke zakelijke entiteit. Elke Cliënt heeft een of meerdere Organizaties onder zijn hoede. Elke Cliënt definieert de boekhoudparameters (Boekhoud Schema, Boom definitie, Niet-financiële meeteenheden). Om nieuwe Cliënts te maken voer je de Initiële Client Setup uit met de Systeem Administrator Rol.
Maak geen nieuwe Cliënt aan in dit scherm, maar gebruik de "Initiële Client Setip" om de vereiste veiligheids- en toegangsregels te maken. Als je een nieuwe Cliënt hier aanmaakt zal je deze niet kunnen zien en zal de vereiste Client infrastructuur niet opgezet zijn.

 

    
    
=== TAB: Client ===

'''Beschrijving:''' Client/Tenant Definition 


'''Help''' The Client Definition Tab defines a unique client.
Do not create a new client in this window, but use "Initial Client Setup" (System Administrator Role) to set up the required security and access rules. If you create a new client here, you will not be able to view it and also the required client infrastructure would not have been set up.


[[image:Cliënt - Client - Venster (iDempiere 1.0.0).png]]




     


{| border="1" cellpadding="5" cellspacing="0" 
|- 
|-valign="top" 
!style="background:#efefef;" |'''''Naam''''' 
!style="background:#efefef;" |'''''Naam''''' 
!style="background:#efefef;" |'''''Beschrijving''''' 
!style="background:#efefef;" |'''''Help''''' 
!style="background:#efefef;" |'''''Specificaties''''' 
|-valign="top" 
|- 


|-valign="top" 
|Search Key
|Search Key
|Search key for the record in the format required - must be unique 
|A search key allows you a fast method of finding a particular record.
If you leave the search key empty, the system automatically creates a numeric number.  The document sequence used for this fallback number is defined in the "Maintain Sequence" window with the name "DocumentNo_<TableName>", where TableName is the actual name of the table (e.g. C_Order).
|Value<br>character varying(40) NOT NULL<br>String
|-valign="top" 
|-

|-valign="top" 
|Name
|Name
|Alphanumeric identifier of the entity 
|The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length.
|Name<br>character varying(60) NOT NULL<br>String
|-valign="top" 
|-

|-valign="top" 
|Description
|Beschrijving
|Optional short description of the record 
|A description is limited to 255 characters.
|Description<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|Active
|Actief
|The record is active in the system 
|There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records:
(1) The system requires the record for audit purposes.
(2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.
|IsActive<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Use Beta Functions
|Use Beta Functions
|Enable the use of Beta Functionality 
|The exact scope of Beta Functionality is listed in the release note.  It is usually not recommended to enable Beta functionality in production environments.
|IsUseBetaFunctions<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Language
|Taal
|Language for this entity 
|The Language identifies the language to use for display and formatting
|AD_Language<br>character varying(6)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Multi Lingual Documents
|Multi Lingual Documents
|Documents are Multi Lingual 
|If selected, you enable multi lingual documents and need to maintain translations for entities used in documents (examples: Products, Payment Terms, ...).<br>
Please note, that the base language is always English.
|IsMultiLingualDocument<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Auto Archive
|Auto Archive
|Enable and level of automatic Archive of documents 
|Adempiere allows to automatically create archives of Documents (e.g. Invoices) or Reports. You view the archived material with the Archive Viewer
|AutoArchive<br>character(1) NOT NULL<br>List
|-valign="top" 
|-

|-valign="top" 
|Material Policy
|Material Policy
|Material Movement Policy 
|The Material Movement Policy determines how the stock is flowing (FiFo or LiFo) if a specific Product Instance was not selected.  The policy can not contradict the costing method (e.g. FiFo movement policy and LiFo costing method).
|MMPolicy<br>character(1) NOT NULL<br>List
|-valign="top" 
|-

|-valign="top" 
|Mail Host
|Mail Host
|Hostname of Mail Server for SMTP and IMAP 
|The host name of the Mail Server for this client with SMTP services to send mail, and IMAP to process incoming mail.
|SMTPHost<br>character varying(60)<br>String
|-valign="top" 
|-

|-valign="top" 
|SMTP Authentication
|SMTP Authentication
|Your mail server requires Authentication 
|Some email servers require authentication before sending emails.  If yes, users are required to define their email user name and password.  If authentication is required and no user name and password is required, delivery will fail.
|IsSmtpAuthorization<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|SMTP Port
|SMTP Port
|SMTP Port Number 
|null
|SMTPPort<br>numeric(10)<br>Integer
|-valign="top" 
|-

|-valign="top" 
|SMTP SSL/TLS
|SMTP SSL/TLS
|Use SSL/TLS for SMTP 
|null
|IsSecureSMTP<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Request EMail
|Request EMail
|EMail address to send automated mails from or receive mails for automated processing (fully qualified) 
|EMails for requests, alerts and escalation are sent from this email address as well as delivery information if the sales rep does not have an email account. The address must be filly qualified (e.g. joe.smith@company.com) and should be a valid address.
|RequestEMail<br>character varying(60)<br>String
|-valign="top" 
|-

|-valign="top" 
|Request Folder
|Request Folder
|EMail folder to process incoming emails; if empty INBOX is used 
|Email folder used to read emails to process as requests, If left empty the default mailbox (INBOX) will be used. Requires IMAP services.
|RequestFolder<br>character varying(20)<br>String
|-valign="top" 
|-

|-valign="top" 
|Request User
|Request User
|User Name (ID) of the email owner 
|EMail user name for requests, alerts and escalation are sent from this email address as well as delivery information if the sales rep does not have an email account. Required, if your mail server requires authentification as well as for processing incoming mails.
|RequestUser<br>character varying(60)<br>String
|-valign="top" 
|-

|-valign="top" 
|Request User Password
|Request User Password
|Password of the user name (ID) for mail processing 
|null
|RequestUserPW<br>character varying(20)<br>String
|-valign="top" 
|-

|-valign="top" 
|Server EMail
|Server EMail
|Send EMail from Server 
|When selected, mail is sent from the server rather then the client.  This decreases availability.  You would select this when you do not want to enable email relay for the client addresses in your mail server.
|IsServerEMail<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Test EMail
|Test EMail
|Test EMail Connection 
|Test EMail Connection based on info defined. An EMail is sent from the request user to the request user.  Also, the web store mail settings are tested.
|EMailTest<br>character(1)<br>Button
|-valign="top" 
|-

|-valign="top" 
|Model Validation Classes
|Model Validation Classes
|List of data model validation classes separated by ; 
|List of classes implementing the interface org.compiere.model.ModelValidator, separated by semicolon.
The class is called for the client and allows to validate documents in the prepare stage and monitor model changes.
|ModelValidationClasses<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|Store Attachments On File System
|Store Attachments On File System
|null 
|null
|StoreAttachmentsOnFileSystem<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Windows Attachment Path
|Windows Attachment Path
|null 
|null
|WindowsAttachmentPath<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|Unix Attachment Path
|Unix Attachment Path
|null 
|null
|UnixAttachmentPath<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|Store Archive On File System
|Store Archive On File System
|null 
|null
|StoreArchiveOnFileSystem<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Windows Archive Path
|Windows Archive Path
|null 
|null
|WindowsArchivePath<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|Unix Archive Path
|Unix Archive Path
|null 
|null
|UnixArchivePath<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|IsUseASP
|IsUseASP
|null 
|null
|IsUseASP<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Replication Strategy
|Replication Strategy
|Data Replication Strategy 
|The Data Replication Strategy determines what and how tables are replicated 
|AD_ReplicationStrategy_ID<br>numeric(10)<br>Table Direct
|-valign="top" 
|-
|}
  



    
    
=== TAB: Client Info ===

'''Beschrijving:''' Client Info 


'''Help''' The Client Info Tab defines the details for each client.  The accounting rules and high level defaults are defined here. The Calendar is used to determine if a period is open or closed.


[[image:Cliënt - Client Info - Venster (iDempiere 1.0.0).png]]




     


{| border="1" cellpadding="5" cellspacing="0" 
|- 
|-valign="top" 
!style="background:#efefef;" |'''''Naam''''' 
!style="background:#efefef;" |'''''Naam''''' 
!style="background:#efefef;" |'''''Beschrijving''''' 
!style="background:#efefef;" |'''''Help''''' 
!style="background:#efefef;" |'''''Specificaties''''' 
|-valign="top" 
|- 


|-valign="top" 
|Organization
|Organization
|Organizational entity within client 
|An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
|AD_Org_ID<br>numeric(10) NOT NULL<br>Table Direct
|-valign="top" 
|-

|-valign="top" 
|Active
|Actief
|The record is active in the system 
|There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records:
(1) The system requires the record for audit purposes.
(2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.
|IsActive<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Client
|Client
|Client/Tenant for this installation. 
|A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client.
|AD_Client_ID<br>numeric(10) NOT NULL<br>Table Direct
|-valign="top" 
|-

|-valign="top" 
|Discount calculated from Line Amounts
|Discount calculated from Line Amounts
|Payment Discount calculation does not include Taxes and Charges 
|If the payment discount is calculated from line amounts only, the tax and charge amounts are not included. This is e.g. business practice in the US.  If not selected the total invoice amount is used to calculate the payment discount.
|IsDiscountLineAmt<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Calendar
|Agenda
|Accounting Calendar Name 
|The Calendar uniquely identifies an accounting calendar.  Multiple calendars can be used.  For example you may need a standard calendar that runs from Jan 1 to Dec 31 and a fiscal calendar that runs from July 1 to June 30.
|C_Calendar_ID<br>numeric(10)<br>Table Direct
|-valign="top" 
|-

|-valign="top" 
|Primary Accounting Schema
|Primary Accounting Schema
|Primary rules for accounting 
|An Accounting  Schema defines the rules used accounting such as costing method, currency and calendar.
|C_AcctSchema1_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|UOM for Volume
|Volume Eenheid
|Standard Unit of Measure for Volume 
|The Standard UOM for Volume indicates the UOM to use for products referenced by volume in a document.
|C_UOM_Volume_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|UOM for Weight
|Gewicht Eenheid
|Standard Unit of Measure for Weight 
|The Standard UOM for Weight indicates the UOM to use for products referenced by weight in a document.
|C_UOM_Weight_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|UOM for Length
|Lengte Eenheid
|Standard Unit of Measure for Length 
|The Standard UOM for Length indicates the UOM to use for products referenced by length in a document.
|C_UOM_Length_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|UOM for Time
|Tijd Eenheid
|Standard Unit of Measure for Time 
|The Standard UOM for Time indicates the UOM to use for products referenced by time in a document.
|C_UOM_Time_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Template B.Partner
|Template B.Partner
|Business Partner used for creating new Business Partners on the fly 
|When creating a new Business Partner from the Business Partner Search Field (right-click: Create), the selected business partner is used as a template, e.g. to define price list, payment terms, etc.
|C_BPartnerCashTrx_ID<br>numeric(10)<br>Search
|-valign="top" 
|-

|-valign="top" 
|Product for Freight
|Product for Freight
|null 
|null
|M_ProductFreight_ID<br>numeric(10)<br>Search
|-valign="top" 
|-

|-valign="top" 
|Days to keep Log
|Days to keep Log
|Number of days to keep the log entries 
|Older Log entries may be deleted
|KeepLogDays<br>numeric(10)<br>Integer
|-valign="top" 
|-

|-valign="top" 
|Organization Tree
|Organization Tree
|Trees are used for (financial) reporting and security access (via role) 
|Trees are used for (finanial) reporting and security access (via role)
|AD_Tree_Org_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Menu Tree
|Menu Tree
|Tree of the menu 
|Menu access tree
|AD_Tree_Menu_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|BPartner Tree
|BPartner Tree
|Trees are used for (financial) reporting 
|Trees are used for (finanial) reporting
|AD_Tree_BPartner_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Product Tree
|Product Tree
|Trees are used for (financial) reporting 
|Trees are used for (finanial) reporting
|AD_Tree_Product_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Project Tree
|Project Tree
|Trees are used for (financial) reporting 
|Trees are used for (finanial) reporting
|AD_Tree_Project_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Sales Region Tree
|Sales Region Tree
|Trees are used for (financial) reporting 
|Trees are used for (finanial) reporting
|AD_Tree_SalesRegion_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Campaign Tree
|Campaign Tree
|Trees are used for (financial) reporting 
|Trees are used for (finanial) reporting
|AD_Tree_Campaign_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Activity Tree
|Activity Tree
|Trees are used for (financial) reporting 
|Trees are used for (finanial) reporting
|AD_Tree_Activity_ID<br>numeric(10)<br>Table
|-valign="top" 
|-

|-valign="top" 
|Logo
|Logo
|null 
|null
|Logo_ID<br>numeric(10)<br>Image
|-valign="top" 
|-

|-valign="top" 
|Logo Report
|Logo Report
|null 
|null
|LogoReport_ID<br>numeric(10)<br>Image
|-valign="top" 
|-

|-valign="top" 
|Logo Web
|Logo Web
|null 
|null
|LogoWeb_ID<br>numeric(10)<br>Image
|-valign="top" 
|-
|}
  



    
    
=== TAB: Client Share ===

'''Beschrijving:''' Force (not) sharing of client/org entities 


'''Help''' Business Partner can be either defined on Client level (shared) or on Org level (not shared).  You can define here of Products are always shared (i.e. always created under Organization "*") or if they are not shared (i.e. you cannot enter them with Organization "*").<br>
The creation of  "Client and Org" shared records is the default and is ignored.


[[image:Cliënt - Client Share - Venster (iDempiere 1.0.0).png]]




     


{| border="1" cellpadding="5" cellspacing="0" 
|- 
|-valign="top" 
!style="background:#efefef;" |'''''Naam''''' 
!style="background:#efefef;" |'''''Naam''''' 
!style="background:#efefef;" |'''''Beschrijving''''' 
!style="background:#efefef;" |'''''Help''''' 
!style="background:#efefef;" |'''''Specificaties''''' 
|-valign="top" 
|- 


|-valign="top" 
|Client
|Client
|Client/Tenant for this installation. 
|A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client.
|AD_Client_ID<br>numeric(10) NOT NULL<br>Table Direct
|-valign="top" 
|-

|-valign="top" 
|Organization
|Organization
|Organizational entity within client 
|An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
|AD_Org_ID<br>numeric(10) NOT NULL<br>Table Direct
|-valign="top" 
|-

|-valign="top" 
|Name
|Name
|Alphanumeric identifier of the entity 
|The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length.
|Name<br>character varying(60) NOT NULL<br>String
|-valign="top" 
|-

|-valign="top" 
|Description
|Beschrijving
|Optional short description of the record 
|A description is limited to 255 characters.
|Description<br>character varying(255)<br>String
|-valign="top" 
|-

|-valign="top" 
|Active
|Actief
|The record is active in the system 
|There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records:
(1) The system requires the record for audit purposes.
(2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.
|IsActive<br>character(1) NOT NULL<br>Yes-No
|-valign="top" 
|-

|-valign="top" 
|Table
|Tabel
|Database Table information 
|The Database Table provides the information of the table definition
|AD_Table_ID<br>numeric(10) NOT NULL<br>Table Direct
|-valign="top" 
|-

|-valign="top" 
|Share Type
|Share Type
|Type of sharing 
|Defines if a table is shared within a client or not.
|ShareType<br>character(1) NOT NULL<br>List
|-valign="top" 
|-
|}