The Timer start event is a component in SAP Cloud Integration used to trigger an integration flow based on a defined schedule. It provides a "Run Once" scheduling option, which is specifically designed to execute the integration flow a single time, immediately after it has been successfully deployed to the runtime. This directly addresses the requirement to run a flow right after deployment without any external trigger. The other options are processing steps within a flow, not start events.

A. Content Modifier: This is a message processing step used to modify the message body, headers, or properties. It does not initiate the integration flow.

B. Router: This is a routing element that directs the message to different processing paths based on specified conditions. It is not a start event.

C. Message Digest: This is a security-related flow step used to calculate a digest (hash) of the message content to ensure data integrity. It does not trigger a flow.

1. SAP Help Portal

SAP Cloud Integration Documentation: "Define Timer Start Event"

Reference Details: In the section describing the scheduler configuration for the Timer event

the "Run Once" option is detailed. The documentation states: "The integration flow is scheduled to run immediately after deployment." This confirms that the Timer event is the correct component for this purpose.

Source: SAP Help Portal

Cloud Integration > Creating an Integration Flow > Define the Integration Flow > Define Start and End Events > Define Timer Start Event.

2. SAP Help Portal

SAP Cloud Integration Documentation: "Integration Flow"

Reference Details: The general overview of an integration flow distinguishes between start events (like Timer or Sender adapters) that initiate the process and flow steps (like Content Modifier

Router) that process the message. This document clarifies the different roles of the components mentioned in the question options.

Source: SAP Help Portal

Cloud Integration > Getting Started > Basic Concepts > Integration Flow.