SAP NetWeaver 2004s Business Workflow教程：构建与维护组织流程

workflow

需积分: 10 136 浏览量更新于2024-08-02 收藏 1.15MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

Tutorial: Workflow Modeling April 2006

Unit 3: Creating a Workflow

Business Workflow - Tutorials 11

3. Choose Task description as the text type. Click on the text Click here to edit task.

The

Task description screen is displayed. You can create a text here using the

SAP

script Editor.

4. 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.>

5. Choose to go back to the processing of the workflow.

Determining agents

To enable the workflow to be started in dialog, you have to assign possible agents to the

workflow.

6. Choose

in the application toolbar.

The

workflow template: agent assignment screen is displayed.

7. Position the cursor on the name of your workflow.

8. Choose

Properties…

You go to the dialog box

Task.

9. Set the

General task flag.

10. Choose

Copy and then .

Designating your workflow as a general task [Extern]

means that every user in

the system is authorized to start this workflow in dialog.

11. Exit the basic data of the workflow and choose

Save.

Result

You have created a workflow with its basic data. The required multistep task was created

automatically by the system.

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 [Extern] or a multistep task [Extern]. 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.

Tutorial: Workflow Modeling April 2006

Unit 4: Defining and Inserting Task "Create Notification of Absence"

Business Workflow - Tutorials 12

For more information, see Definition of Multistep Tasks [Extern] in the SAP Business

Workflow documentation.

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.

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 more information, see Tasks and Task Groups [Extern]

in the SAP Business Workflow

documentation.

2.4 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

[Extern] 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 your workflow is displayed in change mode.

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.

Tutorial: Workflow Modeling April 2006

Unit 4: Defining and Inserting Task "Create Notification of Absence"

Business Workflow - Tutorials 13

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

3. 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.

4. Enter

Create notification of absence in the Work item text field.

Object type and method

5. Enter an object type and a method:

Object category: BOR object type

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.

6. 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.

Task description

The task description is used in the work item preview to provide the recipient of the work item

with more information.

7. Go to the

Description tab.

2. Choose the text type Task description and then

The

Task description screen is displayed. You can create a text here using the

SAP

script Editor.

3. Enter a text that describes the task. You can use the following proposal:

<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.

Tutorial: Workflow Modeling April 2006

Unit 4: Defining and Inserting Task "Create Notification of Absence"

Business Workflow - Tutorials 14

If your request is rejected, you can revise it and resubmit it

for review or withdraw it completely.>

4. Choose Back and save the task definition.

8. Exit the task definition with

Interim result

You have now defined your first task. This task is used in the activity that you created in the

Workflow Builder.

Completing Activity

When you exit the task definition, the Define Container Elements and Binding dialog box is

displayed in which the system proposes a change to the workflow container and a binding

definition:

● The upper part of the dialog box contains proposals 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.

● The lower part of the dialog box contains proposals for a binding definition from and to

the task container.

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 _WI_Object_ID element in the task

container)

to the workflow (to the AbsenceForm element in the workflow container).

For more information on automatic binding definition proposals, see Binding Definitions from

the Workflow Container [Extern] and Binding Definitions from the Task Container [Extern] 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 more information, see Workflow System Elements

in the Workflow Container [Extern].

2. Enter a text to describe the step.

You can, of course, leave the name of the task that is proposed by the system. The

name entered here is used to identify the step in your workflow definition.

3. Go to the

Outcomes tab.

All of the possible outcomes for this step are displayed here. Only the outcome

Step

executed

is active.

4. Enter a text for the name of the active outcome.

Enter the name (proposal: <

Application filled out>) in the Step executed line.

Each step has at least one subsequent outcome (in this case:

Step executed). The

name 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

Tutorial: Workflow Modeling April 2006

Unit 4: Defining and Inserting Task "Create Notification of Absence"

Business Workflow - Tutorials 15

workflow definition. If one of the exceptions actually occurs at runtime, the workflow will

assume the

error status.

Checking the binding definition (optional)

5. Go to the Control tab.

6. Choose

Binding (present).

The

Binding for Step '<Create notification of absence (ini)>' dialog box is then

displayed.

○ 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.

○ 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

_WI_ObjectId. &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 task, but

also in the workflow.

You can view the definition of both containers by choosing

Workflow container or Task

container.

(The element of the task container

_WI_Object_ID is called Notif. of absence.)

7. Choose

You then return to the step definition.

Defining recipients

You have to define who is to execute the work item at runtime. You can enter possible,

responsible, and excluded agents. Recipients of the work item are all responsible agents who

are also possible agents and who are not listed as excluded agents.

Determining possible agents

Selecting the possible agents [Extern] 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 [Extern]

8. Choose

on the Control tab page in the frame Task properties.

This takes you to the

Standard task: Maintain Agent Assignment screen.

9. Position the cursor on the name of your task.

10. Choose

Properties…

You go to the

Task: dialog box.

11. Set the

General task indicator.

12. Choose

Copy and then .

剩余104页未读，继续阅读

meteor_yang

粉丝: 0
资源: 1

SAP NetWeaver 2004s Business Workflow教程：构建与维护组织流程

BC600_SAP Business Workflow Introduction

SAP Business Workflow 4.6C入门教程：BC610开发指南

sap po bussiness component

sap basis常用底表

workflow工作流前端 开源

activiti workflow框架

flowable6.5

odoo 用的 流程控制的框架是什么

工作流java啥意思

activiti工作流的参考文献有哪些

流程引擎python

绘制一个简单的uml层图

我想学习工作流引擎，应该从哪里着手

flowable bpmn

sap abap c#

oracle soa suite 12c handbook

中国石油大学(北京)克拉玛依校区在广东2021-2024各专业最低录取分数及位次表.pdf

浙江越秀外国语学院在广东2021-2024各专业最低录取分数及位次表.pdf

最新资源

workflow工作流前端开源

odoo 用的流程控制的框架是什么