Are you talking about all these tables?

krns_adhoc_rte_actn_recip_t
krns_att_t
krns_doc_hdr_t
krns_doc_typ_attr_s
krns_lock_s
krns_lookup_rslt_s
krns_lookup_rslt_t
krns_lookup_sel_t
krns_maint_doc_att_lst_t
krns_maint_doc_att_s
krns_maint_doc_att_t
krns_maint_doc_t
krns_maint_lock_s
krns_maint_lock_t
krns_nte_s
krns_nte_t
krns_nte_typ_t
krns_pessimistic_lock_t
krns_sesn_doc_t

For the analysis we need to do the following:

1. Determine which tables are candidates for the change
2. Analyze how tables are used and which tables will be deprecated for KRAD
3. Ask Jerry to confirm results

I started an analysis document: https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AqGzZp-mOGfNdEdSUzdRYXVCa3BubkZ6eWxScEJtSUE#gid=0

Analysis Notes:

1. In general, most tables are renamed from krns_ to krad_
2. We can safely drop krns_doc_typ_attr_s as it is unused
3. krns_lookup_rslt_s will remain the same as it is deprecated
4. krns_lookup_rslt_t and krns_lookup_sel_t will remain the same as they are deprecated, but there are some accidental references in KRAD, so those need to be removed
5. krns_sesn_doc_t will remain the same as it is deprecated, and the code will be removed as per KULRICE-10178

Jerry has confirmed these results so we should be good to go on the implementation.

We're adding another table that goes along with the krns_nte_t and krns_att_t tables. It is named krns_att_cntnt_t and it will be used with an optional implementation of the attachment framework which will store attachments in the database instead of the filesystem (See KULRICE-12444).