When you load a database dump that was created in an earlier version than the current SAP ASE, you are not required to perform the pre-upgrade tasks before loading the dump. Therefore, you do not receive any notification if the compiled objects in your database dump are missing their source text.
After loading a database dump, run sp_checksource to verify the existence of the source text for all compiled objects in the database. Then, you can allow the compiled objects to be upgraded as they are executed, or you can run dbcc upgrade_object to find potential problems and upgrade objects manually.
See the Reference Manual: Procedures.
Look at the sysprocedures.version column. If the object was upgraded, this column contains the number 15000 for any 15.x version of SAP ASE.
If you are upgrading to a 64-bit pointer size in the same version, look at the sysprocedures.status column. If the object has been upgraded, and is using 64-bit pointers, this column contains a hexadecimal bit setting of 0x2 to indicate that the object uses 64-bit pointers. If this bit is not set, it indicates the object is still a 32-bit object, and has not been upgraded.