An event is a message sent by an object to say that it has changed its state (attributes). It generally contains export parameters but no import parameters. It is like an inverse method and can be defined in a class or an interface. Events are commonly user-driven.
Cause of an entry in the injury/illness log or incident/accident log.
Examples:
Object type in the R/3 Reference Model.
In the R/3 Reference Model, an event is a status that has business relevance. An event can trigger an SAP System function, and it can be the result of a function.
Example: Standard order received.
Status change of an object which is "published" throughout the system. Examples: "invoice entered", "purchase order released".
The list of possible events is defined with the relevant object type in the Business Object Builder. This list can be extended according to customer requirements using the delegation concept. You have to ensure that the events added are actually created.
Each event carries information from its creation context in its event container. This information is available to the receiver of the event and can be used for event-driven control and communication mechanisms.
An event may start, terminate or continue tasks and workflows.
This concept is used in connection with bulk materials processing and describes transactions such as the sales order or the start of the loading, among others.
Factor, the effect of which on SOP data cannot be deduced from historical patterns.
Events complement the planning results derived from the forecast.
Deals, promotions, and market intelligence are all examples of events.