Qbyte Exchange for Mineral Sub

File Number*

File Sub*

File Status*

Code must exist in Validation Table > File Status Mineral.

Note: Generally, terminating/inactivating files should be done in the Qbyte CS Land application. IF the File Status is changed in Qbyte Exchange, remember to also update the Status Date.

Status Date*

Value must be in a yyyy-MM-dd format and cannot be greater than today's date.

Division

Code must exist in Validation Table.

Area*

Code must exist in Validation Table.

Extension

Code must exist in Validation Table > Extensions.

Extension Date

Value must be in a yyyy-MM-dd format.

Sub Interest Type*

Rental Rate

Total Sub Rental

Sub Operator*

BA Code entered must exist in Business Associates.

Count Acreage

Value must be Y or N.

Sub Exp Acres

Sub Gross Acres

Sub Exp Hect

Sub Gross Hect

Owner Interest

Producing Status

Code must exist in Validation Table > Acreage Status > Producing.

Prod Acres

Prod Hect

Nonprod Acres

Nonprod Hect

Developed Status

Code must exist in Validation Table > Acreage Status > Developed.

Dev Acres

Dev Hect

Undev Acres

Undev Hect

Proven Status

Code must exist in Validation Table > Acreage Status > Proven.

Proven Acres

Proven Hect

Nonproven Acres

Nonproven Hect

Land District

Code must exist in Validation Table > Land District.

Explor District

Code must exist in Validation Table > Exploration District.

File Number*

File Sub*

Occurrence

Do not populate this column when inserting new data. This is a system-generated value and it will be populated during Save.

Note : T he  Occurrence (Occ) Number can be renumbered at any time in the Qbyte CS Land application (if required) to change the display order of the rows.

Delete

This value is applicable on the spreadsheet only and is not stored in the table. 

When inserting a new Remarks record, enter a value of "N".  If blank, "N" is assumed.

When updating, retrieve existing data via Get Data, the Delete value will default to "N".  Change the value to "Y" to indicate that you wish to delete the specific row.  If blank, "N" is assumed. 

• Validate will display a 'Conflict' error along with message 'Row will be deleted - are you sure?'.  Simply change the Delete column back to "N", if you change your mind.  

• Upon Save, the Remarks with a delete flag of "Y" are deleted from the database and the remaining remarks occurrence number will be renumbered.  However, the just deleted row will still appear temporarily on the spreadsheet with status = 'Deleted' as a visual indication that the row has been deleted and the occurrence renumber will not be apparent.  A subsequent Get Data will omit the deleted rows and display the reordered remarks occurrence. 

Remark Type*

Code must exist in Validation Table.

Remark Date

Value must be in a yyyy-MM-dd format.

Remark*

Free-format up to 1910 characters.

File Number*

File Sub*

Land Description*

File Number*

File Sub*

Rights Held*

File Number*

When inserting new records, the File Number specified must already exist.

Note: This field cannot be updated after Insert → Save is completed. If relationship is no longer required, it must be deleted in the application. When using 'get data' to retrieve existing data, you may want to sort by File Number to ensure all rows for each File Number appear grouped together.

File Sub*

When inserting new records, the File Sub specified must already exist.

Related Subsystem*

When inserting new records, enter the module for which the related files is part of.

Acceptable codes:  C (any Contract category), M (Mineral), S (any Surface category), W (Well).  Qbyte Exchange has the same Related Files exceptions as Qbyte CS Land.

Note : This field cannot be updated after Insert → Save is completed.

Related File Number*

When inserting new records, enter the file number for which you are relating to the file number specified in column A.

Note: This field cannot be updated after Insert → Save is completed.

Related File Sub

When inserting new records, enter a sub, if applicable to relate files at the sub level.

Note: This field cannot be updated after Insert → Save is completed.

Relationship

If entered, the code must exist in Relationship Validation Table.

Comment

Free-format up to 120 characters.

File Number*

When inserting new Obligation records, the File Number specified must already exist.  

When updating an existing Obligation, the File Number cannot be changed.

File Sub*

When inserting new records, the File Sub specified must already exist.

When updating an existing Obligation, the File Number cannot be changed. 

Occurrence*

When inserting a new row do not populate this column, this is a system-generated value, and it will be populated during Save.

Note: The  Occurrence (Occ) Number can be renumbered at any time in the Qbyte CS Land application (if required) to change the display order of the rows.

Delete

This value is applicable on the spreadsheet only and is not stored in the table. 

When inserting a new record, enter a value of "N".  If blank, "N" is assumed.

