public static class ProductPlantCosting.ProductPlantCostingBuilder extends Object
public ProductPlantCosting.ProductPlantCostingBuilder product(@Nullable String product)
Original property name from the Odata EDM: Product
this.public ProductPlantCosting.ProductPlantCostingBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.public ProductPlantCosting.ProductPlantCostingBuilder isCoProduct(@Nullable Boolean isCoProduct)
Original property name from the Odata EDM: IsCoProduct
this.public ProductPlantCosting.ProductPlantCostingBuilder costingLotSize(@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.
the basis for costing.this.public ProductPlantCosting.ProductPlantCostingBuilder varianceKey(@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.
this.public ProductPlantCosting.ProductPlantCostingBuilder baseUnit(@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.
enter in other units of measure (alternative units of measure) to the base unit of measure.this.public ProductPlantCosting.ProductPlantCostingBuilder taskListGroupCounter(@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.
this.public ProductPlantCosting.ProductPlantCostingBuilder taskListGroup(@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.
this.public ProductPlantCosting.ProductPlantCostingBuilder taskListType(@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
this.public ProductPlantCosting.ProductPlantCostingBuilder costingProductionVersion(@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.
estimate.this.public ProductPlantCosting.ProductPlantCostingBuilder isFixedPriceCoProduct(@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.
this.public ProductPlantCosting.ProductPlantCostingBuilder costingSpecialProcurementType(@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.
detail for costing.this.public ProductPlantCosting.ProductPlantCostingBuilder sourceBOMAlternative(@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.
this.public ProductPlantCosting.ProductPlantCostingBuilder productBOMUsage(@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.
this.public ProductPlantCosting.ProductPlantCostingBuilder productIsCostingRelevant(@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.
this.public ProductPlantCosting build()
Copyright © 2020 SAP SE. All rights reserved.