Skip to Content
author's profile photo Former Member
Former Member

Workflow and branching

Hi Experts!

I am creating a workflow for Material creation scenario.I am not using LDAP and all user and roles are defined in SAP MDM.

I have 10 plants and have 2 level approver for 6 material types.

That means there are 6 material types with differen approvers and each in turn are different for 10 plants.

So I want to know which is a better way,

1.Maintaining 10 workflow for each plan and then branching for various types.

2.Creating 1 workflow which determines which plant and call from that Workflow other worflows.

If you have any other ideas pls share.

Thanks in advance!



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 22, 2010 at 12:25 PM

    Hello Ravz,

    How you are maintaining different plants at material level?

    Is it using tuple or using qualified lookup?

    If yes then how will you restrict user's from modifying or approving data of other user's plant?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks for your input!

      Yes you are quiet right,it seems very unscalable solution at MDM.

      What I can do is based on Locationdata.record and only one Display field Plant i can break into various branches.

      Then each branch would call individual users from that plant.

      Issue here is if one user puts request for creation of record,how do i ensure only that user gets notification on completion?

      This is a challenge as for one Plant under one Material type there are 3 roles and each roles will have 3-4 users.

      Please guide.

  • author's profile photo Former Member
    Former Member
    Posted on Oct 20, 2010 at 12:19 PM

    Hello Ravz

    Somebody should to launch your WF.


    If that somebody has limitation for records visability.Hi(she) can launch WF for specified records(or plants) depend of limitation rules.

    2) branch working into WF only (you can not set rule for WF launch depends of materials or plants)

    3) i suggest you to split WF because that is better for development, but it is not good for transport from one environment to another and for WF management

    business process in that case will be:

    main WF ->WF depend of materials ->WF depend of plants

    main WF ->WF depend of plants ->WF depend of materials


    Kanstantsin Chernichenka

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.