InspPlanOpCharacteristic (SAP Cloud SDK

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

```
public class InspPlanOpCharacteristic
extends VdmEntity<InspPlanOpCharacteristic>
```
Insp Plan – Characteristic Version API

Original entity name from the Odata EDM: A_InspPlanOpCharacteristicType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static InspPlanOpCharacteristicSelectable`	`ALL_FIELDS` Selector for all available fields of InspPlanOpCharacteristic.
`static InspPlanOpCharacteristicField<String>`	`BILL_OF_OPERATIONS_VERSION` Use with available fluent helpers to apply the BillOfOperationsVersion field to query operations.
`static InspPlanOpCharacteristicField<String>`	`BOO_CHARACTERISTIC` Use with available fluent helpers to apply the BOOCharacteristic field to query operations.
`static InspPlanOpCharacteristicField<String>`	`BOO_CHARACTERISTIC_VERSION` Use with available fluent helpers to apply the BOOCharacteristicVersion field to query operations.
`static InspPlanOpCharacteristicField<Boolean>`	`BOO_CHARC_HAS_INSP_SPEC_REFERENCE` Use with available fluent helpers to apply the BOOCharcHasInspSpecReference field to query operations.
`static InspPlanOpCharacteristicField<BigDecimal>`	`BOO_CHARC_SAMPLE_QUANTITY` Use with available fluent helpers to apply the BOOCharcSampleQuantity field to query operations.
`static InspPlanOpCharacteristicField<String>`	`BOO_OP_INTERNAL_VERSION_COUNTER` Use with available fluent helpers to apply the BOOOpInternalVersionCounter field to query operations.
`static InspPlanOpCharacteristicField<String>`	`BOO_OPERATION_INTERNAL_ID` Use with available fluent helpers to apply the BOOOperationInternalID field to query operations.
`static InspPlanOpCharacteristicField<String>`	`BOO_OPERATION_PRT_INTERNAL_ID` Use with available fluent helpers to apply the BOOOperationPRTInternalID field to query operations.
`static InspPlanOpCharacteristicField<String>`	`CHANGE_NUMBER` Use with available fluent helpers to apply the ChangeNumber field to query operations.
`static InspPlanOpCharacteristicField<ZonedDateTime>`	`CHANGED_DATE_TIME` Use with available fluent helpers to apply the ChangedDateTime field to query operations.
`static InspPlanOpCharacteristicField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static InspPlanOpCharacteristicField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_CHARACTERISTIC_SAMPLE_UNIT` Use with available fluent helpers to apply the InspCharacteristicSampleUnit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_RESULT_IS_DOCUMENTATION_RQD` Use with available fluent helpers to apply the InspResultIsDocumentationRqd field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CATALOG2` Use with available fluent helpers to apply the InspSpecAdditionalCatalog2 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CATALOG3` Use with available fluent helpers to apply the InspSpecAdditionalCatalog3 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CATALOG4` Use with available fluent helpers to apply the InspSpecAdditionalCatalog4 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CATALOG5` Use with available fluent helpers to apply the InspSpecAdditionalCatalog5 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CODE_GROUP2` Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup2 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CODE_GROUP3` Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup3 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CODE_GROUP4` Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup4 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_CODE_GROUP5` Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup5 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_SELECTED_SET2` Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet2 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_SELECTED_SET3` Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet3 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_SELECTED_SET4` Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet4 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDITIONAL_SELECTED_SET5` Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet5 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDL_SELD_CODE_SET_PLANT2` Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant2 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDL_SELD_CODE_SET_PLANT3` Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant3 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDL_SELD_CODE_SET_PLANT4` Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant4 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_ADDL_SELD_CODE_SET_PLANT5` Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant5 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_CHARC_CATEGORY` Use with available fluent helpers to apply the InspSpecCharcCategory field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_CONTROL_INDICATORS` Use with available fluent helpers to apply the InspSpecControlIndicators field to query operations.
`static InspPlanOpCharacteristicField<Short>`	`INSP_SPEC_DECIMAL_PLACES` Use with available fluent helpers to apply the InspSpecDecimalPlaces field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_DEFECT_CODE_GRP_REJECTION` Use with available fluent helpers to apply the InspSpecDefectCodeGrpRejection field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER` Use with available fluent helpers to apply the InspSpecDefectCodeGrpRjcnLower field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER` Use with available fluent helpers to apply the InspSpecDefectCodeGrpRjcnUpper field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_DEFECT_CODE_REJECTION` Use with available fluent helpers to apply the InspSpecDefectCodeRejection field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_DEFECT_CODE_RJCN_LOWER` Use with available fluent helpers to apply the InspSpecDefectCodeRjcnLower field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_DEFECT_CODE_RJCN_UPPER` Use with available fluent helpers to apply the InspSpecDefectCodeRjcnUpper field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_HAS_FIXED_CTRL_INDICATORS` Use with available fluent helpers to apply the InspSpecHasFixedCtrlIndicators field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_HAS_LOWER_LIMIT` Use with available fluent helpers to apply the InspSpecHasLowerLimit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_HAS_TARGET_VALUE` Use with available fluent helpers to apply the InspSpecHasTargetValue field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_HAS_UPPER_LIMIT` Use with available fluent helpers to apply the InspSpecHasUpperLimit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IMPORTANCE_CODE` Use with available fluent helpers to apply the InspSpecImportanceCode field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_INFORMATION_FIELD1` Use with available fluent helpers to apply the InspSpecInformationField1 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_INFORMATION_FIELD2` Use with available fluent helpers to apply the InspSpecInformationField2 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_INFORMATION_FIELD3` Use with available fluent helpers to apply the InspSpecInformationField3 field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_CHG_DOC_REQUIRED` Use with available fluent helpers to apply the InspSpecIsChgDocRequired field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_CONTROL_CHART_USED` Use with available fluent helpers to apply the InspSpecIsControlChartUsed field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC` Use with available fluent helpers to apply the InspSpecIsDefectsRecgAutomatic field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_DESTRUCTIVE` Use with available fluent helpers to apply the InspSpecIsDestructive field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_LONG_TERM_INSPECTION` Use with available fluent helpers to apply the InspSpecIsLongTermInspection field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_LOWER_LIMIT_REQUIRED` Use with available fluent helpers to apply the InspSpecIsLowerLimitRequired field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_MEASURED_VALUE_RQD` Use with available fluent helpers to apply the InspSpecIsMeasuredValueRqd field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_QUANTITATIVE` Use with available fluent helpers to apply the InspSpecIsQuantitative field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE` Use with available fluent helpers to apply the InspSpecIsSampleQtyAdditive field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_SAMPLING_PROCED_RQD` Use with available fluent helpers to apply the InspSpecIsSamplingProcedRqd field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_SCRAP_RELEVANT` Use with available fluent helpers to apply the InspSpecIsScrapRelevant field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_SELECTED_SET_REQUIRED` Use with available fluent helpers to apply the InspSpecIsSelectedSetRequired field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT` Use with available fluent helpers to apply the InspSpecIsTargetValueInLimit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_TEST_EQUIPMENT_RQD` Use with available fluent helpers to apply the InspSpecIsTestEquipmentRqd field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_IS_UPPER_LIMIT_REQUIRED` Use with available fluent helpers to apply the InspSpecIsUpperLimitRequired field to query operations.
`static InspPlanOpCharacteristicField<Double>`	`INSP_SPEC_LOWER_LIMIT` Use with available fluent helpers to apply the InspSpecLowerLimit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_PRINT_CONTROL` Use with available fluent helpers to apply the InspSpecPrintControl field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_RECORDING_TYPE` Use with available fluent helpers to apply the InspSpecRecordingType field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_SPEC_RESULT_CALCULATION` Use with available fluent helpers to apply the InspSpecResultCalculation field to query operations.
`static InspPlanOpCharacteristicField<Double>`	`INSP_SPEC_TARGET_VALUE` Use with available fluent helpers to apply the InspSpecTargetValue field to query operations.
`static InspPlanOpCharacteristicField<Double>`	`INSP_SPEC_UPPER_LIMIT` Use with available fluent helpers to apply the InspSpecUpperLimit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSP_TOLERANCE_SPECIFICATION` Use with available fluent helpers to apply the InspToleranceSpecification field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_METHOD` Use with available fluent helpers to apply the InspectionMethod field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_METHOD_PLANT` Use with available fluent helpers to apply the InspectionMethodPlant field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_METHOD_VERSION` Use with available fluent helpers to apply the InspectionMethodVersion field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_PLAN` Use with available fluent helpers to apply the InspectionPlan field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_PLAN_GROUP` Use with available fluent helpers to apply the InspectionPlanGroup field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_PLAN_INTERNAL_VERSION` Use with available fluent helpers to apply the InspectionPlanInternalVersion field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_SCOPE` Use with available fluent helpers to apply the InspectionScope field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_SPECIFICATION` Use with available fluent helpers to apply the InspectionSpecification field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_SPECIFICATION_PLANT` Use with available fluent helpers to apply the InspectionSpecificationPlant field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_SPECIFICATION_TEXT` Use with available fluent helpers to apply the InspectionSpecificationText field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_SPECIFICATION_UNIT` Use with available fluent helpers to apply the InspectionSpecificationUnit field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTION_SPECIFICATION_VERSION` Use with available fluent helpers to apply the InspectionSpecificationVersion field to query operations.
`static InspPlanOpCharacteristicField<String>`	`INSPECTOR_QUALIFICATION` Use with available fluent helpers to apply the InspectorQualification field to query operations.
`static InspPlanOpCharacteristicField<Boolean>`	`IS_DELETED` Use with available fluent helpers to apply the IsDeleted field to query operations.
`static InspPlanOpCharacteristicField<LocalDateTime>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static InspPlanOpCharacteristicField<String>`	`LAST_CHANGED_BY_USER` Use with available fluent helpers to apply the LastChangedByUser field to query operations.
`static InspPlanOpCharacteristicField<String>`	`SAMPLING_PROCEDURE` Use with available fluent helpers to apply the SamplingProcedure field to query operations.
`static InspPlanOpCharacteristicField<String>`	`SELECTED_CODE_SET` Use with available fluent helpers to apply the SelectedCodeSet field to query operations.
`static InspPlanOpCharacteristicField<String>`	`SELECTED_CODE_SET_PLANT` Use with available fluent helpers to apply the SelectedCodeSetPlant field to query operations.
`static InspPlanOpCharacteristicField<LocalDateTime>`	`VALIDITY_END_DATE` Use with available fluent helpers to apply the ValidityEndDate field to query operations.
`static InspPlanOpCharacteristicField<LocalDateTime>`	`VALIDITY_START_DATE` Use with available fluent helpers to apply the ValidityStartDate field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`InspPlanOpCharacteristic()`
InspPlanOpCharacteristic(String inspectionPlanGroup, String bOOOperationInternalID, String bOOCharacteristic, String bOOCharacteristicVersion, String bOOOpInternalVersionCounter, String inspectionPlanInternalVersion, String inspectionPlan, LocalDateTime validityStartDate, LocalDateTime validityEndDate, String changeNumber, Boolean isDeleted, String bOOOperationPRTInternalID, String inspectionMethod, String inspectionMethodVersion, String inspectionMethodPlant, String inspSpecImportanceCode, String inspectorQualification, String inspectionSpecification, String inspectionSpecificationVersion, String inspectionSpecificationPlant, Boolean bOOCharcHasInspSpecReference, String inspSpecControlIndicators, String inspSpecIsQuantitative, String inspSpecIsMeasuredValueRqd, String inspSpecIsSelectedSetRequired, String inspSpecIsUpperLimitRequired, String inspSpecIsLowerLimitRequired, String inspSpecIsTargetValueInLimit, String inspectionScope, String inspSpecIsLongTermInspection, String inspSpecRecordingType, String inspResultIsDocumentationRqd, String inspSpecCharcCategory, String inspSpecIsSampleQtyAdditive, String inspSpecIsDestructive, String inspSpecResultCalculation, String inspSpecIsSamplingProcedRqd, String inspSpecIsScrapRelevant, String inspSpecHasFixedCtrlIndicators, String inspSpecIsTestEquipmentRqd, String inspSpecIsDefectsRecgAutomatic, String inspSpecIsChgDocRequired, String inspSpecIsControlChartUsed, String inspSpecPrintControl, String inspToleranceSpecification, Short inspSpecDecimalPlaces, String inspectionSpecificationUnit, Double inspSpecTargetValue, String inspSpecHasTargetValue, Double inspSpecUpperLimit, Double inspSpecLowerLimit, String inspSpecHasLowerLimit, String inspSpecHasUpperLimit, String inspSpecDefectCodeGrpRejection, String inspSpecDefectCodeRejection, String inspSpecDefectCodeGrpRjcnUpper, String inspSpecDefectCodeRjcnUpper, String inspSpecDefectCodeGrpRjcnLower, String inspSpecDefectCodeRjcnLower, String selectedCodeSet, String selectedCodeSetPlant, String inspSpecAdditionalCatalog2, String inspSpecAdditionalSelectedSet2, String inspSpecAdditionalCodeGroup2, String inspSpecAddlSeldCodeSetPlant2, String inspSpecAdditionalCatalog3, String inspSpecAdditionalSelectedSet3, String inspSpecAdditionalCodeGroup3, String inspSpecAddlSeldCodeSetPlant3, String inspSpecAdditionalCatalog4, String inspSpecAdditionalSelectedSet4, String inspSpecAdditionalCodeGroup4, String inspSpecAddlSeldCodeSetPlant4, String inspSpecAdditionalCatalog5, String inspSpecAdditionalSelectedSet5, String inspSpecAdditionalCodeGroup5, String inspSpecAddlSeldCodeSetPlant5, String samplingProcedure, String inspCharacteristicSampleUnit, BigDecimal bOOCharcSampleQuantity, String inspSpecInformationField1, String inspSpecInformationField2, String inspSpecInformationField3, String inspectionSpecificationText, String createdByUser, LocalDateTime creationDate, String lastChangedByUser, LocalDateTime lastChangeDate, String billOfOperationsVersion, 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 InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`static <T> InspPlanOpCharacteristicField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> InspPlanOpCharacteristicField<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)`
`String`	`getBillOfOperationsVersion()` Constraints: Not nullable, Maximum length: 4
`String`	`getBOOCharacteristic()` (Key Field) Constraints: Not nullable, Maximum length: 4
`String`	`getBOOCharacteristicVersion()` (Key Field) Constraints: Not nullable, Maximum length: 8
`Boolean`	`getBOOCharcHasInspSpecReference()` Constraints: none
`BigDecimal`	`getBOOCharcSampleQuantity()` Constraints: Not nullable, Precision: 5, Scale: 2
`String`	`getBOOOperationInternalID()` (Key Field) Constraints: Not nullable, Maximum length: 8
`String`	`getBOOOperationPRTInternalID()` Constraints: Not nullable, Maximum length: 8
`String`	`getBOOOpInternalVersionCounter()` (Key Field) Constraints: Not nullable, Maximum length: 8
`ZonedDateTime`	`getChangedDateTime()` Constraints: Not nullable, Precision: 0
`String`	`getChangeNumber()` Constraints: Not nullable, Maximum length: 12
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getInspCharacteristicSampleUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getInspectionMethod()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspectionMethodPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspectionMethodVersion()` Constraints: Not nullable, Maximum length: 6
`String`	`getInspectionPlan()` (Key Field) Constraints: Not nullable, Maximum length: 2
`String`	`getInspectionPlanGroup()` (Key Field) Constraints: Not nullable, Maximum length: 8
`String`	`getInspectionPlanInternalVersion()` (Key Field) Constraints: Not nullable, Maximum length: 8
`String`	`getInspectionScope()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspectionSpecification()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspectionSpecificationPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspectionSpecificationText()` Constraints: Not nullable, Maximum length: 40
`String`	`getInspectionSpecificationUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getInspectionSpecificationVersion()` Constraints: Not nullable, Maximum length: 6
`String`	`getInspectorQualification()` Constraints: Not nullable, Maximum length: 5
`String`	`getInspResultIsDocumentationRqd()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecAdditionalCatalog2()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecAdditionalCatalog3()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecAdditionalCatalog4()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecAdditionalCatalog5()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecAdditionalCodeGroup2()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalCodeGroup3()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalCodeGroup4()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalCodeGroup5()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalSelectedSet2()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalSelectedSet3()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalSelectedSet4()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAdditionalSelectedSet5()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecAddlSeldCodeSetPlant2()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecAddlSeldCodeSetPlant3()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecAddlSeldCodeSetPlant4()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecAddlSeldCodeSetPlant5()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecCharcCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecControlIndicators()` Constraints: Not nullable, Maximum length: 30
`Short`	`getInspSpecDecimalPlaces()` Constraints: none
`String`	`getInspSpecDefectCodeGrpRejection()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecDefectCodeGrpRjcnLower()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecDefectCodeGrpRjcnUpper()` Constraints: Not nullable, Maximum length: 8
`String`	`getInspSpecDefectCodeRejection()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecDefectCodeRjcnLower()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecDefectCodeRjcnUpper()` Constraints: Not nullable, Maximum length: 4
`String`	`getInspSpecHasFixedCtrlIndicators()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecHasLowerLimit()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecHasTargetValue()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecHasUpperLimit()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecImportanceCode()` Constraints: Not nullable, Maximum length: 2
`String`	`getInspSpecInformationField1()` Constraints: Not nullable, Maximum length: 10
`String`	`getInspSpecInformationField2()` Constraints: Not nullable, Maximum length: 20
`String`	`getInspSpecInformationField3()` Constraints: Not nullable, Maximum length: 40
`String`	`getInspSpecIsChgDocRequired()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsControlChartUsed()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsDefectsRecgAutomatic()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsDestructive()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsLongTermInspection()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsLowerLimitRequired()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsMeasuredValueRqd()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsQuantitative()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsSampleQtyAdditive()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsSamplingProcedRqd()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsScrapRelevant()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsSelectedSetRequired()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsTargetValueInLimit()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsTestEquipmentRqd()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecIsUpperLimitRequired()` Constraints: Not nullable, Maximum length: 1
`Double`	`getInspSpecLowerLimit()` Constraints: none
`String`	`getInspSpecPrintControl()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecRecordingType()` Constraints: Not nullable, Maximum length: 1
`String`	`getInspSpecResultCalculation()` Constraints: Not nullable, Maximum length: 1
`Double`	`getInspSpecTargetValue()` Constraints: none
`Double`	`getInspSpecUpperLimit()` Constraints: none
`String`	`getInspToleranceSpecification()` Constraints: Not nullable, Maximum length: 4
`Boolean`	`getIsDeleted()` Constraints: none
`protected Map<String,Object>`	`getKey()`
`LocalDateTime`	`getLastChangeDate()` Constraints: Not nullable, Precision: 0
`String`	`getLastChangedByUser()` Constraints: Not nullable, Maximum length: 12
`String`	`getSamplingProcedure()` Constraints: Not nullable, Maximum length: 8
`String`	`getSelectedCodeSet()` Constraints: Not nullable, Maximum length: 8
`String`	`getSelectedCodeSetPlant()` Constraints: Not nullable, Maximum length: 4
`Class<InspPlanOpCharacteristic>`	`getType()`
`LocalDateTime`	`getValidityEndDate()` Constraints: Not nullable, Precision: 0
`LocalDateTime`	`getValidityStartDate()` Constraints: Not nullable, Precision: 0
`int`	`hashCode()`
`void`	`setBillOfOperationsVersion(String billOfOperationsVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setBOOCharacteristic(String bOOCharacteristic)` (Key Field) Constraints: Not nullable, Maximum length: 4
`void`	`setBOOCharacteristicVersion(String bOOCharacteristicVersion)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setBOOCharcHasInspSpecReference(Boolean bOOCharcHasInspSpecReference)` Constraints: none
`void`	`setBOOCharcSampleQuantity(BigDecimal bOOCharcSampleQuantity)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setBOOOperationInternalID(String bOOOperationInternalID)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setBOOOperationPRTInternalID(String bOOOperationPRTInternalID)` Constraints: Not nullable, Maximum length: 8
`void`	`setBOOOpInternalVersionCounter(String bOOOpInternalVersionCounter)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setChangedDateTime(ZonedDateTime changedDateTime)` Constraints: Not nullable, Precision: 0
`void`	`setChangeNumber(String changeNumber)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setInspCharacteristicSampleUnit(String inspCharacteristicSampleUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setInspectionMethod(String inspectionMethod)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspectionMethodPlant(String inspectionMethodPlant)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspectionMethodVersion(String inspectionMethodVersion)` Constraints: Not nullable, Maximum length: 6
`void`	`setInspectionPlan(String inspectionPlan)` (Key Field) Constraints: Not nullable, Maximum length: 2
`void`	`setInspectionPlanGroup(String inspectionPlanGroup)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setInspectionPlanInternalVersion(String inspectionPlanInternalVersion)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setInspectionScope(String inspectionScope)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspectionSpecification(String inspectionSpecification)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspectionSpecificationPlant(String inspectionSpecificationPlant)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspectionSpecificationText(String inspectionSpecificationText)` Constraints: Not nullable, Maximum length: 40
`void`	`setInspectionSpecificationUnit(String inspectionSpecificationUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setInspectionSpecificationVersion(String inspectionSpecificationVersion)` Constraints: Not nullable, Maximum length: 6
`void`	`setInspectorQualification(String inspectorQualification)` Constraints: Not nullable, Maximum length: 5
`void`	`setInspResultIsDocumentationRqd(String inspResultIsDocumentationRqd)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecAdditionalCatalog2(String inspSpecAdditionalCatalog2)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecAdditionalCatalog3(String inspSpecAdditionalCatalog3)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecAdditionalCatalog4(String inspSpecAdditionalCatalog4)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecAdditionalCatalog5(String inspSpecAdditionalCatalog5)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecAdditionalCodeGroup2(String inspSpecAdditionalCodeGroup2)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalCodeGroup3(String inspSpecAdditionalCodeGroup3)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalCodeGroup4(String inspSpecAdditionalCodeGroup4)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalCodeGroup5(String inspSpecAdditionalCodeGroup5)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalSelectedSet2(String inspSpecAdditionalSelectedSet2)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalSelectedSet3(String inspSpecAdditionalSelectedSet3)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalSelectedSet4(String inspSpecAdditionalSelectedSet4)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAdditionalSelectedSet5(String inspSpecAdditionalSelectedSet5)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecAddlSeldCodeSetPlant2(String inspSpecAddlSeldCodeSetPlant2)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecAddlSeldCodeSetPlant3(String inspSpecAddlSeldCodeSetPlant3)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecAddlSeldCodeSetPlant4(String inspSpecAddlSeldCodeSetPlant4)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecAddlSeldCodeSetPlant5(String inspSpecAddlSeldCodeSetPlant5)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecCharcCategory(String inspSpecCharcCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecControlIndicators(String inspSpecControlIndicators)` Constraints: Not nullable, Maximum length: 30
`void`	`setInspSpecDecimalPlaces(Short inspSpecDecimalPlaces)` Constraints: none
`void`	`setInspSpecDefectCodeGrpRejection(String inspSpecDefectCodeGrpRejection)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecDefectCodeGrpRjcnLower(String inspSpecDefectCodeGrpRjcnLower)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecDefectCodeGrpRjcnUpper(String inspSpecDefectCodeGrpRjcnUpper)` Constraints: Not nullable, Maximum length: 8
`void`	`setInspSpecDefectCodeRejection(String inspSpecDefectCodeRejection)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecDefectCodeRjcnLower(String inspSpecDefectCodeRjcnLower)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecDefectCodeRjcnUpper(String inspSpecDefectCodeRjcnUpper)` Constraints: Not nullable, Maximum length: 4
`void`	`setInspSpecHasFixedCtrlIndicators(String inspSpecHasFixedCtrlIndicators)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecHasLowerLimit(String inspSpecHasLowerLimit)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecHasTargetValue(String inspSpecHasTargetValue)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecHasUpperLimit(String inspSpecHasUpperLimit)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecImportanceCode(String inspSpecImportanceCode)` Constraints: Not nullable, Maximum length: 2
`void`	`setInspSpecInformationField1(String inspSpecInformationField1)` Constraints: Not nullable, Maximum length: 10
`void`	`setInspSpecInformationField2(String inspSpecInformationField2)` Constraints: Not nullable, Maximum length: 20
`void`	`setInspSpecInformationField3(String inspSpecInformationField3)` Constraints: Not nullable, Maximum length: 40
`void`	`setInspSpecIsChgDocRequired(String inspSpecIsChgDocRequired)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsControlChartUsed(String inspSpecIsControlChartUsed)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsDefectsRecgAutomatic(String inspSpecIsDefectsRecgAutomatic)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsDestructive(String inspSpecIsDestructive)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsLongTermInspection(String inspSpecIsLongTermInspection)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsLowerLimitRequired(String inspSpecIsLowerLimitRequired)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsMeasuredValueRqd(String inspSpecIsMeasuredValueRqd)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsQuantitative(String inspSpecIsQuantitative)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsSampleQtyAdditive(String inspSpecIsSampleQtyAdditive)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsSamplingProcedRqd(String inspSpecIsSamplingProcedRqd)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsScrapRelevant(String inspSpecIsScrapRelevant)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsSelectedSetRequired(String inspSpecIsSelectedSetRequired)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsTargetValueInLimit(String inspSpecIsTargetValueInLimit)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsTestEquipmentRqd(String inspSpecIsTestEquipmentRqd)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecIsUpperLimitRequired(String inspSpecIsUpperLimitRequired)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecLowerLimit(Double inspSpecLowerLimit)` Constraints: none
`void`	`setInspSpecPrintControl(String inspSpecPrintControl)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecRecordingType(String inspSpecRecordingType)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecResultCalculation(String inspSpecResultCalculation)` Constraints: Not nullable, Maximum length: 1
`void`	`setInspSpecTargetValue(Double inspSpecTargetValue)` Constraints: none
`void`	`setInspSpecUpperLimit(Double inspSpecUpperLimit)` Constraints: none
`void`	`setInspToleranceSpecification(String inspToleranceSpecification)` Constraints: Not nullable, Maximum length: 4
`void`	`setIsDeleted(Boolean isDeleted)` Constraints: none
`void`	`setLastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setLastChangedByUser(String lastChangedByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setSamplingProcedure(String samplingProcedure)` Constraints: Not nullable, Maximum length: 8
`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`	`setValidityEndDate(LocalDateTime validityEndDate)` Constraints: Not nullable, Precision: 0
`void`	`setValidityStartDate(LocalDateTime validityStartDate)` Constraints: Not nullable, Precision: 0
`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 InspPlanOpCharacteristicSelectable ALL_FIELDS
```
    Selector for all available fields of InspPlanOpCharacteristic.
  - INSPECTION_PLAN_GROUP
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_PLAN_GROUP
```
    Use with available fluent helpers to apply the InspectionPlanGroup field to query operations.
  - BOO_OPERATION_INTERNAL_ID
```
public static final InspPlanOpCharacteristicField<String> BOO_OPERATION_INTERNAL_ID
```
    Use with available fluent helpers to apply the BOOOperationInternalID field to query operations.
  - BOO_CHARACTERISTIC
```
public static final InspPlanOpCharacteristicField<String> BOO_CHARACTERISTIC
```
    Use with available fluent helpers to apply the BOOCharacteristic field to query operations.
  - BOO_CHARACTERISTIC_VERSION
```
public static final InspPlanOpCharacteristicField<String> BOO_CHARACTERISTIC_VERSION
```
    Use with available fluent helpers to apply the BOOCharacteristicVersion field to query operations.
  - BOO_OP_INTERNAL_VERSION_COUNTER
```
public static final InspPlanOpCharacteristicField<String> BOO_OP_INTERNAL_VERSION_COUNTER
```
    Use with available fluent helpers to apply the BOOOpInternalVersionCounter field to query operations.
  - INSPECTION_PLAN_INTERNAL_VERSION
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_PLAN_INTERNAL_VERSION
```
    Use with available fluent helpers to apply the InspectionPlanInternalVersion field to query operations.
  - INSPECTION_PLAN
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_PLAN
```
    Use with available fluent helpers to apply the InspectionPlan field to query operations.
  - VALIDITY_START_DATE
```
public static final InspPlanOpCharacteristicField<LocalDateTime> VALIDITY_START_DATE
```
    Use with available fluent helpers to apply the ValidityStartDate field to query operations.
  - VALIDITY_END_DATE
```
public static final InspPlanOpCharacteristicField<LocalDateTime> VALIDITY_END_DATE
```
    Use with available fluent helpers to apply the ValidityEndDate field to query operations.
  - CHANGE_NUMBER
```
public static final InspPlanOpCharacteristicField<String> CHANGE_NUMBER
```
    Use with available fluent helpers to apply the ChangeNumber field to query operations.
  - IS_DELETED
```
public static final InspPlanOpCharacteristicField<Boolean> IS_DELETED
```
    Use with available fluent helpers to apply the IsDeleted field to query operations.
  - BOO_OPERATION_PRT_INTERNAL_ID
```
public static final InspPlanOpCharacteristicField<String> BOO_OPERATION_PRT_INTERNAL_ID
```
    Use with available fluent helpers to apply the BOOOperationPRTInternalID field to query operations.
  - INSPECTION_METHOD
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_METHOD
```
    Use with available fluent helpers to apply the InspectionMethod field to query operations.
  - INSPECTION_METHOD_VERSION
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_METHOD_VERSION
```
    Use with available fluent helpers to apply the InspectionMethodVersion field to query operations.
  - INSPECTION_METHOD_PLANT
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_METHOD_PLANT
```
    Use with available fluent helpers to apply the InspectionMethodPlant field to query operations.
  - INSP_SPEC_IMPORTANCE_CODE
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IMPORTANCE_CODE
```
    Use with available fluent helpers to apply the InspSpecImportanceCode field to query operations.
  - INSPECTOR_QUALIFICATION
```
public static final InspPlanOpCharacteristicField<String> INSPECTOR_QUALIFICATION
```
    Use with available fluent helpers to apply the InspectorQualification field to query operations.
  - INSPECTION_SPECIFICATION
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION
```
    Use with available fluent helpers to apply the InspectionSpecification field to query operations.
  - INSPECTION_SPECIFICATION_VERSION
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_VERSION
```
    Use with available fluent helpers to apply the InspectionSpecificationVersion field to query operations.
  - INSPECTION_SPECIFICATION_PLANT
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_PLANT
```
    Use with available fluent helpers to apply the InspectionSpecificationPlant field to query operations.
  - BOO_CHARC_HAS_INSP_SPEC_REFERENCE
