/
TAPSS-90 Retain Original Designation Code on Transaction

Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au

TAPSS-90 Retain Original Designation Code on Transaction

As a

GA User

I want to

be able to ensure that we have a record of original COA on transaction

So that

we can trace where we put the money on originally as COA are being moved to different accounts more frequently in the recent times.

 

 

Acceptance Criteria: GIVEN COA codes are changed WHEN Transaction gets' updated THEN we have a record of the original COA code when the transaction was created. AND we should also check historically all transactions where COA could have been updated. check change history on COA then compare changes on linked transactions.

Business Value: Traceability of Gift

GA needs to store COA snapshots, when updating to COA records, there’s a history kept .
Currently process is not very robust - this will uplift and improve the business process

Technical Design/notes:
USYD_Original_Class_Code__c - existing logic

 

 

Acceptance criteria:
USYD_Original_Class_Code__c = COA-group One

USYD_Origina_Designation_Account_Number (new field) = COA-grouptwo-Groupthree-Group-four

 

Add the new field to the page layout and remove the AQB field Designation Account Number

@AlainGasquet @Polina Nikulina Monica has suggested that if any reports have the AQB_Designation_Account_Number field to be removed and use the new USYD_Original_Designation_Account_Number.

Could you please confirm which report types related to Transaction data are in use so that I can make the new field available.

 

Technical Design Notes:

  • Create a new Transaction Before Save flow to capture the Original class code to existing field from COA Group one.

  • Created a new field Original Designation Account Number to capture the COA grouptwo-groupthree-groupfour.

  • Removed the field AQB_Designation_Account_Number from the layout and added the new USYD_OriginalDesignationAccountNumber.

  • Deactivate the existing flow “USYD Populate Chart of Accounts in Transaction (subflow)”.

  • And removed the sub-flow call in the main flow “Transaction After Save”.

Test Scenario 1:

  • Create a Batch with Batch Items and close the batch

  • Transactions will be auto created linked to Batch

  • Open the Transaction and check the Original Class code and Original Designation Account Number at page layout

COA used in the batch item

  • As per the business requirement, now the

    • transaction-Original Class Code = 1234(Segment One)

    • Transaction-Original Designation Account Number = 2232-3223 (Segment two-Segment three) as Segment four is blank

Test Scenario 2:

  • Once the batch closed and transaction created

  • Change the COA, segment one and add the segment four value

  • The Transaction values shouldn’t change

Related content

TAP Product Enhancements Log
TAP Product Enhancements Log
Read with this
TAPSS-63 Flow to record the Original Class Code and Account Number upon Dues transaction creation
TAPSS-63 Flow to record the Original Class Code and Account Number upon Dues transaction creation
More like this
TAPSS-830 Retaining Original Receipt Name on Receipt
TAPSS-830 Retaining Original Receipt Name on Receipt
More like this
TAPSS-68 O2G Relate New COA Creation task to the GIN instead of COA
TAPSS-68 O2G Relate New COA Creation task to the GIN instead of COA
More like this
TAPSS-262 Opportunity Component validation against Opportunity Account type - pending COA
TAPSS-262 Opportunity Component validation against Opportunity Account type - pending COA
More like this