Trunk changes for the german localization
Description
Environment
Attachments
- 11 Sep 2014, 06:02 PM
Activity
Carlos Ruiz April 17, 2015 at 10:19 PM
I think this has been solved - can you please recheck - and reopen if necessary commenting what is still needed
eugen hanussek September 11, 2014 at 6:39 PMEdited
Hi Dirk, Thomas,
there are two things to consider:
the Option Country has Regions, this is Dirk' remark
the Capture Sequence, (this is Thomas' intention ?)
The default in iDempiere is defined like this:
indeed we have regions in Germany and the first default is OK. So in the INTRASTAT report you can defne the fields "Ursprungsregion" resp. "Bestimmungsregion" with @R@.
But the second defalt can be changed, if we allways want to seek for cities corss the regions. This is good if we have recorded only a few cities. Then the default for Capture Sequence can be:
@A1@ @A2@ @A3@ @A4@ D-@P@ @C@ @CO@
I prefere the iDempiere-default, even while iDempiere comes without any DE-citi
By the way:
the Postal Code Format in Germany is defined by 00000
Regards EUGen H.
eugen hanussek September 11, 2014 at 6:02 PM
Screenshon from https://demo.idempiere.com/webui/
Dirk Niemeyer April 28, 2013 at 1:18 AM
Hi Thomas,
I like to object against your proposal concerning regions. When a company is trading goods inside the EU it has to regularly provide the so called INTRASTAT report. One of the details in the report is the German region of the final destination of the goods. For a German localization we should comment out the related code for printing the region in MLocation.
Regards,
Dirk Niemeyer
The Team Germany decided in his last meeting to create a plugin package with german localizations. Some of the changes we need are simply faults in the core database. I want to collect these core contributions under this jira issue.
First examples:
germany has political regions but they do not have to be written in addresses. So in the country database we should switch off the regions
with every language import I have to set the right date and time format. These could be in the database from beginning