Adaxa's Financial Report improvements
Description
Environment
relates to
Activity
Deepak Pansheriya August 24, 2020 at 2:49 PM
@Carlos Ruiz View you mentioned and print format are not related to this enhancement. May be from Adempiere time as I noticed that you updated it for ticket IDEMPIERE-764. If not used then good to delete from core and it may be added using 2pack for whom it is required.
Carlos Ruiz August 24, 2020 at 8:46 AM
Thanks @Steven-Adaxa.
Just noticed the view, report view and print format are inactive in core, so maybe would be better just to delete that.
I noticed the issue because postgresql forbid changing some things unless you delete and recreate the views associated, in this case I was deleting the addDays operator.
Regards,
Carlos Ruiz
Steven-Adaxa August 24, 2020 at 2:16 AM
Hi Carlos,
re: "to_char(f.dateacct::timestamp with time zone + 184::numeric, '"FY"YYYY'::text) AS fyear,"
I dont think this view is used in Financial Reports .. it was a View I used to create quick summary reports by summarising factacct down to one trx per month per org per account and then adding columns for A/C Type, (B)alance Sheet or (P)rofit and Loss .. and a column for Financial Year.
AU standard financial year begins on 1 July so the column said 'add 6 months to the date, find the 'year' value and stick "FY" in front of the year value'. (it works fine for any Financial year using a different offset provided the start date is after 29 Feb).
This was all done before Report Cubes were implemented but it is still useful as a check relying only on the posted transaction data and it is quick. For it to be completely replaced we needed a report and process for 'extract data from Cube' which looked at a View created from the Cube data table but had extra columns added such as Accounted Amount, Financial Year, 'account from' to 'account to', Account Type, (B)alance Sheet or (P) and L etc. I still use it fairly often.
regards
steven
Deepak Pansheriya August 23, 2020 at 4:58 AM
@Carlos Ruiz will check this and if not fixed then will create sub ticket.
Carlos Ruiz August 22, 2020 at 1:35 PM
Not sure if is related to this one, but maybe it can be reviewed.
Recently I found that the view rv_fact_adaxa intended for financial reports has a hardcoded value to calculate the fiscal year:
to_char(f.dateacct::timestamp with time zone + 184::numeric, '"FY"YYYY'::text) AS fyear,I think it would be better to calculate the fiscal year based on the C_Period
This is parents tickets to trek progress of porting Adaxa's Financial report enhancement to iDempiere. Currently following enhancements are known
1. Making configurable to show opposite sign on financial report
2. Add "Related Period To" field on Financial report column set to specify range relatively
3. Drawing Under/Over line in report (For highlighting total or showing separator)
4. Reversing values on lines
5. Adding configurable report header
6. In Report source, adding support for User1 and User2
7. Adding Display logic on print format item