BOMWhereUsed (SAP Cloud SDK - Parent POM 3.30.0 API)

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

```
public class BOMWhereUsed
extends VdmEntity<BOMWhereUsed>
```
Where Used List

Original entity name from the Odata EDM: A_BOMWhereUsedType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class BOMWhereUsed.BOMWhereUsedBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`BOMWhereUsed.BOMWhereUsedBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static BOMWhereUsedSelectable`	`ALL_FIELDS` Selector for all available fields of BOMWhereUsed.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL` Use with available fluent helpers to apply the BillOfMaterial field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_CATEGORY` Use with available fluent helpers to apply the BillOfMaterialCategory field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_COMPONENT` Use with available fluent helpers to apply the BillOfMaterialComponent field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_ITEM_CATEGORY` Use with available fluent helpers to apply the BillOfMaterialItemCategory field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_ITEM_NODE_NUMBER` Use with available fluent helpers to apply the BillOfMaterialItemNodeNumber field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_ITEM_NUMBER` Use with available fluent helpers to apply the BillOfMaterialItemNumber field to query operations.
`static BOMWhereUsedField<BigDecimal>`	`BILL_OF_MATERIAL_ITEM_QUANTITY` Use with available fluent helpers to apply the BillOfMaterialItemQuantity field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_ITEM_UNIT` Use with available fluent helpers to apply the BillOfMaterialItemUnit field to query operations.
`static BOMWhereUsedField<UUID>`	`BILL_OF_MATERIAL_ITEM_UUID` Use with available fluent helpers to apply the BillOfMaterialItemUUID field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_VARIANT` Use with available fluent helpers to apply the BillOfMaterialVariant field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_VARIANT_USAGE` Use with available fluent helpers to apply the BillOfMaterialVariantUsage field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_VARIANT_USAGE_DESC` Use with available fluent helpers to apply the BillOfMaterialVariantUsageDesc field to query operations.
`static BOMWhereUsedField<String>`	`BILL_OF_MATERIAL_VERSION` Use with available fluent helpers to apply the BillOfMaterialVersion field to query operations.
`static BOMWhereUsedField<String>`	`BOM_ITEM_DESCRIPTION` Use with available fluent helpers to apply the BOMItemDescription field to query operations.
`static BOMWhereUsedField<String>`	`BOM_VERSION_STATUS` Use with available fluent helpers to apply the BOMVersionStatus field to query operations.
`static BOMWhereUsedField<String>`	`BOM_VERSION_STATUS_DESCRIPTION` Use with available fluent helpers to apply the BOMVersionStatusDescription field to query operations.
`static BOMWhereUsedField<String>`	`ENGINEERING_CHANGE_DOCUMENT` Use with available fluent helpers to apply the EngineeringChangeDocument field to query operations.
`static BOMWhereUsedField<String>`	`HEADER_CHANGE_DOCUMENT` Use with available fluent helpers to apply the HeaderChangeDocument field to query operations.
`static BOMWhereUsedField<String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static BOMWhereUsedField<String>`	`MATERIAL_NAME` Use with available fluent helpers to apply the MaterialName field to query operations.
`static BOMWhereUsedField<String>`	`PLANT` Use with available fluent helpers to apply the Plant field to query operations.
`static BOMWhereUsedField<String>`	`PLANT_NAME` Use with available fluent helpers to apply the PlantName field to query operations.
`static BOMWhereUsedField<LocalDateTime>`	`VALIDITY_END_DATE` Use with available fluent helpers to apply the ValidityEndDate field to query operations.
`static BOMWhereUsedField<LocalDateTime>`	`VALIDITY_START_DATE` Use with available fluent helpers to apply the ValidityStartDate field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`BOMWhereUsed()`
BOMWhereUsed(UUID billOfMaterialItemUUID, String billOfMaterialComponent, String billOfMaterialItemNumber, String headerChangeDocument, String billOfMaterialCategory, String billOfMaterial, String billOfMaterialVariant, String billOfMaterialVersion, String billOfMaterialItemCategory, String billOfMaterialItemUnit, BigDecimal billOfMaterialItemQuantity, String engineeringChangeDocument, LocalDateTime validityStartDate, LocalDateTime validityEndDate, String billOfMaterialItemNodeNumber, String bOMItemDescription, String material, String materialName, String plantName, String billOfMaterialVariantUsageDesc, String plant, String billOfMaterialVariantUsage, String bOMVersionStatus, String bOMVersionStatusDescription)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static BOMWhereUsed.BOMWhereUsedBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`static <T> BOMWhereUsedField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> BOMWhereUsedField<T>`	`field(String fieldName, TypeConverter<T,DomainT> typeConverter)` Use with available fluent helpers to apply an extension field to query operations.
`protected void`	`fromMap(Map<String,Object> inputValues)`
`String`	`getBillOfMaterial()` Constraints: Not nullable, Maximum length: 8
`String`	`getBillOfMaterialCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getBillOfMaterialComponent()` Constraints: Not nullable, Maximum length: 40
`String`	`getBillOfMaterialItemCategory()` Constraints: Not nullable, Maximum length: 1
`String`	`getBillOfMaterialItemNodeNumber()` Constraints: Not nullable, Maximum length: 8
`String`	`getBillOfMaterialItemNumber()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getBillOfMaterialItemQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getBillOfMaterialItemUnit()` Constraints: Not nullable, Maximum length: 3
`UUID`	`getBillOfMaterialItemUUID()` (Key Field) Constraints: Not nullable
`String`	`getBillOfMaterialVariant()` Constraints: Not nullable, Maximum length: 2
`String`	`getBillOfMaterialVariantUsage()` Constraints: Not nullable, Maximum length: 1
`String`	`getBillOfMaterialVariantUsageDesc()` Constraints: Not nullable, Maximum length: 30
`String`	`getBillOfMaterialVersion()` Constraints: Not nullable, Maximum length: 4
`String`	`getBOMItemDescription()` Constraints: Not nullable, Maximum length: 40
`String`	`getBOMVersionStatus()` Constraints: Not nullable, Maximum length: 2
`String`	`getBOMVersionStatusDescription()` Constraints: Not nullable, Maximum length: 60
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`String`	`getEngineeringChangeDocument()` Constraints: Not nullable, Maximum length: 12
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getHeaderChangeDocument()` Constraints: Not nullable, Maximum length: 12
`protected Map<String,Object>`	`getKey()`
`String`	`getMaterial()` Constraints: Not nullable, Maximum length: 40
`String`	`getMaterialName()` Constraints: Not nullable, Maximum length: 40
`String`	`getPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getPlantName()` Constraints: Not nullable, Maximum length: 30
`Class<BOMWhereUsed>`	`getType()`
`LocalDateTime`	`getValidityEndDate()` Constraints: Not nullable, Precision: 0
`LocalDateTime`	`getValidityStartDate()` Constraints: Not nullable, Precision: 0
`int`	`hashCode()`
`void`	`setBillOfMaterial(String billOfMaterial)` Constraints: Not nullable, Maximum length: 8
`void`	`setBillOfMaterialCategory(String billOfMaterialCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setBillOfMaterialComponent(String billOfMaterialComponent)` Constraints: Not nullable, Maximum length: 40
`void`	`setBillOfMaterialItemCategory(String billOfMaterialItemCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setBillOfMaterialItemNodeNumber(String billOfMaterialItemNodeNumber)` Constraints: Not nullable, Maximum length: 8
`void`	`setBillOfMaterialItemNumber(String billOfMaterialItemNumber)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillOfMaterialItemQuantity(BigDecimal billOfMaterialItemQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBillOfMaterialItemUnit(String billOfMaterialItemUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setBillOfMaterialItemUUID(UUID billOfMaterialItemUUID)` (Key Field) Constraints: Not nullable
`void`	`setBillOfMaterialVariant(String billOfMaterialVariant)` Constraints: Not nullable, Maximum length: 2
`void`	`setBillOfMaterialVariantUsage(String billOfMaterialVariantUsage)` Constraints: Not nullable, Maximum length: 1
`void`	`setBillOfMaterialVariantUsageDesc(String billOfMaterialVariantUsageDesc)` Constraints: Not nullable, Maximum length: 30
`void`	`setBillOfMaterialVersion(String billOfMaterialVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setBOMItemDescription(String bOMItemDescription)` Constraints: Not nullable, Maximum length: 40
`void`	`setBOMVersionStatus(String bOMVersionStatus)` Constraints: Not nullable, Maximum length: 2
`void`	`setBOMVersionStatusDescription(String bOMVersionStatusDescription)` Constraints: Not nullable, Maximum length: 60
`void`	`setEngineeringChangeDocument(String engineeringChangeDocument)` Constraints: Not nullable, Maximum length: 12
`void`	`setHeaderChangeDocument(String headerChangeDocument)` Constraints: Not nullable, Maximum length: 12
`void`	`setMaterial(String material)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialName(String materialName)` Constraints: Not nullable, Maximum length: 40
`void`	`setPlant(String plant)` Constraints: Not nullable, Maximum length: 4
`void`	`setPlantName(String plantName)` Constraints: Not nullable, Maximum length: 30
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setValidityEndDate(LocalDateTime validityEndDate)` Constraints: Not nullable, Precision: 0
`void`	`setValidityStartDate(LocalDateTime validityStartDate)` Constraints: Not nullable, Precision: 0
`protected Map<String,Object>`	`toMapOfFields()`
`String`	`toString()`

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

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

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

- Field Detail
  - ALL_FIELDS
```
public static final BOMWhereUsedSelectable ALL_FIELDS
```
    Selector for all available fields of BOMWhereUsed.
  - BILL_OF_MATERIAL_ITEM_UUID
```
public static final BOMWhereUsedField<UUID> BILL_OF_MATERIAL_ITEM_UUID
```
    Use with available fluent helpers to apply the BillOfMaterialItemUUID field to query operations.
  - BILL_OF_MATERIAL_COMPONENT
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_COMPONENT
```
    Use with available fluent helpers to apply the BillOfMaterialComponent field to query operations.
  - BILL_OF_MATERIAL_ITEM_NUMBER
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_NUMBER
```
    Use with available fluent helpers to apply the BillOfMaterialItemNumber field to query operations.
  - HEADER_CHANGE_DOCUMENT
```
public static final BOMWhereUsedField<String> HEADER_CHANGE_DOCUMENT
```
    Use with available fluent helpers to apply the HeaderChangeDocument field to query operations.
  - BILL_OF_MATERIAL_CATEGORY
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_CATEGORY
```
    Use with available fluent helpers to apply the BillOfMaterialCategory field to query operations.
  - BILL_OF_MATERIAL
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL
```
    Use with available fluent helpers to apply the BillOfMaterial field to query operations.
  - BILL_OF_MATERIAL_VARIANT
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VARIANT
```
    Use with available fluent helpers to apply the BillOfMaterialVariant field to query operations.
  - BILL_OF_MATERIAL_VERSION
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VERSION
```
    Use with available fluent helpers to apply the BillOfMaterialVersion field to query operations.
  - BILL_OF_MATERIAL_ITEM_CATEGORY
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the BillOfMaterialItemCategory field to query operations.
  - BILL_OF_MATERIAL_ITEM_UNIT
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_UNIT
```
    Use with available fluent helpers to apply the BillOfMaterialItemUnit field to query operations.
  - BILL_OF_MATERIAL_ITEM_QUANTITY
```
public static final BOMWhereUsedField<BigDecimal> BILL_OF_MATERIAL_ITEM_QUANTITY
```
    Use with available fluent helpers to apply the BillOfMaterialItemQuantity field to query operations.
  - ENGINEERING_CHANGE_DOCUMENT
```
public static final BOMWhereUsedField<String> ENGINEERING_CHANGE_DOCUMENT
```
    Use with available fluent helpers to apply the EngineeringChangeDocument field to query operations.
  - VALIDITY_START_DATE
```
public static final BOMWhereUsedField<LocalDateTime> VALIDITY_START_DATE
```
    Use with available fluent helpers to apply the ValidityStartDate field to query operations.
  - VALIDITY_END_DATE
```
public static final BOMWhereUsedField<LocalDateTime> VALIDITY_END_DATE
```
    Use with available fluent helpers to apply the ValidityEndDate field to query operations.
  - BILL_OF_MATERIAL_ITEM_NODE_NUMBER
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_NODE_NUMBER
```
    Use with available fluent helpers to apply the BillOfMaterialItemNodeNumber field to query operations.
  - BOM_ITEM_DESCRIPTION
```
public static final BOMWhereUsedField<String> BOM_ITEM_DESCRIPTION
```
    Use with available fluent helpers to apply the BOMItemDescription field to query operations.
  - MATERIAL
```
public static final BOMWhereUsedField<String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - MATERIAL_NAME
```
public static final BOMWhereUsedField<String> MATERIAL_NAME
```
    Use with available fluent helpers to apply the MaterialName field to query operations.
  - PLANT_NAME
```
public static final BOMWhereUsedField<String> PLANT_NAME
```
    Use with available fluent helpers to apply the PlantName field to query operations.
  - BILL_OF_MATERIAL_VARIANT_USAGE_DESC
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VARIANT_USAGE_DESC
```
    Use with available fluent helpers to apply the BillOfMaterialVariantUsageDesc field to query operations.
  - PLANT
```
public static final BOMWhereUsedField<String> PLANT
```
    Use with available fluent helpers to apply the Plant field to query operations.
  - BILL_OF_MATERIAL_VARIANT_USAGE
```
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VARIANT_USAGE
```
    Use with available fluent helpers to apply the BillOfMaterialVariantUsage field to query operations.
  - BOM_VERSION_STATUS
```
public static final BOMWhereUsedField<String> BOM_VERSION_STATUS
```
    Use with available fluent helpers to apply the BOMVersionStatus field to query operations.
  - BOM_VERSION_STATUS_DESCRIPTION
```
public static final BOMWhereUsedField<String> BOM_VERSION_STATUS_DESCRIPTION
```
    Use with available fluent helpers to apply the BOMVersionStatusDescription field to query operations.
- Constructor Detail
  - BOMWhereUsed
```
public BOMWhereUsed()
```
  - BOMWhereUsed
```
public BOMWhereUsed(@Nullable
                    UUID billOfMaterialItemUUID,
                    @Nullable
                    String billOfMaterialComponent,
                    @Nullable
                    String billOfMaterialItemNumber,
                    @Nullable
                    String headerChangeDocument,
                    @Nullable
                    String billOfMaterialCategory,
                    @Nullable
                    String billOfMaterial,
                    @Nullable
                    String billOfMaterialVariant,
                    @Nullable
                    String billOfMaterialVersion,
                    @Nullable
                    String billOfMaterialItemCategory,
                    @Nullable
                    String billOfMaterialItemUnit,
                    @Nullable
                    BigDecimal billOfMaterialItemQuantity,
                    @Nullable
                    String engineeringChangeDocument,
                    @Nullable
                    LocalDateTime validityStartDate,
                    @Nullable
                    LocalDateTime validityEndDate,
                    @Nullable
                    String billOfMaterialItemNodeNumber,
                    @Nullable
                    String bOMItemDescription,
                    @Nullable
                    String material,
                    @Nullable
                    String materialName,
                    @Nullable
                    String plantName,
                    @Nullable
                    String billOfMaterialVariantUsageDesc,
                    @Nullable
                    String plant,
                    @Nullable
                    String billOfMaterialVariantUsage,
                    @Nullable
                    String bOMVersionStatus,
                    @Nullable
                    String bOMVersionStatusDescription)
```
- Method Detail
  - getType
```
@Nonnull
public Class<BOMWhereUsed> getType()
```
    Specified by:
    
    getType in class VdmObject<BOMWhereUsed>
    
    Returns:
    
    The class of this object.
  - setBillOfMaterialItemUUID
```
public void setBillOfMaterialItemUUID(@Nullable
                                      UUID billOfMaterialItemUUID)
```
    (Key Field) Constraints: Not nullable
    Original property name from the Odata EDM: BillOfMaterialItemUUID
    
    Parameters:
    
    billOfMaterialItemUUID - Global identification of an item's change status
  - setBillOfMaterialComponent
```
public void setBillOfMaterialComponent(@Nullable
                                       String billOfMaterialComponent)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillOfMaterialComponent
    
    A master record is usually maintained in the system for a component.
    
    Parameters:
    
    billOfMaterialComponent - Material number of the components that you enter, change or display as part of the BOM.
  - setBillOfMaterialItemNumber
```
public void setBillOfMaterialItemNumber(@Nullable
                                        String billOfMaterialItemNumber)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfMaterialItemNumber
    
    Parameters:
    
    billOfMaterialItemNumber - This number refers to the sequence of BOM components.
  - setHeaderChangeDocument
```
public void setHeaderChangeDocument(@Nullable
                                    String headerChangeDocument)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: HeaderChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    headerChangeDocument - Number used to uniquely identify a change master record.
  - setBillOfMaterialCategory
```
public void setBillOfMaterialCategory(@Nullable
                                      String billOfMaterialCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialCategory
    
    Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
    
    Parameters:
    
    billOfMaterialCategory - This key defines a BOM according to the object (such as material or equipment) to which it is linked.
  - setBillOfMaterial
```
public void setBillOfMaterial(@Nullable
                              String billOfMaterial)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterial
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Parameters:
    
    billOfMaterial - Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.
  - setBillOfMaterialVariant
```
public void setBillOfMaterialVariant(@Nullable
                                     String billOfMaterialVariant)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BillOfMaterialVariant
    
    One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
    
    Parameters:
    
    billOfMaterialVariant - Identifies one BOM in a BOM group.
  - setBillOfMaterialVersion
```
public void setBillOfMaterialVersion(@Nullable
                                     String billOfMaterialVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfMaterialVersion
    
    Parameters:
    
    billOfMaterialVersion - BOM Version
  - setBillOfMaterialItemCategory
```
public void setBillOfMaterialItemCategory(@Nullable
                                          String billOfMaterialItemCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialItemCategory
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Parameters:
    
    billOfMaterialItemCategory - Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
  - setBillOfMaterialItemUnit
```
public void setBillOfMaterialItemUnit(@Nullable
                                      String billOfMaterialItemUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: BillOfMaterialItemUnit
    
    The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
    
    Parameters:
    
    billOfMaterialItemUnit - The unit for the component quantity.
  - setBillOfMaterialItemQuantity
```
public void setBillOfMaterialItemQuantity(@Nullable
                                          BigDecimal billOfMaterialItemQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: BillOfMaterialItemQuantity
    
    You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Parameters:
    
    billOfMaterialItemQuantity - Quantity of the component, which is entered in relation to the base quantity of the product.
  - setEngineeringChangeDocument
```
public void setEngineeringChangeDocument(@Nullable
                                         String engineeringChangeDocument)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: EngineeringChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Parameters:
    
    engineeringChangeDocument - Number used to uniquely identify a change master record.
  - setValidityStartDate
```
public void setValidityStartDate(@Nullable
                                 LocalDateTime validityStartDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityStartDate
    
    Parameters:
    
    validityStartDate - Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - setValidityEndDate
```
public void setValidityEndDate(@Nullable
                               LocalDateTime validityEndDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityEndDate
    
    Parameters:
    
    validityEndDate - End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - setBillOfMaterialItemNodeNumber
```
public void setBillOfMaterialItemNodeNumber(@Nullable
                                            String billOfMaterialItemNodeNumber)
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
    
    Parameters:
    
    billOfMaterialItemNodeNumber - BOM item node number
  - setBOMItemDescription
```
public void setBOMItemDescription(@Nullable
                                  String bOMItemDescription)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BOMItemDescription
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Parameters:
    
    bOMItemDescription - Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - setMaterial
```
public void setMaterial(@Nullable
                        String material)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Parameters:
    
    material - Alphanumeric key uniquely identifying the material.
  - setMaterialName
```
public void setMaterialName(@Nullable
                            String materialName)
```
    Constraints: Not nullable, Maximum length: 40
    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.
    
    Parameters:
    
    materialName - Text containing up to 40 characters that describes the material in more detail.
  - setPlantName
```
public void setPlantName(@Nullable
                         String plantName)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: PlantName
    
    Parameters:
    
    plantName - Plant Name
  - setBillOfMaterialVariantUsageDesc
```
public void setBillOfMaterialVariantUsageDesc(@Nullable
                                              String billOfMaterialVariantUsageDesc)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: BillOfMaterialVariantUsageDesc
    
    Parameters:
    
    billOfMaterialVariantUsageDesc - This text describes the key for the BOM usage, which represents the specific company organizational area in which the BOM is used (eg. engineering or production).
  - setPlant
```
public void setPlant(@Nullable
                     String plant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    Parameters:
    
    plant - Key uniquely identifying a plant.
  - setBillOfMaterialVariantUsage
```
public void setBillOfMaterialVariantUsage(@Nullable
                                          String billOfMaterialVariantUsage)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialVariantUsage
    
    By setting various indicators, you can define the maximum configuration of the item status and define whether an item must be or cannot be processed in a particular area (such as production).A material is used in the areas production and costing in a company. For each area, you maintain a separate BOM with different items:Production BOM:This BOM contains items that are relevant to production. These items are copied to the planned order. Dependent requirements are generated for them, and they are copied to the production order.Costing BOM:This BOM contains items that are relevant to determining the material costs of a product.When you calculate production costs using a quantity structure, the system automatically determines the BOM and all the BOM items that are relevant to costing, in order to calculate manufacturing costs.
    
    Parameters:
    
    billOfMaterialVariantUsage - This key defines the area (such as engineering/design or production) where a BOM can be used.
  - setBOMVersionStatus
```
public void setBOMVersionStatus(@Nullable
                                String bOMVersionStatus)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BOMVersionStatus
    
    Parameters:
    
    bOMVersionStatus - BOM Version Status
  - setBOMVersionStatusDescription
```
public void setBOMVersionStatusDescription(@Nullable
                                           String bOMVersionStatusDescription)
```
    Constraints: Not nullable, Maximum length: 60
    Original property name from the Odata EDM: BOMVersionStatusDescription
    
    SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
    
    Parameters:
    
    bOMVersionStatusDescription - This text appears when fixed values are displayed in the F4 help. It explains the possible input values.
  - getEntityCollection
```
protected String getEntityCollection()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Specified by:
    
    getEntityCollection in class VdmEntity<BOMWhereUsed>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<BOMWhereUsed>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<BOMWhereUsed>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<BOMWhereUsed>
  - field
```
@Nonnull
public static <T> BOMWhereUsedField<T> field(@Nonnull
                                                      String fieldName,
                                                      @Nonnull
                                                      Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    Parameters:
    
    fieldName - The name of the extension field as returned by the OData service.
    
    fieldType - The Java type to use for the extension field when performing value comparisons.
    
    Returns:
    
    A representation of an extension field from this entity.
  - field
```
@Nonnull
public static <T,DomainT> BOMWhereUsedField<T> field(@Nonnull
                                                              String fieldName,
                                                              @Nonnull
                                                              TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getDestinationForFetch
```
@Nullable
public HttpDestinationProperties getDestinationForFetch()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same destination with multiple queries (e.g. fetching associated entities). New destination to apply to this entity
    
    Overrides:
    
    getDestinationForFetch in class VdmEntity<BOMWhereUsed>
    
    Returns:
    
    The stored destination for executing queries, or null if no such context has been set.
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<BOMWhereUsed>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nonnull
                            HttpDestinationProperties destination)
```
    Description copied from class: VdmEntity
    
    Sets the service path and destination for the fetch commands of this entity. Also applies to any associated entities (navigation properties) that were previously fetched.
    Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    attachToService in class VdmEntity<BOMWhereUsed>
    
    Parameters:
    
    servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the service path has never been set, then the service path will be set to the default defined in the corresponding service interface.
    
    destination - New destination to apply to this entity and any associated entities that were previously fetched.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Overrides:
    
    getDefaultServicePath in class VdmEntity<BOMWhereUsed>
    
    Returns:
    
    Default context path to the OData service. In other words, everything in between the protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)
  - builder
```
@Nonnull
public static BOMWhereUsed.BOMWhereUsedBuilder builder()
```
  - getBillOfMaterialItemUUID
```
@Nullable
public UUID getBillOfMaterialItemUUID()
```
    (Key Field) Constraints: Not nullable
    Original property name from the Odata EDM: BillOfMaterialItemUUID
    
    Returns:
    
    Global identification of an item's change status
  - getBillOfMaterialComponent
```
@Nullable
public String getBillOfMaterialComponent()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillOfMaterialComponent
    
    A master record is usually maintained in the system for a component.
    
    Returns:
    
    Material number of the components that you enter, change or display as part of the BOM.
  - getBillOfMaterialItemNumber
```
@Nullable
public String getBillOfMaterialItemNumber()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfMaterialItemNumber
    
    Returns:
    
    This number refers to the sequence of BOM components.
  - getHeaderChangeDocument
```
@Nullable
public String getHeaderChangeDocument()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: HeaderChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getBillOfMaterialCategory
```
@Nullable
public String getBillOfMaterialCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialCategory
    
    Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
    
    Returns:
    
    This key defines a BOM according to the object (such as material or equipment) to which it is linked.
  - getBillOfMaterial
```
@Nullable
public String getBillOfMaterial()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterial
    
    The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
    
    Returns:
    
    Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.
  - getBillOfMaterialVariant
```
@Nullable
public String getBillOfMaterialVariant()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BillOfMaterialVariant
    
    One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
    
    Returns:
    
    Identifies one BOM in a BOM group.
  - getBillOfMaterialVersion
```
@Nullable
public String getBillOfMaterialVersion()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillOfMaterialVersion
    
    Returns:
    
    BOM Version
  - getBillOfMaterialItemCategory
```
@Nullable
public String getBillOfMaterialItemCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialItemCategory
    
    This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
    
    Returns:
    
    Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
  - getBillOfMaterialItemUnit
```
@Nullable
public String getBillOfMaterialItemUnit()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: BillOfMaterialItemUnit
    
    The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
    
    Returns:
    
    The unit for the component quantity.
  - getBillOfMaterialItemQuantity
```
@Nullable
public BigDecimal getBillOfMaterialItemQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: BillOfMaterialItemQuantity
    
    You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
    
    Returns:
    
    Quantity of the component, which is entered in relation to the base quantity of the product.
  - getEngineeringChangeDocument
```
@Nullable
public String getEngineeringChangeDocument()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: EngineeringChangeDocument
    
    If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company.
    
    Returns:
    
    Number used to uniquely identify a change master record.
  - getValidityStartDate
```
@Nullable
public LocalDateTime getValidityStartDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityStartDate
    
    Returns:
    
    Specifies the start date for the validity period of an object (such as material, BOM, or routing).
  - getValidityEndDate
```
@Nullable
public LocalDateTime getValidityEndDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ValidityEndDate
    
    Returns:
    
    End of validity period of an object (such as material, BOM, or routing) in the SAP System.
  - getBillOfMaterialItemNodeNumber
```
@Nullable
public String getBillOfMaterialItemNodeNumber()
```
    Constraints: Not nullable, Maximum length: 8
    Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
    
    Returns:
    
    BOM item node number
  - getBOMItemDescription
```
@Nullable
public String getBOMItemDescription()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BOMItemDescription
    
    If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
    
    Returns:
    
    Text of up to 40 characters, which forms the first of two lines of text describing the item.
  - getMaterial
```
@Nullable
public String getMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getMaterialName
```
@Nullable
public String getMaterialName()
```
    Constraints: Not nullable, Maximum length: 40
    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.
    
    Returns:
    
    Text containing up to 40 characters that describes the material in more detail.
  - getPlantName
```
@Nullable
public String getPlantName()
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: PlantName
    
    Returns:
    
    Plant Name
  - getBillOfMaterialVariantUsageDesc
```
@Nullable
public String getBillOfMaterialVariantUsageDesc()
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: BillOfMaterialVariantUsageDesc
    
    Returns:
    
    This text describes the key for the BOM usage, which represents the specific company organizational area in which the BOM is used (eg. engineering or production).
  - getPlant
```
@Nullable
public String getPlant()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
    
    Returns:
    
    Key uniquely identifying a plant.
  - getBillOfMaterialVariantUsage
```
@Nullable
public String getBillOfMaterialVariantUsage()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillOfMaterialVariantUsage
    
    By setting various indicators, you can define the maximum configuration of the item status and define whether an item must be or cannot be processed in a particular area (such as production).A material is used in the areas production and costing in a company. For each area, you maintain a separate BOM with different items:Production BOM:This BOM contains items that are relevant to production. These items are copied to the planned order. Dependent requirements are generated for them, and they are copied to the production order.Costing BOM:This BOM contains items that are relevant to determining the material costs of a product.When you calculate production costs using a quantity structure, the system automatically determines the BOM and all the BOM items that are relevant to costing, in order to calculate manufacturing costs.
    
    Returns:
    
    This key defines the area (such as engineering/design or production) where a BOM can be used.
  - getBOMVersionStatus
```
@Nullable
public String getBOMVersionStatus()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: BOMVersionStatus
    
    Returns:
    
    BOM Version Status
  - getBOMVersionStatusDescription
```
@Nullable
public String getBOMVersionStatusDescription()
```
    Constraints: Not nullable, Maximum length: 60
    Original property name from the Odata EDM: BOMVersionStatusDescription
    
    SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
    
    Returns:
    
    This text appears when fixed values are displayed in the F4 help. It explains the possible input values.
  - toString
```
@Nonnull
public String toString()
```
    Overrides:
    
    toString in class VdmObject<BOMWhereUsed>
  - equals
```
public boolean equals(@Nullable
                      Object o)
```
    Overrides:
    
    equals in class VdmObject<BOMWhereUsed>
  - canEqual
```
protected boolean canEqual(@Nullable
                           Object other)
```
    Overrides:
    
    canEqual in class VdmObject<BOMWhereUsed>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<BOMWhereUsed>

Class BOMWhereUsed

Nested Class Summary

Field Summary

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

Constructor Summary

Method Summary

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

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

BILL_OF_MATERIAL_ITEM_UUID

BILL_OF_MATERIAL_COMPONENT

BILL_OF_MATERIAL_ITEM_NUMBER

HEADER_CHANGE_DOCUMENT

BILL_OF_MATERIAL_CATEGORY

BILL_OF_MATERIAL

BILL_OF_MATERIAL_VARIANT

BILL_OF_MATERIAL_VERSION

BILL_OF_MATERIAL_ITEM_CATEGORY

BILL_OF_MATERIAL_ITEM_UNIT

BILL_OF_MATERIAL_ITEM_QUANTITY

ENGINEERING_CHANGE_DOCUMENT

VALIDITY_START_DATE

VALIDITY_END_DATE

BILL_OF_MATERIAL_ITEM_NODE_NUMBER

BOM_ITEM_DESCRIPTION

MATERIAL

MATERIAL_NAME

PLANT_NAME

BILL_OF_MATERIAL_VARIANT_USAGE_DESC

PLANT

BILL_OF_MATERIAL_VARIANT_USAGE

BOM_VERSION_STATUS

BOM_VERSION_STATUS_DESCRIPTION

Constructor Detail

BOMWhereUsed

BOMWhereUsed

Method Detail

getType

setBillOfMaterialItemUUID

setBillOfMaterialComponent

setBillOfMaterialItemNumber

setHeaderChangeDocument

setBillOfMaterialCategory

setBillOfMaterial

setBillOfMaterialVariant

setBillOfMaterialVersion

setBillOfMaterialItemCategory

setBillOfMaterialItemUnit

setBillOfMaterialItemQuantity

setEngineeringChangeDocument

setValidityStartDate

setValidityEndDate

setBillOfMaterialItemNodeNumber

setBOMItemDescription

setMaterial

setMaterialName

setPlantName

setBillOfMaterialVariantUsageDesc

setPlant

setBillOfMaterialVariantUsage

setBOMVersionStatus

setBOMVersionStatusDescription

getEntityCollection

getKey

toMapOfFields

fromMap

field

field

getDestinationForFetch

setServicePathForFetch

attachToService

getDefaultServicePath

builder

getBillOfMaterialItemUUID

getBillOfMaterialComponent

getBillOfMaterialItemNumber

getHeaderChangeDocument

getBillOfMaterialCategory