How does Toad for Oracle handle Toad objects during migration to Oracle Applications Tablespace M (4269836)

How does Toad for Oracle handle Toad objects during migration OATM model in Oracle?   Since it is a new standard, customers that have installed older versions need to use a utility to migrate database to new model (to new tablespaces).

This utility handles Oracle objects but there is no information concerning third party objects : toad objects in this case.   Users have found objects belonging to TOAD user, and reside in "users" tablespace :
owner : TOAD
objects : TOAD_PLAN_SQL, TOAD_PLAN_PLAN (tables)

In addition, they have also found objects (quest related) in ABMD tablespace :
owner OEMMGR
objects : QUEST_COM_PRODUCTS, QUEST_COM_PRODUCTS_USED_BY, QUEST_COM_PRODUCT_PRIVS, QUEST_COM_USERS, QUEST_COM_USER_PRIVILEGES

OEMMGR is the Oracle owner for Oracle Enterprise Manager.

"Users" tablespace is not a tablespace used by Oracle E-Business Suite.

What has to be done with these objects?

There are no  additional tasks  to be done with the Quest created objects.   Optionally, the objects can be moved to another tablespace.   It does not matter which option is chosen.

OATM stands for Oracle Applications Tablespace Model.   It is the new tablespace model for Oracle E-Business Suite. Default tablespace model with all new Oracle applications fresh install ( starting with db 10g).   This OATM tablespace model is mandatory for Oracle E-Business Suite Version 12.   Since it is a new standard, customers that have installed older versions need to use a utility to migrate database to new model (to new tablespaces).