SAP workFlow handbooks

W

ORKFLOW

It is the automation of business procedures during which documents, information or tasks are passed from one participant to another in a way that is governed by rules or

procedures.

A

DVANTAGES OF USING

W

ORKFLOW

a. Duration of the process is reduced dramatically.

b. The process definition becomes transparent i.e. everyone knows what they are doing and why.

c. Each process instance is transparent. During the process run and afterwards you can track who did what, when.

d. The process is under control. We can change the definition on the fly to improve it or react to sudden changes in the environment.

S

TEP

T

YPES

ACTIVITY Execution of a task. This task can be a single-step task or a Multistep task WEB ACTIVITY The selected container elements are posted using the http protocol in an XML

or SOAP message. This step can also wait for a message reply. DOCUMENT

FROM TEMPLATE Step type in a workflow definition for creating documents on the basis of user-defined templates at runtime. The documents can be created with programs that are installed on the local PC and are OLE-compatible, 32-bit, Windows applications (for example Microsoft Word 97).

LOOP (UNTIL) Repeated processing of steps within the workflow definition. UNTIL and WHILE are available as loop types.

LOOP (WHILE)

Step type in a workflow definition for processing a sequence of steps

repeatedly at runtime as long as the comparisons defined in the step

definition apply. To make the decision, the workflow system checks

the value of a basis of comparison (= expression from the workflow

container) against the defined comparison values.

The first check is

made before the loop is processed.

SEND MAIL

The text entered in this step type is sent as an E-Mail. The task

required and the necessary bindings are automatically created by the

workflow system.

CONDITION

Step type in a workflow definition to execute one of two defined paths

in the definition. ("Two-way fork"). The Workflow system decides on

the path on the basis of the defined conditions and information

contained in the Workflow container as values.

You define conditions using the conditions editor, which allows you to

define complex and multilevel conditions.

MULTIPLE

CONDITION

Step type in a workflow definition to process one of more defined

_{branches of the workflow definition at runtime. This is based on}

information from the context of the workflow or the objects

processed. The value of the basis of comparison (expression from

workflow container) is checked against the comparison values defined.

EVENT CREATOR

_{Step type in a workflow definition to create an event at runtime}

WAIT FOR EVENT The system waits for a specified event. The workitem is only completed if the expected event occurs. Data from the event container can be sent to the workflow container using a binding.

CONTAINER

OPERATION

Step type in a workflow definition for performing elementary

_{arithmetic operations or value assignments on individual elements of}

the workflow container at runtime.

F

ORK Arrangement of independent steps in their own individual parallel processing branches. You can specify that only a proportion of the parallel processing branches has to be processed in order to continue the workflow afterwards. Parallel processing can be ended by the specification of a minimum number of branches to be processed or by the definition of a termination condition. UNDEFINED Step type without functionality which can be inserted as a placeholder in a

workflow definition. Undefined steps are always followed by an undefined event. Together they form a unit and therefore ensure the consistency of a workflow definition. The initial representation of a workflow definition contains an undefined step and an undefined event. Undefined steps can also be inserted whenever individual steps are required in a generated block but still need to be specified according to particular rules

PROCESS

CONTROL The functions Cancel work item or Set work item to obsolete are applied to other Work items of the current workflow. It will be useful to cancel any previous work item.

U

SER

D

ECISION In User Decision Title (Max. 80 Chars). 4 User parameters from workflow container can be substituted. [Substitution by position].

Ex : Title : Leave Approval Done by &Workflow Version& Sales Order Number &Customer No&

P1 : &Wf_Initiator& P2 : &WF_Version&

P3 : &Sales.Salesdocument& P4 : &Sales.OrderingParty. Customer No& Result :

Title : Leave Approval done by US KAAV02 workflow Version0000 Sales Order No. 7343 Customer No. 470.

AD

H

OC

A

NCHOR U specify workflows that can replace this step. At runtime, an authorized user can select one of the specified workflows. The steps of this workflow then dynamically replace the Ad Hoc Anchor.

S

UB

W

ORKFLOW An activity that refers to another workflow rather than a task. A binding from the workflow container interfaces with the sub-workflow container.

M

ACROS (INCLUDE <CNTN01>)

For Declaring Purpose:

BEGIN_DATA << Start of the object declaration >> END_DATA << End of the object declaration >>

For Attributes:

GET_PROPERTY <Attr.> CHANGING CONTAINER Start of a virtual attribute implementation

GET_TABLE_PROPERTY <TABLE NAME>

Start of the database attribute implementation

END_PROPERTY. - End of an attribute implementation.

For Method:

BEGIN_METHOD <METHOD> CHANGING CONTAINER Start of a method implementation

END_METHOD - End of a method implementation For Object Key

SWC_SET_OBJECTKEY <Object Key>.

Sets the object key of the current object. Usually only instance independent methods use this to return a reference to an object instance of the current object.

M

ACROS FOR

M

ETHOD

E

XCEPTIONS

E

XIT

_O

BJECT

_N

OT

_F

OUND Tells workflow that an object does not exist.

E

XIT

_C

ANCELLLED

Tells workflow that the user cancelled execution Of a method

E

XIT

_R

ETURN<EXCEPTION><MSG VAR1> <MSG VAR2> <MSG VAR3> <MSG VAR4> Tells workflow that an error has occurred.

E

XIT

_N

OT

_I

MPLEMENTED

Tells workflow that a method is not implemented.

E

XIT

_P

ARAMETER

_

NOT

_

FOUND Tells workflow that a mandatory parameter of a Method is missing.

M

ACROS TO

P

ROCESS A

C

ONTAINER SWC_CONTAINER <CONTAINER>

Declares a container

SWC_CREATE_CONTAINER <CONTAINER>

Initializes a container. The macros SWC_RELEASE_CONTAINER and SWC_CLEAR_CONTAINER have the same functions.

M

ACROS TO PROCESS ELEMENTS FROM THE CONTAINER

SWC_GET_ELEMENT <Container> <Container Element> <Variable> Read Single value element from the CONTAINER INTO A VARIABLE. SWC_SET_ELEMENT <Container> <Container Element> <Variable>

Write single value element from a VARIABLE TO THE CONTAINER. SWC_GET_TABLE <Container> <Container Element> <Internal Table>

Read Multiline element from the container into an internal table.

SWC_SET_TABLE <Container> <Container Element> <Internal Table> Write Multiline element from an internal table to the container.

SWC_COPY_ELEMENT <Source Cont.> < Source Cont.Ele.> <Target Cont.> <Target Cont. Ele.>

Copies a container element from a source container to a target container. SWC_DELETE_ELEMENT <Container> <Container Element>