```
public static final InspPlanOpCharacteristicField<Boolean> BOO_CHARC_HAS_INSP_SPEC_REFERENCE
```
    Use with available fluent helpers to apply the BOOCharcHasInspSpecReference field to query operations.
  - INSP_SPEC_CONTROL_INDICATORS
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_CONTROL_INDICATORS
```
    Use with available fluent helpers to apply the InspSpecControlIndicators field to query operations.
  - INSP_SPEC_IS_QUANTITATIVE
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_QUANTITATIVE
```
    Use with available fluent helpers to apply the InspSpecIsQuantitative field to query operations.
  - INSP_SPEC_IS_MEASURED_VALUE_RQD
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_MEASURED_VALUE_RQD
```
    Use with available fluent helpers to apply the InspSpecIsMeasuredValueRqd field to query operations.
  - INSP_SPEC_IS_SELECTED_SET_REQUIRED
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SELECTED_SET_REQUIRED
```
    Use with available fluent helpers to apply the InspSpecIsSelectedSetRequired field to query operations.
  - INSP_SPEC_IS_UPPER_LIMIT_REQUIRED
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_UPPER_LIMIT_REQUIRED
```
    Use with available fluent helpers to apply the InspSpecIsUpperLimitRequired field to query operations.
  - INSP_SPEC_IS_LOWER_LIMIT_REQUIRED
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_LOWER_LIMIT_REQUIRED
```
    Use with available fluent helpers to apply the InspSpecIsLowerLimitRequired field to query operations.
  - INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT
```
    Use with available fluent helpers to apply the InspSpecIsTargetValueInLimit field to query operations.
  - INSPECTION_SCOPE
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_SCOPE
```
    Use with available fluent helpers to apply the InspectionScope field to query operations.
  - INSP_SPEC_IS_LONG_TERM_INSPECTION
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_LONG_TERM_INSPECTION
```
    Use with available fluent helpers to apply the InspSpecIsLongTermInspection field to query operations.
  - INSP_SPEC_RECORDING_TYPE
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_RECORDING_TYPE
```
    Use with available fluent helpers to apply the InspSpecRecordingType field to query operations.
  - INSP_RESULT_IS_DOCUMENTATION_RQD
