MDM workflow step branch

Hi,
i have a workflow with step of branch and user must choose himself on which branch workflow realization will go later. Help me, please, to write validation/expression (or it can be done in the other way?)
Thanks in advance!

Hello,
Based on the values available to the User, design a Lookup and create a validation for each steps.
For building validation please follow the below link
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/master-data-management/_master-data-management/elearning/step-by-step%20tutorial%20on%20creating%20validations%20in%20sap%20mdm.sim
Based on this validation, you can branch the user in the respective realizations steps.
For example country, has values india, US, UK, Germany, Singapore, Australia.
Design 6+1 validation,
country = 'india'
country = 'US' and so on 
and the last one as, if country = NULL, then error message.
Then use this validation in your branch step.
Regards,
Abhishek
Edited by: Abhishek Biwal on Dec 26, 2011 2:50 PM

Similar Messages

  • MDM Workflow:branch step.

    Hi ,
    Can anyone explain the use of Branch step?
    Hw can u connect it can anyone elaborate?
    Satisfactory answers will be rewarded points
    Regards
    Nisha

    Hi,
    i give u a short Example through workflow, using this you will come to know how to use Branch Step.
    >Assign---->Stop1
    Start--->Branch
    >Stop2
    Suppose in your Main table there is a field which you want should always have some value say this field is Product ID
    So, in Main table select Validations Pane and Create a validation say validation Name Mandatory Product ID
    Here validation shud contain expression as IS_NOT_NULL(Product ID)
    Create a new field of type Text Say Status in Main table.
    Create an assignment say Approved Records in Assignment Pane Select Property Table Field = Status in assignment expression write say Approved
    During configuring workflow in Branch Step select Property Validations = Mandatory Product ID
    on selecting this two more Properties get Enabled Select Property Mandatory Product ID = Assign and Property Default = Stop2 , All the steps should be connected properly using Connector,
    For Assign Step select Property Assignment = Approved Records and this Assign step further connect to Stop1
    So using this workflow it will fill the values Approved in the field Status for all the records having Product ID and for failed records it go directly to stop2
    Hope it will Help you,
    Rewards if Useful.....
    Mandeep Saini
    Edited by: Mandeep Saini on Jun 19, 2008 7:28 AM

  • Dynamic text in MDM notify workflow step

    Hallo MDM Gurus,
    Do you know how to create a dynamic text in the MDM notify workflow step?
    I would like to insert some record informations in the text of this step.
    Any suggestion is helpful.
    Thank you.
    SB

    Try the following parameters in Subject and Description of Notify stuff....
    pelase feel free to revert to me.
    %RepositoryName%            --> The repository name.
    %TableName%                    --> The table name.
    %JobId%                             --> The job id.
    %JobName%                       --> The job name.
    %StepId%                           --> The step id.
    %StepName%                     --> The step name.
    %Records%                        --> The record id and display fields of the job records.

  • MDM workflow - syndication step

    Dear MDM experts
    I would like to ask you about help with workflow step - syndicate.
    I just make a workflow which seems to be working fine. There is only one step I do not understand why is not behaving as I expect it. That step is syndicate. I can see the status is "Received" but nothing happen. I cannot find file under syndication folder.
    Can you help me to explain why it is like that?

    Hi Rafal,
    There can be a couple of reasons for that:
    1. Syndication port should be manual.
    2. The record, which you are trying to syndicate, might not fit your map criteria. Connect to the port in syndicator and try to syndicate the same record and see if you are able to do so.
    3. At the time your WF is at syndication step, you are not connected to same port through syndicator.
    4. You do not have a descrption for syndication step in WF. (Although it may sound wierd, but it is required iin some MDM versions).
    5. Repository password saved in console/mdss.ini might not be correct.
    If everything seems fine, check the logs. This will tell you the actual problem.
    Best regards,
    Dheeraj

  • MDM workflow - dynamic approver determination

    Hallo,
    in MDM workflow, i see that in the visio workflow definition of the approval step, it is possible to set approvers. This sound to me like a static approval definition.
    Let say that according to some field value I want to determine different approvers, meaning if Product category is 1 approver is X, if Product category is 2 approver is Y, etc..
    Is this possible to achieve?
    How?
    thank you in advance,
    Regards,
    Marco

    Marco,
    I am assuming you have 3 approvers X, Y and Z. Create 3 validations for all 3 cases:
    Validation A: Category =1  => goes to approver X
    Validation B: Category =2  => goes to approver Y
    Validation C: Category =3  => goes to approver Z
    Start -> Branch (Add validation A) -> Form 2 processes (1 which is TRUE goes to Approver X and for false it is either Y or Z)
                -> (TRUE) -> Approver (Assign X)
                -> (FALSE) -> Branch (Add Validation B) -> Form 2 processes (1 which is TRUE goes to Approver Y and for false it is Z)
                -> (TRUE) -> Approver (Assign Y)
                -> (FALSE) -> Approver (Assign Z if this the default approver else add one more iteration)
    I hope this should work.

  • Workflow step - Add record to mask

    Hi,
    Is there a workflow step that can add a record to a mask? Any ideas on how we can achieve that?
    Thanks.

    TS is correct,
    this may be another solution, but a quite complex and I'm not sure that it works fine for your requirements. Besides, probabily enrichment is not in your MDM package because needs another license. In any case this solution required java customizing.
    Regards,
    Vito

  • MDM Workflow Expiry message

    Hi Experts,
    I have a scenario in which MDM workflow is active, workflow is working fine and there are absolutely no issues. The only problem is, For workflow owner, I am getting following message everyday (If workflow is not clear or executed).
    The following workflow step is overdue because it has exceeded its expiration timeout:
    Assignee:                ; MDM System
    Job:                    10565
    Job Owner:              MDM System
    Records:                1
    Start time:             04/14/2011 00:22:19 GMT
    Expiration time:        04/24/2011 00:22:19 GMT
    Workflow:               Workflow Name
    Step:                   ABC
    Description:   
    Repository:             MDM Repository
    May be some setting missing, I want to deactivale this workflow reminder. Can you please guide and help?
    Regards,
    Maddy

    not sure on why you want to take the notifications out - for the sake of receiving harmless emails
    u can direct them to the spam folder easily
    but still if u wish
    go to the workflow visio diagram -- find notify step -- and remove ur emai id from the settings.
    thanks
    -Adrivit
    This will stop ALL email notifications pertaining to THIS workflow to ur id.
    Edited by: Adrivit on May 23, 2011 1:42 PM

  • Portal check out record does not check in when MDM workflow is active

    Hi Experts,
    We are using portal as front end for the MDM material creation/update.
    when a user tries to edit a material via portal, the record is checked out in mdm and once the record update is done and submitted that particular record will be checked in. this is normal process and automatic in nature till date.
    However, we have created a simple workflow in mdm, we havent checked out records in start step of workflow.
    So it normally executes without check out /in via MDM Workflow.
    workflow triggerring action = record import, record update, record add.
    when i edit the material vai data manager WF triggers fine and all is well.
    However when i edit the material via portal, record is checked out (which is normal) and once record is submitted, the workflow in mdm is triggered successfully.
    Workflow ends with all necessary syndication's and validations and ends successfully, But after this the record still remains as checked out? ???
    ideally as mentioned above (in bold) once the user completes editing the record and submits it, the record should be checked in, but this is not happening!!!
    Please let me know why is this happening.
    Please help.
    Regards
    Eva

    Hi Eva,
    That is useful.
    Analyzing this issue I came across SAP note 1740194-Record remains in exclusive lock after workflow is completed.This was an issue observed in SAP MDM 7.1 SP08.
    It gives a workaround -
    The workaround is:
    The owner of updating has to click on the modified record in Data Manager after workflow completed. The original modified record will be unlocked.
    Ofcourse,resolution would require an upgrade.
    Thanks,
    Ravi

  • MDM Workflow - Assign

    Hi all,
    I am trying to set up a workflow that automatically triggered when I update the main table. I have created an assignment to assign a static value to one of the text fields and inserted this assignment as an assign step within the workflow. (the assignment works fine when triggered manually)
    The workflow Max Record launch is set to 1 and the Max Time Launch is set to 0h.
    When I update a main record table, the workflow gets triggered but goes into status 'Error' at the assign step. I am able to manually 'Perform' the assignment and then forward it to the next step within the workflow.
    Do you know if this is because I was still locking the record when I was updating the record? I tried declaring the Start and Stop of the workflow with Check Out and Check In, but I am still receiving the same problem.
    What is the correct way to use an assignment within an MDM workflow?
    Are check-in/outs mandatory?
    Please help. Thanks in advance.
    Foh

    Hi,
    Please share our solution with team .
    As question is marked as answered.
    Thanks,
    Shruti.

  • MDM WorkFlow external application

    HI Expect
    We want to create a Work flow process on MDM that will execute external application, or exe. So is this possible on MDM workflow. One option was to use Portal, but we need the same functionality to be used for MDM Data Manager Console users.
    Regards
    Tebogo

    Hi,
    This is not possible with MDM Workflowsr. MDM Workflows are light-weight and supports only basic functionalities which can be achieved using the steps provided to design the workflow. You need to have the custom application to achieve this requirement
    Regards,
    Jitesh Talreja

  • Workflow steps

    Hi ,
    Can someone pls tell the steps ( preferably detailed) to create a workflow in MDM .Here is the simple scenario :
    1. User A adds a record say Product name .
    2. User B approves the records and then only this record should be available in the repository .
    How do I achieve the above and what settings  i need to perform .
    I have MS Visio installed

    Hi Amit Jha,
    Kindly follow the steps the achive your scenario.
    1. Select workflow table in the Data Manager and create a new workflow.
    2. Give workflow name (Ex: Create record approval) and other details set the Trigger action to "manual".
    3. Click on the browse button in the property named Workflow. It will open the MS Visio prespective.
    4. Create a work flow as defined below
    Start -> Process -> Approve->stop
    5. Change the property of the steps Approve and Stop as follows to make the workflow meaningful.
    Approve
    Name - "Send for Approval"
    Assignee user - say "MDUser" (User who send the added record for approval) remove other users to avoid confusion.
    Stop
    Name - "Add record in the MDM"
    Assignee user - say "MD_Manager" (User who approves) remove other users.
    6. Save the workflow.
    7. Execute the add record and approve scenario as follows
    a. Login as "MDUser" in the datamanager. Add a record, right click on the record, select workflows -> Add to job->  Create record approval (Workflow name) from the context menu.
    b. select Workflow tab in the properties. Select the workflow (Status is Unlaunched) and launch the workflow using the launch option from the context menu.
    c. The status will now change to received. Using context menu select "Next Step" -> "Send for approval".
    d. Now Login as "MD_manager". Go to workflow tad in the properties. You can find a workflow job with status "received". Click on the workflow job, you can see the record(s) assigned to the workflow in the record pane.
    e. Select "Next step" -> "Add record to MDM" from the context menu of the workflo job.
    You can add one or more records to a workflow job. Also try adding some validation in the workflow steps. Refer Data manager refernce guide for more details.
    Now I am done with the process of creating and executing the workflow for your scenario. Hope this helps.
    Regards,
    Arun prabhu S

  • Trigger MDM workflow from Webdynpro Java

    Hi All,
    After updating records in MDM, I want to trigger an MDM workflow from Webdynpro Java and pass those updated records to workflow. Any inputs on how to accomplish this. Workflow has already been developed using MSVISIO by the MDM team.
    Thanks,
    Tom

    By following steps, it is possible to integrate  workflow (or any workflow designed in MDM) within portal:
    1. UWL (Universal Worklist): The UWL gives users unified and centralized way to access their work and the relevant
    information in the portal. It collects tasks and notifications from multiple provider systems. One can expose MDM
    workflow functionality on Portal using UWL.
    2. JAVA APIu2019s: MDM Java API consists of set of classes related to MDM workflows through which one can create an
    application that provide the MDM workflow functionality and expose the application as an iView in the portal.

  • SAP MDM workflow erroe while launching

    Hi Experts,
    I am using SAP MDM 7.1 (7.1.04.142).Whenever I am trying to launch a workflow I am getting this error
    One or more records have following validation failures:
    Invalid validation recordId(s) in val;idate field
    Any help please
    Thanks
    Vinay

    Hi Vinay,
    As per this SAP Note: Workflow stop at Stop Check-in.
    Are you using Check out at Start step in your workflow ?
    So I would also suggest try to launch the workflow who is Owner of the workflow. May be that user has not right to launch the workflow.
    Also check who can send next step in your Start step of MDM workflow, Owner/Launcher/Any user ?
    For testing, Create a new record in your Data Manager then Add this record to Workfow job manually by right click on this record Workflows>Add to Job>workflow name and check are you able to complete this work-flow or not?
    Regards,
    Mandeep Saini

  • SAP MDM Workflow

    Hi,
    I have written some SAP MDM Workflows.
    Now, the email is not firing.
    There is a setting to be done in .rhosts or in some particular
    where you have to specify SMTP Mail Server.
    Regards
    Kaushik Banerjee

    Hi Kaushik,
    For activating the Notification step in MDM workflows you have to make settings in the mds.ini file in the server folder location,where you have to mention the Smtp server taht you are using for sending the mails.
    Bedsides this settings you will have to crete users in MDM console with their email ids so that they can receive mails acc from the owner of the workflow.
    You will have to add the notify step in the Visio template and fill in the correct property details.
    These settings should enable your mail services for the wf users.
    The mail will be shooted in 1 sec to the desired user as the timeout default time is set to 1 sec however you can set this prameter,if the mail sending is failed due to any unknown reasons an error is loged but the sending is not redone.
    Follow the below link to get a clearer idea o the same:
    http://help.sap.com/saphelp_mdm550/helpdata/en/43/e0615f82b40a2ee10000000a11466f/frameset.htm
    http://help.sap.com/saphelp_mdm550/helpdata/en/43/8b11b4249a6fcee10000000a1553f6/content.htm
    Hope It Helped,
    Thanks & Regards
    Simona Pinto

  • 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!
    Regards,
    Ravz

    Hello Ravz,
    Your scenario is best suited for modeling outside MDM (possibly in BPM).
    Modeling this in MDM will be more complicated from implementation as well as maintenance point of view.
    Probably you will end up with lots of customizations, if you decide to model it in MDM.
    Because you cannot dynamically assign approver's in MDM workflow.
    Also you cannot access modifier (i.e. user) and its role details, anywhere in MDM (assignments, validations, and workflows);
    hence you need to keep this plant to its approver mapping somewhere else.
    Also consider the point that you cannot use checkin/checkout operations on Tuple or Qualified level.
    This will lead to dirty read, because you have to save modifications on original record before approval,
    that too you cannot revert modifications in case of rejection.
    Tuple or Qualified level change Syndication is another headache.
    Designing this scenario in MDM will become measure maintenance night-mer after go-live.
    One option of design may solve most of the above problems.
    That is: Create a dedicated main table for plants.
    Means you will have two main tables one will be analogous to MARA and another will represent MARC.
    But, this design is against the packaged Material repository provided by SAP.
    Also decision of creating multiple main table should be taken carefully, because it may be a performance hit.
    Regards,
    Shaailesh.

Maybe you are looking for