Wellbore Tubing

the wellbore tubing table describes the tubing strings installed in a wellbore each record is one tubing string with its depth interval, diameters, and run/pull dates prodx uses tubing geometry to determine the flow path and compute bottomhole pressures the unique constraint on tubing entries is sourcewellboreid + sourceid variable data type unit of measure is nullable? default value description sourceid string no source id for the tubing string from wellview wvtub table, idrec column from openwells cd assembly table, assembly id column sourcewellid string no source id for the well from wellview wvtub table, idwell column from openwells cd assembly table, well id column sourcewellboreid string no source id for the wellbore from wellview wvtub table, idrecwellbore column from openwells cd assembly table, wellbore id column topmd double ft yes 0 0 top measured depth of the tubing string bottommd double ft no bottom measured depth of the tubing string id double in no inner diameter of the tubing from wellview wvtub table, szidnommincalc column od double in no outer diameter of the tubing from wellview wvtub table, szodnommincalc column roughness double in yes 0 0006 absolute roughness coefficient of the tubing material rundate datetime offset yes date the tubing was run datetime offset (with timezone) in iso 8601 format example 2022 09 27t16 28 37 +0000 pulldate datetime offset yes date the tubing was pulled datetime offset (with timezone) in iso 8601 format wellbore tubing notes tubing data is optional for wells with no tubing data and tubing pressures missing or atmospheric, the well model interprets casing flow for wells with no tubing data and tubing pressures greater than atmospheric, the well model interprets tubing flow, copying tubing properties and dimensions from the temporally adjacent tubing string top measured depth notes if topmd is null, the system assumes 0 ft roughness notes if roughness is null, the compute engine applies 0 0006 in its place data integrity checks condition response any non nullable field is null or empty record rejected (sourcewellid, sourcewellboreid) does not match an existing wellbore row skipped partial success on bulk ingest rows referencing an unknown wellbore are skipped while the remaining rows are written the error response names each skipped row an error response therefore does not mean nothing was written common error messages api scenario error response add / upsert tubing unknown wellbore tubing with sourceid 'xxx' was skipped wellbore with sourcewellid 'xxx' and sourcewellboreid 'xxx' was not found