Scribd
Upload
28 views1 page

New Mic Word Document

Events are occurrences that can trigger changes in workflows and tasks in SAP. Examples include an invoice being entered or a purchase order being released. Events must be defined as object types and can then be used as triggering events to start workflows and tasks or as terminating events to end tasks. Events are created from application programs and can pass information to tasks and workflows. For a workflow or task to use a particular event, that event must be defined in the relevant business object or class.

Uploaded by

Anil Bheemavarapu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
28 views1 page

New Mic Word Document

Events are occurrences that can trigger changes in workflows and tasks in SAP. Examples include an invoice being entered or a purchase order being released. Events must be defined as object types and can then be used as triggering events to start workflows and tasks or as terminating events to end tasks. Events are created from application programs and can pass information to tasks and workflows. For a workflow or task to use a particular event, that event must be defined in the relevant business object or class.

Uploaded by

Anil Bheemavarapu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

SAP Workflow EVENTS

Skip to end of metadata Page restrictions apply Attachments:4 Added by Prabhakar Dharmala, last edited by sachin sharma on Feb 11, 2009 (view change) show comment Go to start of metadata
Unknown macro: {gliffy} Event An occurrence of a change of state in an object, which is published throughout the system. An event is an object type component. The list of possible events is defined with the relevant object type in the Business Object Builder. This list can be extended according to customer requirements using the delegation concept. The actual creation of the events added must be catered for. Events can start, terminate or continue tasks and workflows. Examples of events are:

Invoice entered Purchase order released Triggering Event Event whose occurrence starts a task or a workflow. The event must be entered as a triggering event for the task or workflow that is to be started. The event linkage must be activated. A task or workflow can have several triggering events. Information from the event creation context can be passed in the binding from the event container to the task container or workflow container. The event must be defined as an object type component in the Business Object Builder. Use of the event You use an event in a workflow under the following circumstances

In a task definition or in the version-independent basic data of a workflow as a triggering event. In task definiton as a terminating event.(The task is terminated when ever a event is occured) In version dependent basic data of the workflow. In a workflow defintion for steps of types Event Creator and Wait for event. A event is created from any application program. Multiple receivers are possible for a event. When ever you want to use a event in your workflow then that particular event must be defined in the appropriate Business Object (Object Type) or in the Business Class (ABAP classes that are supported by workflows). Start Workflow by Triggering a event You can start a workflow when a event is triggered by specifying the business object and its associated event in the basic data of the workflow. In the Basic data of the workflow we can even specify the name of the class and its related event as the triggering event.

You might also like