public static class InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder extends Object
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionPlanGroup(@Nullable String inspectionPlanGroup)
Original property name from the Odata EDM: InspectionPlanGroup
You can use groups, for instance, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOOperationInternalID(@Nullable String bOOOperationInternalID)
Original property name from the Odata EDM: BOOOperationInternalID
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOCharacteristic(@Nullable String bOOCharacteristic)
Original property name from the Odata EDM: BOOCharacteristic
plan.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOCharacteristicVersion(@Nullable String bOOCharacteristicVersion)
Original property name from the Odata EDM: BOOCharacteristicVersion
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOOpInternalVersionCounter(@Nullable String bOOOpInternalVersionCounter)
Original property name from the Odata EDM: BOOOpInternalVersionCounter
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionPlanInternalVersion(@Nullable String inspectionPlanInternalVersion)
Original property name from the Odata EDM: InspectionPlanInternalVersion
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionPlan(@Nullable String inspectionPlan)
Original property name from the Odata EDM: InspectionPlan
In Production Planning and Control, for example, it serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.The group counter can be used to identify different lot-size ranges, for example.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder validityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder changeNumber(@Nullable String changeNumber)
Original property name from the Odata EDM: ChangeNumber
If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder isDeleted(@Nullable Boolean isDeleted)
Original property name from the Odata EDM: IsDeleted
This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
number.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOOperationPRTInternalID(@Nullable String bOOOperationPRTInternalID)
Original property name from the Odata EDM: BOOOperationPRTInternalID
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionMethod(@Nullable String inspectionMethod)
Original property name from the Odata EDM: InspectionMethod
An inspection method describes how to inspect an inspection characteristic. You can assign an inspection method to a master inspection characteristic or directly to an inspection characteristic in an inspection plan.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionMethodVersion(@Nullable String inspectionMethodVersion)
Original property name from the Odata EDM: InspectionMethodVersion
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionMethodPlant(@Nullable String inspectionMethodPlant)
Original property name from the Odata EDM: InspectionMethodPlant
For inspection methods this plant is the planning plant, in which the inspection method was created in QM.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionSpecificationVersion(@Nullable String inspectionSpecificationVersion)
Original property name from the Odata EDM: InspectionSpecificationVersion
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionSpecificationPlant(@Nullable String inspectionSpecificationPlant)
Original property name from the Odata EDM: InspectionSpecificationPlant
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOCharcHasInspSpecReference(@Nullable Boolean bOOCharcHasInspSpecReference)
Original property name from the Odata EDM: BOOCharcHasInspSpecReference
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecControlIndicators(@Nullable String inspSpecControlIndicators)
Original property name from the Odata EDM: InspSpecControlIndicators
plan default valuesresults recordinginspection processing
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecIsQuantitative(@Nullable String inspSpecIsQuantitative)
Original property name from the Odata EDM: InspSpecIsQuantitative
Set the indicator for the characteristic type (quantitative or qualitative) or enter a control key.If you used a control key, for which the "fixed" indicator is set in Customizing, you cannot change the indicator for the characteristic type. In addition, you cannot delete this indicator or enter another control key.
You thereby define the control indicators that are relevant for the inspection characteristic. A quantitative characteristic is subject to measurement inspections. You can define tolerance limits and a target value for a quantitative characteristic.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecIsMeasuredValueRqd(@Nullable String inspSpecIsMeasuredValueRqd)
Original property name from the Odata EDM: InspSpecIsMeasuredValueRqd
confirmed.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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).public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecIsUpperLimitRequired(@Nullable String inspSpecIsUpperLimitRequired)
Original property name from the Odata EDM: InspSpecIsUpperLimitRequired
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecIsLowerLimitRequired(@Nullable String inspSpecIsLowerLimitRequired)
Original property name from the Odata EDM: InspSpecIsLowerLimitRequired
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecIsTargetValueInLimit(@Nullable String inspSpecIsTargetValueInLimit)
Original property name from the Odata EDM: InspSpecIsTargetValueInLimit
indicator, the system checks whether the target value lies within the tolerance.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionScope(@Nullable String inspectionScope)
Original property name from the Odata EDM: InspectionScope
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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).public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspResultIsDocumentationRqd(@Nullable String inspResultIsDocumentationRqd)
Original property name from the Odata EDM: InspResultIsDocumentationRqd
recorded.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecHasFixedCtrlIndicators(@Nullable String inspSpecHasFixedCtrlIndicators)
Original property name from the Odata EDM: InspSpecHasFixedCtrlIndicators
characteristic using a control key cannot be changed.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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:public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecPrintControl(@Nullable String inspSpecPrintControl)
Original property name from the Odata EDM: InspSpecPrintControl
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecDecimalPlaces(@Nullable Short inspSpecDecimalPlaces)
Original property name from the Odata EDM: InspSpecDecimalPlaces
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder selectedCodeSet(@Nullable String selectedCodeSet)
Original property name from the Odata EDM: SelectedCodeSet
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder selectedCodeSetPlant(@Nullable String selectedCodeSetPlant)
Original property name from the Odata EDM: SelectedCodeSetPlant
Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCatalog2(@Nullable String inspSpecAdditionalCatalog2)
Original property name from the Odata EDM: InspSpecAdditionalCatalog2
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
characteristic attributes, defect types, usage decisions).public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalSelectedSet2(@Nullable String inspSpecAdditionalSelectedSet2)
Original property name from the Odata EDM: InspSpecAdditionalSelectedSet2
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCodeGroup2(@Nullable String inspSpecAdditionalCodeGroup2)
Original property name from the Odata EDM: InspSpecAdditionalCodeGroup2
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAddlSeldCodeSetPlant2(@Nullable String inspSpecAddlSeldCodeSetPlant2)
Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant2
Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCatalog3(@Nullable String inspSpecAdditionalCatalog3)
Original property name from the Odata EDM: InspSpecAdditionalCatalog3
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
characteristic attributes, defect types, usage decisions).public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalSelectedSet3(@Nullable String inspSpecAdditionalSelectedSet3)
Original property name from the Odata EDM: InspSpecAdditionalSelectedSet3
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCodeGroup3(@Nullable String inspSpecAdditionalCodeGroup3)
Original property name from the Odata EDM: InspSpecAdditionalCodeGroup3
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAddlSeldCodeSetPlant3(@Nullable String inspSpecAddlSeldCodeSetPlant3)
Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant3
Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCatalog4(@Nullable String inspSpecAdditionalCatalog4)
Original property name from the Odata EDM: InspSpecAdditionalCatalog4
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
characteristic attributes, defect types, usage decisions).public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalSelectedSet4(@Nullable String inspSpecAdditionalSelectedSet4)
Original property name from the Odata EDM: InspSpecAdditionalSelectedSet4
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCodeGroup4(@Nullable String inspSpecAdditionalCodeGroup4)
Original property name from the Odata EDM: InspSpecAdditionalCodeGroup4
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAddlSeldCodeSetPlant4(@Nullable String inspSpecAddlSeldCodeSetPlant4)
Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant4
Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCatalog5(@Nullable String inspSpecAdditionalCatalog5)
Original property name from the Odata EDM: InspSpecAdditionalCatalog5
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.NOTEYou CANNOT assign selected sets from catalog type 1 to quantitative characteristics or to qualitative characteristics for which the characteristic attributes indicator is not set.
characteristic attributes, defect types, usage decisions).public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalSelectedSet5(@Nullable String inspSpecAdditionalSelectedSet5)
Original property name from the Odata EDM: InspSpecAdditionalSelectedSet5
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAdditionalCodeGroup5(@Nullable String inspSpecAdditionalCodeGroup5)
Original property name from the Odata EDM: InspSpecAdditionalCodeGroup5
If you are processing a quantitative characteristic or a qualitative characteristic for which the characteristic attributes indicator is not set, you can assign up to 4 code groups or selected sets to describe the inspection characteristic or the inspection method.Catalog types 2,3,4,5 are also used in defects recording:If you record defects with reference to an inspection characteristic, you can limit the allowed catalog confirmations by predefining code groups or selected sets.
indicator is set, you can assign up to 5 code groups or selected sets to describe the inspection characteristic or the inspection method.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspSpecAddlSeldCodeSetPlant5(@Nullable String inspSpecAddlSeldCodeSetPlant5)
Original property name from the Odata EDM: InspSpecAddlSeldCodeSetPlant5
Selected sets are defined at the plant level.Therefore you must enter a plant for each selected set that you assign to a master record.If you select a selected set from a list of catalog entries, the system automatically copies the selected set and the plant.Do not enter a plant for a code group that you have assigned to a master record.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder samplingProcedure(@Nullable String samplingProcedure)
Original property name from the Odata EDM: SamplingProcedure
In the sampling procedure, the valuation mode is also defined for the inspection result.A sampling procedure is assigned to an inspection characteristic in a task list or material specification. In addition, you can assign the procedure to an unplanned characteristic, when you record results.If you do not enter a sampling procedure for an inspection characteristic, the system chooses a sampling procedure proposed in the settings at plant level. If no sampling procedure was entered in these settings, the system takes the lot size as the sample size.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspCharacteristicSampleUnit(@Nullable String inspCharacteristicSampleUnit)
Original property name from the Odata EDM: InspCharacteristicSampleUnit
The unit in which a sample is measured.To permit this unit of measure to be converted into the material unit of measure when the system selects the inspection specifications for an inspection lot, you must have maintained the conversion factors in the material master record100 ml are needed to inspect a characteristic. In this case, the sample unit of measure is ml.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder bOOCharcSampleQuantity(@Nullable BigDecimal bOOCharcSampleQuantity)
Original property name from the Odata EDM: BOOCharcSampleQuantity
The sample unit is the product of the following factors: Base sample quantity and the sample unit of measure.To inspect a characteristic, 100 ml are needed. In this case:Sample unit of measure = mlBase sample quantity = 100Sample unit = 100mlIf the sampling procedure that is defined for the characteristic stipulates that 5 individual samples are needed, the sample unit is multiplied by five. As a result, 5 x 100 ml must be drawn to inspect this characteristic.Sample quantity = 500 ml
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder 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.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder inspectionSpecificationText(@Nullable String inspectionSpecificationText)
Original property name from the Odata EDM: InspectionSpecificationText
short text.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
The system enters the current system date.
public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder billOfOperationsVersion(@Nullable String billOfOperationsVersion)
Original property name from the Odata EDM: BillOfOperationsVersion
changes to a new routing version until it is released. Released routing versions can be used in production execution and cannot be changed. If you want to make changes to a routing version, you can create a new routing version and then you can make the necessary changes.public InspPlanOpCharacteristic.InspPlanOpCharacteristicBuilder changedDateTime(@Nullable ZonedDateTime changedDateTime)
Original property name from the Odata EDM: ChangedDateTime
To standardize local times in a UTC time stamp and thus make them comparable with other times, these local times
need to be converted using your time zone and the ABAP command convert.Even if the system is able to determine
the time zone from Customizing or master data, you shoul save the time zone redundantly here.The internal
structure of the UTC time stamp is subdivided into a date part and a time part in packed number format
public InspPlanOpCharacteristic build()
Copyright © 2019 SAP SE. All rights reserved.