User Tools

Site Tools


faq:bank_rec:reattatch

It should be noted that this process should be used at your discression, and is not a normal fix to the problem of a transaction not being attached to the appropriate bank rec. The normal fix is to remove and re-do all bank recs back to when this happened. This is as per programming. The idea is that hopefully the damage is in the previous bank rec so you can just delete the current bank rec and re-open the previous bank rec.

Note: Since there are security measures in place that prevent you from deleting the line off of the old bank rec the old bank recs should not be damaged unless done on purpose. It might be a good idea to report any holes that allow accidental removal of a cleared transaction from an old bank rec. Report these as incidents.

  • Step1: Create New entry with same dates
  • Unordered List Item
  • Step2: Get GL Line Unique ID for trandata query
  • Step3: Clear this Item on the new bank rec
  • Step4: Open Pervasive and open the BankRecH table.
  • Step5: Find the current Bank Rec record and its BRH_Unique (Normally with Highest BRH_Unique number). Confirm by checking Account, Department, and Dates etc.
  • Step6: Fin the Bank Rec Record you are trying to attatch to and its BRH_Unique. Confirm by checking the corresponding fields
  • Step7: Use the query below to view the detailed Bank Rec Record. Remember to use the positive and negative versions of the TrandataUnique
  • SELECT * FROM “BankRecD” where TrandataUnique = 64 or TrandataUnique = -64
  • Step8: The value in the BankRecUnique should correspond to BRH_Unique value on the Current Bank Rec (From the BankRecH table)
  • Step9: Change the value to the BRH_Unique of the Bank Rec you are trying to attatch this transaction to.
  • Step10: re-load the bank rec you are trying to fix, and confirm that it's value has changed by the amount of this transaction.
faq/bank_rec/reattatch.txt · Last modified: 2009/06/09 16:36 (15 years ago) by cliff