public static class ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder extends Object
@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder serviceConfirmation(@Nullable String serviceConfirmation)
Original property name from the Odata EDM: ServiceConfirmation
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder serviceConfirmationItem(@Nullable String serviceConfirmationItem)
Original property name from the Odata EDM: ServiceConfirmationItem
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder pricingProcedureStep(@Nullable String pricingProcedureStep)
Original property name from the Odata EDM: PricingProcedureStep
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder pricingProcedureCounter(@Nullable String pricingProcedureCounter)
Original property name from the Odata EDM: PricingProcedureCounter
During automatic pricing, the system takes into account the sequence specified by the counter.
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder conditionType(@Nullable String conditionType)
Original property name from the Odata EDM: ConditionType
The condition type indicates, for example, whether, during pricing, the system applies a price, a discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these pricing elements, there is a condition type defined in the system.
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder conditionRateValue(@Nullable BigDecimal conditionRateValue)
Original property name from the Odata EDM: ConditionRateValue
Depending on the condition type, it can be a fixed amount, a percentage, or per mille. If the condition includes a pricing scale, the condition amount or percentage displays the first line of the scale.The following examples illustrate how you can use the condition amount or percentage in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you create a condition based on percentage, such as discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Condition Unit field.
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder conditionCurrency(@Nullable String conditionCurrency)
Original property name from the Odata EDM: ConditionCurrency
this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder conditionQuantity(@Nullable BigDecimal conditionQuantity)
Original property name from the Odata EDM: ConditionQuantity
You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
example, bottles).this
.@Nonnull public ServiceConfItemPriceElement.ServiceConfItemPriceElementBuilder conditionQuantityUnit(@Nullable String conditionQuantityUnit)
Original property name from the Odata EDM: ConditionQuantityUnit
this
.@Nonnull public ServiceConfItemPriceElement build()
Copyright © 2020 SAP SE. All rights reserved.