_WI_OBJECT_ID Vs _WI_GROUP_ID
Hi
Can any one tell me what is the difference between WIOBJECT_ID and WIGROUP_ID.
Can I put WIGROUP_ID instead of WIOBJECT_ID after binding to a particular BO?
Please give me an example where I can use WIOBJECT_ID and where WIGROUP_ID.
Thanks in advance.
Regards,
Sucheta
Hello,
WF ZBusObj -> TASK &_WI_OBJECT_ID&
This is what you do for the main object of the workflow, the one that it is based on (e.g. the BOR object of the starting event)
WF ZBusObj -> TASK ZBusObj
This is for when you want to bind in additional objects. You can also use it for the main object.
regards
Rick Bakker
hanabi technology
Similar Messages
-
Unable to Open Inbox in SBWP - runtime error
Hi Gurus,
I have a problem with my inbox - I'm experiencing runtime error (time_out) when opening it. It says 'Time limit exceeded', and 'The program 'SAPFSSO0' has exceeded the maximum permitted runtime without interruption and has therefore been terminated.
Can anyone of the Workflow experts tell me what is the probable cause, and what do you sugggest to solve this and prevent from happening again?
Thanks!
Regards,
JoyreenThis may or may not solve your problem but gives you an idea on performance of SBWP.
Check the Note 764707 - Performance in Business Workplace
This note describes the factors that affect the performance in the Business Workplace, and ways in which you can improve the performance:
The performance in the workflow inbox depends on several factors:
1. Use of organizational objects (O, S ...) for tasks
If agent assignment for tasks is controlled using organizational objects, a structural explosion is necessary. Complex organizational structures can mean that the time required to construct the inbox is greater. This is carried out once a day for each user when the user logs on initially, and the information is then buffered. As a result, the initial construction of the inbox takes the most time.
2. Number of work items in the system
The time required for selecting work items for a user increases with the number of work items that exist in the system.
3. Number of work items that are displayed in the workflow inbox or in the subordinate views.
4. Use of dynamic columns
The dynamic columns are filled on a task-specific basis with content that is determined dynamically during runtime. To do this, it is necessary for the system to read the work item container and then to determine the attributes to be displayed, for example, of an business object.
Displaying the dynamic columns greatly affects performance, since the system accesses both the work item container and application tables.
5. Grouping according to contents, content type and sort key
Each work item carries the two container elements WIObject_ID (dominant object) and WIGroup_ID (Grouping characteristic) to its container. Both elements are defined so that an object reference can be included.
Grouping according to content and content type is based on the container element WIObject_ID, and grouping according to sort key is based on WIGroup_ID. For each of these grouping types, the system needs to access the container for each work item to read the object reference. In addition, the system must determine the default attribute of the respective object, which involves accessing the application tables.
6. Showing the columns group object and work item contents
As above, showing the two columns is based on the container elements WIObject_ID and WIGroup_ID. The system determines the values to be shown by reading the work item container and the default attribute of the relevant object.
Solution
1. Detail the assignment of tasks in the organizational model.
2. Archive work items that are no longer needed (see Note 49545).
3. In the Business Workplace, BAdIs are available for the following purposes:
a) WF_BWP_SELECT_FILTER
This BAdI enables you to limit the number of the work items displayed by filtering. It is mainly suited to scenarios where all users are working on the same inventory of work items (for example, call center).
(see Note 765783)
b) WF_BWP_DYN_COLUMN
Hiding the dynamic columns improves performance in the Business Workplace.
If this is not possible, you can implement the BAdI WF_BWP_DYN_COLUMN to determine the values of the dynamic columns directly from the application data. The BAdI is available with Note 848382.
c) WF_BWP_OBJ_ATTRIBUTE
With this BAdI, it is possible to set the default attributes of the dominant object (_WI_Object_ID) and the grouping characteristic (_WI_Group_ID). The default attributes are used for grouping according to content, and grouping according to sort key and for hiding the group object column and work item content.
The BAdI is available with Note 848382.
4. It is also advisable to implement Note 848382 (or one of the corresponding Support Packages) if you do not want to implement either of the BAdIs. The note also contains an optimization that affects the determination of the object references in the container elements WIObject_ID and WIGroup_ID.
Header Data
Regards,
PR. -
Rule with SELFITEM-SENDTASKDESCRITION task's workitem goes error
Dear all,
I have created a workflow with an activity step that uses business object SELFITEM and method SENDTASKDESCRIPTION with rule AC00000168.
On executing the WF, the workitem successfully goes to right agent.
But, when the agent executes the workitem, it goes to error state.
In the workflow log, I get the error message as "Exception occurred Error handling for work item 000000968991 eeom division 09.07.2010 - 11:28:52 " with exception 0,error type 1 and message 0.
Following is binding details between workflow and task container.
&MANAGER& -> &ADDRESSSTRINGS&
&_ATTACH_OBJECTS& -> &ATTACHMENTS&
&ATTENDANCEINSTANCE& -> &ATTENDANCE&
&EXPRESS& -> &EXPRESS&
&LANGUAGE& -> &LANGUAGE&
&LINEWIDTH& -> &LINEWIDTH&
&TYPEID& -> &TYPEID&
&SELFITEM& -> &_WI_OBJECT_ID&
In the above binding parameter,MANAGER. is a workflow container of ABAP data dictionary type WFSYST-AGENT where the rule's agent is collected.
Please suggest why the work item at agent inbox on execution goes error for which I will be grateful.
Thanks and regards,
S.SureshHello Rick !
Thank you so much for your fruitful solution.
Also, I am deeply sorry for delayed reply.
I used the function module 'SWX_GET_MANAGER' in the custom method as you suggested.
BEGIN_METHOD FINDMANAGER CHANGING CONTAINER.
DATA:
EXTENDEDOBJECTID TYPE OBJEC-REALO,
addresstype like soxna-type,
RECIPIENTADDRESS TYPE SOXNA-FULLNAME.
DATA:
ac_container like swcont occurs 0 with
addressstrings like soxna-fullname occu
SWC_GET_ELEMENT CONTAINER 'ExtendedObjectID
addresstype = 'G'.
ac_container-element = 'OBJID'.
ac_container-tab_index = '000001'.
ac_container-elemlength = '008'.
ac_container-type = 'N'.
ac_container-value = EXTENDEDOBJECTID.
append ac_container.
ac_container-element = 'OTYPE'.
ac_container-tab_index = '000001'.
ac_container-elemlength = '002'.
ac_container-type = 'C'.
ac_container-value = 'P '.
append ac_container.
CALL FUNCTION 'SWX_GET_MANAGER'
TABLES
ACTOR_TAB = addressstrings
AC_CONTAINER = ac_container
EXCEPTIONS
NOBODY_FOUND = 01
OTHERS = 02.
CASE SY-SUBRC.
WHEN 0. " OK
WHEN 01. " to be implemented
WHEN OTHERS. " to be implemented
ENDCASE.
loop at addressstrings.
if addressstrings(2) = 'P '.
delete addressstrings.
endif.
endloop.
move addressstrings to recipientaddress.
SWC_SET_ELEMENT CONTAINER 'RecipientAddress' RECIPIENTADDRESS.
END_METHOD.
Therafter, the values accumulated at RECIPIENTADDRESS is passed to the workflow container(SOXNA-FULLNAME) of SENDMAIL step.
Also, I thank every one who contributed fruitful suggestions to solve my problem.
Thanks and regards,
S.Suresh -
Values from Structure used in Form to be transferred to a Business Object
Hello,
I have defined a structure (zcsks) in the workflow container. This structure is used in two forms (Change and Approve).
With the approval (button pressed on approve form) the data entered in the structure zcsks has to be transferred to the business object ZBUS0012 in the workflow container, so that the business object method CREATE can be executed automatically.
The values for the structure ZCSKS is already transferred from the form to the workflow container automatically.
My question now is how I can transfer values from ZCSKS to ZBUS0012 and execute its method CREATE automatically ?
Thank you in advance!Hello,
"Value of expression '&_WI_OBJECT_ID.COSTCENTER&' cannot be used as the target of an assignment"
This is because you are trying to assign a value to an attribute of the main object of a workflow (_WI_OBJECT_ID).
That won't work. I thought you meant you had an object in the workflow container and wanted to
instantiate that.
When the workflow is created the main object is already instantiated so you can't change it.
regards
Rick Bakker
Hanabi Technology -
How To Add Line Items to Workflow Document Template
Hi Gurus,
ive made a Workflow which has few containers referencing VBKPF, VBSEGS, and constructed two methods which one of them gets the table VBKPF data into MyStructure and the second the data into MyStructure2.
Inside of the workflow i made two container operations and assigned those two methods to VBKPF and VBSEGS containers.
The Problem is that VBSEGS is a (multi) line item table and it doesnt show me the data inside of the document template.
What could be the solution for this scenario
Thanks, Points for RewardHi,
i checked the swo1 methods and it looks good. I didnt change the binding that ive implemented, and some values are getting showed, but still they do not correspond to the BO element (concerning Acct.Doc.Nr)
My binding is:
Display Document Task:
#######Workflow -> Step Display Parked Doc
**************BO FIPP -> &_WI_OBJECT_ID&
#######Workflow <- Step Display Parked Doc
**************Empty
Document Template:
#######Workflow -> Step Create Doc From Template
**************&_WORKITEM& -> &FLOWITEM&
**************DC8BA2ADFCEA4EF18D2F00145EDCE7A4 -> &TEMPLATE&
#######Workflow <- Step Create Doc From Template
**************&WF_DOCUMENT_0001& <- &_WI_OBJECT_ID&
**************&_WF_INITIATOR& <- &_WI_ACTUAL_AGENT&
As ive explained earlier i have a Container VBSEGS with abap table vbsegs, which is filled using method ReturnMe2 with MyStruct2 structure.
Regards
Laurynas Prikockis -
Error While Creating Workflow for Purchase Requisition Rejection
HI Experts,
Purchase Requisition No is not Displaying in the Business Workplace Inbox after my Work flow got triggered.
In Work flow i am Using the Task 97600004 which i copied from the Standard Task 65400032. This Task i called in the Activity Step having Work Item Display Tab. In this Tab while i am checking at Work Item Text for Identification of Work item in work flow inbox level it is Giving Error "Container element '_WI_OBJECT_ID' does not exist and also Insert Expression is in Disable Mode.
In Business Workplace Inbox i am getting message as "Purchase requisition 00000 rejected".
Please Suggest where i am Committing Error.
Thanks in Advance
Srikanth KumarHI.
I Have Checked the work flow as suggested Dheepak
In Start Event of Work flow i declared BUS2105 as BOR Object . The Task which i copied contains BUS2009 as default.
As Raj Suggested In Task i have Created a New Element BUS2105 at Container Tab and set binding in task and set the Binding between Work flow and Task. Now it is working fine and i am getting the PR No in the Message of SBWP inbox.
But i Having one more doubt regarding this issue only Why BUS2009 BOR object Type is not working which is the Task as default even though its binding is set between work flow and task?
Thanks Dheepak and Raj for Your Valuable Suggestions. My gmail id is srikanth537. Can u add me In your Friends list.
Thanks
Srikanth Kumar
09937876902
Edited by: Srikanth Kumar Talasu on Dec 23, 2008 11:59 AM -
How to populate the CONTAINER, when calling a WorkFlow Task via FM?
Hello,
I am trying to trigger an email notification to user's SAP Inbox, if Outbound IDOC got failed. I wrote the below code in the processing FM, but, i am stucked at populating the CONTAINER parameter of this Task, pls. let me know How/with What I have to populate the CONTAINER parameter of this FM?
DATA: wa_input_container TYPE swr_cont,
wa_swr_messag TYPE swr_messag,
wa_swragent TYPE swragent.
* Fill Workflow element
wa_input_container-element = '_WI_OBJECT_ID' .
wa_input_container-value = wa_idoc_control-docnum.
APPEND wa_input_container TO itab_input_container.
* Fill Email body
wa_swr_messag-msg_type = 'E'.
wa_swr_messag-line = 'Error'.
APPEND wa_swr_messag TO itab_swr_messag.
CALL FUNCTION 'SAP_WAPI_START_WORKFLOW'
EXPORTING
task = 'TS00007989'
language = sy-langu
user = sy-uname
start_asynchronous = 'X'
IMPORTING
return_code = v_sy_subrc
TABLES
input_container = itab_input_container
message_lines = itab_swr_messag
agents = itab_swragent.
ENDIF.
Thank you.Hi,
Pls refer below link.
FM SAP_WAPI_START_WORKFLOW Exporting container without values -
Properties of the element of a task container.
Hello there,
The element I am binding from workflow to the container element doesn't allow me to change its property to 'import'
When I check the binding. I get this diagnostic message:
<element-name> is not an import element and is hence not to be changed
Message no. SWF_BND_001016
Diagnosis
The current binding instruction is aimed at an expression whose basis element <element-name> is not an import parameter. Only import parameters should be filled.
Procedure
If the value has to be sent, the element <element-name> should be marked as an import parameter and thus included in the interface.
Can anybody tell me how to fix this.
Thanks and regards.Hi,
From the problem that you have I assume that you are doing the binding from the Workflow container to the Task container. If that is right then check the following:
1. The task container is nothing but a reflection of the method parameters. When you define your method in SWO1 then these parameters usually get generated automatically if you use a function module or a BAPI. You have the option of adding them as well. There you have the check boxes of Import, Export and Multiline. You can change them but since they are auto generated you should not change them as they are a reflection of the interface parameters of the Function module.
2. If you want to change the entire container's property then go to the respective task either from the workflow builder or PFTC and then go to the tab "Container", select the container nd go to the properties tab and change the properties. However this applies to the container elements you have created and not the generated one (_WI_OBJECT_ID).
Hope this helps,
Sudhi -
hi can any one tell me what is workflow? where is it used ? how a workflow is created in SAP XI
Work Flow
Unit 1: Organizational Structure
Use
In order for the workflow system to establish the relationship between the requester and their superior, you must create an organizational plan in the system.
For this tutorial, of course, this organizational plan does not have to be complete and valid across the enterprise. To keep the test as simple as possible initially, define an organizational plan that only contains one administrator and one head of department.
Assign both items to yourself. As a result, all work items will appear in your own Business Workplace. Later you will modify the organizational plan such that you will have to work through the scenario with two users.
Procedure
The organizational plan required for this tutorial consists, when complete, of one organizational unit (= "department"), which contains two positions: a head of department and an administrator.
Each position is described by one job and each position is assigned one user as holder. The head of department position is also designated as chief position of the organizational unit.
Of course, a "real" organizational plan is created by arranging several organizational units with their positions in a hierarchy. Usually several positions are described by one job.
For further information, refer to the documentation Organizational Plan.
The procedure in this unit is divided into four parts:
1. You create an organizational unit.
2. Enter necessary jobs as required.
3. You create a position for the head of department in the new organizational unit.
You define a position in three steps:
i. You create a position that is assigned your organizational unit.
ii. You assign a holder to the position.
iii. You assign a job to the position.
3. You create a position for the administrator in the organizational unit.
Creating an organizational unit
1. Choose Tools  SAP Business Workflow  Development Definition tools  Organizational Management  Organizational plan  Create (T.Code: PPOCW).
2. Confirm the validity period proposed in the dialog box Creating a Root Organizational Unit.
This takes you to the Create Organization and Staffing (Workflow) screen. This user interface is divided into four screen areas:
3. On the Basic Data tab in the details area, enter an abbreviation and a name in the Organizational unit input fields.
Abbreviation: <ini_sales>
Name: <OrgUnit: Sales (ini)>
4. Choose .
You can now create the position for a head of department and one administrator.
Create jobs
When enhancing an organizational unit, the necessary jobs are usually already available. For this tutorial however, you create the necessary jobs for head of department and administrator yourself.
1. Choose Edit  Create jobs.
You go to the dialog box Create jobs. The lower area contains a list of existing jobs and the upper area contains an input table in which you can create new jobs by entering abbreviations and names.
2. In the input table, enter an abbreviation and a name for each of the new jobs.
Job - head of department:
Object abbreviation: < ini_dhead_C >
Name: < job: head of department (ini) >
Job administrator:
Object abbreviation: < ini_admi_C >
Name: < job: administrator (ini) >
3. Choose .
Creating Position for Head of Department
1. Change to the overview area in the staff assignments of the organizational unit, in order to assign positions, jobs and holders. Choose the arrow on the right next to the and then the staff assignments (list).
2. Choose .
A new position is then created in the staff assignments and is displayed in a new line in the table. The position is vacant and no job is assigned to it.
3. Open the details view for the new position in the details area by double-clicking on the entry in the table.
4. On the Basic Data tab, enter a code and a description in the Position input fields. Overwrite the previous contents.
Abbreviation: < ini_dhead_S >
Description: < position: head of department ( ini ) >
Assigning a holder to the position
You now assign R/3 users to the positions. The staff assignments for your organizational unit are displayed and you see the vacant position in the table.
5. Select User in the search area and enter the search criteria in order to find your user names.
All of the user names that match your search criterion are listed in the selection screen.
6. Select your user name in the selection area and drag it to the Person/User column of the position in the overview area.
Confirm the message that the relationship period of the validity has been changed.
7. Set the Head of own organizational unit indicator in the details area.
Assigning a job to the position
Assign the job of the head of department you created earlier to the position.
8. Select Job in the search area and enter the search criteria in order to find the job of the head of department.
All jobs that match your search criterion are listed in the selection screen.
9. Select job: head of department ( ini) in the selection area and drag it to the Job column of the position in the overview area.
10. Choose .
The job is assigned the position. Check this by switching to the staff assignments of the organizational unit. Select the organizational unit in the overview area, choose the arrow on the right next to the and then the staff assignments (list). The newly created job is displayed in the job column.
Create position for administrator and assign holder and job
You are now in the staff assignments of the organizational unit.
1. Choose .
A new position is then created in the staff assignments and is displayed in a new line in the table. The position is vacant and no job is assigned to it.
2. On the Basic Data tab in the details area, enter an abbreviation and a name in the Position input fields. Overwrite the previous contents.
ID: <ini admiS >
Description: < position: administrator ( ini ) >
3. Choose .
4. Select User in the search area and enter the search criteria in order to find your user names.
5. Select your user name in the selection area and drag it to the Person/User column of the position in the overview area.
Confirm the message that the relationship period of the validity has been changed.
6. Select Job in the search area and enter the search criteria in order to find the job of the administrator.
7. Select job: administrator ( ini) in the selection area and drag it to the Job column of the position in the overview area.
8. Choose .
Result
Display your entire staffing schedule again and make sure that all the information listed is correct.
You can display a detailed view of jobs, users, and positions. Choose the relevant cell in the table by double-clicking it.
In the details view of a position or job, all of the assigned tasks are displayed on the Tasks tab.
You have now completed the first unit (defining the organizational plan). You can now start on the next unit. To exit processing of the organizational structure, choose Back.
Unit 2: Creating a Workflow
Use
To define the flow of the approval process in the system, you first create a multistep task workflow template.
For further information, refer to Definition of Multistep Tasks in the SAP Business Workflow documentation.
Procedure: Creating a workflow template
1. Choose Tools  Business Workflow  Development Definition Tools  Tasks/Task Groups  Create (T.Code PFTC_INS)
This takes you to the Task: Maintain screen.
2. In the Task type field, choose the Workflow template entry.
3. Choose .
The Workflow Template: Add screen is then displayed.
Entering the basic data for the workflow template
1. Enter an abbreviation (of your choice) and a name (of your choice) for the workflow template to be created.
Abbreviation: < ini _ws>
Name: <Workflow: notification of absence ( ini )>
2. Choose .
3. In the Create Object Directory Entry dialog box, choose Local object.
The system has now allocated an 8-digit number for your workflow template. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. This number together with the letters WS forms the workflow ID. Make a note of the ID so that you can later call the workflow more quickly.
Entering a workflow description
4. Go to the Description tab.
5. Choose the text type Task description and then .
The SAPscript text editor is then launched.
6. Enter a text that describes the task. You can use the following proposal:
<You can use this workflow to create a notification of absence. This will then be sent to your superior for review. You will be notified of the result of this review.
If your request is rejected, you can revise it and resubmit it for review or withdraw it completely.>
7. Choose to return to the workflow template and then save the workflow template.
Determining agents
To enable the workflow template to be started in dialog, the workflow template must be assigned to its possible agents.
8. Select Additional data Agent assignment  Maintain
The workflow template: agent assignment screen is displayed.
9. Position the cursor on the name of your workflow template.
10. Choose Properties
The dialog box Task: <Workflow: Notification of absence (ini)> is displayed.
11. Set the General task flag.
12. Choose Copy and then .
Designating your workflow template as a general task means that every user in the system is authorized to start this workflow template in dialog.
Result
You have now created a workflow template as a "framework" for a workflow definition.
To create a workflow definition, you need tasks that are used as steps in the workflow definition.
Additional information: Tasks
A task can either be a single-step task or a multistep task. In our example of the notification of absence, making the application and checking the application are single-step tasks. The entire procedure involved in processing a leave request consists of these (and other) single steps, and is therefore a multistep task.
In this tutorial, a single step task is generally described as a task. The difference between the task types is only explicitly explained if there is a risk of confusion over multistep tasks. The term workflow is used as the umbrella term for the workflow template (and thus the multistep task) and the workflow definition. More precise differentiation only takes place if there is a risk of confusion.
On a technical level, the main difference between single-step tasks and multistep tasks is that:
Every single-step task refers to an object method
Every multistep task refers to a workflow definition
A workflow definition is made up of a sequence of different steps (for example, all steps required to process a leave request).
Standard tasks and workflow templates are client-independent. Customer and workflow tasks are client-dependent. Customer and workflow tasks are no longer supported and are therefore no longer used in this tutorial.
An Activity is a possible step type in a workflow definition. An activity refers to a task. It references a task, which can be a single-step or multistep task (subworkflow).
For further information, refer to Tasks and Task Groups in the SAP Business Workflow documentation.
Unit 4: Defining and Inserting Task "Create Notification of Absence"
Use
The notification of absence is created in the first step of the workflow. You will also need a task that executes this function. You can create the task separately from the workflow definition or directly from the Workflow Builder. This unit describes how you create the task from the Workflow Builder.
For further information on creating an individual task, refer to Definition of Single-Step Tasks in the SAP Business Workflow documentation.
Prerequisites
This task is a single-step task and it references one object method. The object type used (FORMABSENC (notification of absence)) and the required method (Create) are already defined and implemented in the Business Object Repository.
You are in the Workflow Builder and the initial workflow definition is displayed.
Procedure
Creating an Activity as a Step in the Workflow Definition
Add a first step of the type Activity to the workflow definition.
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step and click.
By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
Defining a Task "Create Notification of Absence"
You now create a new task, with which a notification of absence can be created.
1. Choose the arrow on the right next to the and then Create task.
The Basic data tab in the Standard task: Create screen is then displayed.
Entering the basic data
2. Enter an abbreviation (of your choice) and a name (of your choice) for the standard task to be created.
Abbreviation: < ini _creat>
Name :<Create notification of absence (ini)>
Work item text
The work item text appears as an information text in the Business Workplace as soon as there is a work item for the step with this task.
3. Enter Create notification of absence in the Work item text field.
Object type and method
4. Enter an object type and a method:
Object type: FORMABSENC
Method: CREATE
You can also use the F4 input help to select the method. Additional indicators associated with this method are set automatically.
You can view the definition of the object type entered by double-clicking on it. Information about its components is provided.
5. Save your task as a local object.
The system has now allocated an 8-digit number for your task. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. The identification of this task consists of TS and the eight digit number.
Determining agents
Selecting the possible agents for this task determines who is to be authorized to make leave requests. For this task, this should be all employees in your enterprise. Define the task as a general task.
1. Select Additional data Agent assignment  Maintain
This takes you to the Standard task: Maintain Agent Assignment screen.
2. Position the cursor on the name of your task.
3. Choose Properties
The dialog box Task: <Notification of absence (ini)> is displayed.
4. Set the General task indicator.
5. Choose Copy and then .
6. Exit the task definition with .
Interim result
You have now defined your first task in full. This task is used in the activity that you created in the Workflow Builder.
Completing Activity
The Define Container Elements and Binding dialog box is then displayed in which the system proposes a change to the workflow container and a binding definition.
Upper part of the dialog box: Proposal for new container elements in the workflow container.
The system proposes that you create a local container element in the workflow container, which can store the reference to the notification of absence created in this step. The element has the technical name AbsenceForm .
Lower part of dialog box: Proposed binding definition
The system proposes that you define a binding from the task container to the workflow container. This binding transports the reference to the generated object (i.e. the created notification of absence) from the task (from the WIObject_ID element in the task container) to the workflow (to the AbsenceForm element in the workflow container).
Further information on automatic binding definition proposals is available under Binding Definitions from the Workflow Container and Binding Definitions from the Task Container in the documentation on SAP Business Workflow.
1. Confirm the proposal with .
The new AbsenceForm container element is displayed in the workflow container. Local container elements are marked . The remaining elements in the workflow container are workflow system elements. For further information, please refer to Workflow System Elements in the Workflow Container.
2. Enter a text to describe the step.
You can, of course, leave the description of the task that is proposed by the system.
(The current step in your workflow definition appears here.)
3. Go to the Outcomes tab.
All of the outcomes for this step are displayed here.
4. Enter a text for the description.
The description (proposal: < Application filled out> ) in the Task executed synchronously line.
Each step has at least one subsequent event (in this case: Task executed synchronously). The description is the text with which the outcome is labeled in the workflow definition.
The Form does not exist and Form could not be generated outcomes are the possible exceptions that could occur in the method execution. You "run the risk" of not intercepting these exceptions and not modeling any exception handling in your workflow definition. If one of the exceptions actually occurs at runtime, the workflow will assume the error status.
Checking the binding definition (optional)
1. Go to the Control tab.
2. Choose Binding (present).
The WF Builder: Binding for Step <Create notification of absence> dialog box is then displayed.
o In the upper part of the screen, the binding defined from the workflow container to the task container is displayed. The system executes this binding before providing the task for execution.
This binding direction is not relevant for this step since no information is to be transported from the workflow to the task.
o In the lower part of the screen, the binding defined from the task container to the workflow container is displayed. This system executes this binding after the user has processed the task.
Here, the binding is WIObjectId. &ABSENCEFORM& has been automatically defined here by the system. This binding ensures that the reference to the notification of absence created is not only known in the single-step task, but also in the workflow.
You can view the contents of both containers by choosing Workflow container or Task container.
(The element of the task container WIObject_ID is called Notif. of absence .)
3. Choose .
You then return to the step definition.
Entering the agents responsible
On the tab page Control, choose the entry Workflow initiator (expression) in the area agent as the agent responsible.
The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
You start your executable workflow later manually. At this point in time, the system fills the workflow container element WFInitiator automatically with your user name.
The above assignment informs the workflow system that the first work item for creating the notification of absence should be addressed as the "starter" as the workflow.
You return to the screen Workflow definition: Create step: Activity
Concluding step definition
1. Choose to check the step definition.
2. Choose to exit the step definition.
3. Choose to view the entire workflow definition in the workflow area on the screen.
You will notice that your workflow definition now contains a new step (the activity just created). The undefined step is also still there.
4. Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
5. Exit the Workflow Builder.
Result
You have now completed this unit and can start the next unit.
Unit 3: Starting the Workflow Builder
Use
A workflow definition is created with the help of the Workflow Builder.
Prerequisites
You have now created a workflow template ( Unit 2: Creating a Workflow).
Procedure
Calling the Workflow Builder
1. Choose Tools  Business Workflow  Development  Definition Tools  Workflow Builder.
The Workflow Builder is then launched with the workflow definition that was processed last. If the Workflow Builder has not yet been called, then an initial workflow definition is displayed.
The Workflow Builder screen is divided into the following areas.
The workflow definition is displayed in the Workflow area on the screen. If the workflow is shown in display mode, the step type area is not displayed. For further information, refer to Workflow Builder in the SAP Business Workflow documentation.
2. Choose and enter the abbreviation of your workflow template (< WSeight digit number >) .
You can use the F4 input help. Enter the start of the abbreviation for your workflow (for example: < ini*> ) and choose All of the workflows that match are displayed. Select your workflow and choose .
Result
The workflow definition is displayed and if necessary can be processed. If the Workflow Builder is called for the first processing of a newly created initial workflow definition, the following graphic is displayed:
If the graphic displayed differs from that above, check the graphic settings in the Workflow Builder. Choose Extras  Options, and click the Graphic tab. Choose the Without event-driven process chains view.
The start of the workflow definition is indicated by Start Workflow. If the new workflow definition has been called from the definition of a multistep task for which triggering events are defined, these are represented by the symbol and their description.
The end of the workflow definition is indicated by Workflow terminated.
The area in which the new workflow definition can be added is indicated by an undefined step with an outcome. Steps are displayed in the form of symbols. The description of an outcome is illustrated in the standard view with an arrow.
This unit is now complete. In the following unit you create the first step in your workflow and define a task for this purpose at the same time.
Creating an Activity as a Step in the Workflow Definition
Add a first step of the type Activity to the workflow definition.
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step and click.
By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
Entering basic data for control
3. Enter the abbreviation ( TS<8-digit number> ) of the standard task Create Notification of Absence in the Task field and choose .
If you no longer know the full abbreviation, you can use different methods to search for it:
o Use the F4 input help to search via the object type and method of the single-step task.
This brings you to the Search and Find: Tasks dialog box.
On the tab page Obj. type and method, enter the object type FORMABSENC and the method CREATE .
Then double-click your single-step task in the list. You should recognize your single-step task from your initials in the abbreviation. Choose .
o Enter a character string in the abbreviation or description and choose .
A list of tasks is then displayed in which you can double-click the desired task.
Every activity, as a step in a workflow definition, refers to a task.
At this point, the unique reference to this task is entered. The identification is made up of an abbreviation (T, TS, WF, or WS) followed by an 8-digit number.
If you select a workflow task (WF) or workflow template (WS) as your task, your activity is a subworkflow. If you select a customer task (T) or standard task (TS), your activity is a single step.
The Define Container Elements and Binding dialog box is then displayed in which the system proposes a change to the workflow container and a binding definition.
o Upper part of the dialog box: Proposal for new container elements in the workflow container.
The system proposes that you create a local container element in the workflow container, which can store the reference to the notification of absence created in this step. The element has the technical name AbsenceForm .
o Lower part of dialog box: Proposed binding definition
The system proposes that you define a binding from the task container to the workflow container. This binding transports the reference to the generated object (i.e. the created notification of absence) from the task (from the WIObject_ID element in the task container) to the workflow (to the AbsenceForm element in the workflow container).
Further information on automatic binding definition proposals is available under Binding Definitions from the Workflow Container and Binding Definitions from the Task Container in the documentation on SAP Business Workflow.
4. Confirm the proposal with .
The new AbsenceForm container element is displayed in the object area of the workflow container folder. Local container elements are marked . The remaining elements in the workflow container are workflow system variables. For further information, please refer to Workflow System Variables in the Workflow Container.
5. Enter a text to describe the step.
You can, of course, leave the description of the single-step task that is proposed by the system.
(The current step in your workflow definition appears here.)
6. Go to the Events tab.
All of the outcomes for this step are displayed here.
7. Enter a text for the description.
The description (proposal: < Application filled out> ) in the Task executed synchronously line.
Each step has at least one subsequent event (in this case: Task executed synchronously). The description is the text with which the outcome is labeled in the workflow definition.
The Form does not exist and Form could not be generated outcomes are the possible exceptions that could occur in the method execution. You "run the risk" of not intercepting these exceptions and not modeling any exception handling in your workflow definition. If one of the exceptions actually occurs at runtime, the workflow will assume the error status.
Checking the binding definition (optional)
1. Go to the Control tab.
2. Choose Binding (present).
The WF Builder: Binding for Step <Create notification of absence> dialog box is then displayed.
o In the upper part of the screen, the binding defined from the workflow container to the task container is displayed. The system executes this binding before providing the task for execution.
This binding direction is not relevant for this step since no information is to be transported from the workflow to the task.
o In the lower part of the screen, the binding defined from the task container to the workflow container is displayed. This system executes this binding after the user has processed the task.
Here, the binding is WIObjectId. &ABSENCEFORM& has been automatically defined here by the system. This binding ensures that the reference to the notification of absence created is not only known in the single-step task, but also in the workflow.
You can view the contents of both containers by choosing Workflow container or Task container.
(The element of the task container WIObject_ID is called Notif. of absence .)
3. Choose .
You then return to the step definition.
Entering the agents responsible
Choose Workflow initiator (expression) under Agents.
The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
By doing so, you choose the agent responsible.
You start your executable workflow later manually. At this point in time, the system fills the workflow container element WFInitiator automatically with your user name.
The above assignment informs the workflow system that the first work item for creating the notification of absence should be addressed as the "starter" as the workflow.
You return to the screen Workflow definition: Create step: Activity
Concluding step definition
1. Choose to check the step definition.
2. Choose to exit the step definition.
3. Choose to view the entire workflow definition in the workflow area on the screen.
You will notice that your workflow definition now contains a new step (the activity just created). The undefined step is also still there.
4. Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
5. Exit the Workflow Builder.
Result
You have now completed this unit and can start the next unit.
Unit 5: First Test
Use
You are now going to start a workflow in dialog for the first time, which will run according to your workflow definition. This workflow definition only contains a step for creating a notification of absence so far.
For further information on starting workflows, refer to Starting Workflows (Test Environment) in the SAP Business Workflow documentation.
Prerequisites
The creation of a notification of absence, which you carry out within your workflow, is reported on a system-wide basis by an event. Other workflows entered as event receivers for this event may therefore be started. The notification of absence created by you (and published by the event) is then also processed with these workflows.
This event is not used in connection with this tutorial.
To ensure that only you work exclusively with the notification of absence, you can deactivate any existing linkages between the event and its receivers. Proceed as follows:
If you carry out the following steps, you prevent other workflows being started unintentionally by your notification of absence.
However, you may interrupt other workflow demonstrations. Therefore, be careful and speak to the colleagues involved if necessary.
1. Choose Tools  Business Workflow  Development  Utilities  Events  Simulate Event.
2. Enter FORMABSENC in the Object type field.
3. Enter created in the Event field.
4. Choose .
The system simulates the event FORMABSENC.Created and establishes which workflows would be started.
5. If you find one or more entries in the list under the branch Tasks without syntax errors to be started, position the cursor on an entry and choose Event linkage.
The dialog box Event linkage: Triggering events is displayed.
6. Position the cursor on the entry with the red background for the event and choose .
The linkage between workflow and event is deactivated.
7. Choose .
8. Repeat steps 5 to 7 or repeat the whole simulation as applicable.
Procedure
Starting the workflow and filling out the form
1. If you are still in the Workflow Builder, choose .
The Start Workflow (Test Environment) screen is then displayed. The number of your workflow template is entered.
If you are no longer in the Workflow Builder, choose Tools  Business Workflow  Development  Runtime Tools  Start Workflow (Test Environment). Enter the identification of your workflow or use the F4 input help.
2. Choose .
To handle work processes more quickly, SAP Business Workflow supports Advancing with Immediate Dialog. When a workflow is started in dialog, this means that the first work item of the workflow is made available for processing immediately provided that the user who starts the workflow is also one of the recipients of this first work item. This is the case here because you entered the container element WFInitiator as the agent in the step definition.
The Create notification of absence screen, therefore, is displayed immediately where you can see the notification of absence form. It is the method Create that is executed with the first work item.
3. Fill out the form with entries of your choice.
4. Choose .
The Start Workflow (Test Environment) screen is then displayed again.
5. Choose and exit the Workflow Builder if necessary.
Starting a workflow / Business Workplace
Before you extend your workflow definition, carry out the following test. It will familiarize you with the Business Workplace.
1. Start your workflow in dialog again. Choose Tools  Business Workflow  Development  Runtime Tools  Start Workflow. (T.Code SWUI)
You go to the screen Start task.
2. Choose your workflow in the table on the left.
3. Choose Start on the right-hand side of the screen.
The notification of absence form is displayed.
4. Do not make any entries and do not save. Instead, choose .
You have now started the workflow but canceled the processing of its first step. But the processing of the work item is not yet completed. You have only broken the processing chain of advancing with immediate dialog.
5. Choose .
6. Choose Tools  Business Workflow  Development  Runtime Tools  Business Workplace.
7. Open the Inbox node and choose the Workflow folder.
Your workflow inbox now contains (at least) one work item for processing. This is the work item for creating a notification of absence, the processing of which you canceled previously.
8. Select the work item, if necessary, and choose .
You return to the Create notification of absence screen where the notification of absence form is displayed.
9. Fill out the form and choose .
The work item disappears from your workflow inbox.
Result
You have now completed this unit and can start the next unit.
Reporting and analysis
In this first test, you will take a look at the work item analysis function.
1. Choose Tools  Business Workflow  Development  Reporting  Work Item Analysis  Work Items Per Task
The Work Items Per Task screen is then displayed.
2. Select the monitoring period Today.
3. Select the work item type (Sub-)Workflow only.
4. Choose .
The system then determines all of the workflows that were started today. These are then listed on the Work Items Per Task from <Date> to <Date> screen. The number of work items in each workflow is also shown here.
Make sure that you only ever analyze the work items for your workflow and your absence notification.
5. Display the list of associated work items by double-clicking the workflow ID.
Both the workflows you just started for this workflow identification are displayed with status Completed.
6. Display the workflow log by double-clicking a work item ID.
The Workflow Log screen is then displayed.
For information on the workflow log, see Workflow Log in the SAP Business Workflow documentation.
7. Exit the work item analysis function.
Unit 6: Creating a Task "Check Notification of Absence"
Use
You define the task Check notification of absence. This task is incorporated into your workflow definition as the second step.
As this is not the first task you have defined, many steps will doubtless be familiar to you. (Refer to Unit 4: Defining and Inserting Task "Create Notification of Absence.)
Prerequisites
The object type used (here: FORMABSENC (notification of absence)) and the required method (here: Approve) are already defined and implemented in the Business Object Repository.
Procedure
1. Choose Tools  Business Workflow  Development Definition Tools  Tasks/Task Groups  Create.
The screen Task: Maintain is displayed.
2. In the Task type field, choose the Standard task entry.
3. Choose .
The Basic data tab in the Standard task: Create screen is then displayed.
Entering the basic data
1. Enter an abbreviation (of your choice) and a name (of your choice) for the task to be created.
Abbreviation: < ini _check>
Name: <Check notification of absence (ini)>
Object type and method
2. Enter an object type and a method:
Object type: FORMABSENC
Method: APPROVE
You can also use the F4 input help to select the method.
Work item text
3. In the Work item text field, enter the text Check notification of absence from .
4. Choose . Save your standard task as a local object.
5. You can include variables in your work item text to be filled with values from the task container at runtime..
The name of the creator of the notification of absence is to be included into the work item text. As soon as the work item appears in the superiors Business Workplace, the name of the creator appears in the work item information text.
Position the cursor in the work item text after the word of .
6. Choose .
The Please choose an expression dialog box is then displayed.
7. Choose the expression Notif. of absence by double-clicking the Container node.  Issuer object ref.  Name.
If WIObject_ID is displayed instead of Notif. of absence, choose . The system then displays the description of the expressions instead of their technical names.
The variable &_WI_Object_ID.Creator.Name& has been added to the work item text automatically. The variable name displayed here is the technical name of the expression.
You can integrate all of the elements in the task container in your work item text. This enables you to include information into the work item text, which is not available until runtime.
Entering the description text
1. Go to the Description tab.
2. Choose Task description in the Test type field.
The current task description is then displayed. This text is intended to inform future recipients of a work item in which this task is referenced and help them in their work.
The text will often be similar to the work item text or may supplement it.
3. Choose .
4. Enter the following text:
Please check notification of absence no. &_WI_OBJECT_ID.NUMBER& from &_WI_OBJECT_ID.CREATEDATE& of employee &_WI_OBJECT_ID.CREATOR.NAME& .
Decide whether to approve the request.
If you want to insert an expression from the task container as a text variable, choose Include  Expression. Then choose the relevant expression in the Please choose an expression dialog box by double-clicking the Container node.
5. Choose .
6. Choose .
Determining possible agents
1. Select Additional data Agent assignment  Maintain
This takes you to the Standard task: Maintain Agent Assignment screen.
2. Position the cursor on the name of your task.
3. Choose .
You go to the dialog box Choose agent type.
4. Double-click Job.
The dialog box Choose Job is displayed.
5. Enter either part of or the full abbreviation of the job that you created for the head of department in Unit 1: Organizational Plan.
You return to the screen Standard task: Maintain agent assignment.
6. Choose .
You have linked the task to the job of a head of department. In the organizational plan, you use this job to describe a position. The holder of the position is also displayed.
7. Choose .
8. Choose .
Result
The task for checking the notification of absence is defined in full. You can now exit the screen for defining a task.
In the next unit, you will incorporate this task into the workflow definition.
Display your organizational plan again.
a. Choose Tools  Business Workflow  Development  Definition Tools  Organizational Management  Organizational Plan  Display.
b. Choose your organizational unit in the search area. Display it by double-clicking the entry in the table.
c. In the overview screen, choose the arrow on the right next to the and then Staff assignments (list).
d. Display a detailed view of the position of the head of department by double-clicking the entry in the list.
Here, you can see that this position is assigned to the job and, on the Tasks tab, that it is also assigned to the task Check notification of absence.
Unit 7: Including "Check Notification of Absence" in the Workflow Definition
Use
The task with which an employee can check a notification of absence is ready to be included into your workflow definition as the next step.
Prerequisites
You have defined a workflow with a step ( Unit 4: Task Defining and Inserting "Create Notification of Absence") and created the task Check Notification of Absence ( Unit 6: Create Task "Notification of Absence").
Procedure
Calling the Workflow Builder
1. Choose Tools  SAP Business Workflow  Development  Definition Tools  Workflow Builder.
The Workflow Builder is then launched in display mode with the workflow that was processed last.
2. Work through the following steps to display your workflow for this tutorial in change mode.
i. If the workflow you created for this tutorial is already displayed, choose . Go to step 3.
ii. If a different workflow is displayed, check whether the workflow you created is listed in the My available tasks area. Double-click it and choose . Go to step 3.
iii. Choose . Enter the complete abbreviation in the Task field on the Open other workflow definition dialog box and press RETURN. You can now also enter the workflow abbreviation. Enter either the full abbreviation or just the first characters (for example: < i*> ). Press F4 . The search result is then displayed. Choose your workflow by double-clicking it. When you enter the abbreviation in the Task field on the Open other workflow definition dialog box, all of the available versions are displayed. Since you have not created any versions, select version 0000 and choose . The workflow is then loaded in display mode. To switch to change mode, choose .
1. Choose to display the entire workflow in the workflow area on the screen.
Creating a container element in the workflow container
You need an additional container element in the workflow container to store the name of the user who will execute this step. This user name is to be used later in the notification text that is sent to the requester.
1. Choose the entry <Double-click to create> by double-clicking in the Workflow Container.
The dialog box for entering a container element is displayed.
2. Make the following entries:
Element: Approver
Name: Approver
Description: Approver of the absence request
Reference table: WFSYST
Reference field: AGENT
3. Choose .
You have now added a local container element to the workflow container, which is ready to take an agent name, based on its data type reference. However, you have not yet determined a value for this container element.
Creating an Activity as a Step in the Workflow Definition
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step that follows the outcome Request completed and click.
By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
Entering basic data for control
3. In the Task field, enter the abbreviation ( TS<8-digit number> ) of the task Check Notification of Absence that you defined in the previous unit. Choose .
If you no longer know the full abbreviation, you can use different methods to search for it:
o Use the F4 input help to search via the object type and method of the task.
This brings you to the Search and Find: Tasks dialog box.
On the tab page Obj. type and method, enter the object type FORMABSENC and the method CREATE .
Then double-click your task in the list. You should recognize your task from your initials in the abbreviation. Choose .
o Enter a character string in the abbreviation or description and choose .
A list of tasks is then displayed in which you can double-click the desired task.
Every activity, as a step in a workflow definition, refers to a task.
At this point, the unique reference to this task is entered. The identification is made up of an abbreviation (T, TS, WF, or WS) followed by an 8-digit number.
If you select a workflow (WS or WS) as your task, your activity is a subworkflow. If you select a task (TS or T), your activity is a single step.
You go to a dialog box in which the system proposes binding from the workflow container to the task container.
Here, the object reference to the notification of absence is transported from the workflow container (container element AbsenceForm ) to the task container (to the container element WIObject_ID ).
1. Choose to confirm the proposal.
Extending the binding definition
Now define another binding via which the current agent of the work item (the superior) is stored in a container element of the workflow container.
2. Choose Binding (present).
The Binding for Step 'Check notification of absence' dialog box is then displayed. If the first column is entitled Element, choose to display the element description.
The system has created the following binding definition from the workflow container to the task container:
Notif. of absence &AbsenceForm&
This binding ensures that the correct notification of absence is checked in the task.
3. Choose .
All of the container elements in the task container are now displayed on the left-hand side. You can define a binding from these container elements to the workflow container.
4. Position the cursor in the lower half of the screen, in the empty input field beside the container element Actual agent and call the F4 input help.
5. Double-click Approver.
In addition to the bindings already existing, the following binding is now defined:
Actual Agent &Approver&
6. Choose .
Determining outcomes
The method APPROVE of the object type FORMABSENC, to which you refer in the standard task definition, is defined with a result. The three possible values of this result are offered on the tab page Outcomes as outcomes of this step:
Approved
rejected
New
The indicates that these outcomes have already been transferred to the workflow definition. The outcome New is not really appropriate at this point. At this stage of processing, the notification of absence cannot be "new" any more. It should therefore not be incorporated in the definition.
1. Click on the symbol in front of the outcome New.
The symbol changes to .
The outcome Processing obsolete is processed if the relevant work item is set to obsolete via a process control step. This functionality is not used in this tutorial.
The outcome Form not available results from the exception defined for the method APPROVE. You could include this outcome into the workflow definition and would then have to model appropriate subsequent steps. However, you do not model anything for the purposes of this tutorial and accept that your workflow will have an error at runtime if this exception is raised.
2. Choose .
Two branches are now inserted in your workflow definition for the two marked outcomes Approved and Rejected.
Inputs for the agent
If you are working through this tutorial alone, do not specify anything for responsibility at this point. If it is processed when the workflow is executed, therefore, this step will be "offered" for processing to all employees declared as possible agents of the single-step task Check notification of absence. This means all user whose positions are described with the job head of department.
In your organizational plan, there is only one users who is a possible agent -> you.
You have maintained the organizational plan with jobs, positions, and user assignments in Unit 1: Organizational Plan.
You have defined the single-step task "Check notification of absence" and have assigned the possible agents in Unit 6: Definition of the Standard Task "Check Notification of Absence".
Concluding step definition
Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
Result
You can subject your workflow definition to a second test.
Unit 8: Second Test
Use
You start your workflow in dialog and two steps are executed. The notification of absence is created in the first step and then checked in the second.
Procedure
Starting the workflow and filling out the form
1. If you are still in the Workflow Builder, choose .
The Start Workflow (Test Environment) screen is then displayed. The number of your workflow is entered.
If you are no longer in the Workflow Builder, choose Tools  Business Workflow  Development  Runtime Tools  Start Workflow (Test Environment). Enter the number of your workflow or use the F4 input help.
2. Choose .
You go to the screen Create Notification of Absence.
From the requesters perspective
When the workflow is started, the work item for creating the notification of absence is provided to you directly for processing. This is because of advancing with immediate dialog. You were introduced to this in the first test.
3. Fill out the form and choose .
From the head of department's perspective
You created the step for checking the notification of absence in your workflow definition without specifying the agents responsible. This means that all of the possible agents of the single-step task are recipients of the work item. Since you occupy the position of both requester and head of department, you are automatically and immediately presented with the work item for approving the application. This is again because of advancing with immediate dialog.
As the superior, you have several options:
Approve the request
Reject the request
Cancel processing of the request.
4. Choose to cancel processing.
The Start Workflow (Test Environment) screen is then displayed again.
Exit this dialog and, if necessary, the Workflow Builder.
Reporting and analysis: Workflow outbox
In the first test of your workflow, you were introduced at this point to work item analysis. Now, you will be introduced to the workflow outbox.
Amongst other things, the work items which you started in dialog along with date, time and current status are displayed in the workflow outbox.
1. Choose Tools  Business Workflow  Development  Runtime Tools  Business Workplace.
2. In the tree displayed, choose Outbox  Started workflows.
3. Choose the arrow on the right next to the and then Today only.
The work items for all the workflows you started today are then displayed. Note the statuses of the work items displayed in the Status column of the Business Workplace. Read the F1 help for the Status column.
4. Position the cursor on the work item for the workflow just started. This work item has the status in process.
From the current workflow data, you can see that the step Create notification of absence has been completed successfully, when that was, and who processed it. The work item has the status completed.
You can also see that the work item representing the task for checking the request still has status ready and can therefore still be seen in the superiors Business Workplace.
Business Workplace - check notification of absence
You now once again occupy the position of the superior who canceled processing earlier when the application was to be checked.
5. In the tree, choose Inbox  Workflow.
The work items for you to process are displayed with their work item texts and certain other attributes.
A preview of the selected work item is displayed below the list and contains the description of the work item.
6. Select the work item for checking the notification of absence and choose .
You go to the work item display. There you find amongst other things the description text, also with replaced text variables.
7. Choose to return to the Business Workplace.
8. Choose or start execution by double-clicking the entry.
9. Either reject or approve the request. You should start the workflow twice and test each variant.
To check whether the workflow was completed correctly, go to your workflow outbox. The procedure is described above.
Result
Your workflow definition has now been tested and you can continue with the next unit.
Unit 9: Adding a User Decision
Use
In the previous units, you created a workflow whose definition contains two activities. These activities are based on two standard tasks that you created.
In this unit, you will add a user decision to your workflow definition.
With the user decision, the requester can decide to revise and resubmit the notification of absence if the head of department rejects it.
For further information, refer to Maintaining a User Decision in the SAP Business Workflow documentation.
Procedure
You start the Workflow Builder and open your workflow definition in Change mode. Proceed as described in Unit 7: Including "Check Notification of Absence" in the Workflow Definition.
Creating a user decision as a step in the workflow definition
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step that follows the outcome Rejected and click.
By doing so, you add a user decision to your workflow definition. The step definition is shown in the right-hand part of the screen. The Decision tab is displayed.
Entering basic data for user decision
3. Enter Your request was rejected by &. Revise? in the Title field.
This text is used as the title for the alternative decisions when the workflow is executed. The variable & is a placeholder for a parameter that is filled from the task container at runtime.
4. Choose the F4 input help in the Parameter 1 field.
The Expression for first parameter of user decision dialog box is then displayed.
5. Choose the Approver container element by double-clicking it.
Entering alternative decisions
6. Define the alternative decisions. Enter the following texts:
Decision texts Name
Decision: Revise request? Revise
Decision: Withdraw request? Withdraw
7. The decision texts you enter here appear as decision options on the screen that can be processed by the requester after their leave request has been rejected.
8. The descriptions are the terms used to describe the outcomes in the workflow definition.
9. Entering the agents responsible
10. Choose Workflow initiator (expression) under Agents.
The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
Concluding step definition
1. Choose to check the step definition.
2. Choose to exit the step definition.
3. Choose to view the entire workflow definition in the workflow area on the screen.
You can see that your workflow definition contains a user decision in the rejected branch. This has two outcomes whose branches converge again in the rejected branch. Each new branch contains an undefined step.
4. Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
Result
You can now subject your workflow definition to another test.
Unit 10: 3rd Test
Use
You start your workflow in dialog and three steps are executed: Two activities, for creating and checking a notification of absence, and one user decision.
Procedure
Starting the workflow and filling out the form, checking the notification of absence, user decision
1. If you are still in the Workflow Builder, choose .
The Start Workflow (Test Environment) screen is then displayed. The number of your workflow is entered.
If you are no longer in the Workflow Builder, choose Tools  SAP Business Workflow  Development  Runtime tools  Start workflow (test environment). Enter the number of your workflow or use the F4 input help.
2. Choose .
You go to the screen Create Notification of Absence.
From the requesters perspective
3. Fill out the form and choose .
When you save the form, you (as superior) can immediately approve or reject the application (reason: advancing with immediate dialog).
From the superiors perspective
4. Do not approve the application.
5. Choose .
If the request is not approved, the next step in the workflow definition is the user decision. The requester was entered as the agent for the step. The decision is therefore offered to you again as the requester (reason: advancing with immediate dialog).
From the requesters perspective
You are given three options:
Revise request?
Withdraw request?
Cancel
It is irrelevant which option you choose since you have not defined any follow-up steps. You should start the workflow several times and try out the different options. The complete process flow can be checked each time in the work item analysis or workflow outbox.
Unit 11: Define and Include "Revise Notification of Absence" in the Workflow Definition
Use
You will now add the activity Revise notification of absence to your workflow definition. You will create the necessary task within the -
Extract PO header text in PO work flow item description
Hi,
I'm trying to display PO header text using standard PO workflow.
I managed to retrieve the PO header text information at the business object(SWO1). Now it is only displaying the last line of the PO header text. I define object &_WI_OBJECT_ID.POTEXT& in the work item text. POTEXT is of type VIRTUAL and with reference to table tline and field tdline.
How to make this field POTEXT multiline in the workflow work item?
For example PO header text contains:
Header testing1
Header testing2
Header testing3.
Currently, it is showing only Header testing 3. I'm not sure how to do coding in business objects for this case.
I am using 'READ_TEXT' function module, but how to display the text information in this field POTEXT?
Please advise. Thanks.Hi Dev,
Thank you for your quick & prompt response.
The program that you have given is showing the text details but it is not showing complete text details, it is only showing 1st line of text. Please see screen shot for your reference, please suggest how to get complete text details. -
Why am I getting "Associated object cannot be opened"?
I have created a task that utilizes method CRMSALESPROCESSEDIT of standard BOR object BUS2000115 on our CRM sandbox. As a test, I launched the Webclient UI from transaction BSP_WD_CMPWB by clicking on the Test pushbutton for component CRM_UI_FRAME. I can see my task in the CRM Task List. However, when I try to execute the task I receive the message, "Associated object cannot be opened; contact your system administrator".
According to the second edition of the text "Practical Workflow for SAP", I "can use every standard BOR object type that is enabled for dynamic navigation for your own workflow without further customizing and implementation effort". Accordingly, I checked in table BSP_DLC_OBJ_TYPE and found object BUS2000115. So why am I getting the error message?
I tried maintaining Object Specific Navigation for this method in the IMG but it did not make a difference. But I might not have maintained it properly.
When I execute this task in the Business Workplace of the SAPGui it takes me to the "Search for Business Transactions" screen.
I am on version 'SAP CRM ABAP 6.0', with SAP_ABA and SAP_BASIS = 700. SAP_AP = 700. PI_BASIS = 2006_1_700. ST-PI = 2008_1_700. BBPCRM = 600.
Thanks for your help.Hi Lars,
I will do what I can to help but I am going from memory. Our sandbox has been rebuilt several times in the the last few years. Plus we only use our SAP CRM system for channel managment now.
I think that I instantiated an instance of the business object BUS2000115 in a previous step of the workflow with a custom task that utilized method 'GENERICINSTANTIATE' of object 'SYSTEM'. I bound that instance to a workflow container object (probably called BUS2000115).
In a subsequent step I think that I failed to explicitly bind BUS2000115 to &_WI_OBJECT_ID&. This was in the definition of the step. In other words, from the workflow builder (transaction PFTC_CHG) I clicked on the "Workflow Builder" pushbutton. Then I double clicked on the step where I wanted to change the sales transaction. I entered the appropriate task and step name for changing the sales transaction. Then I clicked on the Binding pushbutton just below the "Step Name". In the top table control on the popup I entered &BUS2000115& on the left and &_WI_OBJECT_ID& on the right.
Once I did that then the error message was resolved. Hope that helps.
Cheers,
Paul -
Mass Approval for Leave in UWL
Dear Gurus,
we are facing issues in mass approval for leave process in our UWL. we have customized the xml file and added approve and reject columns in the table. this is all in a new custom view that is designed and uploaded with high priority.
when selecting radiobuttons and clicking submit, Task disappears from UWL and moved to outbox in SAP Inbox.
But the document status is "SENT" and not changing to Approved /Rejected. Workflow Status is showing as completed.
Any clue.? Do we need to change the Workflow to accept the user decision via UWL. Any Container/parameters to be updated in addition?
<Action name="approved" userDecision="yes" handler="UpdatingContainerHandler" referenceBundle="com.sap.pct.erp.mss.leaverequest.approve">
<Properties>
<Property name="_WI_OBJECT_ID.STATUS" value="APPROVED"/>
<Property name="_WI_RESULT" value="A"/>
<Property name="_RESULT" value="A"/>
</Properties>
</Action>
<Action name="rejected" userDecision="yes" handler="UpdatingContainerHandler" referenceBundle="com.sap.pct.erp.mss.leaverequest.reject">
<Properties>
<Property name="_WI_OBJECT_ID.STATUS" value="REJECTED"/>
<Property name="_WI_RESULT" value="R"/>
<Property name="_RESULT" value="R"/>
</Properties>
</Action>
Kindly help
Regards,
AnkurDear All,
An Update. although workitems go away from manager's UWL, the leave status of the employee remains "SENT" and does not change to "Approved".
this is because from 3 steps that are allowed in workflow Accept(approved), reject(rejected) and cancelled(error step), the workflow progresses to step 3(cancelled).
I checked with workflow consultants and they checked everything and reported that this requirement cannot be handled by changing the workflow as enough information is not passed to them to change the status of the particular leave in the tables...
Kindly advice, if this configuration could work, or we need to go for custom development to create a new portal applicaton along with adaptive RFC's? in this case it will be a big and time consuming process in itself.
regards,
'Ankur Agarwal' -
Terminating Event with Decision Step
Hi,
In our purchase requisition approval workflow, I need to have a decision step in which to prompt approver to either approve the req. or reject the requisition. In this decision step, I need for it to have terminating events for "SIGNIFICANTLYCHANGED", "RELEASE", "REJECT" and "RESET".
First, I copy the generic decision task 8267 to my my own custom decision task. Then I added a BUS2009 in the container, releasecode and other needed elements. In this custom decision task, I was able to add these terminating events that has been defined in the BUS2009. I was able to setup binding, except the one binding
Terminating Event -> Task
&_EVT_OBJECT& -> &_WI_OBJECT_ID&
Since the &_EVT_OBJECT& for the terminating event is BUS2009. And the custom decision task &_WI_OBJECT_ID& is DECISION business object. They're incompatable business object. So I replaced that binding with
Terminating Event -> Task
&_EVT_OBJECT& -> &PURCHASE_REQ&
After all the configuration has been setup. I created a new purchase requisition. Upon the RELEASESTEPCREATED event, it create a custom decision workitem in my agent's inbox. When I triggered the "RELEASE" event, it is however not terminating my custom decision workitem. The workitem still sits in the agent's inbox waiting to be execute.
Is it possible to setup terminating events for decision step? Any kind of suggestions or inputs would be greatly appreciated.
Thank you.
Jennifer Tran
System AnalystI will suggest you to create a fork with 2 parallel branch and 1 necessary branch. Put the approval step in 1 branch and the wait for Release step event in another branch in this way you can suffice your requirment.
Thanks
Arghadip -
Terminating Event Generate an Error
Hi All.
My custom workflow has asynchronous task where the terminating events trigger from ABAP program and passed some data.
This task will completed upon custom event "ACCEPTED" raised in the system based on certain keyfield and continue next steps.
Terminating events tab contains element WIOBJECT_ID and my custom event "ACCEPTED".
Binding is use standard element Binding details as per standards, &_EVT_CREATOR& --> &INITIATOR and &_EVT_OBJECT& --> &_WI_OBJECT_ID&
I though this is the only step that I need to do and of course wait step.
However when I test this terminating event via SWUE with proper object key, event trace transaction reported event "ACCEPTED" for task TS95000052 not defined as start/end event.
I check in instance linkage transaction, linkage is activated for my object type, "ACCEPTED" and receiver type "WORK ITEM".
Event type linkages between event and my asynchronous task also active.
Will someone give me a clue, what should I do to resolve this issue?
Many ThanksYou cannot exit from a for loop until it is done. Use a while loop instead. Also, using the event structure in this case causes all kinds of exit problems. Try it and you will see what I mean. Instead, use the abort button itself. Put a case statement at the end to give the error output if the abort button was pressed. See attached vi.
- tbob
Inventor of the WORM Global
Attachments:
abortTesting.vi 45 KB -
Event finds no receiver even though object key is OK
Hello,
can’t see what goes wrong here. I have a work item waiting for an event. I trigger the event for with the matching object key, but the event finds no receiver, and nothing happens.
To elaborate,
the asynchronous ‘Document review’ task has terminating events REJECT etc. from my ABAP (business) class ZCL_PROL. On the terminating events tab:
_WI_OBJECT_ID CL ABAP Class ZCL_PROL REJECTED
I trigger the event using cl_swf_evt_event=>raise and from SWEL I see that the event has been created correctly, for the right object type and object key.
On the other hand, from SWEINST I see that the ‘Document review’ work item is registered for the event. Table entry
CL ABAP Class ZCL_PROL REJECTED WORKITEM 10000000000392 000000045550
The class ZCL_PROL and the object key 10000000000392 in SWEINST are identical to what I see in SWEL.
The method FIND_BY_LPOR must be fine, as the wf has proceeded to this point. And no issues to be seen in SWEQADM.
Now, what goes wrong? Why doesn’t my work item react to the event?
Message was edited by: Arto PihlajaAnjan, Prakash, thanks for your lightning fast replies!
I actually found the issue myself.
I had
cl_swf_evt_event=>raise(
im_objcateg = cl_swf_evt_event=>MC_OBJCATEG_BC
im_objtype = mv_objtype
im_event = gc_rejected
im_objkey = mv_instid
im_event_container = mr_event_container
Once I changed the object category to MC_OBJCATEG_CL, it started working. Clearly I had misunderstood the meaning of 'Business Class'. I changed back to regular CL, and it's fine.
Once again, thanks for your activity!
Maybe you are looking for
-
Infopath form for sharepoint 2013 lags when searching for person or group.
Dear all, After implementing a infopath form on sharepoint, the search for person or group column lags when I search for someone the second time. (The first time won't lag). Is there a fix to this? And is there a way to modify the search for person o
-
Macbook Pro Retina Display - Sound and video doesn't work at the same time.
I just bought a macbook pro retina display and tried to watch a movie by connecting my macbook pro via hdmi to my home theater receiver (Onkyo TX-SR309) and into my HDTV (Sony Bravia 42"). My problem is, i don't get sound from the speakers connected
-
I'm a user of Lightroom 5 and Photoshop CS6 runiing the current version of each. I signed up for Creative Cloud and have downloaded and installed Photoshop CC. I have not downloaded and installed Lightroom from CC as I understand it is the exact sa
-
hi everybody, I have 2 fields on the screen X1 and X2. and i have an internal table with 4 fields (itab). my problem is i want the whole internal table when i press F4 on filed X1 and if i select a record from F4, field X1 must be populated with (ita
-
Masking sensitive fields during display
We want to mask some sensitive fields such as bank account number, social security number, credit card number etc during display based on an authority check. The displayed values, if not authorized, may look something like *****1234 or 1234***** with