InspectionSubset.InspectionSubsetBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.qualityinspectiondata.InspectionSubset.InspectionSubsetBuilder

Enclosing class:: InspectionSubset

public static class InspectionSubset.InspectionSubsetBuilder
extends Object

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`InspectionSubset`	`build()`
`InspectionSubset.InspectionSubsetBuilder`	`changedDateTime(ZonedDateTime changedDateTime)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`createdByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`InspectionSubset.InspectionSubsetBuilder`	`creationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`creationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`equipment(String equipment)` Constraints: Not nullable, Maximum length: 18
`InspectionSubset.InspectionSubsetBuilder`	`functionalLocation(String functionalLocation)` Constraints: Not nullable, Maximum length: 40
`InspectionSubset.InspectionSubsetBuilder`	`inspectionLot(String inspectionLot)` (Key Field) Constraints: Not nullable, Maximum length: 12
`InspectionSubset.InspectionSubsetBuilder`	`inspectionPartialLot(String inspectionPartialLot)` Constraints: Not nullable, Maximum length: 6
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetDate(LocalDateTime inspectionSubsetDate)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetInternalID(String inspectionSubsetInternalID)` (Key Field) Constraints: Not nullable, Maximum length: 6
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetLongCharKey(String inspectionSubsetLongCharKey)` Constraints: Not nullable, Maximum length: 18
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetQtyUnit(String inspectionSubsetQtyUnit)` Constraints: Not nullable, Maximum length: 3
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetReworkQty(BigDecimal inspectionSubsetReworkQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetScrapQty(BigDecimal inspectionSubsetScrapQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetShortCharKey(String inspectionSubsetShortCharKey)` Constraints: Not nullable, Maximum length: 10
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetSortKey(String inspectionSubsetSortKey)` Constraints: Not nullable, Maximum length: 70
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetTime(LocalTime inspectionSubsetTime)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`inspectionSubsetYieldQty(BigDecimal inspectionSubsetYieldQty)` Constraints: Not nullable, Precision: 13, Scale: 3
`InspectionSubset.InspectionSubsetBuilder`	`inspector(String inspector)` Constraints: Not nullable, Maximum length: 12
`InspectionSubset.InspectionSubsetBuilder`	`inspPlanOperationInternalID(String inspPlanOperationInternalID)` (Key Field) Constraints: Not nullable, Maximum length: 8
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstDateFldProperty(String inspSbstDateFldProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstEquipProperty(String inspSbstEquipProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstFuncnlLocProperty(String inspSbstFuncnlLocProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstLongNmbrFldProperty(String inspSbstLongNmbrFldProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstLongTxtFldProperty(String inspSbstLongTxtFldProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstMatlSmplProperty(String inspSbstMatlSmplProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstShrtNmbrFldProperty(String inspSbstShrtNmbrFldProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstShrtTxtFldProperty(String inspSbstShrtTxtFldProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSbstTimeFldProperty(String inspSbstTimeFldProperty)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`inspSubsetLongNumericKey(String inspSubsetLongNumericKey)` Constraints: Not nullable, Maximum length: 10
`InspectionSubset.InspectionSubsetBuilder`	`inspSubsetShortNumericKey(String inspSubsetShortNumericKey)` Constraints: Not nullable, Maximum length: 3
`InspectionSubset.InspectionSubsetBuilder`	`inspSubsetUsageDcsnCode(String inspSubsetUsageDcsnCode)` Constraints: Not nullable, Maximum length: 4
`InspectionSubset.InspectionSubsetBuilder`	`inspSubsetUsageDcsnCodeGroup(String inspSubsetUsageDcsnCodeGroup)` Constraints: Not nullable, Maximum length: 8
`InspectionSubset.InspectionSubsetBuilder`	`inspSubsetUsageDcsnValuation(String inspSubsetUsageDcsnValuation)` Constraints: Not nullable, Maximum length: 1
`InspectionSubset.InspectionSubsetBuilder`	`lastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`lastChangedByUser(String lastChangedByUser)` Constraints: Not nullable, Maximum length: 12
`InspectionSubset.InspectionSubsetBuilder`	`lastChangeTime(LocalTime lastChangeTime)` Constraints: Not nullable, Precision: 0
`InspectionSubset.InspectionSubsetBuilder`	`materialSample(String materialSample)` Constraints: Not nullable, Maximum length: 12
`InspectionSubset.InspectionSubsetBuilder`	`selectedCodeSet(String selectedCodeSet)` Constraints: Not nullable, Maximum length: 8
`InspectionSubset.InspectionSubsetBuilder`	`selectedCodeSetPlant(String selectedCodeSetPlant)` Constraints: Not nullable, Maximum length: 4
`InspectionSubset.InspectionSubsetBuilder`	`shopFloorItem(Long shopFloorItem)` Constraints: none
`String`	`toString()`
`InspectionSubset.InspectionSubsetBuilder`	`trigger_valuation_ac(Boolean trigger_valuation_ac)` Constraints: none

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

