InspectionSubset (SAP Cloud SDK - Parent POM 3.9.0 API)

java.lang.Object
- com.sap.cloud.sdk.datamodel.odata.helper.VdmObject<EntityT>
- - com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity<InspectionSubset>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.qualityinspectiondata.InspectionSubset

```
public class InspectionSubset
extends VdmEntity<InspectionSubset>
```
Inspection Subset

Original entity name from the Odata EDM: A_InspectionSubsetType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class InspectionSubset.InspectionSubsetBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`InspectionSubset.InspectionSubsetBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static InspectionSubsetSelectable`	`ALL_FIELDS` Selector for all available fields of InspectionSubset.
`static InspectionSubsetField<ZonedDateTime>`	`CHANGED_DATE_TIME` Use with available fluent helpers to apply the ChangedDateTime field to query operations.
`static InspectionSubsetField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static InspectionSubsetField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static InspectionSubsetField<LocalTime>`	`CREATION_TIME` Use with available fluent helpers to apply the CreationTime field to query operations.
`static InspectionSubsetField<String>`	`EQUIPMENT` Use with available fluent helpers to apply the Equipment field to query operations.
`static InspectionSubsetField<String>`	`FUNCTIONAL_LOCATION` Use with available fluent helpers to apply the FunctionalLocation field to query operations.
`static InspectionSubsetField<String>`	`INSP_PLAN_OPERATION_INTERNAL_ID` Use with available fluent helpers to apply the InspPlanOperationInternalID field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_DATE_FLD_PROPERTY` Use with available fluent helpers to apply the InspSbstDateFldProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_EQUIP_PROPERTY` Use with available fluent helpers to apply the InspSbstEquipProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_FUNCNL_LOC_PROPERTY` Use with available fluent helpers to apply the InspSbstFuncnlLocProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_LONG_NMBR_FLD_PROPERTY` Use with available fluent helpers to apply the InspSbstLongNmbrFldProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_LONG_TXT_FLD_PROPERTY` Use with available fluent helpers to apply the InspSbstLongTxtFldProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_MATL_SMPL_PROPERTY` Use with available fluent helpers to apply the InspSbstMatlSmplProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_SHRT_NMBR_FLD_PROPERTY` Use with available fluent helpers to apply the InspSbstShrtNmbrFldProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_SHRT_TXT_FLD_PROPERTY` Use with available fluent helpers to apply the InspSbstShrtTxtFldProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SBST_TIME_FLD_PROPERTY` Use with available fluent helpers to apply the InspSbstTimeFldProperty field to query operations.
`static InspectionSubsetField<String>`	`INSP_SUBSET_LONG_NUMERIC_KEY` Use with available fluent helpers to apply the InspSubsetLongNumericKey field to query operations.
`static InspectionSubsetField<String>`	`INSP_SUBSET_SHORT_NUMERIC_KEY` Use with available fluent helpers to apply the InspSubsetShortNumericKey field to query operations.
`static InspectionSubsetField<String>`	`INSP_SUBSET_USAGE_DCSN_CODE` Use with available fluent helpers to apply the InspSubsetUsageDcsnCode field to query operations.
`static InspectionSubsetField<String>`	`INSP_SUBSET_USAGE_DCSN_CODE_GROUP` Use with available fluent helpers to apply the InspSubsetUsageDcsnCodeGroup field to query operations.
`static InspectionSubsetField<String>`	`INSP_SUBSET_USAGE_DCSN_VALUATION` Use with available fluent helpers to apply the InspSubsetUsageDcsnValuation field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_LOT` Use with available fluent helpers to apply the InspectionLot field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_PARTIAL_LOT` Use with available fluent helpers to apply the InspectionPartialLot field to query operations.
`static InspectionSubsetField<LocalDateTime>`	`INSPECTION_SUBSET_DATE` Use with available fluent helpers to apply the InspectionSubsetDate field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_SUBSET_INTERNAL_ID` Use with available fluent helpers to apply the InspectionSubsetInternalID field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_SUBSET_LONG_CHAR_KEY` Use with available fluent helpers to apply the InspectionSubsetLongCharKey field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_SUBSET_QTY_UNIT` Use with available fluent helpers to apply the InspectionSubsetQtyUnit field to query operations.
`static InspectionSubsetField<BigDecimal>`	`INSPECTION_SUBSET_REWORK_QTY` Use with available fluent helpers to apply the InspectionSubsetReworkQty field to query operations.
`static InspectionSubsetField<BigDecimal>`	`INSPECTION_SUBSET_SCRAP_QTY` Use with available fluent helpers to apply the InspectionSubsetScrapQty field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_SUBSET_SHORT_CHAR_KEY` Use with available fluent helpers to apply the InspectionSubsetShortCharKey field to query operations.
`static InspectionSubsetField<String>`	`INSPECTION_SUBSET_SORT_KEY` Use with available fluent helpers to apply the InspectionSubsetSortKey field to query operations.
`static InspectionSubsetField<LocalTime>`	`INSPECTION_SUBSET_TIME` Use with available fluent helpers to apply the InspectionSubsetTime field to query operations.
`static InspectionSubsetField<BigDecimal>`	`INSPECTION_SUBSET_YIELD_QTY` Use with available fluent helpers to apply the InspectionSubsetYieldQty field to query operations.
`static InspectionSubsetField<String>`	`INSPECTOR` Use with available fluent helpers to apply the Inspector field to query operations.
`static InspectionSubsetField<LocalDateTime>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static InspectionSubsetField<LocalTime>`	`LAST_CHANGE_TIME` Use with available fluent helpers to apply the LastChangeTime field to query operations.
`static InspectionSubsetField<String>`	`LAST_CHANGED_BY_USER` Use with available fluent helpers to apply the LastChangedByUser field to query operations.
`static InspectionSubsetField<String>`	`MATERIAL_SAMPLE` Use with available fluent helpers to apply the MaterialSample field to query operations.
`static InspectionSubsetField<String>`	`SELECTED_CODE_SET` Use with available fluent helpers to apply the SelectedCodeSet field to query operations.
`static InspectionSubsetField<String>`	`SELECTED_CODE_SET_PLANT` Use with available fluent helpers to apply the SelectedCodeSetPlant field to query operations.
`static InspectionSubsetField<Long>`	`SHOP_FLOOR_ITEM` Use with available fluent helpers to apply the ShopFloorItem field to query operations.
`static InspectionSubsetField<Boolean>`	`TRIGGER_VALUATION_AC` Use with available fluent helpers to apply the Trigger_valuation_ac field to query operations.

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
changedOriginalFields

Constructor Summary

Constructors
Constructor and Description
`InspectionSubset()`
InspectionSubset(Boolean trigger_valuation_ac, String inspectionLot, String inspPlanOperationInternalID, String inspectionSubsetInternalID, String materialSample, String equipment, String functionalLocation, Long shopFloorItem, String selectedCodeSetPlant, String selectedCodeSet, String inspSubsetUsageDcsnCodeGroup, String inspSubsetUsageDcsnCode, String inspSubsetUsageDcsnValuation, LocalTime inspectionSubsetTime, LocalDateTime inspectionSubsetDate, String inspSubsetLongNumericKey, String inspSubsetShortNumericKey, String inspectionSubsetLongCharKey, String inspectionSubsetShortCharKey, String inspectionPartialLot, String inspector, BigDecimal inspectionSubsetYieldQty, BigDecimal inspectionSubsetScrapQty, BigDecimal inspectionSubsetReworkQty, String inspectionSubsetQtyUnit, String inspSbstFuncnlLocProperty, String inspSbstEquipProperty, String inspSbstMatlSmplProperty, String inspectionSubsetSortKey, String inspSbstDateFldProperty, String inspSbstLongNmbrFldProperty, String inspSbstShrtNmbrFldProperty, String inspSbstLongTxtFldProperty, String inspSbstTimeFldProperty, String inspSbstShrtTxtFldProperty, String createdByUser, LocalDateTime creationDate, LocalTime creationTime, String lastChangedByUser, LocalDateTime lastChangeDate, LocalTime lastChangeTime, ZonedDateTime changedDateTime)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static InspectionSubset.InspectionSubsetBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`static <T> InspectionSubsetField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> InspectionSubsetField<T>`	`field(String fieldName, TypeConverter<T,DomainT> typeConverter)` Use with available fluent helpers to apply an extension field to query operations.
`protected void`	`fromMap(Map<String,Object> inputValues)`
`ZonedDateTime`	`getChangedDateTime()` Constraints: Not nullable, Precision: 0
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`LocalTime`	`getCreationTime()` Constraints: Not nullable, Precision: 0
`protected String`	`getDefaultServicePath()`
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`protected String`	`getEntityCollection()`
`String`	`getEquipment()` Constraints: Not nullable, Maximum length: 18
`String`	`getFunctionalLocation()` Constraints: Not nullable, Maximum length: 40
`String`	`getInspectionLot()` (Key Field) Constraints: Not nullable, Maximum length: 12
`String`	`getInspectionPartialLot()` Constraints: Not nullable, Maximum length: 6
`LocalDateTime`	`getInspectionSubsetDate()` Constraints: Not nullable, Precision: 0
`String`	`getInspectionSubsetInternalID()` (Key Field) Constraints: Not nullable, Maximum length: 6
`String`	`getInspectionSubsetLongCharKey()` Constraints: Not nullable, Maximum length: 18
`String`	`getInspectionSubsetQtyUnit()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getInspectionSubsetReworkQty()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getInspectionSubsetScrapQty()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getInspectionSubsetShortCharKey()` Constraints: Not nullable, Maximum length: 10
`String`	`getInspectionSubsetSortKey()` Constraints: Not nullable, Maximum length: 70
`LocalTime`	`getInspectionSubsetTime()` Constraints: Not nullable, Precision: 0
`BigDecimal`	`getInspectionSubsetYieldQty()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getInspector()` Constraints: Not nullable, Maximum length: 12
`String`	`getInspPlanOperationInternalID()` (Key Field) Constraints: Not nullable, Maximum length: 8
`String`	`getInspSbstDateFldProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstEquipProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstFuncnlLocProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstLongNmbrFldProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstLongTxtFldProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstMatlSmplProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstShrtNmbrFldProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstShrtTxtFldProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSbstTimeFldProperty()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSubsetLongNumericKey()` Constraints: Not nullable, Maximum length: 10
`String`	`getInspSubsetShortNumericKey()` Constraints: Not nullable, Maximum length: 3
`String`	`getInspSubsetUsageDcsnCode()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSubsetUsageDcsnCodeGroup()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSubsetUsageDcsnValuation()` Constraints: Not nullable, Maximum length: 1
`protected Map<String,Object>`	`getKey()`
`LocalDateTime`	`getLastChangeDate()` Constraints: Not nullable, Precision: 0
`String`	`getLastChangedByUser()` Constraints: Not nullable, Maximum length: 12
`LocalTime`	`getLastChangeTime()` Constraints: Not nullable, Precision: 0
`String`	`getMaterialSample()` Constraints: Not nullable, Maximum length: 12
`String`	`getSelectedCodeSet()` Constraints: Not nullable, Maximum length: 8
`String`	`getSelectedCodeSetPlant()` Constraints: Not nullable, Maximum length: 4
`Long`	`getShopFloorItem()` Constraints: none
`Boolean`	`getTrigger_valuation_ac()` Constraints: none
`Class<InspectionSubset>`	`getType()`
`int`	`hashCode()`
`void`	`setChangedDateTime(ZonedDateTime changedDateTime)` Constraints: Not nullable, Precision: 0
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCreationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`void`	`setEquipment(String equipment)` Constraints: Not nullable, Maximum length: 18
`void`	`setFunctionalLocation(String functionalLocation)` Constraints: Not nullable, Maximum length: 40
`void`	`setInspectionLot(String inspectionLot)` (Key Field) Constraints: Not nullable, Maximum length: 12
`void`	`setInspectionPartialLot(String inspectionPartialLot)` Constraints: Not nullable, Maximum length: 6
`void`	`setInspectionSubsetDate(LocalDateTime inspectionSubsetDate)` Constraints: Not nullable, Precision: 0
`void`	`setInspectionSubsetInternalID(String inspectionSubsetInternalID)` (Key Field) Constraints: Not nullable, Maximum length: 6
`void`	`setInspectionSubsetLongCharKey(String inspectionSubsetLongCharKey)` Constraints: Not nullable, Maximum length: 18
`void`	`setInspectionSubsetQtyUnit(String inspectionSubsetQtyUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setInspectionSubsetReworkQty(BigDecimal inspectionSubsetReworkQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setInspectionSubsetScrapQty(BigDecimal inspectionSubsetScrapQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setInspectionSubsetShortCharKey(String inspectionSubsetShortCharKey)` Constraints: Not nullable, Maximum length: 10
`void`	`setInspectionSubsetSortKey(String inspectionSubsetSortKey)` Constraints: Not nullable, Maximum length: 70
`void`	`setInspectionSubsetTime(LocalTime inspectionSubsetTime)` Constraints: Not nullable, Precision: 0
`void`	`setInspectionSubsetYieldQty(BigDecimal inspectionSubsetYieldQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setInspector(String inspector)` Constraints: Not nullable, Maximum length: 12
`void`	`setInspPlanOperationInternalID(String inspPlanOperationInternalID)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setInspSbstDateFldProperty(String inspSbstDateFldProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstEquipProperty(String inspSbstEquipProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstFuncnlLocProperty(String inspSbstFuncnlLocProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstLongNmbrFldProperty(String inspSbstLongNmbrFldProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstLongTxtFldProperty(String inspSbstLongTxtFldProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstMatlSmplProperty(String inspSbstMatlSmplProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstShrtNmbrFldProperty(String inspSbstShrtNmbrFldProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstShrtTxtFldProperty(String inspSbstShrtTxtFldProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSbstTimeFldProperty(String inspSbstTimeFldProperty)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSubsetLongNumericKey(String inspSubsetLongNumericKey)` Constraints: Not nullable, Maximum length: 10
`void`	`setInspSubsetShortNumericKey(String inspSubsetShortNumericKey)` Constraints: Not nullable, Maximum length: 3
`void`	`setInspSubsetUsageDcsnCode(String inspSubsetUsageDcsnCode)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSubsetUsageDcsnCodeGroup(String inspSubsetUsageDcsnCodeGroup)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSubsetUsageDcsnValuation(String inspSubsetUsageDcsnValuation)` Constraints: Not nullable, Maximum length: 1
`void`	`setLastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setLastChangedByUser(String lastChangedByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setLastChangeTime(LocalTime lastChangeTime)` Constraints: Not nullable, Precision: 0
`void`	`setMaterialSample(String materialSample)` Constraints: Not nullable, Maximum length: 12
`void`	`setSelectedCodeSet(String selectedCodeSet)` Constraints: Not nullable, Maximum length: 8
`void`	`setSelectedCodeSetPlant(String selectedCodeSetPlant)` Constraints: Not nullable, Maximum length: 4
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setShopFloorItem(Long shopFloorItem)` Constraints: none
`void`	`setTrigger_valuation_ac(Boolean trigger_valuation_ac)` Constraints: none
`protected Map<String,Object>`	`toMapOfFields()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties

Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait

- Field Detail
  - ALL_FIELDS
```
public static final InspectionSubsetSelectable ALL_FIELDS
```
    Selector for all available fields of InspectionSubset.
  - TRIGGER_VALUATION_AC
```
public static final InspectionSubsetField<Boolean> TRIGGER_VALUATION_AC
```
    Use with available fluent helpers to apply the Trigger_valuation_ac field to query operations.
  - INSPECTION_LOT
```
public static final InspectionSubsetField<String> INSPECTION_LOT
```
    Use with available fluent helpers to apply the InspectionLot field to query operations.
  - INSP_PLAN_OPERATION_INTERNAL_ID
```
public static final InspectionSubsetField<String> INSP_PLAN_OPERATION_INTERNAL_ID
```
    Use with available fluent helpers to apply the InspPlanOperationInternalID field to query operations.
  - INSPECTION_SUBSET_INTERNAL_ID
```
public static final InspectionSubsetField<String> INSPECTION_SUBSET_INTERNAL_ID
```
    Use with available fluent helpers to apply the InspectionSubsetInternalID field to query operations.
  - MATERIAL_SAMPLE
```
public static final InspectionSubsetField<String> MATERIAL_SAMPLE
```
    Use with available fluent helpers to apply the MaterialSample field to query operations.
  - EQUIPMENT
```
public static final InspectionSubsetField<String> EQUIPMENT
```
    Use with available fluent helpers to apply the Equipment field to query operations.
  - FUNCTIONAL_LOCATION
```
public static final InspectionSubsetField<String> FUNCTIONAL_LOCATION
```
    Use with available fluent helpers to apply the FunctionalLocation field to query operations.
  - SHOP_FLOOR_ITEM
```
public static final InspectionSubsetField<Long> SHOP_FLOOR_ITEM
```
    Use with available fluent helpers to apply the ShopFloorItem field to query operations.
  - SELECTED_CODE_SET_PLANT
```
public static final InspectionSubsetField<String> SELECTED_CODE_SET_PLANT
```
    Use with available fluent helpers to apply the SelectedCodeSetPlant field to query operations.
  - SELECTED_CODE_SET
```
public static final InspectionSubsetField<String> SELECTED_CODE_SET
```
    Use with available fluent helpers to apply the SelectedCodeSet field to query operations.
  - INSP_SUBSET_USAGE_DCSN_CODE_GROUP
```
public static final InspectionSubsetField<String> INSP_SUBSET_USAGE_DCSN_CODE_GROUP
```
    Use with available fluent helpers to apply the InspSubsetUsageDcsnCodeGroup field to query operations.
  - INSP_SUBSET_USAGE_DCSN_CODE
```
public static final InspectionSubsetField<String> INSP_SUBSET_USAGE_DCSN_CODE
```
    Use with available fluent helpers to apply the InspSubsetUsageDcsnCode field to query operations.
  - INSP_SUBSET_USAGE_DCSN_VALUATION
```
public static final InspectionSubsetField<String> INSP_SUBSET_USAGE_DCSN_VALUATION
```
    Use with available fluent helpers to apply the InspSubsetUsageDcsnValuation field to query operations.
  - INSPECTION_SUBSET_TIME
```
public static final InspectionSubsetField<LocalTime> INSPECTION_SUBSET_TIME
```
    Use with available fluent helpers to apply the InspectionSubsetTime field to query operations.
  - INSPECTION_SUBSET_DATE
```
public static final InspectionSubsetField<LocalDateTime> INSPECTION_SUBSET_DATE
```
    Use with available fluent helpers to apply the InspectionSubsetDate field to query operations.
  - INSP_SUBSET_LONG_NUMERIC_KEY
```
public static final InspectionSubsetField<String> INSP_SUBSET_LONG_NUMERIC_KEY
```
    Use with available fluent helpers to apply the InspSubsetLongNumericKey field to query operations.
  - INSP_SUBSET_SHORT_NUMERIC_KEY
```
public static final InspectionSubsetField<String> INSP_SUBSET_SHORT_NUMERIC_KEY
```
    Use with available fluent helpers to apply the InspSubsetShortNumericKey field to query operations.
  - INSPECTION_SUBSET_LONG_CHAR_KEY
```
public static final InspectionSubsetField<String> INSPECTION_SUBSET_LONG_CHAR_KEY
```
    Use with available fluent helpers to apply the InspectionSubsetLongCharKey field to query operations.
  - INSPECTION_SUBSET_SHORT_CHAR_KEY
```
public static final InspectionSubsetField<String> INSPECTION_SUBSET_SHORT_CHAR_KEY
```
    Use with available fluent helpers to apply the InspectionSubsetShortCharKey field to query operations.
  - INSPECTION_PARTIAL_LOT
```
public static final InspectionSubsetField<String> INSPECTION_PARTIAL_LOT
```
    Use with available fluent helpers to apply the InspectionPartialLot field to query operations.
  - INSPECTOR
```
public static final InspectionSubsetField<String> INSPECTOR
```
    Use with available fluent helpers to apply the Inspector field to query operations.
  - INSPECTION_SUBSET_YIELD_QTY
```
public static final InspectionSubsetField<BigDecimal> INSPECTION_SUBSET_YIELD_QTY
```
    Use with available fluent helpers to apply the InspectionSubsetYieldQty field to query operations.
  - INSPECTION_SUBSET_SCRAP_QTY
```
public static final InspectionSubsetField<BigDecimal> INSPECTION_SUBSET_SCRAP_QTY
```
    Use with available fluent helpers to apply the InspectionSubsetScrapQty field to query operations.
  - INSPECTION_SUBSET_REWORK_QTY
```
public static final InspectionSubsetField<BigDecimal> INSPECTION_SUBSET_REWORK_QTY
```
    Use with available fluent helpers to apply the InspectionSubsetReworkQty field to query operations.
  - INSPECTION_SUBSET_QTY_UNIT
```
public static final InspectionSubsetField<String> INSPECTION_SUBSET_QTY_UNIT
```
    Use with available fluent helpers to apply the InspectionSubsetQtyUnit field to query operations.
  - INSP_SBST_FUNCNL_LOC_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_FUNCNL_LOC_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstFuncnlLocProperty field to query operations.
  - INSP_SBST_EQUIP_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_EQUIP_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstEquipProperty field to query operations.
  - INSP_SBST_MATL_SMPL_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_MATL_SMPL_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstMatlSmplProperty field to query operations.
  - INSPECTION_SUBSET_SORT_KEY
```
public static final InspectionSubsetField<String> INSPECTION_SUBSET_SORT_KEY
```
    Use with available fluent helpers to apply the InspectionSubsetSortKey field to query operations.
  - INSP_SBST_DATE_FLD_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_DATE_FLD_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstDateFldProperty field to query operations.
  - INSP_SBST_LONG_NMBR_FLD_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_LONG_NMBR_FLD_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstLongNmbrFldProperty field to query operations.
  - INSP_SBST_SHRT_NMBR_FLD_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_SHRT_NMBR_FLD_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstShrtNmbrFldProperty field to query operations.
  - INSP_SBST_LONG_TXT_FLD_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_LONG_TXT_FLD_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstLongTxtFldProperty field to query operations.
  - INSP_SBST_TIME_FLD_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_TIME_FLD_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstTimeFldProperty field to query operations.
  - INSP_SBST_SHRT_TXT_FLD_PROPERTY
```
public static final InspectionSubsetField<String> INSP_SBST_SHRT_TXT_FLD_PROPERTY
```
    Use with available fluent helpers to apply the InspSbstShrtTxtFldProperty field to query operations.
  - CREATED_BY_USER
```
public static final InspectionSubsetField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - CREATION_DATE
```
public static final InspectionSubsetField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATION_TIME
```
public static final InspectionSubsetField<LocalTime> CREATION_TIME
```
    Use with available fluent helpers to apply the CreationTime field to query operations.
  - LAST_CHANGED_BY_USER
```
public static final InspectionSubsetField<String> LAST_CHANGED_BY_USER
```
    Use with available fluent helpers to apply the LastChangedByUser field to query operations.
  - LAST_CHANGE_DATE
```
public static final InspectionSubsetField<LocalDateTime> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - LAST_CHANGE_TIME
```
public static final InspectionSubsetField<LocalTime> LAST_CHANGE_TIME
```
    Use with available fluent helpers to apply the LastChangeTime field to query operations.
  - CHANGED_DATE_TIME
```
public static final InspectionSubsetField<ZonedDateTime> CHANGED_DATE_TIME
```
    Use with available fluent helpers to apply the ChangedDateTime field to query operations.
- Constructor Detail
  - InspectionSubset
```
public InspectionSubset()
```
  - InspectionSubset
```
public InspectionSubset(@Nullable
                        Boolean trigger_valuation_ac,
                        @Nullable
                        String inspectionLot,
                        @Nullable
                        String inspPlanOperationInternalID,
                        @Nullable
                        String inspectionSubsetInternalID,
                        @Nullable
                        String materialSample,
                        @Nullable
                        String equipment,
                        @Nullable
                        String functionalLocation,
                        @Nullable
                        Long shopFloorItem,
                        @Nullable
                        String selectedCodeSetPlant,
                        @Nullable
                        String selectedCodeSet,
                        @Nullable
                        String inspSubsetUsageDcsnCodeGroup,
                        @Nullable
                        String inspSubsetUsageDcsnCode,
                        @Nullable
                        String inspSubsetUsageDcsnValuation,
                        @Nullable
                        LocalTime inspectionSubsetTime,
                        @Nullable
                        LocalDateTime inspectionSubsetDate,
                        @Nullable
                        String inspSubsetLongNumericKey,
                        @Nullable
                        String inspSubsetShortNumericKey,
                        @Nullable
                        String inspectionSubsetLongCharKey,
                        @Nullable
                        String inspectionSubsetShortCharKey,
                        @Nullable
                        String inspectionPartialLot,
                        @Nullable
                        String inspector,
                        @Nullable
                        BigDecimal inspectionSubsetYieldQty,
                        @Nullable
                        BigDecimal inspectionSubsetScrapQty,
                        @Nullable
                        BigDecimal inspectionSubsetReworkQty,
                        @Nullable
                        String inspectionSubsetQtyUnit,
                        @Nullable
                        String inspSbstFuncnlLocProperty,
                        @Nullable
                        String inspSbstEquipProperty,
                        @Nullable
                        String inspSbstMatlSmplProperty,
                        @Nullable
                        String inspectionSubsetSortKey,
                        @Nullable
                        String inspSbstDateFldProperty,
                        @Nullable
                        String inspSbstLongNmbrFldProperty,
                        @Nullable
                        String inspSbstShrtNmbrFldProperty,
                        @Nullable
                        String inspSbstLongTxtFldProperty,
                        @Nullable
                        String inspSbstTimeFldProperty,
                        @Nullable
                        String inspSbstShrtTxtFldProperty,
                        @Nullable
                        String createdByUser,
                        @Nullable
                        LocalDateTime creationDate,
                        @Nullable
                        LocalTime creationTime,
                        @Nullable
                        String lastChangedByUser,
                        @Nullable
                        LocalDateTime lastChangeDate,
                        @Nullable
                        LocalTime lastChangeTime,
                        @Nullable
                        ZonedDateTime changedDateTime)
```
- Method Detail
  - getType
```
@Nonnull
public Class<InspectionSubset> getType()
```
    Specified by:
    
    getType in class VdmObject<InspectionSubset>
    
    Returns:
    
    The class of this object.
  - setTrigger_valuation_ac
```
public void setTrigger_valuation_ac(@Nullable
                                    Boolean trigger_valuation_ac)
```
    Constraints: none
    Original property name from the Odata EDM: Trigger_valuation_ac
    
    Parameters:
    
    trigger_valuation_ac - Dynamic Action Property
  - setInspectionLot
```
public void setInspectionLot(@Nullable
                             String inspectionLot)
```
    (Key Field) Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: InspectionLot
    
    The inspection lot number is assigned by the system.
    
    Parameters:
    
    inspectionLot - Number that uniquely identifies an inspection lot.
  - setInspPlanOperationInternalID
```
public void setInspPlanOperationInternalID(@Nullable
                                           String inspPlanOperationInternalID)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspPlanOperationInternalID
    
    Parameters:
    
    inspPlanOperationInternalID - Current Node Number from Order Counter
  - setInspectionSubsetInternalID
```
public void setInspectionSubsetInternalID(@Nullable
                                          String inspectionSubsetInternalID)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionSubsetInternalID
    
    Parameters:
    
    inspectionSubsetInternalID - The sample number is copied to this field from results recording. The inspection results are referenced via this number.
  - setMaterialSample
```
public void setMaterialSample(@Nullable
                              String materialSample)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: MaterialSample
    
    Parameters:
    
    materialSample - Unique, client-wide identifier for a sample.
  - setEquipment
```
public void setEquipment(@Nullable
                         String equipment)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: Equipment
    
    Parameters:
    
    equipment - Number by which a piece of equipment can be clearly identified.
  - setFunctionalLocation
```
public void setFunctionalLocation(@Nullable
                                  String functionalLocation)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: FunctionalLocation
    
    If alternative labels exist for a functional location, you can define in your user profile which label should be displayed in this field.
    
    Parameters:
    
    functionalLocation - Label that uniquely identifies a functional location.
  - setShopFloorItem
```
public void setShopFloorItem(@Nullable
                             Long shopFloorItem)
```
    Constraints: none
    Original property name from the Odata EDM: ShopFloorItem
    
    Parameters:
    
    shopFloorItem - ID of Serialized Material
  - setSelectedCodeSetPlant
```
public void setSelectedCodeSetPlant(@Nullable
                                    String selectedCodeSetPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SelectedCodeSetPlant
    
    Parameters:
    
    selectedCodeSetPlant - Key uniquely identifying a plant.
  - setSelectedCodeSet
```
public void setSelectedCodeSet(@Nullable
                               String selectedCodeSet)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SelectedCodeSet
    
    Parameters:
    
    selectedCodeSet - Selected set of the usage decision.
  - setInspSubsetUsageDcsnCodeGroup
```
public void setInspSubsetUsageDcsnCodeGroup(@Nullable
                                            String inspSubsetUsageDcsnCodeGroup)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSubsetUsageDcsnCodeGroup
    
    Parameters:
    
    inspSubsetUsageDcsnCodeGroup - Code group of the usage decision.
  - setInspSubsetUsageDcsnCode
```
public void setInspSubsetUsageDcsnCode(@Nullable
                                       String inspSubsetUsageDcsnCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSubsetUsageDcsnCode
    
    Parameters:
    
    inspSubsetUsageDcsnCode - Code of the usage decision.
  - setInspSubsetUsageDcsnValuation
```
public void setInspSubsetUsageDcsnValuation(@Nullable
                                            String inspSubsetUsageDcsnValuation)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSubsetUsageDcsnValuation
    
    Parameters:
    
    inspSubsetUsageDcsnValuation - Specifies the valuation of a code from the inspection catalog.
  - setInspectionSubsetTime
```
public void setInspectionSubsetTime(@Nullable
                                    LocalTime inspectionSubsetTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InspectionSubsetTime
    
    Parameters:
    
    inspectionSubsetTime - User Field for Time
  - setInspectionSubsetDate
```
public void setInspectionSubsetDate(@Nullable
                                    LocalDateTime inspectionSubsetDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InspectionSubsetDate
    
    Parameters:
    
    inspectionSubsetDate - User Field for Date
  - setInspSubsetLongNumericKey
```
public void setInspSubsetLongNumericKey(@Nullable
                                        String inspSubsetLongNumericKey)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspSubsetLongNumericKey
    
    Parameters:
    
    inspSubsetLongNumericKey - User Field for 10 Digits
  - setInspSubsetShortNumericKey
```
public void setInspSubsetShortNumericKey(@Nullable
                                         String inspSubsetShortNumericKey)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspSubsetShortNumericKey
    
    Parameters:
    
    inspSubsetShortNumericKey - User Field for 3 Digits
  - setInspectionSubsetLongCharKey
```
public void setInspectionSubsetLongCharKey(@Nullable
                                           String inspectionSubsetLongCharKey)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: InspectionSubsetLongCharKey
    
    Parameters:
    
    inspectionSubsetLongCharKey - User Field for 18 Characters
  - setInspectionSubsetShortCharKey
```
public void setInspectionSubsetShortCharKey(@Nullable
                                            String inspectionSubsetShortCharKey)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspectionSubsetShortCharKey
    
    Parameters:
    
    inspectionSubsetShortCharKey - User Field for 10 Characters
  - setInspectionPartialLot
```
public void setInspectionPartialLot(@Nullable
                                    String inspectionPartialLot)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionPartialLot
    
    You can process partial lots by:Inspecting during production using inspection pointsRunning a batch split for the delivery note
    
    Parameters:
    
    inspectionPartialLot - The partial lot's number, which is only unique within the corresponding inspection lot.
  - setInspector
```
public void setInspector(@Nullable
                         String inspector)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: Inspector
    
    The system does not check the entries made.
    
    Parameters:
    
    inspector - The system enters the name of the user as the name of the inspector, if no other entry is made.
  - setInspectionSubsetYieldQty
```
public void setInspectionSubsetYieldQty(@Nullable
                                        BigDecimal inspectionSubsetYieldQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetYieldQty
    
    A quantity proposal is possible if the following conditions are fulfilled:Quantity-based inspection intervals are defined at operation level in the task list.The indicator for the proposal of activities is marked for the current order type in the order confirmation parameters.When you record the inspection point identifier for an order number for the first time, the planned interval quantity is proposed.In the case of an inspection point identifier, where a quantity was already recorded in an earlier operation, the last quantity recorded is proposed.
    
    Parameters:
    
    inspectionSubsetYieldQty - Indicates the yield produced since the last inspection and, if necessary, confirmed for the operation.
  - setInspectionSubsetScrapQty
```
public void setInspectionSubsetScrapQty(@Nullable
                                        BigDecimal inspectionSubsetScrapQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetScrapQty
    
    Parameters:
    
    inspectionSubsetScrapQty - Indicates the amount of scrap produced since the last inspection and which may be confirmed for the operation.
  - setInspectionSubsetReworkQty
```
public void setInspectionSubsetReworkQty(@Nullable
                                         BigDecimal inspectionSubsetReworkQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetReworkQty
    
    Enter the rework quantity that has accumulated since the last inspection.Depending on the confirmation indicator, this quantity is confirmed to the PP operation.If the rework quantity is simultaneously confirmed for PP, it can have the following effects:When you include a reference operation set in the current order from the confirmation (by means of trigger points),the rework quantity is adopted as the operation quantity for the rework operations.When you create a new order from the confirmation by means of trigger points, the rework quantity is adopted as the order quantity for the rework order.
    
    Parameters:
    
    inspectionSubsetReworkQty - Indicates the quantity to be reworked as a result of poor workmanship or insufficient quality.
  - setInspectionSubsetQtyUnit
```
public void setInspectionSubsetQtyUnit(@Nullable
                                       String inspectionSubsetQtyUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspectionSubsetQtyUnit
    
    The unit of measure applies to the yield, the scrap quantity and/or the rework quantity.
    
    Parameters:
    
    inspectionSubsetQtyUnit - Unit used for the inspection point quantity within QM.
  - setInspSbstFuncnlLocProperty
```
public void setInspSbstFuncnlLocProperty(@Nullable
                                         String inspSbstFuncnlLocProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstFuncnlLocProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstFuncnlLocProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstEquipProperty
```
public void setInspSbstEquipProperty(@Nullable
                                     String inspSbstEquipProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstEquipProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstEquipProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstMatlSmplProperty
```
public void setInspSbstMatlSmplProperty(@Nullable
                                        String inspSbstMatlSmplProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstMatlSmplProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstMatlSmplProperty - An identification field is only active if you have made an entry in this field.
  - setInspectionSubsetSortKey
```
public void setInspectionSubsetSortKey(@Nullable
                                       String inspectionSubsetSortKey)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: InspectionSubsetSortKey
    
    Parameters:
    
    inspectionSubsetSortKey - Used to identify an inspection point.
  - setInspSbstDateFldProperty
```
public void setInspSbstDateFldProperty(@Nullable
                                       String inspSbstDateFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstDateFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstDateFldProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstLongNmbrFldProperty
```
public void setInspSbstLongNmbrFldProperty(@Nullable
                                           String inspSbstLongNmbrFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstLongNmbrFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstLongNmbrFldProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstShrtNmbrFldProperty
```
public void setInspSbstShrtNmbrFldProperty(@Nullable
                                           String inspSbstShrtNmbrFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstShrtNmbrFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstShrtNmbrFldProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstLongTxtFldProperty
```
public void setInspSbstLongTxtFldProperty(@Nullable
                                          String inspSbstLongTxtFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstLongTxtFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstLongTxtFldProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstTimeFldProperty
```
public void setInspSbstTimeFldProperty(@Nullable
                                       String inspSbstTimeFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstTimeFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstTimeFldProperty - An identification field is only active if you have made an entry in this field.
  - setInspSbstShrtTxtFldProperty
```
public void setInspSbstShrtTxtFldProperty(@Nullable
                                          String inspSbstShrtTxtFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstShrtTxtFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Parameters:
    
    inspSbstShrtTxtFldProperty - An identification field is only active if you have made an entry in this field.
  - setCreatedByUser
```
public void setCreatedByUser(@Nullable
                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Parameters:
    
    createdByUser - Name of Person Who Created Object
  - setCreationDate
```
public void setCreationDate(@Nullable
                            LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Parameters:
    
    creationDate - Date on Which Record Was Created
  - setCreationTime
```
public void setCreationTime(@Nullable
                            LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Parameters:
    
    creationTime - Time at Which Data Record Was Created
  - setLastChangedByUser
```
public void setLastChangedByUser(@Nullable
                                 String lastChangedByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: LastChangedByUser
    
    Parameters:
    
    lastChangedByUser - Name of Person who Changed Object
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Parameters:
    
    lastChangeDate - Date of Last Change
  - setLastChangeTime
```
public void setLastChangeTime(@Nullable
                              LocalTime lastChangeTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeTime
    
    Parameters:
    
    lastChangeTime - Time at Which Data Record Was Changed
  - setChangedDateTime
```
public void setChangedDateTime(@Nullable
                               ZonedDateTime changedDateTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ChangedDateTime
    
    To standardize local times in a UTC time stamp and thus make them comparable with other times, these local times need to be converted using your time zone and the ABAP command convert.Even if the system is able to determine the time zone from Customizing or master data, you shoul save the time zone redundantly here.The internal structure of the UTC time stamp is subdivided into a date part and a time part in packed number format . You can also use the high resolution UTC time stamp (10^-7 seconds).
    
    Parameters:
    
    changedDateTime - The UTC time stamp is the date and time relative to UTC (Universal Coordinated Time).
  - getEntityCollection
```
protected String getEntityCollection()
```
    Specified by:
    
    getEntityCollection in class VdmEntity<InspectionSubset>
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<InspectionSubset>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<InspectionSubset>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<InspectionSubset>
  - field
```
@Nonnull
public static <T> InspectionSubsetField<T> field(@Nonnull
                                                          String fieldName,
                                                          @Nonnull
                                                          Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    Parameters:
    
    fieldName - The name of the extension field as returned by the OData service.
    
    fieldType - The Java type to use for the extension field when performing value comparisons.
    
    Returns:
    
    A representation of an extension field from this entity.
  - field
```
@Nonnull
public static <T,DomainT> InspectionSubsetField<T> field(@Nonnull
                                                                  String fieldName,
                                                                  @Nonnull
                                                                  TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getDestinationForFetch
```
@Nullable
public HttpDestinationProperties getDestinationForFetch()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same destination with multiple queries (e.g. fetching associated entities). New destination to apply to this entity
    
    Overrides:
    
    getDestinationForFetch in class VdmEntity<InspectionSubset>
    
    Returns:
    
    The stored destination for executing queries, or null if no such context has been set.
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<InspectionSubset>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nonnull
                            HttpDestinationProperties destination)
```
    Description copied from class: VdmEntity
    
    Sets the service path and destination for the fetch commands of this entity. Also applies to any associated entities (navigation properties) that were previously fetched.
    Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    attachToService in class VdmEntity<InspectionSubset>
    
    Parameters:
    
    servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the service path has never been set, then the service path will be set to the default defined in the corresponding service interface.
    
    destination - New destination to apply to this entity and any associated entities that were previously fetched.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Overrides:
    
    getDefaultServicePath in class VdmEntity<InspectionSubset>
  - builder
```
public static InspectionSubset.InspectionSubsetBuilder builder()
```
  - getTrigger_valuation_ac
```
@Nullable
public Boolean getTrigger_valuation_ac()
```
    Constraints: none
    Original property name from the Odata EDM: Trigger_valuation_ac
    
    Returns:
    
    Dynamic Action Property
  - getInspectionLot
```
@Nullable
public String getInspectionLot()
```
    (Key Field) Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: InspectionLot
    
    The inspection lot number is assigned by the system.
    
    Returns:
    
    Number that uniquely identifies an inspection lot.
  - getInspPlanOperationInternalID
```
@Nullable
public String getInspPlanOperationInternalID()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspPlanOperationInternalID
    
    Returns:
    
    Current Node Number from Order Counter
  - getInspectionSubsetInternalID
```
@Nullable
public String getInspectionSubsetInternalID()
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionSubsetInternalID
    
    Returns:
    
    The sample number is copied to this field from results recording. The inspection results are referenced via this number.
  - getMaterialSample
```
@Nullable
public String getMaterialSample()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: MaterialSample
    
    Returns:
    
    Unique, client-wide identifier for a sample.
  - getEquipment
```
@Nullable
public String getEquipment()
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: Equipment
    
    Returns:
    
    Number by which a piece of equipment can be clearly identified.
  - getFunctionalLocation
```
@Nullable
public String getFunctionalLocation()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: FunctionalLocation
    
    If alternative labels exist for a functional location, you can define in your user profile which label should be displayed in this field.
    
    Returns:
    
    Label that uniquely identifies a functional location.
  - getShopFloorItem
```
@Nullable
public Long getShopFloorItem()
```
    Constraints: none
    Original property name from the Odata EDM: ShopFloorItem
    
    Returns:
    
    ID of Serialized Material
  - getSelectedCodeSetPlant
```
@Nullable
public String getSelectedCodeSetPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SelectedCodeSetPlant
    
    Returns:
    
    Key uniquely identifying a plant.
  - getSelectedCodeSet
```
@Nullable
public String getSelectedCodeSet()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SelectedCodeSet
    
    Returns:
    
    Selected set of the usage decision.
  - getInspSubsetUsageDcsnCodeGroup
```
@Nullable
public String getInspSubsetUsageDcsnCodeGroup()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSubsetUsageDcsnCodeGroup
    
    Returns:
    
    Code group of the usage decision.
  - getInspSubsetUsageDcsnCode
```
@Nullable
public String getInspSubsetUsageDcsnCode()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSubsetUsageDcsnCode
    
    Returns:
    
    Code of the usage decision.
  - getInspSubsetUsageDcsnValuation
```
@Nullable
public String getInspSubsetUsageDcsnValuation()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSubsetUsageDcsnValuation
    
    Returns:
    
    Specifies the valuation of a code from the inspection catalog.
  - getInspectionSubsetTime
```
@Nullable
public LocalTime getInspectionSubsetTime()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InspectionSubsetTime
    
    Returns:
    
    User Field for Time
  - getInspectionSubsetDate
```
@Nullable
public LocalDateTime getInspectionSubsetDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InspectionSubsetDate
    
    Returns:
    
    User Field for Date
  - getInspSubsetLongNumericKey
```
@Nullable
public String getInspSubsetLongNumericKey()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspSubsetLongNumericKey
    
    Returns:
    
    User Field for 10 Digits
  - getInspSubsetShortNumericKey
```
@Nullable
public String getInspSubsetShortNumericKey()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspSubsetShortNumericKey
    
    Returns:
    
    User Field for 3 Digits
  - getInspectionSubsetLongCharKey
```
@Nullable
public String getInspectionSubsetLongCharKey()
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: InspectionSubsetLongCharKey
    
    Returns:
    
    User Field for 18 Characters
  - getInspectionSubsetShortCharKey
```
@Nullable
public String getInspectionSubsetShortCharKey()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspectionSubsetShortCharKey
    
    Returns:
    
    User Field for 10 Characters
  - getInspectionPartialLot
```
@Nullable
public String getInspectionPartialLot()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionPartialLot
    
    You can process partial lots by:Inspecting during production using inspection pointsRunning a batch split for the delivery note
    
    Returns:
    
    The partial lot's number, which is only unique within the corresponding inspection lot.
  - getInspector
```
@Nullable
public String getInspector()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: Inspector
    
    The system does not check the entries made.
    
    Returns:
    
    The system enters the name of the user as the name of the inspector, if no other entry is made.
  - getInspectionSubsetYieldQty
```
@Nullable
public BigDecimal getInspectionSubsetYieldQty()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetYieldQty
    
    A quantity proposal is possible if the following conditions are fulfilled:Quantity-based inspection intervals are defined at operation level in the task list.The indicator for the proposal of activities is marked for the current order type in the order confirmation parameters.When you record the inspection point identifier for an order number for the first time, the planned interval quantity is proposed.In the case of an inspection point identifier, where a quantity was already recorded in an earlier operation, the last quantity recorded is proposed.
    
    Returns:
    
    Indicates the yield produced since the last inspection and, if necessary, confirmed for the operation.
  - getInspectionSubsetScrapQty
```
@Nullable
public BigDecimal getInspectionSubsetScrapQty()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetScrapQty
    
    Returns:
    
    Indicates the amount of scrap produced since the last inspection and which may be confirmed for the operation.
  - getInspectionSubsetReworkQty
```
@Nullable
public BigDecimal getInspectionSubsetReworkQty()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetReworkQty
    
    Enter the rework quantity that has accumulated since the last inspection.Depending on the confirmation indicator, this quantity is confirmed to the PP operation.If the rework quantity is simultaneously confirmed for PP, it can have the following effects:When you include a reference operation set in the current order from the confirmation (by means of trigger points),the rework quantity is adopted as the operation quantity for the rework operations.When you create a new order from the confirmation by means of trigger points, the rework quantity is adopted as the order quantity for the rework order.
    
    Returns:
    
    Indicates the quantity to be reworked as a result of poor workmanship or insufficient quality.
  - getInspectionSubsetQtyUnit
```
@Nullable
public String getInspectionSubsetQtyUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspectionSubsetQtyUnit
    
    The unit of measure applies to the yield, the scrap quantity and/or the rework quantity.
    
    Returns:
    
    Unit used for the inspection point quantity within QM.
  - getInspSbstFuncnlLocProperty
```
@Nullable
public String getInspSbstFuncnlLocProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstFuncnlLocProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstEquipProperty
```
@Nullable
public String getInspSbstEquipProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstEquipProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstMatlSmplProperty
```
@Nullable
public String getInspSbstMatlSmplProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstMatlSmplProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspectionSubsetSortKey
```
@Nullable
public String getInspectionSubsetSortKey()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: InspectionSubsetSortKey
    
    Returns:
    
    Used to identify an inspection point.
  - getInspSbstDateFldProperty
```
@Nullable
public String getInspSbstDateFldProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstDateFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstLongNmbrFldProperty
```
@Nullable
public String getInspSbstLongNmbrFldProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstLongNmbrFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstShrtNmbrFldProperty
```
@Nullable
public String getInspSbstShrtNmbrFldProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstShrtNmbrFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstLongTxtFldProperty
```
@Nullable
public String getInspSbstLongTxtFldProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstLongTxtFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstTimeFldProperty
```
@Nullable
public String getInspSbstTimeFldProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstTimeFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getInspSbstShrtTxtFldProperty
```
@Nullable
public String getInspSbstShrtTxtFldProperty()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstShrtTxtFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    An identification field is only active if you have made an entry in this field.
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    Name of Person Who Created Object
  - getCreationDate
```
@Nullable
public LocalDateTime getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    Date on Which Record Was Created
  - getCreationTime
```
@Nullable
public LocalTime getCreationTime()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Returns:
    
    Time at Which Data Record Was Created
  - getLastChangedByUser
```
@Nullable
public String getLastChangedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: LastChangedByUser
    
    Returns:
    
    Name of Person who Changed Object
  - getLastChangeDate
```
@Nullable
public LocalDateTime getLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Returns:
    
    Date of Last Change
  - getLastChangeTime
```
@Nullable
public LocalTime getLastChangeTime()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeTime
    
    Returns:
    
    Time at Which Data Record Was Changed
  - getChangedDateTime
```
@Nullable
public ZonedDateTime getChangedDateTime()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ChangedDateTime
    
    To standardize local times in a UTC time stamp and thus make them comparable with other times, these local times need to be converted using your time zone and the ABAP command convert.Even if the system is able to determine the time zone from Customizing or master data, you shoul save the time zone redundantly here.The internal structure of the UTC time stamp is subdivided into a date part and a time part in packed number format . You can also use the high resolution UTC time stamp (10^-7 seconds).
    
    Returns:
    
    The UTC time stamp is the date and time relative to UTC (Universal Coordinated Time).
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<InspectionSubset>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<InspectionSubset>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<InspectionSubset>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<InspectionSubset>

Class InspectionSubset

Nested Class Summary

Field Summary

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

TRIGGER_VALUATION_AC

INSPECTION_LOT

INSP_PLAN_OPERATION_INTERNAL_ID

INSPECTION_SUBSET_INTERNAL_ID

MATERIAL_SAMPLE

EQUIPMENT

FUNCTIONAL_LOCATION

SHOP_FLOOR_ITEM

SELECTED_CODE_SET_PLANT

SELECTED_CODE_SET

INSP_SUBSET_USAGE_DCSN_CODE_GROUP

INSP_SUBSET_USAGE_DCSN_CODE

INSP_SUBSET_USAGE_DCSN_VALUATION

INSPECTION_SUBSET_TIME

INSPECTION_SUBSET_DATE

INSP_SUBSET_LONG_NUMERIC_KEY

INSP_SUBSET_SHORT_NUMERIC_KEY

INSPECTION_SUBSET_LONG_CHAR_KEY

INSPECTION_SUBSET_SHORT_CHAR_KEY

INSPECTION_PARTIAL_LOT

INSPECTOR

INSPECTION_SUBSET_YIELD_QTY

INSPECTION_SUBSET_SCRAP_QTY

INSPECTION_SUBSET_REWORK_QTY

INSPECTION_SUBSET_QTY_UNIT

INSP_SBST_FUNCNL_LOC_PROPERTY

INSP_SBST_EQUIP_PROPERTY

INSP_SBST_MATL_SMPL_PROPERTY

INSPECTION_SUBSET_SORT_KEY

INSP_SBST_DATE_FLD_PROPERTY

INSP_SBST_LONG_NMBR_FLD_PROPERTY

INSP_SBST_SHRT_NMBR_FLD_PROPERTY

INSP_SBST_LONG_TXT_FLD_PROPERTY

INSP_SBST_TIME_FLD_PROPERTY

INSP_SBST_SHRT_TXT_FLD_PROPERTY

CREATED_BY_USER

CREATION_DATE

CREATION_TIME

LAST_CHANGED_BY_USER

LAST_CHANGE_DATE

LAST_CHANGE_TIME

CHANGED_DATE_TIME

Constructor Detail

InspectionSubset

InspectionSubset

Method Detail

getType

setTrigger_valuation_ac

setInspectionLot

setInspPlanOperationInternalID

setInspectionSubsetInternalID

setMaterialSample

setEquipment

setFunctionalLocation

setShopFloorItem

setSelectedCodeSetPlant

setSelectedCodeSet

setInspSubsetUsageDcsnCodeGroup

setInspSubsetUsageDcsnCode

setInspSubsetUsageDcsnValuation

setInspectionSubsetTime

setInspectionSubsetDate

setInspSubsetLongNumericKey

setInspSubsetShortNumericKey

setInspectionSubsetLongCharKey

setInspectionSubsetShortCharKey

setInspectionPartialLot

setInspector

setInspectionSubsetYieldQty