Functionality of OM statuses Active, Planned Submitted Approved & Rejected
I want to understand the functionality & concept of the statuses in Tx PO13, PO10 etc
my question is regarding a requirement.
We need if some object is created that should be submitted for approval and in this case e-mails shud be triggered for approval to superiors. Once that is approved the created object shud exist as a valid object in system, otherwise should exist in system but not as an active object and cannot not be used for assigning holders. I mean should not be a valid object.
I want to know if these statuses will help doing it with work-flows and can we restrict the user to use only one of the five statuses..
Pls advise ...