Fixed bug
29808: Impossible to create several calendars for the same organization
Two pieces of code were affected by this bug:
PeriodEventHandler.java: EntityPersistenceEventObserver in charge of checking overlap in manual inserts/updates (or any java process) in c_period table
C_YEARPERIODS: db function associated to the create periods process inside the Fiscal Calendar | Year tab. It also verifies the periods don't overlap other periods.
The fix consists in checking that there is no date overlap per calendar. Before this fix the calendar wasn't taken into account, so it was not possible to define several calendars for the same organization with the same periods.
Related to issue
29808: Backout wrong changeset
The changeset pushed was not the good one, and failed in Oracle
Related to bug
29884: Code Review
Add coalesce in case there is no batch associated to set GL Journal Org, in order to avoid issues in the if condition done right after the query if null values are compared
Fixes issue
29884: Error while completing a Simple G/L Journal in Oracle
A query in gl_journal_post has been changed to avoid errors in Oracle when retrieving a null id
Fixes issue
29889 & Fixes issue
29887: Error in Price Correction Background
IsCostCalculated will not be considered to set CheckPriceDifference flag, when completing an invoice.
Instead, when running Price Correction Background, transactions will be filtered by IsCostCalculated to avoid calculate price differences in transactions where cost has not been calculated.
Fixes issue
29899: False positives in GLJournalAccountingCheck validation
Missing ad_table_id constraint ends up in wrong validation when there are old records using numeric values for ids.