New field proposal for UomConversionDated entity

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

New field proposal for UomConversionDated entity

Bilgin Ibryam
Hi Devs,

We have different currency rates(conversionFactor) for different  
purposes (internal currency conversion for invoices, external for  
customer currency exchange and son on) for the same date.

For coverring this case I´d like to add a new purposeEnumId field to  
UomConversionDated entity, so it can be possible to use the right  
conversion Factor based on purpose and date.

Are there any other proposals/ideas for handling this case?
If nobody sees a problem in this change, I will commit it after one  
week.

Thanks
Bilgin
Reply | Threaded
Open this post in threaded view
|

Re: New field proposal for UomConversionDated entity

Sumit Pandit-3
+1,

Bilgin it's a good idea. It make identification easy.


----- Original Message -----
From: "Bilgin Ibryam" <[hidden email]>
To: [hidden email]
Sent: Wednesday, November 19, 2008 4:46:28 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: New field proposal for UomConversionDated entity

Hi Devs,

We have different currency rates(conversionFactor) for different  
purposes (internal currency conversion for invoices, external for  
customer currency exchange and son on) for the same date.

For coverring this case I´d like to add a new purposeEnumId field to  
UomConversionDated entity, so it can be possible to use the right  
conversion Factor based on purpose and date.

Are there any other proposals/ideas for handling this case?
If nobody sees a problem in this change, I will commit it after one  
week.

Thanks
Bilgin
Reply | Threaded
Open this post in threaded view
|

Re: New field proposal for UomConversionDated entity

Bilgin Ibryam
In reply to this post by Bilgin Ibryam
Committed in r721431

On Nov 19, 2008, at 1:16 PM, Bilgin Ibryam wrote:

> Hi Devs,
>
> We have different currency rates(conversionFactor) for different  
> purposes (internal currency conversion for invoices, external for  
> customer currency exchange and son on) for the same date.
>
> For coverring this case I´d like to add a new purposeEnumId field to  
> UomConversionDated entity, so it can be possible to use the right  
> conversion Factor based on purpose and date.
>
> Are there any other proposals/ideas for handling this case?
> If nobody sees a problem in this change, I will commit it after one  
> week.
>
> Thanks
> Bilgin