Deletes a container element.

M

ACROS FOR CALLING OBJECT METHODS

SWC_CALL_METHOD <Object> <Method> <Containter>

Calls the method of an object. All parameters are passed to / from the method as contents of the container.

M

ACROS FOR PROCESSING OBJECT REFERENCE

SWC_CREATE_OBJECT <Object> <Object Type> <Object Key> Create an object reference from an object type and object key. SWC_REFRESH_OBJECT <Object>

Invalidates the object reference buffer so that all attributes will be recalculated when they are next called.

SWC_GET_OBJECT_KEY <Object> <Object Key>

Returns the object key of an object reference. Used in generic object programming.

SWC_GET_OBJECT_TYPE <Object> <Object Type>

Returns the object type of an object reference. Used in a generic object programming.

M

ACROS FOR DELEGATION

SWE_SET_DELEGATION To delegate. FUNCTION MODULES  RH_ACT_LEADING_POSITION  RH_GET_LEADING_POSITION  RH_GET_ACTORS (SUPERIORS)  RH_GET_ADDRESS

 SWX_GET_MANAGER - Gives the Superior(output from FM)of the user (input to FM).

 RH_GET_STRUCTURE

 SWD_WFD_REPLICATE_FROM_9999 (When Standard Wf is not there. Execute this Function Module with IM_TASK = Workflow Number)

O

RG

.

E

NVIRONMENT

RH_WF_OM_INDICES_TIMESTAMP_RFS Resets the timestamp on all HR buffers RH_TASK_INBOX_VIEW_REFRESH Refreshes the buffer for the current user only RH_TASH_AGENTS_INDEX_REFRESH Refreshed the buffer for a particular task ID only

W

ORKFLOW

C

ONTAINER

E

LEMENTS

(D

EFAULT

)

_Adhoc Objects Adhoc Objects of workflow Instance _Attach Objects Attachments of workflow instance _WF_Initiator Initiator of workflow instance

_Wf_priority Priority of workflow instance

_Wi_group_id Grouping characteristics for workflow instance _Workitem Workflow Instance

_Wf_version Definition version of this workflow instance

E

VENT

C

ONTAINER

E

LEMENTS

(D

EFAULT

)

_EVT_OBJECT Object

_EVT_OBJTYPE Object Type _EVT_NAME Event of an Object _EVT_OBJKEY Key Element _EVT_RECEVIER_ID _EVT_CREATION_DATE _EVT_CREATION_TIME

E

VENT

T

RIGGERING

F

UNCTION MODULE SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT(External Commit)

(1). The ID of the event,

(2). The ID of the triggering object type

(3). The object type-specific key  passed as import parameters

(4) the event container  a table parameter.

Special cases, use: SWE_EVENT_CREATE_IN_UPD_TASK or SWE_EVENT_CREATE_FOR_UPD_TASK

SWW_WI_START_SIMPLE this function module is used to trigger workflow without BOR by passing the WF NO directly.

SWEC - Change documents When change documents are written

Status changes of objects which are logged as change

documents are reported automatically as events as well.

(W) BSVW- General Status Mgt.

Event creation upon status changes The system automatically creates an event for objects that use general status management when an object status changes. Table: CDHDR

Message control

Event creation as message type SWUY, SE91

Events can be created via a connection to Message Control.

For this, you must create a separate output type and declare 9 (workflow event) as transmission medium. AWUW - Logistics Info. System

(LIS)

When an exception situation occurs (LIS exception)

The occurrence of an exception situation defined within the LIS as an exception is to cause an event to be created. (W)

SWU_EWBTE - Business

Transaction Events It is not related to Business Object Events. They triggered from Financial Applications, such as G/L accounting and accounts receivable / payable accounting in R/3. and are used to notify other parts of the system of operations being performed in financial accounting, such as a document being created.

SWEHR1/2/3 - HR Master Data

When HR master data changes Must carry out the following Personnel Management Customizing activities: IMG under Personnel Management Global Settings in

WORKFLOW AFFECTED TABLES

TADIR - Directory of Repository Objects (All WF can be viewed here by giving PgID - R3TR and Obj - PDWS)

TDEVC - Development Class TOJTT - Objects Text Basic Data

TOJTB - Business Object Repository: Basic Data (Object Definition) TOJTD - Customizing Object Types (Delegation)

T7791 - Assignment to SAP Organizational Object Type BDCP - Change Pointer

CDHDR - Change Document Header CDPOS - Change Document Items SWECDOBJ - Events for Change Document SWECDVALUE - Field (Values) for Event Linkage SWWWIAGENT- Agents for Execution of a Work Item

SWDSHEADER - WF. Definition Basic Data (To find WF created Date) SWD_WFCONT- WF. Definition Container

SWWBINDEF - Obsolete - Workflow Runtime(Save Binding Definitions) SWWUSERWI - Current work items assigned for a user.

SWWWIAGENT- Agents for Execution of a work Item. SWFAWRKITM - WF. Work Item for Reporting (Structure) DM40L - DM Data Model

SWW_OUTBOX -Lists Workflows in outbox together with status SWW_CONT -Container Contents for Work Item Data Container

SWW_CONTOB -Container Cont. for Work Item Data Container (Only Objects) SWWLOGHIST -History of a work item

SWWORGTASK -Assignment of WIs to Org.Units and Tasks SWWUSERWI -Current Work Items Assigned to a User

SWWWIHEAD -Header Table for all Work Item Types (To find WI created Date) SWWWIRET Workflow Runtime: Return Values of Method Call

SWWWIDEADL Workflow Runtime: Deadline Data for Work Items SWEINSTCOU Instance Linkage Event – Receiver

SWZAI Header Table for all Properties of a Work Queue SWZAIENTRY Object Table for Work Queues (Entries)

SWPSTEPLOG Workflow: Instance Data of Steps of a Workflow Execution HRUS_D2 User Substituted by User

SWDSCONT WF Definition (You can delete a Work Flow here but not a good Practice)

R

EPORTS

 RSWWWIDE – Delete work items (SWWL)  RHSOBJCH - fix PD Control Tables

 RSWUWFML/ RSWUWFML2 - sends an e-mail to an external Internet address to notify the user of new work items.

 RSWNSENDMAIL1 – Send E-Mail to external Id with Subject and Content  RSWELOGD - Delete Event Trace

WORKFLOW TRANSACTIONS

 AWUV Wizard for event creation Def.tools  Event creation  Set up with wizard  MCA1 Workflow Info. System Reporting  Workflow Information System (WIS)  OOAW Evaluation paths

 SWLV View for maintaining Views  PFAC Maintain standard roles

 PFOM Maintain assignment to SAP organizational objects Definition tools  SAP

