Wiki source code of Twopot testing

Version 1.1 by Phillip Swanepoel on 2025/02/04 10:44

Show last authors
1 go to ~~\Dropbox\EBSphere\Everest SQL\SQL\2Pot Claims Automation [DO NOT RUN]
2 \\Run in all scripts, compare before running from folders: 'Critical Core SPS'
3
4 Can only be tested if the products are set up already.
5 Testing:
6 Kick off workflow on Everest:  Member > Statutory > "Process Withdrawal" (edit > change selected withdrawal amount) (also test recalculate)
7 User need bank details for two pot withdrawal under the type 'South African 2 Pot withdrawal' - needs to be verified by hyphen (or bypassed for testing)
8
9 checks on db:
10 check tblClaim event where fkimemberid= 'xxx' for blnprocessed = 1 (not cancelled)
11
12 check tblworkflowtracking where fkimemberid = 'xxx' as the steps are completed. (validation can fail and create a QA workflow)
13
14 automation can be forced using spf_automatedprocesscontrol  with hardcoded memberid (can cause duplication)
15
16 calculations for disinvestment is done on trldisinvestments_V2
17
18 Parent > account > cashflows > memberexitdisinvestment > Multiple Claim Event 2Pot System (to be disinvested as rand) (for your amount) to force disinvestment.[[image:image-20250204120628-1.png]]
19 click select under the disinvest claim event amount for mandated amount
20
21 [[image:image-20250204120642-2.png]]
22
23
24 will then create 2 reports to show disinvestment.
25
26 check on trldisinvestments_V2 for blncompleted switch in process
27
28 Workflow will now move to waiting for switch price.
29
30 (force on test finswitch handles this usually) Accounts > Cashflow unit prices. Find your transactions and set the price(bnid and offer). click confirm on transaction.
31 check on tbldisinvestements_V2 for FinalDis, [[image:image-20250204120959-3.png]]
32
33 If Finaldis is present then the pricing was successful
34
35 Fee: Admin > financial settings > claim event fees. load on parent level
36
37 Tax upload (won't happen on staging): force on staging using SP_ClaimEventTaxUploaded 
38 [[image:image-20250204121400-5.png||height="110" width="376"]]set current dbname in both sps, tax sim simulates a sarsimport
39
40 [[image:image-20250204121703-6.png]]shows success
41
42 Validate payment requisition happens next -  automated
43
44 EFT approval next: simulate on staging: Accounts> BatchEFT Authorisatio n> claim event authorisatiion (creates a workflow Batch payment approval)
45
46 Complete step 1 on workflow
47
48 on step Authorise 1/2  click on [[image:image-20250204121935-7.png]]
49
50 here users check values. user clicks first approve [[image:image-20250204122023-8.png||height="43" width="88"]]
51
52 approve second in sSQL : TMPEFT where fkiMemberID = 'xxx'
53
54 UPDATE tmpEFT
55 set blnBankAuthorised=1
56 where fkiMemberID = @fkimemberID
57 and txtGroup ='Multiple Claim Event'
58 and blnBatchCompleted =0 and blnBatchdeleted =0
59 \\waiting for EFT to be released:
60
61 accounts > payment management 
62 choose banking system > see payment - click on include [[image:image-20250204123925-10.png]]
63
64 now hyphen will pick up OR can be done manually for testing(not doing a real payment) using:
65
66 UPDATE tmpEFT
67 set blnBatchCompleted=1
68 where fkiMemberID = @fkimemberID
69 and txtGroup ='Multiple Claim Event'
70 and blnBatchCompleted =0 and blnBatchdeleted =0
71
72 will generate payment report next using autoclaimdocument service
73
74 [[image:image-20250204124321-11.png]]

Need help?

If you need help with XWiki you can contact: