public static class BOMWhereUsed.BOMWhereUsedBuilder extends Object
Modifier and Type | Method and Description |
---|---|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterial(String billOfMaterial)
Constraints: Not nullable, Maximum length: 8
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialCategory(String billOfMaterialCategory)
Constraints: Not nullable, Maximum length: 1
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialComponent(String billOfMaterialComponent)
Constraints: Not nullable, Maximum length: 40
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialItemCategory(String billOfMaterialItemCategory)
Constraints: Not nullable, Maximum length: 1
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialItemNodeNumber(String billOfMaterialItemNodeNumber)
Constraints: Not nullable, Maximum length: 8
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialItemNumber(String billOfMaterialItemNumber)
Constraints: Not nullable, Maximum length: 4
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialItemQuantity(BigDecimal billOfMaterialItemQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialItemUnit(String billOfMaterialItemUnit)
Constraints: Not nullable, Maximum length: 3
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialItemUUID(UUID billOfMaterialItemUUID)
(Key Field) Constraints: Not nullable
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialVariant(String billOfMaterialVariant)
Constraints: Not nullable, Maximum length: 2
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialVariantUsage(String billOfMaterialVariantUsage)
Constraints: Not nullable, Maximum length: 1
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialVariantUsageDesc(String billOfMaterialVariantUsageDesc)
Constraints: Not nullable, Maximum length: 30
|
BOMWhereUsed.BOMWhereUsedBuilder |
billOfMaterialVersion(String billOfMaterialVersion)
Constraints: Not nullable, Maximum length: 4
|
BOMWhereUsed.BOMWhereUsedBuilder |
bOMItemDescription(String bOMItemDescription)
Constraints: Not nullable, Maximum length: 40
|
BOMWhereUsed.BOMWhereUsedBuilder |
bOMVersionStatus(String bOMVersionStatus)
Constraints: Not nullable, Maximum length: 2
|
BOMWhereUsed.BOMWhereUsedBuilder |
bOMVersionStatusDescription(String bOMVersionStatusDescription)
Constraints: Not nullable, Maximum length: 60
|
BOMWhereUsed |
build() |
BOMWhereUsed.BOMWhereUsedBuilder |
engineeringChangeDocument(String engineeringChangeDocument)
Constraints: Not nullable, Maximum length: 12
|
BOMWhereUsed.BOMWhereUsedBuilder |
headerChangeDocument(String headerChangeDocument)
Constraints: Not nullable, Maximum length: 12
|
BOMWhereUsed.BOMWhereUsedBuilder |
material(String material)
Constraints: Not nullable, Maximum length: 40
|
BOMWhereUsed.BOMWhereUsedBuilder |
materialName(String materialName)
Constraints: Not nullable, Maximum length: 40
|
BOMWhereUsed.BOMWhereUsedBuilder |
plant(String plant)
Constraints: Not nullable, Maximum length: 4
|
BOMWhereUsed.BOMWhereUsedBuilder |
plantName(String plantName)
Constraints: Not nullable, Maximum length: 30
|
String |
toString() |
BOMWhereUsed.BOMWhereUsedBuilder |
validityEndDate(LocalDateTime validityEndDate)
Constraints: Not nullable, Precision: 0
|
BOMWhereUsed.BOMWhereUsedBuilder |
validityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 0
|
@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder billOfMaterialItemUUID(@Nullable UUID billOfMaterialItemUUID)
Original property name from the Odata EDM: BillOfMaterialItemUUID
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder billOfMaterialItemNumber(@Nullable String billOfMaterialItemNumber)
Original property name from the Odata EDM: BillOfMaterialItemNumber
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder billOfMaterial(@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
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder billOfMaterialVersion(@Nullable String billOfMaterialVersion)
Original property name from the Odata EDM: BillOfMaterialVersion
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder validityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder billOfMaterialItemNodeNumber(@Nullable String billOfMaterialItemNodeNumber)
Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder materialName(@Nullable String materialName)
Original property name from the Odata EDM: MaterialName
You can enter one material description in each of any number of languages.In principle, you enter the material description on the data screen of the first user department for which you enter data, and in your logon language. You can overwrite the material description on the Basic Data screen.
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder plantName(@Nullable String plantName)
Original property name from the Odata EDM: PlantName
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder billOfMaterialVariantUsageDesc(@Nullable String billOfMaterialVariantUsageDesc)
Original property name from the Odata EDM: BillOfMaterialVariantUsageDesc
in which the BOM is used (eg. engineering or production).this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder 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 BOMWhereUsed.BOMWhereUsedBuilder bOMVersionStatus(@Nullable String bOMVersionStatus)
Original property name from the Odata EDM: BOMVersionStatus
this
.@Nonnull public BOMWhereUsed.BOMWhereUsedBuilder bOMVersionStatusDescription(@Nullable String bOMVersionStatusDescription)
Original property name from the Odata EDM: BOMVersionStatusDescription
SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
this
.@Nonnull public BOMWhereUsed build()
Copyright © 2020 SAP SE. All rights reserved.