MM06 mark for deletion in MDG

[balu99]

It's Co-Deployment system.

Please clarify on below points.

1. What will be impact on MDG if user marks the material from deletion directly from S/4 through MM06?

2. Whether user should do it through MDG only? If yes, How can we give the access to them and what will be efforts from MDG end?

[tushar_007]

1. When you use MDG irrespective of co-deployment or hub, the first idea is restrict usage of transactions MM**

If your material is locked in MDG CR, anyways system will not allow to change it using MM06.

2. Yes, User should do it using MDG, it has very few efforts as we are talking about setting up some defined material status here. Based on your workflow design, the efforts should vary, but still on lesser end.

There are several ways to provide access but one of the way is based on change request reason you can restrict their access only for this activity

[RiccardoBrogi]

Hello,

Point #1 is not correct: in the backend, there isn't any check controlling if the material is locked or not in a MDG Change Request. Technically, a material can be changed/extended/marked for deletion in the "active" area using MMxx transaction even when it is already "in process" in MDG; once a Change Request is created, MDG takes a snapshot of the record and it works with these data until the workflow is not finalized. In case of any change performed directly in the active area, the system raises an info message when the MDG Change Request is processed.

That's an other reason to restrict the usage of "classical" transactions once MDG is active.