Академический Документы
Профессиональный Документы
Культура Документы
Take Decision
Check Decision
Approved Rejected
Yeah! Approved
Definition
Workflow: Ex. Material creation Approval Business Object: Ex. Material
Instantiation
Workflow for Material 123 Workflow for Material 456
Decision Decision
Approved Rejected Approved Rejected
Multiple Condition
Case Switch
Loop Fork
Business object types are like an ABAP class. At runtime we instantiate or create runtime objects for any BO based upon the key fields we pass.
Key fields
o The primary key. Ex. Material Number, PO Number, etc.
Attributes
o Other properties of the BO
o If custom attribute is added, then code should be written to fetch the value from a table for that attribute
Methods
o Actions that can be taken on this BO.
o Every method has its own parameters and exceptions
o The parameters have to be explicitly ‘set’ and ‘get’ from the container.
o For custom methods we need to define the parameters and the exceptions
Events
o Notification of particular changes to the BO.
o If custom events are defined, then they need to be triggered at the right point.
Every Business Object has its underlying code in a program which determines the values of attributes when a BO is instantiated.
Delegation
A standard business object can be enhanced. A new Business Object is created with the standard BO as Supertype. As per inheritance, all properties of th
e Supertype are inherited by the new BO. However, the Supertype has to be delegated. This means that we use the name of the standard BO, even thou
gh we can refer to the custom attributes, methods and events of the new Business Object.
Event Rule
Container Container
Data from workflow is sent to task and can be Data from workflow container is received in the While writing a code in method, import and ex
received from task via the container. task container and can be sent back to w port parameters have to be exclusively
orkflow container. ‘get’ and ‘set’ from the method container.
Synchronous or Asynchronous
o Asynchronous indicates that the activity is not complete until a terminating event is received. When asynchronous methods are
executed, workflow does not continue to the next step until it receives an acknowledgement that the method has finished.
o A task that refers to an asynchronous object method must be defined with at least one terminating event. If you define an asynchronous
method, you must ensure that one of the terminating events is triggered after execution of the method.
o At runtime, the relevant work item is only terminated if one of the defined terminating events occurs.
Ex: In a task, a specific order is to be released for billing. In the task, call the (general) method Process order and enter the event billing_
block_deleted as the terminating event.
o Synchronous : At runtime, the relevant work item is generally terminated when the synchronous method has been successfully executed
Ex: The method Display for displaying an object.
Background or Dialog
o Background: Work item that represents a single-step task at runtime whose execution does not require a dialog and, therefore, can be
controlled automatically by the system.
o Dialog: Work item that represents a task at runtime that requires interaction with the user.
o When a dialog work item is executed, the underlying object method of the task is called. The deadlines for executing dialog work items
are monitored.
o A dialog work item is displayed with ready status in the workflow inbox of the Business Workplace. It is removed from the integrated
inboxes of the other agents when the recipient reserves, executes, or processes this work item with other functions