```
public static final InspPlanOpCharacteristicField<String> INSP_RESULT_IS_DOCUMENTATION_RQD
```
    Use with available fluent helpers to apply the InspResultIsDocumentationRqd field to query operations.
  - INSP_SPEC_CHARC_CATEGORY
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_CHARC_CATEGORY
```
    Use with available fluent helpers to apply the InspSpecCharcCategory field to query operations.
  - INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE
```
    Use with available fluent helpers to apply the InspSpecIsSampleQtyAdditive field to query operations.
  - INSP_SPEC_IS_DESTRUCTIVE
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_DESTRUCTIVE
```
    Use with available fluent helpers to apply the InspSpecIsDestructive field to query operations.
  - INSP_SPEC_RESULT_CALCULATION
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_RESULT_CALCULATION
```
    Use with available fluent helpers to apply the InspSpecResultCalculation field to query operations.
  - INSP_SPEC_IS_SAMPLING_PROCED_RQD
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SAMPLING_PROCED_RQD
```
    Use with available fluent helpers to apply the InspSpecIsSamplingProcedRqd field to query operations.
  - INSP_SPEC_IS_SCRAP_RELEVANT
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SCRAP_RELEVANT
```
    Use with available fluent helpers to apply the InspSpecIsScrapRelevant field to query operations.
  - INSP_SPEC_HAS_FIXED_CTRL_INDICATORS
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_FIXED_CTRL_INDICATORS
```
    Use with available fluent helpers to apply the InspSpecHasFixedCtrlIndicators field to query operations.
  - INSP_SPEC_IS_TEST_EQUIPMENT_RQD
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_TEST_EQUIPMENT_RQD
```
    Use with available fluent helpers to apply the InspSpecIsTestEquipmentRqd field to query operations.
  - INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC
```
    Use with available fluent helpers to apply the InspSpecIsDefectsRecgAutomatic field to query operations.
  - INSP_SPEC_IS_CHG_DOC_REQUIRED
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_CHG_DOC_REQUIRED
```
    Use with available fluent helpers to apply the InspSpecIsChgDocRequired field to query operations.
  - INSP_SPEC_IS_CONTROL_CHART_USED
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_CONTROL_CHART_USED
```
    Use with available fluent helpers to apply the InspSpecIsControlChartUsed field to query operations.
  - INSP_SPEC_PRINT_CONTROL
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_PRINT_CONTROL
```
    Use with available fluent helpers to apply the InspSpecPrintControl field to query operations.
  - INSP_TOLERANCE_SPECIFICATION
```
public static final InspPlanOpCharacteristicField<String> INSP_TOLERANCE_SPECIFICATION
```
    Use with available fluent helpers to apply the InspToleranceSpecification field to query operations.
  - INSP_SPEC_DECIMAL_PLACES
```
public static final InspPlanOpCharacteristicField<Short> INSP_SPEC_DECIMAL_PLACES
```
    Use with available fluent helpers to apply the InspSpecDecimalPlaces field to query operations.
  - INSPECTION_SPECIFICATION_UNIT
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_UNIT
```
    Use with available fluent helpers to apply the InspectionSpecificationUnit field to query operations.
  - INSP_SPEC_TARGET_VALUE
```
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_TARGET_VALUE
```
    Use with available fluent helpers to apply the InspSpecTargetValue field to query operations.
  - INSP_SPEC_HAS_TARGET_VALUE
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_TARGET_VALUE
```
    Use with available fluent helpers to apply the InspSpecHasTargetValue field to query operations.
  - INSP_SPEC_UPPER_LIMIT
```
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_UPPER_LIMIT
```
    Use with available fluent helpers to apply the InspSpecUpperLimit field to query operations.
  - INSP_SPEC_LOWER_LIMIT
```
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_LOWER_LIMIT
```
    Use with available fluent helpers to apply the InspSpecLowerLimit field to query operations.
  - INSP_SPEC_HAS_LOWER_LIMIT
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_LOWER_LIMIT
```
    Use with available fluent helpers to apply the InspSpecHasLowerLimit field to query operations.
  - INSP_SPEC_HAS_UPPER_LIMIT
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_UPPER_LIMIT
```
    Use with available fluent helpers to apply the InspSpecHasUpperLimit field to query operations.
  - INSP_SPEC_DEFECT_CODE_GRP_REJECTION
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_GRP_REJECTION
```
    Use with available fluent helpers to apply the InspSpecDefectCodeGrpRejection field to query operations.
  - INSP_SPEC_DEFECT_CODE_REJECTION
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_REJECTION
```
    Use with available fluent helpers to apply the InspSpecDefectCodeRejection field to query operations.
  - INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER
```
    Use with available fluent helpers to apply the InspSpecDefectCodeGrpRjcnUpper field to query operations.
  - INSP_SPEC_DEFECT_CODE_RJCN_UPPER
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_RJCN_UPPER
```
    Use with available fluent helpers to apply the InspSpecDefectCodeRjcnUpper field to query operations.
  - INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER
```
    Use with available fluent helpers to apply the InspSpecDefectCodeGrpRjcnLower field to query operations.
  - INSP_SPEC_DEFECT_CODE_RJCN_LOWER
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_RJCN_LOWER
```
    Use with available fluent helpers to apply the InspSpecDefectCodeRjcnLower field to query operations.
  - SELECTED_CODE_SET
```
public static final InspPlanOpCharacteristicField<String> SELECTED_CODE_SET
```
    Use with available fluent helpers to apply the SelectedCodeSet field to query operations.
  - SELECTED_CODE_SET_PLANT
```
public static final InspPlanOpCharacteristicField<String> SELECTED_CODE_SET_PLANT
```
    Use with available fluent helpers to apply the SelectedCodeSetPlant field to query operations.
  - INSP_SPEC_ADDITIONAL_CATALOG2
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG2
```
    Use with available fluent helpers to apply the InspSpecAdditionalCatalog2 field to query operations.
  - INSP_SPEC_ADDITIONAL_SELECTED_SET2
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET2
```
    Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet2 field to query operations.
  - INSP_SPEC_ADDITIONAL_CODE_GROUP2
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP2
```
    Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup2 field to query operations.
  - INSP_SPEC_ADDL_SELD_CODE_SET_PLANT2
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT2
```
    Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant2 field to query operations.
  - INSP_SPEC_ADDITIONAL_CATALOG3
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG3
```
    Use with available fluent helpers to apply the InspSpecAdditionalCatalog3 field to query operations.
  - INSP_SPEC_ADDITIONAL_SELECTED_SET3
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET3
```
    Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet3 field to query operations.
  - INSP_SPEC_ADDITIONAL_CODE_GROUP3
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP3
```
    Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup3 field to query operations.
  - INSP_SPEC_ADDL_SELD_CODE_SET_PLANT3
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT3
```
    Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant3 field to query operations.
  - INSP_SPEC_ADDITIONAL_CATALOG4
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG4
```
    Use with available fluent helpers to apply the InspSpecAdditionalCatalog4 field to query operations.
  - INSP_SPEC_ADDITIONAL_SELECTED_SET4
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET4
```
    Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet4 field to query operations.
  - INSP_SPEC_ADDITIONAL_CODE_GROUP4
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP4
```
    Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup4 field to query operations.
  - INSP_SPEC_ADDL_SELD_CODE_SET_PLANT4
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT4
```
    Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant4 field to query operations.
  - INSP_SPEC_ADDITIONAL_CATALOG5
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG5
```
    Use with available fluent helpers to apply the InspSpecAdditionalCatalog5 field to query operations.
  - INSP_SPEC_ADDITIONAL_SELECTED_SET5
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET5
```
    Use with available fluent helpers to apply the InspSpecAdditionalSelectedSet5 field to query operations.
  - INSP_SPEC_ADDITIONAL_CODE_GROUP5
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP5
```
    Use with available fluent helpers to apply the InspSpecAdditionalCodeGroup5 field to query operations.
  - INSP_SPEC_ADDL_SELD_CODE_SET_PLANT5
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT5
```
    Use with available fluent helpers to apply the InspSpecAddlSeldCodeSetPlant5 field to query operations.
  - SAMPLING_PROCEDURE
```
public static final InspPlanOpCharacteristicField<String> SAMPLING_PROCEDURE
```
    Use with available fluent helpers to apply the SamplingProcedure field to query operations.
  - INSP_CHARACTERISTIC_SAMPLE_UNIT
```
public static final InspPlanOpCharacteristicField<String> INSP_CHARACTERISTIC_SAMPLE_UNIT
```
    Use with available fluent helpers to apply the InspCharacteristicSampleUnit field to query operations.
  - BOO_CHARC_SAMPLE_QUANTITY
```
public static final InspPlanOpCharacteristicField<BigDecimal> BOO_CHARC_SAMPLE_QUANTITY
```
    Use with available fluent helpers to apply the BOOCharcSampleQuantity field to query operations.
  - INSP_SPEC_INFORMATION_FIELD1
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INFORMATION_FIELD1
```
    Use with available fluent helpers to apply the InspSpecInformationField1 field to query operations.
  - INSP_SPEC_INFORMATION_FIELD2
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INFORMATION_FIELD2
```
    Use with available fluent helpers to apply the InspSpecInformationField2 field to query operations.
  - INSP_SPEC_INFORMATION_FIELD3
```
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INFORMATION_FIELD3
```
    Use with available fluent helpers to apply the InspSpecInformationField3 field to query operations.
  - INSPECTION_SPECIFICATION_TEXT
```
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_TEXT
```
    Use with available fluent helpers to apply the InspectionSpecificationText field to query operations.
  - CREATED_BY_USER
```
public static final InspPlanOpCharacteristicField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - CREATION_DATE
```
public static final InspPlanOpCharacteristicField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - LAST_CHANGED_BY_USER
```
public static final InspPlanOpCharacteristicField<String> LAST_CHANGED_BY_USER
```
    Use with available fluent helpers to apply the LastChangedByUser field to query operations.
  - LAST_CHANGE_DATE
```
public static final InspPlanOpCharacteristicField<LocalDateTime> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - BILL_OF_OPERATIONS_VERSION
```
public static final InspPlanOpCharacteristicField<String> BILL_OF_OPERATIONS_VERSION
```
    Use with available fluent helpers to apply the BillOfOperationsVersion field to query operations.
  - CHANGED_DATE_TIME
```
public static final InspPlanOpCharacteristicField<ZonedDateTime> CHANGED_DATE_TIME
```
    Use with available fluent helpers to apply the ChangedDateTime field to query operations.
- Constructor Detail
  - InspPlanOpCharacteristic
```
public InspPlanOpCharacteristic()
```
  - InspPlanOpCharacteristic
```
public InspPlanOpCharacteristic(@Nullable
                                String inspectionPlanGroup,
                                @Nullable
                                String bOOOperationInternalID,
                                @Nullable
                                String bOOCharacteristic,
                                @Nullable
                                String bOOCharacteristicVersion,
                                @Nullable
                                String bOOOpInternalVersionCounter,
                                @Nullable
                                String inspectionPlanInternalVersion,
                                @Nullable
                                String inspectionPlan,
                                @Nullable
                                LocalDateTime validityStartDate,
                                @Nullable
                                LocalDateTime validityEndDate,
                                @Nullable
                                String changeNumber,
                                @Nullable
                                Boolean isDeleted,
                                @Nullable
                                String bOOOperationPRTInternalID,
                                @Nullable
                                String inspectionMethod,
                                @Nullable
                                String inspectionMethodVersion,
                                @Nullable
                                String inspectionMethodPlant,
                                @Nullable
                                String inspSpecImportanceCode,
                                @Nullable
                                String inspectorQualification,
                                @Nullable
                                String inspectionSpecification,
                                @Nullable
                                String inspectionSpecificationVersion,
                                @Nullable
                                String inspectionSpecificationPlant,
                                @Nullable
                                Boolean bOOCharcHasInspSpecReference,
                                @Nullable
                                String inspSpecControlIndicators,
                                @Nullable
                                String inspSpecIsQuantitative,
                                @Nullable
                                String inspSpecIsMeasuredValueRqd,
                                @Nullable
                                String inspSpecIsSelectedSetRequired,
                                @Nullable
                                String inspSpecIsUpperLimitRequired,
                                @Nullable
                                String inspSpecIsLowerLimitRequired,
                                @Nullable
                                String inspSpecIsTargetValueInLimit,
                                @Nullable
                                String inspectionScope,
                                @Nullable
                                String inspSpecIsLongTermInspection,
                                @Nullable
                                String inspSpecRecordingType,
                                @Nullable
                                String inspResultIsDocumentationRqd,
                                @Nullable
                                String inspSpecCharcCategory,
                                @Nullable
                                String inspSpecIsSampleQtyAdditive,
                                @Nullable
                                String inspSpecIsDestructive,
                                @Nullable
                                String inspSpecResultCalculation,
                                @Nullable
                                String inspSpecIsSamplingProcedRqd,
                                @Nullable
                                String inspSpecIsScrapRelevant,
                                @Nullable
                                String inspSpecHasFixedCtrlIndicators,
                                @Nullable
                                String inspSpecIsTestEquipmentRqd,
                                @Nullable
                                String inspSpecIsDefectsRecgAutomatic,
                                @Nullable
                                String inspSpecIsChgDocRequired,
                                @Nullable
                                String inspSpecIsControlChartUsed,
                                @Nullable
                                String inspSpecPrintControl,
                                @Nullable
                                String inspToleranceSpecification,
                                @Nullable
                                Short inspSpecDecimalPlaces,
                                @Nullable
                                String inspectionSpecificationUnit,
                                @Nullable
                                Double inspSpecTargetValue,
                                @Nullable
                                String inspSpecHasTargetValue,
                                @Nullable
                                Double inspSpecUpperLimit,
                                @Nullable
                                Double inspSpecLowerLimit,
                                @Nullable
                                String inspSpecHasLowerLimit,
                                @Nullable
                                String inspSpecHasUpperLimit,
                                @Nullable
                                String inspSpecDefectCodeGrpRejection,
                                @Nullable
                                String inspSpecDefectCodeRejection,
                                @Nullable
                                String inspSpecDefectCodeGrpRjcnUpper,
                                @Nullable
                                String inspSpecDefectCodeRjcnUpper,
                                @Nullable
                                String inspSpecDefectCodeGrpRjcnLower,
                                @Nullable
                                String inspSpecDefectCodeRjcnLower,
                                @Nullable
                                String selectedCodeSet,
                                @Nullable
                                String selectedCodeSetPlant,
                                @Nullable
                                String inspSpecAdditionalCatalog2,
                                @Nullable
                                String inspSpecAdditionalSelectedSet2,
                                @Nullable
                                String inspSpecAdditionalCodeGroup2,
                                @Nullable
                                String inspSpecAddlSeldCodeSetPlant2,
                                @Nullable
                                String inspSpecAdditionalCatalog3,
                                @Nullable
                                String inspSpecAdditionalSelectedSet3,
                                @Nullable
                                String inspSpecAdditionalCodeGroup3,
                                @Nullable
                                String inspSpecAddlSeldCodeSetPlant3,
                                @Nullable
                                String inspSpecAdditionalCatalog4,
                                @Nullable
                                String inspSpecAdditionalSelectedSet4,
                                @Nullable
                                String inspSpecAdditionalCodeGroup4,
                                @Nullable
                                String inspSpecAddlSeldCodeSetPlant4,
                                @Nullable
                                String inspSpecAdditionalCatalog5,
                                @Nullable
                                String inspSpecAdditionalSelectedSet5,
                                @Nullable
                                String inspSpecAdditionalCodeGroup5,
                                @Nullable
                                String inspSpecAddlSeldCodeSetPlant5,
                                @Nullable
                                String samplingProcedure,
                                @Nullable
                                String inspCharacteristicSampleUnit,
                                @Nullable
                                BigDecimal bOOCharcSampleQuantity,
                                @Nullable
                                String inspSpecInformationField1,
                                @Nullable
                                String inspSpecInformationField2,
                                @Nullable
                                String inspSpecInformationField3,
                                @Nullable
                                String inspectionSpecificationText,
                                @Nullable
                                String createdByUser,
                                @Nullable
                                LocalDateTime creationDate,
                                @Nullable
                                String lastChangedByUser,
                                @Nullable
                                LocalDateTime lastChangeDate,
                                @Nullable
                                String billOfOperationsVersion,
                                @Nullable
                                ZonedDateTime changedDateTime)
