public static final class SalesOrderBOMItem.SalesOrderBOMItemBuilder extends Object
@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterial(SalesOrderBOM value)
value - The SalesOrderBOM to build this SalesOrderBOMItem with.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterial(String value)
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
value - The billOfMaterial to build this SalesOrderBOMItem with.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bomItemCategory(BOMItemCategory value)
value - The BOMItemCategory to build this SalesOrderBOMItem with.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialCategory(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialVariant(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialItemNodeNumber(@Nullable String billOfMaterialItemNodeNumber)
Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder headerChangeDocument(@Nullable String headerChangeDocument)
Original property name from the Odata EDM: HeaderChangeDocument
If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialVariantUsage(@Nullable String billOfMaterialVariantUsage)
Original property name from the Odata EDM: BillOfMaterialVariantUsage
By setting various indicators, you can define the maximum configuration of the item status and define whether an item must be or cannot be processed in a particular area (such as production).A material is used in the areas production and costing in a company. For each area, you maintain a separate BOM with different items:Production BOM:This BOM contains items that are relevant to production. These items are copied to the planned order. Dependent requirements are generated for them, and they are copied to the production order.Costing BOM:This BOM contains items that are relevant to determining the material costs of a product.When you calculate production costs using a quantity structure, the system automatically determines the BOM and all the BOM items that are relevant to costing, in order to calculate manufacturing costs.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialItemUUID(@Nullable UUID billOfMaterialItemUUID)
Original property name from the Odata EDM: BillOfMaterialItemUUID
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemInternalChangeCount(@Nullable String bOMItemInternalChangeCount)
Original property name from the Odata EDM: BOMItemInternalChangeCount
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder validityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder engineeringChangeDocForEdit(@Nullable String engineeringChangeDocForEdit)
Original property name from the Odata EDM: EngineeringChangeDocForEdit
If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder engineeringChangeDocument(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder chgToEngineeringChgDocument(@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.
object (material, for example).this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder inheritedNodeNumberForBOMItem(@Nullable String inheritedNodeNumberForBOMItem)
Original property name from the Odata EDM: InheritedNodeNumberForBOMItem
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemRecordCreationDate(@Nullable LocalDateTime bOMItemRecordCreationDate)
Original property name from the Odata EDM: BOMItemRecordCreationDate
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemCreatedByUser(@Nullable String bOMItemCreatedByUser)
Original property name from the Odata EDM: BOMItemCreatedByUser
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemLastChangeDate(@Nullable LocalDateTime bOMItemLastChangeDate)
Original property name from the Odata EDM: BOMItemLastChangeDate
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemLastChangedByUser(@Nullable String bOMItemLastChangedByUser)
Original property name from the Odata EDM: BOMItemLastChangedByUser
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialComponent(@Nullable String billOfMaterialComponent)
Original property name from the Odata EDM: BillOfMaterialComponent
A master record is usually maintained in the system for a component.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialItemCategory(@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.
(for example, material master or document info record) or whether they are kept in stock.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialItemNumber(@Nullable String billOfMaterialItemNumber)
Original property name from the Odata EDM: BillOfMaterialItemNumber
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialItemUnit(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder billOfMaterialItemQuantity(@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
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isAssembly(@Nullable String isAssembly)
Original property name from the Odata EDM: IsAssembly
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isSubItem(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemSorter(@Nullable String bOMItemSorter)
Original property name from the Odata EDM: BOMItemSorter
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder fixedQuantity(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemHasFixedQuantity(@Nullable Boolean bOMItemHasFixedQuantity)
Original property name from the Odata EDM: BOMItemHasFixedQuantity
A fixed quantity is not allowed for the following items:alternative itemco-productIf the component quantity isfixed,The quantity fixed quantity is not in proportion to the assembly being produced or the order quantity.The quantity for provision of material is fixed.not fixed,The quantity is in proportion to the quantity of the assembly being produced or the order quantity.The quantity for provision of material is in proportion to the order quantity.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder purchasingGroup(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder currency(@Nullable String currency)
Original property name from the Odata EDM: Currency
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder materialComponentPrice(@Nullable BigDecimal materialComponentPrice)
Original property name from the Odata EDM: MaterialComponentPrice
purposes.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder identifierBOMItem(@Nullable String identifierBOMItem)
Original property name from the Odata EDM: IdentifierBOMItem
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder materialPriceUnitQty(@Nullable BigDecimal materialPriceUnitQty)
Original property name from the Odata EDM: MaterialPriceUnitQty
If 10 gallons of gasoline cost $12.00, the price unit is 10.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder componentScrapInPercent(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder operationScrapInPercent(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isNetScrap(@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
quantity (the required quantity without assembly scrap from the material master record).this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder numberOfVariableSizeItem(@Nullable BigDecimal numberOfVariableSizeItem)
Original property name from the Odata EDM: NumberOfVariableSizeItem
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder quantityVariableSizeItem(@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.
enter a variable-size item formula for the. calculation.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder formulaKey(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder componentDescription(@Nullable String componentDescription)
Original property name from the Odata EDM: ComponentDescription
If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemDescription(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemText2(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder materialGroup(@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
them to a particular material group.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder documentType(@Nullable String documentType)
Original property name from the Odata EDM: DocumentType
organizational procedures which result from them.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder docNumber(@Nullable String docNumber)
Original property name from the Odata EDM: DocNumber
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder documentVersion(@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).
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder documentPart(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder classNumber(@Nullable String classNumber)
Original property name from the Odata EDM: ClassNumber
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder classType(@Nullable String classType)
Original property name from the Odata EDM: ClassType
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder resultingItemCategory(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder dependencyObjectNumber(@Nullable String dependencyObjectNumber)
Original property name from the Odata EDM: DependencyObjectNumber
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder objectType(@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.
material or document.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isClassificationRelevant(@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).
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isBulkMaterial(@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.
example, washers or grease).this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemIsSparePart(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemIsSalesRelevant(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isProductionRelevant(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemIsPlantMaintRelevant(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMItemIsCostingRelevant(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isEngineeringRelevant(@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.
production.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder specialProcurementType(@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.
material type.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isBOMRecursiveAllowed(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder operationLeadTimeOffset(@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.
operation.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder opsLeadTimeOffsetUnit(@Nullable String opsLeadTimeOffsetUnit)
Original property name from the Odata EDM: OpsLeadTimeOffsetUnit
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isMaterialProvision(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder bOMIsRecursive(@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----- ----
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder documentIsCreatedByCAD(@Nullable Boolean documentIsCreatedByCAD)
Original property name from the Odata EDM: DocumentIsCreatedByCAD
system via an interface.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder distrKeyCompConsumption(@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.
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.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder deliveryDurationInDays(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder creditor(@Nullable String creditor)
Original property name from the Odata EDM: Creditor
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder costElement(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder size1(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder size2(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder size3(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder unitOfMeasureForSize1To3(@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.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder goodsReceiptDuration(@Nullable BigDecimal goodsReceiptDuration)
Original property name from the Odata EDM: GoodsReceiptDuration
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder purchasingOrganization(@Nullable String purchasingOrganization)
Original property name from the Odata EDM: PurchasingOrganization
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder requiredComponent(@Nullable Boolean requiredComponent)
Original property name from the Odata EDM: RequiredComponent
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.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder multipleSelectionAllowed(@Nullable Boolean multipleSelectionAllowed)
Original property name from the Odata EDM: MultipleSelectionAllowed
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.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder prodOrderIssueLocation(@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.
is posted to this issue location if required.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder materialIsCoProduct(@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
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder explosionType(@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
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder alternativeItemGroup(@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
alternative item group.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder alternativeItemPriority(@Nullable String alternativeItemPriority)
Original property name from the Odata EDM: AlternativeItemPriority
With respect to withdrawal postings, the ranking order determines which material components from the alternative item group should be taken into account for the reservation in the production order.Withdrawal according to usage probabilityFor all items that should be reserved, maintain:strategy (value 1 or no entry)ranking order (only effects the material sort)usage probabilityWithdrawal on 100% availabilityFor all items that should be reserved, maintain:ranking orderIf you do not enter the ranking order, the system checks the items in the order that they are transmitted to the availability check.strategy (value 2)usage probabilityThree items (0060 und 0065 and 0070) are assigned to an alternative item group and are given the following values for ranking order:position ranking order0060 30065 20070 1This means that the system reads item 0070 first.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder alternativeItemStrategy(@Nullable String alternativeItemStrategy)
Original property name from the Odata EDM: AlternativeItemStrategy
This strategy is ignored in material requirements planning (MRP).The withdrawal posting for the reservation in the production order can be selected as follows:According to usage probability (manual changes possible)For all items that you want to reserve, enter:Strategy (value 1 or no entry)Priority (only influences how materials are sorted)Usage probabilityWithdrawal if 100% availabilityFor all items that you want to reserve, enter:Strategy (value 2)PriorityIf you do not enter a priority, the system checks the items in the sequence in which they are transferred to the availability check.Usage probabilityEnter the same strategy for all alternative items in an alternative item group.Withdrawal if 100% availability (strategy 2)This strategy uses ATP logic to check availability in the defined ranking order.Gross requirements: 100 piecesM UP (%) RO RQ ATP qty Issue qtyA 20 1 20 30 0B 30 2 30 150 100C 50 3 50 180 0KeyM MaterialUP Usage probabilityRO Ranking orderRQ Requirements quantityThe first material in the ranking order that is supplied 100% on the requirement date is reserved in the required quantity (material B).If a partial withdrawal is carried out in a production order, when additional partial withdrawals take place, no further checks are carried out for this production order. Additional partial withdrawals result from the alternative item, from which the first withdrawal took place.If when using strategy 2 none of the alternative items cover the requirements 100%, the availability check for all items will confirm the available. A reservation only occurs for the available quantity.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder usageProbabilityPercent(@Nullable BigDecimal usageProbabilityPercent)
Original property name from the Odata EDM: UsageProbabilityPercent
The usage probability is always taken into account for requirements planning.Maintain selected usage probabilityRequirements planning for alternative items is based on the usage probability.Quantities are suggested based on the usage probability for the withdrawal posting according to strategy 1. You can plan in excess for the alternative items since the usage probability is not limited to 100%. You can change the proposed quantities. Maintain no usage probability If you do not enter a usage probability, the alternative item just serves as information that can be evaluated, for example, in a situation with a missing part.You receive a warning since dependent requirements with 0 as quantity are created.Withdrawal based on usage probabilityStrategy: value 1An alternative item group is maintained for each assembly. This alternative item group contains four materials with differing usage probabilities. Dependent requirements are passed on with 100 as quantity.Material Usage probability (%) RequirementM-1 70 70M-2 20 20M-3 20 20M-4 0 no requirementIn this case, the materials are planned in excess since the sum of the usage probabilities is greater than 100%.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder followUpGroup(@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
material. The follow-up group shows which follow-up item(s) are to replace the item to be discontinued.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder discontinuationGroup(@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
BOM.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isConfigurableBOM(@Nullable String isConfigurableBOM)
Original property name from the Odata EDM: IsConfigurableBOM
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder referencePoint(@Nullable String referencePoint)
Original property name from the Odata EDM: ReferencePoint
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder leadTimeOffset(@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.
production of the superior assembly.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder productionSupplyArea(@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.
make material directly available for production purposes.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isDeleted(@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.
number.this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder isALE(@Nullable Boolean isALE)
Original property name from the Odata EDM: IsALE
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
If, for example, you want to display or change a sales document and you have only the purchase order number from the customer, you can use a matchcode to find the document.You created a sales order which refers to customer purchase order number 12544-D. To locate the sales order, you can enter =a.12544-D in the sales document field.
this.@Nonnull public SalesOrderBOMItem.SalesOrderBOMItemBuilder salesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
this.@Nonnull public SalesOrderBOMItem build()
Copyright © 2021 SAP SE. All rights reserved.