Brief Overview of SAP Business Workflow Terminology.
There are certain primary terms which are of utmost importance
for you to get started with workflows. Throughout the lesson, we shall
describe these terms in the light of the leave application approval
procedure that we have discussed earlier. Please note that leave
application approval is henceforth referred as “Notification of
absence”.
EVENT: An event represents an action in the system. For example, “Creating Absence Notification” is an ACTION. For this action the SAP Application creates an event. This event in turn triggers a workflow.
OBJECT: Workflow routes the document among different persons. Each person performs certain activities. Whatever goal the workflow is intended to achieve, can be put inside an object type. Consider an Object as a Structure ( Abstract Enclosure ) with certain data and some logic. For example, there is a standard object type called FORMABSENC in SAP. This is used for the notification of leave. It has certain data and some logic. If you are familiar with Object Oriented Programming then this concept will be pretty familiar and straight forward.
Data
– KEY ( Absence Notification Number )
– ATTRIBUTES (Created By , Entered on , Status etc )
Logic
– METHODS ( Create, Approve etc )
-EVENTS ( Created, Deleted etc )
An OBJECT is a specific instance of the OBJECT TYPE. So, if an user created a Leave Application Form Object of type FORMABSENC , an instance with a unique number ( say 100001 ) is created.
TASK: An SAP workflow task represents an activity. It serves a purpose here. Some examples of tasks are Revise Absence Notification, Approve Absence Notification etc. The task Approve Absence Notification performs a business function – Submits the relevant absence notification form to the manager and on approval , it changes the status of the form to Approved and so on. How does it perform this function ? It follows the logic created inside the method of an object type. So , in simple terms, a workflow TASK refers to the method of an object type.
BUSINESS WORKPLACE & WORKITEM: Business Workplace is a work area that an SAP user can use to carry out business Processes. For example, the business workplace of an user could be his inbox. Let us take the example of the absence notification again. The employee submits the notification to his manager. The manager receives the request in his inbox to approve the absence notification. The manager opens it , checks the details and approves the same. The request that the manager receives in this inbox is called a WORK ITEM. In technical terms, a work item is a run time request of a task in real time. Inbox contains not just the work items – it may as well contain simple text message. Examples include Notification messages, that need not be acted upon and are just used to inform the owner.
AGENT: An Agent is a person who executes a work item. In our example, manager Mr. John is the agent of the workflow task ‘approve absence notification.
STEP: Steps are the building blocks of a workflow. In other words, a workflow consists of steps arranged in a sequence. A step in general refers to a business activity. A step can therefore refer to an activity where it refers to a task. Eg., a step is created that refers to the task of approving absence notification or a user decision where the receiver of the notification has to decide on an „Approval‟ or a „Rejection‟ or a document from a template where a document can be edited from within a workflow. Steps can also refer to other programmatic conditions like loops, conditions, forks ( creation of a child process ) etc.
RULE: As discussed earlier, in the workflow task, as a responsible agent, we need to mention the name of the person who should execute the work item of approving absence notification. This method of specifying directly, the user name or job or position is called fixed agent assignment. But in some cases, we may want to determine the agent at run time, i.e when the workflow task is actually executed.
Then, instead of specifying the manager’s name, we specify a RULE ‘superior of workflow initiator’. What does this rule perform?
It takes the employee as input, refers to the organizational plan,checks who the superior of the employee is, at that point in time, and sends the work item to his inbox. This method is called RULE RESOLUTION.
WORKFLOW:
Lets summarize the term SAP workflow and how these key terms are linked together.
1. Workflow engine automates business processes.
2. Workflow can be triggered by an event.
3. Workflow definition consists of a sequence of steps.
4. Each step can be an activity which is nothing but a task.
5. Task in turn refers to a method of a workflow to implement a specific logic.
6. Steps can also refer to user decision, and other programattic controls.
7. Runtime reprsentation of the step is called a work item.
8. This work item sits in the inbox(business workplace) of the responsible agent assigned to the step.
9. Agent determination can make use of Rule.
In large business applications this concept of delegation plays a vital role considering its high level of re-usability brings reduction in coding procedures as well as in testing or maintenance and in turn increases savings.
Delegation is a pre-requisite for redefinition.
[detailed article on https://wiki.scn.sap.com/wiki/display/ABAP/Delegation+and+Redefining+methods+of+business+object+BUS1001?preview=/https%3A%2F%2Fwiki.sdn.sap.com%2Fwiki%2Fdownload%2Fattachments%2F43680%2FDAVE_PART1_13.jpg]
GUYS PLEASE LEARN THE BINDING CONCEPT BECAUSE IT IS VERY IMPORTANT IN TERMS OF SAP WORKFLOW.
Workflow Terminology
SAP Work-flow :
It's would be simple to understand workflow , if you have the knowledge of this things in minds,
these things will help you solve industry's biggest challenge in terms of designing workflow.
There are sites like SAPTECHINCLWEBSITE that has most tutorial and practical examples but it still doesn't have that contents so that a beginner can understand workflow very easily and be familiar with terms of workflow.
EVENT: An event represents an action in the system. For example, “Creating Absence Notification” is an ACTION. For this action the SAP Application creates an event. This event in turn triggers a workflow.
OBJECT: Workflow routes the document among different persons. Each person performs certain activities. Whatever goal the workflow is intended to achieve, can be put inside an object type. Consider an Object as a Structure ( Abstract Enclosure ) with certain data and some logic. For example, there is a standard object type called FORMABSENC in SAP. This is used for the notification of leave. It has certain data and some logic. If you are familiar with Object Oriented Programming then this concept will be pretty familiar and straight forward.
Data
– KEY ( Absence Notification Number )
– ATTRIBUTES (Created By , Entered on , Status etc )
Logic
– METHODS ( Create, Approve etc )
-EVENTS ( Created, Deleted etc )
An OBJECT is a specific instance of the OBJECT TYPE. So, if an user created a Leave Application Form Object of type FORMABSENC , an instance with a unique number ( say 100001 ) is created.
TASK: An SAP workflow task represents an activity. It serves a purpose here. Some examples of tasks are Revise Absence Notification, Approve Absence Notification etc. The task Approve Absence Notification performs a business function – Submits the relevant absence notification form to the manager and on approval , it changes the status of the form to Approved and so on. How does it perform this function ? It follows the logic created inside the method of an object type. So , in simple terms, a workflow TASK refers to the method of an object type.
BUSINESS WORKPLACE & WORKITEM: Business Workplace is a work area that an SAP user can use to carry out business Processes. For example, the business workplace of an user could be his inbox. Let us take the example of the absence notification again. The employee submits the notification to his manager. The manager receives the request in his inbox to approve the absence notification. The manager opens it , checks the details and approves the same. The request that the manager receives in this inbox is called a WORK ITEM. In technical terms, a work item is a run time request of a task in real time. Inbox contains not just the work items – it may as well contain simple text message. Examples include Notification messages, that need not be acted upon and are just used to inform the owner.
AGENT: An Agent is a person who executes a work item. In our example, manager Mr. John is the agent of the workflow task ‘approve absence notification.
- Possible agent is the person who is eligible to execute the work item. The name of the possible agent is mentioned in the workflow task.
- Responsible agent is the person who should execute the work item, or who is responsible for acting on the work item.Name of the responsible agent is mentioned in the workflow step.
- Excluded agent is the person who should not execute the work item,
name of the excluded agent is mentioned in the workflow step.John is a
manager at the Southern Zone of an organization. Any manager can execute
the task „approve absence notification‟ in general. Meaning all the
managers have the expertise, authority and eligibility to execute the
task of approving. They are the possible agents who can execute the
task. Hence, in the task, we mention the job ‘manager’ as the possible
agent. This applies to all the managers in general.
But, it is not a good idea to send the request for approving absence notification to all the managers. We have to select one responsible person, who should act on it. So, in the workflow step, we specifically mention the name of the manager ‘John’. He is called the responsible agent.
There might be a requirement that managers of Northern Zone only should not be able to check/approve the absence notification. In that case we mention the job ‘Manager – Northern Zone’ as the excluded agent of the workflow step.
Hence, the system sends the work item to the responsible agent who is also the possible agent and not the excluded agent. In this example, the system sends the work item to John who is also the manager and not the northern zone manager.
STEP: Steps are the building blocks of a workflow. In other words, a workflow consists of steps arranged in a sequence. A step in general refers to a business activity. A step can therefore refer to an activity where it refers to a task. Eg., a step is created that refers to the task of approving absence notification or a user decision where the receiver of the notification has to decide on an „Approval‟ or a „Rejection‟ or a document from a template where a document can be edited from within a workflow. Steps can also refer to other programmatic conditions like loops, conditions, forks ( creation of a child process ) etc.
RULE: As discussed earlier, in the workflow task, as a responsible agent, we need to mention the name of the person who should execute the work item of approving absence notification. This method of specifying directly, the user name or job or position is called fixed agent assignment. But in some cases, we may want to determine the agent at run time, i.e when the workflow task is actually executed.
Then, instead of specifying the manager’s name, we specify a RULE ‘superior of workflow initiator’. What does this rule perform?
It takes the employee as input, refers to the organizational plan,checks who the superior of the employee is, at that point in time, and sends the work item to his inbox. This method is called RULE RESOLUTION.
WORKFLOW:
Lets summarize the term SAP workflow and how these key terms are linked together.
1. Workflow engine automates business processes.
2. Workflow can be triggered by an event.
3. Workflow definition consists of a sequence of steps.
4. Each step can be an activity which is nothing but a task.
5. Task in turn refers to a method of a workflow to implement a specific logic.
6. Steps can also refer to user decision, and other programattic controls.
7. Runtime reprsentation of the step is called a work item.
8. This work item sits in the inbox(business workplace) of the responsible agent assigned to the step.
9. Agent determination can make use of Rule.
Delegation allows a subtype to use its own defined methods as well as the original inherited methods from the standard business object.
This is very important in terms of business aspect as it allows us to customize our standard business applications effectively and improves the performance by means of re-usability.In large business applications this concept of delegation plays a vital role considering its high level of re-usability brings reduction in coding procedures as well as in testing or maintenance and in turn increases savings.
- Redefinition:
Delegation is a pre-requisite for redefinition.
[detailed article on https://wiki.scn.sap.com/wiki/display/ABAP/Delegation+and+Redefining+methods+of+business+object+BUS1001?preview=/https%3A%2F%2Fwiki.sdn.sap.com%2Fwiki%2Fdownload%2Fattachments%2F43680%2FDAVE_PART1_13.jpg]
GUYS PLEASE LEARN THE BINDING CONCEPT BECAUSE IT IS VERY IMPORTANT IN TERMS OF SAP WORKFLOW.
