This topic illustrates a business object for an inbound event.
The following diagram represents a business object for an inbound event.
The Business Object structure follows the Template Business Graph pattern of the Business Object Framework (BOF). Where there is a business graph and template or top level object (TLO) which is a single element to the graph and what we consider the data parameters for the methods on the business service.
The top level object contains metadata information that states the business service for which the business object corresponds. The business graph contains Top Level Verbs which are used during event notification as an emit event which is based on the verb. The verbs currently supported are Create, Update and Delete.
The data in the TLO is a combination of the representation of both input and output arguments with the Siebel Message as a container. This same business object can be used for both request and response to and from the adapter to interact with the underlying Siebel EIS. This means that the same business object type you send in as a request will be returned as the result of the execution.
The Siebel Message is a wrapper similar to the wrapper the Siebel EIS uses to wrap Integration Objects and their respective fields and components within business services.
Parent topic: Business object structure examples