public class PurContrItemCondition extends VdmEntity<PurContrItemCondition>
Original entity name from the Odata EDM: A_PurContrItemConditionType
Modifier and Type | Class and Description |
---|---|
static class |
PurContrItemCondition.PurContrItemConditionBuilder |
Modifier and Type | Field and Description |
---|---|
static PurContrItemConditionField<String> |
ADDITIONAL_VALUE_DAYS
Use with available fluent helpers to apply the AdditionalValueDays field to query operations.
|
static PurContrItemConditionSelectable |
ALL_FIELDS
Selector for all available fields of PurContrItemCondition.
|
static PurContrItemConditionField<String> |
BASE_UNIT
Use with available fluent helpers to apply the BaseUnit field to query operations.
|
static PurContrItemConditionField<String> |
CNDN_MAX_NUMBER_OF_SALES_ORDERS
Use with available fluent helpers to apply the CndnMaxNumberOfSalesOrders field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_ALTERNATIVE_CURRENCY
Use with available fluent helpers to apply the ConditionAlternativeCurrency field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_CALCULATION_TYPE
Use with available fluent helpers to apply the ConditionCalculationType field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_CLASSIFICATION
Use with available fluent helpers to apply the ConditionClassification field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_EXCLUSION
Use with available fluent helpers to apply the ConditionExclusion field to query operations.
|
static PurContrItemConditionField<Boolean> |
CONDITION_IS_DELETED
Use with available fluent helpers to apply the ConditionIsDeleted field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_LOWER_LIMIT
Use with available fluent helpers to apply the ConditionLowerLimit field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_QUANTITY
Use with available fluent helpers to apply the ConditionQuantity field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_QUANTITY_UNIT
Use with available fluent helpers to apply the ConditionQuantityUnit field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_RATE_VALUE
Use with available fluent helpers to apply the ConditionRateValue field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_RATE_VALUE_UNIT
Use with available fluent helpers to apply the ConditionRateValueUnit field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_RECORD
Use with available fluent helpers to apply the ConditionRecord field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_RELEASE_STATUS
Use with available fluent helpers to apply the ConditionReleaseStatus field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_SCALE_AMOUNT
Use with available fluent helpers to apply the ConditionScaleAmount field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_SCALE_AMOUNT_CURRENCY
Use with available fluent helpers to apply the ConditionScaleAmountCurrency field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_SCALE_QUANTITY
Use with available fluent helpers to apply the ConditionScaleQuantity field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_SCALE_QUANTITY_UNIT
Use with available fluent helpers to apply the ConditionScaleQuantityUnit field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_SEQUENTIAL_NUMBER
Use with available fluent helpers to apply the ConditionSequentialNumber field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_TEXT_ID
Use with available fluent helpers to apply the ConditionTextID field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_TO_BASE_QTY_DNMNTR
Use with available fluent helpers to apply the ConditionToBaseQtyDnmntr field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_TO_BASE_QTY_NMRTR
Use with available fluent helpers to apply the ConditionToBaseQtyNmrtr field to query operations.
|
static PurContrItemConditionField<String> |
CONDITION_TYPE
Use with available fluent helpers to apply the ConditionType field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
CONDITION_UPPER_LIMIT
Use with available fluent helpers to apply the ConditionUpperLimit field to query operations.
|
static PurContrItemConditionField<LocalDateTime> |
CONDITION_VALIDITY_END_DATE
Use with available fluent helpers to apply the ConditionValidityEndDate field to query operations.
|
static PurContrItemConditionField<LocalDateTime> |
CONDITION_VALIDITY_START_DATE
Use with available fluent helpers to apply the ConditionValidityStartDate field to query operations.
|
static PurContrItemConditionField<LocalDateTime> |
FIXED_VALUE_DATE
Use with available fluent helpers to apply the FixedValueDate field to query operations.
|
static PurContrItemConditionField<String> |
INCREMENTAL_SCALE
Use with available fluent helpers to apply the IncrementalScale field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
MAXIMUM_CONDITION_AMOUNT
Use with available fluent helpers to apply the MaximumConditionAmount field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
MAXIMUM_CONDITION_BASIS_VALUE
Use with available fluent helpers to apply the MaximumConditionBasisValue field to query operations.
|
static PurContrItemConditionField<BigDecimal> |
MINIMUM_CONDITION_BASIS_VALUE
Use with available fluent helpers to apply the MinimumConditionBasisValue field to query operations.
|
static PurContrItemConditionField<String> |
PAYMENT_TERMS
Use with available fluent helpers to apply the PaymentTerms field to query operations.
|
static PurContrItemConditionField<String> |
PRICING_SCALE_BASIS
Use with available fluent helpers to apply the PricingScaleBasis field to query operations.
|
static PurContrItemConditionField<String> |
PRICING_SCALE_LINE
Use with available fluent helpers to apply the PricingScaleLine field to query operations.
|
static PurContrItemConditionField<String> |
PRICING_SCALE_TYPE
Use with available fluent helpers to apply the PricingScaleType field to query operations.
|
static PurContrItemConditionField<String> |
PURCHASE_CONTRACT
Use with available fluent helpers to apply the PurchaseContract field to query operations.
|
static PurContrItemConditionField<String> |
PURCHASE_CONTRACT_ITEM
Use with available fluent helpers to apply the PurchaseContractItem field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
PurContrItemCondition() |
PurContrItemCondition(String purchaseContract,
String purchaseContractItem,
LocalDateTime conditionValidityEndDate,
String conditionType,
String conditionRecord,
String conditionSequentialNumber,
LocalDateTime conditionValidityStartDate,
String conditionTextID,
String pricingScaleType,
String pricingScaleBasis,
BigDecimal conditionScaleQuantity,
String conditionScaleQuantityUnit,
BigDecimal conditionScaleAmount,
String conditionScaleAmountCurrency,
String conditionCalculationType,
BigDecimal conditionRateValue,
String conditionRateValueUnit,
BigDecimal conditionQuantity,
String conditionQuantityUnit,
BigDecimal conditionToBaseQtyNmrtr,
BigDecimal conditionToBaseQtyDnmntr,
String baseUnit,
BigDecimal conditionLowerLimit,
BigDecimal conditionUpperLimit,
String conditionAlternativeCurrency,
String conditionExclusion,
Boolean conditionIsDeleted,
String additionalValueDays,
LocalDateTime fixedValueDate,
String paymentTerms,
String cndnMaxNumberOfSalesOrders,
BigDecimal minimumConditionBasisValue,
BigDecimal maximumConditionBasisValue,
BigDecimal maximumConditionAmount,
String incrementalScale,
String pricingScaleLine,
String conditionReleaseStatus,
String conditionClassification) |
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 PurContrItemCondition.PurContrItemConditionBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> PurContrItemConditionField<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) |
String |
getAdditionalValueDays()
Constraints: Not nullable, Maximum length: 2
|
String |
getBaseUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getCndnMaxNumberOfSalesOrders()
Constraints: Not nullable, Maximum length: 2
|
String |
getConditionAlternativeCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getConditionCalculationType()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionClassification()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionExclusion()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getConditionIsDeleted()
Constraints: none
|
BigDecimal |
getConditionLowerLimit()
Constraints: Not nullable, Precision: 12, Scale: 3
|
BigDecimal |
getConditionQuantity()
Constraints: Not nullable, Precision: 5, Scale: 0
|
String |
getConditionQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionRateValue()
Constraints: Not nullable, Precision: 12, Scale: 3
|
String |
getConditionRateValueUnit()
Constraints: Not nullable, Maximum length: 5
|
String |
getConditionRecord()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getConditionReleaseStatus()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getConditionScaleAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getConditionScaleAmountCurrency()
Constraints: Not nullable, Maximum length: 5
|
BigDecimal |
getConditionScaleQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getConditionScaleQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getConditionSequentialNumber()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
String |
getConditionTextID()
Constraints: Not nullable, Maximum length: 10
|
BigDecimal |
getConditionToBaseQtyDnmntr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
BigDecimal |
getConditionToBaseQtyNmrtr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
String |
getConditionType()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getConditionUpperLimit()
Constraints: Not nullable, Precision: 12, Scale: 3
|
LocalDateTime |
getConditionValidityEndDate()
(Key Field) Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getConditionValidityStartDate()
Constraints: Not nullable, Precision: 0
|
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.
|
LocalDateTime |
getFixedValueDate()
Constraints: Not nullable, Precision: 0
|
String |
getIncrementalScale()
Constraints: Not nullable, Maximum length: 4
|
protected Map<String,Object> |
getKey() |
BigDecimal |
getMaximumConditionAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
BigDecimal |
getMaximumConditionBasisValue()
Constraints: Not nullable, Precision: 15, Scale: 3
|
BigDecimal |
getMinimumConditionBasisValue()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
String |
getPricingScaleBasis()
Constraints: Not nullable, Maximum length: 1
|
String |
getPricingScaleLine()
Constraints: Not nullable, Maximum length: 4
|
String |
getPricingScaleType()
Constraints: Not nullable, Maximum length: 1
|
String |
getPurchaseContract()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getPurchaseContractItem()
(Key Field) Constraints: Not nullable, Maximum length: 5
|
Class<PurContrItemCondition> |
getType() |
int |
hashCode() |
void |
setAdditionalValueDays(String additionalValueDays)
Constraints: Not nullable, Maximum length: 2
|
void |
setBaseUnit(String baseUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setCndnMaxNumberOfSalesOrders(String cndnMaxNumberOfSalesOrders)
Constraints: Not nullable, Maximum length: 2
|
void |
setConditionAlternativeCurrency(String conditionAlternativeCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionCalculationType(String conditionCalculationType)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionClassification(String conditionClassification)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionExclusion(String conditionExclusion)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionIsDeleted(Boolean conditionIsDeleted)
Constraints: none
|
void |
setConditionLowerLimit(BigDecimal conditionLowerLimit)
Constraints: Not nullable, Precision: 12, Scale: 3
|
void |
setConditionQuantity(BigDecimal conditionQuantity)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setConditionQuantityUnit(String conditionQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionRateValue(BigDecimal conditionRateValue)
Constraints: Not nullable, Precision: 12, Scale: 3
|
void |
setConditionRateValueUnit(String conditionRateValueUnit)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionRecord(String conditionRecord)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setConditionReleaseStatus(String conditionReleaseStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionScaleAmount(BigDecimal conditionScaleAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setConditionScaleAmountCurrency(String conditionScaleAmountCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionScaleQuantity(BigDecimal conditionScaleQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setConditionScaleQuantityUnit(String conditionScaleQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionSequentialNumber(String conditionSequentialNumber)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setConditionTextID(String conditionTextID)
Constraints: Not nullable, Maximum length: 10
|
void |
setConditionToBaseQtyDnmntr(BigDecimal conditionToBaseQtyDnmntr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setConditionToBaseQtyNmrtr(BigDecimal conditionToBaseQtyNmrtr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
void |
setConditionType(String conditionType)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setConditionUpperLimit(BigDecimal conditionUpperLimit)
Constraints: Not nullable, Precision: 12, Scale: 3
|
void |
setConditionValidityEndDate(LocalDateTime conditionValidityEndDate)
(Key Field) Constraints: Not nullable, Precision: 0
|
void |
setConditionValidityStartDate(LocalDateTime conditionValidityStartDate)
Constraints: Not nullable, Precision: 0
|
void |
setFixedValueDate(LocalDateTime fixedValueDate)
Constraints: Not nullable, Precision: 0
|
void |
setIncrementalScale(String incrementalScale)
Constraints: Not nullable, Maximum length: 4
|
void |
setMaximumConditionAmount(BigDecimal maximumConditionAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setMaximumConditionBasisValue(BigDecimal maximumConditionBasisValue)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setMinimumConditionBasisValue(BigDecimal minimumConditionBasisValue)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setPaymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setPricingScaleBasis(String pricingScaleBasis)
Constraints: Not nullable, Maximum length: 1
|
void |
setPricingScaleLine(String pricingScaleLine)
Constraints: Not nullable, Maximum length: 4
|
void |
setPricingScaleType(String pricingScaleType)
Constraints: Not nullable, Maximum length: 1
|
void |
setPurchaseContract(String purchaseContract)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setPurchaseContractItem(String purchaseContractItem)
(Key Field) Constraints: Not nullable, Maximum length: 5
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final PurContrItemConditionSelectable ALL_FIELDS
public static final PurContrItemConditionField<String> PURCHASE_CONTRACT
public static final PurContrItemConditionField<String> PURCHASE_CONTRACT_ITEM
public static final PurContrItemConditionField<LocalDateTime> CONDITION_VALIDITY_END_DATE
public static final PurContrItemConditionField<String> CONDITION_TYPE
public static final PurContrItemConditionField<String> CONDITION_RECORD
public static final PurContrItemConditionField<String> CONDITION_SEQUENTIAL_NUMBER
public static final PurContrItemConditionField<LocalDateTime> CONDITION_VALIDITY_START_DATE
public static final PurContrItemConditionField<String> CONDITION_TEXT_ID
public static final PurContrItemConditionField<String> PRICING_SCALE_TYPE
public static final PurContrItemConditionField<String> PRICING_SCALE_BASIS
public static final PurContrItemConditionField<BigDecimal> CONDITION_SCALE_QUANTITY
public static final PurContrItemConditionField<String> CONDITION_SCALE_QUANTITY_UNIT
public static final PurContrItemConditionField<BigDecimal> CONDITION_SCALE_AMOUNT
public static final PurContrItemConditionField<String> CONDITION_SCALE_AMOUNT_CURRENCY
public static final PurContrItemConditionField<String> CONDITION_CALCULATION_TYPE
public static final PurContrItemConditionField<BigDecimal> CONDITION_RATE_VALUE
public static final PurContrItemConditionField<String> CONDITION_RATE_VALUE_UNIT
public static final PurContrItemConditionField<BigDecimal> CONDITION_QUANTITY
public static final PurContrItemConditionField<String> CONDITION_QUANTITY_UNIT
public static final PurContrItemConditionField<BigDecimal> CONDITION_TO_BASE_QTY_NMRTR
public static final PurContrItemConditionField<BigDecimal> CONDITION_TO_BASE_QTY_DNMNTR
public static final PurContrItemConditionField<String> BASE_UNIT
public static final PurContrItemConditionField<BigDecimal> CONDITION_LOWER_LIMIT
public static final PurContrItemConditionField<BigDecimal> CONDITION_UPPER_LIMIT
public static final PurContrItemConditionField<String> CONDITION_ALTERNATIVE_CURRENCY
public static final PurContrItemConditionField<String> CONDITION_EXCLUSION
public static final PurContrItemConditionField<Boolean> CONDITION_IS_DELETED
public static final PurContrItemConditionField<String> ADDITIONAL_VALUE_DAYS
public static final PurContrItemConditionField<LocalDateTime> FIXED_VALUE_DATE
public static final PurContrItemConditionField<String> PAYMENT_TERMS
public static final PurContrItemConditionField<String> CNDN_MAX_NUMBER_OF_SALES_ORDERS
public static final PurContrItemConditionField<BigDecimal> MINIMUM_CONDITION_BASIS_VALUE
public static final PurContrItemConditionField<BigDecimal> MAXIMUM_CONDITION_BASIS_VALUE
public static final PurContrItemConditionField<BigDecimal> MAXIMUM_CONDITION_AMOUNT
public static final PurContrItemConditionField<String> INCREMENTAL_SCALE
public static final PurContrItemConditionField<String> PRICING_SCALE_LINE
public static final PurContrItemConditionField<String> CONDITION_RELEASE_STATUS
public static final PurContrItemConditionField<String> CONDITION_CLASSIFICATION
public PurContrItemCondition()
public PurContrItemCondition(@Nullable String purchaseContract, @Nullable String purchaseContractItem, @Nullable LocalDateTime conditionValidityEndDate, @Nullable String conditionType, @Nullable String conditionRecord, @Nullable String conditionSequentialNumber, @Nullable LocalDateTime conditionValidityStartDate, @Nullable String conditionTextID, @Nullable String pricingScaleType, @Nullable String pricingScaleBasis, @Nullable BigDecimal conditionScaleQuantity, @Nullable String conditionScaleQuantityUnit, @Nullable BigDecimal conditionScaleAmount, @Nullable String conditionScaleAmountCurrency, @Nullable String conditionCalculationType, @Nullable BigDecimal conditionRateValue, @Nullable String conditionRateValueUnit, @Nullable BigDecimal conditionQuantity, @Nullable String conditionQuantityUnit, @Nullable BigDecimal conditionToBaseQtyNmrtr, @Nullable BigDecimal conditionToBaseQtyDnmntr, @Nullable String baseUnit, @Nullable BigDecimal conditionLowerLimit, @Nullable BigDecimal conditionUpperLimit, @Nullable String conditionAlternativeCurrency, @Nullable String conditionExclusion, @Nullable Boolean conditionIsDeleted, @Nullable String additionalValueDays, @Nullable LocalDateTime fixedValueDate, @Nullable String paymentTerms, @Nullable String cndnMaxNumberOfSalesOrders, @Nullable BigDecimal minimumConditionBasisValue, @Nullable BigDecimal maximumConditionBasisValue, @Nullable BigDecimal maximumConditionAmount, @Nullable String incrementalScale, @Nullable String pricingScaleLine, @Nullable String conditionReleaseStatus, @Nullable String conditionClassification)
@Nonnull public Class<PurContrItemCondition> getType()
getType
in class VdmObject<PurContrItemCondition>
public void setPurchaseContract(@Nullable String purchaseContract)
Original property name from the Odata EDM: PurchaseContract
purchaseContract
- Alphanumeric key uniquely identifying the document.public void setPurchaseContractItem(@Nullable String purchaseContractItem)
Original property name from the Odata EDM: PurchaseContractItem
purchaseContractItem
- Specifies the number that uniquely identifies an item in .public void setConditionValidityEndDate(@Nullable LocalDateTime conditionValidityEndDate)
Original property name from the Odata EDM: ConditionValidityEndDate
conditionValidityEndDate
- The conditionValidityEndDate to set.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 setConditionRecord(@Nullable String conditionRecord)
Original property name from the Odata EDM: ConditionRecord
The system uses the condition record number to store and retrieve information during processing (pricing, for example).
conditionRecord
- Number that uniquely identifies a condition record.public void setConditionSequentialNumber(@Nullable String conditionSequentialNumber)
Original property name from the Odata EDM: ConditionSequentialNumber
If you have assigned a condition supplement to the condition, the system automatically assigns the number.
conditionSequentialNumber
- The sequential number that uniquely identifies the condition if a condition supplement exists.public void setConditionValidityStartDate(@Nullable LocalDateTime conditionValidityStartDate)
Original property name from the Odata EDM: ConditionValidityStartDate
conditionValidityStartDate
- The conditionValidityStartDate to set.public void setConditionTextID(@Nullable String conditionTextID)
Original property name from the Odata EDM: ConditionTextID
conditionTextID
- Number of textspublic void setPricingScaleType(@Nullable String pricingScaleType)
Original property name from the Odata EDM: PricingScaleType
From a certain quantity or value (base scale)Up to a certain quantity or value (to-scale)Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
pricingScaleType
- Indicator that controls the validity of the scale value or percentage: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 setConditionScaleQuantity(@Nullable BigDecimal conditionScaleQuantity)
Original property name from the Odata EDM: ConditionScaleQuantity
conditionScaleQuantity
- Scale quantity (for example, number of pieces) to which a scale refers.public void setConditionScaleQuantityUnit(@Nullable String conditionScaleQuantityUnit)
Original property name from the Odata EDM: ConditionScaleQuantityUnit
conditionScaleQuantityUnit
- Unit of measure to which the quantity scale refers.public void setConditionScaleAmount(@Nullable BigDecimal conditionScaleAmount)
Original property name from the Odata EDM: ConditionScaleAmount
conditionScaleAmount
- A value that is part of a pricing scale. The value is an amount in a particular currency.public void setConditionScaleAmountCurrency(@Nullable String conditionScaleAmountCurrency)
Original property name from the Odata EDM: ConditionScaleAmountCurrency
If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value. In the standard version of the SAP System, this field is only relevant in condition records for the following discounts:Price groupPrice group/Material pricing groupYou apply a price group discount to customers in a particular foreign country. When you create a condition record for this discount and enter values in the pricing scale, you can also enter the corresponding foreign currency. During pricing, the system then calculates discounts based on scale values in the foreign currency. The discount amount is then converted into the currency you are using in the sales document.After you enter a currency in this field and save the condition record, you cannot change the currency without deleting the record and creating it again.
conditionScaleAmountCurrency
- Specifies a currency for a pricing scale in a condition record.public void setConditionCalculationType(@Nullable String conditionCalculationType)
Original property name from the Odata EDM: ConditionCalculationType
A percentage value referring to an amount.An absolute amountAn amount referring to a quantity, weight, or volumeYou can set the calculation type when you configure a condition type. The selected value of the calculation type is used as the default when you create a new condition record for this condition type.Note: You can specify another calculation type for the same condition type in a new condition record, but you cannot change it afterwards. The value of the calculation type specified in the condition record finally determines how the value for this price condition is calculated during pricing.In general, the system calculates the condition value by multiplying the condition amount with the condition base value after the appropriate currency and quantity conversions. The following table shows which condition base value the system uses for a specific calculation type:Calculation Type Description Condition Base Value Dimension of Condition Base ValueA Percentage Amount CurrencyB Fixed Amount 1 CurrencyC Quantity Quantity of a Document Item or Group of Items UoM of QuantityD Gross Weight Gross Weight of a Document Item or Group of Items UoM of Gross WeightE Net Weight Net Weight of a Document Item or Group of Items UoM of Net WeightF Volume Volume of a Document Item or Group of Items UoM of VolumeG Formula For more information, see Special Calculation Logic for Calculation Type āGā (Formula)H Percentage (in Hundreds) Amount CurrencyI Percentage (Travel Costs) Amount CurrencyM Quantity - Monthly Price Quantity of a Document Item or Group of Items UoM of Quantity?N Quantity - Monthly Price Quantity of a Document Item or Group of Items UoM of Quantity?O Quantity - Daily Price Quantity of a Document Item or Group of Items UoM of Quantity?P Quantity - Weekly Price Quantity of a Document Item or Group of Items UoM of Quantity?Special Calculation Logic for Calculation Type āGā (Formula)If you set this value, during the standard pricing for this condition type, the system does not determine a condition base value nor a condition amount or condition value. When the system has executed the standard logic to determine the condition base value and the condition value, the fields are filled with random values.Note: You can use formulas in a pricing procedure without setting calculation type G for the condition type.Follow-up Activity for Calculation Type G (Formula):Formulas are represented as routines. You must use routines to ensure that the condition base value and the condition value are determined. Therefore, in the pricing procedures that contain the affected condition type, you must assign a routine for the condition base value and a routine for the condition value to this condition type. If the condition base value is of no importance or if both, the condition base value and the condition value, are determined within the routine of the condition value, you do not have to use a routine for the condition base value.Note: If you use the calculation type G, you are responsible for the calculation of the values in the pricing result.
conditionCalculationType
- A rule that specifies how pricing uses the condition amount and the condition base value to calculate
the condition value. The following are the main cases:public void setConditionRateValue(@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.
conditionRateValue
- The rate that determines how the system calculates pricing using this condition. Depending on the
condition type, the rate can be a fixed amount or a percentage. If the condition includes a pricing
scale, the rate displays the first line of the scale.public void setConditionRateValueUnit(@Nullable String conditionRateValueUnit)
Original property name from the Odata EDM: ConditionRateValueUnit
The following examples illustrate what you can do when using different condition types.If you create a condition that includes prices (for example, prices for a material), you enter the currency that applies to the condition (for example, "USD" for US dollars)If you are creating a condition based on percentage discounts or surcharges (for example, a customer-specific discount), you cannot enter a value in the Condition unit field. Instead, the system automatically enters a percent sign as the condition unit when you enter a value in the Condition Amount field.
conditionRateValueUnit
- The unit that determines whether the condition for a material is based on a percentage or on an amount
in a particular currency. The use of the condition unit depends on the condition type (for example,
whether the condition is a material price or a customer discount).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 refers.public void setConditionToBaseQtyNmrtr(@Nullable BigDecimal conditionToBaseQtyNmrtr)
Original property name from the Odata EDM: ConditionToBaseQtyNmrtr
Many material processing functions, such as creating production requirements, may require that sales units are converted into base units.You store a soft drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units, in this case, gallons.
conditionToBaseQtyNmrtr
- The numerator of the conversion factor that the system uses to convert condition units into base units
of measure.public void setConditionToBaseQtyDnmntr(@Nullable BigDecimal conditionToBaseQtyDnmntr)
Original property name from the Odata EDM: ConditionToBaseQtyDnmntr
Many material processing functions, such as the creation of production requirements, may require that sales units are converted into base units of measure.You produce a soft-drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units of measure, in this case, gallons.
conditionToBaseQtyDnmntr
- The denominator of the conversion factor that the system uses to convert condition units into base
units of measure.public void setBaseUnit(@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.
baseUnit
- Unit of measure in which stocks of the material are managed. The system converts all the quantities
you enter in other units of measure (alternative units of measure) to the base unit of measure.public void setConditionLowerLimit(@Nullable BigDecimal conditionLowerLimit)
Original property name from the Odata EDM: ConditionLowerLimit
When you maintain the scales in a condition record, the system checks whether the scale value falls below the lower limit.
conditionLowerLimit
- Indicates whether, during document processing, the system checks if manual changes fall short of the
lower limit allowed for the corresponding condition record.public void setConditionUpperLimit(@Nullable BigDecimal conditionUpperLimit)
Original property name from the Odata EDM: ConditionUpperLimit
When you maintain a condition record, the system checks automatically whether the scale value exceeds the upper limit.
conditionUpperLimit
- Indicates, during document processing, whether a manually entered price exceeds the upper limit
allowed for the corresponding condition record and/or the condition type.public void setConditionAlternativeCurrency(@Nullable String conditionAlternativeCurrency)
Original property name from the Odata EDM: ConditionAlternativeCurrency
conditionAlternativeCurrency
- Condition Currency (for Cumulation Fields)public void setConditionExclusion(@Nullable String conditionExclusion)
Original property name from the Odata EDM: ConditionExclusion
You can set this indicator in two ways:For a particular condition record (the field appears on the Details screen)For all records of a particular condition type (the field appears on the screen where you define the condition type)If you set the indicator to exclude conditions, there are several things to consider:The system will still take into account any condition supplements that are part of the condition record for the price (condition type PR00, for example)You can allow for exceptions where you want to include discounts in spite of the condition exclusion indicator (for a particular discount condition you can specify a requirement that applies the discount ONLY when the indicator is set)
conditionExclusion
- Indicates whether the system automatically excludes the discounts that are proposed during pricing.public void setConditionIsDeleted(@Nullable Boolean conditionIsDeleted)
Original property name from the Odata EDM: ConditionIsDeleted
conditionIsDeleted
- Indicates whether the condition is no longer taken into account during document processing. The
condition is deleted during the next reorganization run.public void setAdditionalValueDays(@Nullable String additionalValueDays)
Original property name from the Odata EDM: AdditionalValueDays
If you enter a value in this field, you cannot enter a date in the fixed value date field.
additionalValueDays
- The number of days between the billing date and the date on which the terms of payment for the sales
document become effective.public void setFixedValueDate(@Nullable LocalDateTime fixedValueDate)
Original property name from the Odata EDM: FixedValueDate
If you enter a date in this field, you cannot enter a value in the additional value days field.
fixedValueDate
- The date on which the terms of payment related to the sales document become effective.public void setPaymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
paymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setCndnMaxNumberOfSalesOrders(@Nullable String cndnMaxNumberOfSalesOrders)
Original property name from the Odata EDM: CndnMaxNumberOfSalesOrders
You introduce a new product for which you offer an introductory discount. The customer gets this discount only on the first two orders - the initial order and the first replenishment order. Thereafter, the discount is inactive. In this case, you enter '2' in this field.To see how many orders have already benefitted from a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
cndnMaxNumberOfSalesOrders
- Specifies - up to a maximum of three - the number of sales orders that can benefit from this condition
record.public void setMinimumConditionBasisValue(@Nullable BigDecimal minimumConditionBasisValue)
Original property name from the Odata EDM: MinimumConditionBasisValue
minimumConditionBasisValue
- Minimum condition base valuepublic void setMaximumConditionBasisValue(@Nullable BigDecimal maximumConditionBasisValue)
Original property name from the Odata EDM: MaximumConditionBasisValue
You use this field to specify a maximum cumulative quantity, weight, or volume for a condition record.You offer a customer a special discount on a certain product but want to limit this discount to a specified total number of cases. You enter the maximum number of cases in this field. As you process orders that use this condition record, the system updates the cumulative quantity. When the maximum quantity is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative condition base value for a particular condition record, you select Extras -> Cumulative values in the overview screen of the condition record.
maximumConditionBasisValue
- Specifies the maximum condition base value for this condition record.public void setMaximumConditionAmount(@Nullable BigDecimal maximumConditionAmount)
Original property name from the Odata EDM: MaximumConditionAmount
You use this field to limit the use of a particular condition record to a specified total value.You offer a customer a special discount on a certain product but want to limit this discount to a specified total amount. You enter the maximum amount (for example, 1000 USD) in this field. As you process orders that use this condition record, the system updates the cumulative value. When the maximum value is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative value for a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
maximumConditionAmount
- Specifies the maximum condition value for this condition record.public void setIncrementalScale(@Nullable String incrementalScale)
Original property name from the Odata EDM: IncrementalScale
incrementalScale
- Number of incremental scalepublic void setPricingScaleLine(@Nullable String pricingScaleLine)
Original property name from the Odata EDM: PricingScaleLine
pricingScaleLine
- Scale number for pricingpublic void setConditionReleaseStatus(@Nullable String conditionReleaseStatus)
Original property name from the Odata EDM: ConditionReleaseStatus
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status for conditions.
conditionReleaseStatus
- The release status controls in which scenarios the condition records are found.public void setConditionClassification(@Nullable String conditionClassification)
Original property name from the Odata EDM: ConditionClassification
conditionClassification
- The conditionClassification to set.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<PurContrItemCondition>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<PurContrItemCondition>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<PurContrItemCondition>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<PurContrItemCondition>
@Nonnull public static <T> PurContrItemConditionField<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> PurContrItemConditionField<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<PurContrItemCondition>
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<PurContrItemCondition>
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<PurContrItemCondition>
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<PurContrItemCondition>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull public static PurContrItemCondition.PurContrItemConditionBuilder builder()
@Nullable public String getPurchaseContract()
Original property name from the Odata EDM: PurchaseContract
@Nullable public String getPurchaseContractItem()
Original property name from the Odata EDM: PurchaseContractItem
@Nullable public LocalDateTime getConditionValidityEndDate()
Original property name from the Odata EDM: ConditionValidityEndDate
@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 String getConditionRecord()
Original property name from the Odata EDM: ConditionRecord
The system uses the condition record number to store and retrieve information during processing (pricing, for example).
@Nullable public String getConditionSequentialNumber()
Original property name from the Odata EDM: ConditionSequentialNumber
If you have assigned a condition supplement to the condition, the system automatically assigns the number.
@Nullable public LocalDateTime getConditionValidityStartDate()
Original property name from the Odata EDM: ConditionValidityStartDate
@Nullable public String getConditionTextID()
Original property name from the Odata EDM: ConditionTextID
@Nullable public String getPricingScaleType()
Original property name from the Odata EDM: PricingScaleType
From a certain quantity or value (base scale)Up to a certain quantity or value (to-scale)Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
@Nullable public String getPricingScaleBasis()
Original property name from the Odata EDM: PricingScaleBasis
@Nullable public BigDecimal getConditionScaleQuantity()
Original property name from the Odata EDM: ConditionScaleQuantity
@Nullable public String getConditionScaleQuantityUnit()
Original property name from the Odata EDM: ConditionScaleQuantityUnit
@Nullable public BigDecimal getConditionScaleAmount()
Original property name from the Odata EDM: ConditionScaleAmount
@Nullable public String getConditionScaleAmountCurrency()
Original property name from the Odata EDM: ConditionScaleAmountCurrency
If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value. In the standard version of the SAP System, this field is only relevant in condition records for the following discounts:Price groupPrice group/Material pricing groupYou apply a price group discount to customers in a particular foreign country. When you create a condition record for this discount and enter values in the pricing scale, you can also enter the corresponding foreign currency. During pricing, the system then calculates discounts based on scale values in the foreign currency. The discount amount is then converted into the currency you are using in the sales document.After you enter a currency in this field and save the condition record, you cannot change the currency without deleting the record and creating it again.
@Nullable public String getConditionCalculationType()
Original property name from the Odata EDM: ConditionCalculationType
A percentage value referring to an amount.An absolute amountAn amount referring to a quantity, weight, or volumeYou can set the calculation type when you configure a condition type. The selected value of the calculation type is used as the default when you create a new condition record for this condition type.Note: You can specify another calculation type for the same condition type in a new condition record, but you cannot change it afterwards. The value of the calculation type specified in the condition record finally determines how the value for this price condition is calculated during pricing.In general, the system calculates the condition value by multiplying the condition amount with the condition base value after the appropriate currency and quantity conversions. The following table shows which condition base value the system uses for a specific calculation type:Calculation Type Description Condition Base Value Dimension of Condition Base ValueA Percentage Amount CurrencyB Fixed Amount 1 CurrencyC Quantity Quantity of a Document Item or Group of Items UoM of QuantityD Gross Weight Gross Weight of a Document Item or Group of Items UoM of Gross WeightE Net Weight Net Weight of a Document Item or Group of Items UoM of Net WeightF Volume Volume of a Document Item or Group of Items UoM of VolumeG Formula For more information, see Special Calculation Logic for Calculation Type āGā (Formula)H Percentage (in Hundreds) Amount CurrencyI Percentage (Travel Costs) Amount CurrencyM Quantity - Monthly Price Quantity of a Document Item or Group of Items UoM of Quantity?N Quantity - Monthly Price Quantity of a Document Item or Group of Items UoM of Quantity?O Quantity - Daily Price Quantity of a Document Item or Group of Items UoM of Quantity?P Quantity - Weekly Price Quantity of a Document Item or Group of Items UoM of Quantity?Special Calculation Logic for Calculation Type āGā (Formula)If you set this value, during the standard pricing for this condition type, the system does not determine a condition base value nor a condition amount or condition value. When the system has executed the standard logic to determine the condition base value and the condition value, the fields are filled with random values.Note: You can use formulas in a pricing procedure without setting calculation type G for the condition type.Follow-up Activity for Calculation Type G (Formula):Formulas are represented as routines. You must use routines to ensure that the condition base value and the condition value are determined. Therefore, in the pricing procedures that contain the affected condition type, you must assign a routine for the condition base value and a routine for the condition value to this condition type. If the condition base value is of no importance or if both, the condition base value and the condition value, are determined within the routine of the condition value, you do not have to use a routine for the condition base value.Note: If you use the calculation type G, you are responsible for the calculation of the values in the pricing result.
@Nullable public BigDecimal getConditionRateValue()
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.
@Nullable public String getConditionRateValueUnit()
Original property name from the Odata EDM: ConditionRateValueUnit
The following examples illustrate what you can do when using different condition types.If you create a condition that includes prices (for example, prices for a material), you enter the currency that applies to the condition (for example, "USD" for US dollars)If you are creating a condition based on percentage discounts or surcharges (for example, a customer-specific discount), you cannot enter a value in the Condition unit field. Instead, the system automatically enters a percent sign as the condition unit when you enter a value in the Condition Amount field.
@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 BigDecimal getConditionToBaseQtyNmrtr()
Original property name from the Odata EDM: ConditionToBaseQtyNmrtr
Many material processing functions, such as creating production requirements, may require that sales units are converted into base units.You store a soft drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units, in this case, gallons.
@Nullable public BigDecimal getConditionToBaseQtyDnmntr()
Original property name from the Odata EDM: ConditionToBaseQtyDnmntr
Many material processing functions, such as the creation of production requirements, may require that sales units are converted into base units of measure.You produce a soft-drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units of measure, in this case, gallons.
@Nullable public String getBaseUnit()
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.
@Nullable public BigDecimal getConditionLowerLimit()
Original property name from the Odata EDM: ConditionLowerLimit
When you maintain the scales in a condition record, the system checks whether the scale value falls below the lower limit.
@Nullable public BigDecimal getConditionUpperLimit()
Original property name from the Odata EDM: ConditionUpperLimit
When you maintain a condition record, the system checks automatically whether the scale value exceeds the upper limit.
@Nullable public String getConditionAlternativeCurrency()
Original property name from the Odata EDM: ConditionAlternativeCurrency
@Nullable public String getConditionExclusion()
Original property name from the Odata EDM: ConditionExclusion
You can set this indicator in two ways:For a particular condition record (the field appears on the Details screen)For all records of a particular condition type (the field appears on the screen where you define the condition type)If you set the indicator to exclude conditions, there are several things to consider:The system will still take into account any condition supplements that are part of the condition record for the price (condition type PR00, for example)You can allow for exceptions where you want to include discounts in spite of the condition exclusion indicator (for a particular discount condition you can specify a requirement that applies the discount ONLY when the indicator is set)
@Nullable public Boolean getConditionIsDeleted()
Original property name from the Odata EDM: ConditionIsDeleted
@Nullable public String getAdditionalValueDays()
Original property name from the Odata EDM: AdditionalValueDays
If you enter a value in this field, you cannot enter a date in the fixed value date field.
@Nullable public LocalDateTime getFixedValueDate()
Original property name from the Odata EDM: FixedValueDate
If you enter a date in this field, you cannot enter a value in the additional value days field.
@Nullable public String getPaymentTerms()
Original property name from the Odata EDM: PaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
@Nullable public String getCndnMaxNumberOfSalesOrders()
Original property name from the Odata EDM: CndnMaxNumberOfSalesOrders
You introduce a new product for which you offer an introductory discount. The customer gets this discount only on the first two orders - the initial order and the first replenishment order. Thereafter, the discount is inactive. In this case, you enter '2' in this field.To see how many orders have already benefitted from a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
@Nullable public BigDecimal getMinimumConditionBasisValue()
Original property name from the Odata EDM: MinimumConditionBasisValue
@Nullable public BigDecimal getMaximumConditionBasisValue()
Original property name from the Odata EDM: MaximumConditionBasisValue
You use this field to specify a maximum cumulative quantity, weight, or volume for a condition record.You offer a customer a special discount on a certain product but want to limit this discount to a specified total number of cases. You enter the maximum number of cases in this field. As you process orders that use this condition record, the system updates the cumulative quantity. When the maximum quantity is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative condition base value for a particular condition record, you select Extras -> Cumulative values in the overview screen of the condition record.
@Nullable public BigDecimal getMaximumConditionAmount()
Original property name from the Odata EDM: MaximumConditionAmount
You use this field to limit the use of a particular condition record to a specified total value.You offer a customer a special discount on a certain product but want to limit this discount to a specified total amount. You enter the maximum amount (for example, 1000 USD) in this field. As you process orders that use this condition record, the system updates the cumulative value. When the maximum value is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative value for a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
@Nullable public String getIncrementalScale()
Original property name from the Odata EDM: IncrementalScale
@Nullable public String getPricingScaleLine()
Original property name from the Odata EDM: PricingScaleLine
@Nullable public String getConditionReleaseStatus()
Original property name from the Odata EDM: ConditionReleaseStatus
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status for conditions.
@Nullable public String getConditionClassification()
Original property name from the Odata EDM: ConditionClassification
@Nonnull public String toString()
toString
in class VdmObject<PurContrItemCondition>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<PurContrItemCondition>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<PurContrItemCondition>
public int hashCode()
hashCode
in class VdmObject<PurContrItemCondition>
Copyright © 2021 SAP SE. All rights reserved.