UTC Time Stamp in Short Form (YYYYMMDDhhmmss). The UTC time stamp is the date and time relative to UTC (Universal Coordinated Time). 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 <YYYYMMDDhhmmss>. You can also use the high resolution UTC time stamp (10^-7 seconds).
Name of Person Who Created Object. Maximum length: 12.
Date on Which Record Was Created.
Time at Which Data Record Was Created.
Equipment Number. Number by which a piece of equipment can be clearly identified. Maximum length: 18.
Functional Location. Label that uniquely identifies a functional location. If alternative labels exist for a functional location, you can define in your user profile which label should be displayed in this field. Maximum length: 40.
Current Node Number from Order Counter. Maximum length: 8.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
Field Active. An identification field is only active if you have made an entry in this field. 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. Maximum length: 1.
User Field for 10 Digits. Maximum length: 10.
User Field for 3 Digits. Maximum length: 3.
Usage Decision Code. Code of the usage decision. Maximum length: 4.
Code Group of the Usage Decision. Code group of the usage decision. Maximum length: 8.
Code Valuation. Specifies the valuation of a code from the inspection catalog. Maximum length: 1.
Inspection Lot Number. Number that uniquely identifies an inspection lot. The inspection lot number is assigned by the system. Maximum length: 12.
Partial lot number. The partial lot's number, which is only unique within the corresponding inspection lot. You can process partial lots by:Inspecting during production using inspection pointsRunning a batch split for the delivery note. Maximum length: 6.
User Field for Date.
Sample Number (Based on an Inspection Point). The sample number is copied to this field from results recording. The inspection results are referenced via this number. Maximum length: 6.
User Field for 18 Characters. Maximum length: 18.
Unit of Measure for the Inspection Point. Unit used for the inspection point quantity within QM. The unit of measure applies to the yield, the scrap quantity and/or the rework quantity. Maximum length: 3.
Rework Quantity for The Inspection Point. Indicates the quantity to be reworked as a result of poor workmanship or insufficient quality. 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.
Scrap for Inspection Point. Indicates the amount of scrap produced since the last inspection and which may be confirmed for the operation.
User Field for 10 Characters. Maximum length: 10.
Key Field (Sort Field) for Inspection Point. Used to identify an inspection point. Maximum length: 70.
User Field for Time.
Inspection Point Yield. Indicates the yield produced since the last inspection and, if necessary, confirmed for the operation. 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.
Name of Inspector. The system enters the name of the user as the name of the inspector, if no other entry is made. The system does not check the entries made. Maximum length: 12.
Date of Last Change.
Time at Which Data Record Was Changed.
Name of Person who Changed Object. Maximum length: 12.
Material Sample Number. Unique, client-wide identifier for a sample. Maximum length: 12.
Selected Set of the Usage Decision. Selected set of the usage decision. Maximum length: 8.
Plant. Key uniquely identifying a plant. Maximum length: 4.
ID of Serialized Material.
Dynamic Action Property.
All fields selector.
Static representation of the changedDateTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the createdByUser property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the equipment property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the functionalLocation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionLot property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionPartialLot property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetInternalId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetLongCharKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetQtyUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetReworkQty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetScrapQty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetShortCharKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetSortKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspectionSubsetYieldQty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspector property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspPlanOperationInternalId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstDateFldProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstEquipProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstFuncnlLocProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstLongNmbrFldProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstLongTxtFldProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstMatlSmplProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstShrtNmbrFldProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstShrtTxtFldProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSbstTimeFldProperty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSubsetLongNumericKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSubsetShortNumericKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSubsetUsageDcsnCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSubsetUsageDcsnCodeGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inspSubsetUsageDcsnValuation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangedByUser property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangeDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangeTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the materialSample property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the selectedCodeSet property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the selectedCodeSetPlant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shopFloorItem property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the triggerValuationAc property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the InspectionSubset entity.
Default url path for the according service.
Technical entity name for InspectionSubset.
All key fields of the InspectionSubset entity.
Mapping of all key field names to the respective static field property InspectionSubset.
Technical service name for InspectionSubset.
Returns an entity builder to construct instances InspectionSubset.
A builder that constructs instances of entity type InspectionSubset.
Returns a selectable object that allows the selection of custom field in a get request for the entity InspectionSubset.
Name of the custom field to select
A builder that constructs instances of entity type InspectionSubset.
Returns a request builder to construct requests for operations on the InspectionSubset entity type.
A InspectionSubset request builder.
This class represents the entity "A_InspectionSubset" of service "API_INSPECTIONLOT_SRV". This service is part of the following communication scenarios: Quality Inspection Process Integration (SAP_COM_0318). See https://api.sap.com/api/API_INSPECTIONLOT_SRV for more information.