The lowest level in SAP Workflow architecture seems to be the business object, which is located at the bottom level. In SAP Business Workflow, a Business Object is defined as a collection of methods or events for an entity in a business process. Customer, Material, and Vendor are some of the most common Business Objects in a SAP system. All services are provided in the form of executable methods when Business Objects are used.

A Business Object Repository is an object-oriented approach for modeling Business Objects and Processes. It is a collection of Business Object and Interface types, as well as their associated attributes, methods, and events.

Business processes are at the middle level of the Workflow architecture, defining the steps to be performed as part of the Workflow. The Workflow Builder is used to define business processes.Each work process is referred to as an activity, and it consists of a single step task or the workflow template. Business logic is defined in Business Objects using ABAP code.

The top layer of the SAP Workflow architecture is the organization model. People or groups of people are responsible for taking actions in a Business Workflow in an organizational model. People who are in charge of taking action are referred to as actual agents, and they are defined in the Business Workflows workflow activity.

Using Business Object Builder, you can develop new Business Objects. Events in Business Objects are in charge of both the initial start and the termination of the workflow.Events are also used to trigger the execution of subsequent tasks in the workflow. All tasks defined in the Workflow will be executed in the order specified in the Workflow definition.

Examples of common tasks include

• Release Document
• After Invoice 
• Approval Absence
• Run the Change Material
• Call
• Check the report and Work 

The image below depicts how a task is carried out in SAP Workflow and how it interacts with object types and object methods, organization models, events, and texts.

Components of sap workflow:

Business processes in SAP Workflow are defined in the Workflow Builder. Each step is defined as an activity in the Workflow builder. Each activity defines a single-step task or workflow template.

• Organizational plan
• Workflow builder
• Standard task and events triggering 

Each step throughout the workflow definition can be a task that points to a SAP transaction or decision. A decision may include agent specifications and deadline monitoring for a step. The workflow is initiated either manually or automatically by the system at runtime. In order for the system to initiate a workflow, the workflow definition must include a triggering event.

Whenever an event occurs, the appropriate workflow is initiated automatically. Tasks or work items describe the activities involved and can refer to methods that can be executed automatically or methods that must be executed by a user . Tasks are business objects that are coded in ABAP.

Events are activities that initiate a workflow – one or more workflows at the same time. When the workflow is triggered, the definition flowchart determines when and how work is completed. After that, work items are received and executed in MS Outlook, Lotus Notes, mySAP Workflow MiniApp, or the SAP integrated inbox.

Conversely, the workflow system will send e-mail alerts to any mail system, informing the user that they must log in to the SAP system in order to complete the task. Every work item is assigned to one or more users. When the task is completed, the work item is removed from the inboxes of the other users.

Integration to email systems:

Workflow inboxes are typically populated with executable work items. However, casual SAP users, particularly managers, may forget to check their inbox on a regular basis, so it’s a good idea to set up reminder emails, informing people via a batch job that they have work items in their inbox. Alternatively, an email with a hotlink to the Workflow can be sent directly to their Lotus Notes / Outlook account.All emails are sent out of SAP through SAPConnect, whether they are Workflow notifications, Workflow Workitems, or just a standard SAP Office memo. This provides a one-stop shop for connecting SAP and the mail server.

Transporting workflow items between SAPConnect and the mail server (whether Lotus Notes or Microsoft Outlook) has been made easier by SAP-supplied add-ons that are fully optimized for the different protocols required by each server. Lotus Notes, for example, makes use of a “pipe” known as the MTA, or Message Transfer Agent. This was created in collaboration between SAP and Lotus to provide full integration.

It is important to note that the type of transport medium used is determined by the mail server, not the mail client. In other words, if an employee uses Outlook on their computer but the mail server is a Lotus Domino server, the MTA will be used as a mail gateway. Each workflow background user’s user profile must include an email address.It is important to note that no approval or reply notification from an external mail system will be permitted in other words, external email systems will be unable to respond back to SAP for security reasons.

Creating the sap workflow:

The following are the steps in order to create the workflow. They are:

1.Define Organization Plan  (T-code PPOCE)

This transaction is the most straightforward way to define an organizational plan in the SAP system. You must enter the start date of the Organization unit and then click the Green tick mark, as shown in the screenshot below.

Want to gain knowledge in SAP FICO? Then visit here to learn SAP FICO Training in Marathahalli!

Subscribe to our YouTube channel to get new updates..!

2. Create Workflow template: (T-code PFTC_INS) to create a basic template of workflow,

