A stereotype indicates to Agile Business Suite how a class should be interpreted. Stereotyped classes generally have framework methods that are automatically executed at runtime, and particular behaviors, like a report’s ability to destroy itself at the end of its processing cycle. A Class with no stereotype has none of these built-in characteristics.

Because they have no framework methods, their logic is not automatically executed at runtime. You can add methods to a Class with no stereotype, but you must then invoke these methods from logic that is executed.

You would use a Class with no stereotype when the built-in behavior of the stereotyped classes is not necessary or appropriate. This enables you to avoid the segment cycle, including automatic lookups and automatic database updates.

Before adding classes with no stereotype to your model, you should read more information in the Agile Business Suite Developer Online Help.