OFBiz › OFBiz - User

Best way of implementing (external) code tables in ofbiz

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

tore@skynet.be

Best way of implementing (external) code tables in ofbiz

Dear All,

I have some code tables I want to add in my ofbiz installation.

* Excise Products Categories
* Excise Product
* Cn Codes
* Correspondences Cn Code - Excise Product1
* Units Of Measure
* Events Types
* Evidence Types
* History Refusal Reasons
* Language Codes
* Member States
* Country Codes
* Administrative Cooperation Actions
* Administrative Cooperation Request Reasons
* Packaging Codes
* Reasons For Unsatisfactory Receipt Or Control Report
* Reasons For Interruption
* Transport Modes
* Transport Units
* Wine-Growing Zones
* Wine Operation Codes
* Reasons For Delayed Result
* Cancellation Reasons
* Alert Or Rejection Of E-Ad Reasons
* Delay Explanations
* Event Submitting Persons
* Administrative Cooperation Action Not Possible Reasons
* Common Request Rejection Reasons

Most of them have the same format : code , description.

Normally there used to be 2 ways to implement this type of code tables

a) for each code a new table is created with the corresponding screen
for maintenance on the table
b) one code table is created and a field was added as 'descriptor' for
the code. The maintenance screen used the descriptor to filter the
correct codes

What would be the best way to implement these in Ofbiz ?

Kind regards

Tore

Adrian Crum-3

Re: Best way of implementing (external) code tables in ofbiz

I would recommend reading The Data Model Resource Book - the OFBiz data
model is based on it.

-Adrian

On 1/3/2013 8:35 AM, [hidden email] wrote:

> Dear All,
>
> I have some code tables I want to add in my ofbiz installation.
>
> * Excise Products Categories
> * Excise Product
> * Cn Codes
> * Correspondences Cn Code - Excise Product1
> * Units Of Measure
> * Events Types
> * Evidence Types
> * History Refusal Reasons
> * Language Codes
> * Member States
> * Country Codes
> * Administrative Cooperation Actions
> * Administrative Cooperation Request Reasons
> * Packaging Codes
> * Reasons For Unsatisfactory Receipt Or Control Report
> * Reasons For Interruption
> * Transport Modes
> * Transport Units
> * Wine-Growing Zones
> * Wine Operation Codes
> * Reasons For Delayed Result
> * Cancellation Reasons
> * Alert Or Rejection Of E-Ad Reasons
> * Delay Explanations
> * Event Submitting Persons
> * Administrative Cooperation Action Not Possible Reasons
> * Common Request Rejection Reasons
>
>
> Most of them have the same format : code , description.
>
> Normally there used to be 2 ways to implement this type of code tables
>
> a) for each code a new table is created with the corresponding screen
> for maintenance on the table
> b) one code table is created and a field was added as 'descriptor' for
> the code. The maintenance screen used the descriptor to filter the
> correct codes
>
> What would be the best way to implement these in Ofbiz ?
>
> Kind regards
>
> Tore
>
>
>

Atul Vani

Re: Best way of implementing (external) code tables in ofbiz

In reply to this post by tore@skynet.be

Check if "Enumeration" and "EnumerationType" entities are useful to you.
Although, I would suggest the same as Adrian.

On Thu, 03 Jan 2013 16:10:00 +0530, Adrian Crum
<[hidden email]> wrote:

> I would recommend reading The Data Model Resource Book - the OFBiz data
> model is based on it.
>
> -Adrian
>
> On 1/3/2013 8:35 AM, [hidden email] wrote:
>> Dear All,
>>
>> I have some code tables I want to add in my ofbiz installation.
>>
>> * Excise Products Categories
>> * Excise Product
>> * Cn Codes
>> * Correspondences Cn Code - Excise Product1
>> * Units Of Measure
>> * Events Types
>> * Evidence Types
>> * History Refusal Reasons
>> * Language Codes
>> * Member States
>> * Country Codes
>> * Administrative Cooperation Actions
>> * Administrative Cooperation Request Reasons
>> * Packaging Codes
>> * Reasons For Unsatisfactory Receipt Or Control Report
>> * Reasons For Interruption
>> * Transport Modes
>> * Transport Units
>> * Wine-Growing Zones
>> * Wine Operation Codes
>> * Reasons For Delayed Result
>> * Cancellation Reasons
>> * Alert Or Rejection Of E-Ad Reasons
>> * Delay Explanations
>> * Event Submitting Persons
>> * Administrative Cooperation Action Not Possible Reasons
>> * Common Request Rejection Reasons
>>
>>
>> Most of them have the same format : code , description.
>>
>> Normally there used to be 2 ways to implement this type of code tables
>>
>> a) for each code a new table is created with the corresponding screen
>> for maintenance on the table
>> b) one code table is created and a field was added as 'descriptor' for
>> the code. The maintenance screen used the descriptor to filter the
>> correct codes
>>
>> What would be the best way to implement these in Ofbiz ?
>>
>> Kind regards
>>
>> Tore
>>
>>
>>
>

--
Using Opera's revolutionary email client: http://www.opera.com/mail/

Eric.LENS

RE: Best way of implementing (external) code tables in ofbiz

In reply to this post by Adrian Crum-3

Hello Tore,

I think you have to define your new tables as XML definitions which are then automatically created when you restart ofbiz.
I can confirm that the Data Model Resource Book is a must to read in order to have an overview of the database architecture and some business explanations.

Regards,
Eric Lens

-----Original Message-----
From: Adrian Crum [mailto:[hidden email]]
Sent: Thursday, January 03, 2013 11:40 AM
To: [hidden email]
Subject: Re: Best way of implementing (external) code tables in ofbiz

I would recommend reading The Data Model Resource Book - the OFBiz data
model is based on it.

-Adrian

On 1/3/2013 8:35 AM, [hidden email] wrote: