Download pdf - Workflow Forms

Transcript
Page 1: Workflow Forms

Using Forms inWorkflows andGuided Procedures

Page 2: Workflow Forms

Forms in Guided Procedures

Overview

Forms in SAP Business Workflow

Summary and Appendices

Page 3: Workflow Forms

Business Task Management in SAP NetWeaverSAP Interactive Forms by AdobeGuided Procedures and SAP Business Workflow

Overview

Page 4: Workflow Forms

SAP AG 2006, / 4

Business Task Management in SAP NetWeaver

User ProductivityEnablement

Running an EnterprisePortal

Enabling UserCollboration

Business TaskManagement

Mobilizing BusinessProcesses

Enterprise KnowledgeManagement

Data Unification Master-Data Harmonization Master-Data Consolidation Central Master-DataManagement Enterprise Data Warehousing

Business InformationManagement

Enterprise Reporting, Query, andAnalysis

Business Planning and AnalyticalServices Enterprise Data Warehousing

Business EventManagement Business Event Resolution Business Task Management

End-to-End ProcessIntegration

Enabling Application-to-ApplicationProcesses

Enabling Business-to-Business Processes

Business ProcessManagement

Enabling PlatformInteroperability

Business TaskManagement

Custom Development Developing, Configuring, and Adapting Applications Enabling Platform Interoperability

Unified Life-CycleManagement Software Life-Cycle Management SAP NetWeaver Operations

ApplicationGovernance & Security Authentication and Single Sign-On Integrated User and Access Management

Consolidation Enabling PlatformInteroperability SAP NetWeaver Operations Master-Data Consolidation Enterprise Knowledge

Management

Enterprise ServiceArchitecture – Design &Deployment

Enabling Enterprise Services

IT Practices IT Scenarios

On the concept of IT Practices and IT Scenarios…

Page 5: Workflow Forms

SAP AG 2006, / 5

1995

EP 5.0

2003

SAP NetWeaver ‘04

SAP NetWeaver 2004s

BusinessWorkflow

UniversalWorklist

+ CollaborationTasksBPM

+ GuidedProcedures

Business Task Management is Evolutionary

+ Third Party

Duet,UWL API

Page 6: Workflow Forms

SAP AG 2006, / 6

What Is the Current Situation for Managers?

Susan F.Motivateemployees

Performspecific

tasks Control andreduce costs

Managebudgets

Performbudget andheadcountplanning

Initiatepersonnel

data changes

Triggerprocesses

Delegatetasks

Recruit theright people

Identify andreward topperformers

Writeperformance

appraisals

Page 7: Workflow Forms

SAP AG 2006, / 7

Business Task Management Components

Universal WorklistSingle point of access for managing your workCan be personalized to suit each user’s working styleProcess-specific views can be customized for expert users

Collaboration TasksEnables end-users to create their own ad hoc processes and drive collaborationIncludes various types of collaboration tasks including actions, approvals, and feedbackUsers track progress of their delegated task

Guided ProceduresDesigned to implement process flows with greater ease and speed across multiple applicationsIntegrates backend system transactions and interactive formsIncludes process templates that can be easily re-used or copied and easily changed

Interactive FormsGenerate forms that contain data extracted from core systemsUse dynamic or static formsAccelerate forms-based business processes

SAP Business WorkflowStructured, repeatable, simple to complex business processManages the tasks that need to be performed and who should perform the tasksEnsures business process deadlines and service agreements are appropriately monitored and enforced

AlertsException-triggered notificationsDefine follow-on activitiesInter-System alerting

DuetProcesses in Microsoft Outlook

Page 8: Workflow Forms

SAP AG 2006, / 8

Business Task Management – Definition

Business Task Management is the automation, executionand monitoring of tasks

Coordinate and execute tasks arising from automated process flowsand spontaneous eventsTrack the progress of tasks

Tasks include a wide variety of activitiesBusiness TransactionAlertFormDesktop DocumentImpromptu Request

Page 9: Workflow Forms

Business Task Management in SAP NetWeaverSAP Interactive Forms by Adobe

Guided Procedures and SAP Business Workflow

Overview

Page 10: Workflow Forms

SAP AG 2006, / 10

Understanding Forms

Forms typically offer a service, share knowledge, or collect andprovide answers.

A form is the document that an end user views or interacts with.

The form design specifies the layout, data capture, and finalpresentation rules for the form

No complex navigation or business rules

Page 11: Workflow Forms

SAP AG 2006, / 11

Challenges in Forms-Based Processes

Paper-based form processes have limitations.Error-prone and easily outdatedManual data re-entryProcess status is hard to trackHigh costs (e.g. production, storage)$30 million per year for a global organization*

Casual users (including executives) are typicallyunfamiliar with enterprise software.

Access to enterprise applications needs to beintuitive.

External users (suppliers etc.) are disconnectedfrom the process.

System-relevant data capture is cumbersome.

* GISTICS independent study, 2004

Page 12: Workflow Forms

SAP AG 2006, / 12

Key Capabilities

Integrate interactive PDF documents into businessprocesses driven by SAP applications

Allow forms-based input combined with workflowto start automated follow-up steps

Generate forms that contain data extracted fromSAP systems

Use dynamic or static forms

Complete forms online or offline

Submit data from the form back to SAP systems

Allow users to print forms

Interactive Forms based on Adobe Software

1

2

3

4

5

6

7

Page 13: Workflow Forms

SAP AG 2006, / 13

Improving Productivity with Interactive Forms

Eliminate process latency,duplication and errors inpaper forms

Integrate SAP applicationData

Support casual and mobileusers

Minimize training time

Get the job done faster,and at lower cost

Page 14: Workflow Forms

SAP AG 2006, / 14

Form Scenarios

Scenarios for capturing or displaying data in a Form1. Interactive forms

Users complete the form (online/offline)Select options online to submit the form data to a predefined processOptional Support for data validations

2. Non-interactive formsDesigned to present information to end usersPre-populated with dataData can not be added or modified

3. Print and fill formsEnd user opens and prints the formFills it out manuallyReturns it by fax or mail

Page 15: Workflow Forms

SAP AG 2006, / 15

SAP/Adobe Partnership

SAP/Adobe Strategic PartnershipSolution first available with SAP NetWeaver ‘04

Adobe providesOpen technology, de-facto standard for formsBenefits of combination of PDF with XML

Benefits of SAP/Adobe collaborationAdobe Reader installed on virtually all desktops“Natural” look and feel of formsUser-friendly forms design tool lowers cost of operationsIntegration of Adobe’s PDF technology into SAP solutionsInteractive Forms based on Adobe Software (Java - ABAP)Generation of forms to mass print, email or archive (ABAP)Linking of processes and Interactive Forms (Java – ABAP)

Page 16: Workflow Forms

SAP AG 2006, / 16

Where our Integration Starts?

Paper-like layoutSelf-explanatoryNatural look and feel

User HandlingSave locallyDistribute via email / PortalApply digital signaturePrint locally

Background ServicesStructured data in XMLPre-filled application valuesPre-filled list boxes, help values, …Automatic data extractionand integration in application

InteractivePDF

Page 17: Workflow Forms

SAP AG 2006, / 17

ABAP WorkbenchNetWeaver Developer Studio

Interactive Forms – Design Time and Runtime

Adobe Document Services

SAP NetWeaver Application Server

Adobe Document Services

Java PDF Object ABAP PDF Object

SAP J2EE Engine

Page 18: Workflow Forms

SAP AG 2006, / 18

Interactive Forms – Run-Time Architecture

Application Code (Java) Application Code (ABAP)

SAP NetWeaver Application Server

J2EE Stack ABAP Stack

Document ServiceEJB

Web Services

Adobe Document ServicesCore Components

PDF Object (ABAP)

Web Services

SOAP

SOAP

J2EE ABAPApplication Server

Adobe Document ServicesDB and OS Abstraction

Adobe LiveCycleDesigner

Adobe LiveCycleDesigner

PDF Object (Java)

Web Services

Page 19: Workflow Forms

SAP AG 2006, / 19

Adobe LiveCycle Designer

You are able to create the design of your form with the AdobeLiveCycle Designer.

The context elements that were bound to your form can bedragged and dropped onto the form layout.

1 2

3

Page 20: Workflow Forms

Business Task Management in SAP NetWeaverSAP Interactive Forms by Adobe

Guided Procedures and SAP Business Workflow

Overview

Page 21: Workflow Forms

SAP AG 2006, / 21

Execution of Business Task Management

Task 1

TASK MANAGEMENT UI (Universal Worklist)

Task 2

Events trigger tasks(workitems, notifications)

User Interactionwith BPM Runtime

Stable Processes

Human InteractionCollaborative ProcessesAd Hoc Processes

Dynamic Processes

Task x

BPM RUNTIME

Collaboration tasks

Guided Procedures

Business workflows

Page 22: Workflow Forms

SAP AG 2006, / 22

Business Department

“We need to supplementthe companies coreprocesses with ourown departmentalprocedures.”

Central IT

“We need to createflexible, robust andhighly scalablestandardized processes”

Individual

“I want to delegatesome of my tasksto colleagues, andtrack their progress.”

Centralized vs. Decentralized Process Control

Page 23: Workflow Forms

SAP AG 2006, / 23

Business Department

“We need to supplementthe companies coreprocesses with ourown departmentalprocedures.”

Central IT

“We need to createflexible, robust andhighly scalablestandardized processes”

Individual

“I want to delegatesome of my tasksto colleagues, andtrack their progress.”

Centralized vs. Decentralized Process Control

SAP NetWeaverTM

Guided Procedures

Collaboration Room

Unbounded Processes

Embedded Processes

SAP NetWeaverTM

Programmed Processes

Collaboration Tasks

SAP NetWeaverTM

Page 24: Workflow Forms

SAP AG 2006, / 24

You have developer resources toassist with emailing out forms foroffline usage and creating WebDynpros for form rendering online.

When the form is involved in aprocess that accesses severalbackend systems. For example,the form is used in CRM and ERPand SRM and various people willinteract with the various systemsthroughout the process.

You want to take existing workflowfunctions and render them in a formrather than in the current UI.

When the process should emailforms and wait for a reply, or whena form filled in offline shouldinitiate a process.

You are already familiar withBusiness Workflow.

You want a simple offline scenarioand you have no developmentresources available to you.

Users normally work online andwant to process the forms via theirUniversal Worklist.

Your users normally will processthe forms without connection tothe system.

Use BWF for interactiveforms when…

Use GP for interactive formswhen….

Guidelines for Interactive Forms and processes – when touse what tool…

The process requires has strictreporting requirements on formapproval.

Page 25: Workflow Forms

Forms in Guided Procedures

Overview

Forms in SAP Business Workflow

Summary and Appendices

Page 26: Workflow Forms

Business Task Management in SAP NetWeaverSAP Interactive Forms by Adobe

Forms in SAP Business Workflow

Overview of SAP Business WorkflowUniversal Worklist BasicsSAP Interactive Forms Integration

Page 27: Workflow Forms

SAP AG 2006, / 27

automation and monitoring of business processes

providing appropriate business knowledge of how to performbusiness processes

active flow of informationbring the right information at the right time to the right peopledistribution of work according to business rulesexception handling and deadline monitoring

providing metrics on business processese.g. for benchmarking and continuous process improvement

Workflow Definition

Page 28: Workflow Forms

SAP AG 2006, / 28

Customer Workflows

Custom workflows workflow modellerCustomizable business triggers.Workflow-Wizards

Tool

SAP Workflows

Standard workflows ( more than 500)Shrink-wrapped / ´Best Practice´Customizeable

Stan

dard

Fast-path Implementation

Workflow in SAP NetWeaver

Comfortable workbenchAccelerateSAP

LiteratureTraining

User GroupsConsulting Partners

Page 29: Workflow Forms

SAP AG 2006, / 29

Roleresolution

rule

Org.structure

Task

Person

Position

Work-place

Group

Organi-zationalelement

Execute

Forward

Postpone

Cancel

Earliest start

Latest start

Latest end

Roles

Keystructure

Attributes

Methods

ABAP

Transaction

Functionmodules

OLE2

Objects

Work items

Event Work item

Functionmodule

Workflow

Publish &subscribe

flexible coupling

Events

TaskObjects

Actor

Events

Trigger

Workflow Engines - Composed Of:

Page 30: Workflow Forms

SAP AG 2006, / 30

Workflow Builder

DetailHeader

Steps

Step Types

Birds-eyeView

Information

Page 31: Workflow Forms

SAP AG 2006, / 31

Setting up the local task palette

New Workflow

Click here forMy workflows

Page 32: Workflow Forms

SAP AG 2006, / 32

Build Workflow

Drag & Drop

Detail(double-click)

Activate and Test buttons

Page 33: Workflow Forms

SAP AG 2006, / 33

Test-Execute Workflow in Business Workplace

1

2

34

Page 34: Workflow Forms

Business Task Management in SAP NetWeaverSAP Interactive Forms by Adobe

Forms in SAP Business Workflow

Overview of SAP Business WorkflowUniversal Worklist BasicsSAP Interactive Forms Integration

Page 35: Workflow Forms

SAP AG 2006, / 35

Many Systems, Many Inboxes

MySAP CRM

mySAP ERP

R/3

Page 36: Workflow Forms

SAP AG 2006, / 36

ISV/Third Party R/3

mySAP ERP

MySAP CRM

