Workflow - Create an event and Create a method

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.

4: Create a method.

Next a method must be created without using any function module template. When creating the method ensure that the method call is synchronous - this means that the method doesn't require a terminating event.

A method can be synchronous or asynchronous. Synchronous Method

Method that, for the duration of its execution, assumes the process control and, after its execution, reports to the calling component (work item manager, in this case).

Synchronous methods can return the following data, if defined: Return parameters, one result and Exceptions.

Terminating events can also be defined for a single-step task described with a synchronous method. At runtime, the relevant work item is then terminated either when the synchronous method is successfully executed or when one of the defined terminating events occurs.

Asynchronous Method

Method that, after its execution, does not report directly to the calling component (work item manager, in this case).

Asynchronous object methods do not return results, parameters or exceptions.

At least one terminating event must be defined for a single-step task described with an asynchronous object method.

At runtime, the relevant work item is only terminated if one of the defined terminating events occurs.

Next set the status of this object type component to implemented. The methods are not implemented unless you once open their program.  Select the method and open its program. It gives a message “Do you want to generate a template automatically for the missing section”. Click “Yes”. Inside the program insert the code “CALL TRANSACTION ‘FB03’. Display Financial Document.

Method:          Z_METHODXX                              

Name:             Method name: XX                        

Description:   Method Description: XX                  

                                                              

Edit ->Change Release Status ->Object Type Component ->Implemented