Show TOC

 Bulk, Bundle, Collection

Basic service operation patterns, such as request-confirmation, operate on a single instance of a business object. However, this processing mode can cause performance issues when used in mass data run scenarios. Therefore, operation patterns have been introduced to allow many object instances to be processed together. The following types, each with a different error-handling behavior, are used:

  • BulkThe bulk pattern groups multiple messages for processing. A bulk message is executed as a single operation call. The execution of this pattern assumes no logical sequence to the group of messages, nor any dependencies between individual messages. The result of a bulk pattern run is the same as if each message was processed as a single, consecutive service operation. However, use of the bulk pattern does not allow more than one operation on a given business object in a bulk message.

  • Bundle The bundle pattern groups multiple Business Document Objects (BDO) for processing. A bundle message is executed as a single operation call. If an error occurs while processing a BDO, all BDOs in the bundle message are rolled back to their original state. The execution of this pattern assumes no logical sequence to the group of BDOs, nor any dependencies between individual BDOs. Use of the bundle pattern does not allow more than one operation on a given business object in a bundle message.

  • CollectionThe collection pattern groups multiple BDOs for processing. A collection message is executed as a single operation call. If an error occurs in any one service operation, all objects in the bundle are rolled back to their original state. The BDOs contained in a collection message are grouped by business use and may have dependencies. However, use of the collection pattern does not allow more than one operation on a given business object in a collection message.