Since Siamease generates accessible ABAP code, and has its own Object Class and methods, developers can embed solutions into user exits.

Code can also be executed via BTE, substitution, BADI's or even by a simple transaction code. This allows business oriented solutions to be automated automatically when users capture specific data.

E.G. The finance department may wish to charge a levy if a payment is paid late. The transaction capturing a late payment could trigger a Siamease that will post a financial journal to post the levy. The financial journal would be defined by the business analyst, since they know what must be posted, whilst the developers need only determine where to embed the solution.