SalesOrderBOMItem (SAP Cloud SDK - Parent POM 3.39.0 API)

java.lang.Object
- com.sap.cloud.sdk.datamodel.odata.helper.VdmObject<EntityT>
- - com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity<SalesOrderBOMItem>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.orderbillofmaterial.SalesOrderBOMItem

public class SalesOrderBOMItem
extends VdmEntity<SalesOrderBOMItem>

Item

Original entity name from the Odata EDM: SalesOrderBOMItemType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class SalesOrderBOMItem.SalesOrderBOMItemBuilder
Helper class to allow for fluent creation of SalesOrderBOMItem instances.

Nested Classes
Modifier and Type	Class and Description
`static class`	`SalesOrderBOMItem.SalesOrderBOMItemBuilder` Helper class to allow for fluent creation of SalesOrderBOMItem instances.

Field Summary

Fields
Modifier and Type	Field and Description
`static SalesOrderBOMItemSelectable`	`ALL_FIELDS` Selector for all available fields of SalesOrderBOMItem.
`static SalesOrderBOMItemField<String>`	`ALTERNATIVE_ITEM_GROUP` Use with available fluent helpers to apply the AlternativeItemGroup field to query operations.
`static SalesOrderBOMItemField<String>`	`ALTERNATIVE_ITEM_PRIORITY` Use with available fluent helpers to apply the AlternativeItemPriority field to query operations.
`static SalesOrderBOMItemField<String>`	`ALTERNATIVE_ITEM_STRATEGY` Use with available fluent helpers to apply the AlternativeItemStrategy field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL` Use with available fluent helpers to apply the BillOfMaterial field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_CATEGORY` Use with available fluent helpers to apply the BillOfMaterialCategory field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_COMPONENT` Use with available fluent helpers to apply the BillOfMaterialComponent field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_ITEM_CATEGORY` Use with available fluent helpers to apply the BillOfMaterialItemCategory field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_ITEM_NODE_NUMBER` Use with available fluent helpers to apply the BillOfMaterialItemNodeNumber field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_ITEM_NUMBER` Use with available fluent helpers to apply the BillOfMaterialItemNumber field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`BILL_OF_MATERIAL_ITEM_QUANTITY` Use with available fluent helpers to apply the BillOfMaterialItemQuantity field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_ITEM_UNIT` Use with available fluent helpers to apply the BillOfMaterialItemUnit field to query operations.
`static SalesOrderBOMItemField<UUID>`	`BILL_OF_MATERIAL_ITEM_UUID` Use with available fluent helpers to apply the BillOfMaterialItemUUID field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_VARIANT` Use with available fluent helpers to apply the BillOfMaterialVariant field to query operations.
`static SalesOrderBOMItemField<String>`	`BILL_OF_MATERIAL_VARIANT_USAGE` Use with available fluent helpers to apply the BillOfMaterialVariantUsage field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`BOM_IS_RECURSIVE` Use with available fluent helpers to apply the BOMIsRecursive field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_CREATED_BY_USER` Use with available fluent helpers to apply the BOMItemCreatedByUser field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_DESCRIPTION` Use with available fluent helpers to apply the BOMItemDescription field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`BOM_ITEM_HAS_FIXED_QUANTITY` Use with available fluent helpers to apply the BOMItemHasFixedQuantity field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_INTERNAL_CHANGE_COUNT` Use with available fluent helpers to apply the BOMItemInternalChangeCount field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_IS_COSTING_RELEVANT` Use with available fluent helpers to apply the BOMItemIsCostingRelevant field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`BOM_ITEM_IS_PLANT_MAINT_RELEVANT` Use with available fluent helpers to apply the BOMItemIsPlantMaintRelevant field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_IS_SALES_RELEVANT` Use with available fluent helpers to apply the BOMItemIsSalesRelevant field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_IS_SPARE_PART` Use with available fluent helpers to apply the BOMItemIsSparePart field to query operations.
`static SalesOrderBOMItemField<LocalDateTime>`	`BOM_ITEM_LAST_CHANGE_DATE` Use with available fluent helpers to apply the BOMItemLastChangeDate field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_LAST_CHANGED_BY_USER` Use with available fluent helpers to apply the BOMItemLastChangedByUser field to query operations.
`static SalesOrderBOMItemField<LocalDateTime>`	`BOM_ITEM_RECORD_CREATION_DATE` Use with available fluent helpers to apply the BOMItemRecordCreationDate field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_SORTER` Use with available fluent helpers to apply the BOMItemSorter field to query operations.
`static SalesOrderBOMItemField<String>`	`BOM_ITEM_TEXT2` Use with available fluent helpers to apply the BOMItemText2 field to query operations.
`static SalesOrderBOMItemField<String>`	`CHG_TO_ENGINEERING_CHG_DOCUMENT` Use with available fluent helpers to apply the ChgToEngineeringChgDocument field to query operations.
`static SalesOrderBOMItemField<String>`	`CLASS_NUMBER` Use with available fluent helpers to apply the ClassNumber field to query operations.
`static SalesOrderBOMItemField<String>`	`CLASS_TYPE` Use with available fluent helpers to apply the ClassType field to query operations.
`static SalesOrderBOMItemField<String>`	`COMPONENT_DESCRIPTION` Use with available fluent helpers to apply the ComponentDescription field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`COMPONENT_SCRAP_IN_PERCENT` Use with available fluent helpers to apply the ComponentScrapInPercent field to query operations.
`static SalesOrderBOMItemField<String>`	`COST_ELEMENT` Use with available fluent helpers to apply the CostElement field to query operations.
`static SalesOrderBOMItemField<String>`	`CREDITOR` Use with available fluent helpers to apply the Creditor field to query operations.
`static SalesOrderBOMItemField<String>`	`CURRENCY` Use with available fluent helpers to apply the Currency field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`DELIVERY_DURATION_IN_DAYS` Use with available fluent helpers to apply the DeliveryDurationInDays field to query operations.
`static SalesOrderBOMItemField<String>`	`DEPENDENCY_OBJECT_NUMBER` Use with available fluent helpers to apply the DependencyObjectNumber field to query operations.
`static SalesOrderBOMItemField<String>`	`DISCONTINUATION_GROUP` Use with available fluent helpers to apply the DiscontinuationGroup field to query operations.
`static SalesOrderBOMItemField<String>`	`DISTR_KEY_COMP_CONSUMPTION` Use with available fluent helpers to apply the DistrKeyCompConsumption field to query operations.
`static SalesOrderBOMItemField<String>`	`DOC_NUMBER` Use with available fluent helpers to apply the DocNumber field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`DOCUMENT_IS_CREATED_BY_CAD` Use with available fluent helpers to apply the DocumentIsCreatedByCAD field to query operations.
`static SalesOrderBOMItemField<String>`	`DOCUMENT_PART` Use with available fluent helpers to apply the DocumentPart field to query operations.
`static SalesOrderBOMItemField<String>`	`DOCUMENT_TYPE` Use with available fluent helpers to apply the DocumentType field to query operations.
`static SalesOrderBOMItemField<String>`	`DOCUMENT_VERSION` Use with available fluent helpers to apply the DocumentVersion field to query operations.
`static SalesOrderBOMItemField<String>`	`ENGINEERING_CHANGE_DOC_FOR_EDIT` Use with available fluent helpers to apply the EngineeringChangeDocForEdit field to query operations.
`static SalesOrderBOMItemField<String>`	`ENGINEERING_CHANGE_DOCUMENT` Use with available fluent helpers to apply the EngineeringChangeDocument field to query operations.
`static SalesOrderBOMItemField<String>`	`EXPLOSION_TYPE` Use with available fluent helpers to apply the ExplosionType field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`FIXED_QUANTITY` Use with available fluent helpers to apply the FixedQuantity field to query operations.
`static SalesOrderBOMItemField<String>`	`FOLLOW_UP_GROUP` Use with available fluent helpers to apply the FollowUpGroup field to query operations.
`static SalesOrderBOMItemField<String>`	`FORMULA_KEY` Use with available fluent helpers to apply the FormulaKey field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`GOODS_RECEIPT_DURATION` Use with available fluent helpers to apply the GoodsReceiptDuration field to query operations.
`static SalesOrderBOMItemField<String>`	`HEADER_CHANGE_DOCUMENT` Use with available fluent helpers to apply the HeaderChangeDocument field to query operations.
`static SalesOrderBOMItemField<String>`	`IDENTIFIER_BOM_ITEM` Use with available fluent helpers to apply the IdentifierBOMItem field to query operations.
`static SalesOrderBOMItemField<String>`	`INHERITED_NODE_NUMBER_FOR_BOM_ITEM` Use with available fluent helpers to apply the InheritedNodeNumberForBOMItem field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_ALE` Use with available fluent helpers to apply the IsALE field to query operations.
`static SalesOrderBOMItemField<String>`	`IS_ASSEMBLY` Use with available fluent helpers to apply the IsAssembly field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_BOM_RECURSIVE_ALLOWED` Use with available fluent helpers to apply the IsBOMRecursiveAllowed field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_BULK_MATERIAL` Use with available fluent helpers to apply the IsBulkMaterial field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_CLASSIFICATION_RELEVANT` Use with available fluent helpers to apply the IsClassificationRelevant field to query operations.
`static SalesOrderBOMItemField<String>`	`IS_CONFIGURABLE_BOM` Use with available fluent helpers to apply the IsConfigurableBOM field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_DELETED` Use with available fluent helpers to apply the IsDeleted field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_ENGINEERING_RELEVANT` Use with available fluent helpers to apply the IsEngineeringRelevant field to query operations.
`static SalesOrderBOMItemField<String>`	`IS_MATERIAL_PROVISION` Use with available fluent helpers to apply the IsMaterialProvision field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_NET_SCRAP` Use with available fluent helpers to apply the IsNetScrap field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_PRODUCTION_RELEVANT` Use with available fluent helpers to apply the IsProductionRelevant field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`IS_SUB_ITEM` Use with available fluent helpers to apply the IsSubItem field to query operations.
`static SalesOrderBOMItemField<ZonedDateTime>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`LEAD_TIME_OFFSET` Use with available fluent helpers to apply the LeadTimeOffset field to query operations.
`static SalesOrderBOMItemField<String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`MATERIAL_COMPONENT_PRICE` Use with available fluent helpers to apply the MaterialComponentPrice field to query operations.
`static SalesOrderBOMItemField<String>`	`MATERIAL_GROUP` Use with available fluent helpers to apply the MaterialGroup field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`MATERIAL_IS_CO_PRODUCT` Use with available fluent helpers to apply the MaterialIsCoProduct field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`MATERIAL_PRICE_UNIT_QTY` Use with available fluent helpers to apply the MaterialPriceUnitQty field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`MULTIPLE_SELECTION_ALLOWED` Use with available fluent helpers to apply the MultipleSelectionAllowed field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`NUMBER_OF_VARIABLE_SIZE_ITEM` Use with available fluent helpers to apply the NumberOfVariableSizeItem field to query operations.
`static SalesOrderBOMItemField<String>`	`OBJECT_TYPE` Use with available fluent helpers to apply the ObjectType field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`OPERATION_LEAD_TIME_OFFSET` Use with available fluent helpers to apply the OperationLeadTimeOffset field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`OPERATION_SCRAP_IN_PERCENT` Use with available fluent helpers to apply the OperationScrapInPercent field to query operations.
`static SalesOrderBOMItemField<String>`	`OPS_LEAD_TIME_OFFSET_UNIT` Use with available fluent helpers to apply the OpsLeadTimeOffsetUnit field to query operations.
`static SalesOrderBOMItemField<String>`	`PLANT` Use with available fluent helpers to apply the Plant field to query operations.
`static SalesOrderBOMItemField<String>`	`PROD_ORDER_ISSUE_LOCATION` Use with available fluent helpers to apply the ProdOrderIssueLocation field to query operations.
`static SalesOrderBOMItemField<String>`	`PRODUCTION_SUPPLY_AREA` Use with available fluent helpers to apply the ProductionSupplyArea field to query operations.
`static SalesOrderBOMItemField<String>`	`PURCHASING_GROUP` Use with available fluent helpers to apply the PurchasingGroup field to query operations.
`static SalesOrderBOMItemField<String>`	`PURCHASING_ORGANIZATION` Use with available fluent helpers to apply the PurchasingOrganization field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`QUANTITY_VARIABLE_SIZE_ITEM` Use with available fluent helpers to apply the QuantityVariableSizeItem field to query operations.
`static SalesOrderBOMItemField<String>`	`REFERENCE_POINT` Use with available fluent helpers to apply the ReferencePoint field to query operations.
`static SalesOrderBOMItemField<Boolean>`	`REQUIRED_COMPONENT` Use with available fluent helpers to apply the RequiredComponent field to query operations.
`static SalesOrderBOMItemField<String>`	`RESULTING_ITEM_CATEGORY` Use with available fluent helpers to apply the ResultingItemCategory field to query operations.
`static SalesOrderBOMItemField<String>`	`SALES_ORDER` Use with available fluent helpers to apply the SalesOrder field to query operations.
`static SalesOrderBOMItemField<String>`	`SALES_ORDER_ITEM` Use with available fluent helpers to apply the SalesOrderItem field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`SIZE1` Use with available fluent helpers to apply the Size1 field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`SIZE2` Use with available fluent helpers to apply the Size2 field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`SIZE3` Use with available fluent helpers to apply the Size3 field to query operations.
`static SalesOrderBOMItemField<String>`	`SPECIAL_PROCUREMENT_TYPE` Use with available fluent helpers to apply the SpecialProcurementType field to query operations.
`static SalesOrderBOMItemOneToOneLink<SalesOrderBOM>`	`TO_BILL_OF_MATERIAL` Use with available fluent helpers to apply the to_BillOfMaterial navigation property to query operations.
`static SalesOrderBOMItemOneToOneLink<BOMItemCategory>`	`TO_BOM_ITEM_CATEGORY` Use with available fluent helpers to apply the to_BOMItemCategory navigation property to query operations.
`static SalesOrderBOMItemField<String>`	`UNIT_OF_MEASURE_FOR_SIZE1_TO3` Use with available fluent helpers to apply the UnitOfMeasureForSize1To3 field to query operations.
`static SalesOrderBOMItemField<BigDecimal>`	`USAGE_PROBABILITY_PERCENT` Use with available fluent helpers to apply the UsageProbabilityPercent field to query operations.
`static SalesOrderBOMItemField<LocalDateTime>`	`VALIDITY_END_DATE` Use with available fluent helpers to apply the ValidityEndDate field to query operations.
`static SalesOrderBOMItemField<LocalDateTime>`	`VALIDITY_START_DATE` Use with available fluent helpers to apply the ValidityStartDate field to query operations.

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
changedOriginalFields

Constructor Summary

