public class ProductPlantCosting extends VdmEntity<ProductPlantCosting>
Original entity name from the Odata EDM: A_ProductPlantCostingType
Modifier and Type | Class and Description |
---|---|
static class |
ProductPlantCosting.ProductPlantCostingBuilder |
Modifier and Type | Field and Description |
---|---|
static ProductPlantCostingSelectable |
ALL_FIELDS
Selector for all available fields of ProductPlantCosting.
|
static ProductPlantCostingField<String> |
BASE_UNIT
Use with available fluent helpers to apply the BaseUnit field to query operations.
|
static ProductPlantCostingField<BigDecimal> |
COSTING_LOT_SIZE
Use with available fluent helpers to apply the CostingLotSize field to query operations.
|
static ProductPlantCostingField<String> |
COSTING_PRODUCTION_VERSION
Use with available fluent helpers to apply the CostingProductionVersion field to query operations.
|
static ProductPlantCostingField<String> |
COSTING_SPECIAL_PROCUREMENT_TYPE
Use with available fluent helpers to apply the CostingSpecialProcurementType field to query operations.
|
static ProductPlantCostingField<Boolean> |
IS_CO_PRODUCT
Use with available fluent helpers to apply the IsCoProduct field to query operations.
|
static ProductPlantCostingField<Boolean> |
IS_FIXED_PRICE_CO_PRODUCT
Use with available fluent helpers to apply the IsFixedPriceCoProduct field to query operations.
|
static ProductPlantCostingField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static ProductPlantCostingField<String> |
PRODUCT
Use with available fluent helpers to apply the Product field to query operations.
|
static ProductPlantCostingField<String> |
PRODUCT_BOM_USAGE
Use with available fluent helpers to apply the ProductBOMUsage field to query operations.
|
static ProductPlantCostingField<Boolean> |
PRODUCT_IS_COSTING_RELEVANT
Use with available fluent helpers to apply the ProductIsCostingRelevant field to query operations.
|
static ProductPlantCostingField<String> |
SOURCE_BOM_ALTERNATIVE
Use with available fluent helpers to apply the SourceBOMAlternative field to query operations.
|
static ProductPlantCostingField<String> |
TASK_LIST_GROUP
Use with available fluent helpers to apply the TaskListGroup field to query operations.
|
static ProductPlantCostingField<String> |
TASK_LIST_GROUP_COUNTER
Use with available fluent helpers to apply the TaskListGroupCounter field to query operations.
|
static ProductPlantCostingField<String> |
TASK_LIST_TYPE
Use with available fluent helpers to apply the TaskListType field to query operations.
|
static ProductPlantCostingField<String> |
VARIANCE_KEY
Use with available fluent helpers to apply the VarianceKey field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
ProductPlantCosting() |
ProductPlantCosting(String product,
String plant,
Boolean isCoProduct,
BigDecimal costingLotSize,
String varianceKey,
String baseUnit,
String taskListGroupCounter,
String taskListGroup,
String taskListType,
String costingProductionVersion,
Boolean isFixedPriceCoProduct,
String costingSpecialProcurementType,
String sourceBOMAlternative,
String productBOMUsage,
Boolean productIsCostingRelevant) |
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 ProductPlantCosting.ProductPlantCostingBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> ProductPlantCostingField<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 |
getBaseUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getCostingLotSize()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getCostingProductionVersion()
Constraints: Not nullable, Maximum length: 4
|
String |
getCostingSpecialProcurementType()
Constraints: Not nullable, Maximum length: 2
|
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.
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
Boolean |
getIsCoProduct()
Constraints: none
|
Boolean |
getIsFixedPriceCoProduct()
Constraints: none
|
protected Map<String,Object> |
getKey() |
String |
getPlant()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getProduct()
(Key Field) Constraints: Not nullable, Maximum length: 40
|
String |
getProductBOMUsage()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getProductIsCostingRelevant()
Constraints: none
|
String |
getSourceBOMAlternative()
Constraints: Not nullable, Maximum length: 2
|
String |
getTaskListGroup()
Constraints: Not nullable, Maximum length: 8
|
String |
getTaskListGroupCounter()
Constraints: Not nullable, Maximum length: 2
|
String |
getTaskListType()
Constraints: Not nullable, Maximum length: 1
|
Class<ProductPlantCosting> |
getType() |
String |
getVarianceKey()
Constraints: Not nullable, Maximum length: 6
|
int |
hashCode() |
void |
setBaseUnit(String baseUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setCostingLotSize(BigDecimal costingLotSize)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setCostingProductionVersion(String costingProductionVersion)
Constraints: Not nullable, Maximum length: 4
|
void |
setCostingSpecialProcurementType(String costingSpecialProcurementType)
Constraints: Not nullable, Maximum length: 2
|
void |
setIsCoProduct(Boolean isCoProduct)
Constraints: none
|
void |
setIsFixedPriceCoProduct(Boolean isFixedPriceCoProduct)
Constraints: none
|
void |
setPlant(String plant)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setProduct(String product)
(Key Field) Constraints: Not nullable, Maximum length: 40
|
void |
setProductBOMUsage(String productBOMUsage)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductIsCostingRelevant(Boolean productIsCostingRelevant)
Constraints: none
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSourceBOMAlternative(String sourceBOMAlternative)
Constraints: Not nullable, Maximum length: 2
|
void |
setTaskListGroup(String taskListGroup)
Constraints: Not nullable, Maximum length: 8
|
void |
setTaskListGroupCounter(String taskListGroupCounter)
Constraints: Not nullable, Maximum length: 2
|
void |
setTaskListType(String taskListType)
Constraints: Not nullable, Maximum length: 1
|
void |
setVarianceKey(String varianceKey)
Constraints: Not nullable, Maximum length: 6
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final ProductPlantCostingSelectable ALL_FIELDS
public static final ProductPlantCostingField<String> PRODUCT
public static final ProductPlantCostingField<String> PLANT
public static final ProductPlantCostingField<Boolean> IS_CO_PRODUCT
public static final ProductPlantCostingField<BigDecimal> COSTING_LOT_SIZE
public static final ProductPlantCostingField<String> VARIANCE_KEY
public static final ProductPlantCostingField<String> BASE_UNIT
public static final ProductPlantCostingField<String> TASK_LIST_GROUP_COUNTER
public static final ProductPlantCostingField<String> TASK_LIST_GROUP
public static final ProductPlantCostingField<String> TASK_LIST_TYPE
public static final ProductPlantCostingField<String> COSTING_PRODUCTION_VERSION
public static final ProductPlantCostingField<Boolean> IS_FIXED_PRICE_CO_PRODUCT
public static final ProductPlantCostingField<String> COSTING_SPECIAL_PROCUREMENT_TYPE
public static final ProductPlantCostingField<String> SOURCE_BOM_ALTERNATIVE
public static final ProductPlantCostingField<String> PRODUCT_BOM_USAGE
public static final ProductPlantCostingField<Boolean> PRODUCT_IS_COSTING_RELEVANT
public ProductPlantCosting()
public ProductPlantCosting(@Nullable String product, @Nullable String plant, @Nullable Boolean isCoProduct, @Nullable BigDecimal costingLotSize, @Nullable String varianceKey, @Nullable String baseUnit, @Nullable String taskListGroupCounter, @Nullable String taskListGroup, @Nullable String taskListType, @Nullable String costingProductionVersion, @Nullable Boolean isFixedPriceCoProduct, @Nullable String costingSpecialProcurementType, @Nullable String sourceBOMAlternative, @Nullable String productBOMUsage, @Nullable Boolean productIsCostingRelevant)
@Nonnull public Class<ProductPlantCosting> getType()
getType
in class VdmObject<ProductPlantCosting>
public void setProduct(@Nullable String product)
Original property name from the Odata EDM: Product
product
- Alphanumeric key uniquely identifying the material.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setIsCoProduct(@Nullable Boolean isCoProduct)
Original property name from the Odata EDM: IsCoProduct
isCoProduct
- Indicator you can use to specify that the material can also be used as a co-product.public void setCostingLotSize(@Nullable BigDecimal costingLotSize)
Original property name from the Odata EDM: CostingLotSize
The costing lot size in the material master record is usually used as a basis for costing all materials within one low-level code. If these materials (such as semi-finished products) are used in materials (such as finished products) in the next-highest low-level code, the costing results are converted to the costing lot size of the material costed (in this case, the finished product) to calculate the material costs for the finished product.In material costing and sales order costing, you can make a setting in the costing variant to have the system use the costing lot size of the highest material as a basis for costing the materials below it.
costingLotSize
- Lot size of the costed object (such as a material or sales order) used in the product cost estimate as
the basis for costing.public void setVarianceKey(@Nullable String varianceKey)
Original property name from the Odata EDM: VarianceKey
Variances can only be calculated for the orders for which a variance key has been entered. This key is defaulted through the costing view in the material master record.If you have activated variance calculation in the variance key, the value of the scrap is calculated at target cost and subtracted from the actual costs before the variances are determined.If you are working with cost object hierarchies, the cost object category determines how variances are calculated.If the costs collected at hierarchy level are distributed to the assigned orders (product cost collectors or manufacturing orders), you must enter a variance key in each order so that the R/3 System can calculate variances for the assigned orders.If the costs collected at the hierarchy level are settled as price differences, you must store a variance key in the cost object nodes and calculate variances for the entire cost object hierarchy.You select the control parameters for variance calculation through the variance key in the order or in the cost object hierarchy and a target version.
varianceKey
- Key that controls variance calculation.public void setBaseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
baseUnit
- Unit of measure in which stocks of the material are managed. The system converts all the quantities
you enter in other units of measure (alternative units of measure) to the base unit of measure.public void setTaskListGroupCounter(@Nullable String taskListGroupCounter)
Original property name from the Odata EDM: TaskListGroupCounter
In Production Planning and Control, for example, it serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.The group counter can be used to identify different lot-size ranges, for example.
taskListGroupCounter
- This key and the task list group uniquely identify a task list.public void setTaskListGroup(@Nullable String taskListGroup)
Original property name from the Odata EDM: TaskListGroup
You can use groups, for instance, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
taskListGroup
- Key identifying a group.public void setTaskListType(@Nullable String taskListType)
Original property name from the Odata EDM: TaskListType
Routings are defined under the following task list types:RoutingsReference operation setsMaster recipeGeneral maintenance task listEquipment task listInspection planTask list for funct. location
taskListType
- Key which classifies task lists according to their functionality.public void setCostingProductionVersion(@Nullable String costingProductionVersion)
Original property name from the Odata EDM: CostingProductionVersion
With joint production, you can here enter an apportionment structure for a leading co-product, or for a differenct co-product the reference to a leading co-product or process material through which the quantity structure is to be determined.So that the quantity structure can be determined automatically using the production version, you must have selected the setting 2 (selection by production version) or 3 (selection only by production version) in the material master record in MRP view 4 under selection method. This is unnecessary if you entered the production version direct when you created the cost estimate or if it was entered direct in the material master record in costing view 1 under production version.
costingProductionVersion
- Key that determines the production version which is used to determine the quantity structure for the
cost estimate.public void setIsFixedPriceCoProduct(@Nullable Boolean isFixedPriceCoProduct)
Original property name from the Odata EDM: IsFixedPriceCoProduct
A material marked as a fixed price co-product is not costed using a joint production process.If the material is an output material of a process with several co-products, the costs for the fixed price co-product are taken from the process costs using the net realizable-value method.Set this indicator if the material is a co-product, but the costs are not to be determined using an apportionment method; instead, a preset price is to be used for the material.The price for the fixed price co-product is taken from a cost estimate without quantity structure; alternatively, a price from the material master is used.You can only set this indicator if you have also set the co-product indicator for the material.Fixed-price co-products are shown in the itemization as items of category M (not A, as is the case with normal co-products), albeit with negative quantities and values.
isFixedPriceCoProduct
- indicates the material as a fixed price co-product.public void setCostingSpecialProcurementType(@Nullable String costingSpecialProcurementType)
Original property name from the Odata EDM: CostingSpecialProcurementType
If you enter a special procurement type in the Costing view of the material master record, it is used in costing.If you do not enter a special procurement type in the costing view of the material master record, the system uses the special procurement type in the MRP view.If you want to cost a material as externally procured by ignoring the existing quantity structure in the system when costing, the following options are available:· In the MRP view of the material master record, enter procurement type F and no special procurement type (neither in the MRP view nor in the Costing view).· In Customizing for Product Cost Planning, create a new special procurement type (procurement type: F and special procurement type: blank) and enter this special procurement type in the material's Costing view.If you want to cost a material by ignoring the BOM but including the routing, go to Customizing for Product Cost Planning and create a new special procurement type (procurement type: E; special procurement type: E) and enter this special procurement type in the material's Costing view.
costingSpecialProcurementType
- Key that you use to specify the material's procurement type predetermined by the material type in more
detail for costing.public void setSourceBOMAlternative(@Nullable String sourceBOMAlternative)
Original property name from the Odata EDM: SourceBOMAlternative
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.
sourceBOMAlternative
- Identifies one BOM in a BOM group.public void setProductBOMUsage(@Nullable String productBOMUsage)
Original property name from the Odata EDM: ProductBOMUsage
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.
productBOMUsage
- This key defines the area (such as engineering/design or production) where a BOM can be used.public void setProductIsCostingRelevant(@Nullable Boolean productIsCostingRelevant)
Original property name from the Odata EDM: ProductIsCostingRelevant
If you select this indicator, you cannot create any of the following for this material:Material cost estimate (with and without quantity structure)Sales order costingProcurement alternativesThe material is excluded from selection and BOM explosion, so that no cost component split will be created by the costing process. If the material is included in another cost estimate as a component to be valuated, the valuation price is determined through the valuation variant if no cost estimate with the same key exists for the material.
productIsCostingRelevant
- Controls whether a cost estimate or a procurement alternative can be created for a material.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<ProductPlantCosting>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<ProductPlantCosting>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<ProductPlantCosting>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<ProductPlantCosting>
@Nonnull public static <T> ProductPlantCostingField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.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> ProductPlantCostingField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<ProductPlantCosting>
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<ProductPlantCosting>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
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.
attachToService
in class VdmEntity<ProductPlantCosting>
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.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<ProductPlantCosting>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull public static ProductPlantCosting.ProductPlantCostingBuilder builder()
@Nullable public String getProduct()
Original property name from the Odata EDM: Product
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public Boolean getIsCoProduct()
Original property name from the Odata EDM: IsCoProduct
@Nullable public BigDecimal getCostingLotSize()
Original property name from the Odata EDM: CostingLotSize
The costing lot size in the material master record is usually used as a basis for costing all materials within one low-level code. If these materials (such as semi-finished products) are used in materials (such as finished products) in the next-highest low-level code, the costing results are converted to the costing lot size of the material costed (in this case, the finished product) to calculate the material costs for the finished product.In material costing and sales order costing, you can make a setting in the costing variant to have the system use the costing lot size of the highest material as a basis for costing the materials below it.
@Nullable public String getVarianceKey()
Original property name from the Odata EDM: VarianceKey
Variances can only be calculated for the orders for which a variance key has been entered. This key is defaulted through the costing view in the material master record.If you have activated variance calculation in the variance key, the value of the scrap is calculated at target cost and subtracted from the actual costs before the variances are determined.If you are working with cost object hierarchies, the cost object category determines how variances are calculated.If the costs collected at hierarchy level are distributed to the assigned orders (product cost collectors or manufacturing orders), you must enter a variance key in each order so that the R/3 System can calculate variances for the assigned orders.If the costs collected at the hierarchy level are settled as price differences, you must store a variance key in the cost object nodes and calculate variances for the entire cost object hierarchy.You select the control parameters for variance calculation through the variance key in the order or in the cost object hierarchy and a target version.
@Nullable public String getBaseUnit()
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
@Nullable public String getTaskListGroupCounter()
Original property name from the Odata EDM: TaskListGroupCounter
In Production Planning and Control, for example, it serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.The group counter can be used to identify different lot-size ranges, for example.
@Nullable public String getTaskListGroup()
Original property name from the Odata EDM: TaskListGroup
You can use groups, for instance, to identify two routings that have different production steps for one material.Enter the group to which you want to restrict the selection.
@Nullable public String getTaskListType()
Original property name from the Odata EDM: TaskListType
Routings are defined under the following task list types:RoutingsReference operation setsMaster recipeGeneral maintenance task listEquipment task listInspection planTask list for funct. location
@Nullable public String getCostingProductionVersion()
Original property name from the Odata EDM: CostingProductionVersion
With joint production, you can here enter an apportionment structure for a leading co-product, or for a differenct co-product the reference to a leading co-product or process material through which the quantity structure is to be determined.So that the quantity structure can be determined automatically using the production version, you must have selected the setting 2 (selection by production version) or 3 (selection only by production version) in the material master record in MRP view 4 under selection method. This is unnecessary if you entered the production version direct when you created the cost estimate or if it was entered direct in the material master record in costing view 1 under production version.
@Nullable public Boolean getIsFixedPriceCoProduct()
Original property name from the Odata EDM: IsFixedPriceCoProduct
A material marked as a fixed price co-product is not costed using a joint production process.If the material is an output material of a process with several co-products, the costs for the fixed price co-product are taken from the process costs using the net realizable-value method.Set this indicator if the material is a co-product, but the costs are not to be determined using an apportionment method; instead, a preset price is to be used for the material.The price for the fixed price co-product is taken from a cost estimate without quantity structure; alternatively, a price from the material master is used.You can only set this indicator if you have also set the co-product indicator for the material.Fixed-price co-products are shown in the itemization as items of category M (not A, as is the case with normal co-products), albeit with negative quantities and values.
@Nullable public String getCostingSpecialProcurementType()
Original property name from the Odata EDM: CostingSpecialProcurementType
If you enter a special procurement type in the Costing view of the material master record, it is used in costing.If you do not enter a special procurement type in the costing view of the material master record, the system uses the special procurement type in the MRP view.If you want to cost a material as externally procured by ignoring the existing quantity structure in the system when costing, the following options are available:· In the MRP view of the material master record, enter procurement type F and no special procurement type (neither in the MRP view nor in the Costing view).· In Customizing for Product Cost Planning, create a new special procurement type (procurement type: F and special procurement type: blank) and enter this special procurement type in the material's Costing view.If you want to cost a material by ignoring the BOM but including the routing, go to Customizing for Product Cost Planning and create a new special procurement type (procurement type: E; special procurement type: E) and enter this special procurement type in the material's Costing view.
@Nullable public String getSourceBOMAlternative()
Original property name from the Odata EDM: SourceBOMAlternative
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 getProductBOMUsage()
Original property name from the Odata EDM: ProductBOMUsage
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 Boolean getProductIsCostingRelevant()
Original property name from the Odata EDM: ProductIsCostingRelevant
If you select this indicator, you cannot create any of the following for this material:Material cost estimate (with and without quantity structure)Sales order costingProcurement alternativesThe material is excluded from selection and BOM explosion, so that no cost component split will be created by the costing process. If the material is included in another cost estimate as a component to be valuated, the valuation price is determined through the valuation variant if no cost estimate with the same key exists for the material.
@Nonnull public String toString()
toString
in class VdmObject<ProductPlantCosting>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<ProductPlantCosting>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<ProductPlantCosting>
public int hashCode()
hashCode
in class VdmObject<ProductPlantCosting>
Copyright © 2020 SAP SE. All rights reserved.