public class InspPlanOpCharacteristic extends VdmEntity<InspPlanOpCharacteristic>
Original entity name from the Odata EDM: A_InspPlanOpCharacteristicType
| Modifier and Type | Class and Description |
|---|---|
static class |
InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder |
| 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<String> |
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<Double> |
INSP_SPEC_CLASS_MIDPOINT_QTY
Use with available fluent helpers to apply the InspSpecClassMidpointQty field to query operations.
|
static InspPlanOpCharacteristicField<Double> |
INSP_SPEC_CLASS_WIDTH_QTY
Use with available fluent helpers to apply the InspSpecClassWidthQty 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<Double> |
INSP_SPEC_FIRST_LOWER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecFirstLowerSpecLimit field to query operations.
|
static InspPlanOpCharacteristicField<Double> |
INSP_SPEC_FIRST_UPPER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecFirstUpperSpecLimit field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_FORMULA1
Use with available fluent helpers to apply the InspSpecFormula1 field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_FORMULA2
Use with available fluent helpers to apply the InspSpecFormula2 field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_HAS_CLASS_MIDPOINT
Use with available fluent helpers to apply the InspSpecHasClassMidpoint field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_HAS_CLASS_WIDTH
Use with available fluent helpers to apply the InspSpecHasClassWidth field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_HAS_FIRST_LOWER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasFirstLowerSpecLimit field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_HAS_FIRST_UPPER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasFirstUpperSpecLimit 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_FORMULA
Use with available fluent helpers to apply the InspSpecHasFormula 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_SECOND_LOWR_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasSecondLowrSpecLimit field to query operations.
|
static InspPlanOpCharacteristicField<String> |
INSP_SPEC_HAS_SECOND_UPR_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasSecondUprSpecLimit 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_INPUT_PROCEDURE
Use with available fluent helpers to apply the InspSpecInputProcedure 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<Short> |
INSP_SPEC_NUMBER_OF_CLASSES
Use with available fluent helpers to apply the InspSpecNumberOfClasses 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_SECOND_LOWER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecSecondLowerSpecLimit field to query operations.
|
static InspPlanOpCharacteristicField<Double> |
INSP_SPEC_SECOND_UPPER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecSecondUpperSpecLimit 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.
|
changedOriginalFields| 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,
String 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,
Double inspSpecFirstUpperSpecLimit,
String inspSpecHasFirstUpperSpecLimit,
Double inspSpecFirstLowerSpecLimit,
String inspSpecHasFirstLowerSpecLimit,
Double inspSpecSecondUpperSpecLimit,
String inspSpecHasSecondUprSpecLimit,
Double inspSpecSecondLowerSpecLimit,
String inspSpecHasSecondLowrSpecLimit,
String inspSpecInputProcedure,
String inspSpecHasFormula,
String inspSpecFormula1,
String inspSpecFormula2,
Short inspSpecNumberOfClasses,
Double inspSpecClassWidthQty,
String inspSpecHasClassWidth,
Double inspSpecClassMidpointQty,
String inspSpecHasClassMidpoint,
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) |
| 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> |
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
|
String |
getBOOCharcHasInspSpecReference()
Constraints: Not nullable, Maximum length: 1
|
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
|
Double |
getInspSpecClassMidpointQty()
Constraints: none
|
Double |
getInspSpecClassWidthQty()
Constraints: none
|
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
|
Double |
getInspSpecFirstLowerSpecLimit()
Constraints: none
|
Double |
getInspSpecFirstUpperSpecLimit()
Constraints: none
|
String |
getInspSpecFormula1()
Constraints: Not nullable, Maximum length: 60
|
String |
getInspSpecFormula2()
Constraints: Not nullable, Maximum length: 60
|
String |
getInspSpecHasClassMidpoint()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasClassWidth()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasFirstLowerSpecLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasFirstUpperSpecLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasFixedCtrlIndicators()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasFormula()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasLowerLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasSecondLowrSpecLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasSecondUprSpecLimit()
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 |
getInspSpecInputProcedure()
Constraints: Not nullable, Maximum length: 3
|
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
|
Short |
getInspSpecNumberOfClasses()
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 |
getInspSpecSecondLowerSpecLimit()
Constraints: none
|
Double |
getInspSpecSecondUpperSpecLimit()
Constraints: none
|
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(String bOOCharcHasInspSpecReference)
Constraints: Not nullable, Maximum length: 1
|
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 |
setInspSpecClassMidpointQty(Double inspSpecClassMidpointQty)
Constraints: none
|
void |
setInspSpecClassWidthQty(Double inspSpecClassWidthQty)
Constraints: none
|
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 |
setInspSpecFirstLowerSpecLimit(Double inspSpecFirstLowerSpecLimit)
Constraints: none
|
void |
setInspSpecFirstUpperSpecLimit(Double inspSpecFirstUpperSpecLimit)
Constraints: none
|
void |
setInspSpecFormula1(String inspSpecFormula1)
Constraints: Not nullable, Maximum length: 60
|
void |
setInspSpecFormula2(String inspSpecFormula2)
Constraints: Not nullable, Maximum length: 60
|
void |
setInspSpecHasClassMidpoint(String inspSpecHasClassMidpoint)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasClassWidth(String inspSpecHasClassWidth)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasFirstLowerSpecLimit(String inspSpecHasFirstLowerSpecLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasFirstUpperSpecLimit(String inspSpecHasFirstUpperSpecLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasFixedCtrlIndicators(String inspSpecHasFixedCtrlIndicators)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasFormula(String inspSpecHasFormula)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasLowerLimit(String inspSpecHasLowerLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasSecondLowrSpecLimit(String inspSpecHasSecondLowrSpecLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasSecondUprSpecLimit(String inspSpecHasSecondUprSpecLimit)
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 |
setInspSpecInputProcedure(String inspSpecInputProcedure)
Constraints: Not nullable, Maximum length: 3
|
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 |
setInspSpecNumberOfClasses(Short inspSpecNumberOfClasses)
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 |
setInspSpecSecondLowerSpecLimit(Double inspSpecSecondLowerSpecLimit)
Constraints: none
|
void |
setInspSpecSecondUpperSpecLimit(Double inspSpecSecondUpperSpecLimit)
Constraints: none
|
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() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifiergetChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationPropertiespublic static final InspPlanOpCharacteristicSelectable ALL_FIELDS
public static final InspPlanOpCharacteristicField<String> INSPECTION_PLAN_GROUP
public static final InspPlanOpCharacteristicField<String> BOO_OPERATION_INTERNAL_ID
public static final InspPlanOpCharacteristicField<String> BOO_CHARACTERISTIC
public static final InspPlanOpCharacteristicField<String> BOO_CHARACTERISTIC_VERSION
public static final InspPlanOpCharacteristicField<String> BOO_OP_INTERNAL_VERSION_COUNTER
public static final InspPlanOpCharacteristicField<String> INSPECTION_PLAN_INTERNAL_VERSION
public static final InspPlanOpCharacteristicField<String> INSPECTION_PLAN
public static final InspPlanOpCharacteristicField<LocalDateTime> VALIDITY_START_DATE
public static final InspPlanOpCharacteristicField<LocalDateTime> VALIDITY_END_DATE
public static final InspPlanOpCharacteristicField<String> CHANGE_NUMBER
public static final InspPlanOpCharacteristicField<Boolean> IS_DELETED
public static final InspPlanOpCharacteristicField<String> BOO_OPERATION_PRT_INTERNAL_ID
public static final InspPlanOpCharacteristicField<String> INSPECTION_METHOD
public static final InspPlanOpCharacteristicField<String> INSPECTION_METHOD_VERSION
public static final InspPlanOpCharacteristicField<String> INSPECTION_METHOD_PLANT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IMPORTANCE_CODE
public static final InspPlanOpCharacteristicField<String> INSPECTOR_QUALIFICATION
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_VERSION
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_PLANT
public static final InspPlanOpCharacteristicField<String> BOO_CHARC_HAS_INSP_SPEC_REFERENCE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_CONTROL_INDICATORS
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_QUANTITATIVE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_MEASURED_VALUE_RQD
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SELECTED_SET_REQUIRED
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_UPPER_LIMIT_REQUIRED
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_LOWER_LIMIT_REQUIRED
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT
public static final InspPlanOpCharacteristicField<String> INSPECTION_SCOPE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_LONG_TERM_INSPECTION
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_RECORDING_TYPE
public static final InspPlanOpCharacteristicField<String> INSP_RESULT_IS_DOCUMENTATION_RQD
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_CHARC_CATEGORY
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_DESTRUCTIVE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_RESULT_CALCULATION
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SAMPLING_PROCED_RQD
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_SCRAP_RELEVANT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_FIXED_CTRL_INDICATORS
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_TEST_EQUIPMENT_RQD
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_CHG_DOC_REQUIRED
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_IS_CONTROL_CHART_USED
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_PRINT_CONTROL
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_FIRST_UPPER_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_FIRST_UPPER_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_FIRST_LOWER_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_FIRST_LOWER_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_SECOND_UPPER_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_SECOND_UPR_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_SECOND_LOWER_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_SECOND_LOWR_SPEC_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INPUT_PROCEDURE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_FORMULA
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_FORMULA1
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_FORMULA2
public static final InspPlanOpCharacteristicField<Short> INSP_SPEC_NUMBER_OF_CLASSES
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_CLASS_WIDTH_QTY
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_CLASS_WIDTH
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_CLASS_MIDPOINT_QTY
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_CLASS_MIDPOINT
public static final InspPlanOpCharacteristicField<String> INSP_TOLERANCE_SPECIFICATION
public static final InspPlanOpCharacteristicField<Short> INSP_SPEC_DECIMAL_PLACES
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_UNIT
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_TARGET_VALUE
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_TARGET_VALUE
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_UPPER_LIMIT
public static final InspPlanOpCharacteristicField<Double> INSP_SPEC_LOWER_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_LOWER_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_HAS_UPPER_LIMIT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_GRP_REJECTION
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_REJECTION
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_RJCN_UPPER
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_DEFECT_CODE_RJCN_LOWER
public static final InspPlanOpCharacteristicField<String> SELECTED_CODE_SET
public static final InspPlanOpCharacteristicField<String> SELECTED_CODE_SET_PLANT
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG2
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET2
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP2
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT2
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG3
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET3
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP3
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT3
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG4
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET4
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP4
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT4
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CATALOG5
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_SELECTED_SET5
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDITIONAL_CODE_GROUP5
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_ADDL_SELD_CODE_SET_PLANT5
public static final InspPlanOpCharacteristicField<String> SAMPLING_PROCEDURE
public static final InspPlanOpCharacteristicField<String> INSP_CHARACTERISTIC_SAMPLE_UNIT
public static final InspPlanOpCharacteristicField<BigDecimal> BOO_CHARC_SAMPLE_QUANTITY
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INFORMATION_FIELD1
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INFORMATION_FIELD2
public static final InspPlanOpCharacteristicField<String> INSP_SPEC_INFORMATION_FIELD3
public static final InspPlanOpCharacteristicField<String> INSPECTION_SPECIFICATION_TEXT
public static final InspPlanOpCharacteristicField<String> CREATED_BY_USER
public static final InspPlanOpCharacteristicField<LocalDateTime> CREATION_DATE
public static final InspPlanOpCharacteristicField<String> LAST_CHANGED_BY_USER
public static final InspPlanOpCharacteristicField<LocalDateTime> LAST_CHANGE_DATE
public static final InspPlanOpCharacteristicField<String> BILL_OF_OPERATIONS_VERSION
public static final InspPlanOpCharacteristicField<ZonedDateTime> CHANGED_DATE_TIME
public 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 String 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 Double inspSpecFirstUpperSpecLimit, @Nullable String inspSpecHasFirstUpperSpecLimit, @Nullable Double inspSpecFirstLowerSpecLimit, @Nullable String inspSpecHasFirstLowerSpecLimit, @Nullable Double inspSpecSecondUpperSpecLimit, @Nullable String inspSpecHasSecondUprSpecLimit, @Nullable Double inspSpecSecondLowerSpecLimit, @Nullable String inspSpecHasSecondLowrSpecLimit, @Nullable String inspSpecInputProcedure, @Nullable String inspSpecHasFormula, @Nullable String inspSpecFormula1, @Nullable String inspSpecFormula2, @Nullable Short inspSpecNumberOfClasses, @Nullable Double inspSpecClassWidthQty, @Nullable String inspSpecHasClassWidth, @Nullable Double inspSpecClassMidpointQty, @Nullable String inspSpecHasClassMidpoint, @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)
@Nonnull public Class<InspPlanOpCharacteristic> getType()
getType in class VdmObject<InspPlanOpCharacteristic>public void setInspectionPlanGroup(@Nullable String inspectionPlanGroup)
Original property name from the Odata EDM: InspectionPlanGroup
You can use groups, for example, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
inspectionPlanGroup - Key identifying a group.public void setBOOOperationInternalID(@Nullable String bOOOperationInternalID)
Original property name from the Odata EDM: BOOOperationInternalID
bOOOperationInternalID - Number of the Task List Nodepublic void setBOOCharacteristic(@Nullable String bOOCharacteristic)
Original property name from the Odata EDM: BOOCharacteristic
bOOCharacteristic - The number that explicitly identifies an inspection characteristic within an operation in an
inspection plan.public void setBOOCharacteristicVersion(@Nullable String bOOCharacteristicVersion)
Original property name from the Odata EDM: BOOCharacteristicVersion
bOOCharacteristicVersion - Identifies the activity posting.public void setBOOOpInternalVersionCounter(@Nullable String bOOOpInternalVersionCounter)
Original property name from the Odata EDM: BOOOpInternalVersionCounter
bOOOpInternalVersionCounter - Identifies the activity posting.public void setInspectionPlanInternalVersion(@Nullable String inspectionPlanInternalVersion)
Original property name from the Odata EDM: InspectionPlanInternalVersion
inspectionPlanInternalVersion - Identifies the activity posting.public void setInspectionPlan(@Nullable String inspectionPlan)
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.
inspectionPlan - This key and the task list group uniquely identify a task list.public void setValidityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
validityStartDate - Specifies the start date for the validity period of an object (such as material, BOM, or routing).public void setValidityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
validityEndDate - End of validity period of an object (such as material, BOM, or routing) in the SAP System.public void setChangeNumber(@Nullable String changeNumber)
Original property name from the Odata EDM: ChangeNumber
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company
changeNumber - Number used to uniquely identify a change master record.public void setIsDeleted(@Nullable Boolean isDeleted)
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.
isDeleted - Indicator showing that the BOM header or the BOM item has been deleted with reference to the change
number.public void setBOOOperationPRTInternalID(@Nullable String bOOOperationPRTInternalID)
Original property name from the Odata EDM: BOOOperationPRTInternalID
bOOOperationPRTInternalID - Assigned Test Equipmentpublic void setInspectionMethod(@Nullable String inspectionMethod)
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.
inspectionMethod - Name that uniquely identifies an inspection method within a plant.public void setInspectionMethodVersion(@Nullable String inspectionMethodVersion)
Original property name from the Odata EDM: InspectionMethodVersion
inspectionMethodVersion - Version Number of Inspection Methodpublic void setInspectionMethodPlant(@Nullable String inspectionMethodPlant)
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.
inspectionMethodPlant - Key, that identifies a plant.public void setInspSpecImportanceCode(@Nullable String inspSpecImportanceCode)
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.
inspSpecImportanceCode - Classification of inspection characteristics according to their weighting (importance).public void setInspectorQualification(@Nullable String inspectorQualification)
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.
inspectorQualification - Qualification that an inspector must have and, if necessary, validate in order to be able to conduct
an inspection.public void setInspectionSpecification(@Nullable String inspectionSpecification)
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.
inspectionSpecification - Name that uniquely identifies a master inspection characteristic within a plant.public void setInspectionSpecificationVersion(@Nullable String inspectionSpecificationVersion)
Original property name from the Odata EDM: InspectionSpecificationVersion
inspectionSpecificationVersion - Version Number of Master Inspection Characteristicpublic void setInspectionSpecificationPlant(@Nullable String inspectionSpecificationPlant)
Original property name from the Odata EDM: InspectionSpecificationPlant
inspectionSpecificationPlant - Plant for the Master Inspection Characteristicpublic void setBOOCharcHasInspSpecReference(@Nullable String bOOCharcHasInspSpecReference)
Original property name from the Odata EDM: BOOCharcHasInspSpecReference
bOOCharcHasInspSpecReference - Reference to Master Insp. Characteristic in Task Listpublic void setInspSpecControlIndicators(@Nullable String inspSpecControlIndicators)
Original property name from the Odata EDM: InspSpecControlIndicators
plan default valuesresults recordinginspection processing
inspSpecControlIndicators - A characteristic is defined with this control indicator string. It contains indicators for:public void setInspSpecIsQuantitative(@Nullable String inspSpecIsQuantitative)
Original property name from the Odata EDM: InspSpecIsQuantitative
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.public void setInspSpecIsMeasuredValueRqd(@Nullable String inspSpecIsMeasuredValueRqd)
Original property name from the Odata EDM: InspSpecIsMeasuredValueRqd
inspSpecIsMeasuredValueRqd - If you set this indicator, measured values for this quantitative characteristic have to be inspected
and confirmed.public void setInspSpecIsSelectedSetRequired(@Nullable String inspSpecIsSelectedSetRequired)
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".
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).public void setInspSpecIsUpperLimitRequired(@Nullable String inspSpecIsUpperLimitRequired)
Original property name from the Odata EDM: InspSpecIsUpperLimitRequired
inspSpecIsUpperLimitRequired - If you set this indicator, you must enter an upper specification limit for the inspection
characteristic.public void setInspSpecIsLowerLimitRequired(@Nullable String inspSpecIsLowerLimitRequired)
Original property name from the Odata EDM: InspSpecIsLowerLimitRequired
inspSpecIsLowerLimitRequired - If you set this indicator, you must enter a lower specification limit for the inspection
characteristic.public void setInspSpecIsTargetValueInLimit(@Nullable String inspSpecIsTargetValueInLimit)
Original property name from the Odata EDM: InspSpecIsTargetValueInLimit
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.public void setInspectionScope(@Nullable String inspectionScope)
Original property name from the Odata EDM: InspectionScope
inspectionScope - With this field you determine the extent, to which the number of required measured values must adhere.public void setInspSpecIsLongTermInspection(@Nullable String inspSpecIsLongTermInspection)
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.
inspSpecIsLongTermInspection - If you set this indicator, the characteristic is subject to a long-term inspection.public void setInspSpecRecordingType(@Nullable String inspSpecRecordingType)
Original property name from the Odata EDM: InspSpecRecordingType
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).public void setInspResultIsDocumentationRqd(@Nullable String inspResultIsDocumentationRqd)
Original property name from the Odata EDM: InspResultIsDocumentationRqd
inspResultIsDocumentationRqd - Documentation Required for Inspection Resultpublic void setInspSpecCharcCategory(@Nullable String inspSpecCharcCategory)
Original property name from the Odata EDM: InspSpecCharcCategory
inspSpecCharcCategory - Characteristic Categorypublic void setInspSpecIsSampleQtyAdditive(@Nullable String inspSpecIsSampleQtyAdditive)
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.
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.public void setInspSpecIsDestructive(@Nullable String inspSpecIsDestructive)
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.
inspSpecIsDestructive - You set this indicator for inspection characteristics whose inspection samples will be destroyed when
you inspect the characteristics.public void setInspSpecResultCalculation(@Nullable String inspSpecResultCalculation)
Original property name from the Odata EDM: InspSpecResultCalculation
inspSpecResultCalculation - Characteristic Result Calculationpublic void setInspSpecIsSamplingProcedRqd(@Nullable String inspSpecIsSamplingProcedRqd)
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.
inspSpecIsSamplingProcedRqd - If you set this indicator, a sampling procedure must be assigned to the characteristic in the task
list.public void setInspSpecIsScrapRelevant(@Nullable String inspSpecIsScrapRelevant)
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.
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.public void setInspSpecHasFixedCtrlIndicators(@Nullable String inspSpecHasFixedCtrlIndicators)
Original property name from the Odata EDM: InspSpecHasFixedCtrlIndicators
inspSpecHasFixedCtrlIndicators - Set this indicator to specify that the control indicators that were defined for the inspection
characteristic using a control key cannot be changed.public void setInspSpecIsTestEquipmentRqd(@Nullable String inspSpecIsTestEquipmentRqd)
Original property name from the Odata EDM: InspSpecIsTestEquipmentRqd
If you do not make an assignment, the system displays a warning message.
inspSpecIsTestEquipmentRqd - If you set this indicator, you can assign test equipment to the inspection characteristic in the task
list.public void setInspSpecIsDefectsRecgAutomatic(@Nullable String inspSpecIsDefectsRecgAutomatic)
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.
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:public void setInspSpecIsChgDocRequired(@Nullable String inspSpecIsChgDocRequired)
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.
inspSpecIsChgDocRequired - If you set this indicator, change documents are created for this inspection characteristic when
results are recorded based on characteristics.public void setInspSpecIsControlChartUsed(@Nullable String inspSpecIsControlChartUsed)
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.
inspSpecIsControlChartUsed - If you set this indicator, a control chart is run for this characteristic.public void setInspSpecPrintControl(@Nullable String inspSpecPrintControl)
Original property name from the Odata EDM: InspSpecPrintControl
inspSpecPrintControl - Inspection Print Controlpublic void setInspSpecFirstUpperSpecLimit(@Nullable Double inspSpecFirstUpperSpecLimit)
Original property name from the Odata EDM: InspSpecFirstUpperSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
inspSpecFirstUpperSpecLimit - Upper limit value of a user-specified limit, for example, a warning limit.public void setInspSpecHasFirstUpperSpecLimit(@Nullable String inspSpecHasFirstUpperSpecLimit)
Original property name from the Odata EDM: InspSpecHasFirstUpperSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasFirstUpperSpecLimit - 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.public void setInspSpecFirstLowerSpecLimit(@Nullable Double inspSpecFirstLowerSpecLimit)
Original property name from the Odata EDM: InspSpecFirstLowerSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
inspSpecFirstLowerSpecLimit - Lower limiting value of a user-specified limit, for example, a warning limit.public void setInspSpecHasFirstLowerSpecLimit(@Nullable String inspSpecHasFirstLowerSpecLimit)
Original property name from the Odata EDM: InspSpecHasFirstLowerSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasFirstLowerSpecLimit - 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.public void setInspSpecSecondUpperSpecLimit(@Nullable Double inspSpecSecondUpperSpecLimit)
Original property name from the Odata EDM: InspSpecSecondUpperSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
inspSpecSecondUpperSpecLimit - Upper limit value of a user-specified limit, for example, a warning limit.public void setInspSpecHasSecondUprSpecLimit(@Nullable String inspSpecHasSecondUprSpecLimit)
Original property name from the Odata EDM: InspSpecHasSecondUprSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasSecondUprSpecLimit - 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.public void setInspSpecSecondLowerSpecLimit(@Nullable Double inspSpecSecondLowerSpecLimit)
Original property name from the Odata EDM: InspSpecSecondLowerSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
inspSpecSecondLowerSpecLimit - Lower limiting value of a user-specified limit, for example, a warning limit.public void setInspSpecHasSecondLowrSpecLimit(@Nullable String inspSpecHasSecondLowrSpecLimit)
Original property name from the Odata EDM: InspSpecHasSecondLowrSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasSecondLowrSpecLimit - 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.public void setInspSpecInputProcedure(@Nullable String inspSpecInputProcedure)
Original property name from the Odata EDM: InspSpecInputProcedure
Select a three-character key for input processing here. The measured value will be processed in accordance with this key, for example, it may be multiplied by a certain factor or rounded.You can implement a variety of rounding procedures using input processing, for example, rounding according to number of significant digits.Another possibility is the direct conversion of the measured value, for example, measured value is input in centimeters and immediately converted to millimeters.
inspSpecInputProcedure - Key for input processing.public void setInspSpecHasFormula(@Nullable String inspSpecHasFormula)
Original property name from the Odata EDM: InspSpecHasFormula
If you do not set the indicator, the system does not check the formula or calculate it.In this case, you have to perform your own calculation (for example, by using the corresponding user exit).
inspSpecHasFormula - If you set this indicator, the specified formula is checked and calculated in results recording.public void setInspSpecFormula1(@Nullable String inspSpecFormula1)
Original property name from the Odata EDM: InspSpecFormula1
In the task list (checked for correct syntax)The function module CHECK_FORMULA checks whether a formula stored as a literal or as variable has the correct syntax.In results recording (when the value of the calculated characteristic is to be calculated)A formula can be structured as follows (with the standard settings):Characteristic 10 stands for the length and characteristic 20 stands for the width. Characteristic 30 represents the area and is to be calculated from characteristics 10 and 20.Characteristic 30 is therefore a calculated characteristic with the following formula:General: Area = Length * WidthFormula interpreter: Area = ppnnnn * ppnnnn The variable 'pp' defines the formula parameter and 'nnnn' represents the characteristic from which the value of the formula parameter is taken.Example: Area = C00010 * C00020 'C0' stands for the arithmetic mean value and '0010' or '0020' for the respective characteristic.
inspSpecFormula1 - To calculate a value for a calculated characteristic, enter a formula in this field. The formula will
be evaluated by the SAP formula interpreter in the following places:public void setInspSpecFormula2(@Nullable String inspSpecFormula2)
Original property name from the Odata EDM: InspSpecFormula2
In the task list (checked for correct syntax)The function module CHECK_FORMULA checks whether a formula stored as a literal or as variable has the correct syntax.In results recording (when the value of the calculated characteristic is to be calculated)A formula can be structured as follows (with the standard settings):Characteristic 10 stands for the length and characteristic 20 stands for the width. Characteristic 30 represents the area and is to be calculated from characteristics 10 and 20.Characteristic 30 is therefore a calculated characteristic with the following formula:General: Area = Length * WidthFormula interpreter: Area = ppnnnn * ppnnnn The variable 'pp' defines the formula parameter and 'nnnn' represents the characteristic from which the value of the formula parameter is taken.Example: Area = C00010 * C00020 'C0' stands for the arithmetic mean value and '0010' or '0020' for the respective characteristic.
inspSpecFormula2 - To calculate a value for a calculated characteristic, enter a formula in this field. The formula will
be evaluated by the SAP formula interpreter in the following places:public void setInspSpecNumberOfClasses(@Nullable Short inspSpecNumberOfClasses)
Original property name from the Odata EDM: InspSpecNumberOfClasses
The number of classes is stored in this field, if the characteristic is treated as a quantitative characteristic whose values are managed with classes.In addition to the number entered here, marginal classes are maintained adjacent to the highest and lowest classes. The width of a marginal class is not limited on either the upper or lower end. In this way, the values that do not fit in any of the other classes are not lost; they are stored in the marginal classes.In this field you can enter EITHER a value or an *. If you enter an * the system calculates the number of classes as follows:number of classes = tolerance range / class widthYou must enter both specification limits (upper and lower) as well as the class width, so that the system can perform the calculation automatically.
inspSpecNumberOfClasses - Number of consecutive and mutually exclusive intervals into which the total interval is divided.public void setInspSpecClassWidthQty(@Nullable Double inspSpecClassWidthQty)
Original property name from the Odata EDM: InspSpecClassWidthQty
The class width is stored in this field, if the characteristic is treated as a quantitative characteristic whose values are managed with classes. The width of the classes is given in the same unit as the target value and the tolerances.All classes except for the marginal classes have the same width. For additional information about marginal classes, refer to the documentation about the number of classes.
inspSpecClassWidthQty - Difference between the upper limit and the lower limit of a class.public void setInspSpecHasClassWidth(@Nullable String inspSpecHasClassWidth)
Original property name from the Odata EDM: InspSpecHasClassWidth
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasClassWidth - 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.public void setInspSpecClassMidpointQty(@Nullable Double inspSpecClassMidpointQty)
Original property name from the Odata EDM: InspSpecClassMidpointQty
The class midpoint is stored in this field, if the characteristic is treated as a quantitative characteristic whose values are managed with classes.With an uneven number of classes, the classes are laid out so that the value entered here lies in the middle of the middle class.With an even number of classes, this value becomes the limit value of the two classes in the middle.
inspSpecClassMidpointQty - Arithmetic mean of the class limits (upper and lower limits of a class).public void setInspSpecHasClassMidpoint(@Nullable String inspSpecHasClassMidpoint)
Original property name from the Odata EDM: InspSpecHasClassMidpoint
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasClassMidpoint - 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.public void setInspToleranceSpecification(@Nullable String inspToleranceSpecification)
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.
inspToleranceSpecification - User-defined key for tolerance specifications.public void setInspSpecDecimalPlaces(@Nullable Short inspSpecDecimalPlaces)
Original property name from the Odata EDM: InspSpecDecimalPlaces
inspSpecDecimalPlaces - In this field, you define the accuracy (number of decimal places), to which the value is calculated.public void setInspectionSpecificationUnit(@Nullable String inspectionSpecificationUnit)
Original property name from the Odata EDM: InspectionSpecificationUnit
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.public void setInspSpecTargetValue(@Nullable Double inspSpecTargetValue)
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.
inspSpecTargetValue - Value of a quantitative characteristic, from which the actual value of the inspection characteristic
should deviate as little as possible.public void setInspSpecHasTargetValue(@Nullable String inspSpecHasTargetValue)
Original property name from the Odata EDM: InspSpecHasTargetValue
If this indicator is set, then the value of the corresponding numeric field is not initial.
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.public void setInspSpecUpperLimit(@Nullable Double inspSpecUpperLimit)
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.
inspSpecUpperLimit - Upper limit value for the actual value of an inspection characteristic.public void setInspSpecLowerLimit(@Nullable Double inspSpecLowerLimit)
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.
inspSpecLowerLimit - Lower limiting value for the actual value of an inspection characteristic.public void setInspSpecHasLowerLimit(@Nullable String inspSpecHasLowerLimit)
Original property name from the Odata EDM: InspSpecHasLowerLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
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.public void setInspSpecHasUpperLimit(@Nullable String inspSpecHasUpperLimit)
Original property name from the Odata EDM: InspSpecHasUpperLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
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.public void setInspSpecDefectCodeGrpRejection(@Nullable String inspSpecDefectCodeGrpRejection)
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.
inspSpecDefectCodeGrpRejection - Code group from the defect catalog (catalog type 9) that is assigned to an inspection characteristic.public void setInspSpecDefectCodeRejection(@Nullable String inspSpecDefectCodeRejection)
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.
inspSpecDefectCodeRejection - Code from a code group in the defect catalog (catalog type 9) that is assigned to an inspection
characteristic.public void setInspSpecDefectCodeGrpRjcnUpper(@Nullable String inspSpecDefectCodeGrpRjcnUpper)
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.
inspSpecDefectCodeGrpRjcnUpper - Code group from the defect catalog (catalog type 9) that has been assigned to a quantitative
characteristic with an upper specification limit.public void setInspSpecDefectCodeRjcnUpper(@Nullable String inspSpecDefectCodeRjcnUpper)
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.
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.public void setInspSpecDefectCodeGrpRjcnLower(@Nullable String inspSpecDefectCodeGrpRjcnLower)
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.
inspSpecDefectCodeGrpRjcnLower - Code group from the defect catalog (catalog type 9) that was assigned to a quantitative characteristic
with a lower specification limit.public void setInspSpecDefectCodeRjcnLower(@Nullable String inspSpecDefectCodeRjcnLower)
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.
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.public void setSelectedCodeSet(@Nullable String selectedCodeSet)
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.
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.public void setSelectedCodeSetPlant(@Nullable String selectedCodeSetPlant)
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.
selectedCodeSetPlant - Key that uniquely identifies the plant assigned to the selected set.public void setInspSpecAdditionalCatalog2(@Nullable String inspSpecAdditionalCatalog2)
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.
inspSpecAdditionalCatalog2 - Main category by which code groups and codes are classified according to their contents (e.g.
characteristic attributes, defect types, usage decisions).public void setInspSpecAdditionalSelectedSet2(@Nullable String inspSpecAdditionalSelectedSet2)
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.
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.public void setInspSpecAdditionalCodeGroup2(@Nullable String inspSpecAdditionalCodeGroup2)
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.
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.public void setInspSpecAddlSeldCodeSetPlant2(@Nullable String inspSpecAddlSeldCodeSetPlant2)
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.
inspSpecAddlSeldCodeSetPlant2 - Key that uniquely identifies the plant assigned to the selected set.public void setInspSpecAdditionalCatalog3(@Nullable String inspSpecAdditionalCatalog3)
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.
inspSpecAdditionalCatalog3 - Main category by which code groups and codes are classified according to their contents (e.g.
characteristic attributes, defect types, usage decisions).public void setInspSpecAdditionalSelectedSet3(@Nullable String inspSpecAdditionalSelectedSet3)
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.
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.public void setInspSpecAdditionalCodeGroup3(@Nullable String inspSpecAdditionalCodeGroup3)
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.
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.public void setInspSpecAddlSeldCodeSetPlant3(@Nullable String inspSpecAddlSeldCodeSetPlant3)
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.
inspSpecAddlSeldCodeSetPlant3 - Key that uniquely identifies the plant assigned to the selected set.public void setInspSpecAdditionalCatalog4(@Nullable String inspSpecAdditionalCatalog4)
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.
inspSpecAdditionalCatalog4 - Main category by which code groups and codes are classified according to their contents (e.g.
characteristic attributes, defect types, usage decisions).public void setInspSpecAdditionalSelectedSet4(@Nullable String inspSpecAdditionalSelectedSet4)
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.
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.public void setInspSpecAdditionalCodeGroup4(@Nullable String inspSpecAdditionalCodeGroup4)
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.
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.public void setInspSpecAddlSeldCodeSetPlant4(@Nullable String inspSpecAddlSeldCodeSetPlant4)
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.
inspSpecAddlSeldCodeSetPlant4 - Key that uniquely identifies the plant assigned to the selected set.public void setInspSpecAdditionalCatalog5(@Nullable String inspSpecAdditionalCatalog5)
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.
inspSpecAdditionalCatalog5 - Main category by which code groups and codes are classified according to their contents (e.g.
characteristic attributes, defect types, usage decisions).public void setInspSpecAdditionalSelectedSet5(@Nullable String inspSpecAdditionalSelectedSet5)
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.
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.public void setInspSpecAdditionalCodeGroup5(@Nullable String inspSpecAdditionalCodeGroup5)
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.
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.public void setInspSpecAddlSeldCodeSetPlant5(@Nullable String inspSpecAddlSeldCodeSetPlant5)
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.
inspSpecAddlSeldCodeSetPlant5 - Key that uniquely identifies the plant assigned to the selected set.public void setSamplingProcedure(@Nullable String samplingProcedure)
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.
samplingProcedure - Procedure by which the sample size for an inspection is determined.public void setInspCharacteristicSampleUnit(@Nullable String inspCharacteristicSampleUnit)
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.
inspCharacteristicSampleUnit - The base unit of measure that is used to determine a sample for a characteristic.public void setBOOCharcSampleQuantity(@Nullable BigDecimal bOOCharcSampleQuantity)
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
bOOCharcSampleQuantity - Factor for calculating the sample unit.public void setInspSpecInformationField1(@Nullable String inspSpecInformationField1)
Original property name from the Odata EDM: InspSpecInformationField1
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.public void setInspSpecInformationField2(@Nullable String inspSpecInformationField2)
Original property name from the Odata EDM: InspSpecInformationField2
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.public void setInspSpecInformationField3(@Nullable String inspSpecInformationField3)
Original property name from the Odata EDM: InspSpecInformationField3
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.public void setInspectionSpecificationText(@Nullable String inspectionSpecificationText)
Original property name from the Odata EDM: InspectionSpecificationText
inspectionSpecificationText - Text of up to 40 characters that describes the object in more detail. This description is also known
as short text.public void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser - Name of user who created the record.public void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
The system enters the current system date.
creationDate - Date on which the data record was created.public void setLastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
lastChangedByUser - Name of the user who made the last change to this data record.public void setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
The system enters the current system date.
lastChangeDate - Date on which the data record was last changed.public void setBillOfOperationsVersion(@Nullable String billOfOperationsVersion)
Original property name from the Odata EDM: BillOfOperationsVersion
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.public void setChangedDateTime(@Nullable ZonedDateTime changedDateTime)
Original property name from the Odata EDM: ChangedDateTime
changedDateTime - The UTC time stamp is the date and time relative to UTC (Universal Coordinated Time).protected String getEntityCollection()
VdmEntitygetEntityCollection in class VdmEntity<InspPlanOpCharacteristic>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<InspPlanOpCharacteristic>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<InspPlanOpCharacteristic>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<InspPlanOpCharacteristic>@Nonnull public static <T> InspPlanOpCharacteristicField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T - The type of the extension field when performing value comparisons.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.@Nonnull public static <T,DomainT> InspPlanOpCharacteristicField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T - The type of the extension field when performing value comparisons.DomainT - The type of the extension field as returned by the OData service.typeConverter - A TypeConverterfieldName - The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntitygetDestinationForFetch in class VdmEntity<InspPlanOpCharacteristic>protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntityNote: 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.
setServicePathForFetch in class VdmEntity<InspPlanOpCharacteristic>public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntityNote: 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.
attachToService in class VdmEntity<InspPlanOpCharacteristic>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.protected String getDefaultServicePath()
VdmEntitygetDefaultServicePath in class VdmEntity<InspPlanOpCharacteristic>protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)@Nonnull public static InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder builder()
@Nullable public String getInspectionPlanGroup()
Original property name from the Odata EDM: InspectionPlanGroup
You can use groups, for example, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
@Nullable public String getBOOOperationInternalID()
Original property name from the Odata EDM: BOOOperationInternalID
@Nullable public String getBOOCharacteristic()
Original property name from the Odata EDM: BOOCharacteristic
@Nullable public String getBOOCharacteristicVersion()
Original property name from the Odata EDM: BOOCharacteristicVersion
@Nullable public String getBOOOpInternalVersionCounter()
Original property name from the Odata EDM: BOOOpInternalVersionCounter
@Nullable public String getInspectionPlanInternalVersion()
Original property name from the Odata EDM: InspectionPlanInternalVersion
@Nullable public String getInspectionPlan()
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.
@Nullable public LocalDateTime getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public LocalDateTime getValidityEndDate()
Original property name from the Odata EDM: ValidityEndDate
@Nullable public String getChangeNumber()
Original property name from the Odata EDM: ChangeNumber
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company
@Nullable public Boolean getIsDeleted()
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.
@Nullable public String getBOOOperationPRTInternalID()
Original property name from the Odata EDM: BOOOperationPRTInternalID
@Nullable public String getInspectionMethod()
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.
@Nullable public String getInspectionMethodVersion()
Original property name from the Odata EDM: InspectionMethodVersion
@Nullable public String getInspectionMethodPlant()
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.
@Nullable public String getInspSpecImportanceCode()
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.
@Nullable public String getInspectorQualification()
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.
@Nullable public String getInspectionSpecification()
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.
@Nullable public String getInspectionSpecificationVersion()
Original property name from the Odata EDM: InspectionSpecificationVersion
@Nullable public String getInspectionSpecificationPlant()
Original property name from the Odata EDM: InspectionSpecificationPlant
@Nullable public String getBOOCharcHasInspSpecReference()
Original property name from the Odata EDM: BOOCharcHasInspSpecReference
@Nullable public String getInspSpecControlIndicators()
Original property name from the Odata EDM: InspSpecControlIndicators
plan default valuesresults recordinginspection processing
@Nullable public String getInspSpecIsQuantitative()
Original property name from the Odata EDM: InspSpecIsQuantitative
@Nullable public String getInspSpecIsMeasuredValueRqd()
Original property name from the Odata EDM: InspSpecIsMeasuredValueRqd
@Nullable public String getInspSpecIsSelectedSetRequired()
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".
@Nullable public String getInspSpecIsUpperLimitRequired()
Original property name from the Odata EDM: InspSpecIsUpperLimitRequired
@Nullable public String getInspSpecIsLowerLimitRequired()
Original property name from the Odata EDM: InspSpecIsLowerLimitRequired
@Nullable public String getInspSpecIsTargetValueInLimit()
Original property name from the Odata EDM: InspSpecIsTargetValueInLimit
@Nullable public String getInspectionScope()
Original property name from the Odata EDM: InspectionScope
@Nullable public String getInspSpecIsLongTermInspection()
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.
@Nullable public String getInspSpecRecordingType()
Original property name from the Odata EDM: InspSpecRecordingType
@Nullable public String getInspResultIsDocumentationRqd()
Original property name from the Odata EDM: InspResultIsDocumentationRqd
@Nullable public String getInspSpecCharcCategory()
Original property name from the Odata EDM: InspSpecCharcCategory
@Nullable public String getInspSpecIsSampleQtyAdditive()
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.
@Nullable public String getInspSpecIsDestructive()
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.
@Nullable public String getInspSpecResultCalculation()
Original property name from the Odata EDM: InspSpecResultCalculation
@Nullable public String getInspSpecIsSamplingProcedRqd()
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.
@Nullable public String getInspSpecIsScrapRelevant()
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.
@Nullable public String getInspSpecHasFixedCtrlIndicators()
Original property name from the Odata EDM: InspSpecHasFixedCtrlIndicators
@Nullable public String getInspSpecIsTestEquipmentRqd()
Original property name from the Odata EDM: InspSpecIsTestEquipmentRqd
If you do not make an assignment, the system displays a warning message.
@Nullable public String getInspSpecIsDefectsRecgAutomatic()
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.
@Nullable public String getInspSpecIsChgDocRequired()
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.
@Nullable public String getInspSpecIsControlChartUsed()
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.
@Nullable public String getInspSpecPrintControl()
Original property name from the Odata EDM: InspSpecPrintControl
@Nullable public Double getInspSpecFirstUpperSpecLimit()
Original property name from the Odata EDM: InspSpecFirstUpperSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
@Nullable public String getInspSpecHasFirstUpperSpecLimit()
Original property name from the Odata EDM: InspSpecHasFirstUpperSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public Double getInspSpecFirstLowerSpecLimit()
Original property name from the Odata EDM: InspSpecFirstLowerSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
@Nullable public String getInspSpecHasFirstLowerSpecLimit()
Original property name from the Odata EDM: InspSpecHasFirstLowerSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public Double getInspSpecSecondUpperSpecLimit()
Original property name from the Odata EDM: InspSpecSecondUpperSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
@Nullable public String getInspSpecHasSecondUprSpecLimit()
Original property name from the Odata EDM: InspSpecHasSecondUprSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public Double getInspSpecSecondLowerSpecLimit()
Original property name from the Odata EDM: InspSpecSecondLowerSpecLimit
The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.
@Nullable public String getInspSpecHasSecondLowrSpecLimit()
Original property name from the Odata EDM: InspSpecHasSecondLowrSpecLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public String getInspSpecInputProcedure()
Original property name from the Odata EDM: InspSpecInputProcedure
Select a three-character key for input processing here. The measured value will be processed in accordance with this key, for example, it may be multiplied by a certain factor or rounded.You can implement a variety of rounding procedures using input processing, for example, rounding according to number of significant digits.Another possibility is the direct conversion of the measured value, for example, measured value is input in centimeters and immediately converted to millimeters.
@Nullable public String getInspSpecHasFormula()
Original property name from the Odata EDM: InspSpecHasFormula
If you do not set the indicator, the system does not check the formula or calculate it.In this case, you have to perform your own calculation (for example, by using the corresponding user exit).
@Nullable public String getInspSpecFormula1()
Original property name from the Odata EDM: InspSpecFormula1
In the task list (checked for correct syntax)The function module CHECK_FORMULA checks whether a formula stored as a literal or as variable has the correct syntax.In results recording (when the value of the calculated characteristic is to be calculated)A formula can be structured as follows (with the standard settings):Characteristic 10 stands for the length and characteristic 20 stands for the width. Characteristic 30 represents the area and is to be calculated from characteristics 10 and 20.Characteristic 30 is therefore a calculated characteristic with the following formula:General: Area = Length * WidthFormula interpreter: Area = ppnnnn * ppnnnn The variable 'pp' defines the formula parameter and 'nnnn' represents the characteristic from which the value of the formula parameter is taken.Example: Area = C00010 * C00020 'C0' stands for the arithmetic mean value and '0010' or '0020' for the respective characteristic.
@Nullable public String getInspSpecFormula2()
Original property name from the Odata EDM: InspSpecFormula2
In the task list (checked for correct syntax)The function module CHECK_FORMULA checks whether a formula stored as a literal or as variable has the correct syntax.In results recording (when the value of the calculated characteristic is to be calculated)A formula can be structured as follows (with the standard settings):Characteristic 10 stands for the length and characteristic 20 stands for the width. Characteristic 30 represents the area and is to be calculated from characteristics 10 and 20.Characteristic 30 is therefore a calculated characteristic with the following formula:General: Area = Length * WidthFormula interpreter: Area = ppnnnn * ppnnnn The variable 'pp' defines the formula parameter and 'nnnn' represents the characteristic from which the value of the formula parameter is taken.Example: Area = C00010 * C00020 'C0' stands for the arithmetic mean value and '0010' or '0020' for the respective characteristic.
@Nullable public Short getInspSpecNumberOfClasses()
Original property name from the Odata EDM: InspSpecNumberOfClasses
The number of classes is stored in this field, if the characteristic is treated as a quantitative characteristic whose values are managed with classes.In addition to the number entered here, marginal classes are maintained adjacent to the highest and lowest classes. The width of a marginal class is not limited on either the upper or lower end. In this way, the values that do not fit in any of the other classes are not lost; they are stored in the marginal classes.In this field you can enter EITHER a value or an *. If you enter an * the system calculates the number of classes as follows:number of classes = tolerance range / class widthYou must enter both specification limits (upper and lower) as well as the class width, so that the system can perform the calculation automatically.
@Nullable public Double getInspSpecClassWidthQty()
Original property name from the Odata EDM: InspSpecClassWidthQty
The class width is stored in this field, if the characteristic is treated as a quantitative characteristic whose values are managed with classes. The width of the classes is given in the same unit as the target value and the tolerances.All classes except for the marginal classes have the same width. For additional information about marginal classes, refer to the documentation about the number of classes.
@Nullable public String getInspSpecHasClassWidth()
Original property name from the Odata EDM: InspSpecHasClassWidth
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public Double getInspSpecClassMidpointQty()
Original property name from the Odata EDM: InspSpecClassMidpointQty
The class midpoint is stored in this field, if the characteristic is treated as a quantitative characteristic whose values are managed with classes.With an uneven number of classes, the classes are laid out so that the value entered here lies in the middle of the middle class.With an even number of classes, this value becomes the limit value of the two classes in the middle.
@Nullable public String getInspSpecHasClassMidpoint()
Original property name from the Odata EDM: InspSpecHasClassMidpoint
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public String getInspToleranceSpecification()
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.
@Nullable public Short getInspSpecDecimalPlaces()
Original property name from the Odata EDM: InspSpecDecimalPlaces
@Nullable public String getInspectionSpecificationUnit()
Original property name from the Odata EDM: InspectionSpecificationUnit
@Nullable public Double getInspSpecTargetValue()
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.
@Nullable public String getInspSpecHasTargetValue()
Original property name from the Odata EDM: InspSpecHasTargetValue
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public Double getInspSpecUpperLimit()
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.
@Nullable public Double getInspSpecLowerLimit()
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.
@Nullable public String getInspSpecHasLowerLimit()
Original property name from the Odata EDM: InspSpecHasLowerLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public String getInspSpecHasUpperLimit()
Original property name from the Odata EDM: InspSpecHasUpperLimit
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public String getInspSpecDefectCodeGrpRejection()
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.
@Nullable public String getInspSpecDefectCodeRejection()
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.
@Nullable public String getInspSpecDefectCodeGrpRjcnUpper()
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.
@Nullable public String getInspSpecDefectCodeRjcnUpper()
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.
@Nullable public String getInspSpecDefectCodeGrpRjcnLower()
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.
@Nullable public String getInspSpecDefectCodeRjcnLower()
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.
@Nullable public String getSelectedCodeSet()
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.
@Nullable public String getSelectedCodeSetPlant()
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.
@Nullable public String getInspSpecAdditionalCatalog2()
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.
@Nullable public String getInspSpecAdditionalSelectedSet2()
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.
@Nullable public String getInspSpecAdditionalCodeGroup2()
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.
@Nullable public String getInspSpecAddlSeldCodeSetPlant2()
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.
@Nullable public String getInspSpecAdditionalCatalog3()
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.
@Nullable public String getInspSpecAdditionalSelectedSet3()
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.
@Nullable public String getInspSpecAdditionalCodeGroup3()
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.
@Nullable public String getInspSpecAddlSeldCodeSetPlant3()
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.
@Nullable public String getInspSpecAdditionalCatalog4()
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.
@Nullable public String getInspSpecAdditionalSelectedSet4()
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.
@Nullable public String getInspSpecAdditionalCodeGroup4()
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.
@Nullable public String getInspSpecAddlSeldCodeSetPlant4()
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.
@Nullable public String getInspSpecAdditionalCatalog5()
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.
@Nullable public String getInspSpecAdditionalSelectedSet5()
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.
@Nullable public String getInspSpecAdditionalCodeGroup5()
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.
@Nullable public String getInspSpecAddlSeldCodeSetPlant5()
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.
@Nullable public String getSamplingProcedure()
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.
@Nullable public String getInspCharacteristicSampleUnit()
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.
@Nullable public BigDecimal getBOOCharcSampleQuantity()
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
@Nullable public String getInspSpecInformationField1()
Original property name from the Odata EDM: InspSpecInformationField1
@Nullable public String getInspSpecInformationField2()
Original property name from the Odata EDM: InspSpecInformationField2
@Nullable public String getInspSpecInformationField3()
Original property name from the Odata EDM: InspSpecInformationField3
@Nullable public String getInspectionSpecificationText()
Original property name from the Odata EDM: InspectionSpecificationText
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
The system enters the current system date.
@Nullable public String getLastChangedByUser()
Original property name from the Odata EDM: LastChangedByUser
@Nullable public LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
The system enters the current system date.
@Nullable public String getBillOfOperationsVersion()
Original property name from the Odata EDM: BillOfOperationsVersion
@Nullable public ZonedDateTime getChangedDateTime()
Original property name from the Odata EDM: ChangedDateTime
@Nonnull public String toString()
toString in class VdmObject<InspPlanOpCharacteristic>public boolean equals(@Nullable Object o)
equals in class VdmObject<InspPlanOpCharacteristic>protected boolean canEqual(@Nullable Object other)
canEqual in class VdmObject<InspPlanOpCharacteristic>public int hashCode()
hashCode in class VdmObject<InspPlanOpCharacteristic>Copyright © 2021 SAP SE. All rights reserved.