Wellbore ESP

the wellbore esp table describes electric submersible pumps installed in the well an esp belongs to a tubing string — sourcetubingid must match an existing wellbore tubing docid\ t6sgy9y9xnvabpqnnqotq record the pump name must match a pump in the compute catalog to enable modeling tapered assemblies are represented as multiple records on the same tubing string, sequenced by installorder the unique constraint on esp entries is sourcetubingid + sourceid the tubing string referenced by sourcetubingid must be loaded before adding an esp to it variable data type unit of measure is nullable? default value description sourceid string no unique identifier of the esp, to enable upserts sourcewellid string no source id for the well must match the sourceid of a record in the well docid\ p xhbe4jqkjqemay7aol5 table sourcewellboreid string no source id for the wellbore must match the sourceid of a record in the wellbore docid\ xpqwcas8awdawyssmvjy6 table sourcetubingid string no source id of the tubing string in which the esp is installed must match the sourceid of a wellbore tubing docid\ t6sgy9y9xnvabpqnnqotq record name string no pump name must match a pump in the compute catalog installorder int no 0 the installation order of tapered pumps, starting at the top with index 0 for example, with 100 stages of pump a, 125 stages of pump b, and 75 stages of a gas handler pump a is 0, pump b is 1, and the gas handler is 2 stages int no number of pump stages installed headdegradation double % yes default head degradation applied when it cannot be calculated hasgashandler boolean no whether the pump assembly has a gas handler hasseparator boolean no whether the pump assembly has a gas separator viscositycorrection boolean yes whether to apply viscosity corrections in conjunction with gas separation separationefficiency double % yes default gas separation efficiency applied when it cannot be calculated rundate datetime offset no date the pump was installed datetime offset (with timezone) in iso 8601 format example 2022 09 27t16 28 37 +0000 pulldate datetime offset yes date the pump was pulled datetime offset (with timezone) in iso 8601 format data integrity checks condition response any non nullable field is null or empty record rejected (sourcewellid, sourcewellboreid, sourcetubingid) does not match an existing tubing row skipped partial success on bulk ingest rows referencing an unknown tubing string 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 esp unknown tubing esp with sourceid 'xxx' was skipped tubing with sourcewellid 'xxx' and sourcewellboreid 'xxx' and sourcetubingid 'xxx' was not found