MDG Implementation with Standard Data Model

[titu4mdg]

Hi Experts,

This is my second MDG project for Material and Supplier master data. Our Customer does not want to customize anything(no custom fields in the Data Model and on UI), they just want to leverage all the standard fields of the standard data model with their custom rule-based workflow and business rules.

My questions are as follows, Would be a great help if I get answers to these Qs. I am a little confused as my last MDG implementation was project with a lot of custom fields and custom Entities that were implemented in the Data Model, not sure about how much customizations are involved in this project.

1) Do we not have to do any Data Modeling here in this project as we are dealing with only standard fields?

2) If the answer of Q 1) is NO, how would we create the Transport for the Data Model from Dev environment to be transported to QA environment?

3) For Change Request implementation, can we use the standard Change Request Types(MDG-M and MDG-BP) in our implementation or we should create custom ones to develop the custom rule-based workflow?

4) Can you also please tell me what all custom objects we can of developing in this type of MDG implementation where our Customer do not want anything apart from custom rule-based workflow and business rules development(BRFplus or BAdI)? could there be any other RICEFs anywhere to be considered?

5) Since, in the replication also, there is no custom fields to be replicated, can we still use the standard IDOc Type and Message Type.,,,or we can even use SOA Services?

6) For HANA Search, do we still have to activate the standard views...?

Would highly appreciate your reply.

Thanks, TD

[former_member213253]

Welcome and thanks for visiting SAP Community to get answers to your questions. Check out our tutorial to get started in SAP Community: https://developers.sap.com/tutorials/community-start.html By adding a picture to your profile you encourage readers to respond to your question. Learn more about your profile here: https://developers.sap.com/tutorials/community-profile.html

[former_member106 · Accepted solution]

Hello Titu,

I will try to answer all of your questions in best possible way, but from my point of view, you need to decide based on the complete customer requirements.

1) Do we not have to do any Data Modeling here in this project as we are dealing with only standard fields?

A : No, In your case, there is no need to do anything with the data modeling, apart from Activating the data model through the Business Functions. There are some basic steps explained in the

SAP Help Link, which will guide you to setup the system.

2) If the answer of Q 1) is NO, how would we create the Transport for the Data Model from Dev environment to be transported to QA environment?

A : As i explained in the previous question, these are Business Function activation, so this has to be done throughout the system landscape individually. You can take help of SAP Basis consultants to do this activity.

3) For Change Request implementation, can we use the standard Change Request Types(MDG-M and MDG-BP) in our implementation or we should create custom ones to develop the custom rule-based workflow?

A : Yes, you can use the out-of-the-box CR types for your implementation. You require additional CR types only for custom business processes (decide based on customer requirement)

4) Can you also please tell me what all custom objects we can of developing in this type of MDG implementation where our Customer do not want anything apart from custom rule-based workflow and business rules development(BRFplus or BAdI)? could there be any other RICEFs anywhere to be considered?

A : It is a very generic question, but in case of activating only standard features, there won't be a requirement of developing any RICEFs. Again, this purely based on the customer requirements, so please go through the requirement document carefully to decide.

5) Since, in the replication also, there is no custom fields to be replicated, can we still use the standard IDOc Type and Message Type.,,,or we can even use SOA Services?

A: Yes, you can again use the standard replication settings provided by SAP, but you need to create the replication model and assign systems. Please go to this link for more information on the setup.

6) For HANA Search, do we still have to activate the standard views...?

A: Yes, you still need to do some basic setup to use the HANA Search and of course, you need to create Custom Search views, if the standard views are outdated or does not match the customer requirement. Please use this link to setup the Hana Search views.

Hope i answered your questions to the best of your needs. All the best for your new project.

Regards

Senthil.

[titu4mdg · Accepted solution]

Hi Senthil, Thanks so much for taking your time to answer my questions.

Just two follow up questions:

1) I think, we should create our custom CR Types as standard CR Types have already their respective rule-based workflow assigned. Since we have custom data governance steps(customer-specific workflow process) involved in our implementation, can we still overwrite any standard BRFplus application(the rule-based workflow, which is already assigned to the Standard CR Types) with our custom one?

2) In your answer of Q#6, could you please elaborate what did you mean by Stantard Views being outdated? We are using MDG on S4 HANA hosted in HCP(Single Tenant Edition).

Thanks, Titu

[former_member106 · Accepted solution]

Hello titu4mdg

1) In SAP, there is only one rule based workflow WS60800086. This is in general assigned to most of the CR types. The BRF+ rules are then defined for each CR type individually. These are standard delivered, but can be changed by customers as per the business processes. If you decide not to change them, as being standard, then you can also create custom CR types and use the same workflow WS60800086 for this, in this case, you need to define the CR type to the business actions accordingly.

2) As an out-of-the box, SAP provides set of Search views for each business object type (screenshot below). These exists from the previous MDG versions and are not modified frequently by SAP, because, no customer will use these as it is delivered by SAP due to various reasons. For example, you need to have a very specific fields to be available in the views, which may not be covered in these standard views. More over, the irrespective of where the MDG is deployed, these views does not change. So, it is better to either copy them and modify the fields or create a new views according to the requirement.

Hope it make some sense now. Please do not hesitate to revert, in case of any questions. If you like the answer, please rate the answer as well. Thanks

Regards

Senthil.

[titu4mdg · Accepted solution]

Thanks a lot Senthil for all your answers.

Regards, Titu