(T-code SWDD) to build the workflow in the workflow builder

Select the Workflow template in the Task type field. To create tasks: Select Standard Task from the Task type drop-down menu and click Create.

Navigate to T-Code: SWDD to begin building the workflow in the workflow builder.

Step types are different options in the Workflow Builder that you can drag and drop and insert into the Workflow.

3. Define 1st task  (T-code PFTC_INS) (Create notification of absence)

To define the first task, navigate to T-Code: PFTC_INS

Select Standard Task in the Task type field.

Enter the following values and Save the task. Once you save the task, you will get code ID in number 93XXX989

• In the Name field, select Form_created
• In Abbr, select create_form
• In Workitem text, select vik_notif_absence-create
• In Object Type, select FORMABSENC
• In Method field, select CREATE
• Checkbox Synchronous object method, Object method with dialog checked 

4. Add activity > first task in the workflow

You must add an activity to your workflow in place of the undefined step in the Workflow.

As seen in the following screenshot, using T-Code: PFTC_INS, a Task TS99500654 has been created separately.

Step Properties allows you to select various options based on your needs. Select the checkbox – Advance with dialog, as shown in the screenshot above. It demonstrates that the workflow work item is immediately available for processing.

Because we entered WF INITIATOR in Expression under Agents, the person who will initiate the workflow is one of the workitem recipients. There is also a binding option defined that confirms absence notification is not only in this task but also in the workflow – _WI ObjectId &ABSENCEFORM&.

In graphical mode, the Workflow Builder now looks like this:

5. 1st Test in SAP Inbox (T-code SBWP)

Now that the workflow has been executed, workitems such as e-mails are created in the SAP Inbox. When it is executed, it invokes the corresponding task or transaction screen. When you run this workflow, the notification of absence form appears.

To cancel the processing of the first notification, click Cancel. The workflow inbox contains one item for processing – creating an absence notification. Select the workitem and press the Execute button (F8). This will take you back to the “Create notification of absence screen,” where the notification of absence form will be displayed. Fill out the form with your information and save it. The Workitem will be removed from the inbox as a result of this action.

6. Define 2nd task  (Check notification of absence)

Using the object formabsenc-approve, the created form will be sent to the supervisor for approval. Next, use T-Code: PFTC INS to create a new task.

7. Add activity > second task in workflow

Using the task code generated in the previous step, add Task “Check Notification of Absence in the Workflow.”

Define the binding properties as well, as shown in the screenshot below.

8. 2nd Test

The workflow will then be executed, and you will be directed to the workitem for creating notification of absence for processing. This is due to the Advancing with immediate dialog option being selected when creating a task.

Navigate to Business Workplace using the approver’s user-id to see the workitem to process and other attributes to include in the Workitem. Choose Execute after selecting the workitem for checking the notification of absence.

Reject or approve the request. Take note of the two buttons: Accept and Reject.

9. Integrate User Decision for Re-submit

If the approver rejects the leave request, you can also add the user decision to the rejected output. This gives the requester the opportunity to make changes and resubmit the request for approval.

10. 3rd Test

When a request is denied, the next step is for the user to make a decision. Because we specified (&WF INITIATOR&) as the step’s agent, the request will be sent back to us for a decision. You have two choices. Requests should be revised or withdrawn.

11. Define 3rd task  (Revise notification of absence)

For this you need to revise the notification.

12. Add activity > third task to the workflow

To add this step, you have to make the following entries −

Use FORMABSENC-UPDATE as an object.

In the binding option, enter _WI_Object_ID <= &ABSENCEFORM&

In the Agents → add &_WF_INITIATOR& in the expression field

13. Add 4th Customer Task (Send Notification for approval of leave)

To send a notification, you must add a new step called “Send mail.” You must drag this step to the Undefined Step – following the result of the step “Check notification of absence.”

To add this step, you have to make the following entries −

• Select the Recipient type − Enter the Organizational object
• Select Agents → Choose the Expression &_WF_INITIATOR&.
• Enter the subject line as <“Leave Approved”>
• Enter the email text as <“Approved”>

When you press the Enter key, you will be prompted to enter the task’s name and abbreviation. 

Conclusion:

In the above blog post we had clearly explained the in depth of sap workflows, architecture, features and benefits and why to choose the sap workflows. Had any doubts related to this concept drop your queries in the comment section to get them clarified. 

Related Articles

1. SAP Installation

2. SAP cyber security

3. SAP Logistic Execution

4. SAP Master Data