Name | Obligation_Component |
---|---|
Entity Type | Table |
Description | This table is used to capture the relationships between the obligation and other business objects, such as land agreements or wells. Each row in the table should capture one and only one relationship; use as many rows as needed to capture all relevant relationships. (PPDM 3.7) |
Submodel | Obligation |
Entity Scope | Project |
Primary Key | Id |
Natural Key | Obligation_Id , Land_Sale_Offering_Id , Land_Agreement_Parcel_Id , Land_Agreement_Id , Land_Sale_Bid_Id , Facility_Id , Well_Id , Start_Date , End_Date , Existence_Kind , Version |
Generalizations | Transient_Association , IT_Object , Tracked_Object |
Specializations |
Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
---|---|---|---|---|---|
End_Date | DATE | NA |
End time of the association | No |
DATE |
Existence_Kind | REF_EXISTENCE_KIND | NA |
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. | Yes Actual |
VARCHAR2(64) |
Facility_Id | Facility |
|
The facility affected by the obligation. | No |
NUMBER(38) |
Facility_Tbl | Meta_Entity |
|
Facility type | No |
VARCHAR2(30) |
GUID | STRING128 | NA |
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 |
VARCHAR2(128) |
Id | ID | No_Unit |
Unique identifier for this entity. | Yes |
NUMBER(38) |
Insert_Date | DATE | NA |
Date the entity was created in the repository | No |
DATE |
Insert_User | STRING64 | NA |
The name of the user responsible for the creation of this entity in the repository. | No |
VARCHAR2(64) |
Land_Agreement_Id | Land_Agreement |
|
If the obligation component is a land agreement, then this stores the identifier of that land agreement. | No |
NUMBER(38) |
Land_Agreement_Parcel_Id | Land_Agreement_Parcel |
|
If the obligation component is a land agreement parcel, then this stores the identifier of that land agreement parcel. | No |
NUMBER(38) |
Land_Sale_Bid_Id | Land_Sale_Bid |
|
If the obligation component is a land sale bid, this is the identifier of that land sale bid. | No |
NUMBER(38) |
Land_Sale_Offering_Id | Land_Sale_Offering |
|
If the obligation component is a land sale offering, then this stores the identifier of that land sale offering. | No |
NUMBER(38) |
Obligation_Id | Obligation |
|
The identifier of the obligation to which the obligation component is tied. | Yes |
NUMBER(38) |
Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
Remarks | REMARKS_STR | NA |
Remarks about the association between the obligation and the business object. | No |
VARCHAR2(999) |
SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
Start_Date | DATE | NA |
Start time of the association. | No |
DATE |
Update_Date | DATE | NA |
Date of the most-recent modification to the entity. | No |
DATE |
Update_User | STRING64 | NA |
The name of the user responsible for the last modification to this entity. | No |
VARCHAR2(64) |
Version | STRING255 | NA |
The form or variant of the entity. | Yes 1 |
VARCHAR2(255) |
Well_Id | Well |
|
The well affected by the obligation. | No |
NUMBER(38) |
Link | To Entity | Description | Implementation Technique | Required |
---|---|---|---|---|
Land_Sale_Offering | Land_Sale_Offering | If the obligation component is a land sale offering, then this stores the identifier of that land sale offering. | Cascade | No |
Obligation | Obligation | The identifier of the obligation to which the obligation component is tied. | Cascade | Yes |
Well | Well | The well affected by the obligation. | Cascade | No |
Land_Sale_Bid | Land_Sale_Bid | If the obligation component is a land sale bid, this is the identifier of that land sale bid. | Cascade | No |
Land_Agreement | Land_Agreement | If the obligation component is a land agreement, then this stores the identifier of that land agreement. | Cascade | No |
Land_Agreement_Parcel | Land_Agreement_Parcel | If the obligation component is a land agreement parcel, then this stores the identifier of that land agreement parcel. | Cascade | No |
Facility | Facility | The facility affected by the obligation. | Cascade | No |