View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

ERP 2.50:Functional Documentation/General Setup/it

Contents

Introduzione

L'obiettivo di questa sezione è quello di illustrare come configurare Openbravo. Per configurare correttamente Openbravo è necessario, ovviamente, che esso sia stato installato con successo. Il modo corretto di usare OB è il seguente:


General Setup.png


Questa sezione tratta il punto General Setup. Questo modulo migliora e incrementa le performance di OB e permette di configurare molte cose.

Client (Entità)

Introduzione

Openbravo è un'applicazione capace di gestire più aziende. Un client (entità) è un'azienda gestita dall'applicazione. I vari client sono gestiti in maniera indipendente gli uni dagli altri. Ogni client comprende una o più organizzazione.

Openbravo lavora con almeno due diverse entità. La prima gestisce il modello dati (dati che riguardano la struttura dei database) ed i dati sorgente (dati necessari alla costruzione degli oggetti di Openbravo: window,...). La seconda gestisce i dati veri e propri di un'azienda (anagrafica business partner,...). Volendo schematizzare otteniamo:

Entity.png

  1. Il nome del primo client è System. Per vedere tutti i dati relativi a questo client bisogna eseguire il login con il ruolo di System Administrator. Usare l'utente di default: Openbravo (user name), openbravo (password). Ogni modello dati ha tabelle, colonne, finestre, schede, i campi, menu, ecc quindi è indipendente da qualsiasi altro client, ma allo stesso tempo, ogni client utilizzerà le stesse finestre, i campi, etc che sono stati configurati come client system . Allo stesso modo i dati sorgente devono coesistere con i dati sono obbligatori per qualche processo indipendentemente dal resto dei client, ma ogni client ne ha bisogno. Quindi questi sono i dati comuni per tutti i client.
  1. Questo nuovo client deve essere creato utilizzando il processo di Configurazione iniziale del client . Tutti i dati campione / transazionali sono creati sotto questo nuovo client, e solo gli utenti correlati a questo client possono vedere i dati.

Creare un Client

L'unico modo di creare un entità è di utilizzare il processo di Configurazione Iniziale del Client. La ragione è che molti dei processi devono essere fatti per creare la entità correttamente.

Si prega di consultare i passaggi per la creazione di un Creare Nuovo Client.

Quattro compiti principali sono coinvolti nella Configurazione Iniziale del Client:


Client set up.png


Queste quattro attività sono indipendenti per cui se una di esse fallisce, il processo continua a funzionare. Ma il fatto è che se i dati del client o i dati finanziari falliscono OB non funziona correttamente.


1. Dati del client

Questo compito si occupa di:

A titolo di esempio e compilando i campi nella finestra iniziale di Configurazione Iniziale del Client come in questo modo:

Il processo crea :

E si riferisce agli utenti → ruoli → dell'organizzazione che alla fine ha questa struttura:


Isetup.png


Il motivo per cui il processo si riferisce ai nuovi ruoli con l'utente Openbravo è perché Openbravo è il super utente dell'applicazione in modo che l'utente può gestire tutti le entità e il Dizionario dell'Applicazione.

La differenza tra gli utenti Sirof e Amedio proviene dai ruoli così come per le organizzazioni. Avere accesso all'organizzazione * significa che è possibile vedere tutto nell'applicazione in maniera indipendente dalla organizzazione. Tuttavia avere accesso solo all'organizzazione Pamplona significa che è possibile vedere solo i dati relativi a questa organizzazione.


2. Dati Contabili

Questo compito si occupa di:

Questo compito può essere evitato se il piano dei conti non è selezionato. Questo ha senso quando OB non è utilizzato a fini contabili ma solo per la gestione.

3. Dati Finanziari

Questo compito si occupa di:

4. Dati Master

Questo compito si occupa di:

Informazioni sul Client

Going to General setup → Application → Client → Client other things that can be configured:

Organizzazione

Introduzione

An organization is a business unit within an entity. Each entity can have more than one business unit, to reflect different departments or divisions of the parent entity. Organizations can be structured geographically, by region or by function. Every organization is managed independently, but it is possible to share information between them for example business partners and products.

Organizations are set up using a tree structure so an organization can have access to specific documents and those of the child organization but not to documents of the sibiling or parent organizations.

All the organizations always depends on the super organization called '*', which is created automatically during the Initial Client Setup process. A hypothetical tree could be:

Org1.png

Organizations can be independent of each other in terms of account structures, and reporting, but every organization has the following characteristics:

Tipi di Organizzazione

Organization types enable organizations to work together in a coherent way, by controlling how each organization behaves in relation to other organizations. There are four default organization types, which are sufficient for most business scenarios.

