Status management Hi Jennie, Transaction BSVX is for system statuses, and transaction BSVZ is for user-defined statuses. With user status BSVZ a profile is required, which you will have anyway when you set up the user-statuses in the IMG. To maintain BSVZ add the status object type from the object status screen in the transaction (which for sales order items is VBP). The business object type should be dependant on the scenario, BUS2032 for sales orders, BUS2095/34 for contracts. In the second level of BSVZ, status restrictions, you can ignore the system status field. Add the user status you want an event generated for. Things to watch out for: Although you select the user-status name, the internal number for that status will be inserted. This internal number will change every time the user-statuses are redefined in the IMG. Also, the inactive flag determines that the event will be generated when the status is changed FROM that status. To manipulate user statuses in your workflow at runtime, use the methods included with interface IFSTATUS. Hope this helps Regards Philip Kisloff Deloitte Consulting Oberwil-CH

[Philip Kisloff]

______________________________ Reply Separator _________________________________
Subject: Status management
Author:  "Chen; Jennie" <SMTP:xacchenj at ti.com> at US
Date:    06/06/00 13:13
 
 
Hi, friends,
 
I will use Status management to control Event creation.
I never do this before, so can you give me some advice?
For example, what tables and function modules related to Staus management,
what configurations need to be done and what else I need to know?
 
Thanks and best regards,
Jennie