Adding a quantity field to WorkEffortInventoryProduced seems to be
correct since it exists for WorkEffortInventoryAssign.
WorkEffortInventoryAssign also has a statusId field but I'm not sure if
its necessary to add to WorkEffortInventoryProduced also.
I discovered that createAcctgTransForWorkEffortInventoryProduced doesn't
store the inventoryItemId field while trying to figure out a way to
track the original inventory quantities produced by production run
tasks. Since my original intent has been satisfied I'm not as worried
about the potential accounting issue described. If someone thinks its
worth creating a JIRA issue to resolve it then it will be done.
Otherwise I'm not sure how to proceed at the moment and will abandon it
for now.
On 03/06/2014 12:56 PM, Christian Carlow wrote:
> Perhaps adding a quantity field to WorkEffortInventoryProduced would
> be a better solution than adding fields to AcctgTransEntry?
>
> On 03/06/2014 12:28 PM, Christian Carlow wrote:
>> Shouldn't the inventoryItemId be stored in the acctgTransEntry entity
>> when created from production run task declarations or am I
>> misunderstanding something?
>>
>> Also, shouldn't the original quantity that was credited be tracked
>> also? There is no orig_quantity field in AcctgTransEntry as there is
>> for the orig_amounts and orig_currency. Is there any reason an
>> orig_quantity field shouldn't be added to the AcctgTransEntry
>> entity? Without such a field, is there any other way to determine
>> how much inventory a production run task produced? The
>> WorkEffortInventoryProduced table only contains the inventoryItemId
>> and workEffortId fields so the original quantity can't be determined
>> after the InventoryItem quantities are updated.
>
Locked
