public class ProductValuationCosting extends VdmEntity<ProductValuationCosting>
Original entity name from the Odata EDM: A_ProductValuationCostingType
Modifier and Type | Class and Description |
---|---|
static class |
ProductValuationCosting.ProductValuationCostingBuilder |
Modifier and Type | Field and Description |
---|---|
static ProductValuationCostingSelectable |
ALL_FIELDS
Selector for all available fields of ProductValuationCosting.
|
static ProductValuationCostingField<String> |
COST_ORIGIN_GROUP
Use with available fluent helpers to apply the CostOriginGroup field to query operations.
|
static ProductValuationCostingField<String> |
COSTING_OVERHEAD_GROUP
Use with available fluent helpers to apply the CostingOverheadGroup field to query operations.
|
static ProductValuationCostingField<Boolean> |
IS_MATERIAL_COSTED_WITH_QTY_STRUC
Use with available fluent helpers to apply the IsMaterialCostedWithQtyStruc field to query operations.
|
static ProductValuationCostingField<String> |
IS_MATERIAL_RELATED_ORIGIN
Use with available fluent helpers to apply the IsMaterialRelatedOrigin field to query operations.
|
static ProductValuationCostingField<String> |
PRODUCT
Use with available fluent helpers to apply the Product field to query operations.
|
static ProductValuationCostingField<String> |
VALUATION_AREA
Use with available fluent helpers to apply the ValuationArea field to query operations.
|
static ProductValuationCostingField<String> |
VALUATION_TYPE
Use with available fluent helpers to apply the ValuationType field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
ProductValuationCosting() |
ProductValuationCosting(String product,
String valuationArea,
String valuationType,
Boolean isMaterialCostedWithQtyStruc,
String isMaterialRelatedOrigin,
String costOriginGroup,
String costingOverheadGroup) |
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 ProductValuationCosting.ProductValuationCostingBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> ProductValuationCostingField<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 |
getCostingOverheadGroup()
Constraints: Not nullable, Maximum length: 10
|
String |
getCostOriginGroup()
Constraints: Not nullable, Maximum length: 4
|
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 |
getIsMaterialCostedWithQtyStruc()
Constraints: none
|
String |
getIsMaterialRelatedOrigin()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
String |
getProduct()
(Key Field) Constraints: Not nullable, Maximum length: 40
|
Class<ProductValuationCosting> |
getType() |
String |
getValuationArea()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getValuationType()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
int |
hashCode() |
void |
setCostingOverheadGroup(String costingOverheadGroup)
Constraints: Not nullable, Maximum length: 10
|
void |
setCostOriginGroup(String costOriginGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setIsMaterialCostedWithQtyStruc(Boolean isMaterialCostedWithQtyStruc)
Constraints: none
|
void |
setIsMaterialRelatedOrigin(String isMaterialRelatedOrigin)
Constraints: Not nullable, Maximum length: 1
|
void |
setProduct(String product)
(Key Field) Constraints: Not nullable, Maximum length: 40
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setValuationArea(String valuationArea)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setValuationType(String valuationType)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
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 ProductValuationCostingSelectable ALL_FIELDS
public static final ProductValuationCostingField<String> PRODUCT
public static final ProductValuationCostingField<String> VALUATION_AREA
public static final ProductValuationCostingField<String> VALUATION_TYPE
public static final ProductValuationCostingField<Boolean> IS_MATERIAL_COSTED_WITH_QTY_STRUC
public static final ProductValuationCostingField<String> IS_MATERIAL_RELATED_ORIGIN
public static final ProductValuationCostingField<String> COST_ORIGIN_GROUP
public static final ProductValuationCostingField<String> COSTING_OVERHEAD_GROUP
public ProductValuationCosting()
public ProductValuationCosting(@Nullable String product, @Nullable String valuationArea, @Nullable String valuationType, @Nullable Boolean isMaterialCostedWithQtyStruc, @Nullable String isMaterialRelatedOrigin, @Nullable String costOriginGroup, @Nullable String costingOverheadGroup)
@Nonnull public Class<ProductValuationCosting> getType()
getType
in class VdmObject<ProductValuationCosting>
public void setProduct(@Nullable String product)
Original property name from the Odata EDM: Product
product
- Alphanumeric key uniquely identifying the material.public void setValuationArea(@Nullable String valuationArea)
Original property name from the Odata EDM: ValuationArea
PlantAll plants belonging to a company code, in which case the valuation area is the company code
valuationArea
- Organizational level at which the material is valuated. A valuation area can be one of the following:public void setValuationType(@Nullable String valuationType)
Original property name from the Odata EDM: ValuationType
The valuation types allowed for a material are determined by the valuation category.If a material is valuated according to its origin (valuation category H), you can define the possible countries of origin as valuation types.
valuationType
- Uniquely identifies separately valuated stocks of a material.public void setIsMaterialCostedWithQtyStruc(@Nullable Boolean isMaterialCostedWithQtyStruc)
Original property name from the Odata EDM: IsMaterialCostedWithQtyStruc
If you usually cost materials using costing with quantity structure, turn on this indicator.If you usually cost materials using costing without quantity structure, do not turn on this indicator.You can change the indicator in the material master record at a later time.If you always cost your materials (including raw materials) using costing with quantity structure, you should turn on this indicator. This improves performance, because the system does not search in vain for existing cost estimates without a quantity structure for every material when it explodes the BOM. Therefore, only turn on this indicator if you normally cost the materials using costing without quantity structure.Regardless of the setting, you can cost a single material with or without quantity structure. However, you should bear in mind that this setting is always used in the costing run and in mixed costing (creating procurement alternatives).For every cost estimate, the system searches for existing cost estimates that have the materials in their structure. If a released cost estimate exists, the system copies it.If this indicator is set, the material is costed using costing with a quantity structure.The system searches for any existing cost estimates with quantity structure for the individual materials; it ignores existing cost estimates without quantity structure. If the system does not find any valid costing data for the materials, it costs the material or accesses the price in the material master. See also: Transfer controlIf this indicator is not set, the planned costs for the material are calculated using the cost estimate without quantity structure. In this case, you use unit costing to create the quantity structure manually by entering costing items for materials and activity types, for example.The system now searches for any existing cost estimates without quantity structure. If a cost estimate without quantity structure exists for a material, the results of this cost estimate are included in a cost estimate with quantity structure. If there is no cost estimate without quantity structure, the cost estimate with quantity structure accesses the price in the material master record. The planned costs for this material then go into the cost estimate with quantity structure as raw material costs.This does not apply if the indicator Ignore prod cost est w/o qty structure is set in the costing variant.
isMaterialCostedWithQtyStruc
- This indicator determines whether the material is costed using costing with or without a quantity
structure.public void setIsMaterialRelatedOrigin(@Nullable String isMaterialRelatedOrigin)
Original property name from the Odata EDM: IsMaterialRelatedOrigin
If you set this indicator, the costs incurred will be updatedunder a primary cost elementwith reference to the material numberThis enables you to analyze material costs in the information system in more detail.
isMaterialRelatedOrigin
- If this indicator is set, the material number will be written to the cost element itemization in the
Controlling module.public void setCostOriginGroup(@Nullable String costOriginGroup)
Original property name from the Odata EDM: CostOriginGroup
When material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element. If you enter an origin group for the material, the combination of source group and cost element is updated to the CO component. This means that you canDefine calculation bases for determination of overhead rates for particular material groups.Define cost components in product costing for particular material groups.Create rules for activating work in process for each material group.When overhead is calculated, an object is debited with overhead costs and another object (usually a cost center) is credited. For more information on the origin of overhead rates in the credit record, specify an origin group in the credit key. The system then displays the origin group in Cost Center Accounting, as well as the overhead cost element.
costOriginGroup
- Used for subdividing material and overhead costs.public void setCostingOverheadGroup(@Nullable String costingOverheadGroup)
Original property name from the Odata EDM: CostingOverheadGroup
In costing with and without quantity structure, and when costing production orders and run schedule headers, you can apply percentage overhead charges by means of an overhead key, if you:Assign a costing sheet to your production order or run schedule header, or to the valuation variant for the cost estimateEnter overhead charges in this costing sheet that use the overhead key fieldAssign the overhead key to an overhead groupEnter this overhead group in the material master record of the material
costingOverheadGroup
- Key that groups materials to which the same overhead is applied.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<ProductValuationCosting>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<ProductValuationCosting>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<ProductValuationCosting>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<ProductValuationCosting>
@Nonnull public static <T> ProductValuationCostingField<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> ProductValuationCostingField<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<ProductValuationCosting>
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<ProductValuationCosting>
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<ProductValuationCosting>
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<ProductValuationCosting>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull public static ProductValuationCosting.ProductValuationCostingBuilder builder()
@Nullable public String getProduct()
Original property name from the Odata EDM: Product
@Nullable public String getValuationArea()
Original property name from the Odata EDM: ValuationArea
PlantAll plants belonging to a company code, in which case the valuation area is the company code
@Nullable public String getValuationType()
Original property name from the Odata EDM: ValuationType
The valuation types allowed for a material are determined by the valuation category.If a material is valuated according to its origin (valuation category H), you can define the possible countries of origin as valuation types.
@Nullable public Boolean getIsMaterialCostedWithQtyStruc()
Original property name from the Odata EDM: IsMaterialCostedWithQtyStruc
If you usually cost materials using costing with quantity structure, turn on this indicator.If you usually cost materials using costing without quantity structure, do not turn on this indicator.You can change the indicator in the material master record at a later time.If you always cost your materials (including raw materials) using costing with quantity structure, you should turn on this indicator. This improves performance, because the system does not search in vain for existing cost estimates without a quantity structure for every material when it explodes the BOM. Therefore, only turn on this indicator if you normally cost the materials using costing without quantity structure.Regardless of the setting, you can cost a single material with or without quantity structure. However, you should bear in mind that this setting is always used in the costing run and in mixed costing (creating procurement alternatives).For every cost estimate, the system searches for existing cost estimates that have the materials in their structure. If a released cost estimate exists, the system copies it.If this indicator is set, the material is costed using costing with a quantity structure.The system searches for any existing cost estimates with quantity structure for the individual materials; it ignores existing cost estimates without quantity structure. If the system does not find any valid costing data for the materials, it costs the material or accesses the price in the material master. See also: Transfer controlIf this indicator is not set, the planned costs for the material are calculated using the cost estimate without quantity structure. In this case, you use unit costing to create the quantity structure manually by entering costing items for materials and activity types, for example.The system now searches for any existing cost estimates without quantity structure. If a cost estimate without quantity structure exists for a material, the results of this cost estimate are included in a cost estimate with quantity structure. If there is no cost estimate without quantity structure, the cost estimate with quantity structure accesses the price in the material master record. The planned costs for this material then go into the cost estimate with quantity structure as raw material costs.This does not apply if the indicator Ignore prod cost est w/o qty structure is set in the costing variant.
@Nullable public String getIsMaterialRelatedOrigin()
Original property name from the Odata EDM: IsMaterialRelatedOrigin
If you set this indicator, the costs incurred will be updatedunder a primary cost elementwith reference to the material numberThis enables you to analyze material costs in the information system in more detail.
@Nullable public String getCostOriginGroup()
Original property name from the Odata EDM: CostOriginGroup
When material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element. If you enter an origin group for the material, the combination of source group and cost element is updated to the CO component. This means that you canDefine calculation bases for determination of overhead rates for particular material groups.Define cost components in product costing for particular material groups.Create rules for activating work in process for each material group.When overhead is calculated, an object is debited with overhead costs and another object (usually a cost center) is credited. For more information on the origin of overhead rates in the credit record, specify an origin group in the credit key. The system then displays the origin group in Cost Center Accounting, as well as the overhead cost element.
@Nullable public String getCostingOverheadGroup()
Original property name from the Odata EDM: CostingOverheadGroup
In costing with and without quantity structure, and when costing production orders and run schedule headers, you can apply percentage overhead charges by means of an overhead key, if you:Assign a costing sheet to your production order or run schedule header, or to the valuation variant for the cost estimateEnter overhead charges in this costing sheet that use the overhead key fieldAssign the overhead key to an overhead groupEnter this overhead group in the material master record of the material
@Nonnull public String toString()
toString
in class VdmObject<ProductValuationCosting>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<ProductValuationCosting>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<ProductValuationCosting>
public int hashCode()
hashCode
in class VdmObject<ProductValuationCosting>
Copyright © 2021 SAP SE. All rights reserved.