You are on page 1of 9

1.

Unit Test case


1.1 Description:
SCENARIO: 459680 CASE PAGE: 1 OF: 9
NR:
NN
DESCRIPTION: HS/WF-SD: Credit management Workflow
DESCRIPTION Once the sales order has been created and if credit limit exceeds, then Sales Collector assigned to Sales Office will be
EXPECTED
RESULT:
able to Approve/ Reject the Sales Order through workflow
Remarks: Testing in REVISION: 1.0
Part of Integration If yes Test case Test case TESTER: Munish Kumar
test or dependent before after QS1/700
N
test
Y

Location: GIT RUN 05.08.2013 FILENAME: Test STATUS: PASS


DATE: Script_459680.doc

SETUP DATA

TRANSACTIONAL STEPS
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

Test Case1 : For


Sales Order
Approval
1 Create the sales order VA01 Sales order Enter Sales order will Munis ok
type: YWAO be saved with info h
of Static Credit
Limit Exceeded
Sales
And Workflow will
Area:NL59/1
be triggered
5/20
because of sales
order credit limit
exceeded
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

2. Based on the workflow SBWP Click on Message will be Munis ok


design 1st notification InboxUnread shown with info of h
would be triggered to Document sales order needs
Sales order creator to go through
approval /rejection
request because of
credit limit
exceeded
3. Based on the workflow SBWP Click on Message will be Munis ok
design 2nd t notification InboxUnread shown with info of h
would be triggered to Document sales order needs
Sales Collectors to go through
assigned to that approval /rejection
particular Sales request because of
Office credit limit
And if sales order has exceeded
been created without
sales office then
notification will go to
all the Sales Collector
which are maintained
in the table
ZWHNL_DB_CRED
ITC
4. Based on the workflow SBWP Click on Inbox Work item will be Munis ok
design, User decision Workflow Grouped triggered h
step would be according to task
triggered to Sales Generic decision task
collector to Approve .
the sales order.
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

5. Now double click on SBWP Click on Inbox Now here sales Munis ok
work item of sales Workflow Grouped collector can take the h
order to take the according to task decision whether to
decision. Generic decision task approve the sales
order or reject the
sales order
6. Sales order decription If user clicks on Sales So once user clicks Munis ok
shown by Sales Order hyperlink, user Approve button one h
collector to check the would be able to see pop up will come to
credit value the sales order enter the Reason of
means which sales order credit
redirects to VA03. 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

7. Now work item Outbox Work itmes Approved work Munis ok


executed by the sales executed by me items will be shown h
collector will now be
available in
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

8. As per the workflow SBWP{ Message will be Munis ok


check the Inbox
design, once credit of Sales shown with info of h
Unread documents
limit approver order sales order has
approves the work creator been approved
item ,notification s
would be triggered to workpla
sales order creator ce }
(Initiator) to inform
that sales order
Approved
9. VA03/V try to create the delivery will be Munis ok
Now go to sales order A02 delivery created because h
sales order has
been approved and
released
10. To enable the Munis ok
workflow history in h
sales order or Higher
level Management a
Mail to be attached in
sales order
11. In standard SAP SU3 Parameter ID SAVE Munis ok
user can able to
transaction SU3 user = h
see the attached
have to assigned SD_SWU_AC
proper parameter documents in sales
TIVE and
order which is
Parameter
visible as a history
Value = X
and approver
comments in
attachments.
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

12. GOTO SALES ORDER VA03 Click on the Services Attachment list of Munis ok
of object button reason of approval h
Attchements list will be shown

Click on the
approval message The comments
given by Sales
collector during
approval of the
sales order can be
seen here
13. GOTO SALES ORDER VA03 Click on the Services Sales order creator Munis ok
of object button would be able to h
click on workflow see the status of
Workflow overview the workflow and
also attachments if
sales collector has
attached while
approving or
rejecting the credit
limit at Information
objects addressed
so far.
Test Case2 : For
Sales Order
Rejection
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

14. Create the sales order VA01 Sales order Enter Sales order will Munis ok
type: YWAO be saved with info h
of Static Credit
Limit Exceeded
Sales
And Workflow will
Area:NL59/1
be triggered
5/20
because of sales
order credit limit
exceeded
15 Based on the workflow SBWP Click on Message will be Munis ok
design 1st notification InboxUnread shown with info of h
would be triggered to Document sales order needs
Sales order creator to go through
approval /rejection
request because of
credit limit
exceeded
16 Based on the workflow SBWP Click on Message will be Munis ok
design 2nd t notification InboxUnread shown with info of h
would be triggered to Document sales order needs
Sales Collectors to go through
assigned to that approval /rejection
particular Sales request because of
Office credit limit
And if sales order has exceeded
been created without
sales office then
notification will go to
all the Sales Collector
which are maintained
in the table
ZWHNL_DB_CRED
ITC
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

17 Based on the workflow SBWP Click on Inbox Work item will be Munis ok
design, User decision Workflow Grouped triggered h
step would be according to task
triggered to Sales Generic decision
collector to Reject the task.
sales order credit
limit.

18. Now double click on SBWP Click on Inbox Now here sales Munis ok
work item of sales Workflow Grouped collector can take the h
order to take the according to task decision whether to
decision. Generic decision task approve the sales
order or reject the
sales order
19. Sales order decription If user clicks on Sales So once user clicks Munis ok
shown by Sales Order hyperlink, user Reject button one h
collector to check the would be able to see pop up will come to
credit value the sales order enter the Reason of
means which sales order credit
redirects to VA03. 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

20 Now work item Outbox Work items Rejected work Munis ok


executed by the sales executed by me items will be shown h
collector will now be
available in
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

21 As per the workflow SBWP{ Message will be Munis ok


check the Inbox
design, once credit of Sales shown with info of h
Unread documents
limit approver rejects order Credit limit for the
the work item creator sales order has
notification would be s been rejected
triggered to sales workpla
order creator ce }
(Initiator) to inform
that sales order has
been Rejected
22 VA03/V try to create the delivery will not be Munis ok
Now go to sales order A02 delivery created because h
sales order has
been rejected by
Sales Collector and
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 Attachment list of Munis ok
of object button Reason of Rejection h
Attchements list will be shown

Click on the Rejection


message
The comments
given by Sales
collector during
Rejection of the
sales order can be
seen here
S BUSINESS PROCESS STEPS PRO TRANSAC INPUT BUTTON/ EXPECTED RESULTS TESTER OK
CED TION ?
FIELD/VALUE ACTION
URE
id

24 GOTO SALES ORDER VA03 Click on the Services Sales order creator Munis ok
of object button would be able to h
click on workflow see the status of
Workflow overview the workflow and
also attachments if
sales collector has
attached while
rejecting the Sales
order at
Information objects
addressed so far.

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

Conclusion:

You might also like