public class BillOfMaterialItem extends VdmEntity<BillOfMaterialItem>
| Modifier and Type | Class and Description |
|---|---|
static class |
BillOfMaterialItem.BillOfMaterialItemBuilder |
| Modifier and Type | Field and Description |
|---|---|
static BillOfMaterialItemSelectable |
ALL_FIELDS
Selector for all available fields of BillOfMaterialItem.
|
static BillOfMaterialItemField<String> |
ALTERNATIVE_ITEM_GROUP
Use with available fluent helpers to apply the AlternativeItemGroup field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL
Use with available fluent helpers to apply the BillOfMaterial field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_CATEGORY
Use with available fluent helpers to apply the BillOfMaterialCategory field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_COMPONENT
Use with available fluent helpers to apply the BillOfMaterialComponent field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_ITEM_CATEGORY
Use with available fluent helpers to apply the BillOfMaterialItemCategory field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_ITEM_NODE_NUMBER
Use with available fluent helpers to apply the BillOfMaterialItemNodeNumber field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_ITEM_NUMBER
Use with available fluent helpers to apply the BillOfMaterialItemNumber field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
BILL_OF_MATERIAL_ITEM_QUANTITY
Use with available fluent helpers to apply the BillOfMaterialItemQuantity field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_ITEM_UNIT
Use with available fluent helpers to apply the BillOfMaterialItemUnit field to query operations.
|
static BillOfMaterialItemField<UUID> |
BILL_OF_MATERIAL_ITEM_UUID
Use with available fluent helpers to apply the BillOfMaterialItemUUID field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_VARIANT
Use with available fluent helpers to apply the BillOfMaterialVariant field to query operations.
|
static BillOfMaterialItemField<String> |
BILL_OF_MATERIAL_VERSION
Use with available fluent helpers to apply the BillOfMaterialVersion field to query operations.
|
static BillOfMaterialItemField<Boolean> |
BOM_IS_RECURSIVE
Use with available fluent helpers to apply the BOMIsRecursive field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_CREATED_BY_USER
Use with available fluent helpers to apply the BOMItemCreatedByUser field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_DESCRIPTION
Use with available fluent helpers to apply the BOMItemDescription field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_INTERNAL_CHANGE_COUNT
Use with available fluent helpers to apply the BOMItemInternalChangeCount field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_IS_COSTING_RELEVANT
Use with available fluent helpers to apply the BOMItemIsCostingRelevant field to query operations.
|
static BillOfMaterialItemField<Boolean> |
BOM_ITEM_IS_PLANT_MAINT_RELEVANT
Use with available fluent helpers to apply the BOMItemIsPlantMaintRelevant field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_IS_SALES_RELEVANT
Use with available fluent helpers to apply the BOMItemIsSalesRelevant field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_IS_SPARE_PART
Use with available fluent helpers to apply the BOMItemIsSparePart field to query operations.
|
static BillOfMaterialItemField<Calendar> |
BOM_ITEM_LAST_CHANGE_DATE
Use with available fluent helpers to apply the BOMItemLastChangeDate field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_LAST_CHANGED_BY_USER
Use with available fluent helpers to apply the BOMItemLastChangedByUser field to query operations.
|
static BillOfMaterialItemField<Calendar> |
BOM_ITEM_RECORD_CREATION_DATE
Use with available fluent helpers to apply the BOMItemRecordCreationDate field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_SORTER
Use with available fluent helpers to apply the BOMItemSorter field to query operations.
|
static BillOfMaterialItemField<String> |
BOM_ITEM_TEXT2
Use with available fluent helpers to apply the BOMItemText2 field to query operations.
|
static BillOfMaterialItemField<String> |
CHG_TO_ENGINEERING_CHG_DOCUMENT
Use with available fluent helpers to apply the ChgToEngineeringChgDocument field to query operations.
|
static BillOfMaterialItemField<String> |
CLASS_NUMBER
Use with available fluent helpers to apply the ClassNumber field to query operations.
|
static BillOfMaterialItemField<String> |
CLASS_TYPE
Use with available fluent helpers to apply the ClassType field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
COMPONENT_SCRAP_IN_PERCENT
Use with available fluent helpers to apply the ComponentScrapInPercent field to query operations.
|
static BillOfMaterialItemField<String> |
COST_ELEMENT
Use with available fluent helpers to apply the CostElement field to query operations.
|
static BillOfMaterialItemField<String> |
CREDITOR
Use with available fluent helpers to apply the Creditor field to query operations.
|
static BillOfMaterialItemField<String> |
CURRENCY
Use with available fluent helpers to apply the Currency field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
DELIVERY_DURATION_IN_DAYS
Use with available fluent helpers to apply the DeliveryDurationInDays field to query operations.
|
static BillOfMaterialItemField<String> |
DEPENDENCY_OBJECT_NUMBER
Use with available fluent helpers to apply the DependencyObjectNumber field to query operations.
|
static BillOfMaterialItemField<String> |
DISCONTINUATION_GROUP
Use with available fluent helpers to apply the DiscontinuationGroup field to query operations.
|
static BillOfMaterialItemField<String> |
DISTR_KEY_COMP_CONSUMPTION
Use with available fluent helpers to apply the DistrKeyCompConsumption field to query operations.
|
static BillOfMaterialItemField<String> |
DOC_NUMBER
Use with available fluent helpers to apply the DocNumber field to query operations.
|
static BillOfMaterialItemField<Boolean> |
DOCUMENT_IS_CREATED_BY_CAD
Use with available fluent helpers to apply the DocumentIsCreatedByCAD field to query operations.
|
static BillOfMaterialItemField<String> |
DOCUMENT_PART
Use with available fluent helpers to apply the DocumentPart field to query operations.
|
static BillOfMaterialItemField<String> |
DOCUMENT_TYPE
Use with available fluent helpers to apply the DocumentType field to query operations.
|
static BillOfMaterialItemField<String> |
DOCUMENT_VERSION
Use with available fluent helpers to apply the DocumentVersion field to query operations.
|
static BillOfMaterialItemField<String> |
ENGINEERING_CHANGE_DOCUMENT
Use with available fluent helpers to apply the EngineeringChangeDocument field to query operations.
|
static BillOfMaterialItemField<String> |
EXPLOSION_TYPE
Use with available fluent helpers to apply the ExplosionType field to query operations.
|
static BillOfMaterialItemField<Boolean> |
FIXED_QUANTITY
Use with available fluent helpers to apply the FixedQuantity field to query operations.
|
static BillOfMaterialItemField<String> |
FOLLOW_UP_GROUP
Use with available fluent helpers to apply the FollowUpGroup field to query operations.
|
static BillOfMaterialItemField<String> |
FORMULA_KEY
Use with available fluent helpers to apply the FormulaKey field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
GOODS_RECEIPT_DURATION
Use with available fluent helpers to apply the GoodsReceiptDuration field to query operations.
|
static BillOfMaterialItemField<String> |
IDENTIFIER_BOM_ITEM
Use with available fluent helpers to apply the IdentifierBOMItem field to query operations.
|
static BillOfMaterialItemField<String> |
INHERITED_NODE_NUMBER_FOR_BOM_ITEM
Use with available fluent helpers to apply the InheritedNodeNumberForBOMItem field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_ALE
Use with available fluent helpers to apply the IsALE field to query operations.
|
static BillOfMaterialItemField<String> |
IS_ASSEMBLY
Use with available fluent helpers to apply the IsAssembly field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_BOM_RECURSIVE_ALLOWED
Use with available fluent helpers to apply the IsBOMRecursiveAllowed field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_BULK_MATERIAL
Use with available fluent helpers to apply the IsBulkMaterial field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_CLASSIFICATION_RELEVANT
Use with available fluent helpers to apply the IsClassificationRelevant field to query operations.
|
static BillOfMaterialItemField<String> |
IS_CONFIGURABLE_BOM
Use with available fluent helpers to apply the IsConfigurableBOM field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_DELETED
Use with available fluent helpers to apply the IsDeleted field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_ENGINEERING_RELEVANT
Use with available fluent helpers to apply the IsEngineeringRelevant field to query operations.
|
static BillOfMaterialItemField<String> |
IS_MATERIAL_PROVISION
Use with available fluent helpers to apply the IsMaterialProvision field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_NET_SCRAP
Use with available fluent helpers to apply the IsNetScrap field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_PRODUCTION_RELEVANT
Use with available fluent helpers to apply the IsProductionRelevant field to query operations.
|
static BillOfMaterialItemField<Boolean> |
IS_SUB_ITEM
Use with available fluent helpers to apply the IsSubItem field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
LEAD_TIME_OFFSET
Use with available fluent helpers to apply the LeadTimeOffset field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
MATERIAL_COMPONENT_PRICE
Use with available fluent helpers to apply the MaterialComponentPrice field to query operations.
|
static BillOfMaterialItemField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static BillOfMaterialItemField<Boolean> |
MATERIAL_IS_CO_PRODUCT
Use with available fluent helpers to apply the MaterialIsCoProduct field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
MATERIAL_PRICE_UNIT_QTY
Use with available fluent helpers to apply the MaterialPriceUnitQty field to query operations.
|
static BillOfMaterialItemField<Boolean> |
MULTIPLE_SELECTION_ALLOWED
Use with available fluent helpers to apply the MultipleSelectionAllowed field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
NUMBER_OF_VARIABLE_SIZE_ITEM
Use with available fluent helpers to apply the NumberOfVariableSizeItem field to query operations.
|
static BillOfMaterialItemField<String> |
OBJECT_TYPE
Use with available fluent helpers to apply the ObjectType field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
OPERATION_LEAD_TIME_OFFSET
Use with available fluent helpers to apply the OperationLeadTimeOffset field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
OPERATION_SCRAP_IN_PERCENT
Use with available fluent helpers to apply the OperationScrapInPercent field to query operations.
|
static BillOfMaterialItemField<String> |
OPS_LEAD_TIME_OFFSET_UNIT
Use with available fluent helpers to apply the OpsLeadTimeOffsetUnit field to query operations.
|
static BillOfMaterialItemField<String> |
PROD_ORDER_ISSUE_LOCATION
Use with available fluent helpers to apply the ProdOrderIssueLocation field to query operations.
|
static BillOfMaterialItemField<String> |
PRODUCTION_SUPPLY_AREA
Use with available fluent helpers to apply the ProductionSupplyArea field to query operations.
|
static BillOfMaterialItemField<String> |
PURCHASING_GROUP
Use with available fluent helpers to apply the PurchasingGroup field to query operations.
|
static BillOfMaterialItemField<String> |
PURCHASING_ORGANIZATION
Use with available fluent helpers to apply the PurchasingOrganization field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
QUANTITY_VARIABLE_SIZE_ITEM
Use with available fluent helpers to apply the QuantityVariableSizeItem field to query operations.
|
static BillOfMaterialItemField<String> |
REFERENCE_POINT
Use with available fluent helpers to apply the ReferencePoint field to query operations.
|
static BillOfMaterialItemField<Boolean> |
REQUIRED_COMPONENT
Use with available fluent helpers to apply the RequiredComponent field to query operations.
|
static BillOfMaterialItemField<String> |
RESULTING_ITEM_CATEGORY
Use with available fluent helpers to apply the ResultingItemCategory field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
SIZE1
Use with available fluent helpers to apply the Size1 field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
SIZE2
Use with available fluent helpers to apply the Size2 field to query operations.
|
static BillOfMaterialItemField<BigDecimal> |
SIZE3
Use with available fluent helpers to apply the Size3 field to query operations.
|
static BillOfMaterialItemField<String> |
SPECIAL_PROCUREMENT_TYPE
Use with available fluent helpers to apply the SpecialProcurementType field to query operations.
|
static BillOfMaterialItemField<String> |
UNIT_OF_MEASURE_FOR_SIZE1_TO3
Use with available fluent helpers to apply the UnitOfMeasureForSize1To3 field to query operations.
|
static BillOfMaterialItemField<Calendar> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static BillOfMaterialItemField<Calendar> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
| Constructor and Description |
|---|
BillOfMaterialItem() |
BillOfMaterialItem(UUID billOfMaterialItemUUID,
String billOfMaterialCategory,
String billOfMaterial,
String billOfMaterialVariant,
String billOfMaterialVersion,
String billOfMaterialItemNodeNumber,
String bOMItemInternalChangeCount,
Calendar validityStartDate,
Calendar validityEndDate,
String engineeringChangeDocument,
String chgToEngineeringChgDocument,
String inheritedNodeNumberForBOMItem,
Calendar bOMItemRecordCreationDate,
String bOMItemCreatedByUser,
Calendar bOMItemLastChangeDate,
String bOMItemLastChangedByUser,
String billOfMaterialComponent,
String billOfMaterialItemCategory,
String billOfMaterialItemNumber,
String billOfMaterialItemUnit,
BigDecimal billOfMaterialItemQuantity,
String isAssembly,
Boolean isSubItem,
String bOMItemSorter,
Boolean fixedQuantity,
String purchasingGroup,
String currency,
BigDecimal materialComponentPrice,
String identifierBOMItem,
BigDecimal materialPriceUnitQty,
BigDecimal componentScrapInPercent,
BigDecimal operationScrapInPercent,
Boolean isNetScrap,
BigDecimal numberOfVariableSizeItem,
BigDecimal quantityVariableSizeItem,
String formulaKey,
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 followUpGroup,
String discontinuationGroup,
String isConfigurableBOM,
String referencePoint,
BigDecimal leadTimeOffset,
String productionSupplyArea,
Boolean isDeleted,
Boolean isALE,
ErpConfigContext erpConfigContext) |
| Modifier and Type | Method and Description |
|---|---|
static BillOfMaterialItem.BillOfMaterialItemBuilder |
builder() |
boolean |
equals(Object o) |
static <T> BillOfMaterialItemField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAlternativeItemGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getBillOfMaterial()
Constraints: Not nullable, Maximum length: 8
|
String |
getBillOfMaterialCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getBillOfMaterialComponent()
Constraints: Not nullable, Maximum length: 40
|
String |
getBillOfMaterialItemCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getBillOfMaterialItemNodeNumber()
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()
(Key Field) Constraints: Not nullable
|
String |
getBillOfMaterialVariant()
Constraints: Not nullable, Maximum length: 2
|
String |
getBillOfMaterialVersion()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getBOMIsRecursive()
Constraints: none
|
String |
getBOMItemCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
String |
getBOMItemDescription()
Constraints: Not nullable, Maximum length: 40
|
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
|
Calendar |
getBOMItemLastChangeDate()
Constraints: Not nullable, Precision: 0
|
String |
getBOMItemLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
Calendar |
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
|
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
|
BigDecimal |
getDeliveryDurationInDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getDependencyObjectNumber()
Constraints: Not nullable, Maximum length: 18
|
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 |
getEngineeringChangeDocument()
Constraints: Not nullable, Maximum length: 12
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
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 |
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
|
BigDecimal |
getLeadTimeOffset()
Constraints: Not nullable, Precision: 3, Scale: 0
|
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 |
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
|
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<BillOfMaterialItem> |
getType() |
String |
getUnitOfMeasureForSize1To3()
Constraints: Not nullable, Maximum length: 3
|
Calendar |
getValidityEndDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
getValidityStartDate()
Constraints: Not nullable, Precision: 0
|
int |
hashCode() |
void |
setAlternativeItemGroup(String alternativeItemGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setBillOfMaterial(String billOfMaterial)
Constraints: Not nullable, Maximum length: 8
|
void |
setBillOfMaterialCategory(String billOfMaterialCategory)
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)
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)
(Key Field) Constraints: Not nullable
|
void |
setBillOfMaterialVariant(String billOfMaterialVariant)
Constraints: Not nullable, Maximum length: 2
|
void |
setBillOfMaterialVersion(String billOfMaterialVersion)
Constraints: Not nullable, Maximum length: 4
|
void |
setBOMIsRecursive(Boolean bOMIsRecursive)
Constraints: none
|
void |
setBOMItemCreatedByUser(String bOMItemCreatedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setBOMItemDescription(String bOMItemDescription)
Constraints: Not nullable, Maximum length: 40
|
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(Calendar bOMItemLastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setBOMItemLastChangedByUser(String bOMItemLastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setBOMItemRecordCreationDate(Calendar 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 |
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 |
setEngineeringChangeDocument(String engineeringChangeDocument)
Constraints: Not nullable, Maximum length: 12
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
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 |
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 |
setLeadTimeOffset(BigDecimal leadTimeOffset)
Constraints: Not nullable, Precision: 3, Scale: 0
|
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 |
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 |
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 |
setValidityEndDate(Calendar validityEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setValidityStartDate(Calendar validityStartDate)
Constraints: Not nullable, Precision: 0
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final BillOfMaterialItemSelectable ALL_FIELDS
public static final BillOfMaterialItemField<UUID> BILL_OF_MATERIAL_ITEM_UUID
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_CATEGORY
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_VARIANT
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_VERSION
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_ITEM_NODE_NUMBER
public static final BillOfMaterialItemField<String> BOM_ITEM_INTERNAL_CHANGE_COUNT
public static final BillOfMaterialItemField<Calendar> VALIDITY_START_DATE
public static final BillOfMaterialItemField<Calendar> VALIDITY_END_DATE
public static final BillOfMaterialItemField<String> ENGINEERING_CHANGE_DOCUMENT
public static final BillOfMaterialItemField<String> CHG_TO_ENGINEERING_CHG_DOCUMENT
public static final BillOfMaterialItemField<String> INHERITED_NODE_NUMBER_FOR_BOM_ITEM
public static final BillOfMaterialItemField<Calendar> BOM_ITEM_RECORD_CREATION_DATE
public static final BillOfMaterialItemField<String> BOM_ITEM_CREATED_BY_USER
public static final BillOfMaterialItemField<Calendar> BOM_ITEM_LAST_CHANGE_DATE
public static final BillOfMaterialItemField<String> BOM_ITEM_LAST_CHANGED_BY_USER
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_COMPONENT
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_ITEM_CATEGORY
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_ITEM_NUMBER
public static final BillOfMaterialItemField<String> BILL_OF_MATERIAL_ITEM_UNIT
public static final BillOfMaterialItemField<BigDecimal> BILL_OF_MATERIAL_ITEM_QUANTITY
public static final BillOfMaterialItemField<String> IS_ASSEMBLY
public static final BillOfMaterialItemField<Boolean> IS_SUB_ITEM
public static final BillOfMaterialItemField<String> BOM_ITEM_SORTER
public static final BillOfMaterialItemField<Boolean> FIXED_QUANTITY
public static final BillOfMaterialItemField<String> PURCHASING_GROUP
public static final BillOfMaterialItemField<String> CURRENCY
public static final BillOfMaterialItemField<BigDecimal> MATERIAL_COMPONENT_PRICE
public static final BillOfMaterialItemField<String> IDENTIFIER_BOM_ITEM
public static final BillOfMaterialItemField<BigDecimal> MATERIAL_PRICE_UNIT_QTY
public static final BillOfMaterialItemField<BigDecimal> COMPONENT_SCRAP_IN_PERCENT
public static final BillOfMaterialItemField<BigDecimal> OPERATION_SCRAP_IN_PERCENT
public static final BillOfMaterialItemField<Boolean> IS_NET_SCRAP
public static final BillOfMaterialItemField<BigDecimal> NUMBER_OF_VARIABLE_SIZE_ITEM
public static final BillOfMaterialItemField<BigDecimal> QUANTITY_VARIABLE_SIZE_ITEM
public static final BillOfMaterialItemField<String> FORMULA_KEY
public static final BillOfMaterialItemField<String> BOM_ITEM_DESCRIPTION
public static final BillOfMaterialItemField<String> BOM_ITEM_TEXT2
public static final BillOfMaterialItemField<String> MATERIAL_GROUP
public static final BillOfMaterialItemField<String> DOCUMENT_TYPE
public static final BillOfMaterialItemField<String> DOC_NUMBER
public static final BillOfMaterialItemField<String> DOCUMENT_VERSION
public static final BillOfMaterialItemField<String> DOCUMENT_PART
public static final BillOfMaterialItemField<String> CLASS_NUMBER
public static final BillOfMaterialItemField<String> CLASS_TYPE
public static final BillOfMaterialItemField<String> RESULTING_ITEM_CATEGORY
public static final BillOfMaterialItemField<String> DEPENDENCY_OBJECT_NUMBER
public static final BillOfMaterialItemField<String> OBJECT_TYPE
public static final BillOfMaterialItemField<Boolean> IS_CLASSIFICATION_RELEVANT
public static final BillOfMaterialItemField<Boolean> IS_BULK_MATERIAL
public static final BillOfMaterialItemField<String> BOM_ITEM_IS_SPARE_PART
public static final BillOfMaterialItemField<String> BOM_ITEM_IS_SALES_RELEVANT
public static final BillOfMaterialItemField<Boolean> IS_PRODUCTION_RELEVANT
public static final BillOfMaterialItemField<Boolean> BOM_ITEM_IS_PLANT_MAINT_RELEVANT
public static final BillOfMaterialItemField<String> BOM_ITEM_IS_COSTING_RELEVANT
public static final BillOfMaterialItemField<Boolean> IS_ENGINEERING_RELEVANT
public static final BillOfMaterialItemField<String> SPECIAL_PROCUREMENT_TYPE
public static final BillOfMaterialItemField<Boolean> IS_BOM_RECURSIVE_ALLOWED
public static final BillOfMaterialItemField<BigDecimal> OPERATION_LEAD_TIME_OFFSET
public static final BillOfMaterialItemField<String> OPS_LEAD_TIME_OFFSET_UNIT
public static final BillOfMaterialItemField<String> IS_MATERIAL_PROVISION
public static final BillOfMaterialItemField<Boolean> BOM_IS_RECURSIVE
public static final BillOfMaterialItemField<Boolean> DOCUMENT_IS_CREATED_BY_CAD
public static final BillOfMaterialItemField<String> DISTR_KEY_COMP_CONSUMPTION
public static final BillOfMaterialItemField<BigDecimal> DELIVERY_DURATION_IN_DAYS
public static final BillOfMaterialItemField<String> CREDITOR
public static final BillOfMaterialItemField<String> COST_ELEMENT
public static final BillOfMaterialItemField<BigDecimal> SIZE1
public static final BillOfMaterialItemField<BigDecimal> SIZE2
public static final BillOfMaterialItemField<BigDecimal> SIZE3
public static final BillOfMaterialItemField<String> UNIT_OF_MEASURE_FOR_SIZE1_TO3
public static final BillOfMaterialItemField<BigDecimal> GOODS_RECEIPT_DURATION
public static final BillOfMaterialItemField<String> PURCHASING_ORGANIZATION
public static final BillOfMaterialItemField<Boolean> REQUIRED_COMPONENT
public static final BillOfMaterialItemField<Boolean> MULTIPLE_SELECTION_ALLOWED
public static final BillOfMaterialItemField<String> PROD_ORDER_ISSUE_LOCATION
public static final BillOfMaterialItemField<Boolean> MATERIAL_IS_CO_PRODUCT
public static final BillOfMaterialItemField<String> EXPLOSION_TYPE
public static final BillOfMaterialItemField<String> ALTERNATIVE_ITEM_GROUP
public static final BillOfMaterialItemField<String> FOLLOW_UP_GROUP
public static final BillOfMaterialItemField<String> DISCONTINUATION_GROUP
public static final BillOfMaterialItemField<String> IS_CONFIGURABLE_BOM
public static final BillOfMaterialItemField<String> REFERENCE_POINT
public static final BillOfMaterialItemField<BigDecimal> LEAD_TIME_OFFSET
public static final BillOfMaterialItemField<String> PRODUCTION_SUPPLY_AREA
public static final BillOfMaterialItemField<Boolean> IS_DELETED
public static final BillOfMaterialItemField<Boolean> IS_ALE
@Generated(value="lombok") public BillOfMaterialItem()
@ConstructorProperties(value={"billOfMaterialItemUUID","billOfMaterialCategory","billOfMaterial","billOfMaterialVariant","billOfMaterialVersion","billOfMaterialItemNodeNumber","bOMItemInternalChangeCount","validityStartDate","validityEndDate","engineeringChangeDocument","chgToEngineeringChgDocument","inheritedNodeNumberForBOMItem","bOMItemRecordCreationDate","bOMItemCreatedByUser","bOMItemLastChangeDate","bOMItemLastChangedByUser","billOfMaterialComponent","billOfMaterialItemCategory","billOfMaterialItemNumber","billOfMaterialItemUnit","billOfMaterialItemQuantity","isAssembly","isSubItem","bOMItemSorter","fixedQuantity","purchasingGroup","currency","materialComponentPrice","identifierBOMItem","materialPriceUnitQty","componentScrapInPercent","operationScrapInPercent","isNetScrap","numberOfVariableSizeItem","quantityVariableSizeItem","formulaKey","bOMItemDescription","bOMItemText2","materialGroup","documentType","docNumber","documentVersion","documentPart","classNumber","classType","resultingItemCategory","dependencyObjectNumber","objectType","isClassificationRelevant","isBulkMaterial","bOMItemIsSparePart","bOMItemIsSalesRelevant","isProductionRelevant","bOMItemIsPlantMaintRelevant","bOMItemIsCostingRelevant","isEngineeringRelevant","specialProcurementType","isBOMRecursiveAllowed","operationLeadTimeOffset","opsLeadTimeOffsetUnit","isMaterialProvision","bOMIsRecursive","documentIsCreatedByCAD","distrKeyCompConsumption","deliveryDurationInDays","creditor","costElement","size1","size2","size3","unitOfMeasureForSize1To3","goodsReceiptDuration","purchasingOrganization","requiredComponent","multipleSelectionAllowed","prodOrderIssueLocation","materialIsCoProduct","explosionType","alternativeItemGroup","followUpGroup","discontinuationGroup","isConfigurableBOM","referencePoint","leadTimeOffset","productionSupplyArea","isDeleted","isALE","erpConfigContext"}) @Generated(value="lombok") public BillOfMaterialItem(@Nullable UUID billOfMaterialItemUUID, @Nullable String billOfMaterialCategory, @Nullable String billOfMaterial, @Nullable String billOfMaterialVariant, @Nullable String billOfMaterialVersion, @Nullable String billOfMaterialItemNodeNumber, @Nullable String bOMItemInternalChangeCount, @Nullable Calendar validityStartDate, @Nullable Calendar validityEndDate, @Nullable String engineeringChangeDocument, @Nullable String chgToEngineeringChgDocument, @Nullable String inheritedNodeNumberForBOMItem, @Nullable Calendar bOMItemRecordCreationDate, @Nullable String bOMItemCreatedByUser, @Nullable Calendar 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 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 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 followUpGroup, @Nullable String discontinuationGroup, @Nullable String isConfigurableBOM, @Nullable String referencePoint, @Nullable BigDecimal leadTimeOffset, @Nullable String productionSupplyArea, @Nullable Boolean isDeleted, @Nullable Boolean isALE, @Nullable ErpConfigContext erpConfigContext)
public Class<BillOfMaterialItem> getType()
getType in class VdmObject<BillOfMaterialItem>public static <T> BillOfMaterialItemField<T> field(String fieldName, Class<T> fieldType)
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.@Generated(value="lombok") public static BillOfMaterialItem.BillOfMaterialItemBuilder builder()
@Nullable @Generated(value="lombok") public UUID getBillOfMaterialItemUUID()
@Nullable @Generated(value="lombok") public String getBillOfMaterialCategory()
Material BOM - linked to a material Equipment BOM - linked to an equipment Order BOM - linked to material, sales order and sales order item.
@Nullable @Generated(value="lombok") public String getBillOfMaterial()
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 BOM all variants in a variant BOM BOMs that are allocated to more than one plant
@Nullable @Generated(value="lombok") public String getBillOfMaterialVariant()
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.
@Nullable @Generated(value="lombok") public String getBillOfMaterialVersion()
@Nullable @Generated(value="lombok") public String getBillOfMaterialItemNodeNumber()
@Nullable @Generated(value="lombok") public String getBOMItemInternalChangeCount()
@Nullable @Generated(value="lombok") public Calendar getValidityStartDate()
@Nullable @Generated(value="lombok") public Calendar getValidityEndDate()
@Nullable @Generated(value="lombok") public String getEngineeringChangeDocument()
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal: The system determines the validity conditions The conditions that the change is effective under can be defined in the change master record as follows: Changes with a date validity (valid-from date) Changes with parameter effectivity (for example: serial no. effectivity) Log of the changes made Documentation of the changes Assignment of a revision level to a change state of a material or document Release of changes for the different areas in the company
@Nullable @Generated(value="lombok") public String getChgToEngineeringChgDocument()
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 N3 I-----------I----------------------I----------------> 1.1.96 6.1.96 12.2.96 If 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.
@Nullable @Generated(value="lombok") public String getInheritedNodeNumberForBOMItem()
@Nullable @Generated(value="lombok") public Calendar getBOMItemRecordCreationDate()
@Nullable @Generated(value="lombok") public String getBOMItemCreatedByUser()
@Nullable @Generated(value="lombok") public Calendar getBOMItemLastChangeDate()
@Nullable @Generated(value="lombok") public String getBOMItemLastChangedByUser()
@Nullable @Generated(value="lombok") public String getBillOfMaterialComponent()
A master record is usually maintained in the system for a component.
@Nullable @Generated(value="lombok") public String getBillOfMaterialItemCategory()
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 item This item category is used to manage material data that allows an item to be kept in stock. Document item This 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 element This 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.
@Nullable @Generated(value="lombok") public String getBillOfMaterialItemNumber()
@Nullable @Generated(value="lombok") public String getBillOfMaterialItemUnit()
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 measure unit of issue units of measure that have the same dimension as either the base unit of measure or the unit of issue If 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.
@Nullable @Generated(value="lombok") public BigDecimal getBillOfMaterialItemQuantity()
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-products Intra materials (in process industries) In display functions, the system calculates the current component quantity from the required quantity and the base quantity. Required quantity Current component quantity = ------------------ * Saved component quantity Base quantity
@Nullable @Generated(value="lombok") public String getIsAssembly()
@Nullable @Generated(value="lombok") public Boolean getIsSubItem()
Sub-items do not have an operational significance and changes are not stored with history.
@Nullable @Generated(value="lombok") public String getBOMItemSorter()
@Nullable @Generated(value="lombok") public Boolean getFixedQuantity()
A fixed quantity is not allowed for the following items: alternative item co-product If the component quantity is fixed, 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.
@Nullable @Generated(value="lombok") public String getPurchasingGroup()
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.
@Nullable @Generated(value="lombok") public String getCurrency()
@Nullable @Generated(value="lombok") public BigDecimal getMaterialComponentPrice()
@Nullable @Generated(value="lombok") public String getIdentifierBOMItem()
@Nullable @Generated(value="lombok") public BigDecimal getMaterialPriceUnitQty()
If 10 gallons of gasoline cost $12.00, the price unit is 10.
@Nullable @Generated(value="lombok") public BigDecimal getComponentScrapInPercent()
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. Example Required quantity 200 pieces Component scrap 10% Scrap quantity 20 pieces Therefore, 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.
@Nullable @Generated(value="lombok") public BigDecimal getOperationScrapInPercent()
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.
@Nullable @Generated(value="lombok") public Boolean getIsNetScrap()
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 pieces Assembly scrap 2% Component MAT-2: Component quantity 100 pieces Depending 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 10000 Key Comp Component scrap Op. Operation scrap Net ind Net indicator Qty Quantity calculated for component MAT-2 in pieces
@Nullable @Generated(value="lombok") public BigDecimal getNumberOfVariableSizeItem()
@Nullable @Generated(value="lombok") public BigDecimal getQuantityVariableSizeItem()
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: 200 Size 2: 300 Size unit of measure: MM Variable size item unit: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 0,06 SQM --> The variable-size item quantity for each piece is: 0.06 SQM The 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.
@Nullable @Generated(value="lombok") public String getFormulaKey()
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 Customizing Length: 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.
@Nullable @Generated(value="lombok") public String getBOMItemDescription()
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.
@Nullable @Generated(value="lombok") public String getBOMItemText2()
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.
@Nullable @Generated(value="lombok") public String getMaterialGroup()
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
@Nullable @Generated(value="lombok") public String getDocumentType()
@Nullable @Generated(value="lombok") public String getDocNumber()
@Nullable @Generated(value="lombok") public String getDocumentVersion()
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).
@Nullable @Generated(value="lombok") public String getDocumentPart()
Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
@Nullable @Generated(value="lombok") public String getClassNumber()
@Nullable @Generated(value="lombok") public String getClassType()
@Nullable @Generated(value="lombok") public String getResultingItemCategory()
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 item non-stock item variable-size item PM structure element If the class type is linked to documents, you can enter document item as the resulting item category.
@Nullable @Generated(value="lombok") public String getDependencyObjectNumber()
@Nullable @Generated(value="lombok") public String getObjectType()
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.
@Nullable @Generated(value="lombok") public Boolean getIsClassificationRelevant()
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).
@Nullable @Generated(value="lombok") public Boolean getIsBulkMaterial()
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.
@Nullable @Generated(value="lombok") public String getBOMItemIsSparePart()
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.
@Nullable @Generated(value="lombok") public String getBOMItemIsSalesRelevant()
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 areas which items are selected in the BOM explosion The 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.
@Nullable @Generated(value="lombok") public Boolean getIsProductionRelevant()
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 areas Selection of items in the BOM explosion Whether 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.
@Nullable @Generated(value="lombok") public Boolean getBOMItemIsPlantMaintRelevant()
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 areas Selection of items in the BOM explosion Whether 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.
@Nullable @Generated(value="lombok") public String getBOMItemIsCostingRelevant()
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.
@Nullable @Generated(value="lombok") public Boolean getIsEngineeringRelevant()
This item status indicator is used to control: Subsequent processing in related application areas Selection of items in the BOM explosion Whether 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.
@Nullable @Generated(value="lombok") public String getSpecialProcurementType()
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.
@Nullable @Generated(value="lombok") public Boolean getIsBOMRecursiveAllowed()
If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
@Nullable @Generated(value="lombok") public BigDecimal getOperationLeadTimeOffset()
(In the Project System read activity for operation.) The following areas evaluate the operation related lead-time offset: Plant maintenance orders Networks Production orders Process orders Maintain the following times dependently of the +/- sign: Lead-time offset - positive value Component can be available after the operation start date Lead time - negative value Component must be available before the operation start date Operation 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 date M-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.
@Nullable @Generated(value="lombok") public String getOpsLeadTimeOffsetUnit()
@Nullable @Generated(value="lombok") public String getIsMaterialProvision()
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 vendor Material provided by a customer You 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 vendor This 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 customer This indicator is not currently active.
@Nullable @Generated(value="lombok") public Boolean getBOMIsRecursive()
In BOM maintenance you can switch off the recursiveness check by setting the Recursiveness allowed indicator recursiveness is usually recognized online and prevented by an error message in exceptional circumstances, recursiveness is not recognized until the BOM is updated In this case, the system sets the BOM is recursive indicator. Explosion path of BOM M10 ----- ------------> |M10| | ----- | / \ | ---- ---- | M3 M2 | ---- ---- | / \ | ----- ---- -- |M10| M4 ----- ----
@Nullable @Generated(value="lombok") public Boolean getDocumentIsCreatedByCAD()
@Nullable @Generated(value="lombok") public String getDistrKeyCompConsumption()
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.
@Nullable @Generated(value="lombok") public BigDecimal getDeliveryDurationInDays()
When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
@Nullable @Generated(value="lombok") public String getCreditor()
@Nullable @Generated(value="lombok") public String getCostElement()
which is to be debited with the goods issue, if you have entered a consumption account, or for which an account assignment check is to be carried out. This entry is used in various areas: in MRP for purchase requisitions in costing for pricing You can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
@Nullable @Generated(value="lombok") public BigDecimal getSize1()
Variable-size item data for a sheet of metal: Size Description Entry 1 Length 200 2 Width 300 No. of variable-size items: 10 Size unit: MM Stockkeeping unit for sheet metal in material master: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 60.000 SQMM --> Quantity of variable-size item per sheet: 0.06 SQM 10 sheets are entered in the component, so the variable-size item requirement is: 10 * 0.06 SQM = 0.6 SQM.
@Nullable @Generated(value="lombok") public BigDecimal getSize2()
Variable-size item data for a sheet of metal: Size Description Entry 1 Length 200 2 Width 300 No. of variable-size items: 10 Size unit: MM Stockkeeping unit for sheet metal in material master: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 60.000 SQMM --> Quantity of variable-size item per sheet: 0.06 SQM 10 sheets are entered in the component, so the variable-size item requirement is: 10 * 0.06 SQM = 0.6 SQM.
@Nullable @Generated(value="lombok") public BigDecimal getSize3()
Variable-size item data for a sheet of metal: Size Description Entry 1 Length 200 2 Width 300 No. of variable-size items: 10 Size unit: MM Stockkeeping unit for sheet metal in material master: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 60.000 SQMM --> Quantity of variable-size item per sheet: 0.06 SQM 10 sheets are entered in the component, so the variable-size item requirement is: 10 * 0.06 SQM = 0.6 SQM.
@Nullable @Generated(value="lombok") public String getUnitOfMeasureForSize1To3()
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 Entry 1 Length 200 2 Width 300 Size unit for variable-size item: MM If you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area). = 200 MM * 300 MM = 60,000 MM2 Either 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.
@Nullable @Generated(value="lombok") public BigDecimal getGoodsReceiptDuration()
@Nullable @Generated(value="lombok") public String getPurchasingOrganization()
@Nullable @Generated(value="lombok") public Boolean getRequiredComponent()
@Nullable @Generated(value="lombok") public Boolean getMultipleSelectionAllowed()
@Nullable @Generated(value="lombok") public String getProdOrderIssueLocation()
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.
@Nullable @Generated(value="lombok") public Boolean getMaterialIsCoProduct()
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
@Nullable @Generated(value="lombok") public String getExplosionType()
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 assembly Phantom in planning Direct production (collective order) Direct procurement You can also define whether the following functions are performed for the item: Long-term planning Determing individual and collective requirements
@Nullable @Generated(value="lombok") public String getAlternativeItemGroup()
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 probability These 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 planning dependent requirements are changed to a reservation in the production order Alternative positions as information You 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 determination Requirements 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 posting You 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
@Nullable @Generated(value="lombok") public String getFollowUpGroup()
You can control the discontinuation in the following way: Simple discontinuation Settings 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 discontinuation One 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 1 Material of the dependent item: value 3 Settings 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 identical Example of a simple discontinuationf Item 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 1 Item Material Discontinuation group Follow-up group 0010 M-1 A1 - 0010 M-2 - A1 Example of a parallel discontinuation the 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 group 0010 M-1 A1 - 0011 M-2 A1 - 0010 M-3 - A1 0011 M-4 - A1 Abbreviations: Item. Item Mat. Material DisconGrp Discontinuation group FollGrp. Follow-up group
@Nullable @Generated(value="lombok") public String getDiscontinuationGroup()
You can control the discontinuation as follows: Simple discontinuation An 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 discontinuation One 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 1 Material of the dependent item: value 3 Settings 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 discontinuation Item 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 1 Item Mat. DisconGrp FollGrp 0010 M-1 A1 - 0010 M-2 - A1 Example for a Parallel discontinuation Items 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 group 0010 M-1 ,A1 - 0011 M-2 ,A1 - 0010 M-3 - A1 0011 M-4 - A1 Abbreviations: Item. Item Mat. Material DisconGrp Discontinuation group FollGrp. Follow-up group
@Nullable @Generated(value="lombok") public String getIsConfigurableBOM()
@Nullable @Generated(value="lombok") public String getReferencePoint()
@Nullable @Generated(value="lombok") public BigDecimal getLeadTimeOffset()
This value is not included in lead-time scheduling for a task list. You can enter: A positive number of days The component is not required until after the start date. A negative number of days The component is required before the start date. Assembly AS-11 (start date 05/13/1998): Component Lead-time offset Finish date M-01 2+ 05/15/1998 M-02 2- 05/11/1998 M-03 0 05/13/1998 Component 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.
@Nullable @Generated(value="lombok") public String getProductionSupplyArea()
The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
@Nullable @Generated(value="lombok") public Boolean getIsDeleted()
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.
@Nullable @Generated(value="lombok") public Boolean getIsALE()
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setBillOfMaterialItemUUID(@Nullable UUID billOfMaterialItemUUID)
billOfMaterialItemUUID - @Generated(value="lombok") public void setBillOfMaterialCategory(@Nullable String billOfMaterialCategory)
Material BOM - linked to a material Equipment BOM - linked to an equipment Order BOM - linked to material, sales order and sales order item.
billOfMaterialCategory - @Generated(value="lombok") public void setBillOfMaterial(@Nullable String 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 BOM all variants in a variant BOM BOMs that are allocated to more than one plant
billOfMaterial - @Generated(value="lombok") public void setBillOfMaterialVariant(@Nullable String 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.
billOfMaterialVariant - @Generated(value="lombok") public void setBillOfMaterialVersion(@Nullable String billOfMaterialVersion)
billOfMaterialVersion - @Generated(value="lombok") public void setBillOfMaterialItemNodeNumber(@Nullable String billOfMaterialItemNodeNumber)
billOfMaterialItemNodeNumber - @Generated(value="lombok") public void setBOMItemInternalChangeCount(@Nullable String bOMItemInternalChangeCount)
bOMItemInternalChangeCount - @Generated(value="lombok") public void setValidityStartDate(@Nullable Calendar validityStartDate)
validityStartDate - @Generated(value="lombok") public void setValidityEndDate(@Nullable Calendar validityEndDate)
validityEndDate - @Generated(value="lombok") public void setEngineeringChangeDocument(@Nullable String engineeringChangeDocument)
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal: The system determines the validity conditions The conditions that the change is effective under can be defined in the change master record as follows: Changes with a date validity (valid-from date) Changes with parameter effectivity (for example: serial no. effectivity) Log of the changes made Documentation of the changes Assignment of a revision level to a change state of a material or document Release of changes for the different areas in the company
engineeringChangeDocument - @Generated(value="lombok") public void setChgToEngineeringChgDocument(@Nullable String 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 N3 I-----------I----------------------I----------------> 1.1.96 6.1.96 12.2.96 If 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.
chgToEngineeringChgDocument - @Generated(value="lombok") public void setInheritedNodeNumberForBOMItem(@Nullable String inheritedNodeNumberForBOMItem)
inheritedNodeNumberForBOMItem - @Generated(value="lombok") public void setBOMItemRecordCreationDate(@Nullable Calendar bOMItemRecordCreationDate)
bOMItemRecordCreationDate - @Generated(value="lombok") public void setBOMItemCreatedByUser(@Nullable String bOMItemCreatedByUser)
bOMItemCreatedByUser - @Generated(value="lombok") public void setBOMItemLastChangeDate(@Nullable Calendar bOMItemLastChangeDate)
bOMItemLastChangeDate - @Generated(value="lombok") public void setBOMItemLastChangedByUser(@Nullable String bOMItemLastChangedByUser)
bOMItemLastChangedByUser - @Generated(value="lombok") public void setBillOfMaterialComponent(@Nullable String billOfMaterialComponent)
A master record is usually maintained in the system for a component.
billOfMaterialComponent - @Generated(value="lombok") public void setBillOfMaterialItemCategory(@Nullable String 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 item This item category is used to manage material data that allows an item to be kept in stock. Document item This 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 element This 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.
billOfMaterialItemCategory - @Generated(value="lombok") public void setBillOfMaterialItemNumber(@Nullable String billOfMaterialItemNumber)
billOfMaterialItemNumber - @Generated(value="lombok") public void setBillOfMaterialItemUnit(@Nullable String 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 measure unit of issue units of measure that have the same dimension as either the base unit of measure or the unit of issue If 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.
billOfMaterialItemUnit - @Generated(value="lombok") public void setBillOfMaterialItemQuantity(@Nullable BigDecimal 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-products Intra materials (in process industries) In display functions, the system calculates the current component quantity from the required quantity and the base quantity. Required quantity Current component quantity = ------------------ * Saved component quantity Base quantity
billOfMaterialItemQuantity - @Generated(value="lombok") public void setIsAssembly(@Nullable String isAssembly)
isAssembly - @Generated(value="lombok") public void setIsSubItem(@Nullable Boolean isSubItem)
Sub-items do not have an operational significance and changes are not stored with history.
isSubItem - @Generated(value="lombok") public void setBOMItemSorter(@Nullable String bOMItemSorter)
bOMItemSorter - @Generated(value="lombok") public void setFixedQuantity(@Nullable Boolean fixedQuantity)
A fixed quantity is not allowed for the following items: alternative item co-product If the component quantity is fixed, 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.
fixedQuantity - @Generated(value="lombok") public void setPurchasingGroup(@Nullable String 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.
purchasingGroup - @Generated(value="lombok") public void setCurrency(@Nullable String currency)
currency - @Generated(value="lombok") public void setMaterialComponentPrice(@Nullable BigDecimal materialComponentPrice)
materialComponentPrice - @Generated(value="lombok") public void setIdentifierBOMItem(@Nullable String identifierBOMItem)
identifierBOMItem - @Generated(value="lombok") public void setMaterialPriceUnitQty(@Nullable BigDecimal materialPriceUnitQty)
If 10 gallons of gasoline cost $12.00, the price unit is 10.
materialPriceUnitQty - @Generated(value="lombok") public void setComponentScrapInPercent(@Nullable BigDecimal 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. Example Required quantity 200 pieces Component scrap 10% Scrap quantity 20 pieces Therefore, 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.
componentScrapInPercent - @Generated(value="lombok") public void setOperationScrapInPercent(@Nullable BigDecimal 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.
operationScrapInPercent - @Generated(value="lombok") public void setIsNetScrap(@Nullable Boolean 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 pieces Assembly scrap 2% Component MAT-2: Component quantity 100 pieces Depending 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 10000 Key Comp Component scrap Op. Operation scrap Net ind Net indicator Qty Quantity calculated for component MAT-2 in pieces
isNetScrap - @Generated(value="lombok") public void setNumberOfVariableSizeItem(@Nullable BigDecimal numberOfVariableSizeItem)
numberOfVariableSizeItem - @Generated(value="lombok") public void setQuantityVariableSizeItem(@Nullable BigDecimal 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: 200 Size 2: 300 Size unit of measure: MM Variable size item unit: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 0,06 SQM --> The variable-size item quantity for each piece is: 0.06 SQM The 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.
quantityVariableSizeItem - @Generated(value="lombok") public void setFormulaKey(@Nullable String 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 Customizing Length: 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.
formulaKey - @Generated(value="lombok") public void setBOMItemDescription(@Nullable String 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.
bOMItemDescription - @Generated(value="lombok") public void setBOMItemText2(@Nullable String 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.
bOMItemText2 - @Generated(value="lombok") public void setMaterialGroup(@Nullable String materialGroup)
You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
materialGroup - @Generated(value="lombok") public void setDocumentType(@Nullable String documentType)
documentType - @Generated(value="lombok") public void setDocNumber(@Nullable String docNumber)
docNumber - @Generated(value="lombok") public void setDocumentVersion(@Nullable String 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).
documentVersion - @Generated(value="lombok") public void setDocumentPart(@Nullable String documentPart)
Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
documentPart - @Generated(value="lombok") public void setClassNumber(@Nullable String classNumber)
classNumber - @Generated(value="lombok") public void setClassType(@Nullable String classType)
classType - @Generated(value="lombok") public void setResultingItemCategory(@Nullable String 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 item non-stock item variable-size item PM structure element If the class type is linked to documents, you can enter document item as the resulting item category.
resultingItemCategory - @Generated(value="lombok") public void setDependencyObjectNumber(@Nullable String dependencyObjectNumber)
dependencyObjectNumber - @Generated(value="lombok") public void setObjectType(@Nullable String 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.
objectType - @Generated(value="lombok") public void setIsClassificationRelevant(@Nullable Boolean 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).
isClassificationRelevant - @Generated(value="lombok") public void setIsBulkMaterial(@Nullable Boolean 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.
isBulkMaterial - @Generated(value="lombok") public void setBOMItemIsSparePart(@Nullable String 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.
bOMItemIsSparePart - @Generated(value="lombok") public void setBOMItemIsSalesRelevant(@Nullable String 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 areas which items are selected in the BOM explosion The 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.
bOMItemIsSalesRelevant - @Generated(value="lombok") public void setIsProductionRelevant(@Nullable Boolean 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 areas Selection of items in the BOM explosion Whether 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.
isProductionRelevant - @Generated(value="lombok") public void setBOMItemIsPlantMaintRelevant(@Nullable Boolean 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 areas Selection of items in the BOM explosion Whether 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.
bOMItemIsPlantMaintRelevant - @Generated(value="lombok") public void setBOMItemIsCostingRelevant(@Nullable String 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.
bOMItemIsCostingRelevant - @Generated(value="lombok") public void setIsEngineeringRelevant(@Nullable Boolean isEngineeringRelevant)
This item status indicator is used to control: Subsequent processing in related application areas Selection of items in the BOM explosion Whether 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.
isEngineeringRelevant - @Generated(value="lombok") public void setSpecialProcurementType(@Nullable String 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.
specialProcurementType - @Generated(value="lombok") public void setIsBOMRecursiveAllowed(@Nullable Boolean isBOMRecursiveAllowed)
If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
isBOMRecursiveAllowed - @Generated(value="lombok") public void setOperationLeadTimeOffset(@Nullable BigDecimal operationLeadTimeOffset)
(In the Project System read activity for operation.) The following areas evaluate the operation related lead-time offset: Plant maintenance orders Networks Production orders Process orders Maintain the following times dependently of the +/- sign: Lead-time offset - positive value Component can be available after the operation start date Lead time - negative value Component must be available before the operation start date Operation 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 date M-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.
operationLeadTimeOffset - @Generated(value="lombok") public void setOpsLeadTimeOffsetUnit(@Nullable String opsLeadTimeOffsetUnit)
opsLeadTimeOffsetUnit - @Generated(value="lombok") public void setIsMaterialProvision(@Nullable String 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 vendor Material provided by a customer You 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 vendor This 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 customer This indicator is not currently active.
isMaterialProvision - @Generated(value="lombok") public void setBOMIsRecursive(@Nullable Boolean bOMIsRecursive)
In BOM maintenance you can switch off the recursiveness check by setting the Recursiveness allowed indicator recursiveness is usually recognized online and prevented by an error message in exceptional circumstances, recursiveness is not recognized until the BOM is updated In this case, the system sets the BOM is recursive indicator. Explosion path of BOM M10 ----- ------------> |M10| | ----- | / \ | ---- ---- | M3 M2 | ---- ---- | / \ | ----- ---- -- |M10| M4 ----- ----
bOMIsRecursive - @Generated(value="lombok") public void setDocumentIsCreatedByCAD(@Nullable Boolean documentIsCreatedByCAD)
documentIsCreatedByCAD - @Generated(value="lombok") public void setDistrKeyCompConsumption(@Nullable String 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.
distrKeyCompConsumption - @Generated(value="lombok") public void setDeliveryDurationInDays(@Nullable BigDecimal deliveryDurationInDays)
When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
deliveryDurationInDays - @Generated(value="lombok") public void setCreditor(@Nullable String creditor)
creditor - @Generated(value="lombok") public void setCostElement(@Nullable String costElement)
which is to be debited with the goods issue, if you have entered a consumption account, or for which an account assignment check is to be carried out. This entry is used in various areas: in MRP for purchase requisitions in costing for pricing You can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
costElement - @Generated(value="lombok") public void setSize1(@Nullable BigDecimal size1)
Variable-size item data for a sheet of metal: Size Description Entry 1 Length 200 2 Width 300 No. of variable-size items: 10 Size unit: MM Stockkeeping unit for sheet metal in material master: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 60.000 SQMM --> Quantity of variable-size item per sheet: 0.06 SQM 10 sheets are entered in the component, so the variable-size item requirement is: 10 * 0.06 SQM = 0.6 SQM.
size1 - @Generated(value="lombok") public void setSize2(@Nullable BigDecimal size2)
Variable-size item data for a sheet of metal: Size Description Entry 1 Length 200 2 Width 300 No. of variable-size items: 10 Size unit: MM Stockkeeping unit for sheet metal in material master: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 60.000 SQMM --> Quantity of variable-size item per sheet: 0.06 SQM 10 sheets are entered in the component, so the variable-size item requirement is: 10 * 0.06 SQM = 0.6 SQM.
size2 - @Generated(value="lombok") public void setSize3(@Nullable BigDecimal size3)
Variable-size item data for a sheet of metal: Size Description Entry 1 Length 200 2 Width 300 No. of variable-size items: 10 Size unit: MM Stockkeeping unit for sheet metal in material master: SQM Calculation of variable-size item quantity: A = Size 1 * Size 2 A = 200 MM * 300 MM A = 60.000 SQMM --> Quantity of variable-size item per sheet: 0.06 SQM 10 sheets are entered in the component, so the variable-size item requirement is: 10 * 0.06 SQM = 0.6 SQM.
size3 - @Generated(value="lombok") public void setUnitOfMeasureForSize1To3(@Nullable String 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 Entry 1 Length 200 2 Width 300 Size unit for variable-size item: MM If you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area). = 200 MM * 300 MM = 60,000 MM2 Either 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.
unitOfMeasureForSize1To3 - @Generated(value="lombok") public void setGoodsReceiptDuration(@Nullable BigDecimal goodsReceiptDuration)
goodsReceiptDuration - @Generated(value="lombok") public void setPurchasingOrganization(@Nullable String purchasingOrganization)
purchasingOrganization - @Generated(value="lombok") public void setRequiredComponent(@Nullable Boolean requiredComponent)
requiredComponent - @Generated(value="lombok") public void setMultipleSelectionAllowed(@Nullable Boolean multipleSelectionAllowed)
multipleSelectionAllowed - @Generated(value="lombok") public void setProdOrderIssueLocation(@Nullable String 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.
prodOrderIssueLocation - @Generated(value="lombok") public void setMaterialIsCoProduct(@Nullable Boolean 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
materialIsCoProduct - @Generated(value="lombok") public void setExplosionType(@Nullable String 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 assembly Phantom in planning Direct production (collective order) Direct procurement You can also define whether the following functions are performed for the item: Long-term planning Determing individual and collective requirements
explosionType - @Generated(value="lombok") public void setAlternativeItemGroup(@Nullable String 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 probability These 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 planning dependent requirements are changed to a reservation in the production order Alternative positions as information You 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 determination Requirements 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 posting You 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
alternativeItemGroup - @Generated(value="lombok") public void setFollowUpGroup(@Nullable String followUpGroup)
You can control the discontinuation in the following way: Simple discontinuation Settings 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 discontinuation One 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 1 Material of the dependent item: value 3 Settings 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 identical Example of a simple discontinuationf Item 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 1 Item Material Discontinuation group Follow-up group 0010 M-1 A1 - 0010 M-2 - A1 Example of a parallel discontinuation the 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 group 0010 M-1 A1 - 0011 M-2 A1 - 0010 M-3 - A1 0011 M-4 - A1 Abbreviations: Item. Item Mat. Material DisconGrp Discontinuation group FollGrp. Follow-up group
followUpGroup - @Generated(value="lombok") public void setDiscontinuationGroup(@Nullable String discontinuationGroup)
You can control the discontinuation as follows: Simple discontinuation An 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 discontinuation One 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 1 Material of the dependent item: value 3 Settings 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 discontinuation Item 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 1 Item Mat. DisconGrp FollGrp 0010 M-1 A1 - 0010 M-2 - A1 Example for a Parallel discontinuation Items 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 group 0010 M-1 ,A1 - 0011 M-2 ,A1 - 0010 M-3 - A1 0011 M-4 - A1 Abbreviations: Item. Item Mat. Material DisconGrp Discontinuation group FollGrp. Follow-up group
discontinuationGroup - @Generated(value="lombok") public void setIsConfigurableBOM(@Nullable String isConfigurableBOM)
isConfigurableBOM - @Generated(value="lombok") public void setReferencePoint(@Nullable String referencePoint)
referencePoint - @Generated(value="lombok") public void setLeadTimeOffset(@Nullable BigDecimal leadTimeOffset)
This value is not included in lead-time scheduling for a task list. You can enter: A positive number of days The component is not required until after the start date. A negative number of days The component is required before the start date. Assembly AS-11 (start date 05/13/1998): Component Lead-time offset Finish date M-01 2+ 05/15/1998 M-02 2- 05/11/1998 M-03 0 05/13/1998 Component 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.
leadTimeOffset - @Generated(value="lombok") public void setProductionSupplyArea(@Nullable String productionSupplyArea)
The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
productionSupplyArea - @Generated(value="lombok") public void setIsDeleted(@Nullable Boolean 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.
isDeleted - @Generated(value="lombok") public void setIsALE(@Nullable Boolean isALE)
isALE - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<BillOfMaterialItem>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<BillOfMaterialItem>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<BillOfMaterialItem>Copyright © 2018 SAP SE. All rights reserved.