The default organization types have the following characteristics:

Organization Type Legal Entity Legal Entity with Accounting Business Unit Transactions Allowed
Organization N N N N
Legal with accounting Y Y N Y
Legal without accounting Y N N Y
Generic N N N Y

Periodo Fiscale

If an organization belongs to an organization type where the Legal Entity option is selected, you can specify whether that organization is or is not allowed to open or close its own accounting periods. If period control is enabled for an organization, any user with access to that organization can open and close an accounting period.

When opening a period, the user can opt to also open the selected period(s) for child organizations. However, when closing a period, the selected period is closed for all dependent organizations.

If an organization has multiple accounting schemas, the opened / closed period will also be opened / closed in all associated schemas.

Calendario Fiscale

It is not mandatory that each organization has a financial calendar, but where an organization is a Legal Entity, any sub-organizations that require financial calendars must use the same calendar as the parent organization.

Reportistica

You can restrict reports so that they can only be generated for organizations whose organization types have the Business Unit or Legal Entity option selected. In Financial Management > Accounting > Analysis Tools > User Defined Accounting Report Setup, the Filter by Organization option, if selected the Organization field displays only those organizations with a Business Unit or Legal Entity status.

Organization Type Parameters

For most enterprises, the default organization types are enough to enable you to model your organization. However, understanding the underlying settings of organization types will help you decide which organization types you require. Some enterprises may also need to create custom organization types.

In General Setup > Enterprise > Organization Type, there are four options that govern how organizations of each organization type behave.

Legal entity

If an organization type has the Legal Entity option selected:

Legal Entity with accounting

If an organization type includes the With Accounting option:

Transactions allowed

If an organization type includes the Transactions Allowed option, organizations belonging to the organization type are allowed to post transactions for accounting purposes. If an organization is of a type where transactions are not allowed, you cannot include that organization on an accounting document, for example an invoice.

Business Unit

If an organization type includes the Business Unit option:

Organization type rules

If your enterprise has more than one organization, you must observe the following rules when setting up the organizational structure:

It is recommended that you enable period controls on all organizations of legal entity with accounting and assign each legal entity organization its own calendar

Security/Multi-organization

The security permissions in a multi-organization follow this schema:


Orgsec.png


  1. Allowed to create documents in any organization except Org *
  2. Allowed to see data related to any organization
  3. Allowed to create any master data in any organization including Org *
  4. Allowed to create documents in Main org and Org1
  5. Allowed to see data related to Main org and its child organizations (org1, org2). Also the possibility of only selecting the Org1
  6. Allowed to create any master data in any organization except in Org2
  7. Only allowed to create documents in Org2
  8. Only allowed to see the data related to Org2
  9. Only allowed to create master data in Org2 including Org *

See also Creating an organization

Organization information

In this tab there are two very important fields that needs to be well configured:

The calculation of taxes depends on this because when a tax is configured there are four fields that must be correctly setup: Country from/Country to, Region from/Region to.

So in a procurement flow, OB takes the Country from and the Region from from the supplier location and the Country to and Region to from the Organization location.

In a sales flow, is the other way around.

This business partner is used for internal processes that needs a business partner. For example in internal transfers. Doing internal transfers (i.e from the cash journal to the bank account) means create two bills (one payment, one receivable) so a business partner is mandatory for this.

Not having this business partner setup the process Financial management → Receivables&Payables → Transactions → Funds transfers won't work.

Sicurezza

The purpose of this section is to explain the current model for Openbravo security.

Security can be divided into functional and data. Functional Security defines access to different application elements while Data Security determines which data inside those elements is accessible or not.

Sicurezza Funzionale

Vertical security manages the definition of users, roles and permissions adding users to roles and making possible to decide if a user can access to a determinate element (for example to a window, form, process)

So the issues involve in vertical security are:

Utenti

Users are the entities that can log into the application. The minimum requirements for a user to be able to log in is to have a password and at least one role associated. A user is supposed to be a representation of a person (each person should be a different user)

Ruoli

Roles are the connection between users and permissions, permissions are associated to roles and roles are linked to users. A role defines what information is allowed and which is forbidden. Despite of the fact that a single user can have multiple associated roles, only one role is effective at the same time: although the logged user has more than one role she or he will have to select one role or another one in order to have different access permissions.

Permessi

Different permissions can be associated to a role. The effect of this is that the role will have access only to those elements having permission to.

Permissions are defined in the following levels: Organization Access, Element Access (windows, forms, processes...) and Table Access.

Securityrol.png

Data security

Horizontal Security is managed by clients, organizations, access level and user level. Thus is decided which data is accessible and which is not.

Data access level

Access level defines from which client/organizations is data visible. Access level is set for tables, processes, forms, workflows and tasks, so any of this elements has one access level. There are five possible levels:

The access permissions for them is described in the table below, where:

Client Org Description
System 0 * Only allow to see records with client 0 and Org *. For example the application dictionary records
System/client Non 0 * Only allow to see records in any client except 0 and see Org *. For example master data records
Organization Non 0 Non * Only allow to see records in any client except 0 and see any org except *. For example transactional documents
Client/Organization Non 0 Any Only allow to see records in any client except 0 and see any org. For example transactional documents, master data


All Any Any Allow to see anything

User level

Every role has a user level which is used in the vertical security way in order to allow or deny access not only to data but to the whole element (for example to a window). There are three possible user levels (and their combinations): Client, Organization and System. User level is used in conjunction with Data Access level, so only roles defined with a type of user level can access to some types of elements defined in some Data Access level, it's summarized in the table below:


Data Access Level User Level
System System
System/Client System or Client
Organization Organization
Client/Organization Client or Organization
All System, Client or Organization

Configurazione Processi di Background

Any background process can be defined in OpenbravoERP. This processes can be developed as a PL or java file and they can be scheduled and automatically executed. Processes can be executed at whatever interval is required, daily or on the specific days of the week, as a recurrent event or a one-off at a particular time.

The steps to create and setup a process are:

Also the background processes can be activated or deactivated and this is very useful because sometimes when the process can run manually first is mandatory to stop the background process (i.e:PeriodicAcctServer)

Configurazione della Lingua

OpenbravoERP is a multilingual application which means it is possible to see the whole interface in different languages.

See the steps for import/export translations.

In Openbravo database exist some tables that have their own translation table. All these kind of tables must be filled in English and the translation ones in the language that user wants. Whenever you login in English you see the data from the original tables, but if you login in a different language you will see the data from the translation tables.

See the relation of the translations and tables.

Initially (from the installer) the translation tables comes in Spanish as a default language so means all the tables have their translation in Spanish.

The way to import/export translation work is:

Import export.png

Setup default values

In OpenbravoERP there are three ways of setting default values:

Whenever a user logs in, the application establish some session variables and within these are the default values. These all default values are managed in a hierarchy way.

Example 1:

A default value is set in Financial management->Accounting->Set up->Document type marking the record "POS Order"

Now as you are still logged in, if you go to the Sales order window and click New it won't show up the value "POS Order", but logging out and then logging in, the application will establish the new session variables and the "POS Order" value will show up

Example 2:

Maintaining the default value from example 1, the user may decide to set up another default value through the application dictionary in the same table as the window "Sales order" uses.

In this case the user must go to Application dictionary->Tables and columns-> and select the table C_Order. Then select the column C_Doctypetarget_id and fill the field "Default value" writing the ID for the corresponding document type. Let´s write for this example "Warehouse order".

This set up will have effect after the application is compiled

So now for the same window the OpenbravoERP has two default values, POS order and Warehouse Order, but this won't be a problem as the default values work in a hierarchy way.

The default value for the window will be "Warehouse order".

Example 3:

Finally the user decides to set up a new default value for the window "Sales order", but, in this case, using the preferences method.

The user should go to General set up->Application->Preferences and select the window, write C_Doctypetarget_id in the attribute field and the ID of the corresponding document type (e.g. Standard Order)

As before, only by logging out and logging in again will the new default value be established permanently.

So at this point OpenbravoERP will have three default values:

But the definitive default value will be "Standard Order" because the preferences method is the most restrictive way of setting up default values

Setup alerts

Alerts are the way Openbravo ERP informs users about virtually any event that happens in the system and the administrator has defined a rule to show it.

The work flow for alerts is as follows:

For more information click here


Setup Menu

The way of configuring the menu in OpenbravoERP is easy and simple. The menu is organized in a hierarchy way as a tree node.

There can be two types of nodes:

To add these actions in the menu and working:

  1. Create the element through the application dictionary: Windows, Reports, Process, etc.
  2. Compile the window, process, etc.
  3. Create node into the menu and add the action
  4. Finally move the node within the menu

Treenode2.svg


When a node group different nodes, no actions can be related. For example when you create a new module or different sections inside a module (i.e. Reports, Set up)

See how to change the order in the menu.

Retrieved from "http://wiki.openbravo.com/wiki/ERP_2.50:Functional_Documentation/General_Setup/it"

This page has been accessed 7,228 times. This page was last modified on 3 April 2012, at 11:00. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.