Workflow Step 3 : Create an event.

Open the Object type in change mode. When you change your subtype the first step is to create a new event, this is done by selecting the Event node and clicking the create button. Give the event a name and a description. Next set the status of this object type component to implemented.

Event: Z_EVENT_XX
Name: Event name: XX
Description: Event Description: XX


Click on the new event and…

Edit à Change Release Status à Object Type Component à Implemented
(A small box sign vanishes from the right side of the event, indicating that it is implemented)
There can be multiple triggering events for a standard/customer task.

In R/3 4.0 the release strategy for new Object Types and Object Type Components (methods, attributes, events, etc.) was enhanced. Now when an object type and/or components are created, there are different statuses to select, based on its required purpose. The statuses are:


· Modeled - objects cannot be accessed at runtime. This is the status that is automatically set when an object type or component is created. Items with a modeled status cannot be referenced in any type of workflow task.

· Implemented - objects can be used internally in a test environment. They are accessible, but may not be stable (especially if no delegation has been defined).

· Released - objects are ready for production. Note: Local objects cannot be released.

· Obsolete - objects are typically replaced by new functionality or incompatible with previous versions. This status is optional.

Related Link :

Step 1 : http://www.abapcode.info/2008/12/work-flow-for-beginners-step1.html

Step 2 : WorkFlow Step2 : Create a business object