```
- Method Detail
  - getType
```
@Nonnull
public Class<InspPlanOpCharacteristic> getType()
```
    Specified by:
    
    getType in class VdmObject<InspPlanOpCharacteristic>
    
    Returns:
    
    The class of this object.
  - setInspectionPlanGroup
```
public void setInspectionPlanGroup(@Nullable
                                   String inspectionPlanGroup)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionPlanGroup
    
    You can use groups, for instance, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
    
    Parameters:
    
    inspectionPlanGroup - Key identifying a group.
  - setBOOOperationInternalID
```
public void setBOOOperationInternalID(@Nullable
                                      String bOOOperationInternalID)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOOperationInternalID
    
    Parameters:
    
    bOOOperationInternalID - Number of the Task List Node
  - setBOOCharacteristic
```
public void setBOOCharacteristic(@Nullable
                                 String bOOCharacteristic)
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BOOCharacteristic
    
    Parameters:
    
    bOOCharacteristic - The number that explicitly identifies an inspection characteristic within an operation in an inspection plan.
  - setBOOCharacteristicVersion
```
public void setBOOCharacteristicVersion(@Nullable
                                        String bOOCharacteristicVersion)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOCharacteristicVersion
    
    Parameters:
    
    bOOCharacteristicVersion - Identifies the activity posting.
  - setBOOOpInternalVersionCounter
```
public void setBOOOpInternalVersionCounter(@Nullable
                                           String bOOOpInternalVersionCounter)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOOpInternalVersionCounter
    
    Parameters:
    
    bOOOpInternalVersionCounter - Identifies the activity posting.
  - setInspectionPlanInternalVersion
```
public void setInspectionPlanInternalVersion(@Nullable
                                             String inspectionPlanInternalVersion)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionPlanInternalVersion
    
    Parameters:
    
    inspectionPlanInternalVersion - Identifies the activity posting.
  - setInspectionPlan
```
public void setInspectionPlan(@Nullable
                              String inspectionPlan)
