[Columns] [Composed Of] [Referenced By] [Refers To]

General Information

Name Document_Body_Part
Entity Type Table
Description Any excess parts of a document that cannot be stored in the main class due to the limit in force on the size on BLOBs (Binary Large OBject). The sequence number indicates the order of this document part in the whole document body. The first part of a document is stored in the Document_Body attribute of the document class and the subsequent parts are stored in this class with the sequence set to 2 for the second part, 3 for the third etc.
Submodel Utility
Entity Scope Project
Primary Key Id
Natural Key Document_Id , Sequence_Number , Existence_Kind , Version
Generalizations IT_Object , Tracked_Object


[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Document_Id Document
The document to which this part belongs. Yes
Document_Part BLOB NA
The body of the document stored as a blob No
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. Yes
Globally Unique IDentifier for an instance of a class. USAGE NOTES: There are two cases: 1) GUID is not populated or used; and 2) it is populated with a value that is globally unique. If the GUID is populated there are two means of doing so for a given project: 2a) Seabed automatically generates and populates the GUID when an instance is created (valid only on Oracle based systems); and 2b) the GUID is generated and populated by an application (other than Seabed) on instance creation. Whether Seabed automatically generates GUIDs for a project is determined by the Auto_GUID flag in SDS_Account. Note that techniques 2a and 2b can coexist in the same project. When GUIDs are automatically generated an application can override the automatically generated GUID with its own GUID by simply supplying the GUID value. Applications that generate their own GUIDs and populate the GUID column will function correctly on projects which have automatic GUID generation turned on. No
Id ID No_Unit
Unique identifier for this entity. Yes
Insert_Date DATE NA
Date the entity was created in the repository No
Insert_User STRING64 NA
The name of the user responsible for the creation of this entity in the repository. No
Produced_By STRING64 NA
The name of application role that created the entity, for data created programmatically. No
Relative_Size_Indicator CODE NA
An indicator of the relative size of the BLOB (Binary Large OBject) in the Document_Part attribute. The possible values are "Small", "Medium", and "Large". When the partitioning option is selected for a Seabed database, different storage areas (i.e., tablespaces in Oracle) are created to handle different sized objects more efficiently. The relative size indicator helps determine which storage area to use within the partitioning scheme. No
SDAT_Label int No_Unit
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. No
Sequence_Number int No_Unit
An integer that represents the relative position of the document part in a sequence of parts. No
Update_Date DATE NA
Date of the most-recent modification to the entity. No
Update_User STRING64 NA
The name of the user responsible for the last modification to this entity. No
Version STRING255 NA
The form or variant of the entity. Yes

Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Document Document The document to which this part belongs. Cascade Yes

[Seabed Objects] [Entities in Schema Seabed] [Index]

Copyright © 2018 Schlumberger. All rights reserved.