Business Workflow презентация

Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe

Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe

Workflow Definition
SAP Business Workflow® is a cross-application tool that makes it possible to integrate business tasks/processes between applications.
This tool was introduced in R/3 Release 3.0A, and received a substantial facelift in the Enjoy Release, 4.6A, which warranted the new name Workflow Builder.

Need for Workflow
A business process can consist of several steps. Historically, the tasks have been coordinated manually or by some informal means of communication (sticky note, e-mail, shouting, and so on).
The common problem in these approaches is :
Inefficiency
Each lacks a way to trace where a task is
Who executed (or is executing it),
How much time it required.
In contrast, the workflow ensures that the right work is sent to right person at the right time in the right sequence with the right information.

Why SAP Workflow?
Tool for the automization of business processes
Not tied up to any particular application
Operates uniformly across applications
Coordinate all participating tasks
Provide users with active support

Workflow Boundaries
The component uses the existing transactions & function modules. The functionality and operability of the existing transactions and function modules are neither changed nor restricted by the workflow control.
SAP Business Workflow does not intervene in the programmed processes within a transaction
The component makes the R/3 System easier to operate, which is particularly useful for inexperienced or occasional users.

Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe

Workflow
A workflow consists of a sequence of steps, which are processed either by people or automatically by the system.

Workflow Builder
Modeling tool for creating a workflow definition.
Creating and process workflow definition
Test and activate a workflow definition

Workflow Definition
Technical description of a workflow
Workflow definition is made up of individual steps and events with one step and one or more events making up one unit. These units can be arranged in sequence or in parallel.
The workflow definition is the set of rules that determine the path that the process takes. For example, how a purchase requisition is processed, from the initial request to the creation of the purchase order

Workflow Instance
A Workflow Instance, which is often simply referred to as the workflow, is a single workflow run. For example, the processing of a single purchase requisition for computers.

Task
The Tasks are the steps in the process, which have to be performed either by people or automatically by the software. For example, to check for the availability of the spare computers in the company.
During runtime a tasks is represent as a Workitem.
Following tasks exist in the workflow context:
Single-step task
Activity in which an object method is executed on a specific object
Multi-step task (Workflow)
Activity whose description includes reference to a workflow definition

Work Item
A Work item is the task instance that is performed as a single workflow step. For example, check that there are no spare computers available in the company.

Agent
Agents are the people who process the tasks (via the work items). For example, requisitioner and a member of the purchasing department.
A system user who participates actively in SAP Business Workflow and executes work items
Types of agents available
Possible agent
User who is organizationally authorized to start a task and execute the associated work item
Responsible agent
User assigned locally to a step in the workflow definition
Excluded agent
User who is excluded from processing a work item

Container
Container is the place where all the data used in the workflow is collected.
Basic common data structure of the various definition.
Containers have container elements for holding the following:
Values (Constants)
Structure
Object references
Complex types
The container elements can be used to control the execution of work items and workflows.
Types of container:
Workflow container
Task Container
Event Container
Method Container
Rule Container

Binding
Binding is the set of rules that define which data is passed to which part of the process.
Assignment of values to a container element at runtime.
Binding definition:
Specification of assignment rules describing the assignment of data to a container element or the exchange of data between two container element.

Business Object Builder
Tool for creating and processing business object types.
Can be used to access the definition of an object type
Subtypes can be created for existing Business object type

Object Type
Business objects integrate the data and functions of business applications into your workflows.
They enable workflow engine to communicate with business applications with all the flexibility and robustness required for a production environment

Object Type
Description of data (objects) in the system created at definition time in the Business Object Builder
Object types are described and implemented by specifying the following components:
Basic data
Key fields
Attributes
Methods with parameters, result and exceptions
Events with parameters
Implementation program
The Object type must be defined before its data (Objects) can be used in the system.

Workflow project Approach

Business Workflow Overview
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe

WORKFLOW ARCHITECTURE

Workflow Architecture

WORKFLOW CUSTOMIZING

What Auto-Customizing Does
The automatic workflow customizing sets up the system using defaults so that you ready to use the system as quickly as possible.
The most important activities are as follows:
Maintain Active Plan Version
Plan version (with its contents) is seen by the workflow system as the only valid plan version.
All SAP Workflows supplied automatically become part of the plan version that has been selected as the active plan version
Only one of the plan versions created in the system can be active.
Configure RFC Destination
The runtime system always executes its tRFC calls via the logical destination WORKFLOW_LOCAL_XXX (XXX stands for client number)
The workflow runtime system is client dependent i.e. a single workflow instance normally executes within one client
Maintain Workflow System Administrator
Schedule Background Job for Missed Deadlines
Maintain Prefix Numbers

Automatic Workflow Customizing: SWU3
Customizing the system is the very first step that you will take when you plan to use workflow

ORGANIZATIONAL STRUCTURE

Creating an Organizational Plan
The above diagram illustrates that the first step in Simple Maintenance is to create a root organizational unit. Once one organizational unit has been created, the organizational units below it have to be created.
Organizational units and jobs may be created in any order but must exist before the associated positions are created.
Jobs may exist in the job index or may be created once the model contains an organizational unit.
Positions are created once the relevant jobs have been created in the job index.
Tasks are assigned using jobs and positions.
Holders are assigned to positions, not to jobs.

Assignment Workflow Tasks: Organizational Objects
The relevant users receive a work item at runtime.
Task 1: User 1 (via manager job)
Task 2: User 1, user 2 (via manager job/job for secretary)
Task 3: User 1, user 2, user 3, user 4 (via organizational unit)
Task 4: User 1, user 3, user 4 (via position for head of FI department/job for FI employee)
Task 5: User 2 (via secretary job)
Task 6: User 3, user 4 (via job for FI employee)

Create Job: PPOM

Positions

Create Position: PO13

Basic HR Definition for Workflow

Creation of Workflow or Tasks
through T-Code: PFTC
Client Independent
Standard task : TS
Workflow Template : WS
Task Group : TG
Client Dependent
Customer tasks : T
Workflow Task : WF
No longer used, supported in previous versions

Five Questions for each part of a Business Process and how to map them in Steps/Tasks

In What Order?: Workflow Definition
Workflow definition controls the calling sequence of each step. Steps like workflow, can also be triggered by events.

In What Order?: Workflow Builder (SWDD)…How it looks

With What Object? What?:
T-code: PFTC, Calling Methods within a Task
Attach Object Method here, give Object Category, Object Type and Method Name
Define binding between Task Container and Method here.
Define
Synch / Asynch
Dialog / Without Dialog

With What Object?:
Business Object and its Method
Business Object
E.g. BUS2089

What?: Method Configurations

What?: Method Parameters

WHO: Agents
Responsible Agents
Excluded Agents
Possible Agents
Possible Agents assignment
Button turns green if agent assignment is configured

When? T-code: PFTC
Events can be used to trigger:
Workflow instantiation
Commencement of a step
Completion of a step, normally for asynchronous tasks

When?
SWDD? Double Click on Step…
A Condition, Multiple Condition and User Decision step have more than one outcome and depending on the conditions only one of them is executed.
Outcomes can be labeled for easy understanding.

STEP TYPES

Step Types in Workflow
User Decision
- The agent is asked a question and given a pre-defined list of answers
- All the options are available in the work item.
- Each answer is a separate branch in workflow

Step Types in Workflow
Loop (Until)
Runtime use:
- for the purpose of iterative processing of a few steps based on certain condition.

Step Types in Workflow
Send Mail:
- The text entered in this step type is sent as an e-mail
- Both external (on the outlook id) and internal mails (SAP mails) can be sent

Step Types in Workflow
Send Mail:
The subject line of the mail - 50 characters at the max.
To insert Container Elements
To enter text in mail

Step Types in Workflow
Send mail:
Within the Task (under the CONTROL tab) The subject line of mail shown in Work item Text
The Mail Text is present under the description Tab within the Task

Step Types in Workflow
Condition
Run time use:
- Can be used in a scenario where further course of action depends on the condition being true or false

Condition

Step Types in Workflow
Process Control
- This can be used to cancel the execution of a work item or workflow or set a work item to obsolete
- It facilitates the alternate steps to be taken in the process obsolete branch

Step Types in Workflow
Process Control:
The options available with Process control
The workflow step is to be mentioned depending on the Function chosen

Step Types in Workflow
Multiple Condition:
Based on the value of a workflow container element one of the several branches in workflow is processed

Multiple Condition

Step Types in Workflow
Event Creator :
- To raise an event in the workflow
- Data moves from workflow to event

Step Types in Workflow
Wait:
- The system waits for a specific event to be triggered
- The work item is only completed if the expected event occurs

Step Types in Workflow
Fork:
- Used for the purpose of parallel processing
- The user can define the number of parallel processes and how many should be completed for the Fork to terminate and workflow to continue
- The fork can be terminated by defining a condition too

Step Types in Workflow
Container operation:
For the purpose of performing arithmetic operations or value assignments to workflow container
Constants and data within workflow can be used
Multiline operations are allowed

Step Types in Workflow
Ad hoc anchor
- Gives user the option to select between various workflows at runtime
- The steps of the selected Workflow shall replace this one

Step Types in Workflow
Web Activity
- The selected container elements are posted using the http protocol in an XML or SOAP message

Step Types in Workflow
Subworkflow:
- An activity that refers to another workflow rather than a task
Undefined Step:
-These can be used as placeholders during development
- They are ignored at run time

CONTAINER & BINDING

What is a Container
Containers are a common way of holding data throughout the workflow instance’s lifespan.
Containers are used in interface between different parts of the workflow and between the workflow and business applications.

Type of Containers
A workflow container for each workflow and subworkflow
Only container elements classified as import can be filled when the workflow is started.
A task container for each task
Import container elements are filled from the workflow container and export container elements are transferred back.
A method container for each method
Import container elements are filled from task container and export container elements are transferred back.
An event container for each event
All event containers are export container elements only.
A rule container for each rule
The import container elements are filled from the workflow container (or task container). The _RULE_RESULT elements is the only export parameter and this is optional.

Binding
Data can be passed from one type to another using binding.
At runtime, the bindings are executed at the appropriate point in the workflow.
For instance, for a synchronous task, the workflow-to-task binding is executed as part of work item creation and the task-to-workflow binding is executed as part of work item completion.

Containers and Bindings

WORKITEM

Work Item
Object that represents a task or action in the workflow system at runtime.
Work items are subdivided into a specific work item type according to their assignments. The internal processing procedures are controlled via this work item type. The work item type determines which statuses and transitions are valid.
Depending on the work item type, some of these work items are displayed in a user's work list. Other work items, on the other hand, are only used and processed internally.

Work item Types
A Work item that represents a Work Queue
B Work item for Background step
C Work item that represents a container linkage
D Deadline work item; Notification upon Missed Deadline
E Workitem that waits for an Event (Wait step)
F Workflow (Also subworkflow)
N Notification Item (Obsolete)
P Work item that Represents a Remote Work item (Proxy WI)
R Work item that Represents a Remote Work item (http)
W Dialog work item; Represents a Single-step Task
X Work item that Represents a Block

