public static final class SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder extends Object
@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder salesOrder(SalesOrderSimulation value)
value
- The SalesOrderSimulation to build this SalesOrderItmPrcgElmntSimln with.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder salesOrder(String value)
Original property name from the Odata EDM: SalesOrder
value
- The salesOrder to build this SalesOrderItmPrcgElmntSimln with.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder salesOrderItem(SalesOrderItemSimulation value)
value
- The SalesOrderItemSimulation to build this SalesOrderItmPrcgElmntSimln with.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder salesOrderItem(String value)
Original property name from the Odata EDM: SalesOrderItem
value
- The salesOrderItem to build this SalesOrderItmPrcgElmntSimln with.public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder pricingProcedureStep(@Nullable String pricingProcedureStep)
Original property name from the Odata EDM: PricingProcedureStep
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder 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.
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder 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.
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionCalculationType(@Nullable String conditionCalculationType)
Original property name from the Odata EDM: ConditionCalculationType
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.
system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionRateValue(@Nullable BigDecimal conditionRateValue)
Original property name from the Odata EDM: ConditionRateValue
The following examples illustrate how you can use the rate in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you are creating a condition based on percentage 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 Rate unit field.
rate can be an amount or a percentage. If the condition includes a pricing scale, the rate displays the first line of the scale.public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionCurrency(@Nullable String conditionCurrency)
Original property name from the Odata EDM: ConditionCurrency
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder 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).public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionQuantityUnit(@Nullable String conditionQuantityUnit)
Original property name from the Odata EDM: ConditionQuantityUnit
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionIsForStatistics(@Nullable Boolean conditionIsForStatistics)
Original property name from the Odata EDM: ConditionIsForStatistics
altering the value).public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionAmount(@Nullable BigDecimal conditionAmount)
Original property name from the Odata EDM: ConditionAmount
This value is used as a total for the condition in the pricing procedure.
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionInactiveReason(@Nullable String conditionInactiveReason)
Original property name from the Odata EDM: ConditionInactiveReason
A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionIsManuallyChanged(@Nullable Boolean conditionIsManuallyChanged)
Original property name from the Odata EDM: ConditionIsManuallyChanged
condition screen).public SalesOrderItmPrcgElmntSimln build()
Copyright © 2019 SAP SE. All rights reserved.