Incoming eMER lost after being accepted.

Summary

The bug that was recently reported was

258154 Incoming eMER accepted lost on acceptance

Client was unable to find eMER in CAMIS or CAMMS after having accepted it.
Provided the details of a record I located that has the licence number the client provided to the requester of the ticket. Client confirmed that they attached the eMER to that file (licence number).
Refer to the “Problem” and “Solution” sections for more details.

Problem:

Business client accepted an incoming eMER.
After the eMER was accepted the eMER appeared to have disappeared. The client could not find it in CAMIS or CAMMS.

Solution:

Through the use of the following query:

select distinct OWNER, TABLE_NAME, COLUMN_NAME
from all_tab_columns
where column_name like '%LICENCE_NUM%'and table_name not like 'V%'
and table_name not like 'MV%'
order by TABLE_NAME asc;

and

YA003_APPLICANT

and an Entity Relationship Diagram that I generated in TOAD for UA006_MEDICAL_EXAMINATION (double click the image to view the file that I exported from TOAD full size or to download it)

I determined that the best tables to check in this situation are:

UA006_MEDICAL_EXAMINATION

Entity Relationship Diagram for UA006_MEDICAL_EXAMINATION

Queries used to locate the record:

located a record in table UA006_MEDICAL_EXAMINATION using the following query:
select * from UA006_MEDICAL_EXAMINATION where LICENCE_NUM = 830084;
query YA003_APPLICANT
select * from UA006_MEDICAL_EXAMINATION where LICENCE_NUM = 830084;

I also performed the following queries. They did not return data for the date provided by the client.

query DATE_CREATED_DATE
query eMER submission date