org. objects  Create assignments

 PFOS Display assignment to SAP organizational objects Definition tools  SAP org. objects  Display assignments

 PFSO Organizational environment of a user  PFT Maintain customer task

 PFTC General task maintenance

 PFTC_DEL Tcode to delete Task/Workflow

 PFTC_INS, PFTC_CHG, PFTC_DIS, PFTC_COP – Task (Std. WF)  PFAC_INS, PFAC_CHG, PFAC_DIS, PFAC_DEL – Role Resolution  PPOCW – Create Organizational Plan

 PFTR Standard task for transaction  PFTS Standard task

 PFWF Maintain workflow task (customer)  PFWS Maintain workflow template

 PPOC Create organizational plan Def. tools  Organizational plan  Create  PPOCM Create

 PPOWM Create for Workflow  PPOME Change

 PPOSE Display

 PPOM Maintain organizational plan Def. tools  Organizational plan  Change  PPOS Display organizational plan Def. tools  Organizational plan  Display

EXPERT MODE FOR ORGANIZATIONAL UNIT CREATION  PO10 Org. Unit

 PO01 Work Centre  PO03 Job

 PO13 Position  PFCT Task Catalog  PP01 General Plan Data.

 SWF4 Work flow wizard repository  SWDA Alphanumeric Workflow Builder  SWDC Workflow editor administration data

 SWDM Business Workflow Explorer Def. tools  Business Workflow Explorer  SWDD Workflow Builder

 SWDB WF Builder Create  SWDS WF Builder Selection

 SWDD_CONFIG WF Builder Configuration

 SWE2 Event type linkage Utilities  Events  Type linkages

 SWE3 Type Instance linkages Utilities  Events  Instance linkages  SWE4 Switch event log on/off Utilities  Events  Event/log  On/Off  SWEC Link change documents to events Definition tools  Event creation 

Change documents  Linkage

 SWED Assignment of change document objects to object types Definition tools 

 Event creation  Change documents  Define workflow properties

 SWELS Switch Event Trace On/Off  SWF3 Workflow Wizard Explorer  SWF4 Workflow Wizard Repository

 SWI1 Selection report for workflows Utilities  Work item selection  SWI2 Work item analysis Reporting  Work item analysis

 SWI2_DURA To find duration of work item.

 SWI3 Workflow outbox Runtime tools  Workflow outbox  SWI4 Task analysis Reporting  Task analysis

 SWI5 Workload analysis Reporting  Workload analysis  SWI6 Object links Runtime tools  Object links

 SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox  SWI8 Error overview Part of administration of workflow runtime system

(transaction SWUF)

 SWL1 Settings for dynamic columns Customizing, part of ongoing settings  SWLC Check tasks for agents

 SWLD Workbench for Workflow 4.0  SWLP Copy plan version

 SWLV Maintain work item views Customizing, part of ongoing settings  SW01 Business Object Builder Definition tools  Business Object Builder  SW06 Customizing object types – Delegation / SWE_SET_DELEGATION  SWU0 Event simulation Utilities  Events  Simulate event

 SWU2 RFC monitor Utilities  Workflow RFC monitor

 SWU3 Customizing consistency check Utilities  Customizing  SWU4 Consistency check for standard tasks

 SWU5 Consistency check for customer tasks  SWU6 Consistency check for workflow tasks  SWU7 Consistency check for workflow templates  SWU8 Switch technical trace on/off

 SWU9 Display technical trace  SWUD Diagnostic tools

 SWUE To trigger manually

 SWUF Runtime system administration Administration  Runtime system  SWUI Start workflows

 SWUS Test Work flow

 SWUY Wizard for message linkage to workflow  SWUP Switch SAP Forms Trance On / Off  SWUR Send Mails for workitems

 SWUT Namespace for Form Transactions  SWUU SAP Forms : Diagnosis

 SWUV Send E-Mail Notifications

 SWUW Number Range Maint. SWW_WIID.  SWUX SAP Forms Administration

 SWUY Work Flow Message Linkage  SWU10 – Delete Workflow Trace  SWUA Start verification workflow  SWUB Maintain WF RFC Destination  SWUC Customizing Decision Task  SWUD Workflow Diagnosis

 SWUE Trigger an Event

 SWUG Generate workflow start transaction  SWUI Start Workflow

 SWUK Mapping from Type E-Mail address  SWUL Customizing : Process Administration

 SWUN Number Range Maintenance : Form Absenc  SWX1 Create notification of absence

 SWX2 Change notification of absence  SWX3 Display notification of absence  SWX4 Approve notification of absence  SWXF Form applications: out form 

 SWL1 Dynamic Columns

 SWPC Continue Workflow After error  SWPR Restart After Error  SWB_COND Initial Condition  SWI2_DIAG Diagnosis of Errors  SW12_FREQ – Workitem analysis

 SWI1_RULE – Execute Agent rules for workflow  BSVW – Event creation during status change  SCDO – Change document object overview  SWXML – Display Web Flow XML Documents

 SWR_WEBSERVER – Specify ITS Web Server for Web Flow  SWUU – SAP Forms Diagnosis

 SWI30 – Unlock Workflow  SWI5 – Workload analysis

AGENTS

• Agents are the people

who may execute

a workflow task

• “Possible Agents” are those users who are authorized to start and execute a task, but may not be the “selected agents”

• “Responsible Agents” are the people you want to execute a specific workitem

• “Excluded Agents” are people you do NOT want to execute the workitem, even though they are a possible or a responsible agent. For example, a

person who is

responsible for

approving travel

expenses should

probably not be allowed to approve their own travel expenses

Difference between Database Field Attribute and Virtual Attribute:

Virtual Attribute Database Field Attribute

1. No field content in the database corresponds to this attribute

2. Its value is established by evaluating what may be complex database contents at runtime.

3. It generally applies that multi-line attributes

1.Reference is made to a database field as the source of the required information 2. An attribute whose source is a database field can either return the database field contents or an object reference, which is automatically generated from the field content.

A

R

P

E

A

PPROVAL

P

ROCEDURE  Hierarchical Approval

 Dynamic Hierarchical Approval

 Extended Hierarchical Approval

 Parallel Approval

 Circular Approval

 Dynamic Circular

 Parallel Circular

 Dynamic Parallel Circular

HIERARCHICAL APPROVAL workflow, the first agent must agree, before the second agent can decide. Since the workflow can be terminated by any agent, it is very important that the hierarchy be respected (lower positions first, higher positions last).

