Customization Technical Design for

Workflow
Contents
1. OVERVIEW..................................................................................................... 2
2. TECHNICAL FLOW:..........................................................................................3
3. WORK FLOW.................................................................................................. 4
3.1 SAP BUSINESS OBJECTS...................................................................................................... 4
3.2 BUSINESS WORKFLOW DETAILS............................................................................................. 4
3.2.1 Workflow Template.................................................................................................. 4
3.2.2 Trigger Mechanism.................................................................................................. 4
3.2.3 Methods.................................................................................................................. 5
3.2.4 Tasks....................................................................................................................... 5
3.2.5 Workflow Steps....................................................................................................... 6
3.3 AGENT ASSIGNMENT DETAILS............................................................................................... 7
3.3.1 Rule......................................................................................................................... 7

1. Overview

A workflow is a sequential flow of tasks and activities in a business process that is

supported by SAP ECC.
Workflow for Purchase Requisition (PR) approval is to support approving Purchase
Requisitions to ensure the commitment of financial resources is appropriate.
Conversion of approved Purchase Requisitions to Purchase Orders will be automated
whenever possible.
Approval Process
Each purchase requisition workflow process to go through an approval process:
All Purchase requisitions on or above the prescribed value will need to be approved.
1) First Report to Approver. If the Report to Approver does not have the
appropriate spend limit.
2) Next level of approver will be determined based on Purchase Requisition
value at the header level.
3) If approval is necessary, the Purchase Requisition will need to route to the
Financial Manager.

2. Technical flow:

Step1: user submits Purchase Requisition.

Business object: BUS2105

Agent: Agent will be determined using rule .Rule is to be created using method
MMGETAPPROVERS.
Method: MMGETAPPROVERS

Step2. 1st Level Financial Approver Approve/Reject

Agent: 1st Level Financial Approver fetched from HR Mini Master Table
Business object: BUS2105
Method: MMGETAPPROVERS
Decision Step.
1st Level Financial Approver approves or rejects .if it is rejected , a notification mail
is sent to
Requestor. If it approves then go to step-3. (If Financial Approver has an active
delegate/substitute approver in effect in the SAP Portal, re-assign Financial Approval
role to active substitute approver.)

Step3. Does 2nd Level Financial Approver approval required.

Agent: 2nd Level Financial Approver fetched from HR Mini Master Table
Business object: BUS2105
Method: MMGETAPPROVERS

Decision Step
If 1st level financial approver is not authorized to approve invoice based upon dollar
value amount of invoice, 2nd level financial approver is fetched from HR mini master

and custom table. (If Financial Approver has an active delegate/substitute approver
in effect in the SAP Portal, re-assign Financial Approval role to active substitute
approver.)

Step4. If the outcome of step2/step-3 is rejected, a notification should go to

workflow initiator intimating the Non PO line item has been rejected.

Step5. If the outcome of step-4 is approved, Release flag will be set and parked
document will be posted. A notification mail should go to workflow initiator
intimating the Non PO line item has been approved.

3. Work Flow
3.1 SAP Business Objects

Object Types / Class

ZBUS2105

Attributes
Business Object

Methods
Subtype of BUS2105

Events

3.2 Business Workflow Details

3.2.1 Workflow Template

Workflow Name
Workflow Description
Workflow Container Elements
Name
Source company code
DocumentNo
FlagComplet
FiscalYear
FlagReleased
UserRelease
UserChange
UserComplete
UserName
LevelCounter

3.2.2 Trigger Mechanism

Will be mentioned while code building.

Purchase requisition workflow
Description
Source company code
Accounting document number
Completion Flag
FiscalYear
Release flag
User (Release)
Change By
Created By
User Name
Amount Release Approval Levels

Data Type
VBKPF-AUSBK
VBKPF-BELNR
VBKPF-XPREG
VBKPF-GJAHR
VBKPF-XFRGE
VBKPF-USREL
VBKPF-USUPD
VBKPF-USCMP
VBKPF-USNAM
VBKPF-SUBN1_LVL

Business Object Type / Class

Name
BUS2105

Event

Workflow Template

CREATED

BUS2105

3.2.3 Methods
Method Name
Method Description
Exception
Logic
Interface
Parameter

MMGETAPPROVERS

provide Non PO creator functionality to choose Approver

Data Type
RM06B-FRGAB

Import

Export

EX_TECHAPPROVER

SWDSSTEPSDEADL_ROLE

Non PO Invoice

RE_BELNR

ItemOf Non PO
Invoice

RBLGP

EX_DOAAPPROVER

SWDSSTEPSDEADL_ROLE

EX_Comments

SY-LISEl

Status

RV86E-FLAg

ReleaseStatus

RBKP-FRGKZ

IM_ReleaseCode

3.2.4 Tasks

Task Name
Task Abbreviation
Task Description
Task Type
Task Update Type
Task Method

TS00008142
Post the parked document
Post the parked document
Dialog
Synchronous
RELEASE

Mandatory

Task Container Elements

Name
_Attach_Objects
_Wi_Actual_Agent
_Rule_Result

Task Name
Task Abbreviation
Task Description
Task Type
Task Update Type
Task Method
Task Container Elements
Name
_Wf_Initiator
Express
TypeId
AddressStrings

Data Type
BOR OBJECT(SOFM)
WFSYST-AGENT
BOR OBJECT(AAGENT)

Import / Export
Import /Export
Export
Import/Export

Value

TS20000139
Enter and Send short messages
Enter and Send short messages
Dialog
Synchronous
COMPOSE
Data Type
WFSYST-INITIATOR
SOS04- L_SEX
SOS04-L_ART
SOXNA-FULLNAME

Import / Export
Import
Import
Import
Import

Value
&_WF_INITIATOR&
&EXPRESS&
&TYPEID&
&ADDRESSSTRINGS&

3.2.5 Workflow Steps

Step Name
Will be mentioned while code building.
Step Description
Document sent to approval
Task Name
TS20000139
Step Type
Send Mail
Step Logic
Send mail to approver
Agent Assignment
Will be done through rule created.
Deadline Monitoring
If applicable
Binding
Workflow Container Elements
Flow

Task Container Elements

Step Name
If applicable.
Step Description
Approval/Rejection from 1st Level
Task Name
TS00008142
Step Type
User Decision
Step Logic
Agent Assignment
Will be done through rule created.
Deadline Monitoring
If applicable
Binding
Workflow Container Elements
Flow

Task Container Elements

Step Name
Step Description
Approval/Rejection from 2nd Level Approval
Task Name
TS00008142
Step Type
User Decision
Step Logic
Agent Assignment
Will be done through rule created.
Deadline Monitoring
If any
Binding
Workflow Container Elements
Flowlogic

Task Container Elements

3.3 Agent Assignment Details

Agent is to be determined through rule.

3.3.1 Rule

Rule Name
Rule Description
Abbreviation
Logic

To get agent name.

To get agent name.
HR Mini master and custom table used to fetch agent.

Functional Module
Container
Workflow Container Elements
Interface of Functional Module
Parameter
Data Type

Flowlogic

Import

Rule Container Elements

Export

Mandatory