Skip to Content
avatar image
Former Member

Rule based workflow for Supplier

Hi MDG Gurus,

We are implementing MDG-S on MDG 7.0 on SAP ECC 6.0 ehp6 for a client in a co-deployed scenario.

Actually I have a small confusion in designing the workflow for this:

1) Can we only use a rule-based workflow for MDG supplier workflow configuration like we use for MDG-Material ? If yes, then after the activation of BC-set "CA-MDG-APP-SUP_DE_VC_USMD110_C" can we ensure that the BRF+ decision table steps will be imported successfully or do we need to perform some other configuration?

2) But, If we use the conventional method as given in the link Set Up the Workflow - Master Data Governance for Supplier - SAP Library,

then can we achieve success in the successful configuration of the workflow OR do we need to use both the methods as given in the guide.

Please let me know which is the preferred method which we can use for configuration of supplier workflow and please provide some document having screenshots or step by step guide to configure the Supplier workflow using these 2 methods.

Thank you.

Regards,

Satyam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Sep 18, 2014 at 01:32 PM

    Hi Satyam

    • It is possible to use rule based workflow for supplier. We need to update only workflow template against preferred CR type for Suppilier  and we need to maintain all three decesion tables for rule based workflow template in customization
    • Main differance for conventional workflow template it can be spillted functional area wise ( One for General Data, Other for Company Code data and third for purchase data so it can goes to concened cross team in parallel. In rule base workflow it is also possible but  we need to activate BADI for this.One main advantage for Rule based workflow template that we can add additional revi\ewers and approvers also.For conventional workflow step are as per below
    • Sumbission of CR by Requestor
    • Workflow splitted in GD.Cc and PD if all values are maintained and also GET_AGENT table also.
    • Respective functional area specalist review/update/Approved data
    • Then Finally it goes to respective functional area approvers who approved/Reject it.

    Wheras in rule based workflow which is flexible for this we can add additional reviewer also. So it is our call to fit all business requirement and use best suitable option for thses.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Sanjay,

      You've mentioned functional areas like general, company or purchase data with possible different reviews/approvals.

      What i'm looking for is to be able to create parallel request e.g. there's pending request on change to Company Code1 data - this should not stop user from requesting change to Company Code2 or to general data.

      Would you be able to guide me how to achive this - wasn't able to find documentation.

      Regards

      Andrzej