```
    (Key Field) Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InspectionPlan
    
    In Production Planning and Control, for example, it serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.The group counter can be used to identify different lot-size ranges, for example.
    
    Parameters:
    
    inspectionPlan - This key and the task list group uniquely identify a task list.
  - setValidityStartDate
```
public void setValidityStartDate(@Nullable
                                 LocalDateTime validityStartDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityStartDate
    
    Parameters:
    
    validityStartDate - Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - setValidityEndDate
```
public void setValidityEndDate(@Nullable
                               LocalDateTime validityEndDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityEndDate
    
    Parameters:
    
    validityEndDate - End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - setChangeNumber
```
public void setChangeNumber(@Nullable
                            String changeNumber)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ChangeNumber
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    changeNumber - Number used to uniquely identify a change master record.
  - setIsDeleted
```
public void setIsDeleted(@Nullable
                         Boolean isDeleted)
```
    Constraints: none
    Original property name from the Odata EDM: IsDeleted
    
    This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
    
    Parameters:
    
    isDeleted - Indicator showing that the BOM header or the BOM item has been deleted with reference to the change number.
  - setBOOOperationPRTInternalID
```
public void setBOOOperationPRTInternalID(@Nullable
                                         String bOOOperationPRTInternalID)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOOperationPRTInternalID
    
    Parameters:
    
    bOOOperationPRTInternalID - Assigned Test Equipment
  - setInspectionMethod
```
public void setInspectionMethod(@Nullable
                                String inspectionMethod)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionMethod
    
    An inspection method describes how to inspect an inspection characteristic. You can assign an inspection method to a master inspection characteristic or directly to an inspection characteristic in an inspection plan.
    
    Parameters:
    
    inspectionMethod - Name that uniquely identifies an inspection method within a plant.
  - setInspectionMethodVersion
```
public void setInspectionMethodVersion(@Nullable
                                       String inspectionMethodVersion)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionMethodVersion
    
    Parameters:
    
    inspectionMethodVersion - Version Number of the Inspection Method
  - setInspectionMethodPlant
```
public void setInspectionMethodPlant(@Nullable
                                     String inspectionMethodPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspectionMethodPlant
    
    For inspection methods this plant is the planning plant, in which the inspection method was created in QM.
    
    Parameters:
    
    inspectionMethodPlant - Key, that identifies a plant.
  - setInspSpecImportanceCode
```
public void setInspSpecImportanceCode(@Nullable
                                      String inspSpecImportanceCode)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InspSpecImportanceCode
    
    By choosing the corresponding entry, you can classify the inspection characteristic as a critical characteristic, major characteristic, or minor characteristic.
    
    Parameters:
    
    inspSpecImportanceCode - Classification of inspection characteristics according to their weighting (importance).
  - setInspectorQualification
```
public void setInspectorQualification(@Nullable
                                      String inspectorQualification)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: InspectorQualification
    
    This field has no controlling function. However, your entry is checked against a list of qualifications stored in the database.You can enter an inspector qualification in an inspection method, a master inspection characteristic, or a task list.If you use a master inspection characteristic in a task list that has an inspection method assigned, the inspector qualification defined in the inspection method is used in the task list. If there is no inspector qualification in the inspection method, the qualification is taken from the master inspection characteristic.
    
    Parameters:
    
    inspectorQualification - Qualification that an inspector must have and, if necessary, validate in order to be able to conduct an inspection.
  - setInspectionSpecification
```
public void setInspectionSpecification(@Nullable
                                       String inspectionSpecification)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionSpecification
    
    An inspection characteristic describes what is to be inspected, that is, the inspection requirements for materials, parts, and products. To simplify and standardize inspection planning, you can define master inspection characteristics that you can use in various task lists.
    
    Parameters:
    
    inspectionSpecification - Name that uniquely identifies a master inspection characteristic within a plant.
  - setInspectionSpecificationVersion
```
public void setInspectionSpecificationVersion(@Nullable
                                              String inspectionSpecificationVersion)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionSpecificationVersion
    
    Parameters:
    
    inspectionSpecificationVersion - Version Number of the Master Inspection Characteristic
  - setInspectionSpecificationPlant
```
public void setInspectionSpecificationPlant(@Nullable
                                            String inspectionSpecificationPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspectionSpecificationPlant
    
    Parameters:
    
    inspectionSpecificationPlant - Plant for the Master Inspection Characteristic
  - setBOOCharcHasInspSpecReference
```
public void setBOOCharcHasInspSpecReference(@Nullable
                                            Boolean bOOCharcHasInspSpecReference)
```
    Constraints: none
    Original property name from the Odata EDM: BOOCharcHasInspSpecReference
    
    Parameters:
    
    bOOCharcHasInspSpecReference - Boolean Variable (X = True, - = False, Space = Unknown)
  - setInspSpecControlIndicators
```
public void setInspSpecControlIndicators(@Nullable
                                         String inspSpecControlIndicators)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: InspSpecControlIndicators
    
    plan default valuesresults recordinginspection processing
    
    Parameters:
    
    inspSpecControlIndicators - A characteristic is defined with this control indicator string. It contains indicators for:
  - setInspSpecIsQuantitative
```
public void setInspSpecIsQuantitative(@Nullable
                                      String inspSpecIsQuantitative)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsQuantitative
    
    Set the indicator for the characteristic type (quantitative or qualitative) or enter a control key.If you used a control key, for which the "fixed" indicator is set in Customizing, you cannot change the indicator for the characteristic type. In addition, you cannot delete this indicator or enter another control key.
    
    Parameters:
    
    inspSpecIsQuantitative - If you set this indicator, it causes the characteristic to be treated as a quantitative characteristic. You thereby define the control indicators that are relevant for the inspection characteristic. A quantitative characteristic is subject to measurement inspections. You can define tolerance limits and a target value for a quantitative characteristic.
  - setInspSpecIsMeasuredValueRqd
```
public void setInspSpecIsMeasuredValueRqd(@Nullable
                                          String inspSpecIsMeasuredValueRqd)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsMeasuredValueRqd
    
    Parameters:
    
    inspSpecIsMeasuredValueRqd - If you set this indicator, measured values for this quantitative characteristic have to be inspected and confirmed.
  - setInspSpecIsSelectedSetRequired
```
public void setInspSpecIsSelectedSetRequired(@Nullable
                                             String inspSpecIsSelectedSetRequired)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsSelectedSetRequired
    
    If you do not set this indicator, the inspection characteristic is marked as an alternative characteristic, that can only take the values "Accepted" or "Rejected".
    
    Parameters:
    
    inspSpecIsSelectedSetRequired - If you set this indicator, the inspection characteristic is marked as an attributive characteristic, whose allowed values are defined as a selected set from catalog 1 (characteristic attributes).
  - setInspSpecIsUpperLimitRequired
```
public void setInspSpecIsUpperLimitRequired(@Nullable
                                            String inspSpecIsUpperLimitRequired)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsUpperLimitRequired
    
    Parameters:
    
    inspSpecIsUpperLimitRequired - If you set this indicator, you must enter an upper specification limit for the inspection characteristic.
  - setInspSpecIsLowerLimitRequired
```
public void setInspSpecIsLowerLimitRequired(@Nullable
                                            String inspSpecIsLowerLimitRequired)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsLowerLimitRequired
    
    Parameters:
    
    inspSpecIsLowerLimitRequired - If you set this indicator, you must enter a lower specification limit for the inspection characteristic.
  - setInspSpecIsTargetValueInLimit
```
public void setInspSpecIsTargetValueInLimit(@Nullable
                                            String inspSpecIsTargetValueInLimit)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsTargetValueInLimit
    
    Parameters:
    
    inspSpecIsTargetValueInLimit - If you set this indicator and either the "Upper specification limit" or "Lower specification limit" indicator, the system checks whether the target value lies within the tolerance.
  - setInspectionScope
```
public void setInspectionScope(@Nullable
                               String inspectionScope)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspectionScope
    
    Parameters:
    
    inspectionScope - With this field you determine the extent, to which the number of required measured values must adhere.
  - setInspSpecIsLongTermInspection
```
public void setInspSpecIsLongTermInspection(@Nullable
                                            String inspSpecIsLongTermInspection)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsLongTermInspection
    
    If you set this indicator for at least one required characteristic, you can distinguish between "Short-term inspection completion" and a final completion of the inspection (status: Inspection close completed).Optional characteristics only work as long-term characteristics, when they are set for processing before inspection completion.You activate a long-term inspection by confirming the inspection completion for the short-term characteristics. This occurs either in conjunction with the making of the usage decision, or by calling up the special function "Short-term inspection completed."In a long-term inspection:There can already be a usage decision for the inspected material during the long-term inspectionYou can still record inspection results for long-term characteristics, once you have made the usage decisionThe system sets a separate status in the inspection lot to identify the long-term inspection and it provides special worklists and workflow tasks for this purposeIf you want to copy inspection results from a long-term inspection into a batch valuation, note that the data is transferred when the following events occur:Results from a short-term inspection are transferred as soon as the statuses "Short-term inspection completion" and "Usage decision made" are set.Results from a long-term inspection are transferred as soon as the statuses "Long-term inspection completion" and "Usage decision made" are setThis means that you must confirm or correct a usage decision, if it has been made after a short-term inspection. To do this, use the change transaction, a relevant worklist or an appropriate workflow task.
    
    Parameters:
    
    inspSpecIsLongTermInspection - If you set this indicator, the characteristic is subject to a long-term inspection.
  - setInspSpecRecordingType
```
public void setInspSpecRecordingType(@Nullable
                                     String inspSpecRecordingType)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecRecordingType
    
    Parameters:
    
    inspSpecRecordingType - In this field, you define whether and how single characteristic attributes (original values) are to be recorded at inspection results recording. A single value, depending on the inspection characteristic, is a measured value, an attribute code, or the valuation A (accepted) or R (rejected).
  - setInspResultIsDocumentationRqd
```
public void setInspResultIsDocumentationRqd(@Nullable
                                            String inspResultIsDocumentationRqd)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspResultIsDocumentationRqd
    
    Parameters:
    
    inspResultIsDocumentationRqd - Determines whether and how inspection results are to be documented with additional text when they are recorded.
  - setInspSpecCharcCategory
```
public void setInspSpecCharcCategory(@Nullable
                                     String inspSpecCharcCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecCharcCategory
    
    You can make the following entries:Optional characteristicThis characteristic can be inspected, if necessary. You do not have to record results for this characteristic.Conditional characteristic (when the previous characteristic has been accepted)This characteristic must be inspected if the previous required characteristic was accepted.Conditional characteristic (when the previous characteristic has been rejected)This characteristic must be inspected when the previous required characteristic was rejected.Required characteristicThis characteristic must be inspected.
    
    Parameters:
    
    inspSpecCharcCategory - In this field you determine if and when a characteristic is inspected.
  - setInspSpecIsSampleQtyAdditive
```
public void setInspSpecIsSampleQtyAdditive(@Nullable
                                           String inspSpecIsSampleQtyAdditive)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsSampleQtyAdditive
    
    If a partial sample is to be used for several characteristics, it contains the total sample quantity required for all the characteristics.The system calculates the sample quantity for each characteristic. For a partial sample that is used for several characteristics, the system takes the largest determined sample quantity as the partial sample quantity.If you set the Additive sample indicator, the system does not include the sample quantity for this characteristic when calculating partial samples, but takes the next smallest sample quantity as the partial sample quantity and subsequently adds the sample quantity of the additive sample.You can set the indicator for an additive sample, for example, if the inspection for a characteristic is destructive.I II IIISample quantity Additive Additive AdditiveCharacteristic 1 15 pcs (X)Characteristic 2 30 pcs X XCharacteristic 3 20 pcs XTotal qty 30 pcs 50 pcs 65 pcsExample I: No indicator for additive samples is set. The system therefore determines the sample quantity for characteristic 2 as the quantity for the partial sample.Example II: The indicator for additive samples is set for characteristic 2. The system therefore determines the sample quantity of characteristic 3 as the quantity for the partial sample and increases this by the sample size of characteristic 2.Example III: The indicator for additive samples is set for characteristics 2 and 3. The system therefore determines the sample quantity of characteristic 1 as the quantity for the partial sample and increases this by the sample sizes of characteristics 2 and 3, irrespective of whether the indicator was also set for characteristic 1.
    
    Parameters:
    
    inspSpecIsSampleQtyAdditive - If you set this indicator, it causes the size of the partial sample to be increased by the quantity required for this characteristic in inspection sample calculation.
  - setInspSpecIsDestructive
```
public void setInspSpecIsDestructive(@Nullable
                                     String inspSpecIsDestructive)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsDestructive
    
    When you make the usage decision, the system calculates the quantity of materials destroyed and makes a proposal for the stock posting To sample usage. The system takes all inspection characteristics into consideration corresponding to the actual sample size for which the indicator Destructive insp. is set and for which inspection results have been recorded (up to the point of the calculation). This may include optional characteristics, skipped characteristics, long-term characteristics, and unplanned characteristics.For the stock posting, the system proposes only the part of the destroyed quantity that exceeds the amount already posted to sample usage.For example, you set the indicator for an additive sample if the inspection of an inspection characteristic is destructive. In this case, the indicator causes the sample quantity to be increased by the amount needed to inspect this characteristic.If you inspect only one inspection characteristic destructively and you inspect this characteristic last, you should not set the indicator Additive sample for the characteristic.You must set the indicator Additive sample if you inspect more than one inspection characteristic destructively and if you can only inspect one of these characteristics for a partial sample.If several characteristics contribute to the destruction of the inspection sample, you can combine these characteristics for a partial sample.A simple exampleFour characteristics are inspected. The inspection of characteristics 1, 3, and 4 is destructive. The indicator Additive sample was set for characteristic 4.Charac. Destructive Additive To be insp. Inspected1 x 10 * 1 pc 5 * 1 pc2 10 * 1 pc 10 * 1 pc3 x 10 * 1 pc 10 * 1 pc4 x x 4 * 12 pc 5 * 12 pcIn calculating the destroyed quantity, the system only considers the actual inspected sample size specified in results recording ("Inspected" column) and not the sample quantity to be inspected specified in the inspection instruction ("To be inspected" column).When you make the usage decision, the system determines a destroyed quantity of 70 pieces and proposes they be posted to sample usage. Characteristics 1 and 3 are combined, since they are not marked as additive.Extended example with material samples, long-term characteristics, and different units of measureThe unit of measure for the lot is PIECES; the following conversion factors are stored in the material master record:4 pieces = 3 l8 pieces = 9 kgIn the inspection plan, it is defined that characteristics 1, 3, 4, and 6 (material sample 100) are to be inspected in laboratory 1 and characteristics 2, 5, and 7 in laboratory 2 (material sample 200).Charac. Mat.Sample Destructive Additive Inspected1 100 x x 5 * 100 ml2 200 x 1 * 1 kg3 100 x x 5 * 100 ml4 100 x x 4 * 100 ml5 200 x 4 * 1 kg6 100 x x ----7 200 x ----After inspecting characteristics 1 through 5, the destructive quantity consists of 1400 ml and 4 kg, which is rounded off to 6 pieces. When you make the usage decision, the system proposes that 6 pieces be posted to sample usage.You then record the results for long-term characteristics 6 and 7 and change the usage decision.Charac. Mat.Sample Destructive Additive Inspected6 100 x x 8 * 100 ml7 200 x 2 * 1 kgThe destroyed quantity now consists of 2200 ml and 4 kg, which is rounded off to 7 pieces.When you make the usage decision, the system proposes 1 piece to be posted to sample usage, since 6 pieces have already been posted to sample usage.NoteYou can use user exit QEVA0009 to individually calculate and predefine the quantity to be posted to sample usage.
    
    Parameters:
    
    inspSpecIsDestructive - You set this indicator for inspection characteristics whose inspection samples will be destroyed when you inspect the characteristics.
  - setInspSpecResultCalculation
```
public void setInspSpecResultCalculation(@Nullable
                                         String inspSpecResultCalculation)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecResultCalculation
    
    You set this indicator if the inspection result for an inspection characteristic is not determined through the inspection of this characteristic, but on the basis of calculations using the inspection results of other characteristics within the same operation.The SAP system supports the following functions:ABS Absolute amountNOT NegationSIN Sine functionCOS Cosine functionTAN Tangent functionLOG Logarithm for base value e (Natural logarithm)EXP Exponential function for base value eSQRT Square root functionROUND Rounding up to the whole numberTRUNC Proportion of whole numbers for a real numberMOD Modulo methodDIV Proportion of whole numbers for a divisionThe operating factors supported by the SAP system are divided into 6 levels based on their order of precedence. The operating factors in level 0 form the weakest combinations; those in level 6 the strongest. The following operating factors are available for calculation:Level 0AND Logical ANDOR Logical ORLevel 1= Equality<>, >< Inequality< Less than> Greater than<=, =< Less than or equal toLevel 2+ Positive sign (of an expression)- Negative sign (of an expression)+ Addition- SubtractionLevel 3* Multiplication/ DivisionLevel 4** ExponentiationLevel 5ABS Absolute amountNOT Negation (of a logical statement)Level 6All other functionsUser-defined formulasThe SAP system also evaluates user-defined functions that are defined in a table.
    
    Parameters:
    
    inspSpecResultCalculation - The indicator defines the characteristic as a calculated characteristic.
  - setInspSpecIsSamplingProcedRqd
```
public void setInspSpecIsSamplingProcedRqd(@Nullable
                                           String inspSpecIsSamplingProcedRqd)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsSamplingProcedRqd
    
    If you do not assign a sampling procedure to the inspection characteristic and you do not define specifications for the inspection scope on a higher level (in the inspection setup in the Quality Management view of the material master), a 100% inspection takes place.In a 100% inspection, the unit of measure in the inspection lot or the unit of measure in the task list plays a role in determining the sample size.
    
    Parameters:
    
    inspSpecIsSamplingProcedRqd - If you set this indicator, a sampling procedure must be assigned to the characteristic in the task list.
  - setInspSpecIsScrapRelevant
```
public void setInspSpecIsScrapRelevant(@Nullable
                                       String inspSpecIsScrapRelevant)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsScrapRelevant
    
    When making the usage decision, if you use a quality score that is calculated from the share of scrap in the inspection lot or characteristic, the characteristic is only used to calculate the quality score if this indicator is set.
    
    Parameters:
    
    inspSpecIsScrapRelevant - If you set this indicator, the fraction of nonconforming units for this inspection characteristic is taken into account when the share of scrap is calculated in the inspection lot.
  - setInspSpecHasFixedCtrlIndicators
```
public void setInspSpecHasFixedCtrlIndicators(@Nullable
                                              String inspSpecHasFixedCtrlIndicators)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasFixedCtrlIndicators
    
    Parameters:
    
    inspSpecHasFixedCtrlIndicators - Set this indicator to specify that the control indicators that were defined for the inspection characteristic using a control key cannot be changed.
  - setInspSpecIsTestEquipmentRqd
```
public void setInspSpecIsTestEquipmentRqd(@Nullable
                                          String inspSpecIsTestEquipmentRqd)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsTestEquipmentRqd
    
    If you do not make an assignment, the system displays a warning message.
    
    Parameters:
    
    inspSpecIsTestEquipmentRqd - If you set this indicator, you can assign test equipment to the inspection characteristic in the task list.
  - setInspSpecIsDefectsRecgAutomatic
```
public void setInspSpecIsDefectsRecgAutomatic(@Nullable
                                              String inspSpecIsDefectsRecgAutomatic)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsDefectsRecgAutomatic
    
    Defects recording in the backgroundA prerequisite for recording defects in the background is that you must define defect codes in the inspection characteristic.You can specify three defect codes for a quantitative characteristic:A defect code for a general rejectionA defect code for a rejection at an upper specification limitA defect code for a rejection at a lower specification limitIn the case of a qualitative characteristic, you must define the defect code for a general rejection.Defects recording in dialogDefects recording is always executed in dialog for the following cases:If the system does not set a default defect codeIf the confirmation profile contains fields that require an entryWhen you record results using a subsystem, you can only record defects automatically in the background.
    
    Parameters:
    
    inspSpecIsDefectsRecgAutomatic - If you set this indicator and an inspection characteristic is rejected during results recording, the function for recording defects for a characteristic is automatically called up. In this situation, a distinction must be made between the following cases:
  - setInspSpecIsChgDocRequired
```
public void setInspSpecIsChgDocRequired(@Nullable
                                        String inspSpecIsChgDocRequired)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsChgDocRequired
    
    The change documents are only created when editing of the inspection characteristic is completed (status 5) or the indicator for the immediate creation of change documents is set.In any case, the prerequisite for creating the documents is saving to the database.
    
    Parameters:
    
    inspSpecIsChgDocRequired - If you set this indicator, change documents are created for this inspection characteristic when results are recorded based on characteristics.
  - setInspSpecIsControlChartUsed
```
public void setInspSpecIsControlChartUsed(@Nullable
                                          String inspSpecIsControlChartUsed)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsControlChartUsed
    
    If you set this indicator, you must also set the "Sampling procedure" indicator.You must then enter an SPC criterion and a sampling procedure with a control chart type in the task list for the SPC characteristic.
    
    Parameters:
    
    inspSpecIsControlChartUsed - If you set this indicator, a control chart is run for this characteristic.
  - setInspSpecPrintControl
```
public void setInspSpecPrintControl(@Nullable
                                    String inspSpecPrintControl)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecPrintControl
    
    Parameters:
    
    inspSpecPrintControl - Print
  - setInspToleranceSpecification
```
public void setInspToleranceSpecification(@Nullable
                                          String inspToleranceSpecification)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspToleranceSpecification
    
    This key can contain the target value, unit of measurement, accuracy, and tolerance limits.If you use a tolerance key in an inspection characteristic, the information contained in the key is copied into the inspection characteristic.
    
    Parameters:
    
    inspToleranceSpecification - User-defined key for tolerance specifications.
  - setInspSpecDecimalPlaces
```
public void setInspSpecDecimalPlaces(@Nullable
                                     Short inspSpecDecimalPlaces)
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecDecimalPlaces
    
    Parameters:
    
    inspSpecDecimalPlaces - In this field, you define the accuracy (number of decimal places), to which the value is calculated.
  - setInspectionSpecificationUnit
```
public void setInspectionSpecificationUnit(@Nullable
                                           String inspectionSpecificationUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspectionSpecificationUnit
    
    Parameters:
    
    inspectionSpecificationUnit - Three-digit unit of measurement for inspection values (target value, specification limits, etc.) for a quantitative characteristic or for dependent characteristic specifications for a quantitative characteristic. The values are stored in the in this unit of measure in the database.
  - setInspSpecTargetValue
```
public void setInspSpecTargetValue(@Nullable
                                   Double inspSpecTargetValue)
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecTargetValue
    
    The target value of the characteristic is stored in this field. A target value can be, for example, a nominal value or the desired value of a technical procedure. Details of the target value are especially useful in evaluations.
    
    Parameters:
    
    inspSpecTargetValue - Value of a quantitative characteristic, from which the actual value of the inspection characteristic should deviate as little as possible.
  - setInspSpecHasTargetValue
```
public void setInspSpecHasTargetValue(@Nullable
                                      String inspSpecHasTargetValue)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasTargetValue
    
    If this indicator is set, then the value of the corresponding numeric field is not initial.
    
    Parameters:
    
    inspSpecHasTargetValue - For every numeric field there is a corresponding field that denotes whether the value is initial or not, in order to differentiate between null and the initial value.
  - setInspSpecUpperLimit
```
public void setInspSpecUpperLimit(@Nullable
                                  Double inspSpecUpperLimit)
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecUpperLimit
    
    The actual value for an inspection characteristic can be one of the following values, depending on the recording form:Mean value of summarized measured valuesSingle measured valueClass size for a value classIndividual measured values that lie above this specification limit, or value classes whose class limits are above this limiting value, are valuated as "not OK" or "R" (rejected).Mean values that lie above this specification limit are also valuated as "not OK," provided the valuation of the inspection characteristic or sample is planned on the basis of specification limits.
    
    Parameters:
    
    inspSpecUpperLimit - Upper limit value for the actual value of an inspection characteristic.
  - setInspSpecLowerLimit
```
public void setInspSpecLowerLimit(@Nullable
                                  Double inspSpecLowerLimit)
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecLowerLimit
    
    The actual value for an inspection characteristic can be one of the following values, depending on the recording form:Mean value of summarized measured valuesSingle measured valueClass size for a value classIndividual measured values that lie below this specification limit, or value classes whose class limits are below this specification limit, are valuated as "not OK" or "R" (rejected).Mean values that lie below this specification limit are also valuated as "not OK," provided that the valuation of the inspection characteristic or sample is planned on the basis of specification limits.
    
    Parameters:
    
    inspSpecLowerLimit - Lower limiting value for the actual value of an inspection characteristic.
  - setInspSpecHasLowerLimit
```
public void setInspSpecHasLowerLimit(@Nullable
                                     String inspSpecHasLowerLimit)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasLowerLimit
    
    If this indicator is set, then the value of the corresponding numeric field is not initial.
    
    Parameters:
    
    inspSpecHasLowerLimit - For every numeric field there is a corresponding field that denotes whether the value is initial or not, in order to differentiate between null and the initial value.
  - setInspSpecHasUpperLimit
```
public void setInspSpecHasUpperLimit(@Nullable
                                     String inspSpecHasUpperLimit)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasUpperLimit
    
    If this indicator is set, then the value of the corresponding numeric field is not initial.
    
    Parameters:
    
    inspSpecHasUpperLimit - For every numeric field there is a corresponding field that denotes whether the value is initial or not, in order to differentiate between null and the initial value.
  - setInspSpecDefectCodeGrpRejection
```
public void setInspSpecDefectCodeGrpRejection(@Nullable
                                              String inspSpecDefectCodeGrpRejection)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecDefectCodeGrpRejection
    
    The code group and code defined here are used during results recording if the inspection characteristic is rejected or the sample is used to:Determine the defect classGenerate the defect data recordThis is the case if no alternative codes for a rejection with reference to an upper or lower specification limit are maintained.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.NoteIf the control indicator for defects recording is set and you do not enter the code group and code, a warning is issued when the data is maintained.If the inspection characteristic or sample is rejected during results recording, the manual defects recording function is called up automatically.
    
    Parameters:
    
    inspSpecDefectCodeGrpRejection - Code group from the defect catalog (catalog type 9) that is assigned to an inspection characteristic.
  - setInspSpecDefectCodeRejection
```
public void setInspSpecDefectCodeRejection(@Nullable
                                           String inspSpecDefectCodeRejection)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecDefectCodeRejection
    
    The code group and code defined here are used during results recording if the inspection characteristic is rejected or the sample is used to:Determine the defect classGenerate the defect data recordThis is the case if no alternative codes for a rejection with reference to an upper or lower specification limit are maintained.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.NoteIf the control indicator for defects recording is set and you do not enter the code group and code, a warning is issued when the data is maintained.If the inspection characteristic or sample is rejected during results recording, the manual defects recording function is called up automatically.
    
    Parameters:
    
    inspSpecDefectCodeRejection - Code from a code group in the defect catalog (catalog type 9) that is assigned to an inspection characteristic.
  - setInspSpecDefectCodeGrpRjcnUpper
```
public void setInspSpecDefectCodeGrpRjcnUpper(@Nullable
                                              String inspSpecDefectCodeGrpRjcnUpper)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecDefectCodeGrpRjcnUpper
    
    This code group and code are used, if the inspection characteristic or sample is rejected on the basis of an upper specification limit during results recording.A rejection on the basis of an upper specification limit can occur when you make a:Valuation based on the specification limits with and without an acceptance factorValuation based on the action limits of a mean value chartYou can only make an entry in this field for quantitative characteristics, for which the control indicator for the upper specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If you do not enter a code group and code for the inspection characteristic and it is rejected at the upper specification limit, the code for a general rejection will be used during results recording if the inspection characteristic or sample is rejected.If the control indicator for defects recording is set for the inspection characteristic in the task list or for the master inspection characteristic, exactly one defect data record will always be created in the event of a rejection.
    
    Parameters:
    
    inspSpecDefectCodeGrpRjcnUpper - Code group from the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with an upper specification limit.
  - setInspSpecDefectCodeRjcnUpper
```
public void setInspSpecDefectCodeRjcnUpper(@Nullable
                                           String inspSpecDefectCodeRjcnUpper)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecDefectCodeRjcnUpper
    
    The code group and code are used if the inspection characteristic or sample is rejected on the basis of an upper specification limit during results recording.Such a rejection on the basis of an upper specification limit can occur when you make a:Valuation based on the specification limits with and without acceptance factorValuation according to the action limits of a mean value chartYou can only make an entry in this field for a quantitative characteristic, for which the control indicator for the upper specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If the control indicator for defects recording is set in the inspection characteristic, exactly one defect data record is always created in the event of a rejection. The defect code for a rejection at the upper specification limit takes precedence over the defect code for a general rejection. If you do not enter a code group or code for a rejection at the upper specification limit for the inspection characteristic, the code for a general rejection is used during results recording if the inspection characteristic or sample is rejected.
    
    Parameters:
    
    inspSpecDefectCodeRjcnUpper - Code from a code group in the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with an upper specification limit.
  - setInspSpecDefectCodeGrpRjcnLower
```
public void setInspSpecDefectCodeGrpRjcnLower(@Nullable
                                              String inspSpecDefectCodeGrpRjcnLower)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecDefectCodeGrpRjcnLower
    
    The code group and code are used during results recording if the inspection characteristic or sample is rejected on the basis of a lower specification limit.Such a rejection on the basis of a lower specification limit can occur when you make a:Valuation based on specification limits with and without an acceptance factorValuation according to the action limits of a mean value chartYou can only make an entry in this field for a quantitative characteristic, for which the control indicator for the lower specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If you do not enter a code group or code for a rejection of the inspection characteristic at the lower specification limit, the code for a general rejection will be used during results recording if the inspection characteristic or sample is rejected.If the control indicator for defects recording is set for the inspection characteristic in the task list or for the master inspection characteristic, exactly one defect data record will always be created in the event of a rejection.
    
    Parameters:
    
    inspSpecDefectCodeGrpRjcnLower - Code group from the defect catalog (catalog type 9) that was assigned to a quantitative characteristic with a lower specification limit.
  - setInspSpecDefectCodeRjcnLower
```
public void setInspSpecDefectCodeRjcnLower(@Nullable
                                           String inspSpecDefectCodeRjcnLower)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecDefectCodeRjcnLower
    
    The code group and code are used if the inspection characteristic or sample is rejected on the basis of a lower specification limit during results recording.Such a rejection on the basis of a lower specification limit can occur when you make a:Valuation based on the specification limits with and without acceptance factorValuation according to the action limits of a mean value chartYou can only make an entry in this field for a quantitative characteristic, for which the control indicator for the lower specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If the control indicator for defects recording is set in the inspection characteristic, exactly one defect data record will always be created in the event of a rejection. The defect code for a rejection at the lower specification limit takes precedence over the defect code for a general rejection. If you do not enter a code group or a code for a rejection at the lower specification limit , the code for a general rejection is used during results recording if the inspection characteristic or sample is rejected.
    
    Parameters:
    
    inspSpecDefectCodeRjcnLower - Code from a code group in the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with a lower specification limit.
  - setSelectedCodeSet
```
public void setSelectedCodeSet(@Nullable
                               String selectedCodeSet)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SelectedCodeSet
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    selectedCodeSet - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setSelectedCodeSetPlant
```
public void setSelectedCodeSetPlant(@Nullable
                                    String selectedCodeSetPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SelectedCodeSetPlant
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Parameters:
    
    selectedCodeSetPlant - Key that uniquely identifies the plant assigned to the selected set.
  - setInspSpecAdditionalCatalog2
```
public void setInspSpecAdditionalCatalog2(@Nullable
                                          String inspSpecAdditionalCatalog2)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog2
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Parameters:
    
    inspSpecAdditionalCatalog2 - Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - setInspSpecAdditionalSelectedSet2
```
public void setInspSpecAdditionalSelectedSet2(@Nullable
                                              String inspSpecAdditionalSelectedSet2)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet2
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalSelectedSet2 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAdditionalCodeGroup2
```
public void setInspSpecAdditionalCodeGroup2(@Nullable
                                            String inspSpecAdditionalCodeGroup2)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup2
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalCodeGroup2 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAddlSeldCodeSetPlant2
```
public void setInspSpecAddlSeldCodeSetPlant2(@Nullable
                                             String inspSpecAddlSeldCodeSetPlant2)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant2
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Parameters:
    
    inspSpecAddlSeldCodeSetPlant2 - Key that uniquely identifies the plant assigned to the selected set.
  - setInspSpecAdditionalCatalog3
```
public void setInspSpecAdditionalCatalog3(@Nullable
                                          String inspSpecAdditionalCatalog3)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog3
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Parameters:
    
    inspSpecAdditionalCatalog3 - Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - setInspSpecAdditionalSelectedSet3
```
public void setInspSpecAdditionalSelectedSet3(@Nullable
                                              String inspSpecAdditionalSelectedSet3)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet3
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalSelectedSet3 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAdditionalCodeGroup3
```
public void setInspSpecAdditionalCodeGroup3(@Nullable
                                            String inspSpecAdditionalCodeGroup3)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup3
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalCodeGroup3 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAddlSeldCodeSetPlant3
```
public void setInspSpecAddlSeldCodeSetPlant3(@Nullable
                                             String inspSpecAddlSeldCodeSetPlant3)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant3
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Parameters:
    
    inspSpecAddlSeldCodeSetPlant3 - Key that uniquely identifies the plant assigned to the selected set.
  - setInspSpecAdditionalCatalog4
```
public void setInspSpecAdditionalCatalog4(@Nullable
                                          String inspSpecAdditionalCatalog4)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog4
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Parameters:
    
    inspSpecAdditionalCatalog4 - Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - setInspSpecAdditionalSelectedSet4
```
public void setInspSpecAdditionalSelectedSet4(@Nullable
                                              String inspSpecAdditionalSelectedSet4)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet4
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalSelectedSet4 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAdditionalCodeGroup4
```
public void setInspSpecAdditionalCodeGroup4(@Nullable
                                            String inspSpecAdditionalCodeGroup4)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup4
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalCodeGroup4 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAddlSeldCodeSetPlant4
```
public void setInspSpecAddlSeldCodeSetPlant4(@Nullable
                                             String inspSpecAddlSeldCodeSetPlant4)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant4
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Parameters:
    
    inspSpecAddlSeldCodeSetPlant4 - Key that uniquely identifies the plant assigned to the selected set.
  - setInspSpecAdditionalCatalog5
```
public void setInspSpecAdditionalCatalog5(@Nullable
                                          String inspSpecAdditionalCatalog5)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog5
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Parameters:
    
    inspSpecAdditionalCatalog5 - Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - setInspSpecAdditionalSelectedSet5
```
public void setInspSpecAdditionalSelectedSet5(@Nullable
                                              String inspSpecAdditionalSelectedSet5)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet5
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalSelectedSet5 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAdditionalCodeGroup5
```
public void setInspSpecAdditionalCodeGroup5(@Nullable
                                            String inspSpecAdditionalCodeGroup5)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup5
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Parameters:
    
    inspSpecAdditionalCodeGroup5 - If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - setInspSpecAddlSeldCodeSetPlant5
```
public void setInspSpecAddlSeldCodeSetPlant5(@Nullable
                                             String inspSpecAddlSeldCodeSetPlant5)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant5
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Parameters:
    
    inspSpecAddlSeldCodeSetPlant5 - Key that uniquely identifies the plant assigned to the selected set.
  - setSamplingProcedure
```
public void setSamplingProcedure(@Nullable
                                 String samplingProcedure)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SamplingProcedure
    
    In the sampling procedure, the valuation mode is also defined for the inspection result.A sampling procedure is assigned to an inspection characteristic in a task list or material specification. In addition, you can assign the procedure to an unplanned characteristic, when you record results.If you do not enter a sampling procedure for an inspection characteristic, the system chooses a sampling procedure proposed in the settings at plant level. If no sampling procedure was entered in these settings, the system takes the lot size as the sample size.
    
    Parameters:
    
    samplingProcedure - Procedure by which the sample size for an inspection is determined.
  - setInspCharacteristicSampleUnit
```
public void setInspCharacteristicSampleUnit(@Nullable
                                            String inspCharacteristicSampleUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspCharacteristicSampleUnit
    
    The unit in which a sample is measured.To permit this unit of measure to be converted into the material unit of measure when the system selects the inspection specifications for an inspection lot, you must have maintained the conversion factors in the material master record100 ml are needed to inspect a characteristic. In this case, the sample unit of measure is ml.
    
    Parameters:
    
    inspCharacteristicSampleUnit - The base unit of measure that is used to determine a sample for a characteristic.
  - setBOOCharcSampleQuantity
```
public void setBOOCharcSampleQuantity(@Nullable
                                      BigDecimal bOOCharcSampleQuantity)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: BOOCharcSampleQuantity
    
    The sample unit is the product of the following factors: Base sample quantity and the sample unit of measure.To inspect a characteristic, 100 ml are needed. In this case:Sample unit of measure = mlBase sample quantity = 100Sample unit = 100mlIf the sampling procedure that is defined for the characteristic stipulates that 5 individual samples are needed, the sample unit is multiplied by five. As a result, 5 x 100 ml must be drawn to inspect this characteristic.Sample quantity = 500 ml
    
    Parameters:
    
    bOOCharcSampleQuantity - Factor for calculating the sample unit.
  - setInspSpecInformationField1
```
public void setInspSpecInformationField1(@Nullable
                                         String inspSpecInformationField1)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspSpecInformationField1
    
    Parameters:
    
    inspSpecInformationField1 - This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object, such as an inspection method or a master inspection characteristic.
  - setInspSpecInformationField2
```
public void setInspSpecInformationField2(@Nullable
                                         String inspSpecInformationField2)
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: InspSpecInformationField2
    
    Parameters:
    
    inspSpecInformationField2 - This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object, such as an inspection method or a master inspection characteristic.
  - setInspSpecInformationField3
```
public void setInspSpecInformationField3(@Nullable
                                         String inspSpecInformationField3)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: InspSpecInformationField3
    
    Parameters:
    
    inspSpecInformationField3 - This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object, such as an inspection method or a master inspection characteristic.
  - setInspectionSpecificationText
```
public void setInspectionSpecificationText(@Nullable
                                           String inspectionSpecificationText)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: InspectionSpecificationText
    
    Parameters:
    
    inspectionSpecificationText - Text of up to 40 characters that describes the object in more detail. This description is also known as short text.
  - 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 user who created the record.
  - 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 the 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 the user who made the last change to this data record.
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    The system enters the current system date.
    
    Parameters:
    
    lastChangeDate - Date on which the data record was last changed.
  - setBillOfOperationsVersion
```
public void setBillOfOperationsVersion(@Nullable
                                       String billOfOperationsVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfOperationsVersion
    
    Parameters:
    
    billOfOperationsVersion - A routing version is a consistent model of a product's operations and operation activities. You can make changes to a new routing version until it is released. Released routing versions can be used in production execution and cannot be changed. If you want to make changes to a routing version, you can create a new routing version and then you can make the necessary changes.
  - 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()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Specified by:
    
    getEntityCollection in class VdmEntity<InspPlanOpCharacteristic>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<InspPlanOpCharacteristic>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<InspPlanOpCharacteristic>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<InspPlanOpCharacteristic>
  - field
```
@Nonnull
public static <T> InspPlanOpCharacteristicField<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> InspPlanOpCharacteristicField<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<InspPlanOpCharacteristic>
    
    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<InspPlanOpCharacteristic>
  - 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<InspPlanOpCharacteristic>
    
    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()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Overrides:
    
    getDefaultServicePath in class VdmEntity<InspPlanOpCharacteristic>
    
    Returns:
    
    Default context path to the OData service. In other words, everything in between the protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)
  - builder
```
@Nonnull
public static InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder builder()
```
  - getInspectionPlanGroup
```
@Nullable
public String getInspectionPlanGroup()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionPlanGroup
    
    You can use groups, for instance, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
    
    Returns:
    
    Key identifying a group.
  - getBOOOperationInternalID
```
@Nullable
public String getBOOOperationInternalID()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOOperationInternalID
    
    Returns:
    
    Number of the Task List Node
  - getBOOCharacteristic
```
@Nullable
public String getBOOCharacteristic()
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BOOCharacteristic
    
    Returns:
    
    The number that explicitly identifies an inspection characteristic within an operation in an inspection plan.
  - getBOOCharacteristicVersion
```
@Nullable
public String getBOOCharacteristicVersion()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOCharacteristicVersion
    
    Returns:
    
    Identifies the activity posting.
  - getBOOOpInternalVersionCounter
```
@Nullable
public String getBOOOpInternalVersionCounter()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOOpInternalVersionCounter
    
    Returns:
    
    Identifies the activity posting.
  - getInspectionPlanInternalVersion
```
@Nullable
public String getInspectionPlanInternalVersion()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionPlanInternalVersion
    
    Returns:
    
    Identifies the activity posting.
  - getInspectionPlan
```
@Nullable
public String getInspectionPlan()
```
    (Key Field) Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InspectionPlan
    
    In Production Planning and Control, for example, it serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.The group counter can be used to identify different lot-size ranges, for example.
    
    Returns:
    
    This key and the task list group uniquely identify a task list.
  - getValidityStartDate
```
@Nullable
public LocalDateTime getValidityStartDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityStartDate
    
    Returns:
    
    Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - getValidityEndDate
```
@Nullable
public LocalDateTime getValidityEndDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityEndDate
    
    Returns:
    
    End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - getChangeNumber
```
@Nullable
public String getChangeNumber()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ChangeNumber
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getIsDeleted
```
@Nullable
public Boolean getIsDeleted()
```
    Constraints: none
    Original property name from the Odata EDM: IsDeleted
    
    This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
    
    Returns:
    
    Indicator showing that the BOM header or the BOM item has been deleted with reference to the change number.
  - getBOOOperationPRTInternalID
```
@Nullable
public String getBOOOperationPRTInternalID()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOOOperationPRTInternalID
    
    Returns:
    
    Assigned Test Equipment
  - getInspectionMethod
```
@Nullable
public String getInspectionMethod()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionMethod
    
    An inspection method describes how to inspect an inspection characteristic. You can assign an inspection method to a master inspection characteristic or directly to an inspection characteristic in an inspection plan.
    
    Returns:
    
    Name that uniquely identifies an inspection method within a plant.
  - getInspectionMethodVersion
```
@Nullable
public String getInspectionMethodVersion()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionMethodVersion
    
    Returns:
    
    Version Number of the Inspection Method
  - getInspectionMethodPlant
```
@Nullable
public String getInspectionMethodPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspectionMethodPlant
    
    For inspection methods this plant is the planning plant, in which the inspection method was created in QM.
    
    Returns:
    
    Key, that identifies a plant.
  - getInspSpecImportanceCode
```
@Nullable
public String getInspSpecImportanceCode()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: InspSpecImportanceCode
    
    By choosing the corresponding entry, you can classify the inspection characteristic as a critical characteristic, major characteristic, or minor characteristic.
    
    Returns:
    
    Classification of inspection characteristics according to their weighting (importance).
  - getInspectorQualification
```
@Nullable
public String getInspectorQualification()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: InspectorQualification
    
    This field has no controlling function. However, your entry is checked against a list of qualifications stored in the database.You can enter an inspector qualification in an inspection method, a master inspection characteristic, or a task list.If you use a master inspection characteristic in a task list that has an inspection method assigned, the inspector qualification defined in the inspection method is used in the task list. If there is no inspector qualification in the inspection method, the qualification is taken from the master inspection characteristic.
    
    Returns:
    
    Qualification that an inspector must have and, if necessary, validate in order to be able to conduct an inspection.
  - getInspectionSpecification
```
@Nullable
public String getInspectionSpecification()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspectionSpecification
    
    An inspection characteristic describes what is to be inspected, that is, the inspection requirements for materials, parts, and products. To simplify and standardize inspection planning, you can define master inspection characteristics that you can use in various task lists.
    
    Returns:
    
    Name that uniquely identifies a master inspection characteristic within a plant.
  - getInspectionSpecificationVersion
```
@Nullable
public String getInspectionSpecificationVersion()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionSpecificationVersion
    
    Returns:
    
    Version Number of the Master Inspection Characteristic
  - getInspectionSpecificationPlant
```
@Nullable
public String getInspectionSpecificationPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspectionSpecificationPlant
    
    Returns:
    
    Plant for the Master Inspection Characteristic
  - getBOOCharcHasInspSpecReference
```
@Nullable
public Boolean getBOOCharcHasInspSpecReference()
```
    Constraints: none
    Original property name from the Odata EDM: BOOCharcHasInspSpecReference
    
    Returns:
    
    Boolean Variable (X = True, - = False, Space = Unknown)
  - getInspSpecControlIndicators
```
@Nullable
public String getInspSpecControlIndicators()
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: InspSpecControlIndicators
    
    plan default valuesresults recordinginspection processing
    
    Returns:
    
    A characteristic is defined with this control indicator string. It contains indicators for:
  - getInspSpecIsQuantitative
```
@Nullable
public String getInspSpecIsQuantitative()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsQuantitative
    
    Set the indicator for the characteristic type (quantitative or qualitative) or enter a control key.If you used a control key, for which the "fixed" indicator is set in Customizing, you cannot change the indicator for the characteristic type. In addition, you cannot delete this indicator or enter another control key.
    
    Returns:
    
    If you set this indicator, it causes the characteristic to be treated as a quantitative characteristic. You thereby define the control indicators that are relevant for the inspection characteristic. A quantitative characteristic is subject to measurement inspections. You can define tolerance limits and a target value for a quantitative characteristic.
  - getInspSpecIsMeasuredValueRqd
```
@Nullable
public String getInspSpecIsMeasuredValueRqd()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsMeasuredValueRqd
    
    Returns:
    
    If you set this indicator, measured values for this quantitative characteristic have to be inspected and confirmed.
  - getInspSpecIsSelectedSetRequired
```
@Nullable
public String getInspSpecIsSelectedSetRequired()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsSelectedSetRequired
    
    If you do not set this indicator, the inspection characteristic is marked as an alternative characteristic, that can only take the values "Accepted" or "Rejected".
    
    Returns:
    
    If you set this indicator, the inspection characteristic is marked as an attributive characteristic, whose allowed values are defined as a selected set from catalog 1 (characteristic attributes).
  - getInspSpecIsUpperLimitRequired
```
@Nullable
public String getInspSpecIsUpperLimitRequired()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsUpperLimitRequired
    
    Returns:
    
    If you set this indicator, you must enter an upper specification limit for the inspection characteristic.
  - getInspSpecIsLowerLimitRequired
```
@Nullable
public String getInspSpecIsLowerLimitRequired()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsLowerLimitRequired
    
    Returns:
    
    If you set this indicator, you must enter a lower specification limit for the inspection characteristic.
  - getInspSpecIsTargetValueInLimit
```
@Nullable
public String getInspSpecIsTargetValueInLimit()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsTargetValueInLimit
    
    Returns:
    
    If you set this indicator and either the "Upper specification limit" or "Lower specification limit" indicator, the system checks whether the target value lies within the tolerance.
  - getInspectionScope
```
@Nullable
public String getInspectionScope()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspectionScope
    
    Returns:
    
    With this field you determine the extent, to which the number of required measured values must adhere.
  - getInspSpecIsLongTermInspection
```
@Nullable
public String getInspSpecIsLongTermInspection()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsLongTermInspection
    
    If you set this indicator for at least one required characteristic, you can distinguish between "Short-term inspection completion" and a final completion of the inspection (status: Inspection close completed).Optional characteristics only work as long-term characteristics, when they are set for processing before inspection completion.You activate a long-term inspection by confirming the inspection completion for the short-term characteristics. This occurs either in conjunction with the making of the usage decision, or by calling up the special function "Short-term inspection completed."In a long-term inspection:There can already be a usage decision for the inspected material during the long-term inspectionYou can still record inspection results for long-term characteristics, once you have made the usage decisionThe system sets a separate status in the inspection lot to identify the long-term inspection and it provides special worklists and workflow tasks for this purposeIf you want to copy inspection results from a long-term inspection into a batch valuation, note that the data is transferred when the following events occur:Results from a short-term inspection are transferred as soon as the statuses "Short-term inspection completion" and "Usage decision made" are set.Results from a long-term inspection are transferred as soon as the statuses "Long-term inspection completion" and "Usage decision made" are setThis means that you must confirm or correct a usage decision, if it has been made after a short-term inspection. To do this, use the change transaction, a relevant worklist or an appropriate workflow task.
    
    Returns:
    
    If you set this indicator, the characteristic is subject to a long-term inspection.
  - getInspSpecRecordingType
```
@Nullable
public String getInspSpecRecordingType()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecRecordingType
    
    Returns:
    
    In this field, you define whether and how single characteristic attributes (original values) are to be recorded at inspection results recording. A single value, depending on the inspection characteristic, is a measured value, an attribute code, or the valuation A (accepted) or R (rejected).
  - getInspResultIsDocumentationRqd
```
@Nullable
public String getInspResultIsDocumentationRqd()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspResultIsDocumentationRqd
    
    Returns:
    
    Determines whether and how inspection results are to be documented with additional text when they are recorded.
  - getInspSpecCharcCategory
```
@Nullable
public String getInspSpecCharcCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecCharcCategory
    
    You can make the following entries:Optional characteristicThis characteristic can be inspected, if necessary. You do not have to record results for this characteristic.Conditional characteristic (when the previous characteristic has been accepted)This characteristic must be inspected if the previous required characteristic was accepted.Conditional characteristic (when the previous characteristic has been rejected)This characteristic must be inspected when the previous required characteristic was rejected.Required characteristicThis characteristic must be inspected.
    
    Returns:
    
    In this field you determine if and when a characteristic is inspected.
  - getInspSpecIsSampleQtyAdditive
```
@Nullable
public String getInspSpecIsSampleQtyAdditive()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsSampleQtyAdditive
    
    If a partial sample is to be used for several characteristics, it contains the total sample quantity required for all the characteristics.The system calculates the sample quantity for each characteristic. For a partial sample that is used for several characteristics, the system takes the largest determined sample quantity as the partial sample quantity.If you set the Additive sample indicator, the system does not include the sample quantity for this characteristic when calculating partial samples, but takes the next smallest sample quantity as the partial sample quantity and subsequently adds the sample quantity of the additive sample.You can set the indicator for an additive sample, for example, if the inspection for a characteristic is destructive.I II IIISample quantity Additive Additive AdditiveCharacteristic 1 15 pcs (X)Characteristic 2 30 pcs X XCharacteristic 3 20 pcs XTotal qty 30 pcs 50 pcs 65 pcsExample I: No indicator for additive samples is set. The system therefore determines the sample quantity for characteristic 2 as the quantity for the partial sample.Example II: The indicator for additive samples is set for characteristic 2. The system therefore determines the sample quantity of characteristic 3 as the quantity for the partial sample and increases this by the sample size of characteristic 2.Example III: The indicator for additive samples is set for characteristics 2 and 3. The system therefore determines the sample quantity of characteristic 1 as the quantity for the partial sample and increases this by the sample sizes of characteristics 2 and 3, irrespective of whether the indicator was also set for characteristic 1.
    
    Returns:
    
    If you set this indicator, it causes the size of the partial sample to be increased by the quantity required for this characteristic in inspection sample calculation.
  - getInspSpecIsDestructive
```
@Nullable
public String getInspSpecIsDestructive()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsDestructive
    
    When you make the usage decision, the system calculates the quantity of materials destroyed and makes a proposal for the stock posting To sample usage. The system takes all inspection characteristics into consideration corresponding to the actual sample size for which the indicator Destructive insp. is set and for which inspection results have been recorded (up to the point of the calculation). This may include optional characteristics, skipped characteristics, long-term characteristics, and unplanned characteristics.For the stock posting, the system proposes only the part of the destroyed quantity that exceeds the amount already posted to sample usage.For example, you set the indicator for an additive sample if the inspection of an inspection characteristic is destructive. In this case, the indicator causes the sample quantity to be increased by the amount needed to inspect this characteristic.If you inspect only one inspection characteristic destructively and you inspect this characteristic last, you should not set the indicator Additive sample for the characteristic.You must set the indicator Additive sample if you inspect more than one inspection characteristic destructively and if you can only inspect one of these characteristics for a partial sample.If several characteristics contribute to the destruction of the inspection sample, you can combine these characteristics for a partial sample.A simple exampleFour characteristics are inspected. The inspection of characteristics 1, 3, and 4 is destructive. The indicator Additive sample was set for characteristic 4.Charac. Destructive Additive To be insp. Inspected1 x 10 * 1 pc 5 * 1 pc2 10 * 1 pc 10 * 1 pc3 x 10 * 1 pc 10 * 1 pc4 x x 4 * 12 pc 5 * 12 pcIn calculating the destroyed quantity, the system only considers the actual inspected sample size specified in results recording ("Inspected" column) and not the sample quantity to be inspected specified in the inspection instruction ("To be inspected" column).When you make the usage decision, the system determines a destroyed quantity of 70 pieces and proposes they be posted to sample usage. Characteristics 1 and 3 are combined, since they are not marked as additive.Extended example with material samples, long-term characteristics, and different units of measureThe unit of measure for the lot is PIECES; the following conversion factors are stored in the material master record:4 pieces = 3 l8 pieces = 9 kgIn the inspection plan, it is defined that characteristics 1, 3, 4, and 6 (material sample 100) are to be inspected in laboratory 1 and characteristics 2, 5, and 7 in laboratory 2 (material sample 200).Charac. Mat.Sample Destructive Additive Inspected1 100 x x 5 * 100 ml2 200 x 1 * 1 kg3 100 x x 5 * 100 ml4 100 x x 4 * 100 ml5 200 x 4 * 1 kg6 100 x x ----7 200 x ----After inspecting characteristics 1 through 5, the destructive quantity consists of 1400 ml and 4 kg, which is rounded off to 6 pieces. When you make the usage decision, the system proposes that 6 pieces be posted to sample usage.You then record the results for long-term characteristics 6 and 7 and change the usage decision.Charac. Mat.Sample Destructive Additive Inspected6 100 x x 8 * 100 ml7 200 x 2 * 1 kgThe destroyed quantity now consists of 2200 ml and 4 kg, which is rounded off to 7 pieces.When you make the usage decision, the system proposes 1 piece to be posted to sample usage, since 6 pieces have already been posted to sample usage.NoteYou can use user exit QEVA0009 to individually calculate and predefine the quantity to be posted to sample usage.
    
    Returns:
    
    You set this indicator for inspection characteristics whose inspection samples will be destroyed when you inspect the characteristics.
  - getInspSpecResultCalculation
```
@Nullable
public String getInspSpecResultCalculation()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecResultCalculation
    
    You set this indicator if the inspection result for an inspection characteristic is not determined through the inspection of this characteristic, but on the basis of calculations using the inspection results of other characteristics within the same operation.The SAP system supports the following functions:ABS Absolute amountNOT NegationSIN Sine functionCOS Cosine functionTAN Tangent functionLOG Logarithm for base value e (Natural logarithm)EXP Exponential function for base value eSQRT Square root functionROUND Rounding up to the whole numberTRUNC Proportion of whole numbers for a real numberMOD Modulo methodDIV Proportion of whole numbers for a divisionThe operating factors supported by the SAP system are divided into 6 levels based on their order of precedence. The operating factors in level 0 form the weakest combinations; those in level 6 the strongest. The following operating factors are available for calculation:Level 0AND Logical ANDOR Logical ORLevel 1= Equality<>, >< Inequality< Less than> Greater than<=, =< Less than or equal toLevel 2+ Positive sign (of an expression)- Negative sign (of an expression)+ Addition- SubtractionLevel 3* Multiplication/ DivisionLevel 4** ExponentiationLevel 5ABS Absolute amountNOT Negation (of a logical statement)Level 6All other functionsUser-defined formulasThe SAP system also evaluates user-defined functions that are defined in a table.
    
    Returns:
    
    The indicator defines the characteristic as a calculated characteristic.
  - getInspSpecIsSamplingProcedRqd
```
@Nullable
public String getInspSpecIsSamplingProcedRqd()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsSamplingProcedRqd
    
    If you do not assign a sampling procedure to the inspection characteristic and you do not define specifications for the inspection scope on a higher level (in the inspection setup in the Quality Management view of the material master), a 100% inspection takes place.In a 100% inspection, the unit of measure in the inspection lot or the unit of measure in the task list plays a role in determining the sample size.
    
    Returns:
    
    If you set this indicator, a sampling procedure must be assigned to the characteristic in the task list.
  - getInspSpecIsScrapRelevant
```
@Nullable
public String getInspSpecIsScrapRelevant()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsScrapRelevant
    
    When making the usage decision, if you use a quality score that is calculated from the share of scrap in the inspection lot or characteristic, the characteristic is only used to calculate the quality score if this indicator is set.
    
    Returns:
    
    If you set this indicator, the fraction of nonconforming units for this inspection characteristic is taken into account when the share of scrap is calculated in the inspection lot.
  - getInspSpecHasFixedCtrlIndicators
```
@Nullable
public String getInspSpecHasFixedCtrlIndicators()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasFixedCtrlIndicators
    
    Returns:
    
    Set this indicator to specify that the control indicators that were defined for the inspection characteristic using a control key cannot be changed.
  - getInspSpecIsTestEquipmentRqd
```
@Nullable
public String getInspSpecIsTestEquipmentRqd()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsTestEquipmentRqd
    
    If you do not make an assignment, the system displays a warning message.
    
    Returns:
    
    If you set this indicator, you can assign test equipment to the inspection characteristic in the task list.
  - getInspSpecIsDefectsRecgAutomatic
```
@Nullable
public String getInspSpecIsDefectsRecgAutomatic()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsDefectsRecgAutomatic
    
    Defects recording in the backgroundA prerequisite for recording defects in the background is that you must define defect codes in the inspection characteristic.You can specify three defect codes for a quantitative characteristic:A defect code for a general rejectionA defect code for a rejection at an upper specification limitA defect code for a rejection at a lower specification limitIn the case of a qualitative characteristic, you must define the defect code for a general rejection.Defects recording in dialogDefects recording is always executed in dialog for the following cases:If the system does not set a default defect codeIf the confirmation profile contains fields that require an entryWhen you record results using a subsystem, you can only record defects automatically in the background.
    
    Returns:
    
    If you set this indicator and an inspection characteristic is rejected during results recording, the function for recording defects for a characteristic is automatically called up. In this situation, a distinction must be made between the following cases:
  - getInspSpecIsChgDocRequired
```
@Nullable
public String getInspSpecIsChgDocRequired()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsChgDocRequired
    
    The change documents are only created when editing of the inspection characteristic is completed (status 5) or the indicator for the immediate creation of change documents is set.In any case, the prerequisite for creating the documents is saving to the database.
    
    Returns:
    
    If you set this indicator, change documents are created for this inspection characteristic when results are recorded based on characteristics.
  - getInspSpecIsControlChartUsed
```
@Nullable
public String getInspSpecIsControlChartUsed()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecIsControlChartUsed
    
    If you set this indicator, you must also set the "Sampling procedure" indicator.You must then enter an SPC criterion and a sampling procedure with a control chart type in the task list for the SPC characteristic.
    
    Returns:
    
    If you set this indicator, a control chart is run for this characteristic.
  - getInspSpecPrintControl
```
@Nullable
public String getInspSpecPrintControl()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecPrintControl
    
    Returns:
    
    Print
  - getInspToleranceSpecification
```
@Nullable
public String getInspToleranceSpecification()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspToleranceSpecification
    
    This key can contain the target value, unit of measurement, accuracy, and tolerance limits.If you use a tolerance key in an inspection characteristic, the information contained in the key is copied into the inspection characteristic.
    
    Returns:
    
    User-defined key for tolerance specifications.
  - getInspSpecDecimalPlaces
```
@Nullable
public Short getInspSpecDecimalPlaces()
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecDecimalPlaces
    
    Returns:
    
    In this field, you define the accuracy (number of decimal places), to which the value is calculated.
  - getInspectionSpecificationUnit
```
@Nullable
public String getInspectionSpecificationUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspectionSpecificationUnit
    
    Returns:
    
    Three-digit unit of measurement for inspection values (target value, specification limits, etc.) for a quantitative characteristic or for dependent characteristic specifications for a quantitative characteristic. The values are stored in the in this unit of measure in the database.
  - getInspSpecTargetValue
```
@Nullable
public Double getInspSpecTargetValue()
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecTargetValue
    
    The target value of the characteristic is stored in this field. A target value can be, for example, a nominal value or the desired value of a technical procedure. Details of the target value are especially useful in evaluations.
    
    Returns:
    
    Value of a quantitative characteristic, from which the actual value of the inspection characteristic should deviate as little as possible.
  - getInspSpecHasTargetValue
```
@Nullable
public String getInspSpecHasTargetValue()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasTargetValue
    
    If this indicator is set, then the value of the corresponding numeric field is not initial.
    
    Returns:
    
    For every numeric field there is a corresponding field that denotes whether the value is initial or not, in order to differentiate between null and the initial value.
  - getInspSpecUpperLimit
```
@Nullable
public Double getInspSpecUpperLimit()
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecUpperLimit
    
    The actual value for an inspection characteristic can be one of the following values, depending on the recording form:Mean value of summarized measured valuesSingle measured valueClass size for a value classIndividual measured values that lie above this specification limit, or value classes whose class limits are above this limiting value, are valuated as "not OK" or "R" (rejected).Mean values that lie above this specification limit are also valuated as "not OK," provided the valuation of the inspection characteristic or sample is planned on the basis of specification limits.
    
    Returns:
    
    Upper limit value for the actual value of an inspection characteristic.
  - getInspSpecLowerLimit
```
@Nullable
public Double getInspSpecLowerLimit()
```
    Constraints: none
    Original property name from the Odata EDM: InspSpecLowerLimit
    
    The actual value for an inspection characteristic can be one of the following values, depending on the recording form:Mean value of summarized measured valuesSingle measured valueClass size for a value classIndividual measured values that lie below this specification limit, or value classes whose class limits are below this specification limit, are valuated as "not OK" or "R" (rejected).Mean values that lie below this specification limit are also valuated as "not OK," provided that the valuation of the inspection characteristic or sample is planned on the basis of specification limits.
    
    Returns:
    
    Lower limiting value for the actual value of an inspection characteristic.
  - getInspSpecHasLowerLimit
```
@Nullable
public String getInspSpecHasLowerLimit()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasLowerLimit
    
    If this indicator is set, then the value of the corresponding numeric field is not initial.
    
    Returns:
    
    For every numeric field there is a corresponding field that denotes whether the value is initial or not, in order to differentiate between null and the initial value.
  - getInspSpecHasUpperLimit
```
@Nullable
public String getInspSpecHasUpperLimit()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecHasUpperLimit
    
    If this indicator is set, then the value of the corresponding numeric field is not initial.
    
    Returns:
    
    For every numeric field there is a corresponding field that denotes whether the value is initial or not, in order to differentiate between null and the initial value.
  - getInspSpecDefectCodeGrpRejection
```
@Nullable
public String getInspSpecDefectCodeGrpRejection()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecDefectCodeGrpRejection
    
    The code group and code defined here are used during results recording if the inspection characteristic is rejected or the sample is used to:Determine the defect classGenerate the defect data recordThis is the case if no alternative codes for a rejection with reference to an upper or lower specification limit are maintained.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.NoteIf the control indicator for defects recording is set and you do not enter the code group and code, a warning is issued when the data is maintained.If the inspection characteristic or sample is rejected during results recording, the manual defects recording function is called up automatically.
    
    Returns:
    
    Code group from the defect catalog (catalog type 9) that is assigned to an inspection characteristic.
  - getInspSpecDefectCodeRejection
```
@Nullable
public String getInspSpecDefectCodeRejection()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecDefectCodeRejection
    
    The code group and code defined here are used during results recording if the inspection characteristic is rejected or the sample is used to:Determine the defect classGenerate the defect data recordThis is the case if no alternative codes for a rejection with reference to an upper or lower specification limit are maintained.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.NoteIf the control indicator for defects recording is set and you do not enter the code group and code, a warning is issued when the data is maintained.If the inspection characteristic or sample is rejected during results recording, the manual defects recording function is called up automatically.
    
    Returns:
    
    Code from a code group in the defect catalog (catalog type 9) that is assigned to an inspection characteristic.
  - getInspSpecDefectCodeGrpRjcnUpper
```
@Nullable
public String getInspSpecDefectCodeGrpRjcnUpper()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecDefectCodeGrpRjcnUpper
    
    This code group and code are used, if the inspection characteristic or sample is rejected on the basis of an upper specification limit during results recording.A rejection on the basis of an upper specification limit can occur when you make a:Valuation based on the specification limits with and without an acceptance factorValuation based on the action limits of a mean value chartYou can only make an entry in this field for quantitative characteristics, for which the control indicator for the upper specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If you do not enter a code group and code for the inspection characteristic and it is rejected at the upper specification limit, the code for a general rejection will be used during results recording if the inspection characteristic or sample is rejected.If the control indicator for defects recording is set for the inspection characteristic in the task list or for the master inspection characteristic, exactly one defect data record will always be created in the event of a rejection.
    
    Returns:
    
    Code group from the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with an upper specification limit.
  - getInspSpecDefectCodeRjcnUpper
```
@Nullable
public String getInspSpecDefectCodeRjcnUpper()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecDefectCodeRjcnUpper
    
    The code group and code are used if the inspection characteristic or sample is rejected on the basis of an upper specification limit during results recording.Such a rejection on the basis of an upper specification limit can occur when you make a:Valuation based on the specification limits with and without acceptance factorValuation according to the action limits of a mean value chartYou can only make an entry in this field for a quantitative characteristic, for which the control indicator for the upper specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If the control indicator for defects recording is set in the inspection characteristic, exactly one defect data record is always created in the event of a rejection. The defect code for a rejection at the upper specification limit takes precedence over the defect code for a general rejection. If you do not enter a code group or code for a rejection at the upper specification limit for the inspection characteristic, the code for a general rejection is used during results recording if the inspection characteristic or sample is rejected.
    
    Returns:
    
    Code from a code group in the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with an upper specification limit.
  - getInspSpecDefectCodeGrpRjcnLower
```
@Nullable
public String getInspSpecDefectCodeGrpRjcnLower()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecDefectCodeGrpRjcnLower
    
    The code group and code are used during results recording if the inspection characteristic or sample is rejected on the basis of a lower specification limit.Such a rejection on the basis of a lower specification limit can occur when you make a:Valuation based on specification limits with and without an acceptance factorValuation according to the action limits of a mean value chartYou can only make an entry in this field for a quantitative characteristic, for which the control indicator for the lower specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If you do not enter a code group or code for a rejection of the inspection characteristic at the lower specification limit, the code for a general rejection will be used during results recording if the inspection characteristic or sample is rejected.If the control indicator for defects recording is set for the inspection characteristic in the task list or for the master inspection characteristic, exactly one defect data record will always be created in the event of a rejection.
    
    Returns:
    
    Code group from the defect catalog (catalog type 9) that was assigned to a quantitative characteristic with a lower specification limit.
  - getInspSpecDefectCodeRjcnLower
```
@Nullable
public String getInspSpecDefectCodeRjcnLower()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecDefectCodeRjcnLower
    
    The code group and code are used if the inspection characteristic or sample is rejected on the basis of a lower specification limit during results recording.Such a rejection on the basis of a lower specification limit can occur when you make a:Valuation based on the specification limits with and without acceptance factorValuation according to the action limits of a mean value chartYou can only make an entry in this field for a quantitative characteristic, for which the control indicator for the lower specification limit has been set.You must enter both a code group and a code from the defect catalog.You can use the possible entries function to display a list of code groups and codes from which you can then select an entry. You can view the individual codes in a code group by double-clicking the symbol beside the group with the left mouse button. The code and code group are also transferred when you select a code.If the control indicator for defects recording is set in the inspection characteristic, exactly one defect data record will always be created in the event of a rejection. The defect code for a rejection at the lower specification limit takes precedence over the defect code for a general rejection. If you do not enter a code group or a code for a rejection at the lower specification limit , the code for a general rejection is used during results recording if the inspection characteristic or sample is rejected.
    
    Returns:
    
    Code from a code group in the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with a lower specification limit.
  - getSelectedCodeSet
```
@Nullable
public String getSelectedCodeSet()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SelectedCodeSet
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getSelectedCodeSetPlant
```
@Nullable
public String getSelectedCodeSetPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SelectedCodeSetPlant
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Returns:
    
    Key that uniquely identifies the plant assigned to the selected set.
  - getInspSpecAdditionalCatalog2
```
@Nullable
public String getInspSpecAdditionalCatalog2()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog2
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Returns:
    
    Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - getInspSpecAdditionalSelectedSet2
```
@Nullable
public String getInspSpecAdditionalSelectedSet2()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet2
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAdditionalCodeGroup2
```
@Nullable
public String getInspSpecAdditionalCodeGroup2()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup2
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAddlSeldCodeSetPlant2
```
@Nullable
public String getInspSpecAddlSeldCodeSetPlant2()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant2
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Returns:
    
    Key that uniquely identifies the plant assigned to the selected set.
  - getInspSpecAdditionalCatalog3
```
@Nullable
public String getInspSpecAdditionalCatalog3()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog3
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Returns:
    
    Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - getInspSpecAdditionalSelectedSet3
```
@Nullable
public String getInspSpecAdditionalSelectedSet3()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet3
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAdditionalCodeGroup3
```
@Nullable
public String getInspSpecAdditionalCodeGroup3()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup3
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAddlSeldCodeSetPlant3
```
@Nullable
public String getInspSpecAddlSeldCodeSetPlant3()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant3
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Returns:
    
    Key that uniquely identifies the plant assigned to the selected set.
  - getInspSpecAdditionalCatalog4
```
@Nullable
public String getInspSpecAdditionalCatalog4()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog4
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Returns:
    
    Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - getInspSpecAdditionalSelectedSet4
```
@Nullable
public String getInspSpecAdditionalSelectedSet4()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet4
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAdditionalCodeGroup4
```
@Nullable
public String getInspSpecAdditionalCodeGroup4()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup4
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAddlSeldCodeSetPlant4
```
@Nullable
public String getInspSpecAddlSeldCodeSetPlant4()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant4
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Returns:
    
    Key that uniquely identifies the plant assigned to the selected set.
  - getInspSpecAdditionalCatalog5
```
@Nullable
public String getInspSpecAdditionalCatalog5()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSpecAdditionalCatalog5
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
    
    Returns:
    
    Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).
  - getInspSpecAdditionalSelectedSet5
