public class BillOfMaterialItem extends VdmEntity<BillOfMaterialItem>
Original entity name from the Odata EDM: A_BillOfMaterialItemType
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<LocalDateTime> |
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<LocalDateTime> |
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<LocalDateTime> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static BillOfMaterialItemField<LocalDateTime> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
BillOfMaterialItem() |
BillOfMaterialItem(UUID billOfMaterialItemUUID,
String billOfMaterialCategory,
String billOfMaterial,
String billOfMaterialVariant,
String billOfMaterialVersion,
String billOfMaterialItemNodeNumber,
String bOMItemInternalChangeCount,
LocalDateTime validityStartDate,
LocalDateTime validityEndDate,
String engineeringChangeDocument,
String chgToEngineeringChgDocument,
String inheritedNodeNumberForBOMItem,
LocalDateTime bOMItemRecordCreationDate,
String bOMItemCreatedByUser,
LocalDateTime bOMItemLastChangeDate,
String bOMItemLastChangedByUser,
String billOfMaterialComponent,
String billOfMaterialItemCategory,
String billOfMaterialItemNumber,
String billOfMaterialItemUnit,
BigDecimal billOfMaterialItemQuantity,
String isAssembly,
Boolean isSubItem,
String bOMItemSorter,
Boolean fixedQuantity,
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() |
protected boolean |
canEqual(Object other) |
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.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getAlternativeItemGroup()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AlternativeItemGroupAs soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability.
|
String |
getBillOfMaterial()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: BillOfMaterialThe system assigns this number internally.
|
String |
getBillOfMaterialCategory()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BillOfMaterialCategoryMaterial BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
|
String |
getBillOfMaterialComponent()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: BillOfMaterialComponentA master record is usually maintained in the system for a component.
|
String |
getBillOfMaterialItemCategory()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BillOfMaterialItemCategoryThis categorization allows you to process data that is relevant to the individual items in a BOM.
|
String |
getBillOfMaterialItemNodeNumber()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
|
String |
getBillOfMaterialItemNumber()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BillOfMaterialItemNumber
|
BigDecimal |
getBillOfMaterialItemQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: BillOfMaterialItemQuantityYou usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
|
String |
getBillOfMaterialItemUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: BillOfMaterialItemUnitThe system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit.
|
UUID |
getBillOfMaterialItemUUID()
(Key Field) Constraints: Not nullableOriginal property name from the Odata EDM: BillOfMaterialItemUUID
|
String |
getBillOfMaterialVariant()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: BillOfMaterialVariantOne product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes.
|
String |
getBillOfMaterialVersion()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BillOfMaterialVersion
|
Boolean |
getBOMIsRecursive()
Constraints: noneOriginal property name from the Odata EDM: BOMIsRecursiveIn BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
|
String |
getBOMItemCreatedByUser()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BOMItemCreatedByUser
|
String |
getBOMItemDescription()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: BOMItemDescriptionIf 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.
|
String |
getBOMItemInternalChangeCount()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: BOMItemInternalChangeCount
|
String |
getBOMItemIsCostingRelevant()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BOMItemIsCostingRelevantThe 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.
|
Boolean |
getBOMItemIsPlantMaintRelevant()
Constraints: noneOriginal property name from the Odata EDM: BOMItemIsPlantMaintRelevantItems that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen.
|
String |
getBOMItemIsSalesRelevant()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BOMItemIsSalesRelevantFor example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever.
|
String |
getBOMItemIsSparePart()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BOMItemIsSparePartIn 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.
|
LocalDateTime |
getBOMItemLastChangeDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: BOMItemLastChangeDate
|
String |
getBOMItemLastChangedByUser()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BOMItemLastChangedByUser
|
LocalDateTime |
getBOMItemRecordCreationDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: BOMItemRecordCreationDate
|
String |
getBOMItemSorter()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BOMItemSorter
|
String |
getBOMItemText2()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: BOMItemText2You 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.
|
String |
getChgToEngineeringChgDocument()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: ChgToEngineeringChgDocumentIf the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
|
String |
getClassNumber()
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: ClassNumber
|
String |
getClassType()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ClassType
|
BigDecimal |
getComponentScrapInPercent()
Constraints: Not nullable, Precision: 5, Scale: 2 Original property name from the Odata EDM: ComponentScrapInPercentComponent scrap is used in material requirements planning (MRP) to determine the quantities of components required.
|
String |
getCostElement()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostElementwhich is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
|
String |
getCreditor()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Creditor
|
String |
getCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: Currency
|
BigDecimal |
getDeliveryDurationInDays()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: DeliveryDurationInDaysWhen an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
|
String |
getDependencyObjectNumber()
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: DependencyObjectNumber
|
String |
getDiscontinuationGroup()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DiscontinuationGroupYou can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group.
|
String |
getDistrKeyCompConsumption()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: DistrKeyCompConsumptionThis 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.
|
String |
getDocNumber()
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: DocNumber
|
Boolean |
getDocumentIsCreatedByCAD()
Constraints: noneOriginal property name from the Odata EDM: DocumentIsCreatedByCAD
|
String |
getDocumentPart()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: DocumentPartDesign departments, for example, can use document parts to divide up large documents such as design drawings into pages.
|
String |
getDocumentType()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: DocumentType
|
String |
getDocumentVersion()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DocumentVersionA 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).
|
protected String |
getEndpointUrl() |
String |
getEngineeringChangeDocument()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: EngineeringChangeDocumentIf you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
String |
getExplosionType()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: ExplosionTypeYou can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
|
Boolean |
getFixedQuantity()
Constraints: noneOriginal property name from the Odata EDM: FixedQuantityA fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
|
String |
getFollowUpGroup()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: FollowUpGroupYou can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials.
|
String |
getFormulaKey()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: FormulaKeyYou want to calculate the volume of a rolled sheet of metal.
|
BigDecimal |
getGoodsReceiptDuration()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: GoodsReceiptDuration
|
String |
getIdentifierBOMItem()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: IdentifierBOMItem
|
String |
getInheritedNodeNumberForBOMItem()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
|
Boolean |
getIsALE()
Constraints: noneOriginal property name from the Odata EDM: IsALE
|
String |
getIsAssembly()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsAssembly
|
Boolean |
getIsBOMRecursiveAllowed()
Constraints: noneOriginal property name from the Odata EDM: IsBOMRecursiveAllowedIf you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
|
Boolean |
getIsBulkMaterial()
Constraints: noneOriginal property name from the Odata EDM: IsBulkMaterialThe dependent requirements of bulk materials are not relevant to materials planning.
|
Boolean |
getIsClassificationRelevant()
Constraints: noneOriginal property name from the Odata EDM: IsClassificationRelevantIf 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).
|
String |
getIsConfigurableBOM()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsConfigurableBOM
|
Boolean |
getIsDeleted()
Constraints: noneOriginal property name from the Odata EDM: IsDeletedThis 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.
|
Boolean |
getIsEngineeringRelevant()
Constraints: noneOriginal property name from the Odata EDM: IsEngineeringRelevantThis item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen.
|
String |
getIsMaterialProvision()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsMaterialProvisionIn the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part.
|
Boolean |
getIsNetScrap()
Constraints: noneOriginal property name from the Odata EDM: IsNetScrapYou must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp.
|
Boolean |
getIsProductionRelevant()
Constraints: noneOriginal property name from the Odata EDM: IsProductionRelevantItems with this indicator are copied to the planned order, and the system calculates dependent requirements for them.
|
Boolean |
getIsSubItem()
Constraints: noneOriginal property name from the Odata EDM: IsSubItemSub-items do not have an operational significance and changes arenot stored with history.
|
protected Map<String,Object> |
getKey() |
BigDecimal |
getLeadTimeOffset()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: LeadTimeOffsetThis value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
|
BigDecimal |
getMaterialComponentPrice()
Constraints: Not nullable, Precision: 12, Scale: 3 Original property name from the Odata EDM: MaterialComponentPrice
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9 Original property name from the Odata EDM: MaterialGroupYou can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
|
Boolean |
getMaterialIsCoProduct()
Constraints: noneOriginal property name from the Odata EDM: MaterialIsCoProductEnter 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.
|
BigDecimal |
getMaterialPriceUnitQty()
Constraints: Not nullable, Precision: 5, Scale: 0 Original property name from the Odata EDM: MaterialPriceUnitQtyIf 10 gallons of gasoline cost $12.00, the price unit is 10.
|
Boolean |
getMultipleSelectionAllowed()
Constraints: noneOriginal property name from the Odata EDM: MultipleSelectionAllowed
|
BigDecimal |
getNumberOfVariableSizeItem()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: NumberOfVariableSizeItem
|
String |
getObjectType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: ObjectTypeVia 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.
|
BigDecimal |
getOperationLeadTimeOffset()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: OperationLeadTimeOffset(In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.
|
BigDecimal |
getOperationScrapInPercent()
Constraints: Not nullable, Precision: 5, Scale: 2 Original property name from the Odata EDM: OperationScrapInPercentThis 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.
|
String |
getOpsLeadTimeOffsetUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
|
String |
getProdOrderIssueLocation()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ProdOrderIssueLocationIn 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.
|
String |
getProductionSupplyArea()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProductionSupplyAreaThe PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
|
String |
getPurchasingGroup()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PurchasingGroupInternally, 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.
|
String |
getPurchasingOrganization()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PurchasingOrganization
|
BigDecimal |
getQuantityVariableSizeItem()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: QuantityVariableSizeItemThe quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
|
String |
getReferencePoint()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: ReferencePoint
|
Boolean |
getRequiredComponent()
Constraints: noneOriginal property name from the Odata EDM: RequiredComponent
|
String |
getResultingItemCategory()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: ResultingItemCategoryThis categorization allows you to process data that is relevant to BOM items for all objects allocated to the class.
|
BigDecimal |
getSize1()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: Size1Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
|
BigDecimal |
getSize2()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: Size2Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
|
BigDecimal |
getSize3()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: Size3Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
|
String |
getSpecialProcurementType()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SpecialProcurementTypeEnter 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.
|
Class<BillOfMaterialItem> |
getType() |
String |
getUnitOfMeasureForSize1To3()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: UnitOfMeasureForSize1To3Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
|
LocalDateTime |
getValidityEndDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityEndDate
|
LocalDateTime |
getValidityStartDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityStartDate
|
int |
hashCode() |
void |
setAlternativeItemGroup(String alternativeItemGroup)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AlternativeItemGroupAs soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability.
|
void |
setBillOfMaterial(String billOfMaterial)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: BillOfMaterialThe system assigns this number internally.
|
void |
setBillOfMaterialCategory(String billOfMaterialCategory)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BillOfMaterialCategoryMaterial BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
|
void |
setBillOfMaterialComponent(String billOfMaterialComponent)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: BillOfMaterialComponentA master record is usually maintained in the system for a component.
|
void |
setBillOfMaterialItemCategory(String billOfMaterialItemCategory)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BillOfMaterialItemCategoryThis categorization allows you to process data that is relevant to the individual items in a BOM.
|
void |
setBillOfMaterialItemNodeNumber(String billOfMaterialItemNodeNumber)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
|
void |
setBillOfMaterialItemNumber(String billOfMaterialItemNumber)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BillOfMaterialItemNumber
|
void |
setBillOfMaterialItemQuantity(BigDecimal billOfMaterialItemQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: BillOfMaterialItemQuantityYou usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
|
void |
setBillOfMaterialItemUnit(String billOfMaterialItemUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: BillOfMaterialItemUnitThe system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit.
|
void |
setBillOfMaterialItemUUID(UUID billOfMaterialItemUUID)
(Key Field) Constraints: Not nullableOriginal property name from the Odata EDM: BillOfMaterialItemUUID
|
void |
setBillOfMaterialVariant(String billOfMaterialVariant)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: BillOfMaterialVariantOne product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes.
|
void |
setBillOfMaterialVersion(String billOfMaterialVersion)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BillOfMaterialVersion
|
void |
setBOMIsRecursive(Boolean bOMIsRecursive)
Constraints: noneOriginal property name from the Odata EDM: BOMIsRecursiveIn BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
|
void |
setBOMItemCreatedByUser(String bOMItemCreatedByUser)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BOMItemCreatedByUser
|
void |
setBOMItemDescription(String bOMItemDescription)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: BOMItemDescriptionIf 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.
|
void |
setBOMItemInternalChangeCount(String bOMItemInternalChangeCount)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: BOMItemInternalChangeCount
|
void |
setBOMItemIsCostingRelevant(String bOMItemIsCostingRelevant)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BOMItemIsCostingRelevantThe 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.
|
void |
setBOMItemIsPlantMaintRelevant(Boolean bOMItemIsPlantMaintRelevant)
Constraints: noneOriginal property name from the Odata EDM: BOMItemIsPlantMaintRelevantItems that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen.
|
void |
setBOMItemIsSalesRelevant(String bOMItemIsSalesRelevant)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BOMItemIsSalesRelevantFor example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever.
|
void |
setBOMItemIsSparePart(String bOMItemIsSparePart)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BOMItemIsSparePartIn 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.
|
void |
setBOMItemLastChangeDate(LocalDateTime bOMItemLastChangeDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: BOMItemLastChangeDate
|
void |
setBOMItemLastChangedByUser(String bOMItemLastChangedByUser)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BOMItemLastChangedByUser
|
void |
setBOMItemRecordCreationDate(LocalDateTime bOMItemRecordCreationDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: BOMItemRecordCreationDate
|
void |
setBOMItemSorter(String bOMItemSorter)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BOMItemSorter
|
void |
setBOMItemText2(String bOMItemText2)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: BOMItemText2You 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.
|
void |
setChgToEngineeringChgDocument(String chgToEngineeringChgDocument)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: ChgToEngineeringChgDocumentIf the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
|
void |
setClassNumber(String classNumber)
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: ClassNumber
|
void |
setClassType(String classType)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: ClassType
|
void |
setComponentScrapInPercent(BigDecimal componentScrapInPercent)
Constraints: Not nullable, Precision: 5, Scale: 2 Original property name from the Odata EDM: ComponentScrapInPercentComponent scrap is used in material requirements planning (MRP) to determine the quantities of components required.
|
void |
setCostElement(String costElement)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostElementwhich is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
|
void |
setCreditor(String creditor)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Creditor
|
void |
setCurrency(String currency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: Currency
|
void |
setDeliveryDurationInDays(BigDecimal deliveryDurationInDays)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: DeliveryDurationInDaysWhen an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
|
void |
setDependencyObjectNumber(String dependencyObjectNumber)
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: DependencyObjectNumber
|
void |
setDiscontinuationGroup(String discontinuationGroup)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DiscontinuationGroupYou can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group.
|
void |
setDistrKeyCompConsumption(String distrKeyCompConsumption)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: DistrKeyCompConsumptionThis 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.
|
void |
setDocNumber(String docNumber)
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: DocNumber
|
void |
setDocumentIsCreatedByCAD(Boolean documentIsCreatedByCAD)
Constraints: noneOriginal property name from the Odata EDM: DocumentIsCreatedByCAD
|
void |
setDocumentPart(String documentPart)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: DocumentPartDesign departments, for example, can use document parts to divide up large documents such as design drawings into pages.
|
void |
setDocumentType(String documentType)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: DocumentType
|
void |
setDocumentVersion(String documentVersion)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DocumentVersionA 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).
|
void |
setEngineeringChangeDocument(String engineeringChangeDocument)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: EngineeringChangeDocumentIf you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setExplosionType(String explosionType)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: ExplosionTypeYou can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
|
void |
setFixedQuantity(Boolean fixedQuantity)
Constraints: noneOriginal property name from the Odata EDM: FixedQuantityA fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
|
void |
setFollowUpGroup(String followUpGroup)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: FollowUpGroupYou can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials.
|
void |
setFormulaKey(String formulaKey)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: FormulaKeyYou want to calculate the volume of a rolled sheet of metal.
|
void |
setGoodsReceiptDuration(BigDecimal goodsReceiptDuration)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: GoodsReceiptDuration
|
void |
setIdentifierBOMItem(String identifierBOMItem)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: IdentifierBOMItem
|
void |
setInheritedNodeNumberForBOMItem(String inheritedNodeNumberForBOMItem)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
|
void |
setIsALE(Boolean isALE)
Constraints: noneOriginal property name from the Odata EDM: IsALE
|
void |
setIsAssembly(String isAssembly)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsAssembly
|
void |
setIsBOMRecursiveAllowed(Boolean isBOMRecursiveAllowed)
Constraints: noneOriginal property name from the Odata EDM: IsBOMRecursiveAllowedIf you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
|
void |
setIsBulkMaterial(Boolean isBulkMaterial)
Constraints: noneOriginal property name from the Odata EDM: IsBulkMaterialThe dependent requirements of bulk materials are not relevant to materials planning.
|
void |
setIsClassificationRelevant(Boolean isClassificationRelevant)
Constraints: noneOriginal property name from the Odata EDM: IsClassificationRelevantIf 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).
|
void |
setIsConfigurableBOM(String isConfigurableBOM)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsConfigurableBOM
|
void |
setIsDeleted(Boolean isDeleted)
Constraints: noneOriginal property name from the Odata EDM: IsDeletedThis 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.
|
void |
setIsEngineeringRelevant(Boolean isEngineeringRelevant)
Constraints: noneOriginal property name from the Odata EDM: IsEngineeringRelevantThis item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen.
|
void |
setIsMaterialProvision(String isMaterialProvision)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsMaterialProvisionIn the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part.
|
void |
setIsNetScrap(Boolean isNetScrap)
Constraints: noneOriginal property name from the Odata EDM: IsNetScrapYou must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp.
|
void |
setIsProductionRelevant(Boolean isProductionRelevant)
Constraints: noneOriginal property name from the Odata EDM: IsProductionRelevantItems with this indicator are copied to the planned order, and the system calculates dependent requirements for them.
|
void |
setIsSubItem(Boolean isSubItem)
Constraints: noneOriginal property name from the Odata EDM: IsSubItemSub-items do not have an operational significance and changes arenot stored with history.
|
void |
setLeadTimeOffset(BigDecimal leadTimeOffset)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: LeadTimeOffsetThis value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
|
void |
setMaterialComponentPrice(BigDecimal materialComponentPrice)
Constraints: Not nullable, Precision: 12, Scale: 3 Original property name from the Odata EDM: MaterialComponentPrice
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9 Original property name from the Odata EDM: MaterialGroupYou can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
|
void |
setMaterialIsCoProduct(Boolean materialIsCoProduct)
Constraints: noneOriginal property name from the Odata EDM: MaterialIsCoProductEnter 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.
|
void |
setMaterialPriceUnitQty(BigDecimal materialPriceUnitQty)
Constraints: Not nullable, Precision: 5, Scale: 0 Original property name from the Odata EDM: MaterialPriceUnitQtyIf 10 gallons of gasoline cost $12.00, the price unit is 10.
|
void |
setMultipleSelectionAllowed(Boolean multipleSelectionAllowed)
Constraints: noneOriginal property name from the Odata EDM: MultipleSelectionAllowed
|
void |
setNumberOfVariableSizeItem(BigDecimal numberOfVariableSizeItem)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: NumberOfVariableSizeItem
|
void |
setObjectType(String objectType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: ObjectTypeVia 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.
|
void |
setOperationLeadTimeOffset(BigDecimal operationLeadTimeOffset)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: OperationLeadTimeOffset(In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.
|
void |
setOperationScrapInPercent(BigDecimal operationScrapInPercent)
Constraints: Not nullable, Precision: 5, Scale: 2 Original property name from the Odata EDM: OperationScrapInPercentThis 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.
|
void |
setOpsLeadTimeOffsetUnit(String opsLeadTimeOffsetUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
|
void |
setProdOrderIssueLocation(String prodOrderIssueLocation)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ProdOrderIssueLocationIn 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.
|
void |
setProductionSupplyArea(String productionSupplyArea)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProductionSupplyAreaThe PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
|
void |
setPurchasingGroup(String purchasingGroup)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PurchasingGroupInternally, 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.
|
void |
setPurchasingOrganization(String purchasingOrganization)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PurchasingOrganization
|
void |
setQuantityVariableSizeItem(BigDecimal quantityVariableSizeItem)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: QuantityVariableSizeItemThe quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
|
void |
setReferencePoint(String referencePoint)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: ReferencePoint
|
void |
setRequiredComponent(Boolean requiredComponent)
Constraints: noneOriginal property name from the Odata EDM: RequiredComponent
|
void |
setResultingItemCategory(String resultingItemCategory)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: ResultingItemCategoryThis categorization allows you to process data that is relevant to BOM items for all objects allocated to the class.
|
void |
setSize1(BigDecimal size1)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: Size1Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
|
void |
setSize2(BigDecimal size2)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: Size2Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
|
void |
setSize3(BigDecimal size3)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: Size3Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
|
void |
setSpecialProcurementType(String specialProcurementType)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: SpecialProcurementTypeEnter 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.
|
void |
setUnitOfMeasureForSize1To3(String unitOfMeasureForSize1To3)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: UnitOfMeasureForSize1To3Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
|
void |
setValidityEndDate(LocalDateTime validityEndDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityEndDate
|
void |
setValidityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityStartDate
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public 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<LocalDateTime> VALIDITY_START_DATE
public static final BillOfMaterialItemField<LocalDateTime> 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<LocalDateTime> BOM_ITEM_RECORD_CREATION_DATE
public static final BillOfMaterialItemField<String> BOM_ITEM_CREATED_BY_USER
public static final BillOfMaterialItemField<LocalDateTime> 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
public BillOfMaterialItem()
public BillOfMaterialItem(@Nullable UUID billOfMaterialItemUUID, @Nullable String billOfMaterialCategory, @Nullable String billOfMaterial, @Nullable String billOfMaterialVariant, @Nullable String billOfMaterialVersion, @Nullable String billOfMaterialItemNodeNumber, @Nullable String bOMItemInternalChangeCount, @Nullable LocalDateTime validityStartDate, @Nullable LocalDateTime validityEndDate, @Nullable String engineeringChangeDocument, @Nullable String chgToEngineeringChgDocument, @Nullable String inheritedNodeNumberForBOMItem, @Nullable LocalDateTime bOMItemRecordCreationDate, @Nullable String bOMItemCreatedByUser, @Nullable LocalDateTime bOMItemLastChangeDate, @Nullable String bOMItemLastChangedByUser, @Nullable String billOfMaterialComponent, @Nullable String billOfMaterialItemCategory, @Nullable String billOfMaterialItemNumber, @Nullable String billOfMaterialItemUnit, @Nullable BigDecimal billOfMaterialItemQuantity, @Nullable String isAssembly, @Nullable Boolean isSubItem, @Nullable String bOMItemSorter, @Nullable Boolean fixedQuantity, @Nullable 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 void setBillOfMaterialItemUUID(@Nullable UUID billOfMaterialItemUUID)
Original property name from the Odata EDM: BillOfMaterialItemUUID
billOfMaterialItemUUID
- Global identification of an item's change statuspublic void setBillOfMaterialCategory(@Nullable String billOfMaterialCategory)
Original property name from the Odata EDM: BillOfMaterialCategory
Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
billOfMaterialCategory
- This key defines a BOM according to the object (such as material or equipment) to which it is linked.public void setBillOfMaterial(@Nullable String billOfMaterial)
Original property name from the Odata EDM: BillOfMaterial
The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
billOfMaterial
- Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.public void setBillOfMaterialVariant(@Nullable String billOfMaterialVariant)
Original property name from the Odata EDM: BillOfMaterialVariant
One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
billOfMaterialVariant
- Identifies one BOM in a BOM group.public void setBillOfMaterialVersion(@Nullable String billOfMaterialVersion)
Original property name from the Odata EDM: BillOfMaterialVersion
billOfMaterialVersion
- BOM Versionpublic void setBillOfMaterialItemNodeNumber(@Nullable String billOfMaterialItemNodeNumber)
Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
billOfMaterialItemNodeNumber
- public void setBOMItemInternalChangeCount(@Nullable String bOMItemInternalChangeCount)
Original property name from the Odata EDM: BOMItemInternalChangeCount
bOMItemInternalChangeCount
- Identifies the activity posting.public void setValidityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
validityStartDate
- Specifies the start date for the validity period of an object (such as material, BOM, or routing).public void setValidityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
validityEndDate
- End of validity period of an object (such as material, BOM, or routing) in the SAP System.public void setEngineeringChangeDocument(@Nullable String engineeringChangeDocument)
Original property name from the Odata EDM: EngineeringChangeDocument
If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
engineeringChangeDocument
- Number used to uniquely identify a change master record.public void setChgToEngineeringChgDocument(@Nullable String chgToEngineeringChgDocument)
Original property name from the Odata EDM: ChgToEngineeringChgDocument
If the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
chgToEngineeringChgDocument
- Number used to identify the change master, which will determine the subsequent validity period of the object (material, for example).public void setInheritedNodeNumberForBOMItem(@Nullable String inheritedNodeNumberForBOMItem)
Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
inheritedNodeNumberForBOMItem
- Inherited node number of BOM itempublic void setBOMItemRecordCreationDate(@Nullable LocalDateTime bOMItemRecordCreationDate)
Original property name from the Odata EDM: BOMItemRecordCreationDate
bOMItemRecordCreationDate
- Date on which the record was created.public void setBOMItemCreatedByUser(@Nullable String bOMItemCreatedByUser)
Original property name from the Odata EDM: BOMItemCreatedByUser
bOMItemCreatedByUser
- Name of user who created the record.public void setBOMItemLastChangeDate(@Nullable LocalDateTime bOMItemLastChangeDate)
Original property name from the Odata EDM: BOMItemLastChangeDate
bOMItemLastChangeDate
- Date of Last Changepublic void setBOMItemLastChangedByUser(@Nullable String bOMItemLastChangedByUser)
Original property name from the Odata EDM: BOMItemLastChangedByUser
bOMItemLastChangedByUser
- Name of Person who Changed Objectpublic void setBillOfMaterialComponent(@Nullable String billOfMaterialComponent)
Original property name from the Odata EDM: BillOfMaterialComponent
A master record is usually maintained in the system for a component.
billOfMaterialComponent
- Material number of the components that you enter, change or display as part of the BOM.public void setBillOfMaterialItemCategory(@Nullable String billOfMaterialItemCategory)
Original property name from the Odata EDM: BillOfMaterialItemCategory
This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
billOfMaterialItemCategory
- Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.public void setBillOfMaterialItemNumber(@Nullable String billOfMaterialItemNumber)
Original property name from the Odata EDM: BillOfMaterialItemNumber
billOfMaterialItemNumber
- This number refers to the sequence of BOM components.public void setBillOfMaterialItemUnit(@Nullable String billOfMaterialItemUnit)
Original property name from the Odata EDM: BillOfMaterialItemUnit
The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
billOfMaterialItemUnit
- The unit for the component quantity.public void setBillOfMaterialItemQuantity(@Nullable BigDecimal billOfMaterialItemQuantity)
Original property name from the Odata EDM: BillOfMaterialItemQuantity
You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
billOfMaterialItemQuantity
- Quantity of the component, which is entered in relation to the base quantity of the product.public void setIsAssembly(@Nullable String isAssembly)
Original property name from the Odata EDM: IsAssembly
isAssembly
- Indicator: the component in this item has its own BOM.public void setIsSubItem(@Nullable Boolean isSubItem)
Original property name from the Odata EDM: IsSubItem
Sub-items do not have an operational significance and changes arenot stored with history.
isSubItem
- Indicator: this BOM item has sub-items.public void setBOMItemSorter(@Nullable String bOMItemSorter)
Original property name from the Odata EDM: BOMItemSorter
bOMItemSorter
- String which can be defined as required for sorting components for display.public void setFixedQuantity(@Nullable Boolean fixedQuantity)
Original property name from the Odata EDM: FixedQuantity
A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
fixedQuantity
- This indicator shows that the component quantity is always the same.public void setPurchasingGroup(@Nullable String purchasingGroup)
Original property name from the Odata EDM: PurchasingGroup
Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.
purchasingGroup
- Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities.public void setCurrency(@Nullable String currency)
Original property name from the Odata EDM: Currency
currency
- Currency key for amounts in the system.public void setMaterialComponentPrice(@Nullable BigDecimal materialComponentPrice)
Original property name from the Odata EDM: MaterialComponentPrice
materialComponentPrice
- Amount for non-stock item, which is used when costing the end or intermediate product for pricing purposes.public void setIdentifierBOMItem(@Nullable String identifierBOMItem)
Original property name from the Odata EDM: IdentifierBOMItem
identifierBOMItem
- Alphanumeric character string, with which you uniquely identify a BOM item.public void setMaterialPriceUnitQty(@Nullable BigDecimal materialPriceUnitQty)
Original property name from the Odata EDM: MaterialPriceUnitQty
If 10 gallons of gasoline cost $12.00, the price unit is 10.
materialPriceUnitQty
- Number of units to which the price refers.public void setComponentScrapInPercent(@Nullable BigDecimal componentScrapInPercent)
Original property name from the Odata EDM: ComponentScrapInPercent
Component scrap is used in material requirements planning (MRP) to determine the quantities of components required. When exploding the bill of material (BOM), the system increases the required quantities of the components by the calculated scrap quantity.ExampleRequired quantity 200 piecesComponent scrap 10%Scrap quantity 20 piecesTherefore, 220 pieces are required.For examples of calculation in connection with the indicator for net scrap, see the documentation for this indicator.If there is also assembly scrap for a higher-level assembly, the system adds together the two types of scrap.If component scrap has been entered in the BOM, this value applies. Otherwise, the value specified in the material master record is used.
componentScrapInPercent
- Percentage of scrap that occurs during production of the material if the material is a component.public void setOperationScrapInPercent(@Nullable BigDecimal operationScrapInPercent)
Original property name from the Odata EDM: OperationScrapInPercent
This entry is used to override the assembly scrap for materials of high value.If operation scrap is maintained, you avoid the situation whereby too much of the material is planned in MRP for the components of subsequent operations.If you make an entry for operation scrap, you must also select the operation scrap net indicator (Net field).You can find examples of scrap under net scrap.
operationScrapInPercent
- Scrap that is expected in one operation for the quantity of a component to be processed.public void setIsNetScrap(@Nullable Boolean isNetScrap)
Original property name from the Odata EDM: IsNetScrap
You must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp. Operation scrapNet ind Net indicatorQty Quantity calculated for component MAT-2 in pieces
isNetScrap
- This indicator determines whether scrap for the component is calculated on the basis of the net required quantity (the required quantity without assembly scrap from the material master record).public void setNumberOfVariableSizeItem(@Nullable BigDecimal numberOfVariableSizeItem)
Original property name from the Odata EDM: NumberOfVariableSizeItem
numberOfVariableSizeItem
- Number of variable-size items required for the assembly .public void setQuantityVariableSizeItem(@Nullable BigDecimal quantityVariableSizeItem)
Original property name from the Odata EDM: QuantityVariableSizeItem
The quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
quantityVariableSizeItem
- Quantity of variable-size item, which the system calculates from the sizes entered. If you wish you can enter a variable-size item formula for the. calculation.public void setFormulaKey(@Nullable String formulaKey)
Original property name from the Odata EDM: FormulaKey
You want to calculate the volume of a rolled sheet of metal. This has a variable length and height, but a constant width (500 MM).The following are used in the calculation:SI units that are defined in CustomizingLength: M (meters)Volume: M3 (cubic meters)In the variable-size item, you only enter the variable values (size 1 and size 2) with a unit of measure that can be derived from the SI unit of the dimension.Example for dimension Length: MM (milllimeters), CM (centimeters), DM (decimeters), and M (meters)The variable-size item formula uses the SI unit, so you must enter the constant width in the formula in the SI unit (meters).Example: ROMS1 * ROMS2 * 0.5 (M)You can enter units of measure for calculating the variable-size item quantity with a formula. The quantity is always calculated in the SI unit of the dimension, such as M3 (cubic meters) for volume.
formulaKey
- Key that represents the algorithm for calculating the variable-size item quantity.public void setBOMItemDescription(@Nullable String bOMItemDescription)
Original property name from the Odata EDM: BOMItemDescription
If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
bOMItemDescription
- Text of up to 40 characters, which forms the first of two lines of text describing the item.public void setBOMItemText2(@Nullable String bOMItemText2)
Original property name from the Odata EDM: BOMItemText2
You can also enter a long text by choosing menu option Details --> Long text --> Item long text.If the text comprises less than three lines, it is stored in the BOM item. Otherwise, it is stored as a long text in the text database.
bOMItemText2
- Text of up to 40 characters, which forms the second of two lines of text describing the item.public void setMaterialGroup(@Nullable String materialGroup)
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
materialGroup
- Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.public void setDocumentType(@Nullable String documentType)
Original property name from the Odata EDM: DocumentType
documentType
- Part of the document key, which categorizes documents according to their distinguishing features and the organizational procedures which result from them.public void setDocNumber(@Nullable String docNumber)
Original property name from the Odata EDM: DocNumber
docNumber
- This number is the main part of the document key, which is used to identify the document.public void setDocumentVersion(@Nullable String documentVersion)
Original property name from the Odata EDM: DocumentVersion
A new version is assigned after the original files have been edited in the following processing situations:The new processing status varies from the original in a certain way (for example, text change sin a text file).You want the original processing status to remain the same (for example, documentation of project progress).
documentVersion
- Number which identifies the version of a document.public void setDocumentPart(@Nullable String documentPart)
Original property name from the Odata EDM: DocumentPart
Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
documentPart
- Section of a document which is maintained as an independent document.public void setClassNumber(@Nullable String classNumber)
Original property name from the Odata EDM: ClassNumber
classNumber
- Name used to uniquely identify a class within a class type.public void setClassType(@Nullable String classType)
Original property name from the Odata EDM: ClassType
classType
- Uniquely identifies the class typepublic void setResultingItemCategory(@Nullable String resultingItemCategory)
Original property name from the Odata EDM: ResultingItemCategory
This categorization allows you to process data that is relevant to BOM items for all objects allocated to the class. For example, you control field selection and special system activities when you select the resulting item category.The class type determines which resulting item category you can select:If the class type is linked to the material master, you can select one of the following resulting item categories:stock itemnon-stock itemvariable-size itemPM structure elementIf the class type is linked to documents, you can enter document item as the resulting item category.
resultingItemCategory
- Categorization of class items according to the object type linked to the class type.public void setDependencyObjectNumber(@Nullable String dependencyObjectNumber)
Original property name from the Odata EDM: DependencyObjectNumber
dependencyObjectNumber
- Number of Object with Assigned Dependenciespublic void setObjectType(@Nullable String objectType)
Original property name from the Odata EDM: ObjectType
Via settings in Customizing (Bill of mat. -> Item data), you can define a language-dependent abbreviation which the system displays on the General item overview screen.
objectType
- Key which assigns the BOM item to a group of objects which have basic features in common, such as material or document.public void setIsClassificationRelevant(@Nullable Boolean isClassificationRelevant)
Original property name from the Odata EDM: IsClassificationRelevant
If you select this indicator, the classification of the item is taken into account when the object is configured.You can only select this indicator if you have classified the item first (entered a class type).
isClassificationRelevant
- Indicator for defining classification as a selection condition.public void setIsBulkMaterial(@Nullable Boolean isBulkMaterial)
Original property name from the Odata EDM: IsBulkMaterial
The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
isBulkMaterial
- This indicator defines a BOM item as a bulk material, which is available directly at the work center (for example, washers or grease).public void setBOMItemIsSparePart(@Nullable String bOMItemIsSparePart)
Original property name from the Odata EDM: BOMItemIsSparePart
In a BOM explosion, you can use this indicator to restrict item selection.The indicator does not interrupt the explosion of the BOM to the lowest level. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Spare part indicator.These indicators work as filters. The explosion result, you see on the screen only the items that fulfil the selection criteria. In this case, only the items with the spare part indicator you selected are shown.In the IMG for BOMs, you can group spare parts together according to various points of view - for example, according to different maintenance cycles.Spare part group A contains spare parts that need to be replaced after a machine runtime of 100 hours, whereas spare part group B contains spare parts that only need to be replaced after a machine runtime of 500 hours.
bOMItemIsSparePart
- This key defines the item as a spare part.public void setBOMItemIsSalesRelevant(@Nullable String bOMItemIsSalesRelevant)
Original property name from the Odata EDM: BOMItemIsSalesRelevant
For example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Relevant to sales indicator.This status indicator works as a filter. The explosion result you see on the screen only includes the items that fulfil the selection criteria. In this case, only the items that are relevant to sales are shown.
bOMItemIsSalesRelevant
- This indicator shows that this item is relevant to the sales and distribution area of a company.public void setIsProductionRelevant(@Nullable Boolean isProductionRelevant)
Original property name from the Odata EDM: IsProductionRelevant
Items with this indicator are copied to the planned order, and the system calculates dependent requirements for them. When the planned order is converted to a production order, the system automatically copies these items to the production order.This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
isProductionRelevant
- Indicates that the item is relevant to the production process.public void setBOMItemIsPlantMaintRelevant(@Nullable Boolean bOMItemIsPlantMaintRelevant)
Original property name from the Odata EDM: BOMItemIsPlantMaintRelevant
Items that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
bOMItemIsPlantMaintRelevant
- Indicates that this item is relevant to plant maintainance procedures.public void setBOMItemIsCostingRelevant(@Nullable String bOMItemIsCostingRelevant)
Original property name from the Odata EDM: BOMItemIsCostingRelevant
The extent is controlled by predefined factors for fixed and variable costs respectively.If this indicator is not set, the item is not costed.Indicator "x" determines that the item is always relevant to costing in all ways. This means that you do not need to maintain factors.You can enter factors if another indicator is entered.Factors between 0 and 1 are primarily used in inventory costing. These factors are not relevant to standard costing or order costing.Example: factor 0.5 in standard costing means that the item is costed with a factor of 1. Factor 0 means that the item is not costed.
bOMItemIsCostingRelevant
- This key controls whether and to what extent this item is relevant to costing.public void setIsEngineeringRelevant(@Nullable Boolean isEngineeringRelevant)
Original property name from the Odata EDM: IsEngineeringRelevant
This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
isEngineeringRelevant
- Indicates that this item is relevant to the area responsible for producing a functional design for production.public void setSpecialProcurementType(@Nullable String specialProcurementType)
Original property name from the Odata EDM: SpecialProcurementType
Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce a material in-house, it may be appropriate to choose Production in other plant.
specialProcurementType
- Allows you to define the procurement type more closely. The procurement type is determined from the material type.public void setIsBOMRecursiveAllowed(@Nullable Boolean isBOMRecursiveAllowed)
Original property name from the Odata EDM: IsBOMRecursiveAllowed
If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
isBOMRecursiveAllowed
- Indicator: controls whether the system checks the BOM for recursiveness.public void setOperationLeadTimeOffset(@Nullable BigDecimal operationLeadTimeOffset)
Original property name from the Odata EDM: OperationLeadTimeOffset
(In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.---------------------------------------------------------Component Operation Lead-time offset (h) End dateM-01 0010 2+ 05.13.1998, 11 a.m.M-02 0020 2- 05.14.1998, 12 a.m.The component M-01 does not have to be available until 2 hours after the start time of the allocated operation 0010.Because the component M-02 must be available 2 hours before the start time of the allocated operation, the end time is 12 a.m.
operationLeadTimeOffset
- Time that the component lead-time offset states with reference to the start date of the allocated operation.public void setOpsLeadTimeOffsetUnit(@Nullable String opsLeadTimeOffsetUnit)
Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
opsLeadTimeOffsetUnit
- Unit for lead-time offset for operationpublic void setIsMaterialProvision(@Nullable String isMaterialProvision)
Original property name from the Odata EDM: IsMaterialProvision
In the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part. The following indicators are available:Refurbishment material to SC (value S in standard SAP system)Refurbishment material from SC (value X in standard SAP system)Subsequent delivery (value F in standard SAP system)If you do not enter information in this field, the components are provided to the subcontractor as consumable materials (initial value in the standard SAP system).Material provided by a vendorThis indicator controls material requirements planning. Maintain this indicator for BOM components only if the material master record of the header material supports subcontracting (Special procurement field).The special procurement key for subcontracting means that all components of the BOM are provided free of charge to a subcontractor for further processing. The items are copied to a subcontract order.If the item is provided to a vendor, do not enter any material provision indicator.Dependent requirements are generated for this item.If the item is already at a vendor's premises and is not provided by us, do enter an indicator.No dependent requirements are generated for this item.Material provided by a customerThis indicator is not currently active.
isMaterialProvision
- This key indicates that the item is subject to material provision.public void setBOMIsRecursive(@Nullable Boolean bOMIsRecursive)
Original property name from the Odata EDM: BOMIsRecursive
In BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
bOMIsRecursive
- Indicator set by the system if the exploded BOM for an object contains the object itself as an item.public void setDocumentIsCreatedByCAD(@Nullable Boolean documentIsCreatedByCAD)
Original property name from the Odata EDM: DocumentIsCreatedByCAD
documentIsCreatedByCAD
- Information: data for the assembly/component was generated in a CAD system and transferred into the SAP system via an interface.public void setDistrKeyCompConsumption(@Nullable String distrKeyCompConsumption)
Original property name from the Odata EDM: DistrKeyCompConsumption
This means that the MRP controller can plan a daily supply of partial quantities (distributed over the validity period of the RS header) for repetitive manufacturing.
distrKeyCompConsumption
- Determines the split to be used for distributing the run schedule quantity (into partial quantities) over the validity period of the planned order or the production order. In so doing, the relationship between time and the consumption of components is established.public void setDeliveryDurationInDays(@Nullable BigDecimal deliveryDurationInDays)
Original property name from the Odata EDM: DeliveryDurationInDays
When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
deliveryDurationInDays
- Gives the delivery time for the material in days.public void setCreditor(@Nullable String creditor)
Original property name from the Odata EDM: Creditor
creditor
- Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.public void setCostElement(@Nullable String costElement)
Original property name from the Odata EDM: CostElement
which is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
costElement
- Number of the G/L accountpublic void setSize1(@Nullable BigDecimal size1)
Original property name from the Odata EDM: Size1
Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
size1
- One dimension of the variable-size item, used as a variable in the variable-size item formula.public void setSize2(@Nullable BigDecimal size2)
Original property name from the Odata EDM: Size2
Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
size2
- One dimension of the variable-size item, used as a variable in the variable-size item formula.public void setSize3(@Nullable BigDecimal size3)
Original property name from the Odata EDM: Size3
Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
size3
- One dimension of the variable-size item, used as a variable in the variable-size item formula.public void setUnitOfMeasureForSize1To3(@Nullable String unitOfMeasureForSize1To3)
Original property name from the Odata EDM: UnitOfMeasureForSize1To3
Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
unitOfMeasureForSize1To3
- Unit of measure for sizes 1 to 3.public void setGoodsReceiptDuration(@Nullable BigDecimal goodsReceiptDuration)
Original property name from the Odata EDM: GoodsReceiptDuration
goodsReceiptDuration
- Number of workdays required after receiving the material for inspection and placement into storage.public void setPurchasingOrganization(@Nullable String purchasingOrganization)
Original property name from the Odata EDM: PurchasingOrganization
purchasingOrganization
- Denotes the purchasing organization.public void setRequiredComponent(@Nullable Boolean requiredComponent)
Original property name from the Odata EDM: RequiredComponent
requiredComponent
- If this class is used as a class item in a configurable object, this setting has the following effect in interactive configuration: the configuration is incomplete until the class item has been replaced by an object. In low-level configuration (MRP, for example), the "Required component" indicator has no further effects.public void setMultipleSelectionAllowed(@Nullable Boolean multipleSelectionAllowed)
Original property name from the Odata EDM: MultipleSelectionAllowed
multipleSelectionAllowed
- This indicator influences the status of a configuration in cases where a class item has been replaced by more than one object. Only if the configuration scenario allows manual changes to the BOM (order BOM or sales order with manual changes) can a class item be temporarily replaced by more than one object. However, before you save, the selection must be restricted to one object by using a manual object search. If you leave the configuration while the class item is still replaced by more than one object, only the first object is saved or transferred to the calling application. The "Multiple Selection" indicator has the following effect in interactive configuration: the configuration is still consistent if the class item has been replaced by more than one object. Without this indicator, the configuration is inconsistent if the class item has been replaced by more than one object. In low-level configuration (MRP, for example), only one object is used to replace the class, whether or not the "Multiple Selection" indicator is set.public void setProdOrderIssueLocation(@Nullable String prodOrderIssueLocation)
Original property name from the Odata EDM: ProdOrderIssueLocation
In production, first there is a check as to whether an issue location is entered in the BOM item.If there is an issue location in the BOM item, this issue location is copied to the production order as a default value. Otherwise, the issue location is copied from the material master record (in the plant in which you created the BOM).This indicator is only supported for items that are relevant to production and plant maintenance.You cannot enter an issue location for a bulk material.
prodOrderIssueLocation
- Number of the issue location from which the material is issued during the production process. Backflush is posted to this issue location if required.public void setMaterialIsCoProduct(@Nullable Boolean materialIsCoProduct)
Original property name from the Odata EDM: MaterialIsCoProduct
Enter a negative quantity.Example: 6- You can only enter an item as a co-product if:The material master (MRP 2 view) contains the Material can be a co-product indicator. (For some material types, such as raw materials for example, the co-product indicator is hidden in the standard SAP system.)You enter the item as a stock item
materialIsCoProduct
- Indicator showing that the item is a co-product.public void setExplosionType(@Nullable String explosionType)
Original property name from the Odata EDM: ExplosionType
You can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
explosionType
- This is used to control the explosion of an item when determining dependent requirements.public void setAlternativeItemGroup(@Nullable String alternativeItemGroup)
Original property name from the Odata EDM: AlternativeItemGroup
As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:dependent requirements are determined in requirements planningdependent requirements are changed to a reservation in the production orderAlternative positions as informationYou can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.Enter the same character string to denote the alternative items of an alternative item group.Enter the same strategy for all alternative items in the alternative item group.Alternative items are valuated in the following way:Dependent requirements determinationRequirements planning determines the dependent requirements according to the usage probabilities that have been entered.If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created.Withdrawal postingYou can control the withdrawal posting for the resevation in the production order in the following way:Withdrawal according to usage probability (manual change is possible)Withdrawal if there is 100% availability(Check ranking order and strategy)Example: See Strategy for alternative position
alternativeItemGroup
- Consolidation of alternative items within a BOM. Every material in the assembly can be included in the alternative item group.public void setFollowUpGroup(@Nullable String followUpGroup)
Original property name from the Odata EDM: FollowUpGroup
You can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials. When an item (main item) is discontinued, another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: discontinuation indicator value 1Material of the dependent item: value 3Settings in the BOM:The main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.You can only maintain an item as a follow-up item when you enter it for the first time. The field value cannot be changed after you have entered and saved the item.The follow-up item(s) that are to replace the item to be discontinued must have the same value in the Discontinuation group field as the item to be discontinued has in the Follow-up group field (see the example below).The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.You can only maintain the follow-up group for one item if:the component is planned to a schedule (for example, a warehouse item)the base unit of measure of the materials is identicalExample of a simple discontinuationfItem 0010 to be discontinued (material M-1) is replaced by item 0010 to be introduced (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Material Discontinuation group Follow-up group0010 M-1 A1 -0010 M-2 - A1Example of a parallel discontinuationthe items 0010 (material M-1) and 0011 (material M-2) are replaced by the items 0010 (material M-3) and 0011 (material M-4) to be ntroduced.Discontinuation indicator in the material master record:M-1: Value 1 (main discontinued item)M-2: Value 3 (dependent discontinued item)Item Material Discontinuation group Follow-up group0010 M-1 A1 -0011 M-2 A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
followUpGroup
- This is a freely-definable character string which is assigned to linked follow-up items in a bill of material. The follow-up group shows which follow-up item(s) are to replace the item to be discontinued.public void setDiscontinuationGroup(@Nullable String discontinuationGroup)
Original property name from the Odata EDM: DiscontinuationGroup
You can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group. If an item is to be discontinued (main item), another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: value 1Material of the dependent item: value 3Settings in the BOM:Both the main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.Both the follow-up group of the items to be introduced and the discontinuation group of the items to be discontinued must have the same value.You can only enter a discontinuation group for an item if the discontinuation indicator (material master, MRP 4 view) supports discontinuation.A discontinued item is replaced by a follow-up item. In the follow-up item, you maintain a follow-up group.Example for a simple discontinuationItem 0010 (material M-1) is to be discontinued and replaced by follow-up item 0010 (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Mat. DisconGrp FollGrp 0010 M-1 A1 -0010 M-2 - A1Example for a Parallel discontinuationItems 0010 (material M-1) and 0011 (material M-2) to be discontinued are replaced by items 0010 (material M-3) and 0011 (material M-4) to be introduced.Discontinuation indicator in the material master record:M-1: value 1 (main discontinued item)M-2: value 3 (dependent discontinued item)Item Mat. Discontinuation group Follow-up group0010 M-1 ,A1 -0011 M-2 ,A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
discontinuationGroup
- This freely-definable character string is used to group together related items to be discontinued in a BOM.public void setIsConfigurableBOM(@Nullable String isConfigurableBOM)
Original property name from the Odata EDM: IsConfigurableBOM
isConfigurableBOM
- Selection indicator for configurable BOMspublic void setReferencePoint(@Nullable String referencePoint)
Original property name from the Odata EDM: ReferencePoint
referencePoint
- Creates a logical link between BOM items and network activities.public void setLeadTimeOffset(@Nullable BigDecimal leadTimeOffset)
Original property name from the Odata EDM: LeadTimeOffset
This value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
leadTimeOffset
- This value shows the lead-time offset (in workdays) for the component in relation to the start date for production of the superior assembly.public void setProductionSupplyArea(@Nullable String productionSupplyArea)
Original property name from the Odata EDM: ProductionSupplyArea
The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
productionSupplyArea
- The production supply area (PSA) serves as a place for interim storage on the shop floor and is used to make material directly available for production purposes.public void setIsDeleted(@Nullable Boolean isDeleted)
Original property name from the Odata EDM: IsDeleted
This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
isDeleted
- Indicator showing that the BOM header or the BOM item has been deleted with reference to the change number.public void setIsALE(@Nullable Boolean isALE)
Original property name from the Odata EDM: IsALE
isALE
- Shows that data of the assembly or component has been distributed to the SAP system using ALE.protected String getEndpointUrl()
getEndpointUrl
in class VdmEntity<BillOfMaterialItem>
protected String getEntityCollection()
getEntityCollection
in class VdmEntity<BillOfMaterialItem>
protected Map<String,Object> getKey()
getKey
in class VdmObject<BillOfMaterialItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<BillOfMaterialItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
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.public static BillOfMaterialItem.BillOfMaterialItemBuilder builder()
@Nullable public UUID getBillOfMaterialItemUUID()
Original property name from the Odata EDM: BillOfMaterialItemUUID
@Nullable public String getBillOfMaterialCategory()
Original property name from the Odata EDM: BillOfMaterialCategory
Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
@Nullable public String getBillOfMaterial()
Original property name from the Odata EDM: BillOfMaterial
The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
@Nullable public String getBillOfMaterialVariant()
Original property name from the Odata EDM: BillOfMaterialVariant
One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
@Nullable public String getBillOfMaterialVersion()
Original property name from the Odata EDM: BillOfMaterialVersion
@Nullable public String getBillOfMaterialItemNodeNumber()
Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
@Nullable public String getBOMItemInternalChangeCount()
Original property name from the Odata EDM: BOMItemInternalChangeCount
@Nullable public LocalDateTime getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public LocalDateTime getValidityEndDate()
Original property name from the Odata EDM: ValidityEndDate
@Nullable public String getEngineeringChangeDocument()
Original property name from the Odata EDM: EngineeringChangeDocument
If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
@Nullable public String getChgToEngineeringChgDocument()
Original property name from the Odata EDM: ChgToEngineeringChgDocument
If the object has been changed using a change number, the system determines this change number automatically.Three change numbers (N1, N2 and N3) define the validity periods of the item:N1 N2 N3I-----------I----------------------I---------------->1.1.96 6.1.96 12.2.96If you change the item within the validity period of change number N1, the system enters N2 in Change number to.If you change the item within the validity period of change number N2, the system enters N3 in Change number to.
@Nullable public String getInheritedNodeNumberForBOMItem()
Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
@Nullable public LocalDateTime getBOMItemRecordCreationDate()
Original property name from the Odata EDM: BOMItemRecordCreationDate
@Nullable public String getBOMItemCreatedByUser()
Original property name from the Odata EDM: BOMItemCreatedByUser
@Nullable public LocalDateTime getBOMItemLastChangeDate()
Original property name from the Odata EDM: BOMItemLastChangeDate
@Nullable public String getBOMItemLastChangedByUser()
Original property name from the Odata EDM: BOMItemLastChangedByUser
@Nullable public String getBillOfMaterialComponent()
Original property name from the Odata EDM: BillOfMaterialComponent
A master record is usually maintained in the system for a component.
@Nullable public String getBillOfMaterialItemCategory()
Original property name from the Odata EDM: BillOfMaterialItemCategory
This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
@Nullable public String getBillOfMaterialItemNumber()
Original property name from the Odata EDM: BillOfMaterialItemNumber
@Nullable public String getBillOfMaterialItemUnit()
Original property name from the Odata EDM: BillOfMaterialItemUnit
The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
@Nullable public BigDecimal getBillOfMaterialItemQuantity()
Original property name from the Odata EDM: BillOfMaterialItemQuantity
You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
@Nullable public String getIsAssembly()
Original property name from the Odata EDM: IsAssembly
@Nullable public Boolean getIsSubItem()
Original property name from the Odata EDM: IsSubItem
Sub-items do not have an operational significance and changes arenot stored with history.
@Nullable public String getBOMItemSorter()
Original property name from the Odata EDM: BOMItemSorter
@Nullable public Boolean getFixedQuantity()
Original property name from the Odata EDM: FixedQuantity
A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
@Nullable public String getPurchasingGroup()
Original property name from the Odata EDM: PurchasingGroup
Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.
@Nullable public String getCurrency()
Original property name from the Odata EDM: Currency
@Nullable public BigDecimal getMaterialComponentPrice()
Original property name from the Odata EDM: MaterialComponentPrice
@Nullable public String getIdentifierBOMItem()
Original property name from the Odata EDM: IdentifierBOMItem
@Nullable public BigDecimal getMaterialPriceUnitQty()
Original property name from the Odata EDM: MaterialPriceUnitQty
If 10 gallons of gasoline cost $12.00, the price unit is 10.
@Nullable public BigDecimal getComponentScrapInPercent()
Original property name from the Odata EDM: ComponentScrapInPercent
Component scrap is used in material requirements planning (MRP) to determine the quantities of components required. When exploding the bill of material (BOM), the system increases the required quantities of the components by the calculated scrap quantity.ExampleRequired quantity 200 piecesComponent scrap 10%Scrap quantity 20 piecesTherefore, 220 pieces are required.For examples of calculation in connection with the indicator for net scrap, see the documentation for this indicator.If there is also assembly scrap for a higher-level assembly, the system adds together the two types of scrap.If component scrap has been entered in the BOM, this value applies. Otherwise, the value specified in the material master record is used.
@Nullable public BigDecimal getOperationScrapInPercent()
Original property name from the Odata EDM: OperationScrapInPercent
This entry is used to override the assembly scrap for materials of high value.If operation scrap is maintained, you avoid the situation whereby too much of the material is planned in MRP for the components of subsequent operations.If you make an entry for operation scrap, you must also select the operation scrap net indicator (Net field).You can find examples of scrap under net scrap.
@Nullable public Boolean getIsNetScrap()
Original property name from the Odata EDM: IsNetScrap
You must set this indicator if you want assembly scrap to be ignored.You must set this indicator if you enter operation scrap.You can set this indicator if you only enter component scrap, to calculate scrap on the basis of the net required quantity for the assembly.Bill of material:Assembly MAT-1:Required quantity 100 piecesAssembly scrap 2%Component MAT-2:Component quantity 100 piecesDepending on the applicable scrap and the net indicator, the following 6 quantities are required for component MAT-2 for a required quantity of 100 pieces of MAT-1:1 2 3 4 5 6 Comp 5% - 5% 5% - -Op. 6% 6% - - - -Net ind X X X - - X---------------------------------------------------------------------Qty 11130 10600 10500 10710 10200 10000KeyComp Component scrapOp. Operation scrapNet ind Net indicatorQty Quantity calculated for component MAT-2 in pieces
@Nullable public BigDecimal getNumberOfVariableSizeItem()
Original property name from the Odata EDM: NumberOfVariableSizeItem
@Nullable public BigDecimal getQuantityVariableSizeItem()
Original property name from the Odata EDM: QuantityVariableSizeItem
The quantity of the variable-size item shown is per piece (PC)If you change a field that affects the calculation of the variable-size item quantity (for example, size or formula), the system only recalculates the quantity if you delete the existing quantity first.To do this, delete the contents of the Qty Var-sz item field.Size 1: 200Size 2: 300Size unit of measure: MMVariable size item unit: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 0,06 SQM--> The variable-size item quantity for each piece is: 0.06 SQMThe value calculated is required in MRP, in order to calculate the total quantity of the raw material requirement for the component.If 10 pieces are required for the component, the variable-size item quantity is: 10 * 0.06 SQM = 0.6 SQM.
@Nullable public String getFormulaKey()
Original property name from the Odata EDM: FormulaKey
You want to calculate the volume of a rolled sheet of metal. This has a variable length and height, but a constant width (500 MM).The following are used in the calculation:SI units that are defined in CustomizingLength: M (meters)Volume: M3 (cubic meters)In the variable-size item, you only enter the variable values (size 1 and size 2) with a unit of measure that can be derived from the SI unit of the dimension.Example for dimension Length: MM (milllimeters), CM (centimeters), DM (decimeters), and M (meters)The variable-size item formula uses the SI unit, so you must enter the constant width in the formula in the SI unit (meters).Example: ROMS1 * ROMS2 * 0.5 (M)You can enter units of measure for calculating the variable-size item quantity with a formula. The quantity is always calculated in the SI unit of the dimension, such as M3 (cubic meters) for volume.
@Nullable public String getBOMItemDescription()
Original property name from the Odata EDM: BOMItemDescription
If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
@Nullable public String getBOMItemText2()
Original property name from the Odata EDM: BOMItemText2
You can also enter a long text by choosing menu option Details --> Long text --> Item long text.If the text comprises less than three lines, it is stored in the BOM item. Otherwise, it is stored as a long text in the text database.
@Nullable public String getMaterialGroup()
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
@Nullable public String getDocumentType()
Original property name from the Odata EDM: DocumentType
@Nullable public String getDocNumber()
Original property name from the Odata EDM: DocNumber
@Nullable public String getDocumentVersion()
Original property name from the Odata EDM: DocumentVersion
A new version is assigned after the original files have been edited in the following processing situations:The new processing status varies from the original in a certain way (for example, text change sin a text file).You want the original processing status to remain the same (for example, documentation of project progress).
@Nullable public String getDocumentPart()
Original property name from the Odata EDM: DocumentPart
Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
@Nullable public String getClassNumber()
Original property name from the Odata EDM: ClassNumber
@Nullable public String getClassType()
Original property name from the Odata EDM: ClassType
@Nullable public String getResultingItemCategory()
Original property name from the Odata EDM: ResultingItemCategory
This categorization allows you to process data that is relevant to BOM items for all objects allocated to the class. For example, you control field selection and special system activities when you select the resulting item category.The class type determines which resulting item category you can select:If the class type is linked to the material master, you can select one of the following resulting item categories:stock itemnon-stock itemvariable-size itemPM structure elementIf the class type is linked to documents, you can enter document item as the resulting item category.
@Nullable public String getDependencyObjectNumber()
Original property name from the Odata EDM: DependencyObjectNumber
@Nullable public String getObjectType()
Original property name from the Odata EDM: ObjectType
Via settings in Customizing (Bill of mat. -> Item data), you can define a language-dependent abbreviation which the system displays on the General item overview screen.
@Nullable public Boolean getIsClassificationRelevant()
Original property name from the Odata EDM: IsClassificationRelevant
If you select this indicator, the classification of the item is taken into account when the object is configured.You can only select this indicator if you have classified the item first (entered a class type).
@Nullable public Boolean getIsBulkMaterial()
Original property name from the Odata EDM: IsBulkMaterial
The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.Dependent requirements are only created in the planned order for information purposes and they can be displayed there. Dependent requirements for bulk material are not shown in the MRP list or the stock/req. list.You can maintain this indicator in both the material master record an the BOM item. The indicator in the material master record has higher priority.If a material is always used as a bulk material, set the indicator in the material master record.In this case, the Bulk material indicator in material master record is automatically set in the BOM item.If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.To improve system performance, you can define in the IMG for MRP that no dependent requirements are to be created for bulk material items. However, this also means that you see no information on bulk material components in the planned order or production order.
@Nullable public String getBOMItemIsSparePart()
Original property name from the Odata EDM: BOMItemIsSparePart
In a BOM explosion, you can use this indicator to restrict item selection.The indicator does not interrupt the explosion of the BOM to the lowest level. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Spare part indicator.These indicators work as filters. The explosion result, you see on the screen only the items that fulfil the selection criteria. In this case, only the items with the spare part indicator you selected are shown.In the IMG for BOMs, you can group spare parts together according to various points of view - for example, according to different maintenance cycles.Spare part group A contains spare parts that need to be replaced after a machine runtime of 100 hours, whereas spare part group B contains spare parts that only need to be replaced after a machine runtime of 500 hours.
@Nullable public String getBOMItemIsSalesRelevant()
Original property name from the Odata EDM: BOMItemIsSalesRelevant
For example, in sales order processing vor variant products, you see items that are relevant to sales as order items for the header material.This item status indicator is used to control:subsequent processing in related application areaswhich items are selected in the BOM explosionThe indicator does not interrupt the explosion of the BOM to the lowest lever. There are two steps to the BOM explosion:First, the system explodes the entire BOM, regardless of the indicators selected to restrict items. You do not see the result of this explosion on the screen.Second, the system reads the indicators selected to restrict items, such as the Relevant to sales indicator.This status indicator works as a filter. The explosion result you see on the screen only includes the items that fulfil the selection criteria. In this case, only the items that are relevant to sales are shown.
@Nullable public Boolean getIsProductionRelevant()
Original property name from the Odata EDM: IsProductionRelevant
Items with this indicator are copied to the planned order, and the system calculates dependent requirements for them. When the planned order is converted to a production order, the system automatically copies these items to the production order.This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
@Nullable public Boolean getBOMItemIsPlantMaintRelevant()
Original property name from the Odata EDM: BOMItemIsPlantMaintRelevant
Items that are relevant to plant maintenance are used in maintenance BOMs (material BOMs that are relevant to plant maintenance, equipment BOMs, and functional location BOMs).This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
@Nullable public String getBOMItemIsCostingRelevant()
Original property name from the Odata EDM: BOMItemIsCostingRelevant
The extent is controlled by predefined factors for fixed and variable costs respectively.If this indicator is not set, the item is not costed.Indicator "x" determines that the item is always relevant to costing in all ways. This means that you do not need to maintain factors.You can enter factors if another indicator is entered.Factors between 0 and 1 are primarily used in inventory costing. These factors are not relevant to standard costing or order costing.Example: factor 0.5 in standard costing means that the item is costed with a factor of 1. Factor 0 means that the item is not costed.
@Nullable public Boolean getIsEngineeringRelevant()
Original property name from the Odata EDM: IsEngineeringRelevant
This item status indicator is used to control:Subsequent processing in related application areasSelection of items in the BOM explosionWhether you can set and remove this indicator, or whether the system makes an unchangeable setting, depends on the BOM usage you selected on the initial screen. You can find further information in Customizing for bills of material under General Data -> BOM Usage -> Define BOM usages.
@Nullable public String getSpecialProcurementType()
Original property name from the Odata EDM: SpecialProcurementType
Enter the special procurement type to which you want to restrict the selection.If you procure a material externally, you may want to choose the special procurement type Consignment. If you produce a material in-house, it may be appropriate to choose Production in other plant.
@Nullable public Boolean getIsBOMRecursiveAllowed()
Original property name from the Odata EDM: IsBOMRecursiveAllowed
If you set the Indicator: recursiveness allowed, no recursiveness check is made for the item concerned: you can create a recursive BOM.
@Nullable public BigDecimal getOperationLeadTimeOffset()
Original property name from the Odata EDM: OperationLeadTimeOffset
(In the Project System read activity for operation.)The following areas evaluate the operation related lead-time offset:Plant maintenance ordersNetworksProduction ordersProcess ordersMaintain the following times dependently of the +/- sign:Lead-time offset - positive valueComponent can be available after the operation start dateLead time - negative valueComponent must be available before the operation start dateOperation start date 0010: 05.13.1998, 9 a.m.Operation start date 0020: 05.14.1998, 2 p.m.---------------------------------------------------------Component Operation Lead-time offset (h) End dateM-01 0010 2+ 05.13.1998, 11 a.m.M-02 0020 2- 05.14.1998, 12 a.m.The component M-01 does not have to be available until 2 hours after the start time of the allocated operation 0010.Because the component M-02 must be available 2 hours before the start time of the allocated operation, the end time is 12 a.m.
@Nullable public String getOpsLeadTimeOffsetUnit()
Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
@Nullable public String getIsMaterialProvision()
Original property name from the Odata EDM: IsMaterialProvision
In the BOM explosion, you can use this indicator to restrict the items selected.There are two types of material provision:Material provided by a vendorMaterial provided by a customerYou can also use the material provision indicator to identify the subcontracting type for a part. The following indicators are available:Refurbishment material to SC (value S in standard SAP system)Refurbishment material from SC (value X in standard SAP system)Subsequent delivery (value F in standard SAP system)If you do not enter information in this field, the components are provided to the subcontractor as consumable materials (initial value in the standard SAP system).Material provided by a vendorThis indicator controls material requirements planning. Maintain this indicator for BOM components only if the material master record of the header material supports subcontracting (Special procurement field).The special procurement key for subcontracting means that all components of the BOM are provided free of charge to a subcontractor for further processing. The items are copied to a subcontract order.If the item is provided to a vendor, do not enter any material provision indicator.Dependent requirements are generated for this item.If the item is already at a vendor's premises and is not provided by us, do enter an indicator.No dependent requirements are generated for this item.Material provided by a customerThis indicator is not currently active.
@Nullable public Boolean getBOMIsRecursive()
Original property name from the Odata EDM: BOMIsRecursive
In BOM maintenanceyou can switch off the recursiveness check by setting the Recursiveness allowed indicatorrecursiveness is usually recognized online and prevented by an error messagein exceptional circumstances, recursiveness is not recognized until the BOM is updatedIn this case, the system sets the BOM is recursive indicator.Explosion path of BOM M10-----------------> |M10|| -----| / \| ---- ----| M3 M2| ---- ----| / \| ----- ------ |M10| M4----- ----
@Nullable public Boolean getDocumentIsCreatedByCAD()
Original property name from the Odata EDM: DocumentIsCreatedByCAD
@Nullable public String getDistrKeyCompConsumption()
Original property name from the Odata EDM: DistrKeyCompConsumption
This means that the MRP controller can plan a daily supply of partial quantities (distributed over the validity period of the RS header) for repetitive manufacturing.
@Nullable public BigDecimal getDeliveryDurationInDays()
Original property name from the Odata EDM: DeliveryDurationInDays
When an order-specific BOM is exploded, a purchase requisition is produced via an MRP program.
@Nullable public String getCreditor()
Original property name from the Odata EDM: Creditor
@Nullable public String getCostElement()
Original property name from the Odata EDM: CostElement
which is to be debited with the goods issue, if you have entered a consumption account, orfor which an account assignment check is to be carried out.This entry is used in various areas:in MRP for purchase requisitionsin costing for pricingYou can only enter a G/L account for which a G/L account master is maintained in the appropriate company code.
@Nullable public BigDecimal getSize1()
Original property name from the Odata EDM: Size1
Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
@Nullable public BigDecimal getSize2()
Original property name from the Odata EDM: Size2
Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
@Nullable public BigDecimal getSize3()
Original property name from the Odata EDM: Size3
Variable-size item data for a sheet of metal:Size Description Entry1 Length 2002 Width 300No. of variable-size items: 10Size unit: MMStockkeeping unit for sheet metalin material master: SQMCalculation of variable-size item quantity:A = Size 1 * Size 2A = 200 MM * 300 MMA = 60.000 SQMM--> Quantity of variable-size item per sheet: 0.06 SQM10 sheets are entered in the component, so the variable-size item requirement is:10 * 0.06 SQM = 0.6 SQM.
@Nullable public String getUnitOfMeasureForSize1To3()
Original property name from the Odata EDM: UnitOfMeasureForSize1To3
Please note:If you do not enter a unit of measure for the size, the system enters the default unit stored in the IMG for BOMs under Control data.The size unit and variable-size item unit are interdependent.Example:Variable-size item data for a metal sheet-----------------------------------------Size Dimension Entry1 Length 2002 Width 300Size unit for variable-size item: MMIf you do not enter a formula, the system uses the standard formula: Size 1 * Size 2 (result -> area).= 200 MM * 300 MM= 60,000 MM2Either the variable-size item unit must have the dimension area (MM2, CM2, M2, and so on), or conversion factors must be maintained in the material master.
@Nullable public BigDecimal getGoodsReceiptDuration()
Original property name from the Odata EDM: GoodsReceiptDuration
@Nullable public String getPurchasingOrganization()
Original property name from the Odata EDM: PurchasingOrganization
@Nullable public Boolean getRequiredComponent()
Original property name from the Odata EDM: RequiredComponent
@Nullable public Boolean getMultipleSelectionAllowed()
Original property name from the Odata EDM: MultipleSelectionAllowed
@Nullable public String getProdOrderIssueLocation()
Original property name from the Odata EDM: ProdOrderIssueLocation
In production, first there is a check as to whether an issue location is entered in the BOM item.If there is an issue location in the BOM item, this issue location is copied to the production order as a default value. Otherwise, the issue location is copied from the material master record (in the plant in which you created the BOM).This indicator is only supported for items that are relevant to production and plant maintenance.You cannot enter an issue location for a bulk material.
@Nullable public Boolean getMaterialIsCoProduct()
Original property name from the Odata EDM: MaterialIsCoProduct
Enter a negative quantity.Example: 6- You can only enter an item as a co-product if:The material master (MRP 2 view) contains the Material can be a co-product indicator. (For some material types, such as raw materials for example, the co-product indicator is hidden in the standard SAP system.)You enter the item as a stock item
@Nullable public String getExplosionType()
Original property name from the Odata EDM: ExplosionType
You can define an explosion type that transfers dependent requirements for phantom assemblies.For example, the explosion type is relevant to materials that have the following special procurement types:Phantom assemblyPhantom in planningDirect production (collective order)Direct procurementYou can also define whether the following functions are performed for the item:Long-term planningDeterming individual and collective requirements
@Nullable public String getAlternativeItemGroup()
Original property name from the Odata EDM: AlternativeItemGroup
As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.You can maintain alternative items in the following situations:Alternative positions with specific usage probabilityThese alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:dependent requirements are determined in requirements planningdependent requirements are changed to a reservation in the production orderAlternative positions as informationYou can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.Enter the same character string to denote the alternative items of an alternative item group.Enter the same strategy for all alternative items in the alternative item group.Alternative items are valuated in the following way:Dependent requirements determinationRequirements planning determines the dependent requirements according to the usage probabilities that have been entered.If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created.Withdrawal postingYou can control the withdrawal posting for the resevation in the production order in the following way:Withdrawal according to usage probability (manual change is possible)Withdrawal if there is 100% availability(Check ranking order and strategy)Example: See Strategy for alternative position
@Nullable public String getFollowUpGroup()
Original property name from the Odata EDM: FollowUpGroup
You can control the discontinuation in the following way:Simple discontinuationSettings in the material master record (MRP 4 view):The discontinuation indicator value 1 is set In the material master record of the material to be discontinued.Settings in the BOM:The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.Dependent parallel discontinuationOne group of materials is replaced by another group of materials. When an item (main item) is discontinued, another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: discontinuation indicator value 1Material of the dependent item: value 3Settings in the BOM:The main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.The value of the follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must be the same.You can only maintain an item as a follow-up item when you enter it for the first time. The field value cannot be changed after you have entered and saved the item.The follow-up item(s) that are to replace the item to be discontinued must have the same value in the Discontinuation group field as the item to be discontinued has in the Follow-up group field (see the example below).The follow-up item defined in the BOM overrides any follow-up material defined in the material master record.You can only maintain the follow-up group for one item if:the component is planned to a schedule (for example, a warehouse item)the base unit of measure of the materials is identicalExample of a simple discontinuationfItem 0010 to be discontinued (material M-1) is replaced by item 0010 to be introduced (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Material Discontinuation group Follow-up group0010 M-1 A1 -0010 M-2 - A1Example of a parallel discontinuationthe items 0010 (material M-1) and 0011 (material M-2) are replaced by the items 0010 (material M-3) and 0011 (material M-4) to be ntroduced.Discontinuation indicator in the material master record:M-1: Value 1 (main discontinued item)M-2: Value 3 (dependent discontinued item)Item Material Discontinuation group Follow-up group0010 M-1 A1 -0011 M-2 A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
@Nullable public String getDiscontinuationGroup()
Original property name from the Odata EDM: DiscontinuationGroup
You can control the discontinuation as follows:Simple discontinuationAn item that is to be discontinued is replaced by a an item that is is to be introduced to the BOM.Settings in the material master record (materials planning):The discontinuation indicator value 1 is set in the material master record of the item to be discontinued.Settings in the BOM:The follow-up group of the item to be introduced and the discontinuation group of the item to be discontinued must have the same value.Dependent parallel discontinuationOne group of materials is replaced by another group. If an item is to be discontinued (main item), another item (dependent item) is also discontinued.Settings in the material master record (materials planning):Material of the main item to be discontinued: value 1Material of the dependent item: value 3Settings in the BOM:Both the main item and the dependent parallel item to be discontinued are identified by the same discontinuation group.Both the follow-up group of the items to be introduced and the discontinuation group of the items to be discontinued must have the same value.You can only enter a discontinuation group for an item if the discontinuation indicator (material master, MRP 4 view) supports discontinuation.A discontinued item is replaced by a follow-up item. In the follow-up item, you maintain a follow-up group.Example for a simple discontinuationItem 0010 (material M-1) is to be discontinued and replaced by follow-up item 0010 (material M-2).Discontinuation indicator in the material master record M-1: value 1Item Mat. DisconGrp FollGrp 0010 M-1 A1 -0010 M-2 - A1Example for a Parallel discontinuationItems 0010 (material M-1) and 0011 (material M-2) to be discontinued are replaced by items 0010 (material M-3) and 0011 (material M-4) to be introduced.Discontinuation indicator in the material master record:M-1: value 1 (main discontinued item)M-2: value 3 (dependent discontinued item)Item Mat. Discontinuation group Follow-up group0010 M-1 ,A1 -0011 M-2 ,A1 -0010 M-3 - A10011 M-4 - A1Abbreviations:Item. ItemMat. MaterialDisconGrp Discontinuation groupFollGrp. Follow-up group
@Nullable public String getIsConfigurableBOM()
Original property name from the Odata EDM: IsConfigurableBOM
@Nullable public String getReferencePoint()
Original property name from the Odata EDM: ReferencePoint
@Nullable public BigDecimal getLeadTimeOffset()
Original property name from the Odata EDM: LeadTimeOffset
This value is not included in lead-time scheduling for a task list.You can enter:A positive number of daysThe component is not required until after the start date.A negative number of daysThe component is required before the start date.Assembly AS-11 (start date 05/13/1998):Component Lead-time offset Finish dateM-01 2+ 05/15/1998M-02 2- 05/11/1998M-03 0 05/13/1998Component M-01 is not required until 2 days after the start date for the superior assembly.Component M-02 is required 2 days before the start date for the superior assembly, so the finish date for this component is 05/11/1998.The lead-time offset for component M-03 is 0, so the start date for the superior assembly is the same as the finish date for this component.Note:This information does not tell you the start date for the components, because the data required (such as in-house production time, processing time, or interoperation time) is not shown.
@Nullable public String getProductionSupplyArea()
Original property name from the Odata EDM: ProductionSupplyArea
The PSA is used in Kanban and JIT Outbound processing and in Extended Warehouse Management.
@Nullable public Boolean getIsDeleted()
Original property name from the Odata EDM: IsDeleted
This indicator is relevant to changes that have been made with reference to a change number with a validity that has been specified using a new validity type.
@Nullable public Boolean getIsALE()
Original property name from the Odata EDM: IsALE
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<BillOfMaterialItem>
erpConfigContext
- public String toString()
toString
in class VdmObject<BillOfMaterialItem>
public boolean equals(Object o)
equals
in class VdmObject<BillOfMaterialItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<BillOfMaterialItem>
public int hashCode()
hashCode
in class VdmObject<BillOfMaterialItem>
Copyright © 2018 SAP SE. All rights reserved.