Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We were planning to have a relook at 

Jira Legacy
serverJIRA (mifosforge.jira.com)
serverId6ed65b55-ae19-3f63-b72c-a969383d4221
keyMIFOSX-695
 and try to clean up the same. However, we are now a bit confused on the functional requirements 

Intra-Branch Transfers

Earlier, I was assuming that the fund sources for all products would be the same, so consolidated transactions like 

...

would make sense (as long as all of them are within the same branch)

 

Questions (Blocker):

What happens if the fund source for two products are different? 

...

Also, such concerns may be purely developer issues and not a valid use case? Can somebody please have a look at the suggested consolidated postings and comment?

 

Technical Changes are quite straightforward: 

Technical Implementation 

 

Approach 1] Created Unbalanced Journal entries for the actual Loan and savings Transaction

Ex, for Scenario 1, create a debit for the Loan Transaction and a debit for the savings transaction?

Approach 2 ] Link journal entries to the account Transaction (in m_account_transfer_transaction)

entity_type_enum = 3 (Account Transfer)
what would the entity Id be? = Need to have a re-look
transaction_id = link to m_account_transfer_transaction ( Here add a new convenience label a "m_account_transfer_transaction tables id" )
account_transfer_transaction_id foreign key

 ( Is Payment details to account transfer (needs to be passed from the account on which the transaction was made) = Need to have a re-look

 

Approach 2] Created Unbalanced Journal entries for the actual Loan and savings Transaction

Ex, for Scenario 1, create a debit for the Loan Transaction and a debit for the savings transaction?