| Name | Obligation |
|---|---|
| Entity Type | Table |
| Description | A condition or commitment that must be fulfilled in order to satisfy the terms of an agreement. Obligations may be financial (such as rental payments) or non-financial (such as reporting). |
| Submodel | Obligation |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Obligation_Number , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Active_Flag | boolean | NA |
A flag indicating if the obligation is currently active and must be met. The setting of this flag is determined by conditions such as whether prior obligations have been met, whether a prerequisite condition has been fulfilled etc. This flag should be set to yes when the obligation has been triggered and there are requirements to be met. If an obligation has not yet been triggered, or if the conditions of the obligation have been met in full, this flag may be set to no. Obligations that have been permanently fulfilled may be flagged by setting Fulfilled_Flag to yes. (PPDM3.7) | No |
NUMBER(1) |
| Critical_Date | DATE | NA |
The date by which an obligation must be fulfilled. (PPDM3.7) | No |
DATE |
| Currency_Code | R_Currency |
|
The currency in which monetary amounts are expressed. | No |
VARCHAR2(64) |
| End_Date | DATE | NA |
Date on which the obligation expired. | 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) |
| Fulfilled_Date | DATE | NA |
Date on which obligation was fulfilled. (PPDM3.7) | No |
DATE |
| Fulfilled_Flag | boolean | NA |
A flag that indicates whether or not the obligation has been fulfilled. For example, this may be used in the case where all rental payments over a five year period have been made in advance, and indicates that there are no additional obligations to incur. (PPDM3.7) | No |
NUMBER(1) |
| Fulfilled_Remark | STRING255 | NA |
Narrative comments about how the obligation was fulfilled. (PPDM3.7) | No |
VARCHAR2(255) |
| 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) |
| Gross_Obligation_Cost | double | No_Unit |
Total payment amount required to fulfill the obligation. (PPDM 3.7) | No |
NUMBER |
| 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) |
| Inspection_Required_Flag | boolean | NA |
A flag that denotes whether or not an inspection is required to verify that the obligation has been fulfilled. | No |
NUMBER(1) |
| Liability_Release_Date | DATE | NA |
The date of release from liability for this obligation. (PPDM3.7) | No |
DATE |
| Life_Cycle_Stage | STRING64 | NA |
The current stage in the life cycle of the obligation. | No |
VARCHAR2(64) |
| Name | ENTITY_NAME | NA |
The name given to any object or data item, e.g. name of Well, name of Field, etc. | No |
VARCHAR2(255) |
| Obligation_Category | R_Obligation_Category |
|
The broad category of obligation. Examples are financial, reporting, work, etc. | No |
VARCHAR2(64) |
| Obligation_Description | REMARKS_STR | NA |
A description of the obligation or commitment. (PPDM3.7) | No |
VARCHAR2(999) |
| Obligation_Duration | double | No_Unit |
Length of time for which obligation is applicable. | No |
NUMBER |
| Obligation_Duration_UOM | R_Unit |
|
The unit in which the Obligation_Duration value is expressed. | No |
VARCHAR2(64) |
| Obligation_Frequency | R_Transient_Period |
|
The frequency with which this obligation is due. (PPDM3.7) For example, yearly, monthly, etc. | No |
VARCHAR2(64) |
| Obligation_Number | STRING64 | NA |
A value, either textual or numeric, that uniquely identifies an obligation. | No |
VARCHAR2(64) |
| Obligation_Start_Date | DATE | NA |
the date on which work to fulfill an obligations started. This could be when a work program was initiated or when a financial obligation was first paid. (PPDM3.7) | No |
DATE |
| Obligation_Trigger_Code | R_Oblig_Trigger |
|
The means by which this obligation is triggered and becomes active. | No |
VARCHAR2(64) |
| Obligation_Type | R_Obligation |
|
The type of obligation incurred, such as termination notice, surrender notice, rental, royalty, etc. | No |
VARCHAR2(64) |
| Obligation_Value | STRING64 | NA |
A value, either textual or numeric, that identifies the number of obligations. For Example 3 wells, > 10 Square Miles. | No |
VARCHAR2(64) |
| Original_Source | STRING64 | NA |
The name of the person, Organization or project source that originally provided this entity, e.g. "IHS-EnergyData" or "FinderUpper Stratton Deeper Pool 15" | No |
VARCHAR2(64) |
| Payment_Flag | boolean | NA |
A flag that indicates whether or not obligation is for payment. (Y= payment obligation) (PPDM3.7) | No |
NUMBER(1) |
| Potential_Obligation_Desc | REMARKS_STR | NA |
Description of the condition or event which triggers the obligation. Could be a SQL query which queries the database to determine whether the condition has been met (typically related to cost and production revenue) (PPDM3.7) | No |
VARCHAR2(999) |
| Potential_Obligation_Flag | boolean | NA |
Indicator to identify if it is a potential obligation. It signifies that this obligation is not currently an obligation, but will become so when the obligation description has been fulfilled. (Y= potential obligation) | No |
NUMBER(1) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Regulatory_Act_Name | STRING255 | NA |
The name or title of an act, piece of legislation or a regulation that has been set up to manage a restricted area such as a bird sanctuary, migration route, fishery or logging reserve. (PPDM3.7) | No |
VARCHAR2(255) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| Resp_BA_Id | Business_Associate |
|
The business associate who is responsible for the fulfillment of this obligation. | No |
NUMBER(38) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Source | STRING64 | NA |
Name of the person or organization responsible for this entitys E and P content and quality. Not the data technologist or IT expert creating the entity, for which see IT_Object.Insert_User and Update_User. | No |
VARCHAR2(64) |
| Start_Date | DATE | NA |
Date on which the obligation became effective. | 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Instrument | Obligation | The actual document the obligation is defined in. | Nullify | No |
| Land_Desc_Component | Obligation | If the land description component is an obligation, this is the identifier of that obligation. | Cascade | No |
| Obligation_Component | Obligation | The identifier of the obligation to which the obligation component is tied. | Cascade | Yes |
| Obligation_Payment | Obligation | The obligation that requires this payment. | Cascade | Yes |
| Obligation_Reference | Referencing_Obligation | The obligation that is referencing another obligation. | Cascade | Yes |
| Obligation_Reference | Referenced_Obligation | The obligation that is referenced by another obligation. | Cascade | Yes |
| Obligation_Remark | Obligation | The obligation to which this remark applies. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Currency_Code | R_Currency | The currency in which monetary amounts are expressed. | Restrict | No |
| Obligation_Category | R_Obligation_Category | The broad category of obligation. Examples are financial, reporting, work, etc. | Restrict | No |
| Obligation_Duration_UOM | R_Unit | The unit in which the Obligation_Duration value is expressed. | Restrict | No |
| Obligation_Frequency | R_Transient_Period | The frequency with which this obligation is due. (PPDM3.7) For example, yearly, monthly, etc. | Restrict | No |
| Obligation_Trigger_Code | R_Oblig_Trigger | The means by which this obligation is triggered and becomes active. | Restrict | No |
| Obligation_Type | R_Obligation | The type of obligation incurred, such as termination notice, surrender notice, rental, royalty, etc. | Restrict | No |
| Resp_BA | Business_Associate | The business associate who is responsible for the fulfillment of this obligation. | Restrict | No |