3688376 - Movement type for follow-up actions of posting change in quality management - SAP S/4HANA Public Cloud Edition

• Movement type 321 and 350 are incorrectly triggered when recording the usage decision with A3 and R310 usage decision code, while the stock is located in GR Zone.
• Movement type 333 and 551 are correctly triggered when the stock is transferred to Final bin when recording the usage decision with A3 and R310 usage decision code.

SAP S/4HANA Public Cloud Edition

• The root cause is related to the inbound delivery reference associated with the stock in GR-AREA. When the stock is in GR-AREA, the inbound delivery reference prevents the system from triggering goods issue directly, resulting in movement type 350 instead of 333.
• When the stock is transferred to Final bin, the inbound delivery reference is removed, enabling the system to trigger movement type 333 directly.

1. Verify the customizing settings for "Maintain Follow-Up Actions" for the A3 usage decision code, which maps to "SWM_SMP".
2. Confirm that the follow-up action is configured for sample consumption (goods issue).
3. Check the customizing settings for "Maintain Storage Types" to ensure that the putaway confirmation flag is set, which removes the inbound delivery reference when stock is transferred to final bin.
4. Ensure that stock is transferred to a final bin other than GR-AREA (e.g., QA-01-A) before recording the usage decision with A3 to trigger movement type 333.

• Refer to: SAP Help Portal - Movement Types for Quality Management.

movement type, 333, 321, 350, 551, usage decision, A3, R310, GR-AREA, QA-01-A, inbound delivery reference, follow-up actions, sample consumption, goods issue, quality management, SAP S/4HANA Cloud. , KBA , SCM-EWM-QM-2CL , Quality Management (Public Cloud) , Problem