Universal Worklist in Central SAP Enterprise Portal

UWL items can include:Business Workflow AlertsCollaboration Tasks KM NotificationsGuided Procedure Actions

Page 37: Workflow Forms

SAP AG 2006, / 37

R/3

mySAP ERP

MySAP CRM

Universal Worklist and External Task

Task

NetWeaverWeb Application Server

Page 38: Workflow Forms

SAP AG 2006, / 38

First look at the Universal Worklist

UWL is part of the standard user end role, accessed via Home - Work

Hint: To Refresh your lists of tasks, use the dropdown menu near the Hide Preview link.

Process-specific views to display context-related columns or details

Page 39: Workflow Forms

SAP AG 2006, / 39

Typical Customer Landscape

Local Portal

MaryLee

UWLADS

SAP Business Suite (R/3…CRM)SAP Business Suite (ERP)

Non-SAP Software

ML005

LeeMary

Page 40: Workflow Forms

SAP AG 2006, / 40

R/3

R/3

MySAP CRM

Universal Worklist and External Task

Task

1. Workflow

Process ControlDeadlinesInvoke ServicesTask Dispatching

3. Task Definitions

User InterfaceContext access

2. Universal Worklist

Display TasksInvoke TasksGeneric Task Control

NetWeaverWeb Application Server

Page 41: Workflow Forms

SAP AG 2006, / 41

Launch Work Transaction

Parameterized launching forBSPiViewURLWeb Dynpro (Java or ABAP)SAP GUI (for HTML)

Page 42: Workflow Forms

SAP AG 2006, / 42

Launch Customization: ABAP Web Dynpro

XML Example<Action name="launchWebDynProABAP"handler="SAPWebDynproABAPLauncher“>

Launches anABAP WebDynpro

1

2

3

Page 43: Workflow Forms

SAP AG 2006, / 43

R/3

mySAP ERP

MySAP CRM

Launch Handler

Task

Launch Configuration:XML generated from

table SWFVISU or coded by hand

SWFVISU

NetWeaverWeb Application Server

Page 44: Workflow Forms

Business Task Management in SAP NetWeaverSAP Interactive Forms by Adobe

Forms in SAP Business Workflow

Overview of SAP Business WorkflowUniversal Worklist BasicsSAP Interactive Forms Integration

Page 45: Workflow Forms

SAP AG 2006, / 45

Adobe LiveCycle Designer

You are able to create the design of your form with the AdobeLiveCycle Designer.

The context elements that were bound to your form can bedragged and dropped onto the form layout.

1 2

3

Page 46: Workflow Forms

SAP AG 2006, / 46

InteractiveForm UI Element Properties

The InteractiveForm UI elementhas 2 properties that are valid forInteractiveForms.

enabled – this property must bechecked off if the form you arecreating is to be Interactive!

readOnly – set if you want anInteractive Form to become readonly.

onSubmit – if you have a submitbutton on the form, this eventmust be assigned an action/eventhandler.

Page 47: Workflow Forms

SAP AG 2006, / 47

Dataflow, Work items, Containers

Step 1

Step 3a

Step 3b

Step 4Step 2

Work Item

Work itemContainer

(local)

Workflow Item

WorkflowContainer(global)

Workflow Definition

Workflow runtime

Page 48: Workflow Forms

SAP AG 2006, / 48

Accessing Process Data in a Task

Workflow (modeling/customizing) Your task (program)

WorkflowContainer Your task

Work itemContainer

UWL

Work itemContainer

Data

Work

itemID

WorkflowContainer

Data

Data

1. Automatic

2. Automatic5. Automatic

4. Code

3. Aut

omati

c

Page 49: Workflow Forms

SAP AG 2006, / 49

workflowrawdata =wd_context->get_child_node(

'WORKFLOWRAWDATA' ).

CALL METHODWORKFLOWRAWDATA->GET_ATTRIBUTE

EXPORTINGNAME = 'WI_ID'

IMPORTINGVALUE = wi_id .

Accessing the Work Item Container

Every work item has a unique work item IDThis is passed to the work item execution service via the UWL

Page 50: Workflow Forms

SAP AG 2006, / 50

* Write the approved flag the workflow.CALL FUNCTION 'SAP_WAPI_READ_CONTAINER'

EXPORTINGWORKITEM_ID = WI_ID

IMPORTINGRETURN_CODE = rc

TABLESSIMPLE_CONTAINER = l_cont.

Reading the Work Item Container

The work item container is updatedThe work item is set to completed (and to ‘confirmed’ if this is required).This is typically performed in the Web Dynpro start method.