EXTENDED HIERARCHICAL APPROVAL workflow is similar to a hierarchical Approval workflow, except that several users are involved at each approval level. Only some of them are authorized to actually approve or reject the object at each level. The other users are only authorized to propose that the object be approved or rejected.

DYNAMIC HIERARCHICAL APPROVAL WORKFLOW, the object type to be approved and the approval task are determined at definition time. However, the depth, and the number of approving users are determined dynamically at run time. Once a recipient does not approve the object, the recipients higher in the hierarchy do not receive the object for approval. PARALLEL APPROVAL WORKFLOW implements majority decisions of the form n from m. If the necessary number of n agreements required for an approval or rejection is reached, then the object is considered approved or rejected respectively.

CIRCULAR APPROVAL WORKFLOW can be used to send a circular (MS word document etc.) sequentially to several users (or positions, jobs, or organizations) who can view it and make comments if necessary. All the recipients of the circular are defined in the workflow definition.

DYNAMIC CIRCULAR WORKFLOW is similar to a circular approval workflow, except that the users who are to view the circular, are defined dynamically at runtime, rather than in the workflow definition.

PARALLEL CIRCULAR APPROVAL WORKFLOW is used to send a circular to several users. The recipients of the circular could be either defined in the workflow definition, or dynamically, at runtime.

DYNAMIC PARALLEL CIRCULAR APPROVAL WORKFLOW is used to send a circular to multiple users at the same time, for their information and approval. The list of recipients is not defined in the definition of the workflow. The list comes as a dialog box when the workflow is initiated, and the user dynamically selects the recipients.

BINDING

Binding involves the specification of assignment rules as to how the data is to be exchanged between two containers. At runtime, these binding definitions are executed, making workflow execution possible. The following are the possible binding definitions:

 Workflow container to Task container.

 Workflow container to Event container.

 Workflow container to Rule container.

 Task container to Workflow container.

 Task container to Rule container.

 Task container to Method container.

 Event container to Workflow container.

 Event container to Task container.

 Method container to Task container. TYPES OF WORKFLOW CONTAINER

o Event Container – Always output

o Workflow Container – import can be given o Task Container – o/p

o Method Container – i/p from workflow container & o/p through Task Container o Rule Container – i/p container

R

ULE BASED PROPOSAL FOR BINDING DEFINITIONS

The workflow system automatically makes proposals for the following binding definitions.

 Workflow container to task container.

 Task container to workflow container

 Task container to method container

 Method container to task container. WORK ITEM

A work item is an object that represents a task or action in the workflow system at runtime. The following are the types of work items:

P - Workitem that represents a Remote Work Item N – Notification Items

W – Runtime representation of single step tasks that require user interaction. D – Notification of missed deadlines.

A – List of objects to be processed once, and together, in a limited time frame. F – Runtime representation of a multi-step task.

B – Runtime representation of a multi-step task that runs in the background. E – Runtime representation of a wait step in the workflow definition.

C – Is required as a special development in the EDI environment. R – Workitem that represents a Remote Work Item

TASKS

The following are the types of tasks:

Standard task – Client independent task (single-step task(TS)). Customer task – Client dependent Task (single-step task (T)). Workflow task – Multi-step task (WS).

Workflow template – As a framework for defining a workflow.

Task group (TG) – are defined, to group standard tasks and workflow templates that are logically related. You can also collect other task groups within a task group, hence making hierarchies of task groups. A standard task or workflow template can be used in several task groups.

D

IAGNOSIS

W

ORKFLOW

-

SWUD

 VERIFY WORKFLOW CUSTOMIZING

A customizing check is the first in the list simply because incomplete customizing is the most frequent source of problems in an unfamiliar system.

 PROBLEM : TASK DOES NOT START.

When the workflow does not start or cannot be found, then you should call this option to track down why this is happening.

 PROBLEM : WORKFLOW IS HANGING

When the workflow starts but stops before completion either with an error or simply by falling to start the next step in the workflow.

 TEST ENVIRONMENT

When you are developing a workflow and want to access the complete suite of test tools from one place then this is the option for you. You will see a list of all components Sub-Workflows, Tasks, Business Objects, Delegated Business Objects

SECONDARY DIAGNOSIS TRANSACTIONS SWU3 : Verify Workflow Customizing.

In this transaction the most important basic customizing for workflow is checked. If you find any errors here.

SWEL : Event Log.

Note: Before you can use the event log, you must make sure it is activated. You check this in transaction SWELS. If you are not sure whether or not it is active, just deactivate and activate the event log once.

SWE2 : Event type linkage

A workflow is usually started or triggered by an EVENT so it is important to make sure that an event occurrs. In the event log you can see the event and its business object type. If an event has been successfully created, it is important to check if there is a receiver type for this event. The receiver type is the workflow that has been triggered by the event. The coupling between an event and the receiver can be maintained in trans. SWE2.

SWU0 : Event simulation

If you have found NO receiver type in the event log, then you should check transaction SWU0, Simulate Events. In this transaction you can simulate an event. The system will check all workflows that could be triggered by the event and tells you whether or not they were triggered. Information is displayed for the workflows that were not triggered successfully.

If a workflow was been correctly triggered and started at least one WORK ITEM should be created. You can view the work items in transaction SWI1, Work Item Selection. The easiest way for the selection is just to go into this transaction after you have checked the event log. By default all the work items of the last hour will be displayed. You will find in this transaction the work item number, the status of the work item and the workflow task that has created the work item. Furthermore, (in the technical workitem display) you can have a look at the container by selecting a work item and using the menu GOTO -> CONTAINER. To display the work item details double click on the item. From the details you can see the selected/ possible/excluded agents for this work item by using the menu GOTO -> AGENT -> SELECTED/POSSIBLE/EXCLUDED AGENTS.

When the status of the work item shows an error you should have a look at the workflow log using the menu EDIT -> DISPLAY WORKFLOW LOG. Here you can see errors that have occurred.

PFTC/SWDD : Task editor/Workflow Builder

If you want to have a look at the definition of the workflow you can use transaction PFTC, Maintain Tasks. The button WORKFLOW BUILDER brings you to a graphical display of the workflow structure, which is fairly easy to read and understand. On the tabstrip TRIGGERING EVENTS you can check if the triggering is activated or not and deactivate/activate it by clicking on the icon in front of the event.

OOCU : Customizing overview

To check if the relevant tasks are activated and users are assigned, you can use transaction OOCU; Task Customizing Overview. In this transaction all the tasks are sorted by the application components and are thus easy to find. Note that if you have almost no entries in this transaction, you should execute the report RS_APPL_REFRESH in transaction SE38.

