Post Cloning Setups (After Each Clone)

There are numerous post cloning activities that are performed on an instance taken from the production copy. Below are the specific steps we used to enable email events and the use of a generic email account.

1. Update wf_notifications
set status = 'CLOSED',mail_status = 'SENT',end_date = sysdate;

2. Update fnd_user
set email_address = 'TestOracle@yourdomain.com ';

3. Update per_people_f
set email_address = 'TestOracle@yourdomain.com ';

4. Update po_vendor_sites_all =
email_address = 'TestOracle@yourdomain.com',remittance_email = 'TestOracle@yourdomain.com';

5. Purge Workflow data :
Run the "Purge Obsolete Workflow Runtime Data" concurrent program

6. If test usernames are implemented, re-enable these accounts with the following code snippet:

UPDATE apps.fnd_user
SET last_update_date = SYSDATE, -- set update date
last_updated_by = -1, -- set to ANONYMOUS
password_accesses_left = NULL,
password_lifespan_accesses = NULL,
password_lifespan_days = NULL,
end_date = NULL -- activate user account
WHERE user_name = 'TEST_APPROVER I'
OR user_name = 'TEST_APPROVER II'
OR user_name = 'TEST_APPROVER III'
OR user_name = 'TEST_BUYER'
OR user_name = 'TEST_REQ'

7. Alerts can be selectively disabled or changed based on your preferences and the type of alert.