Which of the following characteristics apply to the situation handling process of informing if the goods are damaged during delivery? Note: There are 2 correct answers to this question.

Question

Options

• AAn alert is raised to inform the warehouse clerk
• BSituation template Delivery Insights for Ordered Items is used for notification
• CThe supplier invoice is automatically blocked
• DThe information is based on SAP IoT sensor data

• A
  74% (32)
• C
  9% (4)
• D
  16% (7)

Explanation

When goods are damaged during delivery, SAP's Situation Handling framework raises an alert to notify the warehouse clerk (A), enabling them to take immediate action - and it uses the predefined "Delivery Insights for Ordered Items" situation template (B) to trigger and format that notification. These two work together: the template defines the situation type and the alert is the mechanism that delivers the message to the right role.

Option C is wrong because automatic invoice blocking is not part of Situation Handling - that belongs to separate logistics invoice verification processes (e.g., blocking in MIRO/LIV). Option D is wrong because this standard situation handling draws on delivery and goods receipt business document data, not IoT sensor feeds; IoT integration is a distinct capability not involved here.

Memory tip: Think of Situation Handling as "notify, don't act" - it informs (alert to clerk, via a template), but it does not block documents or rely on sensor hardware. The template name contains "Delivery Insights," which hints at its use for delivery-related notifications.

No community discussion yet for this question.