SWUE/SWUS : Event/workflow trigger

If you have activated a user exit, e.g. for the role determination, and you have problems with that, you most probably have to debug the workflow. This can be done using the transaction SWUS or SWUE.

With SWUE you can create an event. After you entered object type and event you have to fill the event parameters and the key for a specific object. If you want to debug the workflow you have to set the flag TRIGGER RECIEVER FM SYNCHR. If you have set a break point in your user exit or in any other function module of the workflow the system will stop at this break point and you can start analyzing.

The second possibility to debug a workflow is to use the transaction SWUS, the workflow test environment. In this transaction you have to enter the workflow task and fill the input data. Please use the F4-help to fill the input data. Here again you have to set a break point in your user exit or in any other function module of the workflow and then the system will stop there.

Summary of the manual alternative to SWUD

Now that you have a better understanding of how to use these transactions, you can follow the steps below to quickly analyze your workflow problems:

1. Go to transaction SWU3 and check if everything is okay. If it is not, please fix it before you proceed.

2. Go to transaction SWEL and check if an event is created. If not, check in transaction SWELS if the event log is activated.

 If you see an event but no workflow is triggered, proceed with step 3.

 If you see an event and a workflow is triggered, but the status of the triggering shows an error, proceed with step 3.

 If you see an event and a workflow is triggered and there is no error, proceed with step 4.

 If the event log is activated and you do not get any event, open up a message using the component of the application to which the business

object type belongs. From release 20C for creation of shopping carts the architecture of workflows changed and no events are visible!

3. Go to transaction SWU0 and simulate the event. Is the workflow that you expect to be triggered visible in the simulation?

 If it is not, then check the workflow definition in PFTC. The event must be defined as triggering event.

 If it is, but the event linkage is not activated, go to transaction OOCU and activated it.

 If it is visible, but it is not activated, go to transaction PFTC and activate it.

4. Go to transaction SWI1. Search for the work item that belongs to the workflow. Check the status of the work item.

B

USINESS

O

BJECTS

BUSINESS OBJECT DESCRIPTION TRANSACTION _DOCUMENT CHANGE GENERAL DECISION SOFM SW PURCHASE RELATED BUS2010 BUS2011 BUS2012 BUS2105 LFA1 BUS1001 BUS2013 BUS2014 BUS2081 BUS2081 SALES RELATED BUS2030 BUS2032 LIKP BUS1065 BUS0012 BUS2094 Engg. Change Mgt. ECM

For User Decision Office Document (For attachment ) RFQ VENDOR QUOTATION PURCHASING ORDER PURCHASE REQUISITION VENDOR MASTER MATERIAL MASTER SCHEDULING AGREEMENT PURCHASE CONTRACT INCOMING INVOICE PARKING CUSTOMER INQUIRY SALES ORDER OUTBOUND DELIVERY(SHIP) HR Master data Cost Center CREDIT MEMO

Engg. Change Master

ME41 ME47 ME21 ME51 MK01 MM01 ME31L ME31K MIRO MIR7 VA11 VA01 VL01 PA30 KS12 FB75 CC01/CC31 EINKBELEG EINKBELEG EINKBELEG BANF KRED MATERIAL EINKBELEG EINKBELEG VERKBELEG VERKBELEG LIEFERUNG -- NO --- KOSTL LIEFERUNG AENNR

M

AJOR

P

URCHASING RELATED

B

USINESS

O

BJECTS  BUS2009 Request for quotation

 BUS2011 Vendor quotation

 BUS2012 Purchase Order

 BUS2013 Purch.scheduling agreement

 BUS2013002 Purchase scheduling agreement release

 BUS2014 Purchase contract

 BUS2052 Outline purchase agreement

 BUS2105 Purchase requisition

 BUS3030 Rebate arrangement: Purchasing

M

AJOR

S

ERVICE

M

ANAGEMENT RELATED

B

USINESS

O

BJECTS  BUS1005 Service

 BUS2080 Service notification

 BUS2088 Service order

 BUS2091 Service entry sheet

 BUS2129 Service order confirmation

M

ASTER

D

ATA

 BUS1006 Business Partner

 BUS1178 Product

W

ORKFLOW

-

FAQ

S Can we define methods

without function module? Yes, using Macros What do you mean by role

resolution Finding the responsible agents and assigning task to him How will u raise the

Exception? EXIT_RETURN <Exception> <Var1> <Var2> <Var3> <Var4> How will u create a method

in Workflow?

1.Using Macro

BEGIN_METHOD <MethodID> CHANGING CONTAINER END_METHOD.

2.Create method-using API

Basic Organization Plan Organizational Unit – Each unit represent a group of people such as a team, section, department, work area, laboratory.

Jobs – Each job describes a functional role within the organization. Positions – each position represent the headcount placement User – Each user is the actual user Id of a person in your organization.

Task – Description of an activity in organizational management which is Performed with in the organizational unit

Task group - is a hierarchical combination of tasks that are related logically

How does triggering local

events work? This step enables you to trigger a local event. A local event can, for example, start a local Workflow. You define local events in the version-dependent basic data of the Workflow.

What are the five attributes

used in business object?  Interfaces Key fields

 Attributes

 Methods

 Events What are the types of data

u can create for attribute? ABAP dictionary – reference table/reference field Object type – Inverse attribute What is meant by a

Single-step task? Its defines an activity that can be executed within a workflow or Independently and no agents are assigned to a single-step task. What is a workflow

template? Sequence of activity together forms a workflow template How does u link workflow

and task? SWE2.

What is a required field for an event and workflow binding?

What is the function module

for triggering the event? SWE_EVENT_CREATE, SAP_WAPI_ CREATE_EVENT. What is the trans. to create

the event?

SWUE What is Async. and

synchronous method? ASYNCHRONOUS METHOD has a terminating events and it is executed by a dialog step. SYNCHRONOUS METHOD may have terminating events and it is Executed by background processing.

What should be the type of task to be a synchronous task?

It should be a background task What is workflow

versioning?

Modifying a workflow without changing an active version. What is CHECK function

module? It is a transaction which used to prevent a linkage being triggered when an event occurs What is meant by event

queue?

Events which are in queue are called an event queue. This is achieved by TRFC for starting the receivers not being called immediately

Which container operation

can be modified? Workflow container What does a check box

“Step not in workflow log” do? What happens when it is checked and when it is not checked?

If it is checked the graphics will not be displayed in the business Workflow log and if it not checked it will be displayed.

What is the difference b/w regular workflow and release strategy workflow?

A release strategy workflow is exclusively for purchase order and purchase requisition and other than this other workflows is regular workflow

