Business Process Testing

[Former Member]

Hello everyone I have a general question about business process testing in Sales and Distribution

we have these business process definition documents and we have some functional requirements for thsoe documents and I wanted to know if someone has done this before where you created scenarios from those requirements and if yes I want to know how did one do it? I just need to understand the concept.

Thanks

Edited by: inzane on Aug 10, 2009 4:16 PM

[Former Member · Accepted solution]

Hello,

How i've handled in the past is to start by creating a list of business scenarios (including key things to be touched - like business areas, company codes, doc types, interfaces, etc. Then build test cases using elements from the list -- pulling in multiple items from the list where it make sense). Not every test would necessarily include all the same elements. Each test case would be assigned a number or code -- and that wold be tracked on the basic business scenario list. Also found it valuable to include business users in development of theese test docs wherever possible.

Not sure if this is what you're looking for, but hope it helps.

[Former Member · Accepted solution]

Jacqueline---

I thank you for our time and effort in answering my question.

however what i am bascially doing is I have a business process lets say (Create Purchase Orders)

I have 32 Functional requirements for it and the objective here is to create testing scenarios from these 32 requirements

and make sure that these requirements cover the purposed business process which is Create purchase orders.

You are absolutely right on the money of what you have stated in your post above but can you please shed some light on my current situation or in your experience how would you go about doing what I am currently tasked to do..

Thanks in advance-

[Former Member · Accepted solution]

Hello,

Business Process Testing is a big exercise, as you are aware of the same. You have mentioned that there are 32 requirements, all these requirement will have to be tested, so that element of error reduces. While you are testing and preparing test script, it is not important that all test will give desired result in first testing. It is possible that some configuration changes are required or some master data is not maintained / not maintaintained accuratelely. Hence the errors requires to be pluged and retested.

Apart from that, the testing are at different level, such as Unit Testing - which will test only the functionality of particular process say creating PO. All errors may not come into knowledge at this point. Integration testing - which will test the entire process along with inegration within SAP and with interfaces. Here there are chances that additional problem area are identified and required to be fixed.

Testing will require good amount of efforts.

Regards,

Rajesh Banka

[Former Member · Accepted solution]

Hello again,

In your place I'd take the same approach -- but of course would drive around purchasing. One thing you might consider is starting by building a fairly basic test case (i.e. not include lots of variables)...then create additional test cases from the basic one adding in other requirements to hit. I'd try to create test cases combining as many of the requirements as possible -- trying to avoid having 32 separate tests...altough you'll likely have several.

You can ensure having covered the scenarios by numbering/coding each test case -- and recording/tracking that on the basic test list.

Good luck.

[Former Member · Accepted solution]

Rajesh and Jacquline I can't appreciate your answers enough.

I guess I am doing the same thing as you have mentioned but I either put very little information for the scenario or too much I was unable to find a close enough match.

Have either of you guys done this before? where you had to actually perform validation? on a business process and then create testing scenarios?

if either of you can share your ideas across or even an easy or i should say lame way of how to do this?

I would appreciate it.

[Former Member · Accepted solution]

The process followed by me for testing Business Scenario for Order to Cash Cycle is demonstrated below"

Initial Testing will be as under:

1. Create Stock artificially (in test server / sand box only)

2. Create Sales Order

--> Here the common expected error would be as under:

a. Sales Order Type not assigned to Sales area

b. Pricing Procedure assignment not done.

c. Pricing Condition record not maintained

d. Material not maintained or extended to relevant combination

On successful creation of Sales Order, next step would be to create Delivery.

3. Create Delivery and PGI

I will test this scenario in multiple manner

a. Create Delivery from Sales Order

b. Create Delivery through Transaction Code VL01N

c. Create Delivery through Transaction Code VL10C

--> Here the common expected error is copy control setting not maintained, defalult Delivery type not maintained accurately in sales Order Type, etc.

On successful creation creation of Delivery, assuing Picking is done appropriately, doing PGI.

Here the challenge is the Account determination setting reguires to be completed, without which in most cases, it will not allow to do PGI.

4. Create Billing

I will test this scenario in multiple manner

a. Create Billing through VF01

b. Create Billing through Transaction Code VF04

Here the challenge is the Account determination may not be complete and Billing Document is saved without creating accounting document.

In Integration Testing:

1. Assure that material stock is availble in unrestricted stock through MM/PP.

2. Creating Sales Order smoothly

3. Creating Delivery, picking and PGI smmothly.

4. Create Billing smoothly with creation of accurate accounting document

Troubleshooting the errors encountered.

Here the objective is that the process should execute seamlessly.

similar exercise is done for other processes like Stock Transfer, Third Party & so on........

Regards,

Rajesh Banka

[Former Member]

Thank you everyone for your help