Importing Files.

Throughout the Manual reference is made to CSV files for mass data loading.
It is recommended to enter the System as a User Administrator of the Client and preferably in English. Most of the generated files have their titles in English.
Additionally it is recommended to select 'Charset used for import / export:' Windows-1250. In this way the accented characters and the ñ will be recognized when importing.

LCO Localization

The LCO localization, allows to incorporate the management of retentions mainly.
  For version 2.0, the procedure is described in the file:

LCO Instructions Installation.docx

Fundamentally it consists of incorporating the 'plugins':
• org.globalqss.idempiere.LCO.detailednames_1.0.0.201309201607.jar
• org.globalqss.idempiere.LCO.withholdings_1.0.0.201309201607.jar
• org.globalqss.idempiere.LCO.magneticmedia_1.0.0.201309201607.jar
Using the FENIX console.
Important, Fields Added to the 'lco_invoicewithholding' table:
• 'Documentno'
• 'Description'

Definitions of Supported Languages.

The version 2.0 September 2014, comes by default configured with English and Spanish Colombia (es_CO). It is necessary to define the Spanish language Venezuela (es_VE) to differentiate the terms expressed in the menus, messages, aids and screens of the system.

There is a large number of tables containing the translation information from the base language to the specified language with the acronym 'ISO Language Code', es_VE for example.

The file 'Change_languaje_from_es_CO_to_es_VE.sql', changes all these tables and places es_VE where es_CO exists and simply changes the terminologies. Then some will have to be changed manually to adapt them to Venezuela.

In the system you must define the Language es_VE as 'System Language'. To do this, enter the system as "System" and select the menu.

"Menu / System Admin / General Rules / System Rules / Language"

Locate the record 'es_VE' and place the check 'System Language'.

This option is the least recommended, because it replaces es_CO translations with es_VE.

The best thing to do is to define the es_VE language as the system language and execute the 'Languaje Mantainance' process. To do this, enter the system as user 'System' and select the menu:

"Menu / System Admin / General Rules / System Rules / Language"

Locate the 'es_VE' registry, define the Check 'System Language' and execute the 'Languaje Mantainance' process. Thus, in this way the system creates new translation records to all tables.
Run the SQL Scrip:

Create_language_from_es_CO_to_es_VE.sql

This script replaces the translations of 'es_CO' into 'es_VE', keeping the 'es_CO' translations unchanged. Subsequently, the translation records 'es_VE' must be modified by the same content of 'es_CO' and change those whose terminology is different.

Backup File: idempiere2.0_src_baseVE.backup.

Installation of Venezuela's Demography

Method A:

It starts from the BD Adempiere_pg.dmp version 2.0.

Once the Database is installed.

The GeographyVenezolanaCompleta.sql Procedure is executed
The zip pack is incorporated
The processes are: 'Synchronize Terminology' and 'Sequence Check'

Method B:

We use the DB:

Idempiere2.0_src_baseVE.backup.

The Complete Demography contains:

Countries (c_country)

Country Regions (c_community * NEW)

States or Provinces (c_region)

Cities (c_city)

Municipalities (c_municipality * NEW)

Parishes (c_parish * NEW)

Postal Zones (c_zipcode * NEW)

Location (c_location)

 

Modification of the Location table to include the variables:

In addition to (c_country_id, c_region_id, c_city_id)

The variables (c_municipality_id, c_parish_id and c_zipcode_id)

To relate them to the corresponding tables.

Additional Consideration for Address Formats:

Define the Default Address of 'System'
Define Capture Order of Address Fields
Default address.

For the default Address enter the System as user 'System' in English preferably. Then locate the 'Location' screen:

System -> Data -> Utilities -> Location

Place the main address, especially the Region and the Country. See figure 1.4.1.

 For the order of capture of the address data, the system validates it for each country. In the case of Venezuela we locate the es_VE Language. Using the menu option:

 

Figure 1.4.1

 For the order of capture of the address fields, it must be modified in the country register, according to the menu:

 

System -> General Rules -> System Rules -> Country Region and Cities

 

Modify the Capture Sequence field according to the following rules:

Capture Sequence

The Capture Sequence defines the fields to be used when capturing an address on this country. The following notations are used: @ CO @ = Country, @ C @ = City, @ P @ = Postal, @ A @ = PostalAdd, @ R @ = Region, @ A1 @ = Address 1 to @ A4 @ = Address 4. Country is always mandatory, add a bang! To make another field mandatory, for example @C! @ Makes city mandatory, @ A1! @ Makes Address 1 mandatory.

 

Figure 1.4.2

The sequence that best uses the combos suggested:

@CO@ @R@ @C@ @A1@ @A2@ @A3@ @A4@, @P@

Idempiere version and Database.

It takes as a starting point version 2.0 of Idempiere (2.0.0.v20140925), whose database version 201409251410_Version.sql. This information is contained in the 'adempiere.ad_system' table and corroborated with the source program in './base/src/org/compiere/Adempiere.java'.

Backup File: idempiere2.0_src_base.backup.

This Database in PostgresSQL Version 9.1. We have called it 'idempiere2.0' and it is conformed by:

Schemas: 2 (adempiere and public)

Approximately Tables: 843, Views: 151, Functions: 61, Operators: 2

Login Form