```
@Nullable
public String getInspSpecAdditionalSelectedSet5()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalSelectedSet5
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAdditionalCodeGroup5
```
@Nullable
public String getInspSpecAdditionalCodeGroup5()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSpecAdditionalCodeGroup5
    
    If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
    
    Returns:
    
    If you are processing a qualitative inspection characteristic for which the characteristic attributes indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.
  - getInspSpecAddlSeldCodeSetPlant5
```
@Nullable
public String getInspSpecAddlSeldCodeSetPlant5()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant5
    
    Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
    
    Returns:
    
    Key that uniquely identifies the plant assigned to the selected set.
  - getSamplingProcedure
```
@Nullable
public String getSamplingProcedure()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SamplingProcedure
    
    In the sampling procedure, the valuation mode is also defined for the inspection result.A sampling procedure is assigned to an inspection characteristic in a task list or material specification. In addition, you can assign the procedure to an unplanned characteristic, when you record results.If you do not enter a sampling procedure for an inspection characteristic, the system chooses a sampling procedure proposed in the settings at plant level. If no sampling procedure was entered in these settings, the system takes the lot size as the sample size.
    
    Returns:
    
    Procedure by which the sample size for an inspection is determined.
  - getInspCharacteristicSampleUnit
```
@Nullable
public String getInspCharacteristicSampleUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspCharacteristicSampleUnit
    
    The unit in which a sample is measured.To permit this unit of measure to be converted into the material unit of measure when the system selects the inspection specifications for an inspection lot, you must have maintained the conversion factors in the material master record100 ml are needed to inspect a characteristic. In this case, the sample unit of measure is ml.
    
    Returns:
    
    The base unit of measure that is used to determine a sample for a characteristic.
  - getBOOCharcSampleQuantity
```
@Nullable
public BigDecimal getBOOCharcSampleQuantity()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: BOOCharcSampleQuantity
    
    The sample unit is the product of the following factors: Base sample quantity and the sample unit of measure.To inspect a characteristic, 100 ml are needed. In this case:Sample unit of measure = mlBase sample quantity = 100Sample unit = 100mlIf the sampling procedure that is defined for the characteristic stipulates that 5 individual samples are needed, the sample unit is multiplied by five. As a result, 5 x 100 ml must be drawn to inspect this characteristic.Sample quantity = 500 ml
    
    Returns:
    
    Factor for calculating the sample unit.
  - getInspSpecInformationField1