Page 51: Workflow Forms

SAP AG 2006, / 51

* Set the approved flag the workflow.

* Set the workitem completed and write resultsCALL FUNCTION 'SAP_WAPI_WORKITEM_COMPLETE'

EXPORTINGWORKITEM_ID = wi_id

TABLESSIMPLE_CONTAINER = l_cont.

Writing the Work Item Container and Completion

The work item container is updatedThe work item is set to completed (and to ‘confirmed’ if this is required).This is typically performed in the Web Dynpro submit method.

Page 52: Workflow Forms

SAP AG 2006, / 52

Web Dynpro Component Architecture

Business Logic

(Models)

ComponentController

Model 1

Model 2

Contains Usagedeclarations

Usa

ge d

ecla

ratio

ns

W e b D y n p r o C o m p o n e n t

Components

CustomController

Component Interface

InterfaceController

Interface view

WindowWindowController

ViewLayout

ViewController

M

M

M

M

M

Interface view

SAP Web Dynpro uses principles of MVC paradigm

Controller handlethe user input andsteers theapplication

Views define thelayout

Model holds andprovide thebusiness logic

Page 53: Workflow Forms

SAP AG 2006, / 53

WindowView ControllerView

View Controller

Outbound Plug

Web Dynpro Plugs and Navigation

ViewCreateAction

OUT

IN

OUT

IN

IN

OUT

Update Workflow

Page 54: Workflow Forms

Forms in Guided Procedures

Overview

Forms in SAP Business Workflow

Summary and Appendices

Page 55: Workflow Forms

Forms in Guided Procedures

Business Task Management in SAP NetWeaverSAP Interactive Forms by AdobeUnderstanding Guided ProceduresIntegrating Forms in Guided Procedures

Page 56: Workflow Forms

SAP AG 2006, / 56

Composite Applications: a Business View

End-user characteristics

Rich user experience

Process context and visibility

Integrated multisource content

Enterprisewide collaboration

High flexibility

Composite Applications are user centric applications supportinghighly collaborative and dynamic business processes which spanbeyond functional, system, and organizational boundaries.

Composite Applications are user centric applications supportinghighly collaborative and dynamic business processes which spanbeyond functional, system, and organizational boundaries.

Efficiency

Flexibility

Analytics

Knowledge

Transactions

Collaboration

Office Client

Portal

Mobile

Page 57: Workflow Forms

SAP AG 2006, / 57

Composite Applications: a Technical View

Technical characteristics

Usage- and process-centric

Based on services

Loosely coupled to backend systems

Abstracting from backend systems

Dependent on service enabling

Composite Applications make use of data and functions provided asservices by platforms and applications, combining these into user-centric processes and views, supported by own business logic andspecific user interfaces.

Composite Applications make use of data and functions provided asservices by platforms and applications, combining these into user-centric processes and views, supported by own business logic andspecific user interfaces.

Page 58: Workflow Forms

SAP AG 2006, / 58

Guided Procedures and Composite Applications

ServiceEnablement

Services Services Services

mySAP CRM SAP NW BI mySAP ERP

Services

UI BuildingBlocks

BusinessProcesses

(Composites))

CompositeProcess<<Step>>

CreatePatient

<<Step>>Request

Appointment

<<Step>>Create

AppointmentYes <<Step>>

NotifyPatientExists?

No

<<Step>>Find Patient

BusinessLogic

ServiceDevelopment

ServiceComposition

User InterfaceName

Title

Check

WorkcenterRole 1 Role 2

Actions

Page 59: Workflow Forms

SAP AG 2006, / 59

Modeling Processes with Guided Procedures

Guided Procedures enables fast and easy implementationof collaborative user-centric business processes acrossheterogeneous environments by seamlessly integratingexisting and new backend system transactions, servicesand applications into the business process context.

Page 60: Workflow Forms

SAP AG 2006, / 60

Process Building Blocks

Reusable Components

Callable Objects

Process Instance

Phase Phase Phase …Block Block Block ...

StepAction

StepAction

n-StepsBlock

…...

VC UIs Adobe Forms Web Services CAF Services …

Process TemplateRuntime

Design Time

Business Users

Developers

Page 61: Workflow Forms

SAP AG 2006, / 61

Components of Guided Procedures

Guided Procedures are composed of…

Blocks:Blocks are the structural units that build a process in Guided Procedures.They are re-usable and may contain actions, nested blocks, or processes.Items in a block can be executed sequentially, in parallel, in a loop, or letthe user choose between several alternatives.

