public class InspectionSubset extends VdmEntity<InspectionSubset>
Original entity name from the Odata EDM: A_InspectionSubsetType
Modifier and Type | Class and Description |
---|---|
static class |
InspectionSubset.InspectionSubsetBuilder |
Modifier and Type | Field and Description |
---|---|
static InspectionSubsetSelectable |
ALL_FIELDS
Selector for all available fields of InspectionSubset.
|
static InspectionSubsetField<ZonedDateTime> |
CHANGED_DATE_TIME
Use with available fluent helpers to apply the ChangedDateTime field to query operations.
|
static InspectionSubsetField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static InspectionSubsetField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static InspectionSubsetField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static InspectionSubsetField<String> |
EQUIPMENT
Use with available fluent helpers to apply the Equipment field to query operations.
|
static InspectionSubsetField<String> |
FUNCTIONAL_LOCATION
Use with available fluent helpers to apply the FunctionalLocation field to query operations.
|
static InspectionSubsetField<String> |
INSP_PLAN_OPERATION_INTERNAL_ID
Use with available fluent helpers to apply the InspPlanOperationInternalID field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_DATE_FLD_PROPERTY
Use with available fluent helpers to apply the InspSbstDateFldProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_EQUIP_PROPERTY
Use with available fluent helpers to apply the InspSbstEquipProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_FUNCNL_LOC_PROPERTY
Use with available fluent helpers to apply the InspSbstFuncnlLocProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_LONG_NMBR_FLD_PROPERTY
Use with available fluent helpers to apply the InspSbstLongNmbrFldProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_LONG_TXT_FLD_PROPERTY
Use with available fluent helpers to apply the InspSbstLongTxtFldProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_MATL_SMPL_PROPERTY
Use with available fluent helpers to apply the InspSbstMatlSmplProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_SHRT_NMBR_FLD_PROPERTY
Use with available fluent helpers to apply the InspSbstShrtNmbrFldProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_SHRT_TXT_FLD_PROPERTY
Use with available fluent helpers to apply the InspSbstShrtTxtFldProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SBST_TIME_FLD_PROPERTY
Use with available fluent helpers to apply the InspSbstTimeFldProperty field to query operations.
|
static InspectionSubsetField<String> |
INSP_SUBSET_LONG_NUMERIC_KEY
Use with available fluent helpers to apply the InspSubsetLongNumericKey field to query operations.
|
static InspectionSubsetField<String> |
INSP_SUBSET_SHORT_NUMERIC_KEY
Use with available fluent helpers to apply the InspSubsetShortNumericKey field to query operations.
|
static InspectionSubsetField<String> |
INSP_SUBSET_USAGE_DCSN_CODE
Use with available fluent helpers to apply the InspSubsetUsageDcsnCode field to query operations.
|
static InspectionSubsetField<String> |
INSP_SUBSET_USAGE_DCSN_CODE_GROUP
Use with available fluent helpers to apply the InspSubsetUsageDcsnCodeGroup field to query operations.
|
static InspectionSubsetField<String> |
INSP_SUBSET_USAGE_DCSN_VALUATION
Use with available fluent helpers to apply the InspSubsetUsageDcsnValuation field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_LOT
Use with available fluent helpers to apply the InspectionLot field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_PARTIAL_LOT
Use with available fluent helpers to apply the InspectionPartialLot field to query operations.
|
static InspectionSubsetField<LocalDateTime> |
INSPECTION_SUBSET_DATE
Use with available fluent helpers to apply the InspectionSubsetDate field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_SUBSET_INTERNAL_ID
Use with available fluent helpers to apply the InspectionSubsetInternalID field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_SUBSET_LONG_CHAR_KEY
Use with available fluent helpers to apply the InspectionSubsetLongCharKey field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_SUBSET_QTY_UNIT
Use with available fluent helpers to apply the InspectionSubsetQtyUnit field to query operations.
|
static InspectionSubsetField<BigDecimal> |
INSPECTION_SUBSET_REWORK_QTY
Use with available fluent helpers to apply the InspectionSubsetReworkQty field to query operations.
|
static InspectionSubsetField<BigDecimal> |
INSPECTION_SUBSET_SCRAP_QTY
Use with available fluent helpers to apply the InspectionSubsetScrapQty field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_SUBSET_SHORT_CHAR_KEY
Use with available fluent helpers to apply the InspectionSubsetShortCharKey field to query operations.
|
static InspectionSubsetField<String> |
INSPECTION_SUBSET_SORT_KEY
Use with available fluent helpers to apply the InspectionSubsetSortKey field to query operations.
|
static InspectionSubsetField<LocalTime> |
INSPECTION_SUBSET_TIME
Use with available fluent helpers to apply the InspectionSubsetTime field to query operations.
|
static InspectionSubsetField<BigDecimal> |
INSPECTION_SUBSET_YIELD_QTY
Use with available fluent helpers to apply the InspectionSubsetYieldQty field to query operations.
|
static InspectionSubsetField<String> |
INSPECTOR
Use with available fluent helpers to apply the Inspector field to query operations.
|
static InspectionSubsetField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static InspectionSubsetField<LocalTime> |
LAST_CHANGE_TIME
Use with available fluent helpers to apply the LastChangeTime field to query operations.
|
static InspectionSubsetField<String> |
LAST_CHANGED_BY_USER
Use with available fluent helpers to apply the LastChangedByUser field to query operations.
|
static InspectionSubsetField<String> |
MATERIAL_SAMPLE
Use with available fluent helpers to apply the MaterialSample field to query operations.
|
static InspectionSubsetField<String> |
SELECTED_CODE_SET
Use with available fluent helpers to apply the SelectedCodeSet field to query operations.
|
static InspectionSubsetField<String> |
SELECTED_CODE_SET_PLANT
Use with available fluent helpers to apply the SelectedCodeSetPlant field to query operations.
|
static InspectionSubsetField<Long> |
SHOP_FLOOR_ITEM
Use with available fluent helpers to apply the ShopFloorItem field to query operations.
|
static InspectionSubsetField<Boolean> |
TRIGGER_VALUATION_AC
Use with available fluent helpers to apply the Trigger_valuation_ac field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
InspectionSubset() |
InspectionSubset(Boolean trigger_valuation_ac,
String inspectionLot,
String inspPlanOperationInternalID,
String inspectionSubsetInternalID,
String materialSample,
String equipment,
String functionalLocation,
Long shopFloorItem,
String selectedCodeSetPlant,
String selectedCodeSet,
String inspSubsetUsageDcsnCodeGroup,
String inspSubsetUsageDcsnCode,
String inspSubsetUsageDcsnValuation,
LocalTime inspectionSubsetTime,
LocalDateTime inspectionSubsetDate,
String inspSubsetLongNumericKey,
String inspSubsetShortNumericKey,
String inspectionSubsetLongCharKey,
String inspectionSubsetShortCharKey,
String inspectionPartialLot,
String inspector,
BigDecimal inspectionSubsetYieldQty,
BigDecimal inspectionSubsetScrapQty,
BigDecimal inspectionSubsetReworkQty,
String inspectionSubsetQtyUnit,
String inspSbstFuncnlLocProperty,
String inspSbstEquipProperty,
String inspSbstMatlSmplProperty,
String inspectionSubsetSortKey,
String inspSbstDateFldProperty,
String inspSbstLongNmbrFldProperty,
String inspSbstShrtNmbrFldProperty,
String inspSbstLongTxtFldProperty,
String inspSbstTimeFldProperty,
String inspSbstShrtTxtFldProperty,
String createdByUser,
LocalDateTime creationDate,
LocalTime creationTime,
String lastChangedByUser,
LocalDateTime lastChangeDate,
LocalTime lastChangeTime,
ZonedDateTime changedDateTime) |
Modifier and Type | Method and Description |
---|---|
void |
attachToService(String servicePath,
ErpConfigContext configContext)
Sets the service path and ERP configuration context for the fetch commands of this entity.
|
static InspectionSubset.InspectionSubsetBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> InspectionSubsetField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
ZonedDateTime |
getChangedDateTime()
Constraints: Not nullable, Precision: 0
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
protected String |
getDefaultServicePath() |
protected String |
getEntityCollection() |
String |
getEquipment()
Constraints: Not nullable, Maximum length: 18
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getFunctionalLocation()
Constraints: Not nullable, Maximum length: 40
|
String |
getInspectionLot()
(Key Field) Constraints: Not nullable, Maximum length: 12
|
String |
getInspectionPartialLot()
Constraints: Not nullable, Maximum length: 6
|
LocalDateTime |
getInspectionSubsetDate()
Constraints: Not nullable, Precision: 0
|
String |
getInspectionSubsetInternalID()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getInspectionSubsetLongCharKey()
Constraints: Not nullable, Maximum length: 18
|
String |
getInspectionSubsetQtyUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getInspectionSubsetReworkQty()
Constraints: Not nullable, Precision: 13, Scale: 3
|
BigDecimal |
getInspectionSubsetScrapQty()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getInspectionSubsetShortCharKey()
Constraints: Not nullable, Maximum length: 10
|
String |
getInspectionSubsetSortKey()
Constraints: Not nullable, Maximum length: 70
|
LocalTime |
getInspectionSubsetTime()
Constraints: Not nullable, Precision: 0
|
BigDecimal |
getInspectionSubsetYieldQty()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getInspector()
Constraints: Not nullable, Maximum length: 12
|
String |
getInspPlanOperationInternalID()
(Key Field) Constraints: Not nullable, Maximum length: 8
|
String |
getInspSbstDateFldProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstEquipProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstFuncnlLocProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstLongNmbrFldProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstLongTxtFldProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstMatlSmplProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstShrtNmbrFldProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstShrtTxtFldProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSbstTimeFldProperty()
Constraints: Not nullable, Maximum length: 1
|
String |
getInspSubsetLongNumericKey()
Constraints: Not nullable, Maximum length: 10
|
String |
getInspSubsetShortNumericKey()
Constraints: Not nullable, Maximum length: 3
|
String |
getInspSubsetUsageDcsnCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getInspSubsetUsageDcsnCodeGroup()
Constraints: Not nullable, Maximum length: 8
|
String |
getInspSubsetUsageDcsnValuation()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
String |
getLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalTime |
getLastChangeTime()
Constraints: Not nullable, Precision: 0
|
String |
getMaterialSample()
Constraints: Not nullable, Maximum length: 12
|
String |
getSelectedCodeSet()
Constraints: Not nullable, Maximum length: 8
|
String |
getSelectedCodeSetPlant()
Constraints: Not nullable, Maximum length: 4
|
Long |
getShopFloorItem()
Constraints: none
|
Boolean |
getTrigger_valuation_ac()
Constraints: none
|
Class<InspectionSubset> |
getType() |
int |
hashCode() |
void |
setChangedDateTime(ZonedDateTime changedDateTime)
Constraints: Not nullable, Precision: 0
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setEquipment(String equipment)
Constraints: Not nullable, Maximum length: 18
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Deprecated.
Use
attachToService(String, ErpConfigContext) instead. |
void |
setFunctionalLocation(String functionalLocation)
Constraints: Not nullable, Maximum length: 40
|
void |
setInspectionLot(String inspectionLot)
(Key Field) Constraints: Not nullable, Maximum length: 12
|
void |
setInspectionPartialLot(String inspectionPartialLot)
Constraints: Not nullable, Maximum length: 6
|
void |
setInspectionSubsetDate(LocalDateTime inspectionSubsetDate)
Constraints: Not nullable, Precision: 0
|
void |
setInspectionSubsetInternalID(String inspectionSubsetInternalID)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setInspectionSubsetLongCharKey(String inspectionSubsetLongCharKey)
Constraints: Not nullable, Maximum length: 18
|
void |
setInspectionSubsetQtyUnit(String inspectionSubsetQtyUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setInspectionSubsetReworkQty(BigDecimal inspectionSubsetReworkQty)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setInspectionSubsetScrapQty(BigDecimal inspectionSubsetScrapQty)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setInspectionSubsetShortCharKey(String inspectionSubsetShortCharKey)
Constraints: Not nullable, Maximum length: 10
|
void |
setInspectionSubsetSortKey(String inspectionSubsetSortKey)
Constraints: Not nullable, Maximum length: 70
|
void |
setInspectionSubsetTime(LocalTime inspectionSubsetTime)
Constraints: Not nullable, Precision: 0
|
void |
setInspectionSubsetYieldQty(BigDecimal inspectionSubsetYieldQty)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setInspector(String inspector)
Constraints: Not nullable, Maximum length: 12
|
void |
setInspPlanOperationInternalID(String inspPlanOperationInternalID)
(Key Field) Constraints: Not nullable, Maximum length: 8
|
void |
setInspSbstDateFldProperty(String inspSbstDateFldProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstEquipProperty(String inspSbstEquipProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstFuncnlLocProperty(String inspSbstFuncnlLocProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstLongNmbrFldProperty(String inspSbstLongNmbrFldProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstLongTxtFldProperty(String inspSbstLongTxtFldProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstMatlSmplProperty(String inspSbstMatlSmplProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstShrtNmbrFldProperty(String inspSbstShrtNmbrFldProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstShrtTxtFldProperty(String inspSbstShrtTxtFldProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSbstTimeFldProperty(String inspSbstTimeFldProperty)
Constraints: Not nullable, Maximum length: 1
|
void |
setInspSubsetLongNumericKey(String inspSubsetLongNumericKey)
Constraints: Not nullable, Maximum length: 10
|
void |
setInspSubsetShortNumericKey(String inspSubsetShortNumericKey)
Constraints: Not nullable, Maximum length: 3
|
void |
setInspSubsetUsageDcsnCode(String inspSubsetUsageDcsnCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setInspSubsetUsageDcsnCodeGroup(String inspSubsetUsageDcsnCodeGroup)
Constraints: Not nullable, Maximum length: 8
|
void |
setInspSubsetUsageDcsnValuation(String inspSubsetUsageDcsnValuation)
Constraints: Not nullable, Maximum length: 1
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setLastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setLastChangeTime(LocalTime lastChangeTime)
Constraints: Not nullable, Precision: 0
|
void |
setMaterialSample(String materialSample)
Constraints: Not nullable, Maximum length: 12
|
void |
setSelectedCodeSet(String selectedCodeSet)
Constraints: Not nullable, Maximum length: 8
|
void |
setSelectedCodeSetPlant(String selectedCodeSetPlant)
Constraints: Not nullable, Maximum length: 4
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setShopFloorItem(Long shopFloorItem)
Constraints: none
|
void |
setTrigger_valuation_ac(Boolean trigger_valuation_ac)
Constraints: none
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final InspectionSubsetSelectable ALL_FIELDS
public static final InspectionSubsetField<Boolean> TRIGGER_VALUATION_AC
public static final InspectionSubsetField<String> INSPECTION_LOT
public static final InspectionSubsetField<String> INSP_PLAN_OPERATION_INTERNAL_ID
public static final InspectionSubsetField<String> INSPECTION_SUBSET_INTERNAL_ID
public static final InspectionSubsetField<String> MATERIAL_SAMPLE
public static final InspectionSubsetField<String> EQUIPMENT
public static final InspectionSubsetField<String> FUNCTIONAL_LOCATION
public static final InspectionSubsetField<Long> SHOP_FLOOR_ITEM
public static final InspectionSubsetField<String> SELECTED_CODE_SET_PLANT
public static final InspectionSubsetField<String> SELECTED_CODE_SET
public static final InspectionSubsetField<String> INSP_SUBSET_USAGE_DCSN_CODE_GROUP
public static final InspectionSubsetField<String> INSP_SUBSET_USAGE_DCSN_CODE
public static final InspectionSubsetField<String> INSP_SUBSET_USAGE_DCSN_VALUATION
public static final InspectionSubsetField<LocalTime> INSPECTION_SUBSET_TIME
public static final InspectionSubsetField<LocalDateTime> INSPECTION_SUBSET_DATE
public static final InspectionSubsetField<String> INSP_SUBSET_LONG_NUMERIC_KEY
public static final InspectionSubsetField<String> INSP_SUBSET_SHORT_NUMERIC_KEY
public static final InspectionSubsetField<String> INSPECTION_SUBSET_LONG_CHAR_KEY
public static final InspectionSubsetField<String> INSPECTION_SUBSET_SHORT_CHAR_KEY
public static final InspectionSubsetField<String> INSPECTION_PARTIAL_LOT
public static final InspectionSubsetField<String> INSPECTOR
public static final InspectionSubsetField<BigDecimal> INSPECTION_SUBSET_YIELD_QTY
public static final InspectionSubsetField<BigDecimal> INSPECTION_SUBSET_SCRAP_QTY
public static final InspectionSubsetField<BigDecimal> INSPECTION_SUBSET_REWORK_QTY
public static final InspectionSubsetField<String> INSPECTION_SUBSET_QTY_UNIT
public static final InspectionSubsetField<String> INSP_SBST_FUNCNL_LOC_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_EQUIP_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_MATL_SMPL_PROPERTY
public static final InspectionSubsetField<String> INSPECTION_SUBSET_SORT_KEY
public static final InspectionSubsetField<String> INSP_SBST_DATE_FLD_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_LONG_NMBR_FLD_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_SHRT_NMBR_FLD_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_LONG_TXT_FLD_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_TIME_FLD_PROPERTY
public static final InspectionSubsetField<String> INSP_SBST_SHRT_TXT_FLD_PROPERTY
public static final InspectionSubsetField<String> CREATED_BY_USER
public static final InspectionSubsetField<LocalDateTime> CREATION_DATE
public static final InspectionSubsetField<LocalTime> CREATION_TIME
public static final InspectionSubsetField<String> LAST_CHANGED_BY_USER
public static final InspectionSubsetField<LocalDateTime> LAST_CHANGE_DATE
public static final InspectionSubsetField<LocalTime> LAST_CHANGE_TIME
public static final InspectionSubsetField<ZonedDateTime> CHANGED_DATE_TIME
public InspectionSubset()
public InspectionSubset(@Nullable Boolean trigger_valuation_ac, @Nullable String inspectionLot, @Nullable String inspPlanOperationInternalID, @Nullable String inspectionSubsetInternalID, @Nullable String materialSample, @Nullable String equipment, @Nullable String functionalLocation, @Nullable Long shopFloorItem, @Nullable String selectedCodeSetPlant, @Nullable String selectedCodeSet, @Nullable String inspSubsetUsageDcsnCodeGroup, @Nullable String inspSubsetUsageDcsnCode, @Nullable String inspSubsetUsageDcsnValuation, @Nullable LocalTime inspectionSubsetTime, @Nullable LocalDateTime inspectionSubsetDate, @Nullable String inspSubsetLongNumericKey, @Nullable String inspSubsetShortNumericKey, @Nullable String inspectionSubsetLongCharKey, @Nullable String inspectionSubsetShortCharKey, @Nullable String inspectionPartialLot, @Nullable String inspector, @Nullable BigDecimal inspectionSubsetYieldQty, @Nullable BigDecimal inspectionSubsetScrapQty, @Nullable BigDecimal inspectionSubsetReworkQty, @Nullable String inspectionSubsetQtyUnit, @Nullable String inspSbstFuncnlLocProperty, @Nullable String inspSbstEquipProperty, @Nullable String inspSbstMatlSmplProperty, @Nullable String inspectionSubsetSortKey, @Nullable String inspSbstDateFldProperty, @Nullable String inspSbstLongNmbrFldProperty, @Nullable String inspSbstShrtNmbrFldProperty, @Nullable String inspSbstLongTxtFldProperty, @Nullable String inspSbstTimeFldProperty, @Nullable String inspSbstShrtTxtFldProperty, @Nullable String createdByUser, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, @Nullable String lastChangedByUser, @Nullable LocalDateTime lastChangeDate, @Nullable LocalTime lastChangeTime, @Nullable ZonedDateTime changedDateTime)
@Nonnull public Class<InspectionSubset> getType()
getType
in class VdmObject<InspectionSubset>
public void setTrigger_valuation_ac(@Nullable Boolean trigger_valuation_ac)
Original property name from the Odata EDM: Trigger_valuation_ac
trigger_valuation_ac
- Dynamic Action Propertypublic void setInspectionLot(@Nullable String inspectionLot)
Original property name from the Odata EDM: InspectionLot
The inspection lot number is assigned by the system.
inspectionLot
- Number that uniquely identifies an inspection lot.public void setInspPlanOperationInternalID(@Nullable String inspPlanOperationInternalID)
Original property name from the Odata EDM: InspPlanOperationInternalID
inspPlanOperationInternalID
- Current Node Number from Order Counterpublic void setInspectionSubsetInternalID(@Nullable String inspectionSubsetInternalID)
Original property name from the Odata EDM: InspectionSubsetInternalID
inspectionSubsetInternalID
- The sample number is copied to this field from results recording. The inspection results are
referenced via this number.public void setMaterialSample(@Nullable String materialSample)
Original property name from the Odata EDM: MaterialSample
materialSample
- Unique, client-wide identifier for a sample.public void setEquipment(@Nullable String equipment)
Original property name from the Odata EDM: Equipment
equipment
- Number by which a piece of equipment can be clearly identified.public void setFunctionalLocation(@Nullable String functionalLocation)
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.
functionalLocation
- Label that uniquely identifies a functional location.public void setShopFloorItem(@Nullable Long shopFloorItem)
Original property name from the Odata EDM: ShopFloorItem
shopFloorItem
- ID of Serialized Materialpublic void setSelectedCodeSetPlant(@Nullable String selectedCodeSetPlant)
Original property name from the Odata EDM: SelectedCodeSetPlant
selectedCodeSetPlant
- Key uniquely identifying a plant.public void setSelectedCodeSet(@Nullable String selectedCodeSet)
Original property name from the Odata EDM: SelectedCodeSet
selectedCodeSet
- Selected set of the usage decision.public void setInspSubsetUsageDcsnCodeGroup(@Nullable String inspSubsetUsageDcsnCodeGroup)
Original property name from the Odata EDM: InspSubsetUsageDcsnCodeGroup
inspSubsetUsageDcsnCodeGroup
- Code group of the usage decision.public void setInspSubsetUsageDcsnCode(@Nullable String inspSubsetUsageDcsnCode)
Original property name from the Odata EDM: InspSubsetUsageDcsnCode
inspSubsetUsageDcsnCode
- Code of the usage decision.public void setInspSubsetUsageDcsnValuation(@Nullable String inspSubsetUsageDcsnValuation)
Original property name from the Odata EDM: InspSubsetUsageDcsnValuation
inspSubsetUsageDcsnValuation
- Specifies the valuation of a code from the inspection catalog.public void setInspectionSubsetTime(@Nullable LocalTime inspectionSubsetTime)
Original property name from the Odata EDM: InspectionSubsetTime
inspectionSubsetTime
- User Field for Timepublic void setInspectionSubsetDate(@Nullable LocalDateTime inspectionSubsetDate)
Original property name from the Odata EDM: InspectionSubsetDate
inspectionSubsetDate
- User Field for Datepublic void setInspSubsetLongNumericKey(@Nullable String inspSubsetLongNumericKey)
Original property name from the Odata EDM: InspSubsetLongNumericKey
inspSubsetLongNumericKey
- User Field for 10 Digitspublic void setInspSubsetShortNumericKey(@Nullable String inspSubsetShortNumericKey)
Original property name from the Odata EDM: InspSubsetShortNumericKey
inspSubsetShortNumericKey
- User Field for 3 Digitspublic void setInspectionSubsetLongCharKey(@Nullable String inspectionSubsetLongCharKey)
Original property name from the Odata EDM: InspectionSubsetLongCharKey
inspectionSubsetLongCharKey
- User Field for 18 Characterspublic void setInspectionSubsetShortCharKey(@Nullable String inspectionSubsetShortCharKey)
Original property name from the Odata EDM: InspectionSubsetShortCharKey
inspectionSubsetShortCharKey
- User Field for 10 Characterspublic void setInspectionPartialLot(@Nullable String inspectionPartialLot)
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
inspectionPartialLot
- The partial lot's number, which is only unique within the corresponding inspection lot.public void setInspector(@Nullable String inspector)
Original property name from the Odata EDM: Inspector
The system does not check the entries made.
inspector
- The system enters the name of the user as the name of the inspector, if no other entry is made.public void setInspectionSubsetYieldQty(@Nullable BigDecimal inspectionSubsetYieldQty)
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.
inspectionSubsetYieldQty
- Indicates the yield produced since the last inspection and, if necessary, confirmed for the operation.public void setInspectionSubsetScrapQty(@Nullable BigDecimal inspectionSubsetScrapQty)
Original property name from the Odata EDM: InspectionSubsetScrapQty
inspectionSubsetScrapQty
- Indicates the amount of scrap produced since the last inspection and which may be confirmed for the
operation.public void setInspectionSubsetReworkQty(@Nullable BigDecimal inspectionSubsetReworkQty)
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.
inspectionSubsetReworkQty
- Indicates the quantity to be reworked as a result of poor workmanship or insufficient quality.public void setInspectionSubsetQtyUnit(@Nullable String inspectionSubsetQtyUnit)
Original property name from the Odata EDM: InspectionSubsetQtyUnit
The unit of measure applies to the yield, the scrap quantity and/or the rework quantity.
inspectionSubsetQtyUnit
- Unit used for the inspection point quantity within QM.public void setInspSbstFuncnlLocProperty(@Nullable String inspSbstFuncnlLocProperty)
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.
inspSbstFuncnlLocProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstEquipProperty(@Nullable String inspSbstEquipProperty)
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.
inspSbstEquipProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstMatlSmplProperty(@Nullable String inspSbstMatlSmplProperty)
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.
inspSbstMatlSmplProperty
- An identification field is only active if you have made an entry in this field.public void setInspectionSubsetSortKey(@Nullable String inspectionSubsetSortKey)
Original property name from the Odata EDM: InspectionSubsetSortKey
inspectionSubsetSortKey
- Used to identify an inspection point.public void setInspSbstDateFldProperty(@Nullable String inspSbstDateFldProperty)
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.
inspSbstDateFldProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstLongNmbrFldProperty(@Nullable String inspSbstLongNmbrFldProperty)
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.
inspSbstLongNmbrFldProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstShrtNmbrFldProperty(@Nullable String inspSbstShrtNmbrFldProperty)
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.
inspSbstShrtNmbrFldProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstLongTxtFldProperty(@Nullable String inspSbstLongTxtFldProperty)
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.
inspSbstLongTxtFldProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstTimeFldProperty(@Nullable String inspSbstTimeFldProperty)
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.
inspSbstTimeFldProperty
- An identification field is only active if you have made an entry in this field.public void setInspSbstShrtTxtFldProperty(@Nullable String inspSbstShrtTxtFldProperty)
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.
inspSbstShrtTxtFldProperty
- An identification field is only active if you have made an entry in this field.public void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- Name of Person Who Created Objectpublic void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime
- Time at Which Data Record Was Createdpublic void setLastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
lastChangedByUser
- Name of Person who Changed Objectpublic void setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
lastChangeDate
- Date of Last Changepublic void setLastChangeTime(@Nullable LocalTime lastChangeTime)
Original property name from the Odata EDM: LastChangeTime
lastChangeTime
- Time at Which Data Record Was Changedpublic void setChangedDateTime(@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
changedDateTime
- The UTC time stamp is the date and time relative to UTC (Universal Coordinated Time).protected String getEntityCollection()
getEntityCollection
in class VdmEntity<InspectionSubset>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<InspectionSubset>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<InspectionSubset>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<InspectionSubset>
@Nonnull public static <T> InspectionSubsetField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> InspectionSubsetField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public ErpConfigContext getErpConfigContext()
VdmEntity
getErpConfigContext
in class VdmEntity<InspectionSubset>
@Deprecated public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
attachToService(String, ErpConfigContext)
instead.VdmEntity
setErpConfigContext
in class VdmEntity<InspectionSubset>
erpConfigContext
- New ERP configuration context to apply to this entityprotected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<InspectionSubset>
public void attachToService(@Nullable String servicePath, @Nullable ErpConfigContext configContext)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<InspectionSubset>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.configContext
- Optional parameter. New ERP configuration context to apply to this entity and any associated entities
that were previously fetched. If a null value is provided and the ERP configuration context has never
been set, then the ERP configuration context will be set to a new instance of
ErpConfigContext
.protected String getDefaultServicePath()
getDefaultServicePath
in class VdmEntity<InspectionSubset>
public static InspectionSubset.InspectionSubsetBuilder builder()
@Nullable public Boolean getTrigger_valuation_ac()
Original property name from the Odata EDM: Trigger_valuation_ac
@Nullable public String getInspectionLot()
Original property name from the Odata EDM: InspectionLot
The inspection lot number is assigned by the system.
@Nullable public String getInspPlanOperationInternalID()
Original property name from the Odata EDM: InspPlanOperationInternalID
@Nullable public String getInspectionSubsetInternalID()
Original property name from the Odata EDM: InspectionSubsetInternalID
@Nullable public String getMaterialSample()
Original property name from the Odata EDM: MaterialSample
@Nullable public String getEquipment()
Original property name from the Odata EDM: Equipment
@Nullable public String getFunctionalLocation()
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.
@Nullable public Long getShopFloorItem()
Original property name from the Odata EDM: ShopFloorItem
@Nullable public String getSelectedCodeSetPlant()
Original property name from the Odata EDM: SelectedCodeSetPlant
@Nullable public String getSelectedCodeSet()
Original property name from the Odata EDM: SelectedCodeSet
@Nullable public String getInspSubsetUsageDcsnCodeGroup()
Original property name from the Odata EDM: InspSubsetUsageDcsnCodeGroup
@Nullable public String getInspSubsetUsageDcsnCode()
Original property name from the Odata EDM: InspSubsetUsageDcsnCode
@Nullable public String getInspSubsetUsageDcsnValuation()
Original property name from the Odata EDM: InspSubsetUsageDcsnValuation
@Nullable public LocalTime getInspectionSubsetTime()
Original property name from the Odata EDM: InspectionSubsetTime
@Nullable public LocalDateTime getInspectionSubsetDate()
Original property name from the Odata EDM: InspectionSubsetDate
@Nullable public String getInspSubsetLongNumericKey()
Original property name from the Odata EDM: InspSubsetLongNumericKey
@Nullable public String getInspSubsetShortNumericKey()
Original property name from the Odata EDM: InspSubsetShortNumericKey
@Nullable public String getInspectionSubsetLongCharKey()
Original property name from the Odata EDM: InspectionSubsetLongCharKey
@Nullable public String getInspectionSubsetShortCharKey()
Original property name from the Odata EDM: InspectionSubsetShortCharKey
@Nullable public String getInspectionPartialLot()
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
@Nullable public String getInspector()
Original property name from the Odata EDM: Inspector
The system does not check the entries made.
@Nullable public BigDecimal getInspectionSubsetYieldQty()
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.
@Nullable public BigDecimal getInspectionSubsetScrapQty()
Original property name from the Odata EDM: InspectionSubsetScrapQty
@Nullable public BigDecimal getInspectionSubsetReworkQty()
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.
@Nullable public String getInspectionSubsetQtyUnit()
Original property name from the Odata EDM: InspectionSubsetQtyUnit
The unit of measure applies to the yield, the scrap quantity and/or the rework quantity.
@Nullable public String getInspSbstFuncnlLocProperty()
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.
@Nullable public String getInspSbstEquipProperty()
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.
@Nullable public String getInspSbstMatlSmplProperty()
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.
@Nullable public String getInspectionSubsetSortKey()
Original property name from the Odata EDM: InspectionSubsetSortKey
@Nullable public String getInspSbstDateFldProperty()
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.
@Nullable public String getInspSbstLongNmbrFldProperty()
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.
@Nullable public String getInspSbstShrtNmbrFldProperty()
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.
@Nullable public String getInspSbstLongTxtFldProperty()
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.
@Nullable public String getInspSbstTimeFldProperty()
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.
@Nullable public String getInspSbstShrtTxtFldProperty()
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.
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nullable public String getLastChangedByUser()
Original property name from the Odata EDM: LastChangedByUser
@Nullable public LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
@Nullable public LocalTime getLastChangeTime()
Original property name from the Odata EDM: LastChangeTime
@Nullable public ZonedDateTime getChangedDateTime()
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 String toString()
toString
in class VdmObject<InspectionSubset>
public boolean equals(Object o)
equals
in class VdmObject<InspectionSubset>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<InspectionSubset>
public int hashCode()
hashCode
in class VdmObject<InspectionSubset>
Copyright © 2019 SAP SE. All rights reserved.