The following business object structures show a method with the same integration object as the input and output, an inbound event business object based on the account interface integration object, and a method with a different integration object as the input and output.
The following diagram represents a method with the same integration object being used as input and output.
The top-level object of the business structure 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 following diagram represents a business object for an inbound event. The top-level data represents 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 enterprise information system (EIS). This means that the same business object type that you send in as a request is 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 (IO) and their respective fields and components within business services, as shown below.
The following diagram corresponds to a custom business service with a different integration object as the method’s input and output.