1.

1.1

Unit Test case

Description:
459680

SCENARIO:

CASE
NR:

PAGE: 1

OF: 9

NN
DESCRIPTION:

HS/WF-SD: Credit management Workflow

DESCRIPTION
EXPECTED
RESULT:

Once the sales order has been created and if credit limit exceeds, then Sales Collector assigned to Sales Office will be
able to Approve/ Reject the Sales Order through workflow

Part of Integration
test or dependent
test
Location:

If yes
N

Test case
before

Test case
after

Remarks:

Testing in
QS1/700

TESTER:

Munish Kumar

RUN
DATE:

05.08.2013

FILENAME:

Test
Script_459680.doc

REVISION:

1.0

STATUS:

PASS

Y
GIT

SETUP DATA
TRANSACTIONAL STEPS
S

BUSINESS PROCESS STEPS

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

FIELD/VALUE

ACTION

VA01

Sales order
type: YWAO

Enter

EXPECTED RESULTS

TESTER

OK
?

Sales order will

be saved with info
of Static Credit
Limit Exceeded

Munis
h

ok

Test Case1 : For

Sales Order
Approval
1

Create the sales order

Sales
Area:NL59/1
5/20

And Workflow will

be triggered
because of sales
order credit limit
exceeded

BUSINESS PROCESS STEPS

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

FIELD/VALUE

ACTION

EXPECTED RESULTS

TESTER

OK
?

2.

Based on the workflow

design 1st notification
would be triggered to
Sales order creator

SBWP

Click on
InboxUnread
Document

Message will be
shown with info of
sales order needs
to go through
approval /rejection
request because of
credit limit
exceeded

Munis
h

ok

3.

Based on the workflow

design 2nd t notification
would be triggered to
Sales Collectors
assigned to that
particular Sales
Office
And if sales order has
been created without
sales office then
notification will go to
all the Sales Collector
which are maintained
in the table

SBWP

Click on
InboxUnread
Document

Message will be
shown with info of
sales order needs
to go through
approval /rejection
request because of
credit limit
exceeded

Munis
h

ok

Based on the workflow

design, User decision
step would be
triggered to Sales
collector to Approve
the sales order.

SBWP

Click on Inbox
Workflow Grouped
according to task
Generic decision task
.

Work item will be

triggered

Munis
h

ok

ZWHNL_DB_CRED
ITC
4.

BUSINESS PROCESS STEPS

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

EXPECTED RESULTS

TESTER

OK
?

FIELD/VALUE

ACTION

Click on Inbox
Workflow Grouped
according to task
Generic decision task

Now here sales

collector can take the
decision whether to
approve the sales
order or reject the
sales order

Munis
h

ok

5.

Now double click on

work item of sales
order to take the
decision.

6.

Sales order decription

shown by Sales
collector to check the
credit value

If user clicks on Sales

Order hyperlink, user
would be able to see
the sales order
means which
redirects to VA03.

So once user clicks Munis

Approve button one h
pop up will come to
enter the Reason of
sales order credit
limits approval.
User can write the
comments in the
comment box and
click on OK Button.
So this work item
would be
disappeared from
approvers decision
task

ok

7.

Now work item

executed by the sales
collector will now be
available in

Outbox Work
itmes executed by
me

Approved work
items will be shown

ok

SBWP

Munis
h

8.

9.

10.

11.

BUSINESS PROCESS STEPS

As per the workflow

design, once credit
limit approver
approves the work
item ,notification
would be triggered to
sales order creator
(Initiator) to inform
that sales order
Approved
Now go to sales order

To enable the
workflow history in
sales order or Higher
level Management a
Mail to be attached in
sales order
In standard SAP
transaction SU3 user
have to assigned
proper parameter

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

FIELD/VALUE

ACTION

EXPECTED RESULTS

TESTER

OK
?

SBWP{
of Sales
order
creator
s
workpla
ce }

check the Inbox

Unread documents

Message will be
shown with info of
sales order has
been approved

Munis
h

ok

VA03/V
A02

try to create the

delivery

delivery will be
created because
sales order has
been approved and
released

Munis
h

ok

Munis
h

ok

Munis
h

ok

SU3

Parameter ID SAVE
=
SD_SWU_AC
TIVE and
Parameter
Value = X

user can able to

see the attached
documents in sales
order which is
visible as a history
and approver
comments in
attachments.

12.

BUSINESS PROCESS STEPS

GOTO SALES ORDER

PRO
CED
URE
id

TRANSAC
TION

VA03

INPUT

BUTTON/

FIELD/VALUE

ACTION

Click on the Services

of object button
Attchements list