Actions:Actions are executable units that define a single step when implementedin a process template. Each action can refer to either one or two callableobjects – one for execution, and an optional one for display. Attaching acallable object to an action is a prerequisite for using it in a processtemplate.

Callable Objects:A callable object is an object that introduces an application or serviceinto the Guided Procedures framework. Callable objects manage theinvocation of the external service and enable its use within GPprocesses. In other words, callable objects are the units of execution inguided procedures.

Page 62: Workflow Forms

SAP AG 2006, / 62

Designing a Process

Page 63: Workflow Forms

SAP AG 2006, / 63

Top-down vs. Bottom-up Design

Process Building Elements(items)

Bottom

Up

Top

Dow

n

a) Create a process template

b) Create block(s)

c) Create action(s)

d) Create callable object(s)

d) Create a process templateand insert the block(s)

c) Create block(s) and insert theaction(s)

b) Create actions(s) and insertthe callable object(s)

a) Create callable objects(s)

Process Model

Page 64: Workflow Forms

SAP AG 2006, / 64

The GP Design Time Environment

The Gallery…

Actions(contextualnavigation

panel)

Filters

Objects

ContentManagement

GP Content

ObjectProperties

Folders

Page 65: Workflow Forms

SAP AG 2006, / 65

Designing a Process

CreateProcess

Template:Basic Data

DefineProcess

Flow

ActivateProcess

Consolidate Parameters

Define Due Dates

Define Built-in Roles

Grant Permissions

Configure Process Control Items

Grant View Permissions

Add Attachments

Required

Optional

MaintainRole

Defaults

Consolidate Roles

Configure Process Instantiation

Define Info Callable Objects

Add Interactive Forms

Select Views

Page 66: Workflow Forms

SAP AG 2006, / 66

Process Role Configuration

Processor of Action 2+ Processor of Action 3

= Consolidated Processor

• Which portal roles are assigned to which tasks?

• Can individual task roles be consolidated to single roles?

• When is user assignment to a role performed?

• Are their default users for particular tasks?

+ =

Page 67: Workflow Forms

SAP AG 2006, / 67

Designing a Block

Create Block:Basic Data

Create Block:Basic Data

ActivateBlock

Configure Exception Handling

Consolidate Roles

Grant View Permissions

Consolidate parameters

Add Info to Callable Objects

Add Attachments

Grant PermissionsRequired

Optional

Page 68: Workflow Forms

SAP AG 2006, / 68

Block Types

At runtime the user chooses one of the available alternatives andhis or her decision defines which item(s) is(are) executed.Alternatives

The items in the block are executed in a loop, but the loop criteriais checked after the last item has been executed. Thisguarantees that the items in the block will be executed at leastonce.

PostconditionLoop

The items in the block are executed in a loop, and the loopcriteria is checked before the execution of the first item.

PreconditionLoop

Multiple processors can be assigned to execute the items in thisblock type. For example, as a part of such a block, a survey canbe completed by multiple users and the results sent to the systemfor further processing. The items are executed in parallel.

ParallelDynamic

The items in the block flow are executed in parallel.Parallel

The items in the block are executed sequentially in the order thatyou have defined.Sequential

DescriptionBlock Type

Page 69: Workflow Forms

SAP AG 2006, / 69

Designing an Action

Create Action:Basic Data

AttachCallableObjects

ActivateAction

Consolidate Parameters

Define Ad-Hoc Items

Add Info Callable Objects

Add Attachments

Grant Permissions

Define Due Date HandlingRequired

Optional

Page 70: Workflow Forms

SAP AG 2006, / 70

Types of Callable Objects

Guided Procedures provides a set of callable objectimplementations that you can use by simply configuringthem in the GP design time. These predefined callableobjects are of two main types:

Web Dynpro Component (GP Interface)Java Callable Object for Background Execution

The predefined callable objects are available in thelist of callable object categories that is displayed inthe first step of the procedure for creating callableobjects. To use a predefined object, you just selectit as a type from the relevant category.

Page 71: Workflow Forms

SAP AG 2006, / 71

Designing a Callable Object

CreateCallableObject:

Basic Data

DefineObject

ActivateCallableObject

Define Input

Define Output

Set Configuration

Grant Permissions

Test Callable ObjectRequired

Optional

Page 72: Workflow Forms

SAP AG 2006, / 72

Design Time Tools

Save a single object or all objects.

Activate the changes to your process and the objects within it.

Insert an appropriate existing object, or create and insert a new object, underthe selected level in the hierarchy. For example, you can insert a block in aprocess, an action or a block in another block, and a callable object in anaction. The Item drop-down is sensitive to the hierarchical context.

