public static class InspectionSpecification.InspectionSpecificationBuilder extends Object
public InspectionSpecification.InspectionSpecificationBuilder inspectionSpecification(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspectionSpecificationVersion(@Nullable String inspectionSpecificationVersion)
Original property name from the Odata EDM: InspectionSpecificationVersion
this.public InspectionSpecification.InspectionSpecificationBuilder inspectionSpecificationPlant(@Nullable String inspectionSpecificationPlant)
Original property name from the Odata EDM: InspectionSpecificationPlant
this.public InspectionSpecification.InspectionSpecificationBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.public InspectionSpecification.InspectionSpecificationBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
this.public InspectionSpecification.InspectionSpecificationBuilder inspectionSpecificationSrchTxt(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecGlobalName(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspectionSpecificationStatus(@Nullable String inspectionSpecificationStatus)
Original property name from the Odata EDM: InspectionSpecificationStatus
deletion.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecTransferType(@Nullable String inspSpecTransferType)
Original property name from the Odata EDM: InspSpecTransferType
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecCreatedByUser(@Nullable String inspSpecCreatedByUser)
Original property name from the Odata EDM: InspSpecCreatedByUser
The system automatically enters the user name.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecCreationDate(@Nullable LocalDateTime inspSpecCreationDate)
Original property name from the Odata EDM: InspSpecCreationDate
The system enters the current system date.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecChangedByUser(@Nullable String inspSpecChangedByUser)
Original property name from the Odata EDM: InspSpecChangedByUser
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecChangeDate(@Nullable LocalDateTime inspSpecChangeDate)
Original property name from the Odata EDM: InspSpecChangeDate
The system enters the current system date.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsQuantitative(@Nullable Boolean inspSpecIsQuantitative)
Original property name from the Odata EDM: InspSpecIsQuantitative
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecCharacteristicType(@Nullable String inspSpecCharacteristicType)
Original property name from the Odata EDM: InspSpecCharacteristicType
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsMeasuredValueRqd(@Nullable String inspSpecIsMeasuredValueRqd)
Original property name from the Odata EDM: InspSpecIsMeasuredValueRqd
confirmed.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsSelectedSetRequired(@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".
whose allowed values are defined as a selected set from catalog 1 (characteristic attributes).this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsUpperLimitRequired(@Nullable String inspSpecIsUpperLimitRequired)
Original property name from the Odata EDM: InspSpecIsUpperLimitRequired
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsLowerLimitRequired(@Nullable String inspSpecIsLowerLimitRequired)
Original property name from the Odata EDM: InspSpecIsLowerLimitRequired
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsTargetValueInLimit(@Nullable String inspSpecIsTargetValueInLimit)
Original property name from the Odata EDM: InspSpecIsTargetValueInLimit
indicator, the system checks whether the target value lies within the tolerance.this.public InspectionSpecification.InspectionSpecificationBuilder inspectionScope(@Nullable String inspectionScope)
Original property name from the Odata EDM: InspectionScope
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsLongTermInspection(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecRecordingType(@Nullable String inspSpecRecordingType)
Original property name from the Odata EDM: InspSpecRecordingType
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).this.public InspectionSpecification.InspectionSpecificationBuilder inspResultIsDocumentationRqd(@Nullable String inspResultIsDocumentationRqd)
Original property name from the Odata EDM: InspResultIsDocumentationRqd
recorded.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecCharcCategory(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsDefectsRecgAutomatic(@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.
function for recording defects for a characteristic is automatically called up. In this situation, a distinction must be made between the following cases:this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsSampleQtyAdditive(@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.
required for this characteristic in inspection sample calculation.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsDestructive(@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.
inspect the characteristics.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecResultCalculation(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsSamplingProcedRqd(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsScrapRelevant(@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.
taken into account when the share of scrap is calculated in the inspection lot.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsTestEquipmentRqd(@Nullable String inspSpecIsTestEquipmentRqd)
Original property name from the Odata EDM: InspSpecIsTestEquipmentRqd
If you do not make an assignment, the system displays a warning message.
list.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsChgDocRequired(@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.
are recorded based on characteristics.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecIsControlChartUsed(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecPrintControl(@Nullable String inspSpecPrintControl)
Original property name from the Odata EDM: InspSpecPrintControl
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecImportanceCode(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspectorQualification(@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.
inspection.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecInformationField1(@Nullable String inspSpecInformationField1)
Original property name from the Odata EDM: InspSpecInformationField1
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.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecInformationField2(@Nullable String inspSpecInformationField2)
Original property name from the Odata EDM: InspSpecInformationField2
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.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecInformationField3(@Nullable String inspSpecInformationField3)
Original property name from the Odata EDM: InspSpecInformationField3
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.this.public InspectionSpecification.InspectionSpecificationBuilder qltyMstrDataAuthorizationGroup(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspToleranceSpecification(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDecimalPlaces(@Nullable Short inspSpecDecimalPlaces)
Original property name from the Odata EDM: InspSpecDecimalPlaces
this.public InspectionSpecification.InspectionSpecificationBuilder inspectionSpecificationUnit(@Nullable String inspectionSpecificationUnit)
Original property name from the Odata EDM: InspectionSpecificationUnit
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.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecTargetValue(@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.
should deviate as little as possible.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasTargetValue(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecLowerLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasLowerLimit(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecLowerPlausibilityLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasLowrPlausibilityLmt(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecFirstLowerSpecLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasFirstLowerSpecLimit(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecSecondLowerSpecLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasSecondLowrSpecLimit(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecLowerSpecLimitChange(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasLowrSpecLimitChange(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecUpperLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasUpperLimit(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecUpperPlausibilityLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasUprPlausibilityLmt(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecFirstUpperSpecLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasFirstUpperSpecLimit(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecSecondUpperSpecLimit(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasSecondUprSpecLimit(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecUpperSpecLimitChange(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecHasUprSpecLimitChange(@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.
in order to differentiate between null and the initial value.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecToleranceChgValidFrom(@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.
enter the date from which the tolerance change is to be active.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecToleranceChgValidTo(@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.
enter the date, up to and including which the tolerance change is to be active.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDefectCodeGrpRejection(@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.
this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDefectCodeRejection(@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.
characteristic.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDefectCodeGrpRjcnUpper(@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.
characteristic with an upper specification limit.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDefectCodeRjcnUpper(@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.
characteristic with an upper specification limit.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDefectCodeGrpRjcnLower(@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.
with a lower specification limit.this.public InspectionSpecification.InspectionSpecificationBuilder inspSpecDefectCodeRjcnLower(@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.
characteristic with a lower specification limit.this.public InspectionSpecification.InspectionSpecificationBuilder characteristicInternalID(@Nullable String characteristicInternalID)
Original property name from the Odata EDM: CharacteristicInternalID
this.public InspectionSpecification.InspectionSpecificationBuilder defectFractionEstimationProced(@Nullable String defectFractionEstimationProced)
Original property name from the Odata EDM: DefectFractionEstimationProced
this.public InspectionSpecification build()
Copyright © 2020 SAP SE. All rights reserved.