Work item Status
WAITING: Waiting (Also: Work items in Resubmission)
READY
SELECTED: Reserved
STARTED: In Process
ERROR
COMMITED: Executed (Only If Expl. End Confirmation Is Expected)
COMPLETED
CANCELLED: Logically Deleted
CHECKED: In Preparation
EXCPCAUGHT: Exception caught
EXCPHANDLR: Exception Being Handled

Deadline Monitoring

Deadlines for Workflow Steps

Deadlines for Workflow Steps
Requested start
Earliest possible point in time for the commencement of processing
The requested start is not a monitored deadline in the strict sense. It is when a work item first appears in an agent's inbox.
Requested end
Requested end deadline for processing a step
Latest start
Latest start deadline for processing a step
Latest end
Deadline by which the processing of a step must be completed.
Note:
All deadlines are monitored using the background job SWWDHEX with job class A. The job calls the report RSWWDHEX.

Business Objects

Creation of Object type
New Object type
Sub-type of an existing Object type
Adv of sub-type: It automatically inherits all the components (methods, attributes, and events) of the original object type including its implementation.

Sub-type
Tools->Business Workflow -> Development -> Definition Tools -> Business Object Builder
In the field object type enter the object type you want to extend.
Choose subtype.
Enter a unique name, object name, name, short description and name of the program.
Save it.

Object Type Definition
Transaction Code : SWO1
Basic data
General: Super Type , Release , Generation
Change & Transport
Default : Method & Attribute
Contd.

Object Type Definition (contd..)
Key Fields
Determines which application table (s) the data is saved
One or more key fields can be used
Combined key field values provide unique identification for an object instance.
Can refer to a database table or a view.
Contd…

Creation of Key fields
Position the cursor on the entry Key fields and choose the “create” button.
If you want to create the key field with a database table then enter ‘yes’.
Enter the table name e.g.: VBAK
The list of key fields will be displayed, select the respective ones, e.g.: VBLEN.

Object Type Definition (contd…)
Attributes
Property of an Object
Source of Information
Database Field
Virtual
Object
Multi Line:
A multiple-line attribute corresponds to an internal table used in ABAP
Contd.
A database attribute is defined with reference to a column (not a key column) of the related application table.
A virtual attribute is calculated with ABAP code.

Creation of Attribute

Object Type Definition contd.
Methods
Dialog/Background
Synchronous/Asynchronous
Function Module
BAPI
Transaction Code
Report
Other
Contd.

Types of methods
Synchronous methods:
Export parameters are returned directly to the calling program.
Exceptions may be triggered.
Asynchronous methods:
Method execution consists of a synchronous part and subsequent update.
Export parameters are not authorized.
Exceptions are only possible in the synchronous part.
Active check box represents a Synchronous method. Inactive represents an Asynchronous method.

Parameter calls from methods
Import parameters
Export parameters
Result (special export parameter)
Exceptions:
Temporary error Application error
System error

Object Type Definition Contd...
Events
System wide message about a change in state of an Object
Events should be used only in conjunction with SAP Object
The SAP application must raise the event and not the Object type.

Release Status
Modeled : Not accessible at runtime.
Implemented: Only in test or internal use, possibly unstable.
Released: Released for use by the customer.
Obsolete:
The functionality has been replaced. The old functionality is still supported for two releases.