How is the release strategy

workflow controlled? Using transaction ME28. What are the difference

b/w a rule and a role? Rule (PFAC) assigns agents at Run time based on Organization, Responsibilities and Function Modules. Role (PFCG) assigns agents at Static Mode and gives the authority check

Multi step task A multi task is a formal framework for a workflow definition. When you create a workflow directly in the in the workflow builder, the multi step task is created by the system.

It can be divided in workflow template and workflow tasks. Single Step Tasks:

 Standard task (task type TS)

 Customer task (task type T) Multi Step Tasks:

 Workflow template (task type WS)

 Workflow task (task type WF) Task group (task type TG)

How do you trigger a workflow Manually

Calling a Start Transaction Calling a Form Transaction

Binding First Ref : Binding takes place before execution ( WF - > Task ) Sec. Ref : Binding takes place after execution ( Task -> WF ) Work Item 1. READY : Usually applies to work items. The work items has been

created and is activated but has not been executed yet. It is sitting in a user’s inbox but they have not opened it yet.

2. SELECTED : Appears in the work item displays as in process. Usually applies to work items. The work item has been opened or reserved by a user but has not yet been executed.

3. COMMITTED: Appears in the work item display as executed. Usually applies to work items. The work item has been executed, but is waiting for the user to mainly confirm the end of processing. Via a set to done option.

4. COMPLETED : The workflow or work item is completed. No further changes can be made once completed.

5. WAITING 6. STARTED 7. ERROR 8. CANCELLED 9. CHECKED

10. EXCPCAUGHT – EXCEPTION CAUGHT

11. EXCPHANDLR –EXCEPTION BEING HANDLED

Synchronous Method It assumes process control for the duration of its execution and report backs to the calling component after its execution. Background processing

Return Parameters, One Result, Exceptions Asynchronous Method

Synchronous Method

It reports back to the calling component Back ground processing Return parameters, one result, Exceptions.

It does not report back directly to the calling component after its execution. Dialog Step

No return Parameters, One Result & Exceptions

Asynchronous Method

It does not reports back directly to the calling component after its execution

Dialog step

Terminating event is necessary

Release strategy Exclusive for Purchase Order, Purchase Requisition

Possible Errors 1. AGENT DETERMINATION ERROR – Wrong Agent / No Agent was found for a dialog workitem.

2. BUFFERING ERROR – SWU_OBUF – These usually manifest themselves as an inability to access workitems despite the maintenance of the agent determination and security being up to date.

3. WORK ITEM ERROR – These are usually caused by incorrectly modeled workflow or rushed transport. For Ex. The workflow does not take into account incomplete data extracted from legacy systems or exceptions in object methods are not trapped 4. EVENT LINKAGE ERROR – These are usually caused by changes in

The workflow didn’t start at all because the triggering event was not raised or failed to start the workflow (or) then workflow hangs in the middle of the process waiting on a terminating event that never happens.

Condition Based Starting W/F  Check Function Module

 Event Creator give condition (avoid WF Triggering)

 SWB_COND => Maintain WF start conditions. There assign the values based on the business object and event we used. It’s not available in release prior to Release 4.6C.

How will u delete a work item,

which is in the inbox?  Use SWWL transaction Use RSWWWIDE Standard Report

 Use Process Control Step in Workflow template  Use SWUF (Workflow Admin)

How can I pass parameters from an ABAP program to the workflow container?

SWW_WI_START_SIMPLE is the Function Module used for triggering workflow from ABAP.

(Try also SWW_WI_CREATE_VIA_EVENT) How to Trigger another

workflow from a workflow in process?

In an Activity, just call the workflow, as u calls the task… How can you make event

linkage?  SWEC  SWE2  SWB_COND

O

BJECT

T

YPES

:

T7780

US - User O - Organization Unit S - Position AG - Role AC - Rule A - Work Center P - Applicant C - Job F - Location K - Cost Center KU - Customer P - Person TG - Task Group TR - Transaction U - Company UG - User Group WA - Work Area WE - Workflow Event WF - Workflow Task WI - Workitem T / TS Task

ACTIVITY Step type in a workflow definition for executing a task at runtime. The task can be a single-step task (customer task/standard task) or a multistep task (workflow task/workflow template).

At runtime, an activity is represented by a work item of one of the following types:

 DIALOG WORK ITEM (TYPE W)

 BACKGROUND WORK ITEM (TYPE B)

 WORKFLOW WORK ITEM (TYPE F) ADVANCE WITH

IMMEDIATE DIALOG Execution property of the workflow system. A work item for which this indicator is set is executed immediately, if the actual agent of the preceding dialog work item is also a recipient of this work item.

This user does not have to call their Business Workplace to execute the work item.

AFTER METHOD Method that is executed after the task's method, synchronously and on the same screen, during execution of a dialog or background work item.

The method can be any object method in the Business Object Repository. It does not have to refer to the same object as the task's method.

If the work item is executed several times (say, for example, the terminating event has not yet occurred), the after method is also executed several times. AGENT Umbrella term for a system user who participates actively in SAP Business

Workflow and executes work items. There are various types of agent:

 CURRENT AGENT

 RECIPIENT

 RESPONSIBLE AGENT

 EXCLUDED AGENT

 POSSIBLE AGENT

APPROVAL TASK Single-step task that executes an approval method with a result. The result must be able to assume at least two values, one of which stands for approval and the other for rejection of the object to be processed.

For an extended approval, the approval method must be able to assume two more values, one for proposed approval and the other for proposed rejection. ASYNCHRONOUS

METHOD

Method that does not report back directly to the calling component (in this case the work item manager) after its execution. It does not return any result, any

parameters or any exceptions. (Except System Error & Application Error)

At least one terminating event must be defined for a single-step task described with an asynchronous object method.

An asynchronous method must enter its results itself. Import parameters can be passed to it only. At runtime, the relevant work item is only completed if one of the defined terminating events occurs.

ATTACHMENT Additional information for a work item, which can be entered by the current agent of the work item. Attachments are displayed to the agents of the subsequent steps of a workflow in read-only form.

Attachments can be SAPscript editor texts or PC application documents. ATTRIBUTE Object type component: Property or characteristic of an object.

The attributes of an object are defined and implemented as part of the object type definition in the Business Object Repository. Value of ABAP Dictionary field

 OBJECT REFERENCE

 VALUE CALCULATED AT RUNTIME

 OBJECT STATUS IN STATUS MANAGEMENT BACKGROUND

WORK ITEM Work item representing a single-step task whose execution does not require any dialog and can therefore be controlled by the system. Work items of type B are not displayed in the Business Workplace, but can be found using the selection report for work items of all types.