Click on the
approval message

13.

GOTO SALES ORDER

Test Case2 : For

Sales Order
Rejection

VA03

Click on the Services

of object button
click on workflow
Workflow overview

EXPECTED RESULTS

TESTER

OK
?

Attachment list of
reason of approval
will be shown

Munis
h

ok

Munis
h

ok

The comments
given by Sales
collector during
approval of the
sales order can be
seen here
Sales order creator
would be able to
see the status of
the workflow and
also attachments if
sales collector has
attached while
approving or
rejecting the credit
limit at Information
objects addressed
so far.

14.

BUSINESS PROCESS STEPS

Create the sales order

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

FIELD/VALUE

ACTION

VA01

Sales order
type: YWAO

Enter

Sales
Area:NL59/1
5/20

EXPECTED RESULTS

TESTER

OK
?

Sales order will

be saved with info
of Static Credit
Limit Exceeded

Munis
h

ok

And Workflow will

be triggered
because of sales
order credit limit
exceeded

15

Based on the workflow

design 1st notification
would be triggered to
Sales order creator

SBWP

Click on
InboxUnread
Document

Message will be
shown with info of
sales order needs
to go through
approval /rejection
request because of
credit limit
exceeded

Munis
h

ok

16

Based on the workflow

design 2nd t notification
would be triggered to
Sales Collectors
assigned to that
particular Sales
Office
And if sales order has
been created without
sales office then
notification will go to
all the Sales Collector
which are maintained
in the table

SBWP

Click on
InboxUnread
Document

Message will be
shown with info of
sales order needs
to go through
approval /rejection
request because of
credit limit
exceeded

Munis
h

ok

ZWHNL_DB_CRED
ITC

BUSINESS PROCESS STEPS

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

FIELD/VALUE

ACTION

EXPECTED RESULTS

TESTER

OK
?

17

Based on the workflow

design, User decision
step would be
triggered to Sales
collector to Reject the
sales order credit
limit.

SBWP

Click on Inbox
Workflow Grouped
according to task
Generic decision
task.

Work item will be

triggered

Munis
h

ok

18.

Now double click on

work item of sales
order to take the
decision.

SBWP

Click on Inbox
Workflow Grouped
according to task
Generic decision task

Now here sales

collector can take the
decision whether to
approve the sales
order or reject the
sales order

Munis
h

ok

19.

Sales order decription

shown by Sales
collector to check the
credit value

If user clicks on Sales

Order hyperlink, user
would be able to see
the sales order
means which
redirects to VA03.

So once user clicks

Reject button one
pop up will come to
enter the Reason of
sales order credit
limits approval.
User can write the
comments in the
comment box and
click on OK Button.
So this work item
would be
disappeared from
Rejecters decision
task

Munis
h

ok

20

Now work item

executed by the sales
collector will now be
available in

Outbox Work
items executed by
me

Rejected work
items will be shown

Munis
h

ok

21

22

BUSINESS PROCESS STEPS

As per the workflow

design, once credit
limit approver rejects
the work item
notification would be
triggered to sales
order creator
(Initiator) to inform
that sales order has
been Rejected
Now go to sales order

PRO
CED
URE
id

TRANSAC
TION

INPUT

BUTTON/

FIELD/VALUE

ACTION

EXPECTED RESULTS

TESTER

OK
?

SBWP{
of Sales
order
creator
s
workpla
ce }

check the Inbox

Unread documents

Message will be
shown with info of
Credit limit for the
sales order has
been rejected

Munis
h

ok

VA03/V
A02

try to create the

delivery

delivery will not be

created because
sales order has
been rejected by
Sales Collector and

Munis
h

ok

Munis
h

ok

Reason of rejection
Y3 has been set in
the Reason of
Rejection tab of the
sales order
23

GOTO SALES ORDER

VA03

Click on the Services

of object button
Attchements list
Click on the Rejection
message

Attachment list of
Reason of Rejection
will be shown

The comments
given by Sales
collector during
Rejection of the
sales order can be
seen here

24

BUSINESS PROCESS STEPS

GOTO SALES ORDER

PRO
CED
URE
id

TRANSAC
TION

VA03

INPUT

BUTTON/

FIELD/VALUE

ACTION

Click on the Services

of object button
click on workflow
Workflow overview

EXPECTED RESULTS

TESTER

OK
?

Sales order creator

would be able to
see the status of
the workflow and
also attachments if
sales collector has
attached while
rejecting the Sales
order at
Information objects
addressed so far.

Munis
h

ok

System - QS1/700: Screen shot of step by step process is shown in the below attachment

Conclusion: