I’m learning the SAP business workflow these days for my next project. I didn’t develop any SAP business workflow before in the real project and just have some basic concept of it. In order to help myself as well as other SAP workflow beginner to learn it, I divided the whole monster into below pieces. There are many roles involved into the SAP business workflow – process consultant, developer, administrator and end user. People doesn’t need to become the expert in all these components and just the components used in your daily work will be sufficient.
I will try to explain each component. Please correct me if I was wrong. I’m also the freshman to this area.:-)
Read more…
There are several ways to start the tasks and workflows. Starting workflows manually means that the workflow is not started by a triggering event but manually. It is irrelevant whether triggering events are defined for the workflow.
Note: you can only start workflow manually if you are entered as a possible agent or the workflow template is marked as the ‘General Task’.
Step 1. Set all the involved task to ‘General Task’ to allow all the users to be the possible agents.
Read more…
SAP Object Type is the object-oriented modeling of business objects such as sales order, customer, vendor. All these Object Types are stored in BOR (Business Object Repository) which acts as the central repository for all the object type definition. BAPIs are defined as methods of SAP business object types (or SAP interface types). The Object Type is also the foundation of SAP business workflow.
Below is a great tutorial on how to create a custom object type in BOR step-by-step. I finished this guide today and found it is quite useful. I would like to share it with my blog audiences.
Tutorial: Workflow Programming
An event is created from any application program and published system-wide. Any number of receivers can react to the event. For example, the create event of sales order may trigger an approval workflow. Events that you want to use must be defined as components of an object type. Events are published without the creating application knowing whether a receiver reacts to them. The event manager checks whether there are active linkages for the published event.
There are many ways to publish an event to the system. In this post, I will introduce how to create event using ABAP program. An event can be created from any program by calling the function module SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT.
Note that events say something about object status changes that have actually occurred. Therefore ensure that the event is not created until the relevant status change has taken place. For this, the function module for creating an event should be called in the same logical unit of work (LUW) as the one in which the status change is made.
Function module SWE_EVENT_CREATE has the following interface:
| Import parameters |
| OBJTYPE |
SWETYPECOU-OBJTYPE |
Type of the triggering object. |
| OBJKEY |
SWEINSTCOU-OBJKEY |
Concatenated, object type-specific key of the triggering object.
The reference to the triggering object is created internally from this information and written to the event container under the element ID _Evt_Object. |
| EVENT |
SWETYPECOU-EVENT |
ID of the event.
The event must be defined for the triggering object type. |
| Export parameters |
| EVENT_ID |
SWEDUMEVID-EVTID |
The event number has a value other than zero if the event manager could establish one or more receiver function modules. |
| Table parameters |
| EVENT_CONTAINER |
SWCONT |
Persistent event container of the event.
You only pass the event container if you have defined event parameters in addition to the predefined elements. The container you pass to the function module is filled with the relevant data in the event-creating application and then contains only the event parameters you defined.
When the function module is executed, the predefined elements (object reference, creation time, creator, and so on) are added to the event container. |
Read more…