Revert to the last saved version.

Removes the selected object from the hierarchy.

Toggle to the display mode for the selected object, or for the selectedobject and for all levels in the hierarchy below and above it..

Toggle to the edit mode for the selected object, or for the selected objectand for all levels in the hierarchy below and above it..

Page 73: Workflow Forms

SAP AG 2006, / 73

Working in the Editor (I)

Work in the properties frame to changeor configure objects in the process flow

PropertiesTabs

Page 74: Workflow Forms

SAP AG 2006, / 74

Working in the Editor (II)

Click on the square next to anobject to select it and work with it

To insert either a new or existing object,select the correct place in the flow,make sure the appropriate object typeshows in the Item drop-down, and clickeither the Insert or the Create New icon.

Page 75: Workflow Forms

SAP AG 2006, / 75

Creating Callable Objects

Page 76: Workflow Forms

SAP AG 2006, / 76

Map Parameters

Mapping parameters allows the ouputs of oneaction to be used as inputs for another. Forour process, the data form outputs becomedecision step inputs.

Page 77: Workflow Forms

SAP AG 2006, / 77

GP Runtime

Page 78: Workflow Forms

SAP AG 2006, / 78

Edit Process Roles

Page 79: Workflow Forms

SAP AG 2006, / 79

Launch the Process

Page 80: Workflow Forms

SAP AG 2006, / 80

Navigation in the Process Instance

Page 81: Workflow Forms

SAP AG 2006, / 81

Your Exercise ScenarioTop-Down Modeling

1. Create Business PartnerProcess

2. Create action(s) and insert thecallable object(s)

3. Create form to start theprocess

Createbusiness

partner

Readbusiness

partner

Displaybusiness

partner in WebDynpro form

Business Partner Process

ERP: M10

BAPI: Create BPBAPI: Display BP

Page 82: Workflow Forms

SAP AG 2006, / 82

Parameter mapping between the actions

Page 83: Workflow Forms

Understanding Guided Procedures

Forms in Guided Procedures

Forms in Guided Procedures

Page 84: Workflow Forms

Forms in Guided Procedures

Business Task Management in SAP NetWeaverSAP Interactive Forms by AdobeUnderstanding Guided ProceduresIntegrating Forms in Guided Procedures

Page 85: Workflow Forms

SAP AG 2006, / 85

Adobe LifeCycle Designer

Layout Editor

Palettes

Page 86: Workflow Forms

SAP AG 2006, / 86

Button properties in the Submit tab

Control Type –type SubmitSubmit Format – format XML Data (XML)Submit to URL %com.sap.caf.gp.if.PostProcessorUrl%

Page 87: Workflow Forms

SAP AG 2006, / 87

Runtime from the End User Perspective

1. Open PDF form

2. Fill in data field

3. ValidationBusiness Partner formatRequired Fields Entered

4. Click Submit

5. Success Message

HTTP

Page 88: Workflow Forms

SAP AG 2006, / 88

Interactive Form Callable Object: Basic Data

Open the gallery, and choose Create Callable Object from thecontextual panel.

From the Type list, select Form Interactive Form and enter therequired basic data

Page 89: Workflow Forms

SAP AG 2006, / 89

Interactive Form Callable Object: Define Object

Specify the XDP Template filecreated with the Adobe LiveCyclesoftware

Page 90: Workflow Forms

SAP AG 2006, / 90

Interactive Form Callable Object: Define Input viaPrefilling

Form template input parameters are parsed anddisplayed as read-only

You can definePrefilling Service

parsed

Page 91: Workflow Forms

SAP AG 2006, / 91

Interactive Form Callable Object: Define FormValidation

mapping FormService

Error Handling

Page 92: Workflow Forms

SAP AG 2006, / 92

Interactive Form Callable Object: Configuration

Enable Use in Guided ProceduresCreate an Offline Interactive Formand send it by e-mailCreate an Interactive Form andComplete Process Step

Enable Use as StandaloneInteractive Form

Send to Processor via E-MailStart a Process on CompletionDefine Standalone Form TimeoutProvide an ImpersonalizedInteractive Form

Page 93: Workflow Forms

SAP AG 2006, / 93

Features of Adobe Interactive Forms in GP

Enable the use of theinteractive form within a GP

process. The form is exposedas a callable object that isexecuted in background

mode. The timeout of the formis handled automatically by

the GP framework.

Page 94: Workflow Forms

SAP AG 2006, / 94

Features of Adobe Interactive Forms in GP

