public class InspectionSpecification extends VdmEntity<InspectionSpecification>
Original entity name from the Odata EDM: A_InspectionSpecificationType
Modifier and Type | Class and Description |
---|---|
static class |
InspectionSpecification.InspectionSpecificationBuilder |
Modifier and Type | Field and Description |
---|---|
static InspectionSpecificationSelectable |
ALL_FIELDS
Selector for all available fields of InspectionSpecification.
|
static InspectionSpecificationField<String> |
CHARACTERISTIC_INTERNAL_ID
Use with available fluent helpers to apply the CharacteristicInternalID field to query operations.
|
static InspectionSpecificationField<String> |
DEFECT_FRACTION_ESTIMATION_PROCED
Use with available fluent helpers to apply the DefectFractionEstimationProced field to query operations.
|
static InspectionSpecificationField<String> |
INSP_RESULT_IS_DOCUMENTATION_RQD
Use with available fluent helpers to apply the InspResultIsDocumentationRqd field to query operations.
|
static InspectionSpecificationField<LocalDateTime> |
INSP_SPEC_CHANGE_DATE
Use with available fluent helpers to apply the InspSpecChangeDate field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_CHANGED_BY_USER
Use with available fluent helpers to apply the InspSpecChangedByUser field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_CHARACTERISTIC_TYPE
Use with available fluent helpers to apply the InspSpecCharacteristicType field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_CHARC_CATEGORY
Use with available fluent helpers to apply the InspSpecCharcCategory field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_CREATED_BY_USER
Use with available fluent helpers to apply the InspSpecCreatedByUser field to query operations.
|
static InspectionSpecificationField<LocalDateTime> |
INSP_SPEC_CREATION_DATE
Use with available fluent helpers to apply the InspSpecCreationDate field to query operations.
|
static InspectionSpecificationField<Short> |
INSP_SPEC_DECIMAL_PLACES
Use with available fluent helpers to apply the InspSpecDecimalPlaces field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_DEFECT_CODE_GRP_REJECTION
Use with available fluent helpers to apply the InspSpecDefectCodeGrpRejection field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER
Use with available fluent helpers to apply the InspSpecDefectCodeGrpRjcnLower field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER
Use with available fluent helpers to apply the InspSpecDefectCodeGrpRjcnUpper field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_DEFECT_CODE_REJECTION
Use with available fluent helpers to apply the InspSpecDefectCodeRejection field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_DEFECT_CODE_RJCN_LOWER
Use with available fluent helpers to apply the InspSpecDefectCodeRjcnLower field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_DEFECT_CODE_RJCN_UPPER
Use with available fluent helpers to apply the InspSpecDefectCodeRjcnUpper field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_FIRST_LOWER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecFirstLowerSpecLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_FIRST_UPPER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecFirstUpperSpecLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_GLOBAL_NAME
Use with available fluent helpers to apply the InspSpecGlobalName field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_FIRST_LOWER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasFirstLowerSpecLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_FIRST_UPPER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasFirstUpperSpecLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_LOWER_LIMIT
Use with available fluent helpers to apply the InspSpecHasLowerLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_LOWR_PLAUSIBILITY_LMT
Use with available fluent helpers to apply the InspSpecHasLowrPlausibilityLmt field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_LOWR_SPEC_LIMIT_CHANGE
Use with available fluent helpers to apply the InspSpecHasLowrSpecLimitChange field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_SECOND_LOWR_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasSecondLowrSpecLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_SECOND_UPR_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecHasSecondUprSpecLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_TARGET_VALUE
Use with available fluent helpers to apply the InspSpecHasTargetValue field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_UPPER_LIMIT
Use with available fluent helpers to apply the InspSpecHasUpperLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_UPR_PLAUSIBILITY_LMT
Use with available fluent helpers to apply the InspSpecHasUprPlausibilityLmt field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_HAS_UPR_SPEC_LIMIT_CHANGE
Use with available fluent helpers to apply the InspSpecHasUprSpecLimitChange field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IMPORTANCE_CODE
Use with available fluent helpers to apply the InspSpecImportanceCode field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_INFORMATION_FIELD1
Use with available fluent helpers to apply the InspSpecInformationField1 field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_INFORMATION_FIELD2
Use with available fluent helpers to apply the InspSpecInformationField2 field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_INFORMATION_FIELD3
Use with available fluent helpers to apply the InspSpecInformationField3 field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_CHG_DOC_REQUIRED
Use with available fluent helpers to apply the InspSpecIsChgDocRequired field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_CONTROL_CHART_USED
Use with available fluent helpers to apply the InspSpecIsControlChartUsed field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC
Use with available fluent helpers to apply the InspSpecIsDefectsRecgAutomatic field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_DESTRUCTIVE
Use with available fluent helpers to apply the InspSpecIsDestructive field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_LONG_TERM_INSPECTION
Use with available fluent helpers to apply the InspSpecIsLongTermInspection field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_LOWER_LIMIT_REQUIRED
Use with available fluent helpers to apply the InspSpecIsLowerLimitRequired field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_MEASURED_VALUE_RQD
Use with available fluent helpers to apply the InspSpecIsMeasuredValueRqd field to query operations.
|
static InspectionSpecificationField<Boolean> |
INSP_SPEC_IS_QUANTITATIVE
Use with available fluent helpers to apply the InspSpecIsQuantitative field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE
Use with available fluent helpers to apply the InspSpecIsSampleQtyAdditive field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_SAMPLING_PROCED_RQD
Use with available fluent helpers to apply the InspSpecIsSamplingProcedRqd field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_SCRAP_RELEVANT
Use with available fluent helpers to apply the InspSpecIsScrapRelevant field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_SELECTED_SET_REQUIRED
Use with available fluent helpers to apply the InspSpecIsSelectedSetRequired field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT
Use with available fluent helpers to apply the InspSpecIsTargetValueInLimit field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_TEST_EQUIPMENT_RQD
Use with available fluent helpers to apply the InspSpecIsTestEquipmentRqd field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_IS_UPPER_LIMIT_REQUIRED
Use with available fluent helpers to apply the InspSpecIsUpperLimitRequired field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_LOWER_LIMIT
Use with available fluent helpers to apply the InspSpecLowerLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_LOWER_PLAUSIBILITY_LIMIT
Use with available fluent helpers to apply the InspSpecLowerPlausibilityLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_LOWER_SPEC_LIMIT_CHANGE
Use with available fluent helpers to apply the InspSpecLowerSpecLimitChange field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_PRINT_CONTROL
Use with available fluent helpers to apply the InspSpecPrintControl field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_RECORDING_TYPE
Use with available fluent helpers to apply the InspSpecRecordingType field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_RESULT_CALCULATION
Use with available fluent helpers to apply the InspSpecResultCalculation field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_SECOND_LOWER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecSecondLowerSpecLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_SECOND_UPPER_SPEC_LIMIT
Use with available fluent helpers to apply the InspSpecSecondUpperSpecLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_TARGET_VALUE
Use with available fluent helpers to apply the InspSpecTargetValue field to query operations.
|
static InspectionSpecificationField<LocalDateTime> |
INSP_SPEC_TOLERANCE_CHG_VALID_FROM
Use with available fluent helpers to apply the InspSpecToleranceChgValidFrom field to query operations.
|
static InspectionSpecificationField<LocalDateTime> |
INSP_SPEC_TOLERANCE_CHG_VALID_TO
Use with available fluent helpers to apply the InspSpecToleranceChgValidTo field to query operations.
|
static InspectionSpecificationField<String> |
INSP_SPEC_TRANSFER_TYPE
Use with available fluent helpers to apply the InspSpecTransferType field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_UPPER_LIMIT
Use with available fluent helpers to apply the InspSpecUpperLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_UPPER_PLAUSIBILITY_LIMIT
Use with available fluent helpers to apply the InspSpecUpperPlausibilityLimit field to query operations.
|
static InspectionSpecificationField<Double> |
INSP_SPEC_UPPER_SPEC_LIMIT_CHANGE
Use with available fluent helpers to apply the InspSpecUpperSpecLimitChange field to query operations.
|
static InspectionSpecificationField<String> |
INSP_TOLERANCE_SPECIFICATION
Use with available fluent helpers to apply the InspToleranceSpecification field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SCOPE
Use with available fluent helpers to apply the InspectionScope field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SPECIFICATION
Use with available fluent helpers to apply the InspectionSpecification field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SPECIFICATION_PLANT
Use with available fluent helpers to apply the InspectionSpecificationPlant field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SPECIFICATION_SRCH_TXT
Use with available fluent helpers to apply the InspectionSpecificationSrchTxt field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SPECIFICATION_STATUS
Use with available fluent helpers to apply the InspectionSpecificationStatus field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SPECIFICATION_UNIT
Use with available fluent helpers to apply the InspectionSpecificationUnit field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTION_SPECIFICATION_VERSION
Use with available fluent helpers to apply the InspectionSpecificationVersion field to query operations.
|
static InspectionSpecificationField<String> |
INSPECTOR_QUALIFICATION
Use with available fluent helpers to apply the InspectorQualification field to query operations.
|
static InspectionSpecificationField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static InspectionSpecificationField<String> |
QLTY_MSTR_DATA_AUTHORIZATION_GROUP
Use with available fluent helpers to apply the QltyMstrDataAuthorizationGroup field to query operations.
|
static InspectionSpecificationField<LocalDateTime> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
InspectionSpecification() |
InspectionSpecification(String inspectionSpecification,
String inspectionSpecificationVersion,
String inspectionSpecificationPlant,
String plant,
LocalDateTime validityStartDate,
String inspectionSpecificationSrchTxt,
String inspSpecGlobalName,
String inspectionSpecificationStatus,
String inspSpecTransferType,
String inspSpecCreatedByUser,
LocalDateTime inspSpecCreationDate,
String inspSpecChangedByUser,
LocalDateTime inspSpecChangeDate,
Boolean inspSpecIsQuantitative,
String inspSpecCharacteristicType,
String inspSpecIsMeasuredValueRqd,
String inspSpecIsSelectedSetRequired,
String inspSpecIsUpperLimitRequired,
String inspSpecIsLowerLimitRequired,
String inspSpecIsTargetValueInLimit,
String inspectionScope,
String inspSpecIsLongTermInspection,
String inspSpecRecordingType,
String inspResultIsDocumentationRqd,
String inspSpecCharcCategory,
String inspSpecIsDefectsRecgAutomatic,
String inspSpecIsSampleQtyAdditive,
String inspSpecIsDestructive,
String inspSpecResultCalculation,
String inspSpecIsSamplingProcedRqd,
String inspSpecIsScrapRelevant,
String inspSpecIsTestEquipmentRqd,
String inspSpecIsChgDocRequired,
String inspSpecIsControlChartUsed,
String inspSpecPrintControl,
String inspSpecImportanceCode,
String inspectorQualification,
String inspSpecInformationField1,
String inspSpecInformationField2,
String inspSpecInformationField3,
String qltyMstrDataAuthorizationGroup,
String inspToleranceSpecification,
Short inspSpecDecimalPlaces,
String inspectionSpecificationUnit,
Double inspSpecTargetValue,
String inspSpecHasTargetValue,
Double inspSpecLowerLimit,
String inspSpecHasLowerLimit,
Double inspSpecLowerPlausibilityLimit,
String inspSpecHasLowrPlausibilityLmt,
Double inspSpecFirstLowerSpecLimit,
String inspSpecHasFirstLowerSpecLimit,
Double inspSpecSecondLowerSpecLimit,
String inspSpecHasSecondLowrSpecLimit,
Double inspSpecLowerSpecLimitChange,
String inspSpecHasLowrSpecLimitChange,
Double inspSpecUpperLimit,
String inspSpecHasUpperLimit,
Double inspSpecUpperPlausibilityLimit,
String inspSpecHasUprPlausibilityLmt,
Double inspSpecFirstUpperSpecLimit,
String inspSpecHasFirstUpperSpecLimit,
Double inspSpecSecondUpperSpecLimit,
String inspSpecHasSecondUprSpecLimit,
Double inspSpecUpperSpecLimitChange,
String inspSpecHasUprSpecLimitChange,
LocalDateTime inspSpecToleranceChgValidFrom,
LocalDateTime inspSpecToleranceChgValidTo,
String inspSpecDefectCodeGrpRejection,
String inspSpecDefectCodeRejection,
String inspSpecDefectCodeGrpRjcnUpper,
String inspSpecDefectCodeRjcnUpper,
String inspSpecDefectCodeGrpRjcnLower,
String inspSpecDefectCodeRjcnLower,
String characteristicInternalID,
String defectFractionEstimationProced) |
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 InspectionSpecification.InspectionSpecificationBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> InspectionSpecificationField<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 |
getCharacteristicInternalID()
Constraints: Not nullable, Maximum length: 30
|
protected String |
getDefaultServicePath() |
String |
getDefectFractionEstimationProced()
Constraints: Not nullable, Maximum length: 2
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection() |
String |
getInspectionScope()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspectionSpecification()
(Key Field) Constraints: Not nullable, Maximum length: 8
|
String |
getInspectionSpecificationPlant()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getInspectionSpecificationSrchTxt()
Constraints: Not nullable, Maximum length: 40
|
String |
getInspectionSpecificationStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspectionSpecificationUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getInspectionSpecificationVersion()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getInspectorQualification()
Constraints: Not nullable, Maximum length: 5
|
String |
getInspResultIsDocumentationRqd()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getInspSpecChangeDate()
Constraints: Not nullable, Precision: 0
|
String |
getInspSpecChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
String |
getInspSpecCharacteristicType()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecCharcCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getInspSpecCreationDate()
Constraints: Not nullable, Precision: 0
|
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 |
getInspSpecGlobalName()
Constraints: Not nullable, Maximum length: 40
|
String |
getInspSpecHasFirstLowerSpecLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasFirstUpperSpecLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasLowerLimit()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasLowrPlausibilityLmt()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasLowrSpecLimitChange()
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 |
getInspSpecHasUprPlausibilityLmt()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecHasUprSpecLimitChange()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecImportanceCode()
Constraints: Not nullable, Maximum length: 2
|
String |
getInspSpecInformationField1()
Constraints: Not nullable, Maximum length: 10
|
String |
getInspSpecInformationField2()
Constraints: Not nullable, Maximum length: 20
|
String |
getInspSpecInformationField3()
Constraints: Not nullable, Maximum length: 40
|
String |
getInspSpecIsChgDocRequired()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecIsControlChartUsed()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecIsDefectsRecgAutomatic()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecIsDestructive()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecIsLongTermInspection()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecIsLowerLimitRequired()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSpecIsMeasuredValueRqd()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getInspSpecIsQuantitative()
Constraints: none
|
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
|
Double |
getInspSpecLowerPlausibilityLimit()
Constraints: none
|
Double |
getInspSpecLowerSpecLimitChange()
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
|
LocalDateTime |
getInspSpecToleranceChgValidFrom()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getInspSpecToleranceChgValidTo()
Constraints: Not nullable, Precision: 0
|
String |
getInspSpecTransferType()
Constraints: Not nullable, Maximum length: 1
|
Double |
getInspSpecUpperLimit()
Constraints: none
|
Double |
getInspSpecUpperPlausibilityLimit()
Constraints: none
|
Double |
getInspSpecUpperSpecLimitChange()
Constraints: none
|
String |
getInspToleranceSpecification()
Constraints: Not nullable, Maximum length: 4
|
protected Map<String,Object> |
getKey() |
String |
getPlant()
Constraints: Not nullable, Maximum length: 4
|
String |
getQltyMstrDataAuthorizationGroup()
Constraints: Not nullable, Maximum length: 8
|
Class<InspectionSpecification> |
getType() |
LocalDateTime |
getValidityStartDate()
Constraints: Not nullable, Precision: 0
|
int |
hashCode() |
void |
setCharacteristicInternalID(String characteristicInternalID)
Constraints: Not nullable, Maximum length: 30
|
void |
setDefectFractionEstimationProced(String defectFractionEstimationProced)
Constraints: Not nullable, Maximum length: 2
|
void |
setInspectionScope(String inspectionScope)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspectionSpecification(String inspectionSpecification)
(Key Field) Constraints: Not nullable, Maximum length: 8
|
void |
setInspectionSpecificationPlant(String inspectionSpecificationPlant)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setInspectionSpecificationSrchTxt(String inspectionSpecificationSrchTxt)
Constraints: Not nullable, Maximum length: 40
|
void |
setInspectionSpecificationStatus(String inspectionSpecificationStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspectionSpecificationUnit(String inspectionSpecificationUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setInspectionSpecificationVersion(String inspectionSpecificationVersion)
(Key Field) 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 |
setInspSpecChangeDate(LocalDateTime inspSpecChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setInspSpecChangedByUser(String inspSpecChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setInspSpecCharacteristicType(String inspSpecCharacteristicType)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecCharcCategory(String inspSpecCharcCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecCreatedByUser(String inspSpecCreatedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setInspSpecCreationDate(LocalDateTime inspSpecCreationDate)
Constraints: Not nullable, Precision: 0
|
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 |
setInspSpecGlobalName(String inspSpecGlobalName)
Constraints: Not nullable, Maximum length: 40
|
void |
setInspSpecHasFirstLowerSpecLimit(String inspSpecHasFirstLowerSpecLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasFirstUpperSpecLimit(String inspSpecHasFirstUpperSpecLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasLowerLimit(String inspSpecHasLowerLimit)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasLowrPlausibilityLmt(String inspSpecHasLowrPlausibilityLmt)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasLowrSpecLimitChange(String inspSpecHasLowrSpecLimitChange)
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 |
setInspSpecHasUprPlausibilityLmt(String inspSpecHasUprPlausibilityLmt)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecHasUprSpecLimitChange(String inspSpecHasUprSpecLimitChange)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecImportanceCode(String inspSpecImportanceCode)
Constraints: Not nullable, Maximum length: 2
|
void |
setInspSpecInformationField1(String inspSpecInformationField1)
Constraints: Not nullable, Maximum length: 10
|
void |
setInspSpecInformationField2(String inspSpecInformationField2)
Constraints: Not nullable, Maximum length: 20
|
void |
setInspSpecInformationField3(String inspSpecInformationField3)
Constraints: Not nullable, Maximum length: 40
|
void |
setInspSpecIsChgDocRequired(String inspSpecIsChgDocRequired)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsControlChartUsed(String inspSpecIsControlChartUsed)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsDefectsRecgAutomatic(String inspSpecIsDefectsRecgAutomatic)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsDestructive(String inspSpecIsDestructive)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsLongTermInspection(String inspSpecIsLongTermInspection)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsLowerLimitRequired(String inspSpecIsLowerLimitRequired)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsMeasuredValueRqd(String inspSpecIsMeasuredValueRqd)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecIsQuantitative(Boolean inspSpecIsQuantitative)
Constraints: none
|
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 |
setInspSpecLowerPlausibilityLimit(Double inspSpecLowerPlausibilityLimit)
Constraints: none
|
void |
setInspSpecLowerSpecLimitChange(Double inspSpecLowerSpecLimitChange)
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 |
setInspSpecToleranceChgValidFrom(LocalDateTime inspSpecToleranceChgValidFrom)
Constraints: Not nullable, Precision: 0
|
void |
setInspSpecToleranceChgValidTo(LocalDateTime inspSpecToleranceChgValidTo)
Constraints: Not nullable, Precision: 0
|
void |
setInspSpecTransferType(String inspSpecTransferType)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSpecUpperLimit(Double inspSpecUpperLimit)
Constraints: none
|
void |
setInspSpecUpperPlausibilityLimit(Double inspSpecUpperPlausibilityLimit)
Constraints: none
|
void |
setInspSpecUpperSpecLimitChange(Double inspSpecUpperSpecLimitChange)
Constraints: none
|
void |
setInspToleranceSpecification(String inspToleranceSpecification)
Constraints: Not nullable, Maximum length: 4
|
void |
setPlant(String plant)
Constraints: Not nullable, Maximum length: 4
|
void |
setQltyMstrDataAuthorizationGroup(String qltyMstrDataAuthorizationGroup)
Constraints: Not nullable, Maximum length: 8
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setValidityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 0
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final InspectionSpecificationSelectable ALL_FIELDS
public static final InspectionSpecificationField<String> INSPECTION_SPECIFICATION
public static final InspectionSpecificationField<String> INSPECTION_SPECIFICATION_VERSION
public static final InspectionSpecificationField<String> INSPECTION_SPECIFICATION_PLANT
public static final InspectionSpecificationField<String> PLANT
public static final InspectionSpecificationField<LocalDateTime> VALIDITY_START_DATE
public static final InspectionSpecificationField<String> INSPECTION_SPECIFICATION_SRCH_TXT
public static final InspectionSpecificationField<String> INSP_SPEC_GLOBAL_NAME
public static final InspectionSpecificationField<String> INSPECTION_SPECIFICATION_STATUS
public static final InspectionSpecificationField<String> INSP_SPEC_TRANSFER_TYPE
public static final InspectionSpecificationField<String> INSP_SPEC_CREATED_BY_USER
public static final InspectionSpecificationField<LocalDateTime> INSP_SPEC_CREATION_DATE
public static final InspectionSpecificationField<String> INSP_SPEC_CHANGED_BY_USER
public static final InspectionSpecificationField<LocalDateTime> INSP_SPEC_CHANGE_DATE
public static final InspectionSpecificationField<Boolean> INSP_SPEC_IS_QUANTITATIVE
public static final InspectionSpecificationField<String> INSP_SPEC_CHARACTERISTIC_TYPE
public static final InspectionSpecificationField<String> INSP_SPEC_IS_MEASURED_VALUE_RQD
public static final InspectionSpecificationField<String> INSP_SPEC_IS_SELECTED_SET_REQUIRED
public static final InspectionSpecificationField<String> INSP_SPEC_IS_UPPER_LIMIT_REQUIRED
public static final InspectionSpecificationField<String> INSP_SPEC_IS_LOWER_LIMIT_REQUIRED
public static final InspectionSpecificationField<String> INSP_SPEC_IS_TARGET_VALUE_IN_LIMIT
public static final InspectionSpecificationField<String> INSPECTION_SCOPE
public static final InspectionSpecificationField<String> INSP_SPEC_IS_LONG_TERM_INSPECTION
public static final InspectionSpecificationField<String> INSP_SPEC_RECORDING_TYPE
public static final InspectionSpecificationField<String> INSP_RESULT_IS_DOCUMENTATION_RQD
public static final InspectionSpecificationField<String> INSP_SPEC_CHARC_CATEGORY
public static final InspectionSpecificationField<String> INSP_SPEC_IS_DEFECTS_RECG_AUTOMATIC
public static final InspectionSpecificationField<String> INSP_SPEC_IS_SAMPLE_QTY_ADDITIVE
public static final InspectionSpecificationField<String> INSP_SPEC_IS_DESTRUCTIVE
public static final InspectionSpecificationField<String> INSP_SPEC_RESULT_CALCULATION
public static final InspectionSpecificationField<String> INSP_SPEC_IS_SAMPLING_PROCED_RQD
public static final InspectionSpecificationField<String> INSP_SPEC_IS_SCRAP_RELEVANT
public static final InspectionSpecificationField<String> INSP_SPEC_IS_TEST_EQUIPMENT_RQD
public static final InspectionSpecificationField<String> INSP_SPEC_IS_CHG_DOC_REQUIRED
public static final InspectionSpecificationField<String> INSP_SPEC_IS_CONTROL_CHART_USED
public static final InspectionSpecificationField<String> INSP_SPEC_PRINT_CONTROL
public static final InspectionSpecificationField<String> INSP_SPEC_IMPORTANCE_CODE
public static final InspectionSpecificationField<String> INSPECTOR_QUALIFICATION
public static final InspectionSpecificationField<String> INSP_SPEC_INFORMATION_FIELD1
public static final InspectionSpecificationField<String> INSP_SPEC_INFORMATION_FIELD2
public static final InspectionSpecificationField<String> INSP_SPEC_INFORMATION_FIELD3
public static final InspectionSpecificationField<String> QLTY_MSTR_DATA_AUTHORIZATION_GROUP
public static final InspectionSpecificationField<String> INSP_TOLERANCE_SPECIFICATION
public static final InspectionSpecificationField<Short> INSP_SPEC_DECIMAL_PLACES
public static final InspectionSpecificationField<String> INSPECTION_SPECIFICATION_UNIT
public static final InspectionSpecificationField<Double> INSP_SPEC_TARGET_VALUE
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_TARGET_VALUE
public static final InspectionSpecificationField<Double> INSP_SPEC_LOWER_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_LOWER_LIMIT
public static final InspectionSpecificationField<Double> INSP_SPEC_LOWER_PLAUSIBILITY_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_LOWR_PLAUSIBILITY_LMT
public static final InspectionSpecificationField<Double> INSP_SPEC_FIRST_LOWER_SPEC_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_FIRST_LOWER_SPEC_LIMIT
public static final InspectionSpecificationField<Double> INSP_SPEC_SECOND_LOWER_SPEC_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_SECOND_LOWR_SPEC_LIMIT
public static final InspectionSpecificationField<Double> INSP_SPEC_LOWER_SPEC_LIMIT_CHANGE
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_LOWR_SPEC_LIMIT_CHANGE
public static final InspectionSpecificationField<Double> INSP_SPEC_UPPER_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_UPPER_LIMIT
public static final InspectionSpecificationField<Double> INSP_SPEC_UPPER_PLAUSIBILITY_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_UPR_PLAUSIBILITY_LMT
public static final InspectionSpecificationField<Double> INSP_SPEC_FIRST_UPPER_SPEC_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_FIRST_UPPER_SPEC_LIMIT
public static final InspectionSpecificationField<Double> INSP_SPEC_SECOND_UPPER_SPEC_LIMIT
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_SECOND_UPR_SPEC_LIMIT
public static final InspectionSpecificationField<Double> INSP_SPEC_UPPER_SPEC_LIMIT_CHANGE
public static final InspectionSpecificationField<String> INSP_SPEC_HAS_UPR_SPEC_LIMIT_CHANGE
public static final InspectionSpecificationField<LocalDateTime> INSP_SPEC_TOLERANCE_CHG_VALID_FROM
public static final InspectionSpecificationField<LocalDateTime> INSP_SPEC_TOLERANCE_CHG_VALID_TO
public static final InspectionSpecificationField<String> INSP_SPEC_DEFECT_CODE_GRP_REJECTION
public static final InspectionSpecificationField<String> INSP_SPEC_DEFECT_CODE_REJECTION
public static final InspectionSpecificationField<String> INSP_SPEC_DEFECT_CODE_GRP_RJCN_UPPER
public static final InspectionSpecificationField<String> INSP_SPEC_DEFECT_CODE_RJCN_UPPER
public static final InspectionSpecificationField<String> INSP_SPEC_DEFECT_CODE_GRP_RJCN_LOWER
public static final InspectionSpecificationField<String> INSP_SPEC_DEFECT_CODE_RJCN_LOWER
public static final InspectionSpecificationField<String> CHARACTERISTIC_INTERNAL_ID
public static final InspectionSpecificationField<String> DEFECT_FRACTION_ESTIMATION_PROCED
public InspectionSpecification()
public InspectionSpecification(@Nullable String inspectionSpecification, @Nullable String inspectionSpecificationVersion, @Nullable String inspectionSpecificationPlant, @Nullable String plant, @Nullable LocalDateTime validityStartDate, @Nullable String inspectionSpecificationSrchTxt, @Nullable String inspSpecGlobalName, @Nullable String inspectionSpecificationStatus, @Nullable String inspSpecTransferType, @Nullable String inspSpecCreatedByUser, @Nullable LocalDateTime inspSpecCreationDate, @Nullable String inspSpecChangedByUser, @Nullable LocalDateTime inspSpecChangeDate, @Nullable Boolean inspSpecIsQuantitative, @Nullable String inspSpecCharacteristicType, @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 inspSpecIsDefectsRecgAutomatic, @Nullable String inspSpecIsSampleQtyAdditive, @Nullable String inspSpecIsDestructive, @Nullable String inspSpecResultCalculation, @Nullable String inspSpecIsSamplingProcedRqd, @Nullable String inspSpecIsScrapRelevant, @Nullable String inspSpecIsTestEquipmentRqd, @Nullable String inspSpecIsChgDocRequired, @Nullable String inspSpecIsControlChartUsed, @Nullable String inspSpecPrintControl, @Nullable String inspSpecImportanceCode, @Nullable String inspectorQualification, @Nullable String inspSpecInformationField1, @Nullable String inspSpecInformationField2, @Nullable String inspSpecInformationField3, @Nullable String qltyMstrDataAuthorizationGroup, @Nullable String inspToleranceSpecification, @Nullable Short inspSpecDecimalPlaces, @Nullable String inspectionSpecificationUnit, @Nullable Double inspSpecTargetValue, @Nullable String inspSpecHasTargetValue, @Nullable Double inspSpecLowerLimit, @Nullable String inspSpecHasLowerLimit, @Nullable Double inspSpecLowerPlausibilityLimit, @Nullable String inspSpecHasLowrPlausibilityLmt, @Nullable Double inspSpecFirstLowerSpecLimit, @Nullable String inspSpecHasFirstLowerSpecLimit, @Nullable Double inspSpecSecondLowerSpecLimit, @Nullable String inspSpecHasSecondLowrSpecLimit, @Nullable Double inspSpecLowerSpecLimitChange, @Nullable String inspSpecHasLowrSpecLimitChange, @Nullable Double inspSpecUpperLimit, @Nullable String inspSpecHasUpperLimit, @Nullable Double inspSpecUpperPlausibilityLimit, @Nullable String inspSpecHasUprPlausibilityLmt, @Nullable Double inspSpecFirstUpperSpecLimit, @Nullable String inspSpecHasFirstUpperSpecLimit, @Nullable Double inspSpecSecondUpperSpecLimit, @Nullable String inspSpecHasSecondUprSpecLimit, @Nullable Double inspSpecUpperSpecLimitChange, @Nullable String inspSpecHasUprSpecLimitChange, @Nullable LocalDateTime inspSpecToleranceChgValidFrom, @Nullable LocalDateTime inspSpecToleranceChgValidTo, @Nullable String inspSpecDefectCodeGrpRejection, @Nullable String inspSpecDefectCodeRejection, @Nullable String inspSpecDefectCodeGrpRjcnUpper, @Nullable String inspSpecDefectCodeRjcnUpper, @Nullable String inspSpecDefectCodeGrpRjcnLower, @Nullable String inspSpecDefectCodeRjcnLower, @Nullable String characteristicInternalID, @Nullable String defectFractionEstimationProced)
@Nonnull public Class<InspectionSpecification> getType()
getType
in class VdmObject<InspectionSpecification>
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 the Master Inspection Characteristicpublic void setInspectionSpecificationPlant(@Nullable String inspectionSpecificationPlant)
Original property name from the Odata EDM: InspectionSpecificationPlant
inspectionSpecificationPlant
- Plant for the Master Inspection Characteristicpublic void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.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 setInspectionSpecificationSrchTxt(@Nullable String inspectionSpecificationSrchTxt)
Original property name from the Odata EDM: InspectionSpecificationSrchTxt
Enter a meaningful word or phrase in this language-independent field. The entry you make should be easy to remember and should identify the master data record uniquely.
inspectionSpecificationSrchTxt
- This field uses the search help to make it easier to find master data records.public void setInspSpecGlobalName(@Nullable String inspSpecGlobalName)
Original property name from the Odata EDM: InspSpecGlobalName
In this field, you can define an additional characteristic description (40 characters long) in the inspection plan, material specification, master inspection characteristic, and certificate profile. This description acts as the characteristic identification for the electronic exchange of characteristic values.
inspSpecGlobalName
- Identification description for a characteristic.public void setInspectionSpecificationStatus(@Nullable String inspectionSpecificationStatus)
Original property name from the Odata EDM: InspectionSpecificationStatus
inspectionSpecificationStatus
- Indicates the processing status of the master record; for example, created, released, blocked, marked
for deletion.public void setInspSpecTransferType(@Nullable String inspSpecTransferType)
Original property name from the Odata EDM: InspSpecTransferType
inspSpecTransferType
- Copy Model/Reference Characteristicpublic void setInspSpecCreatedByUser(@Nullable String inspSpecCreatedByUser)
Original property name from the Odata EDM: InspSpecCreatedByUser
The system automatically enters the user name.
inspSpecCreatedByUser
- Name of the user who created this data record.public void setInspSpecCreationDate(@Nullable LocalDateTime inspSpecCreationDate)
Original property name from the Odata EDM: InspSpecCreationDate
The system enters the current system date.
inspSpecCreationDate
- Date on which the data record was created.public void setInspSpecChangedByUser(@Nullable String inspSpecChangedByUser)
Original property name from the Odata EDM: InspSpecChangedByUser
inspSpecChangedByUser
- Name of the user who made the last change to this data record.public void setInspSpecChangeDate(@Nullable LocalDateTime inspSpecChangeDate)
Original property name from the Odata EDM: InspSpecChangeDate
The system enters the current system date.
inspSpecChangeDate
- Date on which the data record was last changed.public void setInspSpecIsQuantitative(@Nullable Boolean inspSpecIsQuantitative)
Original property name from the Odata EDM: InspSpecIsQuantitative
inspSpecIsQuantitative
- Is Quantitative Characteristicpublic void setInspSpecCharacteristicType(@Nullable String inspSpecCharacteristicType)
Original property name from the Odata EDM: InspSpecCharacteristicType
inspSpecCharacteristicType
- Characteristic Type (Quantitative/Qualitative)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
- Determines whether and how inspection results are to be documented with additional text when they are
recorded.public void setInspSpecCharcCategory(@Nullable String inspSpecCharcCategory)
Original property name from the Odata EDM: InspSpecCharcCategory
You can make the following entries:Optional characteristicThis characteristic can be inspected, if necessary. You do not have to record results for this characteristic.Conditional characteristic (when the previous characteristic has been accepted)This characteristic must be inspected if the previous required characteristic was accepted.Conditional characteristic (when the previous characteristic has been rejected)This characteristic must be inspected when the previous required characteristic was rejected.Required characteristicThis characteristic must be inspected.
inspSpecCharcCategory
- In this field you determine if and when a characteristic is inspected.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 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
You set this indicator if the inspection result for an inspection characteristic is not determined through the inspection of this characteristic, but on the basis of calculations using the inspection results of other characteristics within the same operation.The SAP system supports the following functions:ABS Absolute amountNOT NegationSIN Sine functionCOS Cosine functionTAN Tangent functionLOG Logarithm for base value e (Natural logarithm)EXP Exponential function for base value eSQRT Square root functionROUND Rounding up to the whole numberTRUNC Proportion of whole numbers for a real numberMOD Modulo methodDIV Proportion of whole numbers for a divisionThe operating factors supported by the SAP system are divided into 6 levels based on their order of precedence. The operating factors in level 0 form the weakest combinations; those in level 6 the strongest. The following operating factors are available for calculation:Level 0AND Logical ANDOR Logical ORLevel 1= Equality<>, >< Inequality< Less than> Greater than<=, =< Less than or equal toLevel 2+ Positive sign (of an expression)- Negative sign (of an expression)+ Addition- SubtractionLevel 3* Multiplication/ DivisionLevel 4** ExponentiationLevel 5ABS Absolute amountNOT Negation (of a logical statement)Level 6All other functionsUser-defined formulasThe SAP system also evaluates user-defined functions that are defined in a table.
inspSpecResultCalculation
- The indicator defines the characteristic as a calculated characteristic.public 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 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 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
- Printpublic 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 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 setQltyMstrDataAuthorizationGroup(@Nullable String qltyMstrDataAuthorizationGroup)
Original property name from the Odata EDM: QltyMstrDataAuthorizationGroup
Objects and activities that are affected:Master inspection characteristic, inspection method:Creating with an authorization groupCreating a validity period with an authorization groupChangingDisplayingDeletingChanging authorization groupIncluding inspection method in master inspection characteristic or task listIncluding master inspection characteristic in task list, certificate profile, or material specificationChanging an unplanned characteristic in results recordingSample-drawing procedure:EditingEditing authorization groupIf you enter an authorization group for master data records, the system checks whether the user has access to the objects named above.If no authorization group is entered in the master record, no authorization check takes place.To pass the authorization check, the user must have authorization for master data, which contains the relevant authorization group as a field value.
qltyMstrDataAuthorizationGroup
- The basic data authorization group restricts user access to the Quality Management basic data.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 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 setInspSpecLowerPlausibilityLimit(@Nullable Double inspSpecLowerPlausibilityLimit)
Original property name from the Odata EDM: InspSpecLowerPlausibilityLimit
This field is used only for results recording of quantitative characteristics. It protects against the recording and processing of invalid or improbable values. If the actual value of the variable lies outside the plausibility limit defined by the limiting value entered in this field, the system may issue a warning message or block further processing.
inspSpecLowerPlausibilityLimit
- Minimum plausible value of a plausibility limit.public void setInspSpecHasLowrPlausibilityLmt(@Nullable String inspSpecHasLowrPlausibilityLmt)
Original property name from the Odata EDM: InspSpecHasLowrPlausibilityLmt
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasLowrPlausibilityLmt
- 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 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 setInspSpecLowerSpecLimitChange(@Nullable Double inspSpecLowerSpecLimitChange)
Original property name from the Odata EDM: InspSpecLowerSpecLimitChange
You can increase or reduce the tolerance range for a specific time period. You can make these short-term changes to the tolerance range without having to change the original specification limits.If you enter a POSITIVE value, the lower limiting value is changed to a SMALLER value.If you enter a NEGATIVE value, the lower limiting value is changed to a LARGER value.If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
inspSpecLowerSpecLimitChange
- Amount by which the specification limit is temporarily increased or decreased.public void setInspSpecHasLowrSpecLimitChange(@Nullable String inspSpecHasLowrSpecLimitChange)
Original property name from the Odata EDM: InspSpecHasLowrSpecLimitChange
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasLowrSpecLimitChange
- 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 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 setInspSpecUpperPlausibilityLimit(@Nullable Double inspSpecUpperPlausibilityLimit)
Original property name from the Odata EDM: InspSpecUpperPlausibilityLimit
This field is used only for results recording of quantitative characteristics. It protects against the recording and processing of invalid or improbable values. If the actual value of the variable lies outside the plausibility limit defined by the limiting value entered in this field, the system may issue a warning message or block further processing.
inspSpecUpperPlausibilityLimit
- Maximum plausible value of a plausibility limit.public void setInspSpecHasUprPlausibilityLmt(@Nullable String inspSpecHasUprPlausibilityLmt)
Original property name from the Odata EDM: InspSpecHasUprPlausibilityLmt
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasUprPlausibilityLmt
- 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 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 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 setInspSpecUpperSpecLimitChange(@Nullable Double inspSpecUpperSpecLimitChange)
Original property name from the Odata EDM: InspSpecUpperSpecLimitChange
You can increase or reduce the tolerance range for a specific time period. You can make these short-term changes to the tolerance range without having to change the original specification limits.If you enter a POSITIVE value, the upper specification limit is changed to a LARGER value.If you enter a NEGATIVE value, the upper specification limit is changed to a SMALLER value.If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
inspSpecUpperSpecLimitChange
- Amount by which the specification limit is temporarily increased or decreased.public void setInspSpecHasUprSpecLimitChange(@Nullable String inspSpecHasUprSpecLimitChange)
Original property name from the Odata EDM: InspSpecHasUprSpecLimitChange
If this indicator is set, then the value of the corresponding numeric field is not initial.
inspSpecHasUprSpecLimitChange
- 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 setInspSpecToleranceChgValidFrom(@Nullable LocalDateTime inspSpecToleranceChgValidFrom)
Original property name from the Odata EDM: InspSpecToleranceChgValidFrom
If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
inspSpecToleranceChgValidFrom
- You can temporarily change the tolerance range. To specify the time period for which the change is
valid, enter the date from which the tolerance change is to be active.public void setInspSpecToleranceChgValidTo(@Nullable LocalDateTime inspSpecToleranceChgValidTo)
Original property name from the Odata EDM: InspSpecToleranceChgValidTo
If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
inspSpecToleranceChgValidTo
- You can temporarily change the tolerance range. To specify the time period for the tolerance change,
enter the date, up to and including which the tolerance change is to be active.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 setCharacteristicInternalID(@Nullable String characteristicInternalID)
Original property name from the Odata EDM: CharacteristicInternalID
characteristicInternalID
- Internal characteristicpublic void setDefectFractionEstimationProced(@Nullable String defectFractionEstimationProced)
Original property name from the Odata EDM: DefectFractionEstimationProced
defectFractionEstimationProced
- Fraction Calculationprotected String getEntityCollection()
getEntityCollection
in class VdmEntity<InspectionSpecification>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<InspectionSpecification>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<InspectionSpecification>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<InspectionSpecification>
@Nonnull public static <T> InspectionSpecificationField<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> InspectionSpecificationField<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()
VdmEntity
getDestinationForFetch
in class VdmEntity<InspectionSpecification>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<InspectionSpecification>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<InspectionSpecification>
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()
getDefaultServicePath
in class VdmEntity<InspectionSpecification>
public static InspectionSpecification.InspectionSpecificationBuilder builder()
@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 getPlant()
Original property name from the Odata EDM: Plant
@Nullable public LocalDateTime getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public String getInspectionSpecificationSrchTxt()
Original property name from the Odata EDM: InspectionSpecificationSrchTxt
Enter a meaningful word or phrase in this language-independent field. The entry you make should be easy to remember and should identify the master data record uniquely.
@Nullable public String getInspSpecGlobalName()
Original property name from the Odata EDM: InspSpecGlobalName
In this field, you can define an additional characteristic description (40 characters long) in the inspection plan, material specification, master inspection characteristic, and certificate profile. This description acts as the characteristic identification for the electronic exchange of characteristic values.
@Nullable public String getInspectionSpecificationStatus()
Original property name from the Odata EDM: InspectionSpecificationStatus
@Nullable public String getInspSpecTransferType()
Original property name from the Odata EDM: InspSpecTransferType
@Nullable public String getInspSpecCreatedByUser()
Original property name from the Odata EDM: InspSpecCreatedByUser
The system automatically enters the user name.
@Nullable public LocalDateTime getInspSpecCreationDate()
Original property name from the Odata EDM: InspSpecCreationDate
The system enters the current system date.
@Nullable public String getInspSpecChangedByUser()
Original property name from the Odata EDM: InspSpecChangedByUser
@Nullable public LocalDateTime getInspSpecChangeDate()
Original property name from the Odata EDM: InspSpecChangeDate
The system enters the current system date.
@Nullable public Boolean getInspSpecIsQuantitative()
Original property name from the Odata EDM: InspSpecIsQuantitative
@Nullable public String getInspSpecCharacteristicType()
Original property name from the Odata EDM: InspSpecCharacteristicType
@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
You can make the following entries:Optional characteristicThis characteristic can be inspected, if necessary. You do not have to record results for this characteristic.Conditional characteristic (when the previous characteristic has been accepted)This characteristic must be inspected if the previous required characteristic was accepted.Conditional characteristic (when the previous characteristic has been rejected)This characteristic must be inspected when the previous required characteristic was rejected.Required characteristicThis characteristic must be inspected.
@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 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
You set this indicator if the inspection result for an inspection characteristic is not determined through the inspection of this characteristic, but on the basis of calculations using the inspection results of other characteristics within the same operation.The SAP system supports the following functions:ABS Absolute amountNOT NegationSIN Sine functionCOS Cosine functionTAN Tangent functionLOG Logarithm for base value e (Natural logarithm)EXP Exponential function for base value eSQRT Square root functionROUND Rounding up to the whole numberTRUNC Proportion of whole numbers for a real numberMOD Modulo methodDIV Proportion of whole numbers for a divisionThe operating factors supported by the SAP system are divided into 6 levels based on their order of precedence. The operating factors in level 0 form the weakest combinations; those in level 6 the strongest. The following operating factors are available for calculation:Level 0AND Logical ANDOR Logical ORLevel 1= Equality<>, >< Inequality< Less than> Greater than<=, =< Less than or equal toLevel 2+ Positive sign (of an expression)- Negative sign (of an expression)+ Addition- SubtractionLevel 3* Multiplication/ DivisionLevel 4** ExponentiationLevel 5ABS Absolute amountNOT Negation (of a logical statement)Level 6All other functionsUser-defined formulasThe SAP system also evaluates user-defined functions that are defined in a table.
@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 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 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 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 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 getQltyMstrDataAuthorizationGroup()
Original property name from the Odata EDM: QltyMstrDataAuthorizationGroup
Objects and activities that are affected:Master inspection characteristic, inspection method:Creating with an authorization groupCreating a validity period with an authorization groupChangingDisplayingDeletingChanging authorization groupIncluding inspection method in master inspection characteristic or task listIncluding master inspection characteristic in task list, certificate profile, or material specificationChanging an unplanned characteristic in results recordingSample-drawing procedure:EditingEditing authorization groupIf you enter an authorization group for master data records, the system checks whether the user has access to the objects named above.If no authorization group is entered in the master record, no authorization check takes place.To pass the authorization check, the user must have authorization for master data, which contains the relevant authorization group as a field value.
@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 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 Double getInspSpecLowerPlausibilityLimit()
Original property name from the Odata EDM: InspSpecLowerPlausibilityLimit
This field is used only for results recording of quantitative characteristics. It protects against the recording and processing of invalid or improbable values. If the actual value of the variable lies outside the plausibility limit defined by the limiting value entered in this field, the system may issue a warning message or block further processing.
@Nullable public String getInspSpecHasLowrPlausibilityLmt()
Original property name from the Odata EDM: InspSpecHasLowrPlausibilityLmt
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 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 Double getInspSpecLowerSpecLimitChange()
Original property name from the Odata EDM: InspSpecLowerSpecLimitChange
You can increase or reduce the tolerance range for a specific time period. You can make these short-term changes to the tolerance range without having to change the original specification limits.If you enter a POSITIVE value, the lower limiting value is changed to a SMALLER value.If you enter a NEGATIVE value, the lower limiting value is changed to a LARGER value.If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
@Nullable public String getInspSpecHasLowrSpecLimitChange()
Original property name from the Odata EDM: InspSpecHasLowrSpecLimitChange
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 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 Double getInspSpecUpperPlausibilityLimit()
Original property name from the Odata EDM: InspSpecUpperPlausibilityLimit
This field is used only for results recording of quantitative characteristics. It protects against the recording and processing of invalid or improbable values. If the actual value of the variable lies outside the plausibility limit defined by the limiting value entered in this field, the system may issue a warning message or block further processing.
@Nullable public String getInspSpecHasUprPlausibilityLmt()
Original property name from the Odata EDM: InspSpecHasUprPlausibilityLmt
If this indicator is set, then the value of the corresponding numeric field is not initial.
@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 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 getInspSpecUpperSpecLimitChange()
Original property name from the Odata EDM: InspSpecUpperSpecLimitChange
You can increase or reduce the tolerance range for a specific time period. You can make these short-term changes to the tolerance range without having to change the original specification limits.If you enter a POSITIVE value, the upper specification limit is changed to a LARGER value.If you enter a NEGATIVE value, the upper specification limit is changed to a SMALLER value.If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
@Nullable public String getInspSpecHasUprSpecLimitChange()
Original property name from the Odata EDM: InspSpecHasUprSpecLimitChange
If this indicator is set, then the value of the corresponding numeric field is not initial.
@Nullable public LocalDateTime getInspSpecToleranceChgValidFrom()
Original property name from the Odata EDM: InspSpecToleranceChgValidFrom
If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
@Nullable public LocalDateTime getInspSpecToleranceChgValidTo()
Original property name from the Odata EDM: InspSpecToleranceChgValidTo
If you have altered the tolerance range by changing either the upper or the lower specification limit, you must also define the time period for which the change is valid. This means you must enter both a start date as well as an end date for the time period.
@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 getCharacteristicInternalID()
Original property name from the Odata EDM: CharacteristicInternalID
@Nullable public String getDefectFractionEstimationProced()
Original property name from the Odata EDM: DefectFractionEstimationProced
public String toString()
toString
in class VdmObject<InspectionSpecification>
public boolean equals(Object o)
equals
in class VdmObject<InspectionSpecification>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<InspectionSpecification>
public int hashCode()
hashCode
in class VdmObject<InspectionSpecification>
Copyright © 2019 SAP SE. All rights reserved.