- Method Detail
  - trigger_valuation_ac
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder trigger_valuation_ac(@Nullable
                                                                              Boolean trigger_valuation_ac)
```
    Constraints: none
    Original property name from the Odata EDM: Trigger_valuation_ac
    
    Returns:
    
    this.
  - inspectionLot
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionLot(@Nullable
                                                                       String inspectionLot)
```
    (Key Field) Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: InspectionLot
    
    The inspection lot number is assigned by the system.
    
    Returns:
    
    this.
  - inspPlanOperationInternalID
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspPlanOperationInternalID(@Nullable
                                                                                     String inspPlanOperationInternalID)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspPlanOperationInternalID
    
    Returns:
    
    this.
  - inspectionSubsetInternalID
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetInternalID(@Nullable
                                                                                    String inspectionSubsetInternalID)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionSubsetInternalID
    via this number.
    
    Returns:
    
    this.
  - materialSample
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder materialSample(@Nullable
                                                                        String materialSample)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: MaterialSample
    
    Returns:
    
    this.
  - equipment
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder equipment(@Nullable
                                                                   String equipment)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: Equipment
    
    Returns:
    
    this.
  - functionalLocation
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder functionalLocation(@Nullable
                                                                            String functionalLocation)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: FunctionalLocation
    
    If alternative labels exist for a functional location, you can define in your user profile which label should be displayed in this field.
    
    Returns:
    
    this.
  - shopFloorItem
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder shopFloorItem(@Nullable
                                                                       Long shopFloorItem)