Macros used during SAP Object Programming
Include
OR Include
Container Declaration
: SWC_CONTAINER
Container Initialization : SWC_CREATE_CONTAINER
Contd.
Слайд 91
Macros used during SAP Object Programming contd.
Writing a Field value :
SWC_SET_ELEMENT
Reading a Field value :
SWC_GET_ELEMENT
Writing a Multi Line field value:
SWC_SET_TABLE
Reading a Multi Line field Value:
SWC_GET_TABLE
Слайд 92
DELEGATION
Слайд 93
Delegation
Слайд 94
Delegation
If you create a subtype of an object type, you can
choose to delegate the superior type to the subtype. Delegation means that wherever the super type is referenced throughout workflow, the subtype will actually be used instead.
Delegation lets you use all the existing tasks and workflows based on the SAP object type as if they were using your own subtype.
Customers use their own object extensions with the tasks, events, etc. supplied by SAP
Without having to redefine existing tasks, you can use standard objects with customer extensions
Слайд 95
EVENT
Слайд 96
Events
Events are part of business object, are triggered for changes in
the state of the object, which can cause other processes to begin.
Used for Triggering the Workflow
Necessary information needs to be entered on “Triggering Events” tab of the Workflow Builder.
Workflow Engine will automatically generate the binding. You can change it afterwards.
Events can also be defined in Classes. Their behavior is similar to the events declared in Objects.
Слайд 97
Event Creators & Receivers
Слайд 98
Event Creation and Triggering
Define Object in Business Object Builder
Trigger Event:
Implicitly via
generic tools, for example change documents, status management, message control etc
Explicitly via function module
SWE_CREATE_EVENT
Слайд 99
Event Triggering: Status Change
Слайд 100
Event Triggering: Message control
Create a separate output type and declare 9
(workflow event) as transmission medium
Create a condition table
Create a access sequence
Assign the access sequence to the defined output type for a workflow event
Define condition records and declare the event
Assign the output type to a procedure
Слайд 101
Event Triggering: Change Documents
Слайд 102
Event Triggering: ABAP Code
Fill event container with event parameters
Compose object key
for triggering object
Call SWE_EVENT_CREATE
FM Call error handling
Trigger event with explicit commit work
Слайд 103
Business Workplace
Слайд 104
Worklist as Interface for End User
The Business Workplace is part of
the SAP Business Workflow runtime environment. The employees responsible receive the documents and work items for processing in the Business Workplace. Once a task (= a work item) has been executed and completed, the process can be continued.
The worklist contains all the work items (all the activities to be processed) assigned to this user. The Business Workplace is therefore the most important interface for an employee in their day-to-day work.
Слайд 105
Business Workplace in SAP R/3
The Business Workplace has three screen areas:
Overview tree
Worklist
Work item preview
Слайд 106
Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe
Слайд 107
Demo: Notification of Absence
Слайд 108
Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe
Слайд 109
MONITORING & ANALYSIS
Слайд 110
Monitoring & Analysis
Reporting
Work Item Monitoring
Work Item Analysis
Work load Analysis
Workflow Diagnostic Tool
Слайд 111
Reporting
Reporting on Workflow Progress
Work Items by Processing Duration
Work Items with Monitored
Deadlines
Work Items per Task
Reporting on Agent Behavior
Слайд 112
Reporting on Workflow Progress
Transaction code: SWI1
This report shows all the work
items of the particular task in a particular time period.
This report is also used for monitoring the Workitem
Слайд 113
Reporting on Workflow Progress
Workflows for Object
Transaction code: SWI6.
This report shows
all workflow instances linked to a particular object instance.
Example: Particular Purchase Order
Слайд 114
Reporting on Workflow Progress
Workflows for Object type
Transaction code SWI14
This report shows
all the work items and workflow instances for all object instances of a business object type.
Example: Workflows related to all Purchase Orders
Слайд 115
Work Items by Processing Duration
Transaction code: SWI2_DURA
This report gives list of
work items based on their processing duration for specified type or for a specified tasks.
This report is also used to analyze a Work item.
Слайд 116
Work Items with Monitored Deadlines
Transaction Code: SWI2_DEAD
This report displays work items
with their deadline information, if they are set.
For each missed deadline, the current status of the work item is shown.
This report is also used to analyze a Work item.
Слайд 117
Work Items per Task
Transaction code: SWI2_FREQ
This report shows the number of
work items created in the specified period.
This report is also used to analyze a Work item.
Слайд 118
Reporting on Agent Behavior
Transaction Code: SWI5
With the help of this report
, you can monitor how quickly agent act on their work items
This report is useful for assessing workload over particular time period.
This report is useful for reporting on the type and frequency of tasks being sent to an agent.
This report is also used to analyze a Work load.
Слайд 119
Workflow Diagnostic Tool
Transaction Code: SWUD
A primary diagnostic tool.
Analyze workflow definition.
Following are
the options available:
Verify workflow customizing
Perform Workflow Customizing
Problem: Task does not start
To track down the exact cause of an error
Problem: Workflow is hanging
Choose this option when workflow starts but stops before completion, due to some error.
Test Environment
Choose this option when you want to access the complete suite of test tools from one place.
This option will also display all the components (subworkflow, tasks, business objects, delegated business objects)
Слайд 120
Workflow Diagnosis
Section 1: The current workflow definition to be analyzed.
Section 2:
The list of test options
Section 3: A list of last tem workflow definitions.
Слайд 121
Working with the Workflow Log
At runtime, a workflow has its own
work item (type F) that represents the workflow instance.
The workflow log formats all the information created during the execution of the business process
Standard view
Intended for agents and process owners who want to get an overview of the steps processed.
Technical view
Intended for developers and workflow administrator
Слайд 122
Standard View
Workflow Chronicle (What processed when?
Workflow Agents (Who Processed what?)
Workflow Objects
(What was processed?)
Слайд 123
Workflow Chronicle
The tab page Workflow Chronicle shows a hierarchical display of
all the steps in the workflow. If workflow has a subworkflow structure, the subworkflow are also displayed.
Слайд 124
Workflow Agents
The Tab page Workflow Agents shows the agents involved in
the
workflow.
Following options are displayed for each agent:
What action was carried out in what step
When this action was carried out
The objects involved
Слайд 125
Workflow Objects
The tab page Workflow Objects lists the objects related to
the workflow. This view shows what objects were created and processed.
Слайд 126
Technical View
The technical view shows technical nodes and control structures, container
elements, agent data and workflow data.
Слайд 127
Workflow Status
Слайд 128
Workflow Log
Имя файла: Business-Workflow.pptx
Количество просмотров: 97
Количество скачиваний: 0
Скачать
- Предыдущая
Экспертиза опьянения
Следующая -
Трудовой распорядок и дисциплина труда
Похожие презентации
Ecommerce. Shopping on the Internet
Устройство компьютера
Threads. Выполнение инструкций потоками
Основные операции с данными в СУБД
Операционная система Windows
Scratсh - визуальная учебная среда для обучения школьников программированию
Системы счисления
Компьютерная графика. Цифровая обработка изображений, как сигналов. (Лекция 4)
Триггеры
Решение задач ЕГЭ типа В7
Виды данных и информации. Формы представления информации и передачи данных
Компьютерная графика. Элективный курс
Accounting applications on introduction computer to Microsoft Excel
Защита информационных процессов в компьютерных системах
Информация в обществе и технике
Юридическая обработка правовой информации
Доставка терминалов. Собственный процессинг
Информационные и коммуникационные технологии в образовании
Использование CSS для макетирования
Склеивание мешков цепочек (3 кл.)
Информационная безопасность
Создание игры в Construct 3
Базы данных. Реляционная модель данных
Презентация к уроку по теме Понятие алгоритма, свойства алгоритмов.
Концепция нового товара или услуги
Основы моделирования ГРП
Анимированный кроссворд
Bazele programării
Обратная связь
Email:
Нажмите что бы посмотреть
window.__NUXT__=(function(a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S){return {data:{meta:{result:{meta:{h1:o,main_text:a,main_title:p,main_description:q,main_keywords:r,main_image:a},app:{logo_image:s,logo_image_width:t,logo_image_height:u,logo_text:a,image_width_full:v,image_width_min:w,recaptcha_key:x,yandex_search:y,ya_context:e,banner_1:a,banner_2:a,banner_3:a,banner_4:a,banner_5:a,banner_6:a,banner_7:a,banner_8:a,banner_9:a,banner_10:a,email:z,footer_before:a,footer:a,dark_theme:e,strategy:{image_alt_words:k,item_slide_header:A,item_images:B,item_images_tag:i,item_words_h3:d,item_words_tag:i,item_words_1:l,routing:C,item_slide_skipping:D,item_download_timeout:E,item_slider_width:F,item_show_pdf:d,item_show_contents:d,item_show_filename:d},colors:{header_text:m,header_bg:j,accent:j}},social:G}},categories:{result:[{id:H,ordering:b,name:"Без категории",pseudoname:"uncategorized"},{id:144,ordering:b,name:"Бизнес",pseudoname:"biznes"},{id:146,ordering:b,name:"Образование",pseudoname:"obrazovanie"},{id:149,ordering:b,name:"Финансы",pseudoname:"finansy"},{id:150,ordering:b,name:"Государство",pseudoname:"gosudarstvo"},{id:152,ordering:b,name:"Спорт",pseudoname:"sport"},{id:154,ordering:b,name:"Армия",pseudoname:"armiya"},{id:156,ordering:b,name:"Культурология",pseudoname:"kulturologiya"},{id:157,ordering:b,name:"Еда и кулинария",pseudoname:"eda-i-kulinariya"},{id:158,ordering:b,name:"Лингвистика",pseudoname:"lingvistika"},{id:163,ordering:b,name:"Черчение",pseudoname:"cherchenie"},{id:164,ordering:b,name:"Физкультура",pseudoname:"fizkultura"},{id:165,ordering:b,name:"ИЗО",pseudoname:"izo"},{id:166,ordering:b,name:"Психология",pseudoname:"psihologiya"},{id:116,ordering:H,name:"Английский язык",pseudoname:"angliyskiy-yazyk"},{id:108,ordering:2,name:"Астрономия",pseudoname:"astronomiya"},{id:104,ordering:3,name:"Алгебра",pseudoname:"algebra"},{id:106,ordering:4,name:"Биология",pseudoname:"biologiya"},{id:142,ordering:5,name:"География",pseudoname:"geografiya"},{id:141,ordering:6,name:"Геометрия",pseudoname:"geometria"},{id:123,ordering:7,name:"Детские презентации",pseudoname:"detskie-prezentatsii"},{id:107,ordering:8,name:I,pseudoname:"informatika"},{id:109,ordering:9,name:"История",pseudoname:"istoriya"},{id:139,ordering:k,name:"Литература",pseudoname:"literatura"},{id:119,ordering:l,name:"Маркетинг",pseudoname:"marketing"},{id:114,ordering:12,name:"Математика",pseudoname:"matematika"},{id:138,ordering:13,name:"Медицина",pseudoname:"medetsina"},{id:118,ordering:14,name:"Менеджмент",pseudoname:"menedzhment"},{id:137,ordering:15,name:"Музыка",pseudoname:"muzyka"},{id:136,ordering:16,name:"МХК",pseudoname:"mhk"},{id:130,ordering:17,name:"Немецкий язык",pseudoname:"nemetskiy-yazyk"},{id:105,ordering:18,name:"ОБЖ",pseudoname:"obzh"},{id:133,ordering:19,name:"Обществознание ",pseudoname:"obshchestvoznanie"},{id:132,ordering:20,name:"Окружающий мир ",pseudoname:"okruzhayushchiy-mir"},{id:131,ordering:21,name:"Педагогика ",pseudoname:"pedagogika"},{id:J,ordering:22,name:"Русский язык",pseudoname:"russkiy-yazyk"},{id:128,ordering:24,name:"Технология",pseudoname:"tehnologiya"},{id:127,ordering:25,name:"Физика",pseudoname:"fizika"},{id:126,ordering:26,name:"Философия",pseudoname:"filosofiya"},{id:125,ordering:27,name:"Химия",pseudoname:"himiya"},{id:124,ordering:29,name:"Экология",pseudoname:"ekologiya"},{id:121,ordering:30,name:"Экономика",pseudoname:"ekonomika"},{id:120,ordering:31,name:"Юриспруденция",pseudoname:"yurisprudentsiya"}]},item:{result:{id:249234,name:n,category:I,count:J,jpg:"jpg\u002F249234",hits:97,download:b,h1:"Business Workflow презентация",meta:{h1:n,title:n,description:"Business Workflow презентация на тему, доклад, Информатика",keywords:"Business Workflow, презентация, доклад, проект, скачать, на тему, PowerPoint, урок, класс, школа, Информатика",download_link:a},text:"Вы можете изучить и скачать доклад-презентацию на тему Презентация на тему Business Workflow из раздела Информатика. Презентация на заданную тему содержит 129 слайдов. Для просмотра воспользуйтесь проигрывателем, если материал оказался полезным для Вас - поделитесь им с друзьями с помощью социальных кнопок и добавьте наш сайт презентаций в закладки!",seo_text:"\u003Cp\u003EBusiness Workflow\u003Cbr\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cp\u003E1\u003Cbr\u003E\u003Cp\u003EPrepareMe\u003Cbr\u003E\u003Cp\u003E2\u003Cbr\u003E\u003Cp\u003ETellMe\u003Cbr\u003E\u003Cp\u003E3\u003Cbr\u003E\u003Cp\u003EShowMe\u003Cbr\u003E\u003Cp\u003E4\u003Cbr\u003E\u003Cp\u003ELetMe\u003Cbr\u003E\u003Cp\u003E5\u003Cbr\u003E\u003Cp\u003EHelpMe\u003Cbr\u003E \u003Cp\u003EBusiness Workflow\u003Cbr\u003E\u003Cp\u003E\u003Cbr\u003E\u003Cp\u003E1\u003Cbr\u003E\u003Cp\u003EPrepareMe\u003Cbr\u003E\u003Cp\u003E2\u003Cbr\u003E\u003Cp\u003ETellMe\u003Cbr\u003E\u003Cp\u003E3\u003Cbr\u003E\u003Cp\u003EShowMe\u003Cbr\u003E\u003Cp\u003E4\u003Cbr\u003E\u003Cp\u003ELetMe\u003Cbr",file:"Business-Workflow.pptx",texts:["\u003Cp\u003EAB2002 - Business Workflow - v1.0\u003Cbr\u003E",h,h,"\u003Cp\u003EWorkflow Definition\u003Cbr\u003E\u003Cp\u003ESAP Business Workflow® is a cross-application tool that makes it possible to integrate business tasks\u002Fprocesses between applications. \u003Cbr\u003E\u003Cbr\u003EThis tool was introduced in R\u002F3 Release 3.0A, and received a substantial facelift in the Enjoy Release, 4.6A, which warranted the new name Workflow Builder.\u003Cbr\u003E\u003Cbr\u003E","\u003Cp\u003ENeed for Workflow\u003Cbr\u003E\u003Cp\u003EA business process can consist of several steps. Historically, the tasks have been coordinated manually or by some informal means of communication (sticky note, e-mail, shouting, and so on). \u003Cbr\u003E\u003Cbr\u003EThe common problem in these approaches is :\u003Cbr\u003E Inefficiency\u003Cbr\u003E Each lacks a way to trace where a task is\u003Cbr\u003E Who executed (or is executing it),\u003Cbr\u003E How much time it required. \u003Cbr\u003EIn contrast, the workflow ensures that the right work is sent to right person at the right time in the right sequence with the right information. \u003Cbr\u003E","\u003Cp\u003EWhy SAP Workflow?\u003Cbr\u003E\u003Cp\u003ETool for the automization of business processes\u003Cbr\u003E Not tied up to any particular application\u003Cbr\u003E Operates uniformly across applications\u003Cbr\u003E Coordinate all participating tasks\u003Cbr\u003E Provide users with active support\u003Cbr\u003E\u003Cbr\u003E","\u003Cp\u003EWorkflow Boundaries\u003Cbr\u003E\u003Cp\u003EThe component uses the existing transactions & function modules. The functionality and operability of the existing transactions and function modules are neither changed nor restricted by the workflow control. \u003Cbr\u003ESAP Business Workflow does not intervene in the programmed processes within a transaction\u003Cbr\u003E The component makes the R\u002F3 System easier to operate, which is particularly useful for inexperienced or occasional users.\u003Cbr\u003E\u003Cbr\u003E",h,"\u003Cp\u003EWorkflow\u003Cbr\u003E\u003Cp\u003EA workflow consists of a sequence of steps, which are processed either by people or automatically by the system.\u003Cbr\u003E","\u003Cp\u003EWorkflow Builder\u003Cbr\u003E\u003Cp\u003EModeling tool for creating a workflow definition.\u003Cbr\u003ECreating and process workflow definition\u003Cbr\u003ETest and activate a workflow definition\u003Cbr\u003E","\u003Cp\u003EWorkflow Definition\u003Cbr\u003E\u003Cp\u003ETechnical description of a workflow\u003Cbr\u003EWorkflow definition is made up of individual steps and events with one step and one or more events making up one unit. These units can be arranged in sequence or in parallel.\u003Cbr\u003EThe workflow definition is the set of rules that determine the path that the process takes. For example, how a purchase requisition is processed, from the initial request to the creation of the purchase order\u003Cbr\u003E","\u003Cp\u003EWorkflow Instance\u003Cbr\u003E\u003Cp\u003EA Workflow Instance, which is often simply referred to as the workflow, is a single workflow run. For example, the processing of a single purchase requisition for computers. \u003Cbr\u003E","\u003Cp\u003ETask\u003Cbr\u003E\u003Cp\u003EThe Tasks are the steps in the process, which have to be performed either by people or automatically by the software. For example, to check for the availability of the spare computers in the company. \u003Cbr\u003EDuring runtime a tasks is represent as a Workitem.\u003Cbr\u003EFollowing tasks exist in the workflow context:\u003Cbr\u003ESingle-step task\u003Cbr\u003EActivity in which an object method is executed on a specific object\u003Cbr\u003EMulti-step task (Workflow)\u003Cbr\u003EActivity whose description includes reference to a workflow definition\u003Cbr\u003E","\u003Cp\u003EWork Item\u003Cbr\u003E\u003Cp\u003EA Work item is the task instance that is performed as a single workflow step. For example, check that there are no spare computers available in the company. \u003Cbr\u003E","\u003Cp\u003EAgent\u003Cbr\u003E\u003Cp\u003EAgents are the people who process the tasks (via the work items). For example, requisitioner and a member of the purchasing department.\u003Cbr\u003EA system user who participates actively in SAP Business Workflow and executes work items\u003Cbr\u003ETypes of agents available\u003Cbr\u003EPossible agent\u003Cbr\u003EUser who is organizationally authorized to start a task and execute the associated work item\u003Cbr\u003EResponsible agent\u003Cbr\u003EUser assigned locally to a step in the workflow definition\u003Cbr\u003EExcluded agent\u003Cbr\u003EUser who is excluded from processing a work item\u003Cbr\u003E","\u003Cp\u003EContainer\u003Cbr\u003E\u003Cp\u003EContainer is the place where all the data used in the workflow is collected.\u003Cbr\u003EBasic common data structure of the various definition.\u003Cbr\u003EContainers have container elements for holding the following:\u003Cbr\u003EValues (Constants)\u003Cbr\u003EStructure\u003Cbr\u003EObject references \u003Cbr\u003EComplex types\u003Cbr\u003EThe container elements can be used to control the execution of work items and workflows.\u003Cbr\u003ETypes of container:\u003Cbr\u003EWorkflow container\u003Cbr\u003ETask Container\u003Cbr\u003EEvent Container\u003Cbr\u003EMethod Container \u003Cbr\u003ERule Container\u003Cbr\u003E","\u003Cp\u003EBinding\u003Cbr\u003E\u003Cp\u003EBinding is the set of rules that define which data is passed to which part of the process. \u003Cbr\u003EAssignment of values to a container element at runtime.\u003Cbr\u003EBinding definition:\u003Cbr\u003ESpecification of assignment rules describing the assignment of data to a container element or the exchange of data between two container element.\u003Cbr\u003E","\u003Cp\u003EBusiness Object Builder\u003Cbr\u003E\u003Cp\u003ETool for creating and processing business object types.\u003Cbr\u003ECan be used to access the definition of an object type\u003Cbr\u003ESubtypes can be created for existing Business object type\u003Cbr\u003E","\u003Cp\u003EObject Type\t\u003Cbr\u003E\u003Cp\u003EBusiness objects integrate the data and functions of business applications into your workflows. \u003Cbr\u003E\u003Cbr\u003EThey enable workflow engine to communicate with business applications with all the flexibility and robustness required for a production environment\u003Cbr\u003E","\u003Cp\u003EObject Type\u003Cbr\u003E\u003Cp\u003EDescription of data (objects) in the system created at definition time in the Business Object Builder\u003Cbr\u003EObject types are described and implemented by specifying the following components:\u003Cbr\u003EBasic data\u003Cbr\u003EKey fields\u003Cbr\u003EAttributes\u003Cbr\u003EMethods with parameters, result and exceptions\u003Cbr\u003EEvents with parameters\u003Cbr\u003EImplementation program\u003Cbr\u003EThe Object type must be defined before its data (Objects) can be used in the system.\u003Cbr\u003E","\u003Cp\u003EWorkflow project Approach\u003Cbr\u003E","\u003Cp\u003EBusiness Workflow Overview\u003Cbr\u003E\u003Cp\u003E1\u003Cbr\u003E\u003Cp\u003EPrepareMe\u003Cbr\u003E\u003Cp\u003E2\u003Cbr\u003E\u003Cp\u003ETellMe\u003Cbr\u003E\u003Cp\u003E3\u003Cbr\u003E\u003Cp\u003EShowMe\u003Cbr\u003E\u003Cp\u003E4\u003Cbr\u003E\u003Cp\u003ELetMe\u003Cbr\u003E\u003Cp\u003E5\u003Cbr\u003E\u003Cp\u003EHelpMe\u003Cbr\u003E","\u003Cp\u003EWORKFLOW ARCHITECTURE\u003Cbr\u003E","\u003Cp\u003EWorkflow Architecture\u003Cbr\u003E","\u003Cp\u003EWORKFLOW CUSTOMIZING\u003Cbr\u003E","\u003Cp\u003EWhat Auto-Customizing Does\u003Cbr\u003E\u003Cp\u003EThe automatic workflow customizing sets up the system using defaults so that you ready to use the system as quickly as possible.\u003Cbr\u003EThe most important activities are as follows:\u003Cbr\u003EMaintain Active Plan Version\u003Cbr\u003EPlan version (with its contents) is seen by the workflow system as the only valid plan version.\u003Cbr\u003EAll SAP Workflows supplied automatically become part of the plan version that has been selected as the active plan version\u003Cbr\u003EOnly one of the plan versions created in the system can be active.\u003Cbr\u003EConfigure RFC Destination\u003Cbr\u003EThe runtime system always executes its tRFC calls via the logical destination WORKFLOW_LOCAL_XXX (XXX stands for client number)\u003Cbr\u003EThe workflow runtime system is client dependent i.e. a single workflow instance normally executes within one client\u003Cbr\u003EMaintain Workflow System Administrator\u003Cbr\u003ESchedule Background Job for Missed Deadlines\u003Cbr\u003EMaintain Prefix Numbers\u003Cbr\u003E","\u003Cp\u003EAutomatic Workflow Customizing: SWU3\u003Cbr\u003E\u003Cp\u003ECustomizing the system is the very first step that you will take when you plan to use workflow\u003Cbr\u003E","\u003Cp\u003EORGANIZATIONAL STRUCTURE\u003Cbr\u003E","\u003Cp\u003ECreating an Organizational Plan\u003Cbr\u003E\u003Cp\u003EThe above diagram illustrates that the first step in Simple Maintenance is to create a root organizational unit. Once one organizational unit has been created, the organizational units below it have to be created. \u003Cbr\u003EOrganizational units and jobs may be created in any order but must exist before the associated positions are created. \u003Cbr\u003EJobs may exist in the job index or may be created once the model contains an organizational unit. \u003Cbr\u003EPositions are created once the relevant jobs have been created in the job index. \u003Cbr\u003ETasks are assigned using jobs and positions. \u003Cbr\u003EHolders are assigned to positions, not to jobs. \u003Cbr\u003E","\u003Cp\u003EAssignment Workflow Tasks: Organizational Objects\u003Cbr\u003E\u003Cp\u003EThe relevant users receive a work item at runtime.\u003Cbr\u003ETask 1: User 1 (via manager job)\u003Cbr\u003ETask 2: User 1, user 2 (via manager job\u002Fjob for secretary)\u003Cbr\u003ETask 3: User 1, user 2, user 3, user 4 (via organizational unit)\u003Cbr\u003ETask 4: User 1, user 3, user 4 (via position for head of FI department\u002Fjob for FI employee)\u003Cbr\u003ETask 5: User 2 (via secretary job)\u003Cbr\u003ETask 6: User 3, user 4 (via job for FI employee)\u003Cbr\u003E","\u003Cp\u003ECreate Job: PPOM\u003Cbr\u003E","\u003Cp\u003EPositions\u003Cbr\u003E","\u003Cp\u003ECreate Position: PO13\u003Cbr\u003E","\u003Cp\u003EBasic HR Definition for Workflow\u003Cbr\u003E","\u003Cp\u003ECreation of Workflow or Tasks\r\nthrough T-Code: PFTC\u003Cbr\u003E\u003Cp\u003EClient Independent\u003Cbr\u003EStandard task : TS\u003Cbr\u003EWorkflow Template : WS\u003Cbr\u003ETask Group : TG\u003Cbr\u003E\u003Cp\u003EClient Dependent\u003Cbr\u003ECustomer tasks : T\u003Cbr\u003EWorkflow Task : WF\u003Cbr\u003E\u003Cp\u003ENo longer used, supported in previous versions\u003Cbr\u003E","\u003Cp\u003EFive Questions for each part of a Business Process and how to map them in Steps\u002FTasks\u003Cbr\u003E","\u003Cp\u003EIn What Order?: Workflow Definition\u003Cbr\u003E\u003Cp\u003EWorkflow definition controls the calling sequence of each step. Steps like workflow, can also be triggered by events.\u003Cbr\u003E","\u003Cp\u003EIn What Order?: Workflow Builder (SWDD)…How it looks\u003Cbr\u003E","\u003Cp\u003EWith What Object? What?: \r\nT-code: PFTC, Calling Methods within a Task\u003Cbr\u003E\u003Cp\u003EAttach Object Method here, give Object Category, Object Type and Method Name\u003Cbr\u003E\u003Cp\u003EDefine binding between Task Container and Method here.\u003Cbr\u003E\u003Cp\u003EDefine \u003Cbr\u003ESynch \u002F Asynch\u003Cbr\u003EDialog \u002F Without Dialog\u003Cbr\u003E","\u003Cp\u003EWith What Object?:\r\nBusiness Object and its Method\u003Cbr\u003E\u003Cp\u003EBusiness Object \u003Cbr\u003EE.g. BUS2089\u003Cbr\u003E","\u003Cp\u003EWhat?: Method Configurations\u003Cbr\u003E","\u003Cp\u003EWhat?: Method Parameters\u003Cbr\u003E","\u003Cp\u003EWHO: Agents\u003Cbr\u003E\u003Cp\u003EResponsible Agents\u003Cbr\u003E\u003Cp\u003EExcluded Agents\u003Cbr\u003E\u003Cp\u003EPossible Agents\u003Cbr\u003E\u003Cp\u003EPossible Agents assignment\u003Cbr\u003E\u003Cp\u003EButton turns green if agent assignment is configured\u003Cbr\u003E","\u003Cp\u003EWhen? T-code: PFTC\u003Cbr\u003E\u003Cp\u003EEvents can be used to trigger:\u003Cbr\u003EWorkflow instantiation\u003Cbr\u003ECommencement of a step\u003Cbr\u003ECompletion of a step, normally for asynchronous tasks\u003Cbr\u003E","\u003Cp\u003EWhen? \r\nSWDD? Double Click on Step…\u003Cbr\u003E\u003Cp\u003EA Condition, Multiple Condition and User Decision step have more than one outcome and depending on the conditions only one of them is executed.\u003Cbr\u003EOutcomes can be labeled for easy understanding.\u003Cbr\u003E","\u003Cp\u003ESTEP TYPES\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E User Decision \u003Cbr\u003E \u003Cbr\u003E - The agent is asked a question and given a pre-defined list of answers\u003Cbr\u003E - All the options are available in the work item.\u003Cbr\u003E - Each answer is a separate branch in workflow\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Loop (Until) \u003Cbr\u003E \u003Cbr\u003E Runtime use:\u003Cbr\u003E - for the purpose of iterative processing of a few steps based on certain condition.\u003Cbr\u003E \u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Send Mail:\u003Cbr\u003E - The text entered in this step type is sent as an e-mail\u003Cbr\u003E - Both external (on the outlook id) and internal mails (SAP mails) can be sent\u003Cbr\u003E \u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003ESend Mail:\u003Cbr\u003E\u003Cp\u003EThe subject line of the mail - 50 characters at the max.\u003Cbr\u003E\u003Cp\u003ETo insert Container Elements \u003Cbr\u003E\u003Cp\u003ETo enter text in mail\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003ESend mail:\u003Cbr\u003E \u003Cbr\u003E\u003Cp\u003EWithin the Task (under the CONTROL tab) The subject line of mail shown in Work item Text\u003Cbr\u003E\u003Cp\u003EThe Mail Text is present under the description Tab within the Task \u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Condition \u003Cbr\u003E Run time use:\u003Cbr\u003E - Can be used in a scenario where further course of action depends on the condition being true or false\u003Cbr\u003E","\u003Cp\u003ECondition\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003EProcess Control \u003Cbr\u003E - This can be used to cancel the execution of a work item or workflow or set a work item to obsolete\u003Cbr\u003E - It facilitates the alternate steps to be taken in the process obsolete branch\u003Cbr\u003E \u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003EProcess Control:\u003Cbr\u003E\u003Cbr\u003E\u003Cp\u003EThe options available with Process control\u003Cbr\u003E\u003Cp\u003EThe workflow step is to be mentioned depending on the Function chosen\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Multiple Condition:\u003Cbr\u003E \u003Cbr\u003E \u003Cbr\u003E Based on the value of a workflow container element one of the several branches in workflow is processed\u003Cbr\u003E \u003Cbr\u003E","\u003Cp\u003EMultiple Condition\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Event Creator :\u003Cbr\u003E - To raise an event in the workflow\u003Cbr\u003E \u003Cbr\u003E - Data moves from workflow to event \u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Wait:\u003Cbr\u003E - The system waits for a specific event to be triggered\u003Cbr\u003E - The work item is only completed if the expected event occurs\u003Cbr\u003E\u003Cbr\u003E\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Fork:\u003Cbr\u003E - Used for the purpose of parallel processing \u003Cbr\u003E - The user can define the number of parallel processes and how many should be completed for the Fork to terminate and workflow to continue \u003Cbr\u003E - The fork can be terminated by defining a condition too\u003Cbr\u003E\u003Cbr\u003E \u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Container operation:\u003Cbr\u003EFor the purpose of performing arithmetic operations or value assignments to workflow container \u003Cbr\u003EConstants and data within workflow can be used\u003Cbr\u003EMultiline operations are allowed\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003EAd hoc anchor\u003Cbr\u003E- Gives user the option to select between various workflows at runtime\u003Cbr\u003E- The steps of the selected Workflow shall replace this one\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Web Activity\u003Cbr\u003E - The selected container elements are posted using the http protocol in an XML or SOAP message\u003Cbr\u003E","\u003Cp\u003EStep Types in Workflow\u003Cbr\u003E\u003Cp\u003E Subworkflow:\u003Cbr\u003E - An activity that refers to another workflow rather than a task\u003Cbr\u003E \u003Cbr\u003EUndefined Step:\u003Cbr\u003E \u003Cbr\u003E -These can be used as placeholders during development \u003Cbr\u003E \u003Cbr\u003E - They are ignored at run time\u003Cbr\u003E \u003Cbr\u003E\u003Cbr\u003E","\u003Cp\u003ECONTAINER & BINDING\u003Cbr\u003E","\u003Cp\u003EWhat is a Container\u003Cbr\u003E\u003Cp\u003EContainers are a common way of holding data throughout the workflow instance’s lifespan. \u003Cbr\u003EContainers are used in interface between different parts of the workflow and between the workflow and business applications.\u003Cbr\u003E","\u003Cp\u003EType of Containers\u003Cbr\u003E\u003Cp\u003EA workflow container for each workflow and subworkflow\u003Cbr\u003EOnly container elements classified as import can be filled when the workflow is started.\u003Cbr\u003EA task container for each task\u003Cbr\u003EImport container elements are filled from the workflow container and export container elements are transferred back.\u003Cbr\u003EA method container for each method\u003Cbr\u003EImport container elements are filled from task container and export container elements are transferred back.\u003Cbr\u003EAn event container for each event\u003Cbr\u003EAll event containers are export container elements only.\u003Cbr\u003EA rule container for each rule\u003Cbr\u003EThe import container elements are filled from the workflow container (or task container). The _RULE_RESULT elements is the only export parameter and this is optional.\u003Cbr\u003E","\u003Cp\u003EBinding\u003Cbr\u003E\u003Cp\u003EData can be passed from one type to another using binding.\u003Cbr\u003EAt runtime, the bindings are executed at the appropriate point in the workflow.\u003Cbr\u003EFor instance, for a synchronous task, the workflow-to-task binding is executed as part of work item creation and the task-to-workflow binding is executed as part of work item completion.\u003Cbr\u003E","\u003Cp\u003EContainers and Bindings\u003Cbr\u003E","\u003Cp\u003EWORKITEM\u003Cbr\u003E","\u003Cp\u003EWork Item\u003Cbr\u003E\u003Cp\u003EObject that represents a task or action in the workflow system at runtime.\u003Cbr\u003EWork items are subdivided into a specific work item type according to their assignments. The internal processing procedures are controlled via this work item type. The work item type determines which statuses and transitions are valid. \u003Cbr\u003EDepending on the work item type, some of these work items are displayed in a user's work list. Other work items, on the other hand, are only used and processed internally. \u003Cbr\u003E","\u003Cp\u003EWork item Types\u003Cbr\u003E\u003Cp\u003EA Work item that represents a Work Queue\u003Cbr\u003EB Work item for Background step\u003Cbr\u003EC Work item that represents a container linkage\u003Cbr\u003ED Deadline work item; Notification upon Missed Deadline\u003Cbr\u003EE Workitem that waits for an Event (Wait step)\u003Cbr\u003EF Workflow (Also subworkflow)\u003Cbr\u003EN Notification Item (Obsolete)\u003Cbr\u003EP Work item that Represents a Remote Work item (Proxy WI)\u003Cbr\u003ER Work item that Represents a Remote Work item (http) \u003Cbr\u003EW Dialog work item; Represents a Single-step Task \u003Cbr\u003EX Work item that Represents a Block\u003Cbr\u003E","\u003Cp\u003EWork item Status\u003Cbr\u003E\u003Cp\u003EWAITING: Waiting (Also: Work items in Resubmission)\u003Cbr\u003EREADY\u003Cbr\u003ESELECTED: Reserved\u003Cbr\u003ESTARTED: In Process\u003Cbr\u003EERROR \u003Cbr\u003ECOMMITED: Executed (Only If Expl. End Confirmation Is Expected)\u003Cbr\u003ECOMPLETED \u003Cbr\u003ECANCELLED: Logically Deleted\u003Cbr\u003ECHECKED: In Preparation\u003Cbr\u003EEXCPCAUGHT: Exception caught\u003Cbr\u003EEXCPHANDLR: Exception Being Handled\u003Cbr\u003E","\u003Cp\u003EDeadline Monitoring\u003Cbr\u003E","\u003Cp\u003EDeadlines for Workflow Steps\u003Cbr\u003E","\u003Cp\u003EDeadlines for Workflow Steps\u003Cbr\u003E\u003Cp\u003ERequested start\u003Cbr\u003EEarliest possible point in time for the commencement of processing\r\n\u003Cbr\u003EThe requested start is not a monitored deadline in the strict sense. It is when a work item first appears in an agent's inbox.\u003Cbr\u003ERequested end\u003Cbr\u003ERequested end deadline for processing a step\u003Cbr\u003ELatest start\u003Cbr\u003ELatest start deadline for processing a step\u003Cbr\u003ELatest end\u003Cbr\u003EDeadline by which the processing of a step must be completed. \u003Cbr\u003ENote: \u003Cbr\u003E\t\tAll deadlines are monitored using the background job SWWDHEX with job class A. The job calls the report RSWWDHEX.\u003Cbr\u003E","\u003Cp\u003EBusiness Objects\u003Cbr\u003E","\u003Cp\u003ECreation of Object type\u003Cbr\u003E\u003Cp\u003ENew Object type\u003Cbr\u003ESub-type of an existing Object type\u003Cbr\u003EAdv of sub-type: It automatically inherits all the components (methods, attributes, and events) of the original object type including its implementation.\u003Cbr\u003E","\u003Cp\u003ESub-type\u003Cbr\u003E\u003Cp\u003ETools-\u003EBusiness Workflow -\u003E Development -\u003E Definition Tools -\u003E Business Object Builder\u003Cbr\u003EIn the field object type enter the object type you want to extend.\u003Cbr\u003EChoose subtype.\u003Cbr\u003EEnter a unique name, object name, name, short description and name of the program.\u003Cbr\u003ESave it.\u003Cbr\u003E","\u003Cp\u003EObject Type Definition\u003Cbr\u003E\u003Cp\u003ETransaction Code : SWO1\u003Cbr\u003EBasic data\u003Cbr\u003EGeneral: Super Type , Release , Generation\u003Cbr\u003EChange & Transport\u003Cbr\u003EDefault : Method & Attribute\u003Cbr\u003E\u003Cbr\u003EContd.\u003Cbr\u003E","\u003Cp\u003EObject Type Definition (contd..)\u003Cbr\u003E\u003Cp\u003EKey Fields\u003Cbr\u003EDetermines which application table (s) the data is saved\u003Cbr\u003EOne or more key fields can be used\u003Cbr\u003ECombined key field values provide unique identification for an object instance.\u003Cbr\u003ECan refer to a database table or a view.\u003Cbr\u003E \u003Cbr\u003E Contd…\u003Cbr\u003E \u003Cbr\u003E\u003Cbr\u003E","\u003Cp\u003ECreation of Key fields\u003Cbr\u003E\u003Cp\u003EPosition the cursor on the entry Key fields and choose the “create” button.\u003Cbr\u003EIf you want to create the key field with a database table then enter ‘yes’.\u003Cbr\u003EEnter the table name e.g.: VBAK\u003Cbr\u003EThe list of key fields will be displayed, select the respective ones, e.g.: VBLEN.\u003Cbr\u003E","\u003Cp\u003EObject Type Definition (contd…)\u003Cbr\u003E\u003Cp\u003EAttributes\u003Cbr\u003EProperty of an Object\u003Cbr\u003ESource of Information\u003Cbr\u003EDatabase Field\u003Cbr\u003EVirtual\u003Cbr\u003EObject\u003Cbr\u003EMulti Line:\u003Cbr\u003EA multiple-line attribute corresponds to an internal table used in ABAP\u003Cbr\u003EContd.\u003Cbr\u003E\u003Cp\u003EA database attribute is defined with reference to a column (not a key column) of the related application table.\u003Cbr\u003E\u003Cp\u003EA virtual attribute is calculated with ABAP code.\u003Cbr\u003E","\u003Cp\u003ECreation of Attribute\u003Cbr\u003E","\u003Cp\u003EObject Type Definition contd.\u003Cbr\u003E\u003Cp\u003EMethods\u003Cbr\u003EDialog\u002FBackground\u003Cbr\u003ESynchronous\u002FAsynchronous\u003Cbr\u003EFunction Module\u003Cbr\u003EBAPI\u003Cbr\u003ETransaction Code\u003Cbr\u003EReport\u003Cbr\u003EOther\u003Cbr\u003EContd.\u003Cbr\u003E","\u003Cp\u003ETypes of methods\u003Cbr\u003E\u003Cp\u003ESynchronous methods:\u003Cbr\u003EExport parameters are returned directly to the calling program.\u003Cbr\u003EExceptions may be triggered.\u003Cbr\u003EAsynchronous methods:\u003Cbr\u003EMethod execution consists of a synchronous part and subsequent update.\u003Cbr\u003EExport parameters are not authorized.\u003Cbr\u003EExceptions are only possible in the synchronous part.\u003Cbr\u003E\u003Cp\u003EActive check box represents a Synchronous method. Inactive represents an Asynchronous method.\u003Cbr\u003E","\u003Cp\u003EParameter calls from methods\u003Cbr\u003E\u003Cp\u003EImport parameters\u003Cbr\u003EExport parameters\u003Cbr\u003EResult (special export parameter)\u003Cbr\u003EExceptions:\u003Cbr\u003E Temporary error\u003Cbr\u003E Application error\u003Cbr\u003E System error\u003Cbr\u003E","\u003Cp\u003EObject Type Definition Contd...\u003Cbr\u003E\u003Cp\u003EEvents\u003Cbr\u003ESystem wide message about a change in state of an Object\u003Cbr\u003EEvents should be used only in conjunction with SAP Object\u003Cbr\u003EThe SAP application must raise the event and not the Object type.\u003Cbr\u003E","\u003Cp\u003ERelease Status\u003Cbr\u003E\u003Cp\u003EModeled\t:\t\t\t\t \t\t\tNot accessible at runtime.\u003Cbr\u003EImplemented:\t\t\t\t \t\t\tOnly in test or internal use, possibly unstable.\u003Cbr\u003EReleased:\t\t\t\t\t\t\tReleased for use by the customer.\u003Cbr\u003EObsolete:\u003Cbr\u003E\t\tThe functionality has been replaced. The old functionality is still supported for two releases.\u003Cbr\u003E\u003Cbr\u003E","\u003Cp\u003EMacros used during SAP Object Programming\u003Cbr\u003E\u003Cp\u003EInclude \u003Ccntn01\u003E OR Include \u003Cobject\u003E\u003Cbr\u003EContainer Declaration : \tSWC_CONTAINER \u003Ccontainer\u003E\u003Cbr\u003EContainer Initialization : \tSWC_CREATE_CONTAINER \u003Cbr\u003E\t\t\u003Ccontainer\u003E\u003Cbr\u003EContd.\u003Cbr\u003E","\u003Cp\u003EMacros used during SAP Object Programming contd.\u003Cbr\u003E\u003Cp\u003EWriting a Field value : \u003Cbr\u003E\t\tSWC_SET_ELEMENT \u003Ccontainer\u003E \u003Cbr\u003E\t\t\u003Celement\u003E \u003Cvalue\u003E\u003Cbr\u003EReading a Field value : \u003Cbr\u003E\t\tSWC_GET_ELEMENT \u003Ccontainer\u003E \u003Cbr\u003E\t\t\u003Celement\u003E \u003Cvalue\u003E\u003Cbr\u003EWriting a Multi Line field value:\u003Cbr\u003E\t\tSWC_SET_TABLE \u003Ccontainer\u003E \u003Cbr\u003E\t\t\u003Celement\u003E \u003Cvalue\u003E\u003Cbr\u003EReading a Multi Line field Value:\u003Cbr\u003E\t\tSWC_GET_TABLE \u003Ccontainer\u003E \u003Cbr\u003E\t\t\u003Celement\u003E \u003Cvalue\u003E\u003Cbr\u003E","\u003Cp\u003EDELEGATION\u003Cbr\u003E","\u003Cp\u003EDelegation\u003Cbr\u003E","\u003Cp\u003EDelegation\u003Cbr\u003E\u003Cp\u003EIf you create a subtype of an object type, you can choose to delegate the superior type to the subtype. Delegation means that wherever the super type is referenced throughout workflow, the subtype will actually be used instead.\u003Cbr\u003EDelegation lets you use all the existing tasks and workflows based on the SAP object type as if they were using your own subtype.\u003Cbr\u003ECustomers use their own object extensions with the tasks, events, etc. supplied by SAP \u003Cbr\u003EWithout having to redefine existing tasks, you can use standard objects with customer extensions\u003Cbr\u003E","\u003Cp\u003EEVENT\u003Cbr\u003E","\u003Cp\u003EEvents\u003Cbr\u003EEvents are part of business object, are triggered for changes in the state of the object, which can cause other processes to begin.\u003Cbr\u003EUsed for Triggering the Workflow\u003Cbr\u003ENecessary information needs to be entered on “Triggering Events” tab of the Workflow Builder.\u003Cbr\u003EWorkflow Engine will automatically generate the binding. You can change it afterwards.\u003Cbr\u003EEvents can also be defined in Classes. Their behavior is similar to the events declared in Objects.\u003Cbr\u003E","\u003Cp\u003EEvent Creators & Receivers\u003Cbr\u003E","\u003Cp\u003EEvent Creation and Triggering\u003Cbr\u003E\u003Cp\u003EDefine Object in Business Object Builder\u003Cbr\u003ETrigger Event:\u003Cbr\u003EImplicitly via generic tools, for example change documents, status management, message control etc\u003Cbr\u003EExplicitly via function module\u003Cbr\u003ESWE_CREATE_EVENT\u003Cbr\u003E","\u003Cp\u003EEvent Triggering: Status Change\u003Cbr\u003E","\u003Cp\u003EEvent Triggering: Message control\u003Cbr\u003E\u003Cp\u003ECreate a separate output type and declare 9 (workflow event) as transmission medium\u003Cbr\u003ECreate a condition table\u003Cbr\u003ECreate a access sequence\u003Cbr\u003EAssign the access sequence to the defined output type for a workflow event\u003Cbr\u003EDefine condition records and declare the event\u003Cbr\u003EAssign the output type to a procedure\u003Cbr\u003E","\u003Cp\u003EEvent Triggering: Change Documents\u003Cbr\u003E","\u003Cp\u003EEvent Triggering: ABAP Code\u003Cbr\u003E\u003Cp\u003EFill event container with event parameters\u003Cbr\u003ECompose object key for triggering object\u003Cbr\u003ECall SWE_EVENT_CREATE\u003Cbr\u003EFM Call error handling\u003Cbr\u003ETrigger event with explicit commit work\u003Cbr\u003E","\u003Cp\u003EBusiness Workplace\u003Cbr\u003E","\u003Cp\u003EWorklist as Interface for End User\u003Cbr\u003E\u003Cp\u003EThe Business Workplace is part of the SAP Business Workflow runtime environment. The employees responsible receive the documents and work items for processing in the Business Workplace. Once a task (= a work item) has been executed and completed, the process can be continued. \u003Cbr\u003EThe worklist contains all the work items (all the activities to be processed) assigned to this user. The Business Workplace is therefore the most important interface for an employee in their day-to-day work.\u003Cbr\u003E","\u003Cp\u003EBusiness Workplace in SAP R\u002F3\u003Cbr\u003E\u003Cp\u003EThe Business Workplace has three screen areas: \u003Cbr\u003EOverview tree\u003Cbr\u003EWorklist\u003Cbr\u003EWork item preview\u003Cbr\u003E",h,"\u003Cp\u003EDemo: Notification of Absence\u003Cbr\u003E",h,"\u003Cp\u003EMONITORING & ANALYSIS\u003Cbr\u003E","\u003Cp\u003EMonitoring & Analysis\u003Cbr\u003E\u003Cp\u003EReporting\u003Cbr\u003EWork Item Monitoring\u003Cbr\u003EWork Item Analysis\u003Cbr\u003EWork load Analysis\u003Cbr\u003EWorkflow Diagnostic Tool\u003Cbr\u003E","\u003Cp\u003EReporting\u003Cbr\u003E\u003Cp\u003EReporting on Workflow Progress\u003Cbr\u003EWork Items by Processing Duration\u003Cbr\u003EWork Items with Monitored Deadlines\u003Cbr\u003EWork Items per Task\u003Cbr\u003EReporting on Agent Behavior\u003Cbr\u003E","\u003Cp\u003EReporting on Workflow Progress\u003Cbr\u003E\u003Cp\u003ETransaction code: SWI1\u003Cbr\u003EThis report shows all the work items of the particular task in a particular time period.\u003Cbr\u003EThis report is also used for monitoring the Workitem \u003Cbr\u003E","\u003Cp\u003EReporting on Workflow Progress\u003Cbr\u003E\u003Cp\u003EWorkflows for Object\u003Cbr\u003ETransaction code: SWI6. \u003Cbr\u003EThis report shows all workflow instances linked to a particular object instance.\u003Cbr\u003EExample: Particular Purchase Order\u003Cbr\u003E","\u003Cp\u003EReporting on Workflow Progress\u003Cbr\u003E\u003Cp\u003EWorkflows for Object type\u003Cbr\u003ETransaction code SWI14\u003Cbr\u003EThis report shows all the work items and workflow instances for all object instances of a business object type.\u003Cbr\u003EExample: Workflows related to all Purchase Orders\u003Cbr\u003E","\u003Cp\u003EWork Items by Processing Duration\r\n\u003Cbr\u003E\u003Cp\u003ETransaction code: SWI2_DURA\u003Cbr\u003EThis report gives list of work items based on their processing duration for specified type or for a specified tasks.\u003Cbr\u003EThis report is also used to analyze a Work item.\u003Cbr\u003E","\u003Cp\u003EWork Items with Monitored Deadlines\r\n\u003Cbr\u003E\u003Cp\u003ETransaction Code: SWI2_DEAD\u003Cbr\u003EThis report displays work items with their deadline information, if they are set.\u003Cbr\u003EFor each missed deadline, the current status of the work item is shown.\u003Cbr\u003EThis report is also used to analyze a Work item.\u003Cbr\u003E","\u003Cp\u003EWork Items per Task\u003Cbr\u003E\u003Cp\u003ETransaction code: SWI2_FREQ\u003Cbr\u003EThis report shows the number of work items created in the specified period.\u003Cbr\u003EThis report is also used to analyze a Work item.\u003Cbr\u003E","\u003Cp\u003EReporting on Agent Behavior\u003Cbr\u003E\u003Cp\u003ETransaction Code: SWI5\u003Cbr\u003EWith the help of this report , you can monitor how quickly agent act on their work items\u003Cbr\u003EThis report is useful for assessing workload over particular time period.\u003Cbr\u003EThis report is useful for reporting on the type and frequency of tasks being sent to an agent.\u003Cbr\u003EThis report is also used to analyze a Work load.\u003Cbr\u003E","\u003Cp\u003EWorkflow Diagnostic Tool\u003Cbr\u003E\u003Cp\u003ETransaction Code: SWUD\u003Cbr\u003EA primary diagnostic tool.\u003Cbr\u003EAnalyze workflow definition.\u003Cbr\u003EFollowing are the options available:\u003Cbr\u003EVerify workflow customizing\u003Cbr\u003EPerform Workflow Customizing\u003Cbr\u003EProblem: Task does not start\u003Cbr\u003ETo track down the exact cause of an error\u003Cbr\u003EProblem: Workflow is hanging\u003Cbr\u003EChoose this option when workflow starts but stops before completion, due to some error.\u003Cbr\u003ETest Environment\u003Cbr\u003EChoose this option when you want to access the complete suite of test tools from one place.\u003Cbr\u003EThis option will also display all the components (subworkflow, tasks, business objects, delegated business objects)\u003Cbr\u003E","\u003Cp\u003EWorkflow Diagnosis\u003Cbr\u003E\u003Cp\u003ESection 1: The current workflow definition to be analyzed.\u003Cbr\u003E\u003Cp\u003ESection 2: The list of test options\u003Cbr\u003E\u003Cp\u003ESection 3: A list of last tem workflow definitions.\u003Cbr\u003E","\u003Cp\u003EWorking with the Workflow Log\u003Cbr\u003E\u003Cp\u003EAt runtime, a workflow has its own work item (type F) that represents the workflow instance.\u003Cbr\u003EThe workflow log formats all the information created during the execution of the business process\u003Cbr\u003EStandard view\u003Cbr\u003EIntended for agents and process owners who want to get an overview of the steps processed.\u003Cbr\u003ETechnical view\u003Cbr\u003EIntended for developers and workflow administrator\u003Cbr\u003E","\u003Cp\u003EStandard View\u003Cbr\u003E\u003Cp\u003EWorkflow Chronicle (What processed when?\u003Cbr\u003EWorkflow Agents (Who Processed what?)\u003Cbr\u003EWorkflow Objects (What was processed?)\u003Cbr\u003E","\u003Cp\u003EWorkflow Chronicle\u003Cbr\u003E\u003Cp\u003E\tThe tab page Workflow Chronicle shows a hierarchical display of all the steps in the workflow. If workflow has a subworkflow structure, the subworkflow are also displayed.\u003Cbr\u003E","\u003Cp\u003EWorkflow Agents\u003Cbr\u003E\u003Cp\u003EThe Tab page Workflow Agents shows the agents involved in the\u003Cbr\u003Eworkflow. \u003Cbr\u003E\tFollowing options are displayed for each agent:\u003Cbr\u003EWhat action was carried out in what step\u003Cbr\u003EWhen this action was carried out\u003Cbr\u003EThe objects involved\u003Cbr\u003E","\u003Cp\u003EWorkflow Objects\u003Cbr\u003E\u003Cp\u003E\tThe tab page Workflow Objects lists the objects related to the workflow. This view shows what objects were created and processed.\u003Cbr\u003E","\u003Cp\u003ETechnical View\u003Cbr\u003E\u003Cp\u003EThe technical view shows technical nodes and control structures, container elements, agent data and workflow data.\u003Cbr\u003E","\u003Cp\u003EWorkflow Status\u003Cbr\u003E","\u003Cp\u003EWorkflow Log\u003Cbr\u003E","\u003Cp\u003EList of Transaction Code\u003Cbr\u003E\u003Cp\u003ESWO1: Business Object Builder\u003Cbr\u003ESWDD: Workflow Builder\u003Cbr\u003ESWUD: Workflow Diagnosis\u003Cbr\u003ESBWP: Business Workplace\u003Cbr\u003ESWU3: Automatic Workflow Customizing\u003Cbr\u003EPFTC: Maintain Task\u003Cbr\u003ESWO3: Business Object Repository Browser\u003Cbr\u003ESWE2: Event Linkage\u003Cbr\u003ESWI1: Report for Work items\u003Cbr\u003ESWI2_FREQ: Work Items per Task\u003Cbr\u003ESWI2_DEAD: Work Items with monitored Deadlines\u003Cbr\u003E"],href:"\u002Finformatika\u002Fbusiness-workflow",href_category:"\u002Finformatika",date:1635308502,related:[{id:281645,name:"Ecommerce. Shopping on the Internet",href:"\u002Finformatika\u002Fecommerce-shopping-on-the-internet",jpg:"jpg\u002F281645"},{id:332368,name:"Устройство компьютера",href:"\u002Finformatika\u002Fustroystvo-kompyutera-34",jpg:"jpg\u002F332368"},{id:253163,name:"Threads. Выполнение инструкций потоками",href:"\u002Finformatika\u002Fthreads-vypolnenie-instruktsiy-potokami",jpg:"jpg\u002F253163"},{id:233759,name:"Основные операции с данными в СУБД",href:"\u002Finformatika\u002Fosnovnye-operatsii-s-dannymi-v-subd",jpg:"jpg\u002F233759"},{id:254683,name:"Операционная система Windows",href:"\u002Finformatika\u002Foperatsionnaya-sistema-windows-89",jpg:"jpg\u002F254683"},{id:580130,name:"Scratсh - визуальная учебная среда для обучения школьников программированию",href:"\u002Finformatika\u002Fscratsh-vizualnaya-uchebnaya-sreda-dlya-obucheniya-1",jpg:"jpg\u002F580130"},{id:317603,name:"Системы счисления",href:"\u002Finformatika\u002Fsistemy-schisleniya-49",jpg:"jpg\u002F317603"},{id:109329,name:"Компьютерная графика. Цифровая обработка изображений, как сигналов. (Лекция 4)",href:"\u002Finformatika\u002Fkompyuternaya-grafika-tsifrovaya-obrabotka-izobrazheniy-kak",jpg:"jpg\u002F109329"},{id:2133,name:"Триггеры",href:"\u002Finformatika\u002Ftriggery-1",jpg:"jpg\u002F2133"},{id:542170,name:"Решение задач ЕГЭ типа В7",href:"\u002Finformatika\u002Freshenie-zadach-ege-tipa-v7",jpg:"jpg\u002F542170"},{id:435198,name:"Виды данных и информации. Формы представления информации и передачи данных",href:"\u002Finformatika\u002Fvidy-dannyh-i-informatsii-formy-predstavleniya",jpg:"jpg\u002F435198"},{id:590562,name:"Компьютерная графика. Элективный курс",href:"\u002Finformatika\u002Fkompyuternaya-grafika-elektivnyy-kurs",jpg:"jpg\u002F590562"},{id:100040,name:"Accounting applications on introduction computer to Microsoft Excel",href:"\u002Finformatika\u002Faccounting-applications-on-introduction-computer-to",jpg:"jpg\u002F100040"},{id:102413,name:"Защита информационных процессов в компьютерных системах",href:"\u002Finformatika\u002Fzashchita-informatsionnyh-protsessov-v-kompyuternyh-sistemah",jpg:"jpg\u002F102413"},{id:311079,name:"Информация в обществе и технике",href:"\u002Finformatika\u002Finformatsiya-v-obshchestve-i-tehnike",jpg:"jpg\u002F311079"},{id:318212,name:"Юридическая обработка правовой информации",href:"\u002Finformatika\u002Fyuridicheskaya-obrabotka-pravovoy-informatsii",jpg:"jpg\u002F318212"},{id:266860,name:"Доставка терминалов. Собственный процессинг",href:"\u002Finformatika\u002Fdostavka-terminalov-sobstvennyy-protsessing",jpg:"jpg\u002F266860"},{id:263767,name:"Информационные и коммуникационные технологии в образовании",href:"\u002Finformatika\u002Finformatsionnye-i-kommunikatsionnye-tehnologii-v-obrazovanii",jpg:"jpg\u002F263767"},{id:13279,name:"Использование CSS для макетирования",href:"\u002Finformatika\u002Fispolzovanie-css-dlya-maketirovaniya",jpg:"jpg\u002F13279"},{id:577990,name:"Склеивание мешков цепочек (3 кл.)",href:"\u002Finformatika\u002Fskleivanie-meshkov-tsepochek-3-kl",jpg:"jpg\u002F577990"},{id:141751,name:"Информационная безопасность",href:"\u002Finformatika\u002Finformatsionnaya-bezopasnost-9",jpg:"jpg\u002F141751"},{id:584730,name:"Создание игры в Construct 3",href:"\u002Finformatika\u002Fsozdanie-igry-v-construct-3",jpg:"jpg\u002F584730"},{id:12224,name:"Базы данных. Реляционная модель данных",href:"\u002Finformatika\u002Fbazy-dannyh-relyatsionnaya-model-dannyh",jpg:"jpg\u002F12224"},{id:555123,name:"Презентация к уроку по теме Понятие алгоритма, свойства алгоритмов.",href:"\u002Finformatika\u002Fprezentatsiya-k-uroku-po-teme-ponyatie",jpg:"jpg\u002F555123"},{id:348438,name:"Концепция нового товара или услуги",href:"\u002Finformatika\u002Fkontseptsiya-novogo-tovara-ili-uslugi-1",jpg:"jpg\u002F348438"},{id:283864,name:"Основы моделирования ГРП",href:"\u002Finformatika\u002Fosnovy-modelirovaniya-grp",jpg:"jpg\u002F283864"},{id:556215,name:"Анимированный кроссворд",href:"\u002Finformatika\u002Fanimirovannyy-krossvord-2",jpg:"jpg\u002F556215"},{id:439232,name:"Bazele programării",href:"\u002Finformatika\u002Fbazele-programrii",jpg:"jpg\u002F439232"}],navigation:{next:"\u002Fyurisprudentsiya\u002Ftrudovoy-rasporyadok-i-distsiplina-truda-1",next_name:"Трудовой распорядок и дисциплина труда",prev:"\u002Fmedetsina\u002Fekspertiza-opyaneniya",prev_name:"Экспертиза опьянения"}}}},state:{},_errors:{},serverRendered:d,config:{public:{SITE_NAME:K,SITE_HOST:"mypreza.com",SITE_LANG:L,API_BASE_URL:"https:\u002F\u002Fmypreza.com\u002Fapi\u002F",pwaManifest:{name:K,short_name:a,description:a,lang:L,start_url:"\u002F?standalone=true",display:"standalone",background_color:m,theme_color:"#000000",icons:[{src:"\u002F_nuxt\u002Ficons\u002F64x64.f2a6e93d.png",type:c,sizes:M,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F64x64.maskable.f2a6e93d.png",type:c,sizes:M,purpose:g},{src:"\u002F_nuxt\u002Ficons\u002F120x120.f2a6e93d.png",type:c,sizes:N,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F120x120.maskable.f2a6e93d.png",type:c,sizes:N,purpose:g},{src:"\u002F_nuxt\u002Ficons\u002F144x144.f2a6e93d.png",type:c,sizes:O,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F144x144.maskable.f2a6e93d.png",type:c,sizes:O,purpose:g},{src:"\u002F_nuxt\u002Ficons\u002F152x152.f2a6e93d.png",type:c,sizes:P,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F152x152.maskable.f2a6e93d.png",type:c,sizes:P,purpose:g},{src:"\u002F_nuxt\u002Ficons\u002F192x192.f2a6e93d.png",type:c,sizes:Q,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F192x192.maskable.f2a6e93d.png",type:c,sizes:Q,purpose:g},{src:"\u002F_nuxt\u002Ficons\u002F384x384.f2a6e93d.png",type:c,sizes:R,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F384x384.maskable.f2a6e93d.png",type:c,sizes:R,purpose:g},{src:"\u002F_nuxt\u002Ficons\u002F512x512.f2a6e93d.png",type:c,sizes:S,purpose:f},{src:"\u002F_nuxt\u002Ficons\u002F512x512.maskable.f2a6e93d.png",type:c,sizes:S,purpose:g}]},yandexMetrika:{id:"85004146",metrikaUrl:"https:\u002F\u002Fmc.yandex.ru\u002Fmetrika\u002Ftag.js",accurateTrackBounce:d,childIframe:e,clickmap:e,defer:e,useRuntimeConfig:d,trackHash:e,trackLinks:d,type:b,webvisor:e,triggerEvent:e,consoleLog:d,partytown:e,isDev:e}},app:{baseURL:"\u002F",buildAssetsDir:"\u002F_nuxt\u002F",cdnURL:a}},pinia:{app:{meta:{h1:o,main_text:a,main_title:p,main_description:q,main_keywords:r,main_image:a},app:{logo_image:s,logo_image_width:t,logo_image_height:u,logo_text:a,image_width_full:v,image_width_min:w,recaptcha_key:x,yandex_search:y,ya_context:e,banner_1:a,banner_2:a,banner_3:a,banner_4:a,banner_5:a,banner_6:a,banner_7:a,banner_8:a,banner_9:a,banner_10:a,email:z,footer_before:a,footer:a,dark_theme:e,strategy:{image_alt_words:k,item_slide_header:A,item_images:B,item_images_tag:i,item_words_h3:d,item_words_tag:i,item_words_1:l,routing:C,item_slide_skipping:D,item_download_timeout:E,item_slider_width:F,item_show_pdf:d,item_show_contents:d,item_show_filename:d},colors:{header_text:m,header_bg:j,accent:j}},social:G,token:a}}}}("",0,"image\u002Fpng",true,false,"any","maskable","\u003Cp\u003EBusiness Workflow\u003Cbr\u003E\u003Cp\u003E1\u003Cbr\u003E\u003Cp\u003EPrepareMe\u003Cbr\u003E\u003Cp\u003E2\u003Cbr\u003E\u003Cp\u003ETellMe\u003Cbr\u003E\u003Cp\u003E3\u003Cbr\u003E\u003Cp\u003EShowMe\u003Cbr\u003E\u003Cp\u003E4\u003Cbr\u003E\u003Cp\u003ELetMe\u003Cbr\u003E\u003Cp\u003E5\u003Cbr\u003E\u003Cp\u003EHelpMe\u003Cbr\u003E","h2","#d53032",10,11,"#ffffff","Business Workflow","Учебные презентации","Презентации в PowerPoint на разные темы","Презентации, проекты, доклады в PowerPoint на разные темы для учебы","Презентация, на тему, урок, класс, PowerPoint, скачати презентацію, фон, шаблон, доклад, проект.","images\u002Fdata\u002Flogo.png",185,40,720,480,"6LeioWIpAAAAAGqMN4KqMVIkekcMW7fBKHjXCd-a","2503267","[e-mail]","div","images_before","category","both",88,800,"\u003Cscript src=\"\u002F\u002Fyastatic.net\u002Fes5-shims\u002F0.0.2\u002Fes5-shims.min.js\"\u003E\u003C\u002Fscript\u003E\r\n\u003Cscript src=\"\u002F\u002Fyastatic.net\u002Fshare2\u002Fshare.js\"\u003E\u003C\u002Fscript\u003E\r\n\u003Cdiv class=\"ya-share2\" data-services=\"collections,gplus,vkontakte,facebook,odnoklassniki,gplus,twitter,moimir\" data-counter=\"\"\u003E\u003C\u002Fdiv\u003E",1,"Информатика",129,"Mypreza","ru","64x64","120x120","144x144","152x152","192x192","384x384","512x512")) : SWC_CONTAINER
Container Initialization : SWC_CREATE_CONTAINER
Contd.

Macros used during SAP Object Programming contd.
Writing a Field value :
SWC_SET_ELEMENT
Reading a Field value :
SWC_GET_ELEMENT
Writing a Multi Line field value:
SWC_SET_TABLE
Reading a Multi Line field Value:
SWC_GET_TABLE

DELEGATION

Delegation

Delegation
If you create a subtype of an object type, you can choose to delegate the superior type to the subtype. Delegation means that wherever the super type is referenced throughout workflow, the subtype will actually be used instead.
Delegation lets you use all the existing tasks and workflows based on the SAP object type as if they were using your own subtype.
Customers use their own object extensions with the tasks, events, etc. supplied by SAP
Without having to redefine existing tasks, you can use standard objects with customer extensions

EVENT

Events
Events are part of business object, are triggered for changes in the state of the object, which can cause other processes to begin.
Used for Triggering the Workflow
Necessary information needs to be entered on “Triggering Events” tab of the Workflow Builder.
Workflow Engine will automatically generate the binding. You can change it afterwards.
Events can also be defined in Classes. Their behavior is similar to the events declared in Objects.

Event Creators & Receivers

Event Creation and Triggering
Define Object in Business Object Builder
Trigger Event:
Implicitly via generic tools, for example change documents, status management, message control etc
Explicitly via function module
SWE_CREATE_EVENT

Event Triggering: Status Change

Event Triggering: Message control
Create a separate output type and declare 9 (workflow event) as transmission medium
Create a condition table
Create a access sequence
Assign the access sequence to the defined output type for a workflow event
Define condition records and declare the event
Assign the output type to a procedure

Event Triggering: Change Documents

Event Triggering: ABAP Code
Fill event container with event parameters
Compose object key for triggering object
Call SWE_EVENT_CREATE
FM Call error handling
Trigger event with explicit commit work

Business Workplace

Worklist as Interface for End User
The Business Workplace is part of the SAP Business Workflow runtime environment. The employees responsible receive the documents and work items for processing in the Business Workplace. Once a task (= a work item) has been executed and completed, the process can be continued.
The worklist contains all the work items (all the activities to be processed) assigned to this user. The Business Workplace is therefore the most important interface for an employee in their day-to-day work.

Business Workplace in SAP R/3
The Business Workplace has three screen areas:
Overview tree
Worklist
Work item preview

Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe

Demo: Notification of Absence

Business Workflow
1
PrepareMe
2
TellMe
3
ShowMe
4
LetMe
5
HelpMe

MONITORING & ANALYSIS

Monitoring & Analysis
Reporting
Work Item Monitoring
Work Item Analysis
Work load Analysis
Workflow Diagnostic Tool

Reporting
Reporting on Workflow Progress
Work Items by Processing Duration
Work Items with Monitored Deadlines
Work Items per Task
Reporting on Agent Behavior

Reporting on Workflow Progress
Transaction code: SWI1
This report shows all the work items of the particular task in a particular time period.
This report is also used for monitoring the Workitem

Reporting on Workflow Progress
Workflows for Object
Transaction code: SWI6.
This report shows all workflow instances linked to a particular object instance.
Example: Particular Purchase Order

Reporting on Workflow Progress
Workflows for Object type
Transaction code SWI14
This report shows all the work items and workflow instances for all object instances of a business object type.
Example: Workflows related to all Purchase Orders

Work Items by Processing Duration
Transaction code: SWI2_DURA
This report gives list of work items based on their processing duration for specified type or for a specified tasks.
This report is also used to analyze a Work item.

Work Items with Monitored Deadlines
Transaction Code: SWI2_DEAD
This report displays work items with their deadline information, if they are set.
For each missed deadline, the current status of the work item is shown.
This report is also used to analyze a Work item.

Work Items per Task
Transaction code: SWI2_FREQ
This report shows the number of work items created in the specified period.
This report is also used to analyze a Work item.

Reporting on Agent Behavior
Transaction Code: SWI5
With the help of this report , you can monitor how quickly agent act on their work items
This report is useful for assessing workload over particular time period.
This report is useful for reporting on the type and frequency of tasks being sent to an agent.
This report is also used to analyze a Work load.

Workflow Diagnostic Tool
Transaction Code: SWUD
A primary diagnostic tool.
Analyze workflow definition.
Following are the options available:
Verify workflow customizing
Perform Workflow Customizing
Problem: Task does not start
To track down the exact cause of an error
Problem: Workflow is hanging
Choose this option when workflow starts but stops before completion, due to some error.
Test Environment
Choose this option when you want to access the complete suite of test tools from one place.
This option will also display all the components (subworkflow, tasks, business objects, delegated business objects)

Workflow Diagnosis
Section 1: The current workflow definition to be analyzed.
Section 2: The list of test options
Section 3: A list of last tem workflow definitions.

Working with the Workflow Log
At runtime, a workflow has its own work item (type F) that represents the workflow instance.
The workflow log formats all the information created during the execution of the business process
Standard view
Intended for agents and process owners who want to get an overview of the steps processed.
Technical view
Intended for developers and workflow administrator

Standard View
Workflow Chronicle (What processed when?
Workflow Agents (Who Processed what?)
Workflow Objects (What was processed?)

Workflow Chronicle
The tab page Workflow Chronicle shows a hierarchical display of all the steps in the workflow. If workflow has a subworkflow structure, the subworkflow are also displayed.

Workflow Agents
The Tab page Workflow Agents shows the agents involved in the
workflow.
Following options are displayed for each agent:
What action was carried out in what step
When this action was carried out
The objects involved

Workflow Objects
The tab page Workflow Objects lists the objects related to the workflow. This view shows what objects were created and processed.

Technical View
The technical view shows technical nodes and control structures, container elements, agent data and workflow data.

Workflow Status

Workflow Log