Constructors
Constructor and Description
`SalesOrderBOMItem()`
SalesOrderBOMItem(String billOfMaterial, String billOfMaterialCategory, String billOfMaterialVariant, String billOfMaterialItemNodeNumber, String headerChangeDocument, String material, String plant, String billOfMaterialVariantUsage, UUID billOfMaterialItemUUID, String bOMItemInternalChangeCount, LocalDateTime validityStartDate, LocalDateTime validityEndDate, String engineeringChangeDocForEdit, String engineeringChangeDocument, String chgToEngineeringChgDocument, String inheritedNodeNumberForBOMItem, LocalDateTime bOMItemRecordCreationDate, String bOMItemCreatedByUser, LocalDateTime bOMItemLastChangeDate, String bOMItemLastChangedByUser, String billOfMaterialComponent, String billOfMaterialItemCategory, String billOfMaterialItemNumber, String billOfMaterialItemUnit, BigDecimal billOfMaterialItemQuantity, String isAssembly, Boolean isSubItem, String bOMItemSorter, Boolean fixedQuantity, Boolean bOMItemHasFixedQuantity, String purchasingGroup, String currency, BigDecimal materialComponentPrice, String identifierBOMItem, BigDecimal materialPriceUnitQty, BigDecimal componentScrapInPercent, BigDecimal operationScrapInPercent, Boolean isNetScrap, BigDecimal numberOfVariableSizeItem, BigDecimal quantityVariableSizeItem, String formulaKey, String componentDescription, String bOMItemDescription, String bOMItemText2, String materialGroup, String documentType, String docNumber, String documentVersion, String documentPart, String classNumber, String classType, String resultingItemCategory, String dependencyObjectNumber, String objectType, Boolean isClassificationRelevant, Boolean isBulkMaterial, String bOMItemIsSparePart, String bOMItemIsSalesRelevant, Boolean isProductionRelevant, Boolean bOMItemIsPlantMaintRelevant, String bOMItemIsCostingRelevant, Boolean isEngineeringRelevant, String specialProcurementType, Boolean isBOMRecursiveAllowed, BigDecimal operationLeadTimeOffset, String opsLeadTimeOffsetUnit, String isMaterialProvision, Boolean bOMIsRecursive, Boolean documentIsCreatedByCAD, String distrKeyCompConsumption, BigDecimal deliveryDurationInDays, String creditor, String costElement, BigDecimal size1, BigDecimal size2, BigDecimal size3, String unitOfMeasureForSize1To3, BigDecimal goodsReceiptDuration, String purchasingOrganization, Boolean requiredComponent, Boolean multipleSelectionAllowed, String prodOrderIssueLocation, Boolean materialIsCoProduct, String explosionType, String alternativeItemGroup, String alternativeItemPriority, String alternativeItemStrategy, BigDecimal usageProbabilityPercent, String followUpGroup, String discontinuationGroup, String isConfigurableBOM, String referencePoint, BigDecimal leadTimeOffset, String productionSupplyArea, Boolean isDeleted, Boolean isALE, ZonedDateTime lastChangeDateTime, String salesOrder, String salesOrderItem, SalesOrderBOM toBillOfMaterial, BOMItemCategory toBOMItemCategory)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static SalesOrderBOMItem.SalesOrderBOMItemBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`SalesOrderBOM`	`fetchBillOfMaterial()` Fetches the SalesOrderBOM entity (one to one) associated with this entity.
`BOMItemCategory`	`fetchBOMItemCategory()` Fetches the BOMItemCategory entity (one to one) associated with this entity.
`static <T> SalesOrderBOMItemField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> SalesOrderBOMItemField<T>`	`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)`
`String`	`getAlternativeItemGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getAlternativeItemPriority()` Constraints: Not nullable, Maximum length: 2
`String`	`getAlternativeItemStrategy()` Constraints: Not nullable, Maximum length: 1
`String`	`getBillOfMaterial()` (Key Field) Constraints: Not nullable, Maximum length: 8
`String`	`getBillOfMaterialCategory()` (Key Field) Constraints: Not nullable, Maximum length: 1
`String`	`getBillOfMaterialComponent()` Constraints: Not nullable, Maximum length: 40
`io.vavr.control.Option<SalesOrderBOM>`	`getBillOfMaterialIfPresent()` Retrieval of associated SalesOrderBOM entity (one to one).
`String`	`getBillOfMaterialItemCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getBillOfMaterialItemNodeNumber()` (Key Field) Constraints: Not nullable, Maximum length: 8
`String`	`getBillOfMaterialItemNumber()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getBillOfMaterialItemQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getBillOfMaterialItemUnit()` Constraints: Not nullable, Maximum length: 3
`UUID`	`getBillOfMaterialItemUUID()` Constraints: none
`SalesOrderBOM`	`getBillOfMaterialOrFetch()` Retrieval of associated SalesOrderBOM entity (one to one).
`String`	`getBillOfMaterialVariant()` (Key Field) Constraints: Not nullable, Maximum length: 2
`String`	`getBillOfMaterialVariantUsage()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getBOMIsRecursive()` Constraints: none
`io.vavr.control.Option<BOMItemCategory>`	`getBOMItemCategoryIfPresent()` Retrieval of associated BOMItemCategory entity (one to one).
`BOMItemCategory`	`getBOMItemCategoryOrFetch()` Retrieval of associated BOMItemCategory entity (one to one).
`String`	`getBOMItemCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`String`	`getBOMItemDescription()` Constraints: Not nullable, Maximum length: 40
`Boolean`	`getBOMItemHasFixedQuantity()` Constraints: none
`String`	`getBOMItemInternalChangeCount()` Constraints: Not nullable, Maximum length: 8
`String`	`getBOMItemIsCostingRelevant()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getBOMItemIsPlantMaintRelevant()` Constraints: none
`String`	`getBOMItemIsSalesRelevant()` Constraints: Not nullable, Maximum length: 1
`String`	`getBOMItemIsSparePart()` Constraints: Not nullable, Maximum length: 1
`LocalDateTime`	`getBOMItemLastChangeDate()` Constraints: Not nullable, Precision: 0
`String`	`getBOMItemLastChangedByUser()` Constraints: Not nullable, Maximum length: 12
`LocalDateTime`	`getBOMItemRecordCreationDate()` Constraints: Not nullable, Precision: 0
`String`	`getBOMItemSorter()` Constraints: Not nullable, Maximum length: 10
`String`	`getBOMItemText2()` Constraints: Not nullable, Maximum length: 40
`String`	`getChgToEngineeringChgDocument()` Constraints: Not nullable, Maximum length: 12
`String`	`getClassNumber()` Constraints: Not nullable, Maximum length: 18
`String`	`getClassType()` Constraints: Not nullable, Maximum length: 3
`String`	`getComponentDescription()` Constraints: Not nullable, Maximum length: 40
`BigDecimal`	`getComponentScrapInPercent()` Constraints: Not nullable, Precision: 5, Scale: 2
`String`	`getCostElement()` Constraints: Not nullable, Maximum length: 10
`String`	`getCreditor()` Constraints: Not nullable, Maximum length: 10
`String`	`getCurrency()` Constraints: Not nullable, Maximum length: 5
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`BigDecimal`	`getDeliveryDurationInDays()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getDependencyObjectNumber()` Constraints: Not nullable, Maximum length: 18
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`String`	`getDiscontinuationGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getDistrKeyCompConsumption()` Constraints: Not nullable, Maximum length: 4
`String`	`getDocNumber()` Constraints: Not nullable, Maximum length: 25
`Boolean`	`getDocumentIsCreatedByCAD()` Constraints: none
`String`	`getDocumentPart()` Constraints: Not nullable, Maximum length: 3
`String`	`getDocumentType()` Constraints: Not nullable, Maximum length: 3
`String`	`getDocumentVersion()` Constraints: Not nullable, Maximum length: 2
`String`	`getEngineeringChangeDocForEdit()` Constraints: Not nullable, Maximum length: 12
`String`	`getEngineeringChangeDocument()` Constraints: Not nullable, Maximum length: 12
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getExplosionType()` Constraints: Not nullable, Maximum length: 2
`Boolean`	`getFixedQuantity()` Constraints: none
`String`	`getFollowUpGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getFormulaKey()` Constraints: Not nullable, Maximum length: 2
`BigDecimal`	`getGoodsReceiptDuration()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getHeaderChangeDocument()` (Key Field) Constraints: Not nullable, Maximum length: 12
`String`	`getIdentifierBOMItem()` Constraints: Not nullable, Maximum length: 8
`String`	`getInheritedNodeNumberForBOMItem()` Constraints: Not nullable, Maximum length: 8
`Boolean`	`getIsALE()` Constraints: none
`String`	`getIsAssembly()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIsBOMRecursiveAllowed()` Constraints: none
`Boolean`	`getIsBulkMaterial()` Constraints: none
`Boolean`	`getIsClassificationRelevant()` Constraints: none
`String`	`getIsConfigurableBOM()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIsDeleted()` Constraints: none
`Boolean`	`getIsEngineeringRelevant()` Constraints: none
`String`	`getIsMaterialProvision()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIsNetScrap()` Constraints: none
`Boolean`	`getIsProductionRelevant()` Constraints: none
`Boolean`	`getIsSubItem()` Constraints: none
`protected Map<String,Object>`	`getKey()`
`ZonedDateTime`	`getLastChangeDateTime()` Constraints: Not nullable, Precision: 7
`BigDecimal`	`getLeadTimeOffset()` Constraints: Not nullable, Precision: 3, Scale: 0
`String`	`getMaterial()` (Key Field) Constraints: Not nullable, Maximum length: 40
`BigDecimal`	`getMaterialComponentPrice()` Constraints: Not nullable, Precision: 12, Scale: 3
`String`	`getMaterialGroup()` Constraints: Not nullable, Maximum length: 9
`Boolean`	`getMaterialIsCoProduct()` Constraints: none
`BigDecimal`	`getMaterialPriceUnitQty()` Constraints: Not nullable, Precision: 5, Scale: 0
`Boolean`	`getMultipleSelectionAllowed()` Constraints: none
`BigDecimal`	`getNumberOfVariableSizeItem()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getObjectType()` Constraints: Not nullable, Maximum length: 1
`BigDecimal`	`getOperationLeadTimeOffset()` Constraints: Not nullable, Precision: 3, Scale: 0
`BigDecimal`	`getOperationScrapInPercent()` Constraints: Not nullable, Precision: 5, Scale: 2
`String`	`getOpsLeadTimeOffsetUnit()` Constraints: Not nullable, Maximum length: 3
`String`	`getPlant()` (Key Field) Constraints: Not nullable, Maximum length: 4
`String`	`getProdOrderIssueLocation()` Constraints: Not nullable, Maximum length: 4
`String`	`getProductionSupplyArea()` Constraints: Not nullable, Maximum length: 10
`String`	`getPurchasingGroup()` Constraints: Not nullable, Maximum length: 3
`String`	`getPurchasingOrganization()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getQuantityVariableSizeItem()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getReferencePoint()` Constraints: Not nullable, Maximum length: 20
`Boolean`	`getRequiredComponent()` Constraints: none
`String`	`getResultingItemCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getSalesOrder()` Constraints: Not nullable, Maximum length: 10
`String`	`getSalesOrderItem()` Constraints: Not nullable, Maximum length: 6
`BigDecimal`	`getSize1()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getSize2()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getSize3()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getSpecialProcurementType()` Constraints: Not nullable, Maximum length: 2
`Class<SalesOrderBOMItem>`	`getType()`
`String`	`getUnitOfMeasureForSize1To3()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getUsageProbabilityPercent()` Constraints: Not nullable, Precision: 3, Scale: 0
`LocalDateTime`	`getValidityEndDate()` Constraints: Not nullable, Precision: 0
`LocalDateTime`	`getValidityStartDate()` Constraints: Not nullable, Precision: 0
`int`	`hashCode()`
`void`	`setAlternativeItemGroup(String alternativeItemGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setAlternativeItemPriority(String alternativeItemPriority)` Constraints: Not nullable, Maximum length: 2
`void`	`setAlternativeItemStrategy(String alternativeItemStrategy)` Constraints: Not nullable, Maximum length: 1
`void`	`setBillOfMaterial(SalesOrderBOM value)` Overwrites the associated SalesOrderBOM entity for the loaded navigation property to_BillOfMaterial.
`void`	`setBillOfMaterial(String billOfMaterial)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setBillOfMaterialCategory(String billOfMaterialCategory)` (Key Field) Constraints: Not nullable, Maximum length: 1
`void`	`setBillOfMaterialComponent(String billOfMaterialComponent)` Constraints: Not nullable, Maximum length: 40
`void`	`setBillOfMaterialItemCategory(String billOfMaterialItemCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setBillOfMaterialItemNodeNumber(String billOfMaterialItemNodeNumber)` (Key Field) Constraints: Not nullable, Maximum length: 8
`void`	`setBillOfMaterialItemNumber(String billOfMaterialItemNumber)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillOfMaterialItemQuantity(BigDecimal billOfMaterialItemQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBillOfMaterialItemUnit(String billOfMaterialItemUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setBillOfMaterialItemUUID(UUID billOfMaterialItemUUID)` Constraints: none
`void`	`setBillOfMaterialVariant(String billOfMaterialVariant)` (Key Field) Constraints: Not nullable, Maximum length: 2
`void`	`setBillOfMaterialVariantUsage(String billOfMaterialVariantUsage)` Constraints: Not nullable, Maximum length: 1
`void`	`setBOMIsRecursive(Boolean bOMIsRecursive)` Constraints: none
`void`	`setBOMItemCategory(BOMItemCategory value)` Overwrites the associated BOMItemCategory entity for the loaded navigation property to_BOMItemCategory.
`void`	`setBOMItemCreatedByUser(String bOMItemCreatedByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setBOMItemDescription(String bOMItemDescription)` Constraints: Not nullable, Maximum length: 40
`void`	`setBOMItemHasFixedQuantity(Boolean bOMItemHasFixedQuantity)` Constraints: none
`void`	`setBOMItemInternalChangeCount(String bOMItemInternalChangeCount)` Constraints: Not nullable, Maximum length: 8
`void`	`setBOMItemIsCostingRelevant(String bOMItemIsCostingRelevant)` Constraints: Not nullable, Maximum length: 1
`void`	`setBOMItemIsPlantMaintRelevant(Boolean bOMItemIsPlantMaintRelevant)` Constraints: none
`void`	`setBOMItemIsSalesRelevant(String bOMItemIsSalesRelevant)` Constraints: Not nullable, Maximum length: 1
`void`	`setBOMItemIsSparePart(String bOMItemIsSparePart)` Constraints: Not nullable, Maximum length: 1
`void`	`setBOMItemLastChangeDate(LocalDateTime bOMItemLastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setBOMItemLastChangedByUser(String bOMItemLastChangedByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setBOMItemRecordCreationDate(LocalDateTime bOMItemRecordCreationDate)` Constraints: Not nullable, Precision: 0
`void`	`setBOMItemSorter(String bOMItemSorter)` Constraints: Not nullable, Maximum length: 10
`void`	`setBOMItemText2(String bOMItemText2)` Constraints: Not nullable, Maximum length: 40
`void`	`setChgToEngineeringChgDocument(String chgToEngineeringChgDocument)` Constraints: Not nullable, Maximum length: 12
`void`	`setClassNumber(String classNumber)` Constraints: Not nullable, Maximum length: 18
`void`	`setClassType(String classType)` Constraints: Not nullable, Maximum length: 3
`void`	`setComponentDescription(String componentDescription)` Constraints: Not nullable, Maximum length: 40
`void`	`setComponentScrapInPercent(BigDecimal componentScrapInPercent)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setCostElement(String costElement)` Constraints: Not nullable, Maximum length: 10
`void`	`setCreditor(String creditor)` Constraints: Not nullable, Maximum length: 10
`void`	`setCurrency(String currency)` Constraints: Not nullable, Maximum length: 5
`void`	`setDeliveryDurationInDays(BigDecimal deliveryDurationInDays)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setDependencyObjectNumber(String dependencyObjectNumber)` Constraints: Not nullable, Maximum length: 18
`void`	`setDiscontinuationGroup(String discontinuationGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setDistrKeyCompConsumption(String distrKeyCompConsumption)` Constraints: Not nullable, Maximum length: 4
`void`	`setDocNumber(String docNumber)` Constraints: Not nullable, Maximum length: 25
`void`	`setDocumentIsCreatedByCAD(Boolean documentIsCreatedByCAD)` Constraints: none
`void`	`setDocumentPart(String documentPart)` Constraints: Not nullable, Maximum length: 3
`void`	`setDocumentType(String documentType)` Constraints: Not nullable, Maximum length: 3
`void`	`setDocumentVersion(String documentVersion)` Constraints: Not nullable, Maximum length: 2
`void`	`setEngineeringChangeDocForEdit(String engineeringChangeDocForEdit)` Constraints: Not nullable, Maximum length: 12
`void`	`setEngineeringChangeDocument(String engineeringChangeDocument)` Constraints: Not nullable, Maximum length: 12
`void`	`setExplosionType(String explosionType)` Constraints: Not nullable, Maximum length: 2
`void`	`setFixedQuantity(Boolean fixedQuantity)` Constraints: none
`void`	`setFollowUpGroup(String followUpGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setFormulaKey(String formulaKey)` Constraints: Not nullable, Maximum length: 2
`void`	`setGoodsReceiptDuration(BigDecimal goodsReceiptDuration)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setHeaderChangeDocument(String headerChangeDocument)` (Key Field) Constraints: Not nullable, Maximum length: 12
`void`	`setIdentifierBOMItem(String identifierBOMItem)` Constraints: Not nullable, Maximum length: 8
`void`	`setInheritedNodeNumberForBOMItem(String inheritedNodeNumberForBOMItem)` Constraints: Not nullable, Maximum length: 8
`void`	`setIsALE(Boolean isALE)` Constraints: none
`void`	`setIsAssembly(String isAssembly)` Constraints: Not nullable, Maximum length: 1
`void`	`setIsBOMRecursiveAllowed(Boolean isBOMRecursiveAllowed)` Constraints: none
`void`	`setIsBulkMaterial(Boolean isBulkMaterial)` Constraints: none
`void`	`setIsClassificationRelevant(Boolean isClassificationRelevant)` Constraints: none
`void`	`setIsConfigurableBOM(String isConfigurableBOM)` Constraints: Not nullable, Maximum length: 1
`void`	`setIsDeleted(Boolean isDeleted)` Constraints: none
`void`	`setIsEngineeringRelevant(Boolean isEngineeringRelevant)` Constraints: none
`void`	`setIsMaterialProvision(String isMaterialProvision)` Constraints: Not nullable, Maximum length: 1
`void`	`setIsNetScrap(Boolean isNetScrap)` Constraints: none
`void`	`setIsProductionRelevant(Boolean isProductionRelevant)` Constraints: none
`void`	`setIsSubItem(Boolean isSubItem)` Constraints: none
`void`	`setLastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`void`	`setLeadTimeOffset(BigDecimal leadTimeOffset)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setMaterial(String material)` (Key Field) Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialComponentPrice(BigDecimal materialComponentPrice)` Constraints: Not nullable, Precision: 12, Scale: 3
`void`	`setMaterialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9
`void`	`setMaterialIsCoProduct(Boolean materialIsCoProduct)` Constraints: none
`void`	`setMaterialPriceUnitQty(BigDecimal materialPriceUnitQty)` Constraints: Not nullable, Precision: 5, Scale: 0
`void`	`setMultipleSelectionAllowed(Boolean multipleSelectionAllowed)` Constraints: none
`void`	`setNumberOfVariableSizeItem(BigDecimal numberOfVariableSizeItem)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setObjectType(String objectType)` Constraints: Not nullable, Maximum length: 1
`void`	`setOperationLeadTimeOffset(BigDecimal operationLeadTimeOffset)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setOperationScrapInPercent(BigDecimal operationScrapInPercent)` Constraints: Not nullable, Precision: 5, Scale: 2
`void`	`setOpsLeadTimeOffsetUnit(String opsLeadTimeOffsetUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setPlant(String plant)` (Key Field) Constraints: Not nullable, Maximum length: 4
`void`	`setProdOrderIssueLocation(String prodOrderIssueLocation)` Constraints: Not nullable, Maximum length: 4
`void`	`setProductionSupplyArea(String productionSupplyArea)` Constraints: Not nullable, Maximum length: 10
`void`	`setPurchasingGroup(String purchasingGroup)` Constraints: Not nullable, Maximum length: 3
`void`	`setPurchasingOrganization(String purchasingOrganization)` Constraints: Not nullable, Maximum length: 4
`void`	`setQuantityVariableSizeItem(BigDecimal quantityVariableSizeItem)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setReferencePoint(String referencePoint)` Constraints: Not nullable, Maximum length: 20
`void`	`setRequiredComponent(Boolean requiredComponent)` Constraints: none
`void`	`setResultingItemCategory(String resultingItemCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setSalesOrder(String salesOrder)` Constraints: Not nullable, Maximum length: 10
`void`	`setSalesOrderItem(String salesOrderItem)` Constraints: Not nullable, Maximum length: 6
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setSize1(BigDecimal size1)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSize2(BigDecimal size2)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSize3(BigDecimal size3)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setSpecialProcurementType(String specialProcurementType)` Constraints: Not nullable, Maximum length: 2
`void`	`setUnitOfMeasureForSize1To3(String unitOfMeasureForSize1To3)` Constraints: Not nullable, Maximum length: 3
`void`	`setUsageProbabilityPercent(BigDecimal usageProbabilityPercent)` Constraints: Not nullable, Precision: 3, Scale: 0
`void`	`setValidityEndDate(LocalDateTime validityEndDate)` Constraints: Not nullable, Precision: 0
`void`	`setValidityStartDate(LocalDateTime validityStartDate)` Constraints: Not nullable, Precision: 0
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields

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

- Field Detail
  - ALL_FIELDS
```
public static final SalesOrderBOMItemSelectable ALL_FIELDS
```
    Selector for all available fields of SalesOrderBOMItem.
  - BILL_OF_MATERIAL
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL
```
    Use with available fluent helpers to apply the BillOfMaterial field to query operations.
  - BILL_OF_MATERIAL_CATEGORY
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_CATEGORY
```
    Use with available fluent helpers to apply the BillOfMaterialCategory field to query operations.
  - BILL_OF_MATERIAL_VARIANT
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_VARIANT
```
    Use with available fluent helpers to apply the BillOfMaterialVariant field to query operations.
  - BILL_OF_MATERIAL_ITEM_NODE_NUMBER
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_ITEM_NODE_NUMBER
```
    Use with available fluent helpers to apply the BillOfMaterialItemNodeNumber field to query operations.
  - HEADER_CHANGE_DOCUMENT
```
public static final SalesOrderBOMItemField<String> HEADER_CHANGE_DOCUMENT
```
    Use with available fluent helpers to apply the HeaderChangeDocument field to query operations.
  - MATERIAL
```
public static final SalesOrderBOMItemField<String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - PLANT
```
public static final SalesOrderBOMItemField<String> PLANT
```
    Use with available fluent helpers to apply the Plant field to query operations.
  - BILL_OF_MATERIAL_VARIANT_USAGE
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_VARIANT_USAGE
```
    Use with available fluent helpers to apply the BillOfMaterialVariantUsage field to query operations.
  - BILL_OF_MATERIAL_ITEM_UUID
```
public static final SalesOrderBOMItemField<UUID> BILL_OF_MATERIAL_ITEM_UUID
```
    Use with available fluent helpers to apply the BillOfMaterialItemUUID field to query operations.
  - BOM_ITEM_INTERNAL_CHANGE_COUNT
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_INTERNAL_CHANGE_COUNT
```
    Use with available fluent helpers to apply the BOMItemInternalChangeCount field to query operations.
  - VALIDITY_START_DATE
```
public static final SalesOrderBOMItemField<LocalDateTime> VALIDITY_START_DATE
```
    Use with available fluent helpers to apply the ValidityStartDate field to query operations.
  - VALIDITY_END_DATE
```
public static final SalesOrderBOMItemField<LocalDateTime> VALIDITY_END_DATE
```
    Use with available fluent helpers to apply the ValidityEndDate field to query operations.
  - ENGINEERING_CHANGE_DOC_FOR_EDIT
```
public static final SalesOrderBOMItemField<String> ENGINEERING_CHANGE_DOC_FOR_EDIT
```
    Use with available fluent helpers to apply the EngineeringChangeDocForEdit field to query operations.
  - ENGINEERING_CHANGE_DOCUMENT
```
public static final SalesOrderBOMItemField<String> ENGINEERING_CHANGE_DOCUMENT
```
    Use with available fluent helpers to apply the EngineeringChangeDocument field to query operations.
  - CHG_TO_ENGINEERING_CHG_DOCUMENT
```
public static final SalesOrderBOMItemField<String> CHG_TO_ENGINEERING_CHG_DOCUMENT
```
    Use with available fluent helpers to apply the ChgToEngineeringChgDocument field to query operations.
  - INHERITED_NODE_NUMBER_FOR_BOM_ITEM
```
public static final SalesOrderBOMItemField<String> INHERITED_NODE_NUMBER_FOR_BOM_ITEM
```
    Use with available fluent helpers to apply the InheritedNodeNumberForBOMItem field to query operations.
  - BOM_ITEM_RECORD_CREATION_DATE
```
public static final SalesOrderBOMItemField<LocalDateTime> BOM_ITEM_RECORD_CREATION_DATE
```
    Use with available fluent helpers to apply the BOMItemRecordCreationDate field to query operations.
  - BOM_ITEM_CREATED_BY_USER
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_CREATED_BY_USER
```
    Use with available fluent helpers to apply the BOMItemCreatedByUser field to query operations.
  - BOM_ITEM_LAST_CHANGE_DATE
```
public static final SalesOrderBOMItemField<LocalDateTime> BOM_ITEM_LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the BOMItemLastChangeDate field to query operations.
  - BOM_ITEM_LAST_CHANGED_BY_USER
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_LAST_CHANGED_BY_USER
```
    Use with available fluent helpers to apply the BOMItemLastChangedByUser field to query operations.
  - BILL_OF_MATERIAL_COMPONENT
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_COMPONENT
```
    Use with available fluent helpers to apply the BillOfMaterialComponent field to query operations.
  - BILL_OF_MATERIAL_ITEM_CATEGORY
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the BillOfMaterialItemCategory field to query operations.
  - BILL_OF_MATERIAL_ITEM_NUMBER
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_ITEM_NUMBER
```
    Use with available fluent helpers to apply the BillOfMaterialItemNumber field to query operations.
  - BILL_OF_MATERIAL_ITEM_UNIT
```
public static final SalesOrderBOMItemField<String> BILL_OF_MATERIAL_ITEM_UNIT
```
    Use with available fluent helpers to apply the BillOfMaterialItemUnit field to query operations.
  - BILL_OF_MATERIAL_ITEM_QUANTITY
```
public static final SalesOrderBOMItemField<BigDecimal> BILL_OF_MATERIAL_ITEM_QUANTITY
```
    Use with available fluent helpers to apply the BillOfMaterialItemQuantity field to query operations.
  - IS_ASSEMBLY
```
public static final SalesOrderBOMItemField<String> IS_ASSEMBLY
```
    Use with available fluent helpers to apply the IsAssembly field to query operations.
  - IS_SUB_ITEM
```
public static final SalesOrderBOMItemField<Boolean> IS_SUB_ITEM
```
    Use with available fluent helpers to apply the IsSubItem field to query operations.
  - BOM_ITEM_SORTER
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_SORTER
```
    Use with available fluent helpers to apply the BOMItemSorter field to query operations.
  - FIXED_QUANTITY
```
public static final SalesOrderBOMItemField<Boolean> FIXED_QUANTITY
```
    Use with available fluent helpers to apply the FixedQuantity field to query operations.
  - BOM_ITEM_HAS_FIXED_QUANTITY
```
public static final SalesOrderBOMItemField<Boolean> BOM_ITEM_HAS_FIXED_QUANTITY
```
    Use with available fluent helpers to apply the BOMItemHasFixedQuantity field to query operations.
  - PURCHASING_GROUP
```
public static final SalesOrderBOMItemField<String> PURCHASING_GROUP
```
    Use with available fluent helpers to apply the PurchasingGroup field to query operations.
  - CURRENCY
```
public static final SalesOrderBOMItemField<String> CURRENCY
```
    Use with available fluent helpers to apply the Currency field to query operations.
  - MATERIAL_COMPONENT_PRICE
```
public static final SalesOrderBOMItemField<BigDecimal> MATERIAL_COMPONENT_PRICE
```
    Use with available fluent helpers to apply the MaterialComponentPrice field to query operations.
  - IDENTIFIER_BOM_ITEM
```
public static final SalesOrderBOMItemField<String> IDENTIFIER_BOM_ITEM
```
    Use with available fluent helpers to apply the IdentifierBOMItem field to query operations.
  - MATERIAL_PRICE_UNIT_QTY
```
public static final SalesOrderBOMItemField<BigDecimal> MATERIAL_PRICE_UNIT_QTY
```
    Use with available fluent helpers to apply the MaterialPriceUnitQty field to query operations.
  - COMPONENT_SCRAP_IN_PERCENT
```
public static final SalesOrderBOMItemField<BigDecimal> COMPONENT_SCRAP_IN_PERCENT
```
    Use with available fluent helpers to apply the ComponentScrapInPercent field to query operations.
  - OPERATION_SCRAP_IN_PERCENT
```
public static final SalesOrderBOMItemField<BigDecimal> OPERATION_SCRAP_IN_PERCENT
```
    Use with available fluent helpers to apply the OperationScrapInPercent field to query operations.
  - IS_NET_SCRAP
```
public static final SalesOrderBOMItemField<Boolean> IS_NET_SCRAP
```
    Use with available fluent helpers to apply the IsNetScrap field to query operations.
  - NUMBER_OF_VARIABLE_SIZE_ITEM
```
public static final SalesOrderBOMItemField<BigDecimal> NUMBER_OF_VARIABLE_SIZE_ITEM
```
    Use with available fluent helpers to apply the NumberOfVariableSizeItem field to query operations.
  - QUANTITY_VARIABLE_SIZE_ITEM
```
public static final SalesOrderBOMItemField<BigDecimal> QUANTITY_VARIABLE_SIZE_ITEM
```
    Use with available fluent helpers to apply the QuantityVariableSizeItem field to query operations.
  - FORMULA_KEY
```
public static final SalesOrderBOMItemField<String> FORMULA_KEY
```
    Use with available fluent helpers to apply the FormulaKey field to query operations.
  - COMPONENT_DESCRIPTION
```
public static final SalesOrderBOMItemField<String> COMPONENT_DESCRIPTION
```
    Use with available fluent helpers to apply the ComponentDescription field to query operations.
  - BOM_ITEM_DESCRIPTION
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_DESCRIPTION
```
    Use with available fluent helpers to apply the BOMItemDescription field to query operations.
  - BOM_ITEM_TEXT2
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_TEXT2
```
    Use with available fluent helpers to apply the BOMItemText2 field to query operations.
  - MATERIAL_GROUP
```
public static final SalesOrderBOMItemField<String> MATERIAL_GROUP
```
    Use with available fluent helpers to apply the MaterialGroup field to query operations.
  - DOCUMENT_TYPE
```
public static final SalesOrderBOMItemField<String> DOCUMENT_TYPE
```
    Use with available fluent helpers to apply the DocumentType field to query operations.
  - DOC_NUMBER
```
public static final SalesOrderBOMItemField<String> DOC_NUMBER
```
    Use with available fluent helpers to apply the DocNumber field to query operations.
  - DOCUMENT_VERSION
```
public static final SalesOrderBOMItemField<String> DOCUMENT_VERSION
```
    Use with available fluent helpers to apply the DocumentVersion field to query operations.
  - DOCUMENT_PART
```
public static final SalesOrderBOMItemField<String> DOCUMENT_PART
```
    Use with available fluent helpers to apply the DocumentPart field to query operations.
  - CLASS_NUMBER
```
public static final SalesOrderBOMItemField<String> CLASS_NUMBER
```
    Use with available fluent helpers to apply the ClassNumber field to query operations.
  - CLASS_TYPE
```
public static final SalesOrderBOMItemField<String> CLASS_TYPE
```
    Use with available fluent helpers to apply the ClassType field to query operations.
  - RESULTING_ITEM_CATEGORY
```
public static final SalesOrderBOMItemField<String> RESULTING_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the ResultingItemCategory field to query operations.
  - DEPENDENCY_OBJECT_NUMBER
```
public static final SalesOrderBOMItemField<String> DEPENDENCY_OBJECT_NUMBER
```
    Use with available fluent helpers to apply the DependencyObjectNumber field to query operations.
  - OBJECT_TYPE
```
public static final SalesOrderBOMItemField<String> OBJECT_TYPE
```
    Use with available fluent helpers to apply the ObjectType field to query operations.
  - IS_CLASSIFICATION_RELEVANT
```
public static final SalesOrderBOMItemField<Boolean> IS_CLASSIFICATION_RELEVANT
```
    Use with available fluent helpers to apply the IsClassificationRelevant field to query operations.
  - IS_BULK_MATERIAL
```
public static final SalesOrderBOMItemField<Boolean> IS_BULK_MATERIAL
```
    Use with available fluent helpers to apply the IsBulkMaterial field to query operations.
  - BOM_ITEM_IS_SPARE_PART
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_IS_SPARE_PART
```
    Use with available fluent helpers to apply the BOMItemIsSparePart field to query operations.
  - BOM_ITEM_IS_SALES_RELEVANT
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_IS_SALES_RELEVANT
```
    Use with available fluent helpers to apply the BOMItemIsSalesRelevant field to query operations.
  - IS_PRODUCTION_RELEVANT
```
public static final SalesOrderBOMItemField<Boolean> IS_PRODUCTION_RELEVANT
```
    Use with available fluent helpers to apply the IsProductionRelevant field to query operations.
  - BOM_ITEM_IS_PLANT_MAINT_RELEVANT
```
public static final SalesOrderBOMItemField<Boolean> BOM_ITEM_IS_PLANT_MAINT_RELEVANT
```
    Use with available fluent helpers to apply the BOMItemIsPlantMaintRelevant field to query operations.
  - BOM_ITEM_IS_COSTING_RELEVANT
```
public static final SalesOrderBOMItemField<String> BOM_ITEM_IS_COSTING_RELEVANT
```
    Use with available fluent helpers to apply the BOMItemIsCostingRelevant field to query operations.
  - IS_ENGINEERING_RELEVANT
```
public static final SalesOrderBOMItemField<Boolean> IS_ENGINEERING_RELEVANT
```
    Use with available fluent helpers to apply the IsEngineeringRelevant field to query operations.
  - SPECIAL_PROCUREMENT_TYPE
```
public static final SalesOrderBOMItemField<String> SPECIAL_PROCUREMENT_TYPE
```
    Use with available fluent helpers to apply the SpecialProcurementType field to query operations.
  - IS_BOM_RECURSIVE_ALLOWED
```
public static final SalesOrderBOMItemField<Boolean> IS_BOM_RECURSIVE_ALLOWED
```
    Use with available fluent helpers to apply the IsBOMRecursiveAllowed field to query operations.
  - OPERATION_LEAD_TIME_OFFSET
```
public static final SalesOrderBOMItemField<BigDecimal> OPERATION_LEAD_TIME_OFFSET
```
    Use with available fluent helpers to apply the OperationLeadTimeOffset field to query operations.
  - OPS_LEAD_TIME_OFFSET_UNIT
```
public static final SalesOrderBOMItemField<String> OPS_LEAD_TIME_OFFSET_UNIT
```
    Use with available fluent helpers to apply the OpsLeadTimeOffsetUnit field to query operations.
  - IS_MATERIAL_PROVISION
```
public static final SalesOrderBOMItemField<String> IS_MATERIAL_PROVISION
```
    Use with available fluent helpers to apply the IsMaterialProvision field to query operations.
  - BOM_IS_RECURSIVE
```
public static final SalesOrderBOMItemField<Boolean> BOM_IS_RECURSIVE
```
    Use with available fluent helpers to apply the BOMIsRecursive field to query operations.
  - DOCUMENT_IS_CREATED_BY_CAD
```
public static final SalesOrderBOMItemField<Boolean> DOCUMENT_IS_CREATED_BY_CAD
```
    Use with available fluent helpers to apply the DocumentIsCreatedByCAD field to query operations.
  - DISTR_KEY_COMP_CONSUMPTION
```
public static final SalesOrderBOMItemField<String> DISTR_KEY_COMP_CONSUMPTION
```
    Use with available fluent helpers to apply the DistrKeyCompConsumption field to query operations.
  - DELIVERY_DURATION_IN_DAYS
```
public static final SalesOrderBOMItemField<BigDecimal> DELIVERY_DURATION_IN_DAYS
```
    Use with available fluent helpers to apply the DeliveryDurationInDays field to query operations.
  - CREDITOR
```
public static final SalesOrderBOMItemField<String> CREDITOR
```
    Use with available fluent helpers to apply the Creditor field to query operations.
  - COST_ELEMENT
```
public static final SalesOrderBOMItemField<String> COST_ELEMENT
```
    Use with available fluent helpers to apply the CostElement field to query operations.
  - SIZE1
```
public static final SalesOrderBOMItemField<BigDecimal> SIZE1
```
    Use with available fluent helpers to apply the Size1 field to query operations.
  - SIZE2
```
public static final SalesOrderBOMItemField<BigDecimal> SIZE2
```
    Use with available fluent helpers to apply the Size2 field to query operations.
  - SIZE3
```
public static final SalesOrderBOMItemField<BigDecimal> SIZE3
```
    Use with available fluent helpers to apply the Size3 field to query operations.
  - UNIT_OF_MEASURE_FOR_SIZE1_TO3
```
public static final SalesOrderBOMItemField<String> UNIT_OF_MEASURE_FOR_SIZE1_TO3
```
    Use with available fluent helpers to apply the UnitOfMeasureForSize1To3 field to query operations.
  - GOODS_RECEIPT_DURATION
```
public static final SalesOrderBOMItemField<BigDecimal> GOODS_RECEIPT_DURATION
```
    Use with available fluent helpers to apply the GoodsReceiptDuration field to query operations.
  - PURCHASING_ORGANIZATION
```
public static final SalesOrderBOMItemField<String> PURCHASING_ORGANIZATION
```
    Use with available fluent helpers to apply the PurchasingOrganization field to query operations.
  - REQUIRED_COMPONENT
```
public static final SalesOrderBOMItemField<Boolean> REQUIRED_COMPONENT
```
    Use with available fluent helpers to apply the RequiredComponent field to query operations.
  - MULTIPLE_SELECTION_ALLOWED
```
public static final SalesOrderBOMItemField<Boolean> MULTIPLE_SELECTION_ALLOWED
```
    Use with available fluent helpers to apply the MultipleSelectionAllowed field to query operations.
  - PROD_ORDER_ISSUE_LOCATION
```
public static final SalesOrderBOMItemField<String> PROD_ORDER_ISSUE_LOCATION
```
    Use with available fluent helpers to apply the ProdOrderIssueLocation field to query operations.
  - MATERIAL_IS_CO_PRODUCT
```
public static final SalesOrderBOMItemField<Boolean> MATERIAL_IS_CO_PRODUCT
```
    Use with available fluent helpers to apply the MaterialIsCoProduct field to query operations.
  - EXPLOSION_TYPE
```
public static final SalesOrderBOMItemField<String> EXPLOSION_TYPE
```
    Use with available fluent helpers to apply the ExplosionType field to query operations.
  - ALTERNATIVE_ITEM_GROUP
```
public static final SalesOrderBOMItemField<String> ALTERNATIVE_ITEM_GROUP
```
    Use with available fluent helpers to apply the AlternativeItemGroup field to query operations.
  - ALTERNATIVE_ITEM_PRIORITY
```
public static final SalesOrderBOMItemField<String> ALTERNATIVE_ITEM_PRIORITY
```
    Use with available fluent helpers to apply the AlternativeItemPriority field to query operations.
  - ALTERNATIVE_ITEM_STRATEGY
```
public static final SalesOrderBOMItemField<String> ALTERNATIVE_ITEM_STRATEGY
```
    Use with available fluent helpers to apply the AlternativeItemStrategy field to query operations.
  - USAGE_PROBABILITY_PERCENT
```
public static final SalesOrderBOMItemField<BigDecimal> USAGE_PROBABILITY_PERCENT
```
    Use with available fluent helpers to apply the UsageProbabilityPercent field to query operations.
  - FOLLOW_UP_GROUP
```
public static final SalesOrderBOMItemField<String> FOLLOW_UP_GROUP
```
    Use with available fluent helpers to apply the FollowUpGroup field to query operations.
  - DISCONTINUATION_GROUP
```
public static final SalesOrderBOMItemField<String> DISCONTINUATION_GROUP
```
    Use with available fluent helpers to apply the DiscontinuationGroup field to query operations.
  - IS_CONFIGURABLE_BOM
```
public static final SalesOrderBOMItemField<String> IS_CONFIGURABLE_BOM
```
    Use with available fluent helpers to apply the IsConfigurableBOM field to query operations.
  - REFERENCE_POINT
```
public static final SalesOrderBOMItemField<String> REFERENCE_POINT
```
    Use with available fluent helpers to apply the ReferencePoint field to query operations.
  - LEAD_TIME_OFFSET
```
public static final SalesOrderBOMItemField<BigDecimal> LEAD_TIME_OFFSET
```
    Use with available fluent helpers to apply the LeadTimeOffset field to query operations.
  - PRODUCTION_SUPPLY_AREA
```
public static final SalesOrderBOMItemField<String> PRODUCTION_SUPPLY_AREA
```
    Use with available fluent helpers to apply the ProductionSupplyArea field to query operations.
  - IS_DELETED
```
public static final SalesOrderBOMItemField<Boolean> IS_DELETED
```
    Use with available fluent helpers to apply the IsDeleted field to query operations.
  - IS_ALE
```
public static final SalesOrderBOMItemField<Boolean> IS_ALE
```
    Use with available fluent helpers to apply the IsALE field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final SalesOrderBOMItemField<ZonedDateTime> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - SALES_ORDER
```
public static final SalesOrderBOMItemField<String> SALES_ORDER
```
    Use with available fluent helpers to apply the SalesOrder field to query operations.
  - SALES_ORDER_ITEM
```
public static final SalesOrderBOMItemField<String> SALES_ORDER_ITEM
```
    Use with available fluent helpers to apply the SalesOrderItem field to query operations.
  - TO_BILL_OF_MATERIAL
```
public static final SalesOrderBOMItemOneToOneLink<SalesOrderBOM> TO_BILL_OF_MATERIAL
```
    Use with available fluent helpers to apply the to_BillOfMaterial navigation property to query operations.
  - TO_BOM_ITEM_CATEGORY
```
public static final SalesOrderBOMItemOneToOneLink<BOMItemCategory> TO_BOM_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the to_BOMItemCategory navigation property to query operations.
- Constructor Detail
  - SalesOrderBOMItem
```
public SalesOrderBOMItem()
```
  - SalesOrderBOMItem
```
public SalesOrderBOMItem(@Nullable
                         String billOfMaterial,
                         @Nullable
                         String billOfMaterialCategory,
                         @Nullable
                         String billOfMaterialVariant,
                         @Nullable
                         String billOfMaterialItemNodeNumber,
                         @Nullable
                         String headerChangeDocument,
                         @Nullable
                         String material,
                         @Nullable
                         String plant,
                         @Nullable
                         String billOfMaterialVariantUsage,
                         @Nullable
                         UUID billOfMaterialItemUUID,
                         @Nullable
                         String bOMItemInternalChangeCount,
                         @Nullable
                         LocalDateTime validityStartDate,
                         @Nullable
                         LocalDateTime validityEndDate,
                         @Nullable
                         String engineeringChangeDocForEdit,
                         @Nullable
                         String engineeringChangeDocument,
                         @Nullable
                         String chgToEngineeringChgDocument,
                         @Nullable
                         String inheritedNodeNumberForBOMItem,
                         @Nullable
                         LocalDateTime bOMItemRecordCreationDate,
                         @Nullable
                         String bOMItemCreatedByUser,
                         @Nullable
                         LocalDateTime bOMItemLastChangeDate,
                         @Nullable
                         String bOMItemLastChangedByUser,
                         @Nullable
                         String billOfMaterialComponent,
                         @Nullable
                         String billOfMaterialItemCategory,
                         @Nullable
                         String billOfMaterialItemNumber,
                         @Nullable
                         String billOfMaterialItemUnit,
                         @Nullable
                         BigDecimal billOfMaterialItemQuantity,
                         @Nullable
                         String isAssembly,
                         @Nullable
                         Boolean isSubItem,
                         @Nullable
                         String bOMItemSorter,
                         @Nullable
                         Boolean fixedQuantity,
                         @Nullable
                         Boolean bOMItemHasFixedQuantity,
                         @Nullable
                         String purchasingGroup,
                         @Nullable
                         String currency,
                         @Nullable
                         BigDecimal materialComponentPrice,
                         @Nullable
                         String identifierBOMItem,
                         @Nullable
                         BigDecimal materialPriceUnitQty,
                         @Nullable
                         BigDecimal componentScrapInPercent,
                         @Nullable
                         BigDecimal operationScrapInPercent,
                         @Nullable
                         Boolean isNetScrap,
                         @Nullable
                         BigDecimal numberOfVariableSizeItem,
                         @Nullable
                         BigDecimal quantityVariableSizeItem,
                         @Nullable
                         String formulaKey,
                         @Nullable
                         String componentDescription,
                         @Nullable
                         String bOMItemDescription,
                         @Nullable
                         String bOMItemText2,
                         @Nullable
                         String materialGroup,
                         @Nullable
                         String documentType,
                         @Nullable
                         String docNumber,
                         @Nullable
                         String documentVersion,
                         @Nullable
                         String documentPart,
                         @Nullable
                         String classNumber,
                         @Nullable
                         String classType,
                         @Nullable
                         String resultingItemCategory,
                         @Nullable
                         String dependencyObjectNumber,
                         @Nullable
                         String objectType,
                         @Nullable
                         Boolean isClassificationRelevant,
                         @Nullable
                         Boolean isBulkMaterial,
                         @Nullable
                         String bOMItemIsSparePart,
                         @Nullable
                         String bOMItemIsSalesRelevant,
                         @Nullable
                         Boolean isProductionRelevant,
                         @Nullable
                         Boolean bOMItemIsPlantMaintRelevant,
                         @Nullable
                         String bOMItemIsCostingRelevant,
                         @Nullable
                         Boolean isEngineeringRelevant,
                         @Nullable
                         String specialProcurementType,
                         @Nullable
                         Boolean isBOMRecursiveAllowed,
                         @Nullable
                         BigDecimal operationLeadTimeOffset,
                         @Nullable
                         String opsLeadTimeOffsetUnit,
                         @Nullable
                         String isMaterialProvision,
                         @Nullable
                         Boolean bOMIsRecursive,
                         @Nullable
                         Boolean documentIsCreatedByCAD,
                         @Nullable
                         String distrKeyCompConsumption,
                         @Nullable
                         BigDecimal deliveryDurationInDays,
                         @Nullable
                         String creditor,
                         @Nullable
                         String costElement,
                         @Nullable
                         BigDecimal size1,
                         @Nullable
                         BigDecimal size2,
                         @Nullable
                         BigDecimal size3,
                         @Nullable
                         String unitOfMeasureForSize1To3,
                         @Nullable
                         BigDecimal goodsReceiptDuration,
                         @Nullable
                         String purchasingOrganization,
                         @Nullable
                         Boolean requiredComponent,
                         @Nullable
                         Boolean multipleSelectionAllowed,
                         @Nullable
                         String prodOrderIssueLocation,
                         @Nullable
                         Boolean materialIsCoProduct,
                         @Nullable
                         String explosionType,
                         @Nullable
                         String alternativeItemGroup,
                         @Nullable
                         String alternativeItemPriority,
                         @Nullable
                         String alternativeItemStrategy,
                         @Nullable
                         BigDecimal usageProbabilityPercent,
                         @Nullable
                         String followUpGroup,
                         @Nullable
                         String discontinuationGroup,
                         @Nullable
                         String isConfigurableBOM,
                         @Nullable
                         String referencePoint,
                         @Nullable
                         BigDecimal leadTimeOffset,
                         @Nullable
                         String productionSupplyArea,
                         @Nullable
                         Boolean isDeleted,
                         @Nullable
                         Boolean isALE,
                         @Nullable
                         ZonedDateTime lastChangeDateTime,
                         @Nullable
                         String salesOrder,
                         @Nullable
                         String salesOrderItem,
                         @Nullable
                         SalesOrderBOM toBillOfMaterial,
                         @Nullable
                         BOMItemCategory toBOMItemCategory)
```
- Method Detail
  - getType
```
@Nonnull
public Class<SalesOrderBOMItem> getType()
```
    Specified by:
    
    getType in class VdmObject<SalesOrderBOMItem>
    
    Returns:
    
    The class of this object.
  - setBillOfMaterial
```
public void setBillOfMaterial(@Nullable
                              String billOfMaterial)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterial
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Parameters:
    
    billOfMaterial - Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.
  - setBillOfMaterialCategory
```
public void setBillOfMaterialCategory(@Nullable
                                      String billOfMaterialCategory)
```
    (Key Field) Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialCategory
    
    Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
    
    Parameters:
    
    billOfMaterialCategory - This key defines a BOM according to the object (such as material or equipment) to which it is linked.
  - setBillOfMaterialVariant
```
public void setBillOfMaterialVariant(@Nullable
                                     String billOfMaterialVariant)
```
    (Key Field) Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BillOfMaterialVariant
    
    One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
    
    Parameters:
    
    billOfMaterialVariant - Identifies one BOM in a BOM group.
  - setBillOfMaterialItemNodeNumber
```
public void setBillOfMaterialItemNodeNumber(@Nullable
                                            String billOfMaterialItemNodeNumber)
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
    
    Parameters:
    
    billOfMaterialItemNodeNumber - BOM item node number
  - setHeaderChangeDocument
```
public void setHeaderChangeDocument(@Nullable
                                    String headerChangeDocument)
```
    (Key Field) Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: HeaderChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    headerChangeDocument - Number used to uniquely identify a change master record.
  - setMaterial
```
public void setMaterial(@Nullable
                        String material)
```
    (Key Field) Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Parameters:
    
    material - Alphanumeric key uniquely identifying the material.
  - setPlant
```
public void setPlant(@Nullable
                     String plant)
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    Parameters:
    
    plant - Key uniquely identifying a plant.
  - setBillOfMaterialVariantUsage
```
public void setBillOfMaterialVariantUsage(@Nullable
                                          String billOfMaterialVariantUsage)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialVariantUsage
    
    By setting various indicators, you can define the maximum configuration of the item status and define whether an item must be or cannot be processed in a particular area (such as production).A material is used in the areas production and costing in a company. For each area, you maintain a separate BOM with different items:Production BOM:This BOM contains items that are relevant to production. These items are copied to the planned order. Dependent requirements are generated for them, and they are copied to the production order.Costing BOM:This BOM contains items that are relevant to determining the material costs of a product.When you calculate production costs using a quantity structure, the system automatically determines the BOM and all the BOM items that are relevant to costing, in order to calculate manufacturing costs.
    
    Parameters:
    
    billOfMaterialVariantUsage - This key defines the area (such as engineering/design or production) where a BOM can be used.
  - setBillOfMaterialItemUUID
```
public void setBillOfMaterialItemUUID(@Nullable
                                      UUID billOfMaterialItemUUID)
```
    Constraints: none
    Original property name from the Odata EDM: BillOfMaterialItemUUID
    
    Parameters:
    
    billOfMaterialItemUUID - Global identification of an item's change status
  - setBOMItemInternalChangeCount
```
public void setBOMItemInternalChangeCount(@Nullable
                                          String bOMItemInternalChangeCount)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOMItemInternalChangeCount
    
    Parameters:
    
    bOMItemInternalChangeCount - Identifies the activity posting.
  - setValidityStartDate
```
public void setValidityStartDate(@Nullable
                                 LocalDateTime validityStartDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityStartDate
    
    Parameters:
    
    validityStartDate - Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - setValidityEndDate
```
public void setValidityEndDate(@Nullable
                               LocalDateTime validityEndDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityEndDate
    
    Parameters:
    
    validityEndDate - End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - setEngineeringChangeDocForEdit
```
public void setEngineeringChangeDocForEdit(@Nullable
                                           String engineeringChangeDocForEdit)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: EngineeringChangeDocForEdit
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    engineeringChangeDocForEdit - Number used to uniquely identify a change master record.
  - setEngineeringChangeDocument
```
public void setEngineeringChangeDocument(@Nullable
                                         String engineeringChangeDocument)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: EngineeringChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    engineeringChangeDocument - Number used to uniquely identify a change master record.
  - setChgToEngineeringChgDocument
```
public void setChgToEngineeringChgDocument(@Nullable
                                           String chgToEngineeringChgDocument)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ChgToEngineeringChgDocument
    
    If the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
    
    Parameters:
    
    chgToEngineeringChgDocument - Number used to identify the change master, which will determine the subsequent validity period of the object (material, for example).
  - setInheritedNodeNumberForBOMItem
```
public void setInheritedNodeNumberForBOMItem(@Nullable
                                             String inheritedNodeNumberForBOMItem)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
    
    Parameters:
    
    inheritedNodeNumberForBOMItem - Inherited node number of BOM item
  - setBOMItemRecordCreationDate
```
public void setBOMItemRecordCreationDate(@Nullable
                                         LocalDateTime bOMItemRecordCreationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BOMItemRecordCreationDate
    
    Parameters:
    
    bOMItemRecordCreationDate - Date on which the record was created.
  - setBOMItemCreatedByUser
```
public void setBOMItemCreatedByUser(@Nullable
                                    String bOMItemCreatedByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: BOMItemCreatedByUser
    
    Parameters:
    
    bOMItemCreatedByUser - Name of user who created the record.
  - setBOMItemLastChangeDate
```
public void setBOMItemLastChangeDate(@Nullable
                                     LocalDateTime bOMItemLastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BOMItemLastChangeDate
    
    Parameters:
    
    bOMItemLastChangeDate - Date of Last Change
  - setBOMItemLastChangedByUser
```
public void setBOMItemLastChangedByUser(@Nullable
                                        String bOMItemLastChangedByUser)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: BOMItemLastChangedByUser
    
    Parameters:
    
    bOMItemLastChangedByUser - Name of Person who Changed Object
  - setBillOfMaterialComponent
```
public void setBillOfMaterialComponent(@Nullable
                                       String billOfMaterialComponent)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillOfMaterialComponent
    
    A master record is usually maintained in the system for a component.
    
    Parameters:
    
    billOfMaterialComponent - Material number of the components that you enter, change or display as part of the BOM.
  - setBillOfMaterialItemCategory
```
public void setBillOfMaterialItemCategory(@Nullable
                                          String billOfMaterialItemCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialItemCategory
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Parameters:
    
    billOfMaterialItemCategory - Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
  - setBillOfMaterialItemNumber
```
public void setBillOfMaterialItemNumber(@Nullable
                                        String billOfMaterialItemNumber)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfMaterialItemNumber
    
    Parameters:
    
    billOfMaterialItemNumber - This number refers to the sequence of BOM components.
  - setBillOfMaterialItemUnit
```
public void setBillOfMaterialItemUnit(@Nullable
                                      String billOfMaterialItemUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: BillOfMaterialItemUnit
    
    The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
    
    Parameters:
    
    billOfMaterialItemUnit - The unit for the component quantity.
  - setBillOfMaterialItemQuantity
```
public void setBillOfMaterialItemQuantity(@Nullable
                                          BigDecimal billOfMaterialItemQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: BillOfMaterialItemQuantity
    
    You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Parameters:
    
    billOfMaterialItemQuantity - Quantity of the component, which is entered in relation to the base quantity of the product.
  - setIsAssembly
```
public void setIsAssembly(@Nullable
                          String isAssembly)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsAssembly
    
    Parameters:
    
    isAssembly - Indicator: the component in this item has its own BOM.
  - setIsSubItem
```
public void setIsSubItem(@Nullable
                         Boolean isSubItem)
```
    Constraints: none
    Original property name from the Odata EDM: IsSubItem
    
    Sub-items do not have an operational significance and changes arenot stored with history.
    
    Parameters:
    
    isSubItem - Indicator: this BOM item has sub-items.
  - setBOMItemSorter
```
public void setBOMItemSorter(@Nullable
                             String bOMItemSorter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BOMItemSorter
    
    Parameters:
    
    bOMItemSorter - String which can be defined as required for sorting components for display.
  - setFixedQuantity
```
public void setFixedQuantity(@Nullable
                             Boolean fixedQuantity)
```
    Constraints: none
    Original property name from the Odata EDM: FixedQuantity
    
    A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
    
    Parameters:
    
    fixedQuantity - This indicator shows that the component quantity is always the same.
  - setBOMItemHasFixedQuantity
```
public void setBOMItemHasFixedQuantity(@Nullable
                                       Boolean bOMItemHasFixedQuantity)
```
    Constraints: none
    Original property name from the Odata EDM: BOMItemHasFixedQuantity
    
    A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
    
    Parameters:
    
    bOMItemHasFixedQuantity - This indicator shows that the component quantity is always the same.
  - setPurchasingGroup
```
public void setPurchasingGroup(@Nullable
                               String purchasingGroup)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: PurchasingGroup
    
    Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.
    
    Parameters:
    
    purchasingGroup - Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities.
  - setCurrency
```
public void setCurrency(@Nullable
                        String currency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: Currency
    
    Parameters:
    
    currency - Currency key for amounts in the system.
  - setMaterialComponentPrice
```
public void setMaterialComponentPrice(@Nullable
                                      BigDecimal materialComponentPrice)
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property name from the Odata EDM: MaterialComponentPrice
    
    Parameters:
    
    materialComponentPrice - Amount for non-stock item, which is used when costing the end or intermediate product for pricing purposes.
  - setIdentifierBOMItem
```
public void setIdentifierBOMItem(@Nullable
                                 String identifierBOMItem)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: IdentifierBOMItem
    
    Parameters:
    
    identifierBOMItem - Alphanumeric character string, with which you uniquely identify a BOM item.
  - setMaterialPriceUnitQty
```
public void setMaterialPriceUnitQty(@Nullable
                                    BigDecimal materialPriceUnitQty)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property name from the Odata EDM: MaterialPriceUnitQty
    
    If 10 gallons of gasoline cost $12.00, the price unit is 10.
    
    Parameters:
    
    materialPriceUnitQty - Number of units to which the price refers.
  - setComponentScrapInPercent
```
public void setComponentScrapInPercent(@Nullable
                                       BigDecimal componentScrapInPercent)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: ComponentScrapInPercent
    
    Component scrap is used in material requirements planning (MRP) to determine the quantities of components required. When exploding the bill of material (BOM), the system increases the required quantities of the components by the calculated scrap quantity.ExampleRequired quantity 200 piecesComponent scrap 10%Scrap quantity 20 piecesTherefore, 220 pieces are required.For examples of calculation in connection with the indicator for net scrap, see the documentation for this indicator.If there is also assembly scrap for a higher-level assembly, the system adds together the two types of scrap.If component scrap has been entered in the BOM, this value applies. Otherwise, the value specified in the material master record is used.
    
    Parameters:
    
    componentScrapInPercent - Percentage of scrap that occurs during production of the material if the material is a component.
  - setOperationScrapInPercent
```
public void setOperationScrapInPercent(@Nullable
                                       BigDecimal operationScrapInPercent)
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: OperationScrapInPercent
    
    This entry is used to override the assembly scrap for materials of high value.If operation scrap is maintained, you avoid the situation whereby too much of the material is planned in MRP for the components of subsequent operations.If you make an entry for operation scrap, you must also select the operation scrap net indicator (Net field).You can find examples of scrap under net scrap.
    
    Parameters:
    
    operationScrapInPercent - Scrap that is expected in one operation for the quantity of a component to be processed.
  - setIsNetScrap
```
public void setIsNetScrap(@Nullable
                          Boolean isNetScrap)
```
    Constraints: none
    Original property name from the Odata EDM: IsNetScrap
    
    You must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp. Operation scrapNet ind Net indicatorQty Quantity calculated for component MAT-2 in pieces
    
    Parameters:
    
    isNetScrap - This indicator determines whether scrap for the component is calculated on the basis of the net required quantity (the required quantity without assembly scrap from the material master record).
  - setNumberOfVariableSizeItem
```
public void setNumberOfVariableSizeItem(@Nullable
                                        BigDecimal numberOfVariableSizeItem)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: NumberOfVariableSizeItem
    
    Parameters:
    
    numberOfVariableSizeItem - Number of variable-size items required for the assembly .
  - setQuantityVariableSizeItem
```
public void setQuantityVariableSizeItem(@Nullable
                                        BigDecimal quantityVariableSizeItem)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: QuantityVariableSizeItem
    
    The quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    quantityVariableSizeItem - Quantity of variable-size item, which the system calculates from the sizes entered. If you wish you can enter a variable-size item formula for the. calculation.
  - setFormulaKey
```
public void setFormulaKey(@Nullable
                          String formulaKey)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: FormulaKey
    
    You want to calculate the volume of a rolled sheet of metal. This has a variable length and height, but a constant width (500 MM).The following are used in the calculation:SI units that are defined in CustomizingLength: M (meters)Volume: M3 (cubic meters)In the variable-size item, you only enter the variable values (size 1 and size 2) with a unit of measure that can be derived from the SI unit of the dimension.Example for dimension Length: MM (milllimeters), CM (centimeters), DM (decimeters), and M (meters)The variable-size item formula uses the SI unit, so you must enter the constant width in the formula in the SI unit (meters).Example: ROMS1 * ROMS2 * 0.5 (M)You can enter units of measure for calculating the variable-size item quantity with a formula. The quantity is always calculated in the SI unit of the dimension, such as M3 (cubic meters) for volume.
    
    Parameters:
    
    formulaKey - Key that represents the algorithm for calculating the variable-size item quantity.
  - setComponentDescription
```
public void setComponentDescription(@Nullable
                                    String componentDescription)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: ComponentDescription
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Parameters:
    
    componentDescription - Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - setBOMItemDescription
```
public void setBOMItemDescription(@Nullable
                                  String bOMItemDescription)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BOMItemDescription
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Parameters:
    
    bOMItemDescription - Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - setBOMItemText2
```
public void setBOMItemText2(@Nullable
                            String bOMItemText2)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BOMItemText2
    
    You can also enter a long text by choosing menu option Details --> Long text --> Item long text.If the text comprises less than three lines, it is stored in the BOM item. Otherwise, it is stored as a long text in the text database.
    
    Parameters:
    
    bOMItemText2 - Text of up to 40 characters, which forms the second of two lines of text describing the item.
  - setMaterialGroup
```
public void setMaterialGroup(@Nullable
                             String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    Original property name from the Odata EDM: MaterialGroup
    
    You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
    
    Parameters:
    
    materialGroup - Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - setDocumentType
```
public void setDocumentType(@Nullable
                            String documentType)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: DocumentType
    
    Parameters:
    
    documentType - Part of the document key, which categorizes documents according to their distinguishing features and the organizational procedures which result from them.
  - setDocNumber
```
public void setDocNumber(@Nullable
                         String docNumber)
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: DocNumber
    
    Parameters:
    
    docNumber - This number is the main part of the document key, which is used to identify the document.
  - setDocumentVersion
```
public void setDocumentVersion(@Nullable
                               String documentVersion)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DocumentVersion
    
    A new version is assigned after the original files have been edited in the following processing situations:The new processing status varies from the original in a certain way (for example, text change sin a text file).You want the original processing status to remain the same (for example, documentation of project progress).
    
    Parameters:
    
    documentVersion - Number which identifies the version of a document.
  - setDocumentPart
```
public void setDocumentPart(@Nullable
                            String documentPart)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: DocumentPart
    
    Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
    
    Parameters:
    
    documentPart - Section of a document which is maintained as an independent document.
  - setClassNumber
```
public void setClassNumber(@Nullable
                           String classNumber)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: ClassNumber
    
    Parameters:
    
    classNumber - Name used to uniquely identify a class within a class type.
  - setClassType
```
public void setClassType(@Nullable
                         String classType)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: ClassType
    
    Parameters:
    
    classType - Uniquely identifies the class type
  - setResultingItemCategory
```
public void setResultingItemCategory(@Nullable
                                     String resultingItemCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ResultingItemCategory
    
    This categorization allows you to process data that is relevant to BOM items for all objects allocated to the class. For example, you control field selection and special system activities when you select the resulting item category.The class type determines which resulting item category you can select:If the class type is linked to the material master, you can select one of the following resulting item categories:stock itemnon-stock itemvariable-size itemPM structure elementIf the class type is linked to documents, you can enter document item as the resulting item category.
    
    Parameters:
    
    resultingItemCategory - Categorization of class items according to the object type linked to the class type.
  - setDependencyObjectNumber
```
public void setDependencyObjectNumber(@Nullable
                                      String dependencyObjectNumber)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: DependencyObjectNumber
    
    Parameters:
    
    dependencyObjectNumber - Number of Object with Assigned Dependencies
  - setObjectType
```
public void setObjectType(@Nullable
                          String objectType)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ObjectType
    
    Via settings in Customizing (Bill of mat. -> Item data), you can define a language-dependent abbreviation which the system displays on the General item overview screen.
    
    Parameters:
    
    objectType - Key which assigns the BOM item to a group of objects which have basic features in common, such as material or document.
  - setIsClassificationRelevant
```
public void setIsClassificationRelevant(@Nullable
                                        Boolean isClassificationRelevant)
```
    Constraints: none
    Original property name from the Odata EDM: IsClassificationRelevant
    
    If you select this indicator, the classification of the item is taken into account when the object is configured.You can only select this indicator if you have classified the item first (entered a class type).
    
    Parameters:
    
    isClassificationRelevant - Indicator for defining classification as a selection condition.
  - setIsBulkMaterial
```
public void setIsBulkMaterial(@Nullable
                              Boolean isBulkMaterial)
```
    Constraints: none
    Original property name from the Odata EDM: IsBulkMaterial
    
    The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
    
    Parameters:
    
    isBulkMaterial - This indicator defines a BOM item as a bulk material, which is available directly at the work center (for example, washers or grease).
  - setBOMItemIsSparePart
```
public void setBOMItemIsSparePart(@Nullable
                                  String bOMItemIsSparePart)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BOMItemIsSparePart
    
    In a BOM explosion, you can use this indicator to restrict item selection.The indicator does not interrupt the explosion of the BOM to the lowest level. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Spare part indicator.These indicators work as filters. The explosion result, you see on the screen only the items that fulfil the selection criteria. In this case, only the items with the spare part indicator you selected are shown.In the IMG for BOMs, you can group spare parts together according to various points of view - for example, according to different maintenance cycles.Spare part group A contains spare parts that need to be replaced after a machine runtime of 100 hours, whereas spare part group B contains spare parts that only need to be replaced after a machine runtime of 500 hours.
    
    Parameters:
    
    bOMItemIsSparePart - This key defines the item as a spare part.
  - setBOMItemIsSalesRelevant
```
public void setBOMItemIsSalesRelevant(@Nullable
                                      String bOMItemIsSalesRelevant)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BOMItemIsSalesRelevant
    
    For example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Relevant to sales indicator.This status indicator works as a filter. The explosion result you see on the screen only includes the items that fulfil the selection criteria. In this case, only the items that are relevant to sales are shown.
    
    Parameters:
    
    bOMItemIsSalesRelevant - This indicator shows that this item is relevant to the sales and distribution area of a company.
  - setIsProductionRelevant
```
public void setIsProductionRelevant(@Nullable
                                    Boolean isProductionRelevant)
```
    Constraints: none
    Original property name from the Odata EDM: IsProductionRelevant
    
    Items with this indicator are copied to the planned order, and the system calculates dependent requirements for them. When the planned order is converted to a production order, the system automatically copies these items to the production order.This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Parameters:
    
    isProductionRelevant - Indicates that the item is relevant to the production process.
  - setBOMItemIsPlantMaintRelevant
```
public void setBOMItemIsPlantMaintRelevant(@Nullable
                                           Boolean bOMItemIsPlantMaintRelevant)
```
    Constraints: none
    Original property name from the Odata EDM: BOMItemIsPlantMaintRelevant
    
    Items that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Parameters:
    
    bOMItemIsPlantMaintRelevant - Indicates that this item is relevant to plant maintainance procedures.
  - setBOMItemIsCostingRelevant
```
public void setBOMItemIsCostingRelevant(@Nullable
                                        String bOMItemIsCostingRelevant)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BOMItemIsCostingRelevant
    
    The extent is controlled by predefined factors for fixed and variable costs respectively.If this indicator is not set, the item is not costed.Indicator "x" determines that the item is always relevant to costing in all ways. This means that you do not need to maintain factors.You can enter factors if another indicator is entered.Factors between 0 and 1 are primarily used in inventory costing. These factors are not relevant to standard costing or order costing.Example: factor 0.5 in standard costing means that the item is costed with a factor of 1. Factor 0 means that the item is not costed.
    
    Parameters:
    
    bOMItemIsCostingRelevant - This key controls whether and to what extent this item is relevant to costing.
  - setIsEngineeringRelevant
```
public void setIsEngineeringRelevant(@Nullable
                                     Boolean isEngineeringRelevant)
```
    Constraints: none
    Original property name from the Odata EDM: IsEngineeringRelevant
    
    This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Parameters:
    
    isEngineeringRelevant - Indicates that this item is relevant to the area responsible for producing a functional design for production.
  - setSpecialProcurementType
```
public void setSpecialProcurementType(@Nullable
                                      String specialProcurementType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SpecialProcurementType
    
    Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce a material in-house, it may be appropriate to choose Production in other plant.
    
    Parameters:
    
    specialProcurementType - Allows you to define the procurement type more closely. The procurement type is determined from the material type.
  - setIsBOMRecursiveAllowed
```
public void setIsBOMRecursiveAllowed(@Nullable
                                     Boolean isBOMRecursiveAllowed)
```
    Constraints: none
    Original property name from the Odata EDM: IsBOMRecursiveAllowed
    
    If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
    
    Parameters:
    
    isBOMRecursiveAllowed - Indicator: controls whether the system checks the BOM for recursiveness.
  - setOperationLeadTimeOffset
```
public void setOperationLeadTimeOffset(@Nullable
                                       BigDecimal operationLeadTimeOffset)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: OperationLeadTimeOffset
    
    (In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.---------------------------------------------------------Component Operation Lead-time offset (h) End dateM-01 0010 2+ 05.13.1998, 11 a.m.M-02 0020 2- 05.14.1998, 12 a.m.The component M-01 does not have to be available until 2 hours after the start time of the allocated operation 0010.Because the component M-02 must be available 2 hours before the start time of the allocated operation, the end time is 12 a.m.
    
    Parameters:
    
    operationLeadTimeOffset - Time that the component lead-time offset states with reference to the start date of the allocated operation.
  - setOpsLeadTimeOffsetUnit
```
public void setOpsLeadTimeOffsetUnit(@Nullable
                                     String opsLeadTimeOffsetUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
    
    Parameters:
    
    opsLeadTimeOffsetUnit - Unit for lead-time offset for operation
  - setIsMaterialProvision
```
public void setIsMaterialProvision(@Nullable
                                   String isMaterialProvision)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsMaterialProvision
    
    In the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part. The following indicators are available:Refurbishment material to SC (value S in standard SAP system)Refurbishment material from SC (value X in standard SAP system)Subsequent delivery (value F in standard SAP system)If you do not enter information in this field, the components are provided to the subcontractor as consumable materials (initial value in the standard SAP system).Material provided by a vendorThis indicator controls material requirements planning. Maintain this indicator for BOM components only if the material master record of the header material supports subcontracting (Special procurement field).The special procurement key for subcontracting means that all components of the BOM are provided free of charge to a subcontractor for further processing. The items are copied to a subcontract order.If the item is provided to a vendor, do not enter any material provision indicator.Dependent requirements are generated for this item.If the item is already at a vendor's premises and is not provided by us, do enter an indicator.No dependent requirements are generated for this item.Material provided by a customerThis indicator is not currently active.
    
    Parameters:
    
    isMaterialProvision - This key indicates that the item is subject to material provision.
  - setBOMIsRecursive
```
public void setBOMIsRecursive(@Nullable
                              Boolean bOMIsRecursive)
```
    Constraints: none
    Original property name from the Odata EDM: BOMIsRecursive
    
    In BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
    
    Parameters:
    
    bOMIsRecursive - Indicator set by the system if the exploded BOM for an object contains the object itself as an item.
  - setDocumentIsCreatedByCAD
```
public void setDocumentIsCreatedByCAD(@Nullable
                                      Boolean documentIsCreatedByCAD)
```
    Constraints: none
    Original property name from the Odata EDM: DocumentIsCreatedByCAD
    
    Parameters:
    
    documentIsCreatedByCAD - Information: data for the assembly/component was generated in a CAD system and transferred into the SAP system via an interface.
  - setDistrKeyCompConsumption
```
public void setDistrKeyCompConsumption(@Nullable
                                       String distrKeyCompConsumption)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: DistrKeyCompConsumption
    
    This means that the MRP controller can plan a daily supply of partial quantities (distributed over the validity period of the RS header) for repetitive manufacturing.
    
    Parameters:
    
    distrKeyCompConsumption - Determines the split to be used for distributing the run schedule quantity (into partial quantities) over the validity period of the planned order or the production order. In so doing, the relationship between time and the consumption of components is established.
  - setDeliveryDurationInDays
```
public void setDeliveryDurationInDays(@Nullable
                                      BigDecimal deliveryDurationInDays)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: DeliveryDurationInDays
    
    When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
    
    Parameters:
    
    deliveryDurationInDays - Gives the delivery time for the material in days.
  - setCreditor
```
public void setCreditor(@Nullable
                        String creditor)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Creditor
    
    Parameters:
    
    creditor - Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.
  - setCostElement
```
public void setCostElement(@Nullable
                           String costElement)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CostElement
    
    which is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
    
    Parameters:
    
    costElement - Number of the G/L account
  - setSize1
```
public void setSize1(@Nullable
                     BigDecimal size1)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: Size1
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    size1 - One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - setSize2
```
public void setSize2(@Nullable
                     BigDecimal size2)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: Size2
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    size2 - One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - setSize3
```
public void setSize3(@Nullable
                     BigDecimal size3)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: Size3
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Parameters:
    
    size3 - One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - setUnitOfMeasureForSize1To3
```
public void setUnitOfMeasureForSize1To3(@Nullable
                                        String unitOfMeasureForSize1To3)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: UnitOfMeasureForSize1To3
    
    Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
    
    Parameters:
    
    unitOfMeasureForSize1To3 - Unit of measure for sizes 1 to 3.
  - setGoodsReceiptDuration
```
public void setGoodsReceiptDuration(@Nullable
                                    BigDecimal goodsReceiptDuration)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: GoodsReceiptDuration
    
    Parameters:
    
    goodsReceiptDuration - Number of workdays required after receiving the material for inspection and placement into storage.
  - setPurchasingOrganization
```
public void setPurchasingOrganization(@Nullable
                                      String purchasingOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: PurchasingOrganization
    
    Parameters:
    
    purchasingOrganization - Denotes the purchasing organization.
  - setRequiredComponent
```
public void setRequiredComponent(@Nullable
                                 Boolean requiredComponent)
```
    Constraints: none
    Original property name from the Odata EDM: RequiredComponent
    
    Parameters:
    
    requiredComponent - If this class is used as a class item in a configurable object, this setting has the following effect in interactive configuration: the configuration is incomplete until the class item has been replaced by an object. In low-level configuration (MRP, for example), the "Required component" indicator has no further effects.
  - setMultipleSelectionAllowed
```
public void setMultipleSelectionAllowed(@Nullable
                                        Boolean multipleSelectionAllowed)
```
    Constraints: none
    Original property name from the Odata EDM: MultipleSelectionAllowed
    
    Parameters:
    
    multipleSelectionAllowed - This indicator influences the status of a configuration in cases where a class item has been replaced by more than one object. Only if the configuration scenario allows manual changes to the BOM (order BOM or sales order with manual changes) can a class item be temporarily replaced by more than one object. However, before you save, the selection must be restricted to one object by using a manual object search. If you leave the configuration while the class item is still replaced by more than one object, only the first object is saved or transferred to the calling application. The "Multiple Selection" indicator has the following effect in interactive configuration: the configuration is still consistent if the class item has been replaced by more than one object. Without this indicator, the configuration is inconsistent if the class item has been replaced by more than one object. In low-level configuration (MRP, for example), only one object is used to replace the class, whether or not the "Multiple Selection" indicator is set.
  - setProdOrderIssueLocation
```
public void setProdOrderIssueLocation(@Nullable
                                      String prodOrderIssueLocation)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProdOrderIssueLocation
    
    In production, first there is a check as to whether an issue location is entered in the BOM item.If there is an issue location in the BOM item, this issue location is copied to the production order as a default value. Otherwise, the issue location is copied from the material master record (in the plant in which you created the BOM).This indicator is only supported for items that are relevant to production and plant maintenance.You cannot enter an issue location for a bulk material.
    
    Parameters:
    
    prodOrderIssueLocation - Number of the issue location from which the material is issued during the production process. Backflush is posted to this issue location if required.
  - setMaterialIsCoProduct
```
public void setMaterialIsCoProduct(@Nullable
                                   Boolean materialIsCoProduct)
```
    Constraints: none
    Original property name from the Odata EDM: MaterialIsCoProduct
    
    Enter a negative quantity.Example: 6- You can only enter an item as a co-product if:The material master (MRP 2 view) contains the Material can be a co-product indicator. (For some material types, such as raw materials for example, the co-product indicator is hidden in the standard SAP system.)You enter the item as a stock item
    
    Parameters:
    
    materialIsCoProduct - Indicator showing that the item is a co-product.
  - setExplosionType
```
public void setExplosionType(@Nullable
                             String explosionType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ExplosionType
    
    You can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
    
    Parameters:
    
    explosionType - This is used to control the explosion of an item when determining dependent requirements.
  - setAlternativeItemGroup
```
public void setAlternativeItemGroup(@Nullable
                                    String alternativeItemGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AlternativeItemGroup
    
    As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:dependent requirements are determined in requirements planningdependent requirements are changed to a reservation in the production orderAlternative positions as informationYou can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.Enter the same character string to denote the alternative items of an alternative item group.Enter the same strategy for all alternative items in the alternative item group.Alternative items are valuated in the following way:Dependent requirements determinationRequirements planning determines the dependent requirements according to the usage probabilities that have been entered.If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created.Withdrawal postingYou can control the withdrawal posting for the resevation in the production order in the following way:Withdrawal according to usage probability (manual change is possible)Withdrawal if there is 100% availability(Check ranking order and strategy)Example: See Strategy for alternative position
    
    Parameters:
    
    alternativeItemGroup - Consolidation of alternative items within a BOM. Every material in the assembly can be included in the alternative item group.
  - setAlternativeItemPriority
```
public void setAlternativeItemPriority(@Nullable
                                       String alternativeItemPriority)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AlternativeItemPriority
    
    With respect to withdrawal postings, the ranking order determines which material components from the alternative item group should be taken into account for the reservation in the production order.Withdrawal according to usage probabilityFor all items that should be reserved, maintain:strategy (value 1 or no entry)ranking order (only effects the material sort)usage probabilityWithdrawal on 100% availabilityFor all items that should be reserved, maintain:ranking orderIf you do not enter the ranking order, the system checks the items in the order that they are transmitted to the availability check.strategy (value 2)usage probabilityThree items (0060 und 0065 and 0070) are assigned to an alternative item group and are given the following values for ranking order:position ranking order0060 30065 20070 1This means that the system reads item 0070 first.
    
    Parameters:
    
    alternativeItemPriority - Position of an item in an alternative item group.
  - setAlternativeItemStrategy
```
public void setAlternativeItemStrategy(@Nullable
                                       String alternativeItemStrategy)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: AlternativeItemStrategy
    
    This strategy is ignored in material requirements planning (MRP).The withdrawal posting for the reservation in the production order can be selected as follows:According to usage probability (manual changes possible)For all items that you want to reserve, enter:Strategy (value 1 or no entry)Priority (only influences how materials are sorted)Usage probabilityWithdrawal if 100% availabilityFor all items that you want to reserve, enter:Strategy (value 2)PriorityIf you do not enter a priority, the system checks the items in the sequence in which they are transferred to the availability check.Usage probabilityEnter the same strategy for all alternative items in an alternative item group.Withdrawal if 100% availability (strategy 2)This strategy uses ATP logic to check availability in the defined ranking order.Gross requirements: 100 piecesM UP (%) RO RQ ATP qty Issue qtyA 20 1 20 30 0B 30 2 30 150 100C 50 3 50 180 0KeyM MaterialUP Usage probabilityRO Ranking orderRQ Requirements quantityThe first material in the ranking order that is supplied 100% on the requirement date is reserved in the required quantity (material B).If a partial withdrawal is carried out in a production order, when additional partial withdrawals take place, no further checks are carried out for this production order. Additional partial withdrawals result from the alternative item, from which the first withdrawal took place.If when using strategy 2 none of the alternative items cover the requirements 100%, the availability check for all items will confirm the available. A reservation only occurs for the available quantity.
    
    Parameters:
    
    alternativeItemStrategy - This value defines how items in an alternative group are selected for withdrawal postings.
  - setUsageProbabilityPercent
```
public void setUsageProbabilityPercent(@Nullable
                                       BigDecimal usageProbabilityPercent)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: UsageProbabilityPercent
    
    The usage probability is always taken into account for requirements planning.Maintain selected usage probabilityRequirements planning for alternative items is based on the usage probability.Quantities are suggested based on the usage probability for the withdrawal posting according to strategy 1. You can plan in excess for the alternative items since the usage probability is not limited to 100%. You can change the proposed quantities. Maintain no usage probability If you do not enter a usage probability, the alternative item just serves as information that can be evaluated, for example, in a situation with a missing part.You receive a warning since dependent requirements with 0 as quantity are created.Withdrawal based on usage probabilityStrategy: value 1An alternative item group is maintained for each assembly. This alternative item group contains four materials with differing usage probabilities. Dependent requirements are passed on with 100 as quantity.Material Usage probability (%) RequirementM-1 70 70M-2 20 20M-3 20 20M-4 0 no requirementIn this case, the materials are planned in excess since the sum of the usage probabilities is greater than 100%.
    
    Parameters:
    
    usageProbabilityPercent - Percentage probability that a material will be used in the assembly.
  - setFollowUpGroup
```
public void setFollowUpGroup(@Nullable
                             String followUpGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: FollowUpGroup
    
    You can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials. When an item (main item) is discontinued, another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: discontinuation indicator value 1Material of the dependent item: value 3Settings in the BOM:The main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.You can only maintain an item as a follow-up item when you enter it for the first time. The field value cannot be changed after you have entered and saved the item.The follow-up item(s) that are to replace the item to be discontinued must have the same value in the Discontinuation group field as the item to be discontinued has in the Follow-up group field (see the example below).The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.You can only maintain the follow-up group for one item if:the component is planned to a schedule (for example, a warehouse item)the base unit of measure of the materials is identicalExample of a simple discontinuationfItem 0010 to be discontinued (material M-1) is replaced by item 0010 to be introduced (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Material Discontinuation group Follow-up group0010 M-1 A1 -0010 M-2 - A1Example of a parallel discontinuationthe items 0010 (material M-1) and 0011 (material M-2) are replaced by the items 0010 (material M-3) and 0011 (material M-4) to be ntroduced.Discontinuation indicator in the material master record:M-1: Value 1 (main discontinued item)M-2: Value 3 (dependent discontinued item)Item Material Discontinuation group Follow-up group0010 M-1 A1 -0011 M-2 A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Parameters:
    
    followUpGroup - This is a freely-definable character string which is assigned to linked follow-up items in a bill of material. The follow-up group shows which follow-up item(s) are to replace the item to be discontinued.
  - setDiscontinuationGroup
```
public void setDiscontinuationGroup(@Nullable
                                    String discontinuationGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DiscontinuationGroup
    
    You can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group. If an item is to be discontinued (main item), another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: value 1Material of the dependent item: value 3Settings in the BOM:Both the main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.Both the follow-up group of the items to be introduced and the discontinuation group of the items to be discontinued must have the same value.You can only enter a discontinuation group for an item if the discontinuation indicator (material master, MRP 4 view) supports discontinuation.A discontinued item is replaced by a follow-up item. In the follow-up item, you maintain a follow-up group.Example for a simple discontinuationItem 0010 (material M-1) is to be discontinued and replaced by follow-up item 0010 (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Mat. DisconGrp FollGrp 0010 M-1 A1 -0010 M-2 - A1Example for a Parallel discontinuationItems 0010 (material M-1) and 0011 (material M-2) to be discontinued are replaced by items 0010 (material M-3) and 0011 (material M-4) to be introduced.Discontinuation indicator in the material master record:M-1: value 1 (main discontinued item)M-2: value 3 (dependent discontinued item)Item Mat. Discontinuation group Follow-up group0010 M-1 ,A1 -0011 M-2 ,A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Parameters:
    
    discontinuationGroup - This freely-definable character string is used to group together related items to be discontinued in a BOM.
  - setIsConfigurableBOM
```
public void setIsConfigurableBOM(@Nullable
                                 String isConfigurableBOM)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsConfigurableBOM
    
    Parameters:
    
    isConfigurableBOM - Selection indicator for configurable BOMs
  - setReferencePoint
```
public void setReferencePoint(@Nullable
                              String referencePoint)
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: ReferencePoint
    
    Parameters:
    
    referencePoint - Creates a logical link between BOM items and network activities.
  - setLeadTimeOffset
```
public void setLeadTimeOffset(@Nullable
                              BigDecimal leadTimeOffset)
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: LeadTimeOffset
    
    This value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
    
    Parameters:
    
    leadTimeOffset - This value shows the lead-time offset (in workdays) for the component in relation to the start date for production of the superior assembly.
  - setProductionSupplyArea
```
public void setProductionSupplyArea(@Nullable
                                    String productionSupplyArea)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ProductionSupplyArea
    
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Parameters:
    
    productionSupplyArea - The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.
  - setIsDeleted
```
public void setIsDeleted(@Nullable
                         Boolean isDeleted)
```
    Constraints: none
    Original property name from the Odata EDM: IsDeleted
    
    This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
    
    Parameters:
    
    isDeleted - Indicator showing that the BOM header or the BOM item has been deleted with reference to the change number.
  - setIsALE
```
public void setIsALE(@Nullable
                     Boolean isALE)
```
    Constraints: none
    Original property name from the Odata EDM: IsALE
    
    Parameters:
    
    isALE - Shows that data of the assembly or component has been distributed to the SAP system using ALE.
  - setLastChangeDateTime
```
public void setLastChangeDateTime(@Nullable
                                  ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Parameters:
    
    lastChangeDateTime - The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - setSalesOrder
```
public void setSalesOrder(@Nullable
                          String salesOrder)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesOrder
    
    If, for example, you want to display or change a sales document and you have only the purchase order number from the customer, you can use a matchcode to find the document.You created a sales order which refers to customer purchase order number 12544-D. To locate the sales order, you can enter =a.12544-D in the sales document field.
    
    Parameters:
    
    salesOrder - The number that uniquely identifies the sales document.
  - setSalesOrderItem
```
public void setSalesOrderItem(@Nullable
                              String salesOrderItem)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesOrderItem
    
    Parameters:
    
    salesOrderItem - The number that uniquely identifies the item in the sales document.
  - getEntityCollection
```
protected String getEntityCollection()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Specified by:
    
    getEntityCollection in class VdmEntity<SalesOrderBOMItem>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<SalesOrderBOMItem>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<SalesOrderBOMItem>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<SalesOrderBOMItem>
  - field
```
@Nonnull
public static <T> SalesOrderBOMItemField<T> field(@Nonnull
                                                           String fieldName,
                                                           @Nonnull
                                                           Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    Parameters:
    
    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.
    
    Returns:
    
    A representation of an extension field from this entity.
  - field
```
@Nonnull
public static <T,DomainT> SalesOrderBOMItemField<T> field(@Nonnull
                                                                   String fieldName,
                                                                   @Nonnull
                                                                   TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getDestinationForFetch
```
@Nullable
public HttpDestinationProperties getDestinationForFetch()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same destination with multiple queries (e.g. fetching associated entities). New destination to apply to this entity
    
    Overrides:
    
    getDestinationForFetch in class VdmEntity<SalesOrderBOMItem>
    
    Returns:
    
    The stored destination for executing queries, or null if no such context has been set.
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    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.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<SalesOrderBOMItem>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nonnull
                            HttpDestinationProperties destination)
```
    Description copied from class: VdmEntity
    
    Sets the service path and destination for the fetch commands of this entity. Also applies to any associated entities (navigation properties) that were previously fetched.
    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.
    
    Overrides:
    
    attachToService in class VdmEntity<SalesOrderBOMItem>
    
    Parameters:
    
    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.
    
    destination - New destination to apply to this entity and any associated entities that were previously fetched.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Overrides:
    
    getDefaultServicePath in class VdmEntity<SalesOrderBOMItem>
    
    Returns:
    
    Default context path to the OData service. In other words, everything in between the protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)
  - toMapOfNavigationProperties
```
@Nonnull
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<SalesOrderBOMItem>
  - fetchBillOfMaterial
```
@Nullable
public SalesOrderBOM fetchBillOfMaterial()
                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the SalesOrderBOM entity (one to one) associated with this entity. This corresponds to the OData navigation property to_BillOfMaterial.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated SalesOrderBOM entity, or null if an entity is not associated.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getBillOfMaterialOrFetch
```
@Nullable
public SalesOrderBOM getBillOfMaterialOrFetch()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated SalesOrderBOM entity (one to one). This corresponds to the OData navigation property to_BillOfMaterial.
    If the navigation property to_BillOfMaterial of a queried SalesOrderBOMItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated SalesOrderBOM entity.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getBillOfMaterialIfPresent
```
@Nonnull
public io.vavr.control.Option<SalesOrderBOM> getBillOfMaterialIfPresent()
```
    Retrieval of associated SalesOrderBOM entity (one to one). This corresponds to the OData navigation property to_BillOfMaterial.
    If the navigation property for an entity SalesOrderBOMItem has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_BillOfMaterial is already loaded, the result will contain the SalesOrderBOM entity. If not, an Option with result state empty is returned.
  - setBillOfMaterial
```
public void setBillOfMaterial(SalesOrderBOM value)
```
    Overwrites the associated SalesOrderBOM entity for the loaded navigation property to_BillOfMaterial.
    
    Parameters:
    
    value - New SalesOrderBOM entity.
  - fetchBOMItemCategory
```
@Nullable
public BOMItemCategory fetchBOMItemCategory()
                                               throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BOMItemCategory entity (one to one) associated with this entity. This corresponds to the OData navigation property to_BOMItemCategory.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated BOMItemCategory entity, or null if an entity is not associated.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getBOMItemCategoryOrFetch
```
@Nullable
public BOMItemCategory getBOMItemCategoryOrFetch()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BOMItemCategory entity (one to one). This corresponds to the OData navigation property to_BOMItemCategory.
    If the navigation property to_BOMItemCategory of a queried SalesOrderBOMItem is operated lazily, an ODataException can be thrown in case of an OData query error.
    Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
    
    Returns:
    
    List of associated BOMItemCategory entity.
    
    Throws:
    
    com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.
  - getBOMItemCategoryIfPresent
```
@Nonnull
public io.vavr.control.Option<BOMItemCategory> getBOMItemCategoryIfPresent()
```
    Retrieval of associated BOMItemCategory entity (one to one). This corresponds to the OData navigation property to_BOMItemCategory.
    If the navigation property for an entity SalesOrderBOMItem has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_BOMItemCategory is already loaded, the result will contain the BOMItemCategory entity. If not, an Option with result state empty is returned.
  - setBOMItemCategory
```
public void setBOMItemCategory(BOMItemCategory value)
```
    Overwrites the associated BOMItemCategory entity for the loaded navigation property to_BOMItemCategory.
    
    Parameters:
    
    value - New BOMItemCategory entity.
  - builder
```
@Nonnull
public static SalesOrderBOMItem.SalesOrderBOMItemBuilder builder()
```
  - getBillOfMaterial
```
@Nullable
public String getBillOfMaterial()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterial
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Returns:
    
    Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.
  - getBillOfMaterialCategory
```
@Nullable
public String getBillOfMaterialCategory()
```
    (Key Field) Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialCategory
    
    Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
    
    Returns:
    
    This key defines a BOM according to the object (such as material or equipment) to which it is linked.
  - getBillOfMaterialVariant
```
@Nullable
public String getBillOfMaterialVariant()
```
    (Key Field) Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BillOfMaterialVariant
    
    One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
    
    Returns:
    
    Identifies one BOM in a BOM group.
  - getBillOfMaterialItemNodeNumber
```
@Nullable
public String getBillOfMaterialItemNodeNumber()
```
    (Key Field) Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
    
    Returns:
    
    BOM item node number
  - getHeaderChangeDocument
```
@Nullable
public String getHeaderChangeDocument()
```
    (Key Field) Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: HeaderChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getMaterial
```
@Nullable
public String getMaterial()
```
    (Key Field) Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getPlant
```
@Nullable
public String getPlant()
```
    (Key Field) Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    Returns:
    
    Key uniquely identifying a plant.
  - getBillOfMaterialVariantUsage
```
@Nullable
public String getBillOfMaterialVariantUsage()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialVariantUsage
    
    By setting various indicators, you can define the maximum configuration of the item status and define whether an item must be or cannot be processed in a particular area (such as production).A material is used in the areas production and costing in a company. For each area, you maintain a separate BOM with different items:Production BOM:This BOM contains items that are relevant to production. These items are copied to the planned order. Dependent requirements are generated for them, and they are copied to the production order.Costing BOM:This BOM contains items that are relevant to determining the material costs of a product.When you calculate production costs using a quantity structure, the system automatically determines the BOM and all the BOM items that are relevant to costing, in order to calculate manufacturing costs.
    
    Returns:
    
    This key defines the area (such as engineering/design or production) where a BOM can be used.
  - getBillOfMaterialItemUUID
```
@Nullable
public UUID getBillOfMaterialItemUUID()
```
    Constraints: none
    Original property name from the Odata EDM: BillOfMaterialItemUUID
    
    Returns:
    
    Global identification of an item's change status
  - getBOMItemInternalChangeCount
```
@Nullable
public String getBOMItemInternalChangeCount()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BOMItemInternalChangeCount
    
    Returns:
    
    Identifies the activity posting.
  - getValidityStartDate
```
@Nullable
public LocalDateTime getValidityStartDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityStartDate
    
    Returns:
    
    Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - getValidityEndDate
```
@Nullable
public LocalDateTime getValidityEndDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityEndDate
    
    Returns:
    
    End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - getEngineeringChangeDocForEdit
```
@Nullable
public String getEngineeringChangeDocForEdit()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: EngineeringChangeDocForEdit
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getEngineeringChangeDocument
```
@Nullable
public String getEngineeringChangeDocument()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: EngineeringChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getChgToEngineeringChgDocument
```
@Nullable
public String getChgToEngineeringChgDocument()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ChgToEngineeringChgDocument
    
    If the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
    
    Returns:
    
    Number used to identify the change master, which will determine the subsequent validity period of the object (material, for example).
  - getInheritedNodeNumberForBOMItem
```
@Nullable
public String getInheritedNodeNumberForBOMItem()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
    
    Returns:
    
    Inherited node number of BOM item
  - getBOMItemRecordCreationDate
```
@Nullable
public LocalDateTime getBOMItemRecordCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BOMItemRecordCreationDate
    
    Returns:
    
    Date on which the record was created.
  - getBOMItemCreatedByUser
```
@Nullable
public String getBOMItemCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: BOMItemCreatedByUser
    
    Returns:
    
    Name of user who created the record.
  - getBOMItemLastChangeDate
```
@Nullable
public LocalDateTime getBOMItemLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BOMItemLastChangeDate
    
    Returns:
    
    Date of Last Change
  - getBOMItemLastChangedByUser
```
@Nullable
public String getBOMItemLastChangedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: BOMItemLastChangedByUser
    
    Returns:
    
    Name of Person who Changed Object
  - getBillOfMaterialComponent
```
@Nullable
public String getBillOfMaterialComponent()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillOfMaterialComponent
    
    A master record is usually maintained in the system for a component.
    
    Returns:
    
    Material number of the components that you enter, change or display as part of the BOM.
  - getBillOfMaterialItemCategory
```
@Nullable
public String getBillOfMaterialItemCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialItemCategory
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Returns:
    
    Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
  - getBillOfMaterialItemNumber
```
@Nullable
public String getBillOfMaterialItemNumber()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfMaterialItemNumber
    
    Returns:
    
    This number refers to the sequence of BOM components.
  - getBillOfMaterialItemUnit
```
@Nullable
public String getBillOfMaterialItemUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: BillOfMaterialItemUnit
    
    The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
    
    Returns:
    
    The unit for the component quantity.
  - getBillOfMaterialItemQuantity
```
@Nullable
public BigDecimal getBillOfMaterialItemQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: BillOfMaterialItemQuantity
    
    You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Returns:
    
    Quantity of the component, which is entered in relation to the base quantity of the product.
  - getIsAssembly
```
@Nullable
public String getIsAssembly()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsAssembly
    
    Returns:
    
    Indicator: the component in this item has its own BOM.
  - getIsSubItem
```
@Nullable
public Boolean getIsSubItem()
```
    Constraints: none
    Original property name from the Odata EDM: IsSubItem
    
    Sub-items do not have an operational significance and changes arenot stored with history.
    
    Returns:
    
    Indicator: this BOM item has sub-items.
  - getBOMItemSorter
```
@Nullable
public String getBOMItemSorter()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BOMItemSorter
    
    Returns:
    
    String which can be defined as required for sorting components for display.
  - getFixedQuantity
```
@Nullable
public Boolean getFixedQuantity()
```
    Constraints: none
    Original property name from the Odata EDM: FixedQuantity
    
    A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
    
    Returns:
    
    This indicator shows that the component quantity is always the same.
  - getBOMItemHasFixedQuantity
```
@Nullable
public Boolean getBOMItemHasFixedQuantity()
```
    Constraints: none
    Original property name from the Odata EDM: BOMItemHasFixedQuantity
    
    A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
    
    Returns:
    
    This indicator shows that the component quantity is always the same.
  - getPurchasingGroup
```
@Nullable
public String getPurchasingGroup()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: PurchasingGroup
    
    Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.
    
    Returns:
    
    Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities.
  - getCurrency
```
@Nullable
public String getCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: Currency
    
    Returns:
    
    Currency key for amounts in the system.
  - getMaterialComponentPrice
```
@Nullable
public BigDecimal getMaterialComponentPrice()
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    Original property name from the Odata EDM: MaterialComponentPrice
    
    Returns:
    
    Amount for non-stock item, which is used when costing the end or intermediate product for pricing purposes.
  - getIdentifierBOMItem
```
@Nullable
public String getIdentifierBOMItem()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: IdentifierBOMItem
    
    Returns:
    
    Alphanumeric character string, with which you uniquely identify a BOM item.
  - getMaterialPriceUnitQty
```
@Nullable
public BigDecimal getMaterialPriceUnitQty()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Original property name from the Odata EDM: MaterialPriceUnitQty
    
    If 10 gallons of gasoline cost $12.00, the price unit is 10.
    
    Returns:
    
    Number of units to which the price refers.
  - getComponentScrapInPercent
```
@Nullable
public BigDecimal getComponentScrapInPercent()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: ComponentScrapInPercent
    
    Component scrap is used in material requirements planning (MRP) to determine the quantities of components required. When exploding the bill of material (BOM), the system increases the required quantities of the components by the calculated scrap quantity.ExampleRequired quantity 200 piecesComponent scrap 10%Scrap quantity 20 piecesTherefore, 220 pieces are required.For examples of calculation in connection with the indicator for net scrap, see the documentation for this indicator.If there is also assembly scrap for a higher-level assembly, the system adds together the two types of scrap.If component scrap has been entered in the BOM, this value applies. Otherwise, the value specified in the material master record is used.
    
    Returns:
    
    Percentage of scrap that occurs during production of the material if the material is a component.
  - getOperationScrapInPercent
```
@Nullable
public BigDecimal getOperationScrapInPercent()
```
    Constraints: Not nullable, Precision: 5, Scale: 2
    Original property name from the Odata EDM: OperationScrapInPercent
    
    This entry is used to override the assembly scrap for materials of high value.If operation scrap is maintained, you avoid the situation whereby too much of the material is planned in MRP for the components of subsequent operations.If you make an entry for operation scrap, you must also select the operation scrap net indicator (Net field).You can find examples of scrap under net scrap.
    
    Returns:
    
    Scrap that is expected in one operation for the quantity of a component to be processed.
  - getIsNetScrap
```
@Nullable
public Boolean getIsNetScrap()
```
    Constraints: none
    Original property name from the Odata EDM: IsNetScrap
    
    You must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp. Operation scrapNet ind Net indicatorQty Quantity calculated for component MAT-2 in pieces
    
    Returns:
    
    This indicator determines whether scrap for the component is calculated on the basis of the net required quantity (the required quantity without assembly scrap from the material master record).
  - getNumberOfVariableSizeItem
```
@Nullable
public BigDecimal getNumberOfVariableSizeItem()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: NumberOfVariableSizeItem
    
    Returns:
    
    Number of variable-size items required for the assembly .
  - getQuantityVariableSizeItem
```
@Nullable
public BigDecimal getQuantityVariableSizeItem()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: QuantityVariableSizeItem
    
    The quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    Quantity of variable-size item, which the system calculates from the sizes entered. If you wish you can enter a variable-size item formula for the. calculation.
  - getFormulaKey
```
@Nullable
public String getFormulaKey()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: FormulaKey
    
    You want to calculate the volume of a rolled sheet of metal. This has a variable length and height, but a constant width (500 MM).The following are used in the calculation:SI units that are defined in CustomizingLength: M (meters)Volume: M3 (cubic meters)In the variable-size item, you only enter the variable values (size 1 and size 2) with a unit of measure that can be derived from the SI unit of the dimension.Example for dimension Length: MM (milllimeters), CM (centimeters), DM (decimeters), and M (meters)The variable-size item formula uses the SI unit, so you must enter the constant width in the formula in the SI unit (meters).Example: ROMS1 * ROMS2 * 0.5 (M)You can enter units of measure for calculating the variable-size item quantity with a formula. The quantity is always calculated in the SI unit of the dimension, such as M3 (cubic meters) for volume.
    
    Returns:
    
    Key that represents the algorithm for calculating the variable-size item quantity.
  - getComponentDescription
```
@Nullable
public String getComponentDescription()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: ComponentDescription
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Returns:
    
    Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - getBOMItemDescription
```
@Nullable
public String getBOMItemDescription()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BOMItemDescription
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Returns:
    
    Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - getBOMItemText2
```
@Nullable
public String getBOMItemText2()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BOMItemText2
    
    You can also enter a long text by choosing menu option Details --> Long text --> Item long text.If the text comprises less than three lines, it is stored in the BOM item. Otherwise, it is stored as a long text in the text database.
    
    Returns:
    
    Text of up to 40 characters, which forms the second of two lines of text describing the item.
  - getMaterialGroup
```
@Nullable
public String getMaterialGroup()
```
    Constraints: Not nullable, Maximum length: 9
    Original property name from the Odata EDM: MaterialGroup
    
    You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
    
    Returns:
    
    Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - getDocumentType
```
@Nullable
public String getDocumentType()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: DocumentType
    
    Returns:
    
    Part of the document key, which categorizes documents according to their distinguishing features and the organizational procedures which result from them.
  - getDocNumber
```
@Nullable
public String getDocNumber()
```
    Constraints: Not nullable, Maximum length: 25
    Original property name from the Odata EDM: DocNumber
    
    Returns:
    
    This number is the main part of the document key, which is used to identify the document.
  - getDocumentVersion
```
@Nullable
public String getDocumentVersion()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DocumentVersion
    
    A new version is assigned after the original files have been edited in the following processing situations:The new processing status varies from the original in a certain way (for example, text change sin a text file).You want the original processing status to remain the same (for example, documentation of project progress).
    
    Returns:
    
    Number which identifies the version of a document.
  - getDocumentPart
```
@Nullable
public String getDocumentPart()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: DocumentPart
    
    Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
    
    Returns:
    
    Section of a document which is maintained as an independent document.
  - getClassNumber
```
@Nullable
public String getClassNumber()
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: ClassNumber
    
    Returns:
    
    Name used to uniquely identify a class within a class type.
  - getClassType
```
@Nullable
public String getClassType()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: ClassType
    
    Returns:
    
    Uniquely identifies the class type
  - getResultingItemCategory
```
@Nullable
public String getResultingItemCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ResultingItemCategory
    
    This categorization allows you to process data that is relevant to BOM items for all objects allocated to the class. For example, you control field selection and special system activities when you select the resulting item category.The class type determines which resulting item category you can select:If the class type is linked to the material master, you can select one of the following resulting item categories:stock itemnon-stock itemvariable-size itemPM structure elementIf the class type is linked to documents, you can enter document item as the resulting item category.
    
    Returns:
    
    Categorization of class items according to the object type linked to the class type.
  - getDependencyObjectNumber
```
@Nullable
public String getDependencyObjectNumber()
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: DependencyObjectNumber
    
    Returns:
    
    Number of Object with Assigned Dependencies
  - getObjectType
```
@Nullable
public String getObjectType()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: ObjectType
    
    Via settings in Customizing (Bill of mat. -> Item data), you can define a language-dependent abbreviation which the system displays on the General item overview screen.
    
    Returns:
    
    Key which assigns the BOM item to a group of objects which have basic features in common, such as material or document.
  - getIsClassificationRelevant
```
@Nullable
public Boolean getIsClassificationRelevant()
```
    Constraints: none
    Original property name from the Odata EDM: IsClassificationRelevant
    
    If you select this indicator, the classification of the item is taken into account when the object is configured.You can only select this indicator if you have classified the item first (entered a class type).
    
    Returns:
    
    Indicator for defining classification as a selection condition.
  - getIsBulkMaterial
```
@Nullable
public Boolean getIsBulkMaterial()
```
    Constraints: none
    Original property name from the Odata EDM: IsBulkMaterial
    
    The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
    
    Returns:
    
    This indicator defines a BOM item as a bulk material, which is available directly at the work center (for example, washers or grease).
  - getBOMItemIsSparePart
```
@Nullable
public String getBOMItemIsSparePart()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BOMItemIsSparePart
    
    In a BOM explosion, you can use this indicator to restrict item selection.The indicator does not interrupt the explosion of the BOM to the lowest level. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Spare part indicator.These indicators work as filters. The explosion result, you see on the screen only the items that fulfil the selection criteria. In this case, only the items with the spare part indicator you selected are shown.In the IMG for BOMs, you can group spare parts together according to various points of view - for example, according to different maintenance cycles.Spare part group A contains spare parts that need to be replaced after a machine runtime of 100 hours, whereas spare part group B contains spare parts that only need to be replaced after a machine runtime of 500 hours.
    
    Returns:
    
    This key defines the item as a spare part.
  - getBOMItemIsSalesRelevant
```
@Nullable
public String getBOMItemIsSalesRelevant()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BOMItemIsSalesRelevant
    
    For example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Relevant to sales indicator.This status indicator works as a filter. The explosion result you see on the screen only includes the items that fulfil the selection criteria. In this case, only the items that are relevant to sales are shown.
    
    Returns:
    
    This indicator shows that this item is relevant to the sales and distribution area of a company.
  - getIsProductionRelevant
```
@Nullable
public Boolean getIsProductionRelevant()
```
    Constraints: none
    Original property name from the Odata EDM: IsProductionRelevant
    
    Items with this indicator are copied to the planned order, and the system calculates dependent requirements for them. When the planned order is converted to a production order, the system automatically copies these items to the production order.This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Returns:
    
    Indicates that the item is relevant to the production process.
  - getBOMItemIsPlantMaintRelevant
```
@Nullable
public Boolean getBOMItemIsPlantMaintRelevant()
```
    Constraints: none
    Original property name from the Odata EDM: BOMItemIsPlantMaintRelevant
    
    Items that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Returns:
    
    Indicates that this item is relevant to plant maintainance procedures.
  - getBOMItemIsCostingRelevant
```
@Nullable
public String getBOMItemIsCostingRelevant()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BOMItemIsCostingRelevant
    
    The extent is controlled by predefined factors for fixed and variable costs respectively.If this indicator is not set, the item is not costed.Indicator "x" determines that the item is always relevant to costing in all ways. This means that you do not need to maintain factors.You can enter factors if another indicator is entered.Factors between 0 and 1 are primarily used in inventory costing. These factors are not relevant to standard costing or order costing.Example: factor 0.5 in standard costing means that the item is costed with a factor of 1. Factor 0 means that the item is not costed.
    
    Returns:
    
    This key controls whether and to what extent this item is relevant to costing.
  - getIsEngineeringRelevant
```
@Nullable
public Boolean getIsEngineeringRelevant()
```
    Constraints: none
    Original property name from the Odata EDM: IsEngineeringRelevant
    
    This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
    
    Returns:
    
    Indicates that this item is relevant to the area responsible for producing a functional design for production.
  - getSpecialProcurementType
```
@Nullable
public String getSpecialProcurementType()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: SpecialProcurementType
    
    Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce a material in-house, it may be appropriate to choose Production in other plant.
    
    Returns:
    
    Allows you to define the procurement type more closely. The procurement type is determined from the material type.
  - getIsBOMRecursiveAllowed
```
@Nullable
public Boolean getIsBOMRecursiveAllowed()
```
    Constraints: none
    Original property name from the Odata EDM: IsBOMRecursiveAllowed
    
    If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
    
    Returns:
    
    Indicator: controls whether the system checks the BOM for recursiveness.
  - getOperationLeadTimeOffset
```
@Nullable
public BigDecimal getOperationLeadTimeOffset()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: OperationLeadTimeOffset
    
    (In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.---------------------------------------------------------Component Operation Lead-time offset (h) End dateM-01 0010 2+ 05.13.1998, 11 a.m.M-02 0020 2- 05.14.1998, 12 a.m.The component M-01 does not have to be available until 2 hours after the start time of the allocated operation 0010.Because the component M-02 must be available 2 hours before the start time of the allocated operation, the end time is 12 a.m.
    
    Returns:
    
    Time that the component lead-time offset states with reference to the start date of the allocated operation.
  - getOpsLeadTimeOffsetUnit
```
@Nullable
public String getOpsLeadTimeOffsetUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
    
    Returns:
    
    Unit for lead-time offset for operation
  - getIsMaterialProvision
```
@Nullable
public String getIsMaterialProvision()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsMaterialProvision
    
    In the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part. The following indicators are available:Refurbishment material to SC (value S in standard SAP system)Refurbishment material from SC (value X in standard SAP system)Subsequent delivery (value F in standard SAP system)If you do not enter information in this field, the components are provided to the subcontractor as consumable materials (initial value in the standard SAP system).Material provided by a vendorThis indicator controls material requirements planning. Maintain this indicator for BOM components only if the material master record of the header material supports subcontracting (Special procurement field).The special procurement key for subcontracting means that all components of the BOM are provided free of charge to a subcontractor for further processing. The items are copied to a subcontract order.If the item is provided to a vendor, do not enter any material provision indicator.Dependent requirements are generated for this item.If the item is already at a vendor's premises and is not provided by us, do enter an indicator.No dependent requirements are generated for this item.Material provided by a customerThis indicator is not currently active.
    
    Returns:
    
    This key indicates that the item is subject to material provision.
  - getBOMIsRecursive
```
@Nullable
public Boolean getBOMIsRecursive()
```
    Constraints: none
    Original property name from the Odata EDM: BOMIsRecursive
    
    In BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
    
    Returns:
    
    Indicator set by the system if the exploded BOM for an object contains the object itself as an item.
  - getDocumentIsCreatedByCAD
```
@Nullable
public Boolean getDocumentIsCreatedByCAD()
```
    Constraints: none
    Original property name from the Odata EDM: DocumentIsCreatedByCAD
    
    Returns:
    
    Information: data for the assembly/component was generated in a CAD system and transferred into the SAP system via an interface.
  - getDistrKeyCompConsumption
```
@Nullable
public String getDistrKeyCompConsumption()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: DistrKeyCompConsumption
    
    This means that the MRP controller can plan a daily supply of partial quantities (distributed over the validity period of the RS header) for repetitive manufacturing.
    
    Returns:
    
    Determines the split to be used for distributing the run schedule quantity (into partial quantities) over the validity period of the planned order or the production order. In so doing, the relationship between time and the consumption of components is established.
  - getDeliveryDurationInDays
```
@Nullable
public BigDecimal getDeliveryDurationInDays()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: DeliveryDurationInDays
    
    When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
    
    Returns:
    
    Gives the delivery time for the material in days.
  - getCreditor
```
@Nullable
public String getCreditor()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: Creditor
    
    Returns:
    
    Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.
  - getCostElement
```
@Nullable
public String getCostElement()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CostElement
    
    which is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
    
    Returns:
    
    Number of the G/L account
  - getSize1
```
@Nullable
public BigDecimal getSize1()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: Size1
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - getSize2
```
@Nullable
public BigDecimal getSize2()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: Size2
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - getSize3
```
@Nullable
public BigDecimal getSize3()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: Size3
    
    Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
    
    Returns:
    
    One dimension of the variable-size item, used as a variable in the variable-size item formula.
  - getUnitOfMeasureForSize1To3
```
@Nullable
public String getUnitOfMeasureForSize1To3()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: UnitOfMeasureForSize1To3
    
    Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
    
    Returns:
    
    Unit of measure for sizes 1 to 3.
  - getGoodsReceiptDuration
```
@Nullable
public BigDecimal getGoodsReceiptDuration()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: GoodsReceiptDuration
    
    Returns:
    
    Number of workdays required after receiving the material for inspection and placement into storage.
  - getPurchasingOrganization
```
@Nullable
public String getPurchasingOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: PurchasingOrganization
    
    Returns:
    
    Denotes the purchasing organization.
  - getRequiredComponent
```
@Nullable
public Boolean getRequiredComponent()
```
    Constraints: none
    Original property name from the Odata EDM: RequiredComponent
    
    Returns:
    
    If this class is used as a class item in a configurable object, this setting has the following effect in interactive configuration: the configuration is incomplete until the class item has been replaced by an object. In low-level configuration (MRP, for example), the "Required component" indicator has no further effects.
  - getMultipleSelectionAllowed
```
@Nullable
public Boolean getMultipleSelectionAllowed()
```
    Constraints: none
    Original property name from the Odata EDM: MultipleSelectionAllowed
    
    Returns:
    
    This indicator influences the status of a configuration in cases where a class item has been replaced by more than one object. Only if the configuration scenario allows manual changes to the BOM (order BOM or sales order with manual changes) can a class item be temporarily replaced by more than one object. However, before you save, the selection must be restricted to one object by using a manual object search. If you leave the configuration while the class item is still replaced by more than one object, only the first object is saved or transferred to the calling application. The "Multiple Selection" indicator has the following effect in interactive configuration: the configuration is still consistent if the class item has been replaced by more than one object. Without this indicator, the configuration is inconsistent if the class item has been replaced by more than one object. In low-level configuration (MRP, for example), only one object is used to replace the class, whether or not the "Multiple Selection" indicator is set.
  - getProdOrderIssueLocation
```
@Nullable
public String getProdOrderIssueLocation()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProdOrderIssueLocation
    
    In production, first there is a check as to whether an issue location is entered in the BOM item.If there is an issue location in the BOM item, this issue location is copied to the production order as a default value. Otherwise, the issue location is copied from the material master record (in the plant in which you created the BOM).This indicator is only supported for items that are relevant to production and plant maintenance.You cannot enter an issue location for a bulk material.
    
    Returns:
    
    Number of the issue location from which the material is issued during the production process. Backflush is posted to this issue location if required.
  - getMaterialIsCoProduct
```
@Nullable
public Boolean getMaterialIsCoProduct()
```
    Constraints: none
    Original property name from the Odata EDM: MaterialIsCoProduct
    
    Enter a negative quantity.Example: 6- You can only enter an item as a co-product if:The material master (MRP 2 view) contains the Material can be a co-product indicator. (For some material types, such as raw materials for example, the co-product indicator is hidden in the standard SAP system.)You enter the item as a stock item
    
    Returns:
    
    Indicator showing that the item is a co-product.
  - getExplosionType
```
@Nullable
public String getExplosionType()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ExplosionType
    
    You can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
    
    Returns:
    
    This is used to control the explosion of an item when determining dependent requirements.
  - getAlternativeItemGroup
```
@Nullable
public String getAlternativeItemGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AlternativeItemGroup
    
    As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:dependent requirements are determined in requirements planningdependent requirements are changed to a reservation in the production orderAlternative positions as informationYou can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.Enter the same character string to denote the alternative items of an alternative item group.Enter the same strategy for all alternative items in the alternative item group.Alternative items are valuated in the following way:Dependent requirements determinationRequirements planning determines the dependent requirements according to the usage probabilities that have been entered.If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created.Withdrawal postingYou can control the withdrawal posting for the resevation in the production order in the following way:Withdrawal according to usage probability (manual change is possible)Withdrawal if there is 100% availability(Check ranking order and strategy)Example: See Strategy for alternative position
    
    Returns:
    
    Consolidation of alternative items within a BOM. Every material in the assembly can be included in the alternative item group.
  - getAlternativeItemPriority
```
@Nullable
public String getAlternativeItemPriority()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AlternativeItemPriority
    
    With respect to withdrawal postings, the ranking order determines which material components from the alternative item group should be taken into account for the reservation in the production order.Withdrawal according to usage probabilityFor all items that should be reserved, maintain:strategy (value 1 or no entry)ranking order (only effects the material sort)usage probabilityWithdrawal on 100% availabilityFor all items that should be reserved, maintain:ranking orderIf you do not enter the ranking order, the system checks the items in the order that they are transmitted to the availability check.strategy (value 2)usage probabilityThree items (0060 und 0065 and 0070) are assigned to an alternative item group and are given the following values for ranking order:position ranking order0060 30065 20070 1This means that the system reads item 0070 first.
    
    Returns:
    
    Position of an item in an alternative item group.
  - getAlternativeItemStrategy
```
@Nullable
public String getAlternativeItemStrategy()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: AlternativeItemStrategy
    
    This strategy is ignored in material requirements planning (MRP).The withdrawal posting for the reservation in the production order can be selected as follows:According to usage probability (manual changes possible)For all items that you want to reserve, enter:Strategy (value 1 or no entry)Priority (only influences how materials are sorted)Usage probabilityWithdrawal if 100% availabilityFor all items that you want to reserve, enter:Strategy (value 2)PriorityIf you do not enter a priority, the system checks the items in the sequence in which they are transferred to the availability check.Usage probabilityEnter the same strategy for all alternative items in an alternative item group.Withdrawal if 100% availability (strategy 2)This strategy uses ATP logic to check availability in the defined ranking order.Gross requirements: 100 piecesM UP (%) RO RQ ATP qty Issue qtyA 20 1 20 30 0B 30 2 30 150 100C 50 3 50 180 0KeyM MaterialUP Usage probabilityRO Ranking orderRQ Requirements quantityThe first material in the ranking order that is supplied 100% on the requirement date is reserved in the required quantity (material B).If a partial withdrawal is carried out in a production order, when additional partial withdrawals take place, no further checks are carried out for this production order. Additional partial withdrawals result from the alternative item, from which the first withdrawal took place.If when using strategy 2 none of the alternative items cover the requirements 100%, the availability check for all items will confirm the available. A reservation only occurs for the available quantity.
    
    Returns:
    
    This value defines how items in an alternative group are selected for withdrawal postings.
  - getUsageProbabilityPercent
```
@Nullable
public BigDecimal getUsageProbabilityPercent()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: UsageProbabilityPercent
    
    The usage probability is always taken into account for requirements planning.Maintain selected usage probabilityRequirements planning for alternative items is based on the usage probability.Quantities are suggested based on the usage probability for the withdrawal posting according to strategy 1. You can plan in excess for the alternative items since the usage probability is not limited to 100%. You can change the proposed quantities. Maintain no usage probability If you do not enter a usage probability, the alternative item just serves as information that can be evaluated, for example, in a situation with a missing part.You receive a warning since dependent requirements with 0 as quantity are created.Withdrawal based on usage probabilityStrategy: value 1An alternative item group is maintained for each assembly. This alternative item group contains four materials with differing usage probabilities. Dependent requirements are passed on with 100 as quantity.Material Usage probability (%) RequirementM-1 70 70M-2 20 20M-3 20 20M-4 0 no requirementIn this case, the materials are planned in excess since the sum of the usage probabilities is greater than 100%.
    
    Returns:
    
    Percentage probability that a material will be used in the assembly.
  - getFollowUpGroup
```
@Nullable
public String getFollowUpGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: FollowUpGroup
    
    You can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials. When an item (main item) is discontinued, another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: discontinuation indicator value 1Material of the dependent item: value 3Settings in the BOM:The main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.You can only maintain an item as a follow-up item when you enter it for the first time. The field value cannot be changed after you have entered and saved the item.The follow-up item(s) that are to replace the item to be discontinued must have the same value in the Discontinuation group field as the item to be discontinued has in the Follow-up group field (see the example below).The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.You can only maintain the follow-up group for one item if:the component is planned to a schedule (for example, a warehouse item)the base unit of measure of the materials is identicalExample of a simple discontinuationfItem 0010 to be discontinued (material M-1) is replaced by item 0010 to be introduced (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Material Discontinuation group Follow-up group0010 M-1 A1 -0010 M-2 - A1Example of a parallel discontinuationthe items 0010 (material M-1) and 0011 (material M-2) are replaced by the items 0010 (material M-3) and 0011 (material M-4) to be ntroduced.Discontinuation indicator in the material master record:M-1: Value 1 (main discontinued item)M-2: Value 3 (dependent discontinued item)Item Material Discontinuation group Follow-up group0010 M-1 A1 -0011 M-2 A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Returns:
    
    This is a freely-definable character string which is assigned to linked follow-up items in a bill of material. The follow-up group shows which follow-up item(s) are to replace the item to be discontinued.
  - getDiscontinuationGroup
```
@Nullable
public String getDiscontinuationGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DiscontinuationGroup
    
    You can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group. If an item is to be discontinued (main item), another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: value 1Material of the dependent item: value 3Settings in the BOM:Both the main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.Both the follow-up group of the items to be introduced and the discontinuation group of the items to be discontinued must have the same value.You can only enter a discontinuation group for an item if the discontinuation indicator (material master, MRP 4 view) supports discontinuation.A discontinued item is replaced by a follow-up item. In the follow-up item, you maintain a follow-up group.Example for a simple discontinuationItem 0010 (material M-1) is to be discontinued and replaced by follow-up item 0010 (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Mat. DisconGrp FollGrp 0010 M-1 A1 -0010 M-2 - A1Example for a Parallel discontinuationItems 0010 (material M-1) and 0011 (material M-2) to be discontinued are replaced by items 0010 (material M-3) and 0011 (material M-4) to be introduced.Discontinuation indicator in the material master record:M-1: value 1 (main discontinued item)M-2: value 3 (dependent discontinued item)Item Mat. Discontinuation group Follow-up group0010 M-1 ,A1 -0011 M-2 ,A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
    
    Returns:
    
    This freely-definable character string is used to group together related items to be discontinued in a BOM.
  - getIsConfigurableBOM
```
@Nullable
public String getIsConfigurableBOM()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsConfigurableBOM
    
    Returns:
    
    Selection indicator for configurable BOMs
  - getReferencePoint
```
@Nullable
public String getReferencePoint()
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: ReferencePoint
    
    Returns:
    
    Creates a logical link between BOM items and network activities.
  - getLeadTimeOffset
```
@Nullable
public BigDecimal getLeadTimeOffset()
```
    Constraints: Not nullable, Precision: 3, Scale: 0
    Original property name from the Odata EDM: LeadTimeOffset
    
    This value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
    
    Returns:
    
    This value shows the lead-time offset (in workdays) for the component in relation to the start date for production of the superior assembly.
  - getProductionSupplyArea
```
@Nullable
public String getProductionSupplyArea()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ProductionSupplyArea
    
    The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
    
    Returns:
    
    The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.
  - getIsDeleted
```
@Nullable
public Boolean getIsDeleted()
```
    Constraints: none
    Original property name from the Odata EDM: IsDeleted
    
    This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
    
    Returns:
    
    Indicator showing that the BOM header or the BOM item has been deleted with reference to the change number.
  - getIsALE
```
@Nullable
public Boolean getIsALE()
```
    Constraints: none
    Original property name from the Odata EDM: IsALE
    
    Returns:
    
    Shows that data of the assembly or component has been distributed to the SAP system using ALE.
  - getLastChangeDateTime
```
@Nullable
public ZonedDateTime getLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Returns:
    
    The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - getSalesOrder
```
@Nullable
public String getSalesOrder()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesOrder
    
    If, for example, you want to display or change a sales document and you have only the purchase order number from the customer, you can use a matchcode to find the document.You created a sales order which refers to customer purchase order number 12544-D. To locate the sales order, you can enter =a.12544-D in the sales document field.
    
    Returns:
    
    The number that uniquely identifies the sales document.
  - getSalesOrderItem
```
@Nullable
public String getSalesOrderItem()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesOrderItem
    
    Returns:
    
    The number that uniquely identifies the item in the sales document.
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class VdmObject<SalesOrderBOMItem>
  - equals
```
public boolean equals(@Nullable
                      Object o)
```
    Overrides:
    
    equals in class VdmObject<SalesOrderBOMItem>
  - canEqual
```
protected boolean canEqual(@Nullable
                           Object other)
```
    Overrides:
    
    canEqual in class VdmObject<SalesOrderBOMItem>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<SalesOrderBOMItem>

Class SalesOrderBOMItem

Nested Class Summary

Field Summary

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

BILL_OF_MATERIAL

BILL_OF_MATERIAL_CATEGORY

BILL_OF_MATERIAL_VARIANT

BILL_OF_MATERIAL_ITEM_NODE_NUMBER

HEADER_CHANGE_DOCUMENT

MATERIAL

PLANT

BILL_OF_MATERIAL_VARIANT_USAGE

BILL_OF_MATERIAL_ITEM_UUID

BOM_ITEM_INTERNAL_CHANGE_COUNT

VALIDITY_START_DATE

VALIDITY_END_DATE

ENGINEERING_CHANGE_DOC_FOR_EDIT

ENGINEERING_CHANGE_DOCUMENT

CHG_TO_ENGINEERING_CHG_DOCUMENT

INHERITED_NODE_NUMBER_FOR_BOM_ITEM

BOM_ITEM_RECORD_CREATION_DATE

BOM_ITEM_CREATED_BY_USER

BOM_ITEM_LAST_CHANGE_DATE

BOM_ITEM_LAST_CHANGED_BY_USER

BILL_OF_MATERIAL_COMPONENT

BILL_OF_MATERIAL_ITEM_CATEGORY

BILL_OF_MATERIAL_ITEM_NUMBER

BILL_OF_MATERIAL_ITEM_UNIT

BILL_OF_MATERIAL_ITEM_QUANTITY

IS_ASSEMBLY

IS_SUB_ITEM

BOM_ITEM_SORTER

FIXED_QUANTITY

BOM_ITEM_HAS_FIXED_QUANTITY

PURCHASING_GROUP

CURRENCY

MATERIAL_COMPONENT_PRICE

IDENTIFIER_BOM_ITEM

MATERIAL_PRICE_UNIT_QTY

COMPONENT_SCRAP_IN_PERCENT

OPERATION_SCRAP_IN_PERCENT

IS_NET_SCRAP

NUMBER_OF_VARIABLE_SIZE_ITEM

QUANTITY_VARIABLE_SIZE_ITEM

FORMULA_KEY

COMPONENT_DESCRIPTION

BOM_ITEM_DESCRIPTION

BOM_ITEM_TEXT2

MATERIAL_GROUP

DOCUMENT_TYPE

DOC_NUMBER

DOCUMENT_VERSION

DOCUMENT_PART

CLASS_NUMBER

CLASS_TYPE

RESULTING_ITEM_CATEGORY

DEPENDENCY_OBJECT_NUMBER

OBJECT_TYPE

IS_CLASSIFICATION_RELEVANT

IS_BULK_MATERIAL

BOM_ITEM_IS_SPARE_PART

BOM_ITEM_IS_SALES_RELEVANT

IS_PRODUCTION_RELEVANT

BOM_ITEM_IS_PLANT_MAINT_RELEVANT

BOM_ITEM_IS_COSTING_RELEVANT

IS_ENGINEERING_RELEVANT

SPECIAL_PROCUREMENT_TYPE

IS_BOM_RECURSIVE_ALLOWED

OPERATION_LEAD_TIME_OFFSET

OPS_LEAD_TIME_OFFSET_UNIT

IS_MATERIAL_PROVISION

BOM_IS_RECURSIVE

DOCUMENT_IS_CREATED_BY_CAD