```
@Nullable
public String getInspSpecInformationField1()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspSpecInformationField1
    
    Returns:
    
    This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object, such as an inspection method or a master inspection characteristic.
  - getInspSpecInformationField2
```
@Nullable
public String getInspSpecInformationField2()
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: InspSpecInformationField2
    
    Returns:
    
    This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object, such as an inspection method or a master inspection characteristic.
  - getInspSpecInformationField3
```
@Nullable
public String getInspSpecInformationField3()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: InspSpecInformationField3
    
    Returns:
    
    This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object, such as an inspection method or a master inspection characteristic.
  - getInspectionSpecificationText
```
@Nullable
public String getInspectionSpecificationText()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: InspectionSpecificationText
    
    Returns:
    
    Text of up to 40 characters that describes the object in more detail. This description is also known as short text.
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    Name of user who created the record.
  - getCreationDate
```
@Nullable
public LocalDateTime getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    Date on which the 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 the user who made the last change to this data record.
  - getLastChangeDate
```
@Nullable
public LocalDateTime getLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    The system enters the current system date.
    
    Returns:
    
    Date on which the data record was last changed.
  - getBillOfOperationsVersion
```
@Nullable
public String getBillOfOperationsVersion()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfOperationsVersion
    
    Returns:
    
    A routing version is a consistent model of a product's operations and operation activities. You can make changes to a new routing version until it is released. Released routing versions can be used in production execution and cannot be changed. If you want to make changes to a routing version, you can create a new routing version and then you can make the necessary changes.
  - 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
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class VdmObject<InspPlanOpCharacteristic>
  - equals
```
public boolean equals(@Nullable
                      Object o)
