Delete Community Practice Data

Objectives

Remove practice transactions for a community. This process will also remove practice residents and update operator codes for post-go-live.

Prerequisites

Knowledge of community being centrally or remotely hosted

Access to fc_obj_owner schema on database where data is located

Access to fc_obj_admin schema

Date of community go-live

Names of practice residents to be removed

Instructions

1. Open J:\FullCount\FC - Implementations\Templates - Development\FullCount Practice Data.xlsx.
2. Do a File Save As and save to the community's implemenation folder. This is where we will store the data that we are removing from the system as backup.
3. Download script delete_community_practice_data.txt from http://sourcecontrol.fullcount.net/repos/database/trunk/processes/implementation/delete_community_practice_data.txt
4. Open script using SQLDeveloper or similar software.
5. Open connection to database using fc_obj_owner user.
6. Update community id with the community id of the community having transactions removed for. You can use the query on line 4 to help find the community id. This can be done via Find and Replace.
7. Update date with the date the transactions are being deleted prior to. Ex. - If I wanted to remove all transactions prior to 2/1/2015, I would replace the existing date in the file with 02/01/15. This would remove anything prior to that date, but not anything on that date. This can be done via Find and Replace.
8. For each 'Select' statment, copy and paste the results into the corresponding tab in the template. Note: Some queries may return no rows. For example, a community not taking forms of payment will not have any rows in the PAYMENTS table.
9. Save the Excel spreadsheet template.
10. Run through each 'Delete' statement on the script. After each statment, run a commit to the database. Note: Some statements may remove no rows. For example, a community not taking forms of payment will not remove any rows from the PAYMENTS table. The order items statement may be skipped on central as it currently takes a long time to execute. The orders statement only removes open orders, also due to long execution time to delete all orders.
11. Run the update statements on user_profiles to update implementer operator codes to their post go-live values.
12. Confirm that no duplicate pos operator codes were created by running the select statement below the update statements. If there are duplicates, manually change in back office.
13. Commit to the database.
14. Log into the back office for the community and remove any practice residents/accounts provided by the implementer. This is optional and may not be provided.
15. If the community is utilizing resident portal and remotely hosted, set ENABLE_RP to YES on the COMMUNITY_CONFIG table for the community id of the community.
16. Update implemented date in Tracker if it is not already populated.
17. Communicate with the implementer that the practice transactions have been removed.