```
    Constraints: none
    Original property name from the Odata EDM: ShopFloorItem
    
    Returns:
    
    this.
  - selectedCodeSetPlant
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder selectedCodeSetPlant(@Nullable
                                                                              String selectedCodeSetPlant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SelectedCodeSetPlant
    
    Returns:
    
    this.
  - selectedCodeSet
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder selectedCodeSet(@Nullable
                                                                         String selectedCodeSet)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: SelectedCodeSet
    
    Returns:
    
    this.
  - inspSubsetUsageDcsnCodeGroup
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSubsetUsageDcsnCodeGroup(@Nullable
                                                                                      String inspSubsetUsageDcsnCodeGroup)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InspSubsetUsageDcsnCodeGroup
    
    Returns:
    
    this.
  - inspSubsetUsageDcsnCode
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSubsetUsageDcsnCode(@Nullable
                                                                                 String inspSubsetUsageDcsnCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: InspSubsetUsageDcsnCode
    
    Returns:
    
    this.
  - inspSubsetUsageDcsnValuation
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSubsetUsageDcsnValuation(@Nullable
                                                                                      String inspSubsetUsageDcsnValuation)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSubsetUsageDcsnValuation
    
    Returns:
    
    this.
  - inspectionSubsetTime
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetTime(@Nullable
                                                                              LocalTime inspectionSubsetTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InspectionSubsetTime
    
    Returns:
    
    this.
  - inspectionSubsetDate
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetDate(@Nullable
                                                                              LocalDateTime inspectionSubsetDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: InspectionSubsetDate
    
    Returns:
    
    this.
  - inspSubsetLongNumericKey
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSubsetLongNumericKey(@Nullable
                                                                                  String inspSubsetLongNumericKey)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspSubsetLongNumericKey
    
    Returns:
    
    this.
  - inspSubsetShortNumericKey
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSubsetShortNumericKey(@Nullable
                                                                                   String inspSubsetShortNumericKey)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspSubsetShortNumericKey
    
    Returns:
    
    this.
  - inspectionSubsetLongCharKey
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetLongCharKey(@Nullable
                                                                                     String inspectionSubsetLongCharKey)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: InspectionSubsetLongCharKey
    
    Returns:
    
    this.
  - inspectionSubsetShortCharKey
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetShortCharKey(@Nullable
                                                                                      String inspectionSubsetShortCharKey)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InspectionSubsetShortCharKey
    
    Returns:
    
    this.
  - inspectionPartialLot
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionPartialLot(@Nullable
                                                                              String inspectionPartialLot)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: InspectionPartialLot
    
    You can process partial lots by:Inspecting during production using inspection pointsRunning a batch split for the delivery note
    
    Returns:
    
    this.
  - inspector
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspector(@Nullable
                                                                   String inspector)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: Inspector
    
    The system does not check the entries made.
    
    Returns:
    
    this.
  - inspectionSubsetYieldQty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetYieldQty(@Nullable
                                                                                  BigDecimal inspectionSubsetYieldQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetYieldQty
    
    A quantity proposal is possible if the following conditions are fulfilled:Quantity-based inspection intervals are defined at operation level in the task list.The indicator for the proposal of activities is marked for the current order type in the order confirmation parameters.When you record the inspection point identifier for an order number for the first time, the planned interval quantity is proposed.In the case of an inspection point identifier, where a quantity was already recorded in an earlier operation, the last quantity recorded is proposed.
    
    Returns:
    
    this.
  - inspectionSubsetScrapQty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetScrapQty(@Nullable
                                                                                  BigDecimal inspectionSubsetScrapQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetScrapQty
    operation.
    
    Returns:
    
    this.
  - inspectionSubsetReworkQty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetReworkQty(@Nullable
                                                                                   BigDecimal inspectionSubsetReworkQty)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: InspectionSubsetReworkQty
    
    Enter the rework quantity that has accumulated since the last inspection.Depending on the confirmation indicator, this quantity is confirmed to the PP operation.If the rework quantity is simultaneously confirmed for PP, it can have the following effects:When you include a reference operation set in the current order from the confirmation (by means of trigger points),the rework quantity is adopted as the operation quantity for the rework operations.When you create a new order from the confirmation by means of trigger points, the rework quantity is adopted as the order quantity for the rework order.
    
    Returns:
    
    this.
  - inspectionSubsetQtyUnit
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetQtyUnit(@Nullable
                                                                                 String inspectionSubsetQtyUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: InspectionSubsetQtyUnit
    
    The unit of measure applies to the yield, the scrap quantity and/or the rework quantity.
    
    Returns:
    
    this.
  - inspSbstFuncnlLocProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstFuncnlLocProperty(@Nullable
                                                                                   String inspSbstFuncnlLocProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstFuncnlLocProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstEquipProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstEquipProperty(@Nullable
                                                                               String inspSbstEquipProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstEquipProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstMatlSmplProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstMatlSmplProperty(@Nullable
                                                                                  String inspSbstMatlSmplProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstMatlSmplProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspectionSubsetSortKey
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspectionSubsetSortKey(@Nullable
                                                                                 String inspectionSubsetSortKey)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: InspectionSubsetSortKey
    
    Returns:
    
    this.
  - inspSbstDateFldProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstDateFldProperty(@Nullable
                                                                                 String inspSbstDateFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstDateFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstLongNmbrFldProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstLongNmbrFldProperty(@Nullable
                                                                                     String inspSbstLongNmbrFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstLongNmbrFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstShrtNmbrFldProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstShrtNmbrFldProperty(@Nullable
                                                                                     String inspSbstShrtNmbrFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstShrtNmbrFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstLongTxtFldProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstLongTxtFldProperty(@Nullable
                                                                                    String inspSbstLongTxtFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstLongTxtFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstTimeFldProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstTimeFldProperty(@Nullable
                                                                                 String inspSbstTimeFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstTimeFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - inspSbstShrtTxtFldProperty
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder inspSbstShrtTxtFldProperty(@Nullable
                                                                                    String inspSbstShrtTxtFldProperty)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InspSbstShrtTxtFldProperty
    
    Fields with numeric entries are required fields. The numbering sequence that you define for these fields uniquely identify an inspection point.The inspection point type determines whether required fields are called up for identification. These fields cannot be changed.Wire basket/shift A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.At the operation level, an inspection interval is predefined for every 50 units.You can show this by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10 1 Wire basketNo. Length 3 X ShiftDateTimeBy marking the "Field active" column, you can make a field an optional field.In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.Vessel/Date/Time In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).This can be be shown by the following inspection point identifier:User fields Field active KeywordText Length 18Text Length 10No. Length 10No. Length 3 1 VesselDate 2 DateTime 3 TimeTest equipment Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.This can be be shown by the following inspection point identifier:Predefined field dependent on inspection point type ('1') Field active KeywordEquipment 1 Test equipmentUser fields Field Active KeywordText Length 18 Text Length 10 No. Length 10 No. Length 3 Date Time NoteEven if the test equipment type allows for certain fields, you can define additional user fields.
    
    Returns:
    
    this.
  - createdByUser
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder createdByUser(@Nullable
                                                                       String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: CreatedByUser
    
    Returns:
    
    this.
  - creationDate
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder creationDate(@Nullable
                                                                      LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    this.
  - creationTime
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder creationTime(@Nullable
                                                                      LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Returns:
    
    this.
  - lastChangedByUser
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder lastChangedByUser(@Nullable
                                                                           String lastChangedByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: LastChangedByUser
    
    Returns:
    
    this.
  - lastChangeDate
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder lastChangeDate(@Nullable
                                                                        LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Returns:
    
    this.
  - lastChangeTime
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder lastChangeTime(@Nullable
                                                                        LocalTime lastChangeTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeTime
    
    Returns:
    
    this.
  - changedDateTime
```
@Nonnull
public InspectionSubset.InspectionSubsetBuilder changedDateTime(@Nullable
                                                                         ZonedDateTime changedDateTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ChangedDateTime
    
    To standardize local times in a UTC time stamp and thus make them comparable with other times, these local times need to be converted using your time zone and the ABAP command convert.Even if the system is able to determine the time zone from Customizing or master data, you shoul save the time zone redundantly here.The internal structure of the UTC time stamp is subdivided into a date part and a time part in packed number format . You can also use the high resolution UTC time stamp (10^-7 seconds).
    
    Returns:
    
    this.
  - build
```
@Nonnull
public InspectionSubset build()
```
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class Object

Class InspectionSubset.InspectionSubsetBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

trigger_valuation_ac

inspectionLot

inspPlanOperationInternalID

inspectionSubsetInternalID

materialSample

equipment

functionalLocation

shopFloorItem

selectedCodeSetPlant

selectedCodeSet

inspSubsetUsageDcsnCodeGroup

inspSubsetUsageDcsnCode

inspSubsetUsageDcsnValuation

inspectionSubsetTime

inspectionSubsetDate

inspSubsetLongNumericKey

inspSubsetShortNumericKey

inspectionSubsetLongCharKey

inspectionSubsetShortCharKey

inspectionPartialLot

inspector

inspectionSubsetYieldQty

inspectionSubsetScrapQty

inspectionSubsetReworkQty

inspectionSubsetQtyUnit

inspSbstFuncnlLocProperty

inspSbstEquipProperty

inspSbstMatlSmplProperty

inspectionSubsetSortKey

inspSbstDateFldProperty

inspSbstLongNmbrFldProperty

inspSbstShrtNmbrFldProperty

inspSbstLongTxtFldProperty

inspSbstTimeFldProperty

inspSbstShrtTxtFldProperty

createdByUser

creationDate

creationTime

lastChangedByUser

lastChangeDate

lastChangeTime

changedDateTime

build

toString