[jira] [Comment Edited] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[
https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963344#comment-15963344
]
Thisura edited comment on FINERACT-389 at 4/10/17 7:03 PM:
---
There is a limitation in implementing this in the backend. In the database, we
are storing only the "classification_enum" in the "acc_gl_account"
Classification Enum has the following values for respective account types.
{code}
ASSET - 1
LIABILITY - 2
EQUITY - 3
INCOME - 4
EXPENSE - 5
{code}
The values can't be used to reflect the ascending order of names. Therefore
ORDER BY "classification_enum" won't work in the sql query.
There fore we have two options.
* Write a sorting function to sort the result set based on the
classification_enum and then on gl_code.
* Change the classification_enum values to reflect the ascending order of
account types and add ORDER BY classification_enum ASC, gl_code ASC
The changed enums will look like follows.
{code}
ASSET - 1
LIABILITY - 5
EQUITY - 3
INCOME - 4
EXPENSE - 2
{code}
What is the best option? From the maintenance point of view, I think the first
option is better. But from the performance point of view, the second option is
better.
was (Author: thisura):
There is a limitation in implementing this in the backend. In the database, we
are storing only the "classification_enum" in the "acc_gl_account"
Classification Enum has the following values for respective account types.
{code}
ASSET - 1
LIABILITY - 2
EQUITY - 3
INCOME - 4
EXPENSE - 5
{code}
The values can't be used to reflect the ascending order of names. Therefore
ORDER BY "classification_enum" won't work in the sql query.
There fore we have two options.
* Write a sorting function to sort the result set based on the
classification_enum and then on gl_code.
* Change the classification_enum values to reflect the ascending order of
account types and add ORDER BY classification_enum ASC, gl_code ASC
The changed enums will look like follows.
{code}
ASSET - 1
LIABILITY - 5
EQUITY - 3
INCOME - 4
EXPENSE - 2
{code}
What is the best option? From the maintainance point of view I think the first
option is better. But from the performance point of view, the second option is
better.
> Arrange the accounts that fall under one account type in order of their GL
> codes
>
>
> Key: FINERACT-389
> URL: https://issues.apache.org/jira/browse/FINERACT-389
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
> Labels: p2
>
> Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825
> Original Description:
> Accounts in chart of accounts are arranged by their account type but those
> accounts in the specific account type are randomly arranged.
> I was recommending for the accounts in the same account type to be arranged
> by their GL code. Since the relating accounts will be under one header and so
> their GL codes will be following each other and bring presentable
> arrangement. (accounts in the same header, their GL codes should have
> relation)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (FINERACT-389) Arrange the accounts that fall under one account type in order of their GL codes
[
https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963344#comment-15963344
]
Thisura edited comment on FINERACT-389 at 4/10/17 6:56 PM:
---
There is a limitation in implementing. In the database, we are storing only the
"classification_enum" in the "acc_gl_account"
Classification Enum has the following values for respective account types.
{code}
ASSET - 1
LIABILITY - 2
EQUITY - 3
INCOME - 4
EXPENSE - 5
{code}
The values can't be used to reflect the ascending order of names. Therefore
ORDER BY "classification_enum" won't work in the sql query.
There fore we have two options.
* Write a sorting function to sort the result set based on the
classification_enum and then on gl_code.
* Change the classification_enum values to reflect the ascending order of
account types and add ORDER BY classification_enum ASC, gl_code ASC
The changed enums will look like follows.
{code}
ASSET - 1
LIABILITY - 5
EQUITY - 3
INCOME - 4
EXPENSE - 2
{code}
What is the best option? From the maintainance point of view I think the first
option is better. But from the performance point of view, the second option is
better.
was (Author: thisura):
There is a limitation in implementing. In the database, we are storing only the
"classification_enum" in the "acc_gl_account"
Classification Enum has the following values for respective account types.
{code}
ASSET - 1
LIABILITY - 2
EQUITY - 3
INCOME - 4
EXPENSE - 5
{code}
The values can't be used to reflect the ascending order of names. Therefore
ORDER BY "classification_enum" won't work in the sql query.
There fore we have two options.
* Write a sorting function to sort the result set based on the
classification_enum and then on gl_code.
* Change the classification_enum values to reflect the ascending order of
account types and add ORDER BY classification_enum ASC, gl_code ASC
The changed enums will look like follows.
{code}
ASSET - 1
LIABILITY - 5
EQUITY - 3
INCOME - 4
EXPENSE - 2
{code}
> Arrange the accounts that fall under one account type in order of their GL
> codes
>
>
> Key: FINERACT-389
> URL: https://issues.apache.org/jira/browse/FINERACT-389
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
> Labels: p2
>
> Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825
> Original Description:
> Accounts in chart of accounts are arranged by their account type but those
> accounts in the specific account type are randomly arranged.
> I was recommending for the accounts in the same account type to be arranged
> by their GL code. Since the relating accounts will be under one header and so
> their GL codes will be following each other and bring presentable
> arrangement. (accounts in the same header, their GL codes should have
> relation)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