The form is generatedfrom the form template,and is sent as an offline

interactive form by e-mail.

Page 95: Workflow Forms

SAP AG 2006, / 95

Features of Adobe Interactive Forms in GP

The interactive form isgenerated from the form

template, and stored in theprocess context.

Optionally, you canconfigure the form to be

sent by e-mail to theprocessor. To do that,enable option Send to

Processor by E-Mail. Youcan choose the template for

the e-mail using “ChooseTemplate”.

Page 96: Workflow Forms

SAP AG 2006, / 96

Features of Adobe Interactive Forms in GP

Enable the use of aninteractive form

independently of a GPprocess. Standalone formscan by processed offline, or

accessed by an URL, andare either personalized or

impersonalized

Page 97: Workflow Forms

SAP AG 2006, / 97

Features of Adobe Interactive Forms in GP

The processor will receivean email upon successful

post-processing of theinteractive form.

You can choose thetemplate for the e-mail

using “Choose Template”.

Page 98: Workflow Forms

SAP AG 2006, / 98

Features of Adobe Interactive Forms in GP

Select a processtemplate that will be

initiated uponsuccessful post-processing of theinteractive form.

Page 99: Workflow Forms

SAP AG 2006, / 99

Features of Adobe Interactive Forms in GP

Define timeout for thestandalone interactiveform. If the form is not

returned to the system forpost-processing beforethe timeout expires, it

gets invalidated.

Page 100: Workflow Forms

SAP AG 2006, / 100

Features of Adobe Interactive Forms in GP

Create an impersonalizedform that is not

associated with aparticular user session,

and may be submitted tothe system multiple times

Note: You cannot use Impersonalized Forms as a step in a process

Page 101: Workflow Forms

Forms in Guided Procedures

Overview

Forms in SAP Business Workflow

Summary and Appendices

Page 102: Workflow Forms

SAP AG 2006, / 102

THANK YOU FOR YOURATTENTION !

QUESTIONS – SUGGESTIONS – DISCUSSION

Page 103: Workflow Forms

SAP AG 2006, / 103

Please complete your session evaluation.

Be courteous — deposit your trash,and do not take the handouts for the following session.

Feedback

Thank You !

Page 104: Workflow Forms

Appendix: Tasks for the GPAdministrator

Screenshots from Web Dynpro workflow

Page 105: Workflow Forms

SAP AG 2006, / 105

Impersonalized Forms in the Administration workset

•Impersonalized form templates created in GP design time appear underImpersonalized Forms in the Administration workset

Page 106: Workflow Forms

SAP AG 2006, / 106

Visual Administrator: GP configuration parameters

You can edit the service caf/eu/gp/model (GP configuration parameters) using theVisual Administrator.There choose Cluster Server caf/eu/gp/model.

Page 107: Workflow Forms

SAP AG 2006, / 107

Configuration of GP for Adobe forms (Slide 1 of 2)

Configuration Tasks for SAP NetWeaver Administrator

SLD Data Supplier service is configured to connect to a systemwhere the Adobe Document Services (ADS) server is enabled

HTTP settingsCIM client generation setting

Page 108: Workflow Forms

SAP AG 2006, / 108

Configuration of GP for Adobe forms (Slide 2 of 2)

Configuration Tasks for SAP NetWeaver AdministratorWeb Services Security service settings for the ADS Web Service client

Page 109: Workflow Forms

Appendix: Tasks for the GPAdministrator

Screenshots from Web Dynpro workflow

Page 110: Workflow Forms

SAP AG 2006, / 110

Web Dynpro and Workflow: WI_ID Parameter

Page 111: Workflow Forms

SAP AG 2006, / 111

Web Dynpro and Workflow: HANDLESTART method

Page 112: Workflow Forms

SAP AG 2006, / 112

Web Web Dynpro and Workflow: HANDLESTART Code

Page 113: Workflow Forms

SAP AG 2006, / 113

Web Dynpro and Workflow: PDF object

Page 114: Workflow Forms

SAP AG 2006, / 114

Web Dynpro and Workflow: LiveCycle Designer

From DDICprocstate

Page 115: Workflow Forms

SAP AG 2006, / 115

Web Dynpro and Workflow: SentToWorkflow

Page 116: Workflow Forms

SAP AG 2006, / 116

Web Dynpro and Workflow: SendToWorkflow code

Page 117: Workflow Forms

SAP AG 2006, / 117

Web Dynpro and Workflow: Application

Page 118: Workflow Forms

SAP AG 2006, / 118

Copyright 2007 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. Thislimitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.


Recommended