Related issue 29602: Changed UI pattern to read only mode in some tabs

The problem was that some tabs have their UI patterns wrong.They are
not set properly.

Now it have been solved by updating the UI Pattern to read only mode.

Fixed 30050: cleanup javadoc warnings
This commit clean up all javadoc warnings as shown by eclipse or
ant generate.java.doc
Exception are 3 warnings inside CSSMinimizer.java which is external code
and will should be fixed differently (upstream)

Most fixes are:
- Deleting useless java doc tags (useless as not documenting anything)
- Fixing up paramater references and link target

CI: merge back from main

CI: update AD_MODULE to version 26798

Related to issue 25355: Executed Synchronize Terminology

Related to issue 25355: Fix Dimension fields display

Dimension fields display in Payment In Lines and Payment Out Lines tabs will now work with Accounting Dimensions Central Maintenance.
Also, Order Payment Schedule and Invoice Payment Schedule fields navigation has been fixed.

Fixed bug 25355: Long time to show the lines on the payment in/out windows

Related to issue 29867: grid checkboxes are now selected on refresh
when multiple records were selected

CI: merge back from main

CI: update AD_MODULE to version 26793

Fixed issue 29867: Now grid multiple selection is not lost on refresh

If the selected items are in different pages, only the items belonging to the land
page once the grid get refreshed will be shown. A message notifying this loss will
be shown (in the message bar if this is empty or as a popup if there is a message
already been displayed, to avoid loss its information if we come from a process
execution)

Fixes issue 30007: Payment schedule amount incorrectly calculated.

Payment schedule amount incorrectly calculated when adding a payment from reconcile window to a sales order.
FIN_TransactionProcess and PaidStatusEventHandler have been changed in order to set invoicepaid=true only when FIN_PaymentScheduleDetail has a related InvoicePaymentSchedule.
FIN_PaymentProcess.java has also been changed, in order to check invoicePaidAmounts only if FIN_PaymentScheduleDetail has a related InvoicePaymentSchedule.
In case of a payment to a order without an invoice, updatePaymentAmounts will be called only once.
Name of preference in UpdatePaymentPlan modulescript has been update to run it again and fix wrong data created by the issue.

Fixed issue 29857: When there are not linked items it appears "Loading"

When there are no linked items, the linked items category section shows the message "Loading data..."
instead of the message "No items to show".

The problem was that the fact of not having any item category was not correctly handled.
In the initWidget function, when the linkedItemCategoryListGrid is created, in the function "dataArrived"
there was a condition which called the function that showed the correct message "No items to show" when the
startRow was '0' and when de endRow was '-1', the problem was that in this case of not having any linked Item
category, the endRow and the startRow where both '0', so, the correct message was never shown and it always shows
the message "Loading data...".
To fix this, the condition has been changed, now it is taking into account the length of the data, and if it
is '0' that means that there are not linked items so, the message "No items to show" is shown.

CI: merge back from main

CI: update AD_MODULE to version 26790

Related to issue 25278: updated copyright and fixed indentation

Fixed issue 25278: Long time to update a warehouse with thousends of locators

On an environment with 60.000 locators for one of the warehouse, when updating
a field of the warehouse it takes a long time to save the record.

Part of the problem is the update of the m_warehouse table. When updated, the
trigger launch an update of the organization id for M_LOCATOR and
M_WAREHOUSE_ACCT tables.

The solution is to check if the organization has changed and, if not, avoid the
unnecessary update of those tables.

Related to issue 29566: fixes deprecated method calls in ReportDesignBO

Fixed bug 29904 Performance improvements for orderloading in finance core

review flush () and .list () in FIN_PaymentProcess and FIN_TransactionProcess

Related with issue 29709: Some test cases have been created.

Some test have been created for testing the correct behaviour of the OB.Utilities.Number.roundJSNumber,
OB.Utilities.Number.ScientificToDecimal and OB.Utilities.Number.OBMaskedToOBPlain functions.

fixed bug 30016: upgrading from 2.50 to pi some FKs are missing

There were 2 scenarios where this occurred:
* FKs from recreated to non recreated tables in case none of them are in AD
* both tables participating in the FK are recreated and the referenced one
is loaded before the referencing one in the model

CI: merge back from main

CI: update AD_MODULE to version 26780

Fixed bug 30021: Requisition To Order with several secondary UOMs per product

The system was grouping requisition lines by product without taking into account the secondary UOM.
Now the code takes into account the M_Product_UOM_Id column too to group/split the purchase order line.

Fixed bug 30002: Error in Requisition To Order window

When creating a purchase order from the Requisition To Order window, an error was raised when lines[i].quantityorder is empty.
Now the SQL query returns quantityorder = 0 when it's null. Then, when inserting the purchase order line, the process inserts "" if quantityorder = 0

Fixed issue 30014: There are problems with big numbers in scientific notation

The problem was in OB.Utilities.Number.OBMaskedToOBPlain.
When the function was executed with a big negative number in scientific notation or a positive number with the "+" sign at the beginning, the
obtained decimal value was not correct.
This was caused because the length of the variable "number" (which was the number in scientific notation), was used for creating the final number instead of the
length of the variable "plainNumber", (which was the number in decimal notation).
This generated a problem because, when the spected result was a number longer than the number in scientific notation, it was not correctly obtained.
For example:

-1.0564E7 returned -10564000. This is correct, but:

-1.0564E8 returned -10564000. And this is not correct.

CI: merge back from main

CI: update AD_MODULE to version 26774

Fixes issue 29921: ImportEntryProcessor.LocalHttpRequest compilation errors with Tomcat 7
Removed local declared subclass declaration of HttpRequest, make use of VariablesSecureApp
now working without session

Fixes issue 29934: Extend VariablesBase to internally store session values even if there is no session object
Keep values in Map if there is no session. Changeset includes testcase