Related to Issue 27853: Not any more wrong records created in Costing tab

Changed the filter by Id in CostAdjustmentUtils.getStockOnTransactionDate(), CostAdjustmentUtils.getValuedStockOnTransactionDate() and AverageCostAdjustment.getRelatedTransactions().

Fixes issue 27853: Manual Cost Correction Cost adjustments are not properly created

Fixed bug 27969 landed cost from receipt should be created in status complete

Fixed bug 27966 LandedCostCost should be re-initialized

Fixed 27879.Properly calculate adj amount on backdated inventory amt update.

3 changes have been applied to fix the issue:
- Consider the possibility of having average costing not related to
transactions.
- Properly calculate the adjustment amount of closing inventories. The transaction
that is being adjusted is already calculated and included in the
currentBalanceAmount so no need to compare against it.
- It was checking the fix backdated transactions flag using the fix backdated
transactions process button property instead of the flag's property.

Fixed issue 27947.Use org id instead of object in OBQuery

When filtering a OBCriteria or OBQuery by a BaseOBObject after a clear session
can fail if the object is not correctly reattached to the session. Filtering
by its id avoid this issue.

Fixed issue 27946.Add negative correction for basetrx when needed.

In some cases like Price Difference Correction it is possible to have a base
trx that also requires a negative stock correction adjustment. A check is
added to insert an aditional negative correction line for the base transaction
when needed.

Fixed bug 27968 set properly the organization when process a landed cost from receipt

Costing background fails when a landed cost from receipt is pending to be calculated
and the consting background process is sheduled in Organization "*"

Fixed bug 27972 Landed cost field should be readonly in landed cost tab

Fixed bug 27971 Process matching should not be shown in Goods Receipt window

Fixed bug 27950 Unit Cost of the Inventory Amount Update window is not calculated

Currency is not mandatory in organization, if currency in organization is null
the reference currency should be client currency.

Related to issue 27924

Related to issue 27924

Related to issue 27924

Filter by organization in query should be by FinancialMgmtPeriodControl

Fixed bug 27924 be able to enter backdatedfrom while creating a costing rule

Fixes Issue 27925: Match LC Cost Process P&E now processes correctly Matchings

The problem was due to a missing OBDal.getInstance().flush().

Also LCCostMatchFromInvoiceHandler.java action handler has been improved to return correctly error messages.

Fixes Bug 27926: Fixed process a Landed Cost with amt different than Matched amt

A condition has been removed from m_lc_cost_chk_trg that was preventing to update m_lc_cost table.

Fixes issue 27929: Landed Cost correctly manages multicurrency

Landed Cost adjustment was being created with currency of transaction instead of Landed Cost Cost currency.
The transaction cost currency was being created on Landed Cost adjustment currency instead of transaction currency.

Fixes Issue 27963: Set Unit Cost false in LC Adjustments created in Match LC P&E

Also set as currency of this Landed Cost Adjustment lines the currency of the Landed Cost header.

Fixes Issue 27970:Add Read Only Logic on Landed Cost tab fields in Goods Receipt

Also hide Active field of Landed Cost tab in Goods Receipt window.

Related to issue 27887.Boolean filters are advanced criterias

When filtering by a boolean in a grid the criteria received by the datasource
is an AdvancedCriteria. New isInScope method created for boolean fields based
on the version for BigDecimals to cope with this type of criterias.

Related to issue 27887.Implement filtering by Allocated field.

Fixed issue 27887.Set required fields as show in grid true.

Related to issue 27913

fix convertDateToUTC method and match statement force name process

Related to issue 27913. Miossing related files

Related to issue 27913: Adds comments to method and chnages method name

Fixes bug 27913: System throws error message when user try to match bank statement lines with OB transactions manually

There was a new method created in OBDateUtils which was asuming parameter date was always in the current date. This was wrong so that chnage is reverted and method is no longer doing that assumption.

Related to issue 27913 Add convertToUTC to obdateutils

Fixed bug 27913 variable updated properly formatted in match statement

After fixed issue 27912, variable updated in match statement should formatted as
a date and the conversion to utc should not be performed.

Fixes issue 27912: Time&DateTime fields are properly handled in P&E Windows

The values of Time and DateTime fields were not being properly handled, as they where not converted from the server timezone offset to UTC before being sent to the client. This happened
because the DataToJsonConverter.convertToJsonObjects method did not perform the conversion.

Now it does, when possible. For the conversion to be done properly, the Property associated with the column value must be passed to the convertPrimitiveValue method. This will be done a
s long as the tableId parameter is sent in the datasource request, and as long as the property name can be inferred from the column name.

The QueryListDataSource extends ReadOnlyDataSourceService, but the tableId is not passed, so this changeset does not fix this case, that will be address in a separate issue.