Skip to Content
Technical Articles
Author's profile photo Steffen Ulmer
Steffen Ulmer
February 14, 2017 Less than a 1 minute read

New “How To Guide”: Dynamic Workflow Processing in MDG-S

Hi,
in the Wiki Documentation Center we have recently released a new How To Guide with the name “How to MDGS/MDGC/MDGBP: Dynamic Workflow Processing based on changes to bank details”.
You can find the document here:

SAP How-To Guide MDGS/MDGC/MDGBP: Dynamic Workflow Processing based on changes to bank details
I wrote that guide based on a real request from customer side and I hope you will find it valuable. Looking forward for your feedback.

Best Regards
Steffen

 

Link to Documentation center:

https://wiki.scn.sap.com/wiki/display/SAPMDM/Documentation%3A+Customer%2C+Supplier%2C+and+Business+Partner+Data

Link to How To Guide: http://www.sap.com/documents/2017/01/b42437c9-a47c-0010-82c7-eda71af511fa.html

Assigned Tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Rama Veeturi
      Rama Veeturi

      Hello Steffern,

       

      Thanks for sharing SAP How-To Guide MDGS/MDGC/MDGBP: Dynamic Workflow Processing based on changes to bank details guide. We have same exact requirement to route workflow to different set of users when bank information is changed. I have started following your step-by-step guide and is stuck at step 8 where we need to upload BRF+ decision table.

       

      In the document it says upload Import the BRF+ examples, Now you can import the example. But excel files are missing. Can you please share the BRF+ example 3 decision table excels so that I can upload them and build on them, by changing position details etc.

       

      Also, can you please provide more details on below statements? For us to route the workflow I believe code until this point is sufficient and below method is needed if you want to read any additional data as needed. Is it correct?

       

      READ_DATA: This method can be implemented by you to read all entities in staging typically you use readmode “ gc_readmode_no_act” to get only inactive/staging data Please use the MDG API to retrieve this data

       

      Thanks,

      Rama

      Author's profile photo Steffen Ulmer
      Steffen Ulmer
      Blog Post Author

      Hi,

      Excel files:

        1. https://sap-my.sharepoint.com/:x:/p/steffen_ulmer/ETtKAGrdiRtGvuEHBX4s_YwBSB0kyF1gnn_3x_0FLdVKBw?e=zJeJb2
        2. https://sap-my.sharepoint.com/:x:/p/steffen_ulmer/EdFEi2Ju7sZDouELsPSohpwBSIpCOxlB_X3IvOowBeJpXQ?e=QxiNS
        3. https://sap-my.sharepoint.com/:x:/p/steffen_ulmer/EXFMQ-k9__1MqsLUhg1KlPAB4cG31vfNNi_COx3-HGt5mA?e=GaheLy

      The files will maybe not work in your system because of ECC version or language settings or table settings. It should be rather simple to configure the tables directly in your system.

      Code.

      Yes. In the ABAP code you can read what ever you need. I think you should go through the MDG API Guide for more info in case my code doesnt fit to yours.

      Best regards

      Steffen

      Author's profile photo Sridhar Amruth
      Sridhar Amruth

      Hi Steffen,

       

      Can you please share the Excel files again.as those are expired.

      Thanks in Adv.

      BR,

      Sridhar

      Author's profile photo Sven Hertig
      Sven Hertig

      Hi Steffen,

      thanks a lot for your detailed documentation. I'll tried to implement it for CR-types "Supplier create" and "Supplier change". Because all my changes I'll do in the staging area (usmd_model) no matter if I add a new bank account or change an existing bank account.

      Can you provide me the READ_DATA coding? Because of my following issue:

      If I change the address and bank acount attribute, the READ_DATA method do not retrieve the bank account data. But the bank account data is the trigger for the approval flow. (you know ;-)). If I change only the bank account data all is working fine.

      Do you have a hint for me?

      Thanks and

      Best regards,

      Sven

      PS: We solved our issue.