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.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder pricingProcedureStep(@Nullable String pricingProcedureStep)
Original property name from the Odata EDM: PricingProcedureStep
this
.@Nonnull 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.
this
.@Nonnull 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.
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder priceConditionDeterminationDte(@Nullable LocalDateTime priceConditionDeterminationDte)
Original property name from the Odata EDM: PriceConditionDeterminationDte
this
.@Nonnull 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.
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionBaseValue(@Nullable BigDecimal conditionBaseValue)
Original property name from the Odata EDM: ConditionBaseValue
During the pricing process in a business document, for each condition type used in the pricing procedure, the system calculates the condition value as follows:For several calculation types (for example, A, C, D, E, F, H, I, J, K, M, N, O, P, W), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, A, C, D, E, F, H, I, M, N, O, P), the system multiplies the condition amount with the condition basis to calculate the condition value.For several calculation types (for example, C, D, E, F, H, I, M, N, O, P), the value of the condition basis refers to a unit of measure. If the unit of measure of the conditions basis differs from the unit of measure of the price condition (condition unit), the system automatically converts it into the unit of measure of the condition unit. For calculation types C, M, N, O, and P, the item quantity is the default value for the condition basis.For several calculation types (for example, A, B, H, I, J, K, W), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.For several calculation types (for example, A, B, H, I), the condition basis is a currency field and refers to a currency key field. Such a currency field in the context of pricing is called currency amount. If the currency key of the conditions basis (currency amount) differs from the currency key of the document, the system automatically converts the condition basis (currency amount) into the currency of the document. The system uses the exchange rates for the currencies that are defined in the general settings for currencies.Note: The standard number of decimal places for a currency is two.Currencies that use a different number of decimal places must in addition be entered into table TCURX, where you can explicitly define the number of decimal places, for example, zero decimals for Japanese yen JPY.Deviations are preconfigured depending on the currency, for example, zero decimals for Japanese yen JPY.If you have defined scales, the system uses the condition basis to determine the valid scale line with the corresponding condition amount.In usage-based pricing models, the usage corresponds to the condition basis.The condition basis can be aQuantityWeightVolumeCurrency AmountA sales order includes an item with a quantity of 120 pieces:The determined list price of USD 101 (condition amount) multiplied with the quantity of 120 pieces (condition basis) results in a condition value of USD 12120.Two discounts are applied to the item of this sales order:The first discount (-1 USD / PC) is based on the quantity ordered that is the condition basis equals the item quantity and the result is - 120 USD.The second discount (- 2 %) is calculated as a percentage which is applied to the results of the list price (USD 12120) and the first discount (- 120 USD). Its result (12000 USD) is the condition basis for the second discount. The result of the second discount is - 240 USD.
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder 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 SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionCurrency(@Nullable String conditionCurrency)
Original property name from the Odata EDM: ConditionCurrency
this
.@Nonnull 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.
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionQuantityUnit(@Nullable String conditionQuantityUnit)
Original property name from the Odata EDM: ConditionQuantityUnit
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionQuantitySAPUnit(@Nullable String conditionQuantitySAPUnit)
Original property name from the Odata EDM: ConditionQuantitySAPUnit
For the condition quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionQuantityISOUnit(@Nullable String conditionQuantityISOUnit)
Original property name from the Odata EDM: ConditionQuantityISOUnit
For the condition quantity, you can use either the language-dependent unit code, the ISO code, or the SAP code (the format found in the database without conversions).
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionIsForStatistics(@Nullable Boolean conditionIsForStatistics)
Original property name from the Odata EDM: ConditionIsForStatistics
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionOrigin(@Nullable String conditionOrigin)
Original property name from the Odata EDM: ConditionOrigin
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder isGroupCondition(@Nullable String isGroupCondition)
Original property name from the Odata EDM: IsGroupCondition
For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.A sales order contains two items. Both items belong to the material group 01.Material Quantity Material groupA 150 01B 100 01The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:Scale quantity Discountfrom 1 pc -1%from 200 pc -2%Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.
this
.@Nonnull 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.
this
.@Nonnull 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.
this
.@Nonnull 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
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionClass(@Nullable String conditionClass)
Original property name from the Odata EDM: ConditionClass
Allows standardized processing of individual condition classes within the system.
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder pricingScaleBasis(@Nullable String pricingScaleBasis)
Original property name from the Odata EDM: PricingScaleBasis
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionScaleBasisValue(@Nullable BigDecimal conditionScaleBasisValue)
Original property name from the Odata EDM: ConditionScaleBasisValue
The scale base value can be a condition value or the value of a quantity, weight, and so on that has been entered in the document.You create a price condition based on a simple quantity scale with scale type A: Base scale:Quantity Price per Unit10 12 USD100 11 USD1000 10 USDA sales order item with 150 units qualifies for the condition scale quantity of 100 units and the price per unit of USD 11. In this case, the scale base value that determines the price is 150.
this
.@Nonnull public SalesOrderItmPrcgElmntSimln.SalesOrderItmPrcgElmntSimlnBuilder conditionIsManuallyChanged(@Nullable Boolean conditionIsManuallyChanged)
Original property name from the Odata EDM: ConditionIsManuallyChanged
this
.@Nonnull public SalesOrderItmPrcgElmntSimln build()
Copyright © 2021 SAP SE. All rights reserved.