Customer has variations of the same business process. What is the best practise to model such situations? To define just one business process or many?
Example1:
The main business process would be Sales order management.
Sales orders could be processed differently if created manually (variation1) or by incoming interface (variation2).
Example2:
The main business process would be Sales Distribution.
Distribution process could be different if done by train or by truck.
Maybe above example makes no sence to you, but you got my point I suppose.
Actually my question derives from Solution manager's Project implementation tools and how to define business processes there. Should I define different variations as their own business processes having their own process steps or just one business process and multiple process steps ( like entering process step 'Create Sales Order manually' and 'Create Sales Order from Interface' )?
What I had in mind, was that by choosing the way of describing the variations of same business process, will I have later some impacts on BPEL processing or ARIS or elsewhere? I mean, in business process rules I anyway need to branch "if order created by Interface, do this...else do this....".
I will create a reference of this thread also in Solution manager forum, to have more readers...
Best regards,
Kimmo