When updating, retrieve existing data via Get Data, the Delete value will default to "N".  Change the value to "Y" to indicate that you wish to delete the specific row.  If blank, "N" is assumed. 

• Validate will display a 'Conflict' error along with message 'Row will be deleted - are you sure?'.  Simply change the Delete column back to "N", if you change your mind.  

• Upon Save, the rows with a delete flag of "Y" are deleted from the database and the remaining rows occurrence number will be renumbered.  However, the just deleted row will still appear temporarily on the spreadsheet with status = 'Deleted' as a visual indication that the row has been deleted and the occurrence renumber will not be apparent.  A subsequent Get Data will omit the deleted rows and display the reordered rows occurrence. 

Obligation Type*

Code must exist in Validation Table – Obligation Mineral.

Date*

Date must be in a yyyy-MM-dd format.  Cell format must be Text.

Frequency*

Value must be O, A, SA, Q, M, 2Y, 3Y, 4Y, 5Y, 10, 20, 21 or 25.

Company*

Value must be Y or N.

Satisfied*

Value must be Y or N.

Comp Date

Date must be in a yyyy-MM-dd format.  Cell format must be Text.

Party Resp*

Code must exist in Validation Table – Obligation Responsibility.

Description*

Free-format up to 1910 characters.

File Number*

When inserting new Mineral Lease W.I.s, the File Number specified must already exist.

File Sub*

When inserting new Mineral Lease W.I.s, the File Sub specified must already exist.

DOI Type*

Code must exist in the DOI Types Validation Table. 

Note:  if the exact DOI Type already exists, the existing DOI Type will be expired and a “new” DOI inserted.

Account Group*

Enter either CUR, REF, or RENT.  

Effective Date*

The value must be in a yyyy-MM-dd format. Cell format must be Text.

• Cannot be a “future date”.

• If inserting a new DOI of the same DOI Type of an existing DOI, then the Effective Date must be greater than the Effective Date of the existing DOI.

Comments

Free-format up to 60 characters.

DOI ID

When inserting new Term, do not populate this column. This is a system-generated value and it will be populated during Save.

When updating existing Terms, do not change this column.

Partner BA ID 1*

BA Code entered must exist in Business Associates and must be active.

• Up to 10 Partners and Percentages can be specified.  If more then 10 are required, they must be entered via the Qbyte CS Land application. 

• The total of all Partner Percentages entered must equal 100%.

Partner Percentage 1*

Partner BA ID 2*

Partner Percentage 2*

Partner BA ID 3*

Partner Percentage 3*

Partner BA ID 4*

Partner Percentage 4*

Partner BA ID 5*

Partner Percentage 5*

Partner BA ID 6*

Partner Percentage 6*

Partner BA ID 7*

Partner Percentage 7*

Partner BA ID 8*

Partner Percentage 8*

Partner BA ID 9*

Partner Percentage 9*

Partner BA ID 10*

Partner Percentage 10*

File Number*

When inserting new Mineral Sub Royalty, the File Number specified must already exist.

File Sub*

When inserting new records, the File Sub specified must already exist.

Note: This field cannot be updated after Insert → Save is completed.

Royalty Type*

Valid values for Mineral are LOR or CSS.

Royalty ID

Do not populate this column when inserting new data. This is a system-generated value and it will be populated during Save.

Product*

Code must exist in the Royalty Production Validation Table. i.e. GAS, OIL, PNG, BOTH

Convertible*

Enter Y (Yes), N (No)

Sliding Scale*

Enter Y (Yes), N (No)

Royalty Percent

If the royalty is fixed, not calculated on a sliding scale, enter the royalty percent.  Value must be a positive decimal number not greater than 100.

%

If the royalty is fixed, not calculated on a sliding scale, enter the percentage of production or sales. Note:  Typically on LOR/CSS this % is 100.  Value must be a positive decimal number not greater than 100.

Prod/Sales

If the royalty is fixed, not calculated on a sliding scale, enter PROD (production) or SALES (sales) to indicate where the royalty percentage applies to.

Deductions*

Enter Y (Yes), N (No), U (Unknown) or S (Standard).  Typically, for CSS the deductions are Standard.

Note: For every file that has a Y (Yes) for Deductions, users will have to go into the Qbyte CS Land Mineral lease Sub Royalty to enter the respective Deduction Remarks, otherwise an error may occur when updating the file in Qbyte CS Land in the future.

Gas Royalty

If the well produces gas, enter the royalty percentage to pay.  Value must be a positive decimal number not greater than 100.

Min Pay

If the well produces gas, enter the minimum royalty payment percentage.

