public class BOMWhereUsed extends VdmEntity<BOMWhereUsed>
Original entity name from the Odata EDM: A_BOMWhereUsedType
Modifier and Type | Class and Description |
---|---|
static class |
BOMWhereUsed.BOMWhereUsedBuilder |
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.
|
changedOriginalFields
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,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
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> |
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
|
String |
getEngineeringChangeDocument()
Constraints: Not nullable, Maximum length: 12
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
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 |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
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() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final BOMWhereUsedSelectable ALL_FIELDS
public static final BOMWhereUsedField<UUID> BILL_OF_MATERIAL_ITEM_UUID
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_COMPONENT
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_NUMBER
public static final BOMWhereUsedField<String> HEADER_CHANGE_DOCUMENT
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_CATEGORY
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VARIANT
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VERSION
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_CATEGORY
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_UNIT
public static final BOMWhereUsedField<BigDecimal> BILL_OF_MATERIAL_ITEM_QUANTITY
public static final BOMWhereUsedField<String> ENGINEERING_CHANGE_DOCUMENT
public static final BOMWhereUsedField<LocalDateTime> VALIDITY_START_DATE
public static final BOMWhereUsedField<LocalDateTime> VALIDITY_END_DATE
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_ITEM_NODE_NUMBER
public static final BOMWhereUsedField<String> BOM_ITEM_DESCRIPTION
public static final BOMWhereUsedField<String> MATERIAL
public static final BOMWhereUsedField<String> MATERIAL_NAME
public static final BOMWhereUsedField<String> PLANT_NAME
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VARIANT_USAGE_DESC
public static final BOMWhereUsedField<String> PLANT
public static final BOMWhereUsedField<String> BILL_OF_MATERIAL_VARIANT_USAGE
public static final BOMWhereUsedField<String> BOM_VERSION_STATUS
public static final BOMWhereUsedField<String> BOM_VERSION_STATUS_DESCRIPTION
public 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, @Nullable ErpConfigContext erpConfigContext)
@Nonnull public Class<BOMWhereUsed> getType()
getType
in class VdmObject<BOMWhereUsed>
public void setBillOfMaterialItemUUID(@Nullable UUID billOfMaterialItemUUID)
Original property name from the Odata EDM: BillOfMaterialItemUUID
billOfMaterialItemUUID
- Global identification of an item's change statuspublic void setBillOfMaterialComponent(@Nullable String billOfMaterialComponent)
Original property name from the Odata EDM: BillOfMaterialComponent
A master record is usually maintained in the system for a component.
billOfMaterialComponent
- Material number of the components that you enter, change or display as part of the BOM.public void setBillOfMaterialItemNumber(@Nullable String billOfMaterialItemNumber)
Original property name from the Odata EDM: BillOfMaterialItemNumber
billOfMaterialItemNumber
- This number refers to the sequence of BOM components.public void setHeaderChangeDocument(@Nullable String headerChangeDocument)
Original property name from the Odata EDM: HeaderChangeDocument
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company
headerChangeDocument
- Number used to uniquely identify a change master record.public void setBillOfMaterialCategory(@Nullable String billOfMaterialCategory)
Original property name from the Odata EDM: BillOfMaterialCategory
Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
billOfMaterialCategory
- This key defines a BOM according to the object (such as material or equipment) to which it is linked.public void setBillOfMaterial(@Nullable String billOfMaterial)
Original property name from the Odata EDM: BillOfMaterial
The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
billOfMaterial
- Number used in combination with the BOM category to uniquely identify a BOM or a BOM group.public void setBillOfMaterialVariant(@Nullable String billOfMaterialVariant)
Original property name from the Odata EDM: BillOfMaterialVariant
One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
billOfMaterialVariant
- Identifies one BOM in a BOM group.public void setBillOfMaterialVersion(@Nullable String billOfMaterialVersion)
Original property name from the Odata EDM: BillOfMaterialVersion
billOfMaterialVersion
- BOM Versionpublic void setBillOfMaterialItemCategory(@Nullable String billOfMaterialItemCategory)
Original property name from the Odata EDM: BillOfMaterialItemCategory
This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
billOfMaterialItemCategory
- Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.public void setBillOfMaterialItemUnit(@Nullable String billOfMaterialItemUnit)
Original property name from the Odata EDM: BillOfMaterialItemUnit
The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
billOfMaterialItemUnit
- The unit for the component quantity.public void setBillOfMaterialItemQuantity(@Nullable BigDecimal billOfMaterialItemQuantity)
Original property name from the Odata EDM: BillOfMaterialItemQuantity
You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
billOfMaterialItemQuantity
- Quantity of the component, which is entered in relation to the base quantity of the product.public void setEngineeringChangeDocument(@Nullable String engineeringChangeDocument)
Original property name from the Odata EDM: EngineeringChangeDocument
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company
engineeringChangeDocument
- Number used to uniquely identify a change master record.public void setValidityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
validityStartDate
- Specifies the start date for the validity period of an object (such as material, BOM, or routing).public void setValidityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
validityEndDate
- End of validity period of an object (such as material, BOM, or routing) in the SAP System.public void setBillOfMaterialItemNodeNumber(@Nullable String billOfMaterialItemNodeNumber)
Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
billOfMaterialItemNodeNumber
- public void setBOMItemDescription(@Nullable String bOMItemDescription)
Original property name from the Odata EDM: BOMItemDescription
If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
bOMItemDescription
- Text of up to 40 characters, which forms the first of two lines of text describing the item.public void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setMaterialName(@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.
materialName
- Text containing up to 40 characters that describes the material in more detail.public void setPlantName(@Nullable String plantName)
Original property name from the Odata EDM: PlantName
plantName
- Plant Namepublic void setBillOfMaterialVariantUsageDesc(@Nullable String billOfMaterialVariantUsageDesc)
Original property name from the Odata EDM: BillOfMaterialVariantUsageDesc
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).public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setBillOfMaterialVariantUsage(@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.
billOfMaterialVariantUsage
- This key defines the area (such as engineering/design or production) where a BOM can be used.public void setBOMVersionStatus(@Nullable String bOMVersionStatus)
Original property name from the Odata EDM: BOMVersionStatus
bOMVersionStatus
- BOM Version Statuspublic void setBOMVersionStatusDescription(@Nullable String bOMVersionStatusDescription)
Original property name from the Odata EDM: BOMVersionStatusDescription
SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
bOMVersionStatusDescription
- This text appears when fixed values are displayed in the F4 help. It explains the possible input values.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<BOMWhereUsed>
protected Map<String,Object> getKey()
getKey
in class VdmObject<BOMWhereUsed>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<BOMWhereUsed>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<BOMWhereUsed>
@Nonnull public static <T> BOMWhereUsedField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> BOMWhereUsedField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
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.
setServicePathForFetch
in class VdmEntity<BOMWhereUsed>
public static BOMWhereUsed.BOMWhereUsedBuilder builder()
@Nullable public UUID getBillOfMaterialItemUUID()
Original property name from the Odata EDM: BillOfMaterialItemUUID
@Nullable public String getBillOfMaterialComponent()
Original property name from the Odata EDM: BillOfMaterialComponent
A master record is usually maintained in the system for a component.
@Nullable public String getBillOfMaterialItemNumber()
Original property name from the Odata EDM: BillOfMaterialItemNumber
@Nullable public String getHeaderChangeDocument()
Original property name from the Odata EDM: HeaderChangeDocument
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company
@Nullable public String getBillOfMaterialCategory()
Original property name from the Odata EDM: BillOfMaterialCategory
Material BOM - linked to a materialEquipment BOM - linked to an equipmentOrder BOM - linked to material, sales order and sales order item.
@Nullable public String getBillOfMaterial()
Original property name from the Odata EDM: BillOfMaterial
The system assigns this number internally. These numbers are irrelevant to the user. You access the BOM by entering the object (for example, material or equipment) to which the BOM belongs.The system stores the following information under this number:all alternatives in a multiple BOMall variants in a variant BOMBOMs that are allocated to more than one plant
@Nullable public String getBillOfMaterialVariant()
Original property name from the Odata EDM: BillOfMaterialVariant
One product or assembly can be described by a number of (alternative) BOMs that represent, for example, different manufacturing processes for different lot sizes. These alternative BOMs are grouped together as one multiple BOM.Alternatives are maintained separately for each BOM usage.
@Nullable public String getBillOfMaterialVersion()
Original property name from the Odata EDM: BillOfMaterialVersion
@Nullable public String getBillOfMaterialItemCategory()
Original property name from the Odata EDM: BillOfMaterialItemCategory
This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.Stock itemThis item category is used to manage material data that allows an item to be kept in stock.Document itemThis item category is used to manage document data that allows you to process original application data (for example, graphics created with a graphics program).Class item (for configurable BOMs)In configurable material BOMs, you can enter a class as a placeholder for selectable items. The class can contain either materials or documents.When you assign characteristic values while configuring the BOM, the system replaces the node with an object that has the same values as those assigned to the characteristic of the configuration. This makes BOMs with a larger number of variants easier to maintain, as you do not have to enter all items manually and assign a selection condition to them.Class items can be relevant to MRP.PM structure elementThis item is used to structure an equipment (PM assembly) for design purposes only.If you want to maintain a material for use as a PM structure element, use material type IBAU.
@Nullable public String getBillOfMaterialItemUnit()
Original property name from the Odata EDM: BillOfMaterialItemUnit
The system determines the unit as follows:Material items with a material master record - base unit of measure from the material master record.Class items - unit defined in the additional data of the class.Additional units for material items with a material master record:For material items, you can maintain alternative units of measure to the base unit of measure in the material master.In bills of material, not all alternative units of measure are taken into account - only the unit of issue.Possible values are:base unit of measureunit of issueunits of measure that have the same dimension as either the base unit of measure or the unit of issueIf you enter no unit, the system proposes a unit from the material master if the item has a material master:If the unit of issue was entered on the storage detail screen, the system copies this unit. Otherwise, it copies the base unit of measure.
@Nullable public BigDecimal getBillOfMaterialItemQuantity()
Original property name from the Odata EDM: BillOfMaterialItemQuantity
You usually enter the quantity without a +/- sign (for example, 66).For the following materials, you enter the quantity with a - sign(for example, 22-):Materials that are marked as co-productsIntra materials (in process industries)In display functions, the system calculates the current component quantity from the required quantity and the base quantity.Required quantityCurrent component quantity = ------------------ * Saved component quantityBase quantity
@Nullable public String getEngineeringChangeDocument()
Original property name from the Odata EDM: EngineeringChangeDocument
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company
@Nullable public LocalDateTime getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public LocalDateTime getValidityEndDate()
Original property name from the Odata EDM: ValidityEndDate
@Nullable public String getBillOfMaterialItemNodeNumber()
Original property name from the Odata EDM: BillOfMaterialItemNodeNumber
@Nullable public String getBOMItemDescription()
Original property name from the Odata EDM: BOMItemDescription
If this text length (two lines of 40 characters each) is not sufficient, you can also enter a long text by choosing menu option Extras -> Long text -> Item.When you create an item long text, the first 80 characters of the BOM item text are copied to the long text.If you change the BOM item text, the first 80 characters of long text are automatically changed, too. If you change the first two lines of the BOM item long text, the short text is automatically changed.Note:For text items, this text is copied to the component description field on the item overview.
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getMaterialName()
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.
@Nullable public String getPlantName()
Original property name from the Odata EDM: PlantName
@Nullable public String getBillOfMaterialVariantUsageDesc()
Original property name from the Odata EDM: BillOfMaterialVariantUsageDesc
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public String getBillOfMaterialVariantUsage()
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.
@Nullable public String getBOMVersionStatus()
Original property name from the Odata EDM: BOMVersionStatus
@Nullable public String getBOMVersionStatusDescription()
Original property name from the Odata EDM: BOMVersionStatusDescription
SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<BOMWhereUsed>
erpConfigContext
- public String toString()
toString
in class VdmObject<BOMWhereUsed>
public boolean equals(Object o)
equals
in class VdmObject<BOMWhereUsed>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<BOMWhereUsed>
public int hashCode()
hashCode
in class VdmObject<BOMWhereUsed>
Copyright © 2018 SAP SE. All rights reserved.