MB-335 · Question #274
Drag and Drop Question A lean manufacturing company is implementing Dynamics 365 Supply Chain Management. The company plans to use kanban auto planning for process jobs. Work cells are grouped into…
The correct answer is Postpone; Distribute. Dynamics 365 SCM - Kanban Capacity Shortage Reaction Core Concept In D365 SCM kanban auto planning, the Capacity shortage reaction setting controls what the system does when a work cell's capacity is exceeded during auto planning. Each work cell group can be configured…
Question
Drag and Drop Question A lean manufacturing company is implementing Dynamics 365 Supply Chain Management. The company plans to use kanban auto planning for process jobs. Work cells are grouped into GroupA and GroupB.
- GroupA has a fixed quantity capacity. If the capacity is exceeded
when the auto planning runs, the job must be scheduled when capacity is available again.
- GroupB has hours capacity based on workers. If capacity is exceeded
when the auto planning runs, the job must still be scheduled and the managers will identify the workers needed. You need to configure the Capacity shortage reaction. What should you configure? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content NOTE: Each correct selection is worth one point. Answer:
Exhibits
Answer Area
Drag items
Correct arrangement
- Postpone
- Distribute
Explanation
Dynamics 365 SCM - Kanban Capacity Shortage Reaction
Core Concept
In D365 SCM kanban auto planning, the Capacity shortage reaction setting controls what the system does when a work cell's capacity is exceeded during auto planning. Each work cell group can be configured independently.
Correct Arrangement
| Requirement | Configuration |
|---|---|
| GroupA - Fixed quantity capacity; schedule when capacity is available again | Postpone |
| GroupB - Hours/worker capacity; must still be scheduled regardless | Distribute |
Item-by-Item Explanation
1. GroupA → Postpone
GroupA uses fixed quantity capacity and the business rule is explicit: if capacity is exceeded, the job waits until capacity opens up. Postpone does exactly this - the kanban job is pushed to the next available planning period where capacity exists. The job is not lost or cancelled; it simply queues and is rescheduled automatically when room exists.
2. GroupB → Distribute
GroupB uses hours-based (worker) capacity and the business rule is also explicit: the job must still be scheduled even when capacity is exceeded, and managers will manually resolve the staffing gap. Distribute tells the system to go ahead and schedule the job regardless of the overload - the system accepts the capacity violation and the overload is visible to planners/managers who then assign additional workers.
Why Not the Others?
- Cancel - Eliminates the job entirely on capacity breach. Neither group wants jobs discarded.
- Add to request period - Places the job back into the demand/request bucket rather than scheduling it forward. This is not the behavior described for either group.
Common Misconceptions
- Students often confuse Postpone with Cancel - Postpone reschedules; Cancel removes.
- Distribute does not mean splitting the job across periods - it means "proceed and accept the overload," allowing human intervention (the manager identifying workers).
- The key discriminator in the question is the phrase "must still be scheduled" for GroupB - that phrase directly signals Distribute, not Postpone.
Topics
Community Discussion
No community discussion yet for this question.