```
    Overrides:
    
    equals in class VdmObject<InspPlanOpCharacteristic>
  - canEqual
```
protected boolean canEqual(@Nullable
                           Object other)
```
    Overrides:
    
    canEqual in class VdmObject<InspPlanOpCharacteristic>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<InspPlanOpCharacteristic>

Class InspPlanOpCharacteristic

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

INSPECTION_PLAN_GROUP

BOO_OPERATION_INTERNAL_ID

BOO_CHARACTERISTIC

BOO_CHARACTERISTIC_VERSION

BOO_OP_INTERNAL_VERSION_COUNTER

INSPECTION_PLAN_INTERNAL_VERSION

INSPECTION_PLAN

VALIDITY_START_DATE

VALIDITY_END_DATE

CHANGE_NUMBER

IS_DELETED

BOO_OPERATION_PRT_INTERNAL_ID

INSPECTION_METHOD

INSPECTION_METHOD_VERSION

INSPECTION_METHOD_PLANT

INSP_SPEC_IMPORTANCE_CODE

INSPECTOR_QUALIFICATION

INSPECTION_SPECIFICATION

INSPECTION_SPECIFICATION_VERSION

INSPECTION_SPECIFICATION_PLANT

BOO_CHARC_HAS_INSP_SPEC_REFERENCE

INSP_SPEC_CONTROL_INDICATORS

INSP_SPEC_IS_QUANTITATIVE

INSP_SPEC_IS_MEASURED_VALUE_RQD

INSP_SPEC_IS_SELECTED_SET_REQUIRED

INSP_SPEC_IS_UPPER_LIMIT_REQUIRED

INSP_SPEC_IS_LOWER_LIMIT_REQUIRED

INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT

INSPECTION_SCOPE

INSP_SPEC_IS_LONG_TERM_INSPECTION

INSP_SPEC_RECORDING_TYPE

INSP_RESULT_IS_DOCUMENTATION_RQD

INSP_SPEC_CHARC_CATEGORY

INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE

INSP_SPEC_IS_DESTRUCTIVE

INSP_SPEC_RESULT_CALCULATION

INSP_SPEC_IS_SAMPLING_PROCED_RQD

INSP_SPEC_IS_SCRAP_RELEVANT

INSP_SPEC_HAS_FIXED_CTRL_INDICATORS

INSP_SPEC_IS_TEST_EQUIPMENT_RQD

INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC

INSP_SPEC_IS_CHG_DOC_REQUIRED

INSP_SPEC_IS_CONTROL_CHART_USED

INSP_SPEC_PRINT_CONTROL

INSP_TOLERANCE_SPECIFICATION

INSP_SPEC_DECIMAL_PLACES

INSPECTION_SPECIFICATION_UNIT

INSP_SPEC_TARGET_VALUE

INSP_SPEC_HAS_TARGET_VALUE

INSP_SPEC_UPPER_LIMIT

INSP_SPEC_LOWER_LIMIT

INSP_SPEC_HAS_LOWER_LIMIT

INSP_SPEC_HAS_UPPER_LIMIT

INSP_SPEC_DEFECT_CODE_GRP_REJECTION

INSP_SPEC_DEFECT_CODE_REJECTION

INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER

INSP_SPEC_DEFECT_CODE_RJCN_UPPER

INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER

INSP_SPEC_DEFECT_CODE_RJCN_LOWER

SELECTED_CODE_SET

SELECTED_CODE_SET_PLANT

INSP_SPEC_ADDITIONAL_CATALOG2

INSP_SPEC_ADDITIONAL_SELECTED_SET2

INSP_SPEC_ADDITIONAL_CODE_GROUP2

INSP_SPEC_ADDL_SELD_CODE_SET_PLANT2

INSP_SPEC_ADDITIONAL_CATALOG3

INSP_SPEC_ADDITIONAL_SELECTED_SET3

INSP_SPEC_ADDITIONAL_CODE_GROUP3

INSP_SPEC_ADDL_SELD_CODE_SET_PLANT3