Gas Prod/Sales

If the well produces gas, enter PROD (production) or SALES (sales) to indicate which the minimum royalty payment percentage applies to.

S/S Oil Min

If the well produces oil, enter the minimum royalty payment percentage.

Max

If the well produces oil, enter the maximum royalty payment percentage. 

Div

If the well produces oil, enter the divisor that is used to calculate the royalty payment.

Oil Prod/Sales

If the well produces oil, enter PROD (production) or SALES (sales) to indicate which the royalty applies to.

Other%

If the well produces non-gas or oil products, enter the royalty percentage to pay.  Value must be a positive decimal number not greater than 100.

Min

If the well produces non-gas or oil products, enter the minimum royalty amount to pay.

Oth Prod/Sales

If the well produces non-gas or oil products, enter PROD (production) or SALES (sales) to indicate which the minimum royalty payment amount applies to.

PaidTo DOI Link*

Enter the Account Group for where you want to link the PaidTo to; typically DEPOSITORY will be entered but could be LESSOR, CURR, REF, or RENT.

Note: The Account Group entered must exist (i.e. the Lessor/Depository exists or the specific Account Group exists on the Sub WI). 

Once you have completed the Save data to P2 step, the PaidTo DOI in Qbyte CS Land will indicate: 

• Linked to Lease: DEPOSITORY or LESSOR or <DOI Type from the specified Account Group> 

PaidBy DOI Link*

Enter Account Group for which existing Mineral Lease Sub DOI you want to link the PaidBy to  CURRENT, CURR, REF or RENT

Note: The specified Account Group must exist in the Mineral Lease Sub DOI tab. 

Once you have completed the Save data to P2 step, the PaidBy DOI in Qbyte CS Land will indicate either:

• Linked to Current: <DOI Type from the CURR Accounting Group>  if CURRENT is used.

• Linked to Lease: <DOI Type from the selected Account Group>  if CURR, REF, or RENT is used.

Remarks Type

Code must exist in the Remarks Royalty Validation Table.

Note: Only one Remark can be inserted per Royalty in Qbyte Exchange at this time.   Additional Remarks can be inserted via the Qbyte CS Land Mineral Lease royalty window.

Remarks Date

The value must be in a yyyy-MM-dd format. Cell format must be Text.

Comment

Free-format up to 1910 characters.  

File Number*

When inserting a new Client Defined record, the File Number specified must already exist.  Any one File Number may have multiple rows in the spreadsheet if there are more than 1 applicable Client Defined Labels/Values.  

When updating an existing Client Defined record, the File Number cannot be changed.

Label*

When inserting a new Client Defined record, the Label must be entered exactly as it appears in the Qbyte CS Land window (or as defined in Admin > Client Defined Fields update screen). 

When updating an existing Client Defined record, the Label cannot be changed.

Value*

The Value is required when inserting new rows and can also be updated after the initial save.  The cell is always defined as Text in the Qbyte Exchange spreadsheet regardless of Value entered. 

Values entered are validated accordingly per the field setup in Qbyte CS Land:

• Dates can be entered with or without a format.   For example, if a date format of 'yyyy-mm-dd' has been defined, the date must be entered as '2022-12-13'. If a date format was not defined, the date can be entered as '2022-12-13', and Qbyte Exchange will format the date to the default date format of 'Dec 13, 2022' - just like it is in the application.

• Validation codes entered must exist in the applicable validation code table.

• String values entered must not exceed 1910 alpha/numeric characters.  Alt + Enter can be used to break the text string to a new line.

• Percentage can be entered with or without a format.  

• Number can be entered with or without a format.  For number fields setup with masks:

  • The 0 (zero) character will allow a leading zero to be entered in Qbyte CS Land and all leading zeroes will be visible when the field is imported to Qbyte Exchange.  For example, with mask 000-000-00000, entered as 00-000-0001 in Qbyte CS Land, will display as 000-000-0001 in Qbyte Exchange.

  • The # character will allow a leading zero to be entered in Qbyte CS Land only if there is a non-numeric character like a dash (-) in the mask.  Leading zeroes are not displayed when the field is imported to Qbyte Exchange.  For example, with mask ###-###-####, entered 000-000-0001 in Qbyte CS Land will display as '- -1' in Qbyte Exchange.

Note:  If a Client Defined field was setup in Qbyte CS Land as being mandatory, then in Qbyte Exchange a value must be provided for that field if that Label exists in the spreadsheet.  However, if there is not a row for the Label in the spreadsheet, there is not validation to indicate it is missing.