BEFORE METHOD Method that is executed before the task's method, synchronously and on the same screen, during execution of a dialog or background work item.

The method can be any object method in the Business Object Repository. It does not have to refer to the same object as the task's method and it cannot create the object.

If the work item is executed several times, (say, for example, the terminating event has not yet occurred), the before method is also executed several times. BINDING Assignment of values to a container element at runtime.

The assignment rules to be observed are first defined in the binding definition. BUSINESS

WORKFLOW EXPLORER

Tool for:

 DISPLAYING ALL TASKS ASSIGNED TO A SELECTED SEARCH RANGE

 EDITING THESE TASKS

 CREATING NEW TASKS

The search range can be restricted according to the following criteria:

 APPLICATION COMPONENTS

 TASK GROUPS

 LOCAL TASKS

 SAP PHONE TASKS

 TASKS LAST PROCESSED

 TASKS ASSIGNED TO PARTICULAR TASK GROUPS CHECK FUNCTION

MODULE Function module called Sthe event manager directly before the actual receiver function module is called YNCHRONOUSLY IN THE LUW of the event receiver by if: An event receiver was established, and The name of a check function module is specified.

The check function module has the same interface as the receiver function module. This means that the content of the event container can be checked and the calling of the receiver function module prevented. If the check function module terminates with an exception, the receiver function module is not called and the linkage between the event and the receiver not created.

There is a template check function module called SWE_CD_TEMPLATE_CHECK_FB in the function group SWE_TEMPLATE. COMPOSITION "Is part of" relationship between object types.

The superordinate object type in this relationship is known as the "aggregate type".

In the composition, the "part" object type's key is an extended version of the key of the aggregate type, and the object type has a completely different functionality from that of the aggregate type.

Example

The object type order item "is part of" the object type order.

The object type order is then the aggregate type of the object type order item.

CONTAINER Basic common data structure of the various definition and execution components of SAP Business Workflow.

Containers have container elements for holding the following:

 VALUES (CONSTANTS)

 STRUCTURES

 OBJECT REFERENCES

The container elements can be used to control the execution of work items and workflows.

CONTAINER

DEFINITION General information about the structure of the data to be stored in a container. A container definition specifies the elements included in a container and the properties of those elements (ID, name, data type).

A container is always defined when working with one of the definition tools (OBJECT TYPE DEF., ROLE DEF., TASK DEF., AND WORKFLOW DEF.).

CONTAINER

ELEMENT Entry in a container. It is defined by specifying the following:  ID

 NAME

 DATA TYPE REFERENCE CONTAINER

OPERATION Step type in a workflow definition for performing elementary arithmetic operations or value assignments on individual elements of the workflow container at runtime.

CREATION

DATE/TIME Point in time at which a work item was first created with the status ready or waiting. The latter applies if a "requested start" was declared for the work

item.

CUSTOMER TASK A single-step task created by a customer to meet their specific requirements. The following apply to customer tasks:

 OBJECT TYPE T IN ORGANIZATIONAL MANAGEMENT

 CLIENT-SPECIFIC

 VALIDITY PERIOD

 PLAN VERSION-SPECIFIC

DATA TYPE

REFERENCE Description of the data type of the value that can be assigned to a variable (for example attribute or container element) at runtime. The data type reference is created during definition and enables the system to perform checks at definition time.

A data type reference may be:

 VIA FIELD REFERENCE TO AN ABAP DICT. TABLE OR STRUCTURE & FIELD.

 VIA STRUCTURE REFERENCE TO AN ABAP DICTIONARY STRUCTURE OR TABLE.

 VIA REFERENCE TO AN OBJECT TYPE. DATABASE FIELD

ATTRIBUTE

When this type of attribute is defined, reference is made to a database field as the source of the required information.

An attribute whose source is a database field can either return the database field contents or an object reference, which is automatically generated from the field content.

DEADLINE

MONITORING Functions in the workflow runtime system, which monitor start and end deadlines for the processing of selected work items. The monitoring of the requested start ensures that the work item appears in a Business Workplace at a defined point in time, and not before.

 MISSED DEADLINE NOTIFICATION

Recipients of a missed deadline message are notified with a missed deadline work item in their Business Workplaces.

 MODELLED DEADLINE MONITORING

The reaction is modelled in the workflow definition.

DECISION TASK Single-step task with which the workflow system executes a user decision in the workflow. The method "process" of object type "DECISION" is always executed with a decision task. Decision tasks can differ in the following ways:

 TEXTUAL CONTENT (TASK DESCRIPTION, NOTIFICATIONS)

 ASSIGNMENT OF POSSIBLE AGENTS

The decision task TS00008267 (generic decision task) supplied by SAP is used as standard in the user decision. You can specify another decision task when defining the user decision.

DEFAULT

ATTRIBUTE Attribute or key field of an object, which is entered in the basic data of the object type on the tab page Defaults. The value of the default attribute is displayed when an object is to be described in greater detail. This applies, for example, if a list of objects is displayed. The default attribute of an object can also be used as a sort key in the Business Workplace.

Often the default attribute is a key field of the object. If no default attribute is defined for object type, the key fields of the object are displayed.

DEFAULT METHOD Method of an object type, which is entered in the basic data of the object type on the tab page Defaults.

The default method is often a method for displaying the object. The default method can de executed by double-clicking on an entry in a list, for example. Every object type has a default method. The method Display is proposed for new object types.

DEFAULT ROLE Agent information specified when a single-step task is defined in addition to the assignment of the possible agents.

If the single-step task is included as an activity in a workflow definition and responsible agents are defined there, the default role is not evaluated.

DELEGATION TYPE

(SWO6) Object type whose definition is considered at runtime instead of the definition of another object type, although this other object type is specified in all definition components (for example task and workflow definition, linkage tables). In all definition tools you can still refer to the original object type, but the system uses the definition of the delegation type for every access.

The delegation type must always be a subtype of the object type it is to replace. The delegation type can have different or additional methods, attributes and events.

A delegation type is always defined for an object type on a system-wide and cross-client basis.

DIALOG WORK

ITEM Type W work item that represents a single-step task at runtime, which requires dialog with the user. Dialog work items are usually displayed in the Business Workplace.

When a dialog work item is executed, the object method underlying the single-step task is called. Dialog work item execution can be deadline-monitored. DOCUMENT Collective term for all types of information generated from an application

program.

The folowing are examples of documents:

 SAPSCRIPT TEXT IN RAW FORMAT

 MICROSOFT WORD TEXT IN DOC FORMAT

 MICROSOFT POWERPOINT PRESENTATION IN PPT FORMAT DOCUMENT FROM

TEMPLATE Step type in a workflow definition for creating documents on the basis of user-defined templates at runtime. The documents can be created with programs that are installed on the local PC and are OLE-compatible, 32-bit, Windows applications (for example Microsoft Word 97).

END Date/time of end of processing of a work item.

The processing of a work item is terminated if it assumes the status logically deleted or the status completed.

ENTITY TYPE Each object type can be assigned to an entity type, which further classifies the object type in the company environment.

EVALUATION PATH An evaluation path describes a relationship chain that exists in a hierarchical structure between particular objects.

For example, the evaluation path ORGEH describes the relationship chain Organizational unit > Position > Person. Evaluation paths are used for the selection of objects in evaluations.

After you have specified an evaluation path, the system evaluates the structure along this evaluation path and only takes into account the objects found via the specified evaluation path.

EVENT Status change of an object which is "published" throughout the system. Examples: "invoice entered", "purchase order released".

The list of possible events is defined with the relevant object type in the Business Object Builder. This list can be extended according to customer requirements using the delegation concept. You have to ensure that the events added are actually created.

Each event carries information from its creation context in its event container. This information is available to the receiver of the event and can be used for event-driven control and communication mechanisms.

An event may start, terminate or continue tasks and workflows.

EVENT CONTAINER Container that contains the event parameters of an event. The event must be defined as an object type component in the Business Object Repository (BOR). Event containers can have bindings with workflow containers or task containers.

EVENT CREATION Program or environment in which an event is created.

The creation of an event can be implemented in various ways:

 DIRECTLY FROM AN APPLICATION PROGRAM

 AFTER A CHANGE THAT IS LOGGED BY A CHANGE DOCUMENT BEING WRITTEN

 AFTER A (SYSTEM OR USER) STATUS CHANGE

 AS A SEPARATE OUTPUT TYPE WITHIN MESSAGE CONTROL

The last three creation mechanisms listed can also be used by customers. This means events can be created flexibly and on a customer-specific basis even where the option has not been provided by SAP in the standard version.

An event can only be created if it is defined as a component of an object type in the Business Object Repository.

EVENT MANAGER All the programs and tools provided by the workflow system for event handling. This term includes:

 THE DEFINITION COMPONENTS (FOR CREATING CREATOR-RECEIVER LINKAGES)  THE RUNTIME COMPONENTS (FOR TRIGGERING AN EVENT INSTANCE, EVALUATING

THE EVENT INSTANCE WITH REGARD TO EXISTING LINKAGES, MANAGING THE ASSIGNMENT OF CREATORS TO RECEIVERS, AND FOR THE ACTUAL DATA TRANSFER) EVENT PARAMETER Runtime-specific information from the event creation context. Event

parameters are defined as elements of the event container and are passed to the event receivers via binding.

The following event parameters are automatically contained in the event container:

 THE REFERENCE TO THE OBJECT WHOSE CHANGE OF STATE IS DESCRIBED BY THE EVENT.

 THE USER NAME OF THE PARTY WHO TRIGGERED THE EVENT CREATION. EVENT RECEIVER Application or system program in which an event is evaluated.

The event receiver is started by the asynchronous call to a receiver function module, which is entered in the linkage table.

The event manager evaluates the linkage table and then calls up the receiver function module.

EXCEPTION Object type component: Error which may occur during method execution and indicates whether a method was successful.

Exception categories:

 APPLICATION AND SYSTEM ERROR

 TEMPORARY ERROR

Temporary errors can occur when system resources are not available. So it might make sense to call the method up again later.

You can account for application or system errors in Workflow by defining steps to be carried out when an exception occurs.

EXCLUDED AGENT User who is excluded from processing a work item.

Excluded agents can be established at runtime so that information from the workflow execution environment (agents of previous steps for example) or from the context of the processed application objects can be taken into account.

EXPRESSION Umbrella term for constant, variable and system field.

meanings:

 CONSTANT

Fixed value or fixed object reference

 VARIABLE

 CONTAINER ELEMENT OR

 ATTRIBUTE REFERENCED INDIRECTLY VIA A CONTAINER ELEMENT

 SYSTEM FIELD

Field from table SYST

Expressions are used, for example, to describe the source or destination of data to be transferred in a binding definition.

FORM TASK Single-step task executed with the method Process of object type FORM. The various form tasks differ in the following aspects:

 TASK CONTAINER

 TASK DESCRIPTION

 AGENT ASSIGNMENT

If a form task is executed as a step within a workflow, the recipients of this step see a work item in their Business Workplaces. If the relevant system settings have been made, a mail is also sent to their Internet addresses. This mail contains the data from the task container as an R3F attachment.

GENERAL TASK Indicator for a single-step task or a multistep task. Tasks with this indicator can be executed or started by any user.

The following apply to a work item of this type:

 RECIPIENTS ARE ALL USERS, PROVIDING NO RESTRICTION HAS BEEN IMPOSED BY DEFINING RESPONSIBLE AGENTS.

 IT CAN BE FORWARDED TO ANY USER BY ITS RECIPIENT.

It can be executed by any employee who finds it using work item selection or the workflow log.

IMPLEMENTATION

PROGRAM ABAP program containing the implementation of methods and attributes of the object type. When the attributes, methods and events are defined, the interface of the object type is described, and all essential information about the object type is documented.

Every object type requires one program, containing the following:

 THE CALL TO THE UNDERLYING ABAP FUNCTION AND THE PROVISION OF PARAMETERS IN THE FORM OF SUBROUTINES FOR EACH METHOD DEFINED.

 INDIVIDUAL READ ACCESS FOR EACH ATTRIBUTE.

This collection of subroutines is then accessed by the function modules of the runtime environment to call methods and read attribute values.

The implementation program is partly created automatically by the system from the definition information. Some post processing is required, however. INHERITANCE Relationship between object types allowing common attributes and methods to

be passed on automatically from super types to subtypes.

With inheritance the subtype usually has the same key fields as its super type but greater functionality.

INSTANCE LINKAGE Assignment of a specific receiver instance to a particular combination of EVENT, OBJECT TYPE, AND OBJECT KEY.

The instance linkage is entered in the instance linkage table. The The instance linkage table is one of the two linkage tables for the EVENT-RECEIVER LINKAGE (the other table is THE TYPE LINKAGE TABLE).

If events are used in SAP Business Workflow (as triggering and terminating events, in wait steps), the entries required in the linkage tables are made by the workflow system.

INTERFACE Collection of attribute, method and event definitions for an object type, which are used in a common context.