Business Document Support Type:

Description:

BDoc Not Supported

Business objects do not support database interaction at all and hence cannot be persisted across two different end user sessions. The objects cannot be saved. Such objects are designed as scratch or memory based objects.

The business factory always creates these objects as blank objects with any BDoc assignment. A typical example can be a global business object that implements generic functionality like the Clone method which is then used by other business objects..

New BDoc Supported

Business Objects can be loaded and saved by the assigned BDoc. Calling the Save method leads to a commit of the write-BDoc. They are not dependent on other objects. However, if such a business object has a parent, it will then be saved with the Write BDoc of the parent Business Object rather than its own.

BDoc Supported

Business Objects can be loaded but not saved independently. They are child objects in a 1:1 or 1:n relationship. These objects are hierarchically dependent on the parent object, which has a BDoc support of the type blNewTransactionRequired.

Calling the Save method on these objects will propagate the save to the parent object. The parent object will initiate the save operation of these objects inside its Write BDoc. They are then saved together with the parent object. Inside the BDoc, a segment that is hierarchically dependent on the root segment represents the data of the child object.