public class SalesOrderPrcgElmntSimln extends VdmEntity<SalesOrderPrcgElmntSimln>
Original entity name from the Odata EDM: A_SalesOrderPrcgElmntSimlnType
Modifier and Type | Class and Description |
---|---|
static class |
SalesOrderPrcgElmntSimln.SalesOrderPrcgElmntSimlnBuilder
Helper class to allow for fluent creation of SalesOrderPrcgElmntSimln instances.
|
Modifier and Type | Field and Description |
---|---|
static SalesOrderPrcgElmntSimlnSelectable |
ALL_FIELDS
Selector for all available fields of SalesOrderPrcgElmntSimln.
|
static SalesOrderPrcgElmntSimlnField<BigDecimal> |
CONDITION_AMOUNT
Use with available fluent helpers to apply the ConditionAmount field to query operations.
|
static SalesOrderPrcgElmntSimlnField<BigDecimal> |
CONDITION_BASE_VALUE
Use with available fluent helpers to apply the ConditionBaseValue field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_CALCULATION_TYPE
Use with available fluent helpers to apply the ConditionCalculationType field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_CLASS
Use with available fluent helpers to apply the ConditionClass field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_CURRENCY
Use with available fluent helpers to apply the ConditionCurrency field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_INACTIVE_REASON
Use with available fluent helpers to apply the ConditionInactiveReason field to query operations.
|
static SalesOrderPrcgElmntSimlnField<Boolean> |
CONDITION_IS_FOR_STATISTICS
Use with available fluent helpers to apply the ConditionIsForStatistics field to query operations.
|
static SalesOrderPrcgElmntSimlnField<Boolean> |
CONDITION_IS_MANUALLY_CHANGED
Use with available fluent helpers to apply the ConditionIsManuallyChanged field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_ORIGIN
Use with available fluent helpers to apply the ConditionOrigin field to query operations.
|
static SalesOrderPrcgElmntSimlnField<BigDecimal> |
CONDITION_QUANTITY
Use with available fluent helpers to apply the ConditionQuantity field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_QUANTITY_ISO_UNIT
Use with available fluent helpers to apply the ConditionQuantityISOUnit field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_QUANTITY_SAP_UNIT
Use with available fluent helpers to apply the ConditionQuantitySAPUnit field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_QUANTITY_UNIT
Use with available fluent helpers to apply the ConditionQuantityUnit field to query operations.
|
static SalesOrderPrcgElmntSimlnField<BigDecimal> |
CONDITION_RATE_VALUE
Use with available fluent helpers to apply the ConditionRateValue field to query operations.
|
static SalesOrderPrcgElmntSimlnField<BigDecimal> |
CONDITION_SCALE_BASIS_VALUE
Use with available fluent helpers to apply the ConditionScaleBasisValue field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
CONDITION_TYPE
Use with available fluent helpers to apply the ConditionType field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
IS_GROUP_CONDITION
Use with available fluent helpers to apply the IsGroupCondition field to query operations.
|
static SalesOrderPrcgElmntSimlnField<LocalDateTime> |
PRICE_CONDITION_DETERMINATION_DTE
Use with available fluent helpers to apply the PriceConditionDeterminationDte field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
PRICING_PROCEDURE_COUNTER
Use with available fluent helpers to apply the PricingProcedureCounter field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
PRICING_PROCEDURE_STEP
Use with available fluent helpers to apply the PricingProcedureStep field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
PRICING_SCALE_BASIS
Use with available fluent helpers to apply the PricingScaleBasis field to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
SALES_ORDER
Use with available fluent helpers to apply the SalesOrder field to query operations.
|
static SalesOrderPrcgElmntSimlnOneToOneLink<SalesOrderSimulation> |
TO_SALES_ORDER
Use with available fluent helpers to apply the to_SalesOrder navigation property to query operations.
|
static SalesOrderPrcgElmntSimlnField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SalesOrderPrcgElmntSimln() |
SalesOrderPrcgElmntSimln(String salesOrder,
String pricingProcedureStep,
String pricingProcedureCounter,
String conditionType,
LocalDateTime priceConditionDeterminationDte,
String conditionCalculationType,
BigDecimal conditionBaseValue,
BigDecimal conditionRateValue,
String conditionCurrency,
BigDecimal conditionQuantity,
String conditionQuantityUnit,
String conditionQuantitySAPUnit,
String conditionQuantityISOUnit,
Boolean conditionIsForStatistics,
String conditionOrigin,
String isGroupCondition,
BigDecimal conditionAmount,
String transactionCurrency,
String conditionInactiveReason,
String conditionClass,
String pricingScaleBasis,
BigDecimal conditionScaleBasisValue,
Boolean conditionIsManuallyChanged,
SalesOrderSimulation toSalesOrder) |
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 SalesOrderPrcgElmntSimln.SalesOrderPrcgElmntSimlnBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
SalesOrderSimulation |
fetchSalesOrder()
Fetches the SalesOrderSimulation entity (one to one) associated with this entity.
|
static <T> SalesOrderPrcgElmntSimlnField<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) |
BigDecimal |
getConditionAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
BigDecimal |
getConditionBaseValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
String |
getConditionCalculationType()
Constraints: Not nullable, Maximum length: 3
|
String |
getConditionClass()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getConditionInactiveReason()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getConditionIsForStatistics()
Constraints: none
|
Boolean |
getConditionIsManuallyChanged()
Constraints: none
|
String |
getConditionOrigin()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getConditionQuantity()
Constraints: Not nullable, Precision: 5, Scale: 0
|
String |
getConditionQuantityISOUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getConditionQuantitySAPUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getConditionQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionRateValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
BigDecimal |
getConditionScaleBasisValue()
Constraints: Not nullable, Precision: 24, Scale: 9
|
String |
getConditionType()
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.
|
String |
getIsGroupCondition()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getPriceConditionDeterminationDte()
Constraints: Not nullable, Precision: 0
|
String |
getPricingProcedureCounter()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getPricingProcedureStep()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getPricingScaleBasis()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesOrder()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<SalesOrderSimulation> |
getSalesOrderIfPresent()
Retrieval of associated SalesOrderSimulation entity (one to one).
|
SalesOrderSimulation |
getSalesOrderOrFetch()
Retrieval of associated SalesOrderSimulation entity (one to one).
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<SalesOrderPrcgElmntSimln> |
getType() |
int |
hashCode() |
void |
setConditionAmount(BigDecimal conditionAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setConditionBaseValue(BigDecimal conditionBaseValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setConditionCalculationType(String conditionCalculationType)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionClass(String conditionClass)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionCurrency(String conditionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionInactiveReason(String conditionInactiveReason)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionIsForStatistics(Boolean conditionIsForStatistics)
Constraints: none
|
void |
setConditionIsManuallyChanged(Boolean conditionIsManuallyChanged)
Constraints: none
|
void |
setConditionOrigin(String conditionOrigin)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionQuantity(BigDecimal conditionQuantity)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setConditionQuantityISOUnit(String conditionQuantityISOUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionQuantitySAPUnit(String conditionQuantitySAPUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionQuantityUnit(String conditionQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionRateValue(BigDecimal conditionRateValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setConditionScaleBasisValue(BigDecimal conditionScaleBasisValue)
Constraints: Not nullable, Precision: 24, Scale: 9
|
void |
setConditionType(String conditionType)
Constraints: Not nullable, Maximum length: 4
|
void |
setIsGroupCondition(String isGroupCondition)
Constraints: Not nullable, Maximum length: 1
|
void |
setPriceConditionDeterminationDte(LocalDateTime priceConditionDeterminationDte)
Constraints: Not nullable, Precision: 0
|
void |
setPricingProcedureCounter(String pricingProcedureCounter)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setPricingProcedureStep(String pricingProcedureStep)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setPricingScaleBasis(String pricingScaleBasis)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesOrder(SalesOrderSimulation value)
Overwrites the associated SalesOrderSimulation entity for the loaded navigation property
to_SalesOrder.
|
void |
setSalesOrder(String salesOrder)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final SalesOrderPrcgElmntSimlnSelectable ALL_FIELDS
public static final SalesOrderPrcgElmntSimlnField<String> SALES_ORDER
public static final SalesOrderPrcgElmntSimlnField<String> PRICING_PROCEDURE_STEP
public static final SalesOrderPrcgElmntSimlnField<String> PRICING_PROCEDURE_COUNTER
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_TYPE
public static final SalesOrderPrcgElmntSimlnField<LocalDateTime> PRICE_CONDITION_DETERMINATION_DTE
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_CALCULATION_TYPE
public static final SalesOrderPrcgElmntSimlnField<BigDecimal> CONDITION_BASE_VALUE
public static final SalesOrderPrcgElmntSimlnField<BigDecimal> CONDITION_RATE_VALUE
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_CURRENCY
public static final SalesOrderPrcgElmntSimlnField<BigDecimal> CONDITION_QUANTITY
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_QUANTITY_UNIT
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_QUANTITY_SAP_UNIT
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_QUANTITY_ISO_UNIT
public static final SalesOrderPrcgElmntSimlnField<Boolean> CONDITION_IS_FOR_STATISTICS
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_ORIGIN
public static final SalesOrderPrcgElmntSimlnField<String> IS_GROUP_CONDITION
public static final SalesOrderPrcgElmntSimlnField<BigDecimal> CONDITION_AMOUNT
public static final SalesOrderPrcgElmntSimlnField<String> TRANSACTION_CURRENCY
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_INACTIVE_REASON
public static final SalesOrderPrcgElmntSimlnField<String> CONDITION_CLASS
public static final SalesOrderPrcgElmntSimlnField<String> PRICING_SCALE_BASIS
public static final SalesOrderPrcgElmntSimlnField<BigDecimal> CONDITION_SCALE_BASIS_VALUE
public static final SalesOrderPrcgElmntSimlnField<Boolean> CONDITION_IS_MANUALLY_CHANGED
public static final SalesOrderPrcgElmntSimlnOneToOneLink<SalesOrderSimulation> TO_SALES_ORDER
public SalesOrderPrcgElmntSimln()
public SalesOrderPrcgElmntSimln(@Nullable String salesOrder, @Nullable String pricingProcedureStep, @Nullable String pricingProcedureCounter, @Nullable String conditionType, @Nullable LocalDateTime priceConditionDeterminationDte, @Nullable String conditionCalculationType, @Nullable BigDecimal conditionBaseValue, @Nullable BigDecimal conditionRateValue, @Nullable String conditionCurrency, @Nullable BigDecimal conditionQuantity, @Nullable String conditionQuantityUnit, @Nullable String conditionQuantitySAPUnit, @Nullable String conditionQuantityISOUnit, @Nullable Boolean conditionIsForStatistics, @Nullable String conditionOrigin, @Nullable String isGroupCondition, @Nullable BigDecimal conditionAmount, @Nullable String transactionCurrency, @Nullable String conditionInactiveReason, @Nullable String conditionClass, @Nullable String pricingScaleBasis, @Nullable BigDecimal conditionScaleBasisValue, @Nullable Boolean conditionIsManuallyChanged, @Nullable SalesOrderSimulation toSalesOrder)
@Nonnull public Class<SalesOrderPrcgElmntSimln> getType()
getType
in class VdmObject<SalesOrderPrcgElmntSimln>
public void setSalesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
salesOrder
- Sales Orderpublic void setPricingProcedureStep(@Nullable String pricingProcedureStep)
Original property name from the Odata EDM: PricingProcedureStep
pricingProcedureStep
- Number that determines the sequence of the condition within a procedure.public void setPricingProcedureCounter(@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.
pricingProcedureCounter
- Access number of the conditions within a step in the pricing procedure.public void setConditionType(@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.
conditionType
- The key that uniquely identifies the condition.public void setPriceConditionDeterminationDte(@Nullable LocalDateTime priceConditionDeterminationDte)
Original property name from the Odata EDM: PriceConditionDeterminationDte
priceConditionDeterminationDte
- The priceConditionDeterminationDte to set.public void setConditionCalculationType(@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.
conditionCalculationType
- Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the
system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or
weight.public void setConditionBaseValue(@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.
conditionBaseValue
- Defines the value in a business document that the system uses together with the condition amount to
calculate the condition value for the price condition.public void setConditionRateValue(@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.
conditionRateValue
- Determines how the system calculates prices using a specific condition.public void setConditionCurrency(@Nullable String conditionCurrency)
Original property name from the Odata EDM: ConditionCurrency
conditionCurrency
- Currency key for amounts in the system.public void setConditionQuantity(@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.
conditionQuantity
- The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for
example, bottles).public void setConditionQuantityUnit(@Nullable String conditionQuantityUnit)
Original property name from the Odata EDM: ConditionQuantityUnit
conditionQuantityUnit
- Quantity unit, to which the condition amount or percentage refers.public void setConditionQuantitySAPUnit(@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).
conditionQuantitySAPUnit
- Unit of measure (SAP unit code) for the condition quantity.public void setConditionQuantityISOUnit(@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).
conditionQuantityISOUnit
- Unit of measure (ISO code) for the condition quantity.public void setConditionIsForStatistics(@Nullable Boolean conditionIsForStatistics)
Original property name from the Odata EDM: ConditionIsForStatistics
conditionIsForStatistics
- This indicator causes a surcharge or discount to be set in the document statistically (that is,
without altering the value).public void setConditionOrigin(@Nullable String conditionOrigin)
Original property name from the Odata EDM: ConditionOrigin
conditionOrigin
- Indicates where the condition originated (for example, whether you entered the condition manually or
whether the system determined it automatically).public void setIsGroupCondition(@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.
isGroupCondition
- Indicates whether the system calculates the scale base value or the condition value taking all related
items of the business document into account.public void setConditionAmount(@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.
conditionAmount
- The value, resulting from pricing, for a particular condition, total, or subtotal in a document.public void setTransactionCurrency(@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.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setConditionInactiveReason(@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
conditionInactiveReason
- Indicates if the condition is active.public void setConditionClass(@Nullable String conditionClass)
Original property name from the Odata EDM: ConditionClass
Allows standardized processing of individual condition classes within the system.
conditionClass
- Preliminary structuring of condition types, for example, in surcharges and discounts or prices.public void setPricingScaleBasis(@Nullable String pricingScaleBasis)
Original property name from the Odata EDM: PricingScaleBasis
pricingScaleBasis
- Determines how the system interprets a pricing scale in a condition. For example, the scale can be
based on quantity, weight, or volume.public void setConditionScaleBasisValue(@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.
conditionScaleBasisValue
- A value or quantity that the system uses to access a pricing scale to determine a scale level.public void setConditionIsManuallyChanged(@Nullable Boolean conditionIsManuallyChanged)
Original property name from the Odata EDM: ConditionIsManuallyChanged
conditionIsManuallyChanged
- If this flag is set, the condition has been manually or automatically changed or created (by entry in
the condition screen).protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<SalesOrderPrcgElmntSimln>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<SalesOrderPrcgElmntSimln>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SalesOrderPrcgElmntSimln>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SalesOrderPrcgElmntSimln>
@Nonnull public static <T> SalesOrderPrcgElmntSimlnField<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> SalesOrderPrcgElmntSimlnField<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<SalesOrderPrcgElmntSimln>
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<SalesOrderPrcgElmntSimln>
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<SalesOrderPrcgElmntSimln>
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<SalesOrderPrcgElmntSimln>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<SalesOrderPrcgElmntSimln>
@Nullable public SalesOrderSimulation fetchSalesOrder() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nullable public SalesOrderSimulation getSalesOrderOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SalesOrder of a queried SalesOrderPrcgElmntSimln is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<SalesOrderSimulation> getSalesOrderIfPresent()
If the navigation property for an entity SalesOrderPrcgElmntSimln has not been resolved yet, this method
will not query further information. Instead its Option
result state will be
empty
.
Option
with result state
empty
is returned.public void setSalesOrder(SalesOrderSimulation value)
value
- New SalesOrderSimulation entity.@Nonnull public static SalesOrderPrcgElmntSimln.SalesOrderPrcgElmntSimlnBuilder builder()
@Nullable public String getSalesOrder()
Original property name from the Odata EDM: SalesOrder
@Nullable public String getPricingProcedureStep()
Original property name from the Odata EDM: PricingProcedureStep
@Nullable public String getPricingProcedureCounter()
Original property name from the Odata EDM: PricingProcedureCounter
During automatic pricing, the system takes into account the sequence specified by the counter.
@Nullable public String getConditionType()
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.
@Nullable public LocalDateTime getPriceConditionDeterminationDte()
Original property name from the Odata EDM: PriceConditionDeterminationDte
@Nullable public String getConditionCalculationType()
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.
@Nullable public BigDecimal getConditionBaseValue()
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.
@Nullable public BigDecimal getConditionRateValue()
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.
@Nullable public String getConditionCurrency()
Original property name from the Odata EDM: ConditionCurrency
@Nullable public BigDecimal getConditionQuantity()
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.
@Nullable public String getConditionQuantityUnit()
Original property name from the Odata EDM: ConditionQuantityUnit
@Nullable public String getConditionQuantitySAPUnit()
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).
@Nullable public String getConditionQuantityISOUnit()
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).
@Nullable public Boolean getConditionIsForStatistics()
Original property name from the Odata EDM: ConditionIsForStatistics
@Nullable public String getConditionOrigin()
Original property name from the Odata EDM: ConditionOrigin
@Nullable public String getIsGroupCondition()
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.
@Nullable public BigDecimal getConditionAmount()
Original property name from the Odata EDM: ConditionAmount
This value is used as a total for the condition in the pricing procedure.
@Nullable public String getTransactionCurrency()
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.
@Nullable public String getConditionInactiveReason()
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
@Nullable public String getConditionClass()
Original property name from the Odata EDM: ConditionClass
Allows standardized processing of individual condition classes within the system.
@Nullable public String getPricingScaleBasis()
Original property name from the Odata EDM: PricingScaleBasis
@Nullable public BigDecimal getConditionScaleBasisValue()
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.
@Nullable public Boolean getConditionIsManuallyChanged()
Original property name from the Odata EDM: ConditionIsManuallyChanged
@Nonnull public String toString()
toString
in class VdmObject<SalesOrderPrcgElmntSimln>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<SalesOrderPrcgElmntSimln>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<SalesOrderPrcgElmntSimln>
public int hashCode()
hashCode
in class VdmObject<SalesOrderPrcgElmntSimln>
Copyright © 2021 SAP SE. All rights reserved.