public class PurOrdPricingElement extends VdmEntity<PurOrdPricingElement>
Modifier and Type | Class and Description |
---|---|
static class |
PurOrdPricingElement.PurOrdPricingElementBuilder |
Modifier and Type | Field and Description |
---|---|
static PurOrdPricingElementField<String> |
ACCESS_NUMBER_OF_ACCESS_SEQUENCE
Use with available fluent helpers to apply the AccessNumberOfAccessSequence field to query operations.
|
static PurOrdPricingElementSelectable |
ALL_FIELDS
Selector for all available fields of PurOrdPricingElement.
|
static PurOrdPricingElementField<Boolean> |
CNDN_IS_RELEVANT_FOR_INTCO_BILLING
Use with available fluent helpers to apply the CndnIsRelevantForIntcoBilling field to query operations.
|
static PurOrdPricingElementField<String> |
CNDN_IS_RELEVANT_FOR_INVOICE_LIST
Use with available fluent helpers to apply the CndnIsRelevantForInvoiceList field to query operations.
|
static PurOrdPricingElementField<Boolean> |
CNDN_IS_RELEVANT_FOR_LIMIT_VALUE
Use with available fluent helpers to apply the CndnIsRelevantForLimitValue field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_AMOUNT
Use with available fluent helpers to apply the ConditionAmount field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_APPLICATION
Use with available fluent helpers to apply the ConditionApplication field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_BASE_VALUE
Use with available fluent helpers to apply the ConditionBaseValue field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_CALCULATION_TYPE
Use with available fluent helpers to apply the ConditionCalculationType field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_CATEGORY
Use with available fluent helpers to apply the ConditionCategory field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_CLASS
Use with available fluent helpers to apply the ConditionClass field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_CONTROL
Use with available fluent helpers to apply the ConditionControl field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_CURRENCY
Use with available fluent helpers to apply the ConditionCurrency field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_INACTIVE_REASON
Use with available fluent helpers to apply the ConditionInactiveReason field to query operations.
|
static PurOrdPricingElementField<Boolean> |
CONDITION_IS_FOR_CONFIGURATION
Use with available fluent helpers to apply the ConditionIsForConfiguration field to query operations.
|
static PurOrdPricingElementField<Boolean> |
CONDITION_IS_FOR_STATISTICS
Use with available fluent helpers to apply the ConditionIsForStatistics field to query operations.
|
static PurOrdPricingElementField<Boolean> |
CONDITION_IS_MANUALLY_CHANGED
Use with available fluent helpers to apply the ConditionIsManuallyChanged field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_ORIGIN
Use with available fluent helpers to apply the ConditionOrigin field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_QUANTITY
Use with available fluent helpers to apply the ConditionQuantity field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_QUANTITY_UNIT
Use with available fluent helpers to apply the ConditionQuantityUnit field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_RATE_VALUE
Use with available fluent helpers to apply the ConditionRateValue field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_RECORD
Use with available fluent helpers to apply the ConditionRecord field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_SCALE_BASIS_CURRENCY
Use with available fluent helpers to apply the ConditionScaleBasisCurrency field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_SCALE_BASIS_UNIT
Use with available fluent helpers to apply the ConditionScaleBasisUnit field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_SCALE_BASIS_VALUE
Use with available fluent helpers to apply the ConditionScaleBasisValue field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_SEQUENTIAL_NUMBER
Use with available fluent helpers to apply the ConditionSequentialNumber field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_TO_BASE_QTY_DNMNTR
Use with available fluent helpers to apply the ConditionToBaseQtyDnmntr field to query operations.
|
static PurOrdPricingElementField<BigDecimal> |
CONDITION_TO_BASE_QTY_NMRTR
Use with available fluent helpers to apply the ConditionToBaseQtyNmrtr field to query operations.
|
static PurOrdPricingElementField<String> |
CONDITION_TYPE
Use with available fluent helpers to apply the ConditionType field to query operations.
|
static PurOrdPricingElementField<Double> |
FACTOR_FOR_CONDITION_BASIS_VALUE
Use with available fluent helpers to apply the FactorForConditionBasisValue field to query operations.
|
static PurOrdPricingElementField<String> |
IS_GROUP_CONDITION
Use with available fluent helpers to apply the IsGroupCondition field to query operations.
|
static PurOrdPricingElementField<Boolean> |
IS_RELEVANT_FOR_ACCRUAL
Use with available fluent helpers to apply the IsRelevantForAccrual field to query operations.
|
static PurOrdPricingElementField<String> |
PRICE_DETN_EXCHANGE_RATE
Use with available fluent helpers to apply the PriceDetnExchangeRate field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_DATE_TIME
Use with available fluent helpers to apply the PricingDateTime field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_DOCUMENT
Use with available fluent helpers to apply the PricingDocument field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_DOCUMENT_ITEM
Use with available fluent helpers to apply the PricingDocumentItem field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_PROCEDURE_COUNTER
Use with available fluent helpers to apply the PricingProcedureCounter field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_PROCEDURE_STEP
Use with available fluent helpers to apply the PricingProcedureStep field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_SCALE_BASIS
Use with available fluent helpers to apply the PricingScaleBasis field to query operations.
|
static PurOrdPricingElementField<String> |
PRICING_SCALE_TYPE
Use with available fluent helpers to apply the PricingScaleType field to query operations.
|
static PurOrdPricingElementField<String> |
PURCHASE_ORDER
Use with available fluent helpers to apply the PurchaseOrder field to query operations.
|
static PurOrdPricingElementField<String> |
PURCHASE_ORDER_ITEM
Use with available fluent helpers to apply the PurchaseOrderItem field to query operations.
|
Constructor and Description |
---|
PurOrdPricingElement() |
PurOrdPricingElement(String purchaseOrder,
String purchaseOrderItem,
String pricingDocument,
String pricingDocumentItem,
String pricingProcedureStep,
String pricingProcedureCounter,
String conditionType,
BigDecimal conditionRateValue,
String conditionCurrency,
String priceDetnExchangeRate,
BigDecimal conditionAmount,
String conditionQuantityUnit,
BigDecimal conditionQuantity,
String conditionApplication,
String pricingDateTime,
String conditionCalculationType,
BigDecimal conditionBaseValue,
BigDecimal conditionToBaseQtyNmrtr,
BigDecimal conditionToBaseQtyDnmntr,
String conditionCategory,
Boolean conditionIsForStatistics,
String pricingScaleType,
Boolean isRelevantForAccrual,
String cndnIsRelevantForInvoiceList,
String conditionOrigin,
String isGroupCondition,
Boolean cndnIsRelevantForLimitValue,
String conditionSequentialNumber,
String conditionControl,
String conditionInactiveReason,
String conditionClass,
Double factorForConditionBasisValue,
String pricingScaleBasis,
BigDecimal conditionScaleBasisValue,
String conditionScaleBasisCurrency,
String conditionScaleBasisUnit,
Boolean cndnIsRelevantForIntcoBilling,
Boolean conditionIsForConfiguration,
Boolean conditionIsManuallyChanged,
String conditionRecord,
String accessNumberOfAccessSequence,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static PurOrdPricingElement.PurOrdPricingElementBuilder |
builder() |
boolean |
equals(Object o) |
static <T> PurOrdPricingElementField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAccessNumberOfAccessSequence()
Constraints: Not nullable, Maximum length: 3
|
Boolean |
getCndnIsRelevantForIntcoBilling()
Constraints: none
|
String |
getCndnIsRelevantForInvoiceList()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getCndnIsRelevantForLimitValue()
Constraints: noneE.g.: you can make the use of a particular condition record in the document dependent on a specified total value.This total value can be specified in the condition record.
|
BigDecimal |
getConditionAmount()
Constraints: Not nullable, Precision: 16, Scale: 3 This value is used as a total for the condition in the pricing procedure.
|
String |
getConditionApplication()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getConditionBaseValue()
Constraints: Not nullable, Precision: 24, Scale: 9 The condition base value can be one of the following:QuantityWeightVolumeThe system multiplies the condition base value by the rate to produce the total amount for the condition.
|
String |
getConditionCalculationType()
Constraints: Not nullable, Maximum length: 3 The calculation type can be set when generating new condition records.
|
String |
getConditionCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getConditionClass()
Constraints: Not nullable, Maximum length: 1 Allows standardized processing of individual condition classes within the system.
|
String |
getConditionControl()
Constraints: Not nullable, Maximum length: 1 The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.
|
String |
getConditionCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getConditionInactiveReason()
Constraints: Not nullable, Maximum length: 1 A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
|
Boolean |
getConditionIsForConfiguration()
Constraints: none
|
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 You want to create a condition record for a material price of US$8 for 1 piece.
|
String |
getConditionQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionRateValue()
Constraints: Not nullable, Precision: 24, Scale: 9 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.
|
String |
getConditionRecord()
Constraints: Not nullable, Maximum length: 10 The system uses the condition record number to store and retrieve information during processing (pricing, for example).
|
String |
getConditionScaleBasisCurrency()
Constraints: Not nullable, Maximum length: 5 If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value.
|
String |
getConditionScaleBasisUnit()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getConditionScaleBasisValue()
Constraints: Not nullable, Precision: 24, Scale: 9 You create a pricing condition based on a simple quantity scale:Quantity Price per unit10 $12100 $111000 $10A sales order item for 150 units qualifies for the $11 price.
|
String |
getConditionSequentialNumber()
Constraints: Not nullable, Maximum length: 3 If you have assigned a condition supplement to the condition, the system automatically assigns the number.
|
BigDecimal |
getConditionToBaseQtyDnmntr()
Constraints: Not nullable, Precision: 10, Scale: 0 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.
|
BigDecimal |
getConditionToBaseQtyNmrtr()
Constraints: Not nullable, Precision: 10, Scale: 0 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.
|
String |
getConditionType()
Constraints: Not nullable, Maximum length: 4 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.
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
Double |
getFactorForConditionBasisValue()
Constraints: none
|
String |
getIsGroupCondition()
Constraints: Not nullable, Maximum length: 1 For a group condition to be effective, the items must belong to a group.
|
Boolean |
getIsRelevantForAccrual()
Constraints: noneIf you mark this indicator, the condition appears in the document as a statistical condition.
|
String |
getPriceDetnExchangeRate()
Constraints: Not nullable, Maximum length: 12
|
String |
getPricingDateTime()
Constraints: Not nullable, Maximum length: 14
|
String |
getPricingDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10 The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area.
|
String |
getPricingDocumentItem()
(Key Field) Constraints: Not nullable, Maximum length: 6 The condition item number corresponds to the number in the originating document.
|
String |
getPricingProcedureCounter()
(Key Field) Constraints: Not nullable, Maximum length: 3 During automatic pricing, the system takes into account the sequence specified by the counter.
|
String |
getPricingProcedureStep()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getPricingScaleBasis()
Constraints: Not nullable, Maximum length: 3
|
String |
getPricingScaleType()
Constraints: Not nullable, Maximum length: 1 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.
|
String |
getPurchaseOrder()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getPurchaseOrderItem()
(Key Field) Constraints: Not nullable, Maximum length: 5
|
Class<PurOrdPricingElement> |
getType() |
int |
hashCode() |
void |
setAccessNumberOfAccessSequence(String accessNumberOfAccessSequence)
Constraints: Not nullable, Maximum length: 3
|
void |
setCndnIsRelevantForIntcoBilling(Boolean cndnIsRelevantForIntcoBilling)
Constraints: none
|
void |
setCndnIsRelevantForInvoiceList(String cndnIsRelevantForInvoiceList)
Constraints: Not nullable, Maximum length: 1
|
void |
setCndnIsRelevantForLimitValue(Boolean cndnIsRelevantForLimitValue)
Constraints: noneE.g.: you can make the use of a particular condition record in the document dependent on a specified total value.This total value can be specified in the condition record.
|
void |
setConditionAmount(BigDecimal conditionAmount)
Constraints: Not nullable, Precision: 16, Scale: 3 This value is used as a total for the condition in the pricing procedure.
|
void |
setConditionApplication(String conditionApplication)
Constraints: Not nullable, Maximum length: 2
|
void |
setConditionBaseValue(BigDecimal conditionBaseValue)
Constraints: Not nullable, Precision: 24, Scale: 9 The condition base value can be one of the following:QuantityWeightVolumeThe system multiplies the condition base value by the rate to produce the total amount for the condition.
|
void |
setConditionCalculationType(String conditionCalculationType)
Constraints: Not nullable, Maximum length: 3 The calculation type can be set when generating new condition records.
|
void |
setConditionCategory(String conditionCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setConditionClass(String conditionClass)
Constraints: Not nullable, Maximum length: 1 Allows standardized processing of individual condition classes within the system.
|
void |
setConditionControl(String conditionControl)
Constraints: Not nullable, Maximum length: 1 The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.
|
void |
setConditionCurrency(String conditionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setConditionInactiveReason(String conditionInactiveReason)
Constraints: Not nullable, Maximum length: 1 A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
|
void |
setConditionIsForConfiguration(Boolean conditionIsForConfiguration)
Constraints: none
|
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 You want to create a condition record for a material price of US$8 for 1 piece.
|
void |
setConditionQuantityUnit(String conditionQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionRateValue(BigDecimal conditionRateValue)
Constraints: Not nullable, Precision: 24, Scale: 9 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.
|
void |
setConditionRecord(String conditionRecord)
Constraints: Not nullable, Maximum length: 10 The system uses the condition record number to store and retrieve information during processing (pricing, for example).
|
void |
setConditionScaleBasisCurrency(String conditionScaleBasisCurrency)
Constraints: Not nullable, Maximum length: 5 If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value.
|
void |
setConditionScaleBasisUnit(String conditionScaleBasisUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setConditionScaleBasisValue(BigDecimal conditionScaleBasisValue)
Constraints: Not nullable, Precision: 24, Scale: 9 You create a pricing condition based on a simple quantity scale:Quantity Price per unit10 $12100 $111000 $10A sales order item for 150 units qualifies for the $11 price.
|
void |
setConditionSequentialNumber(String conditionSequentialNumber)
Constraints: Not nullable, Maximum length: 3 If you have assigned a condition supplement to the condition, the system automatically assigns the number.
|
void |
setConditionToBaseQtyDnmntr(BigDecimal conditionToBaseQtyDnmntr)
Constraints: Not nullable, Precision: 10, Scale: 0 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.
|
void |
setConditionToBaseQtyNmrtr(BigDecimal conditionToBaseQtyNmrtr)
Constraints: Not nullable, Precision: 10, Scale: 0 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.
|
void |
setConditionType(String conditionType)
Constraints: Not nullable, Maximum length: 4 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.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setFactorForConditionBasisValue(Double factorForConditionBasisValue)
Constraints: none
|
void |
setIsGroupCondition(String isGroupCondition)
Constraints: Not nullable, Maximum length: 1 For a group condition to be effective, the items must belong to a group.
|
void |
setIsRelevantForAccrual(Boolean isRelevantForAccrual)
Constraints: noneIf you mark this indicator, the condition appears in the document as a statistical condition.
|
void |
setPriceDetnExchangeRate(String priceDetnExchangeRate)
Constraints: Not nullable, Maximum length: 12
|
void |
setPricingDateTime(String pricingDateTime)
Constraints: Not nullable, Maximum length: 14
|
void |
setPricingDocument(String pricingDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10 The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area.
|
void |
setPricingDocumentItem(String pricingDocumentItem)
(Key Field) Constraints: Not nullable, Maximum length: 6 The condition item number corresponds to the number in the originating document.
|
void |
setPricingProcedureCounter(String pricingProcedureCounter)
(Key Field) Constraints: Not nullable, Maximum length: 3 During automatic pricing, the system takes into account the sequence specified by the counter.
|
void |
setPricingProcedureStep(String pricingProcedureStep)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setPricingScaleBasis(String pricingScaleBasis)
Constraints: Not nullable, Maximum length: 3
|
void |
setPricingScaleType(String pricingScaleType)
Constraints: Not nullable, Maximum length: 1 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.
|
void |
setPurchaseOrder(String purchaseOrder)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setPurchaseOrderItem(String purchaseOrderItem)
(Key Field) Constraints: Not nullable, Maximum length: 5
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField
public static final PurOrdPricingElementSelectable ALL_FIELDS
public static final PurOrdPricingElementField<String> PURCHASE_ORDER
public static final PurOrdPricingElementField<String> PURCHASE_ORDER_ITEM
public static final PurOrdPricingElementField<String> PRICING_DOCUMENT
public static final PurOrdPricingElementField<String> PRICING_DOCUMENT_ITEM
public static final PurOrdPricingElementField<String> PRICING_PROCEDURE_STEP
public static final PurOrdPricingElementField<String> PRICING_PROCEDURE_COUNTER
public static final PurOrdPricingElementField<String> CONDITION_TYPE
public static final PurOrdPricingElementField<BigDecimal> CONDITION_RATE_VALUE
public static final PurOrdPricingElementField<String> CONDITION_CURRENCY
public static final PurOrdPricingElementField<String> PRICE_DETN_EXCHANGE_RATE
public static final PurOrdPricingElementField<BigDecimal> CONDITION_AMOUNT
public static final PurOrdPricingElementField<String> CONDITION_QUANTITY_UNIT
public static final PurOrdPricingElementField<BigDecimal> CONDITION_QUANTITY
public static final PurOrdPricingElementField<String> CONDITION_APPLICATION
public static final PurOrdPricingElementField<String> PRICING_DATE_TIME
public static final PurOrdPricingElementField<String> CONDITION_CALCULATION_TYPE
public static final PurOrdPricingElementField<BigDecimal> CONDITION_BASE_VALUE
public static final PurOrdPricingElementField<BigDecimal> CONDITION_TO_BASE_QTY_NMRTR
public static final PurOrdPricingElementField<BigDecimal> CONDITION_TO_BASE_QTY_DNMNTR
public static final PurOrdPricingElementField<String> CONDITION_CATEGORY
public static final PurOrdPricingElementField<Boolean> CONDITION_IS_FOR_STATISTICS
public static final PurOrdPricingElementField<String> PRICING_SCALE_TYPE
public static final PurOrdPricingElementField<Boolean> IS_RELEVANT_FOR_ACCRUAL
public static final PurOrdPricingElementField<String> CNDN_IS_RELEVANT_FOR_INVOICE_LIST
public static final PurOrdPricingElementField<String> CONDITION_ORIGIN
public static final PurOrdPricingElementField<String> IS_GROUP_CONDITION
public static final PurOrdPricingElementField<Boolean> CNDN_IS_RELEVANT_FOR_LIMIT_VALUE
public static final PurOrdPricingElementField<String> CONDITION_SEQUENTIAL_NUMBER
public static final PurOrdPricingElementField<String> CONDITION_CONTROL
public static final PurOrdPricingElementField<String> CONDITION_INACTIVE_REASON
public static final PurOrdPricingElementField<String> CONDITION_CLASS
public static final PurOrdPricingElementField<Double> FACTOR_FOR_CONDITION_BASIS_VALUE
public static final PurOrdPricingElementField<String> PRICING_SCALE_BASIS
public static final PurOrdPricingElementField<BigDecimal> CONDITION_SCALE_BASIS_VALUE
public static final PurOrdPricingElementField<String> CONDITION_SCALE_BASIS_CURRENCY
public static final PurOrdPricingElementField<String> CONDITION_SCALE_BASIS_UNIT
public static final PurOrdPricingElementField<Boolean> CNDN_IS_RELEVANT_FOR_INTCO_BILLING
public static final PurOrdPricingElementField<Boolean> CONDITION_IS_FOR_CONFIGURATION
public static final PurOrdPricingElementField<Boolean> CONDITION_IS_MANUALLY_CHANGED
public static final PurOrdPricingElementField<String> CONDITION_RECORD
public static final PurOrdPricingElementField<String> ACCESS_NUMBER_OF_ACCESS_SEQUENCE
public PurOrdPricingElement()
public PurOrdPricingElement(@Nullable String purchaseOrder, @Nullable String purchaseOrderItem, @Nullable String pricingDocument, @Nullable String pricingDocumentItem, @Nullable String pricingProcedureStep, @Nullable String pricingProcedureCounter, @Nullable String conditionType, @Nullable BigDecimal conditionRateValue, @Nullable String conditionCurrency, @Nullable String priceDetnExchangeRate, @Nullable BigDecimal conditionAmount, @Nullable String conditionQuantityUnit, @Nullable BigDecimal conditionQuantity, @Nullable String conditionApplication, @Nullable String pricingDateTime, @Nullable String conditionCalculationType, @Nullable BigDecimal conditionBaseValue, @Nullable BigDecimal conditionToBaseQtyNmrtr, @Nullable BigDecimal conditionToBaseQtyDnmntr, @Nullable String conditionCategory, @Nullable Boolean conditionIsForStatistics, @Nullable String pricingScaleType, @Nullable Boolean isRelevantForAccrual, @Nullable String cndnIsRelevantForInvoiceList, @Nullable String conditionOrigin, @Nullable String isGroupCondition, @Nullable Boolean cndnIsRelevantForLimitValue, @Nullable String conditionSequentialNumber, @Nullable String conditionControl, @Nullable String conditionInactiveReason, @Nullable String conditionClass, @Nullable Double factorForConditionBasisValue, @Nullable String pricingScaleBasis, @Nullable BigDecimal conditionScaleBasisValue, @Nullable String conditionScaleBasisCurrency, @Nullable String conditionScaleBasisUnit, @Nullable Boolean cndnIsRelevantForIntcoBilling, @Nullable Boolean conditionIsForConfiguration, @Nullable Boolean conditionIsManuallyChanged, @Nullable String conditionRecord, @Nullable String accessNumberOfAccessSequence, @Nullable ErpConfigContext erpConfigContext)
public Class<PurOrdPricingElement> getType()
getType
in class VdmObject<PurOrdPricingElement>
public static <T> PurOrdPricingElementField<T> field(String fieldName, Class<T> fieldType)
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.public static PurOrdPricingElement.PurOrdPricingElementBuilder builder()
@Nullable public String getPurchaseOrder()
@Nullable public String getPurchaseOrderItem()
@Nullable public String getPricingDocument()
The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area. The system uses the internal number to identify the different conditions.
@Nullable public String getPricingDocumentItem()
The condition item number corresponds to the number in the originating document. For example, if the condition applies to a sales order, the condition item number corresponds to the item number in the sales order.
@Nullable public String getPricingProcedureStep()
@Nullable public String getPricingProcedureCounter()
During automatic pricing, the system takes into account the sequence specified by the counter.
@Nullable public String getConditionType()
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 BigDecimal getConditionRateValue()
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 getConditionCurrency()
@Nullable public String getPriceDetnExchangeRate()
@Nullable public BigDecimal getConditionAmount()
This value is used as a total for the condition in the pricing procedure.
@Nullable public String getConditionQuantityUnit()
@Nullable public BigDecimal getConditionQuantity()
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 getConditionApplication()
@Nullable public String getPricingDateTime()
@Nullable public String getConditionCalculationType()
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()
The condition base value can be one of the following:QuantityWeightVolumeThe system multiplies the condition base value by the rate to produce the total amount for the condition. The total amount appears in the pricing procedure of a sales document.If, for example, you have a condition base value of 100 bottles and a rate of $10 per bottle, the amount for the pricing condition is $1000.
@Nullable public BigDecimal getConditionToBaseQtyNmrtr()
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()
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 String getConditionCategory()
@Nullable public Boolean getConditionIsForStatistics()
@Nullable public String getPricingScaleType()
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 Boolean getIsRelevantForAccrual()
If you mark this indicator, the condition appears in the document as a statistical condition.
@Nullable public String getCndnIsRelevantForInvoiceList()
@Nullable public String getConditionOrigin()
@Nullable public String getIsGroupCondition()
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 Boolean getCndnIsRelevantForLimitValue()
E.g.: you can make the use of a particular condition record in the document dependent on a specified total value.This total value can be specified in the condition record.
@Nullable public String getConditionSequentialNumber()
If you have assigned a condition supplement to the condition, the system automatically assigns the number.
@Nullable public String getConditionControl()
The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.
@Nullable public String getConditionInactiveReason()
A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
@Nullable public String getConditionClass()
Allows standardized processing of individual condition classes within the system.
@Nullable public Double getFactorForConditionBasisValue()
@Nullable public String getPricingScaleBasis()
@Nullable public BigDecimal getConditionScaleBasisValue()
You create a pricing condition based on a simple quantity scale:Quantity Price per unit10 $12100 $111000 $10A sales order item for 150 units qualifies for the $11 price. In this case, the scale base value that determines the price is 100.
@Nullable public String getConditionScaleBasisCurrency()
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 getConditionScaleBasisUnit()
@Nullable public Boolean getCndnIsRelevantForIntcoBilling()
@Nullable public Boolean getConditionIsForConfiguration()
@Nullable public Boolean getConditionIsManuallyChanged()
@Nullable public String getConditionRecord()
The system uses the condition record number to store and retrieve information during processing (pricing, for example).
@Nullable public String getAccessNumberOfAccessSequence()
@Nullable public ErpConfigContext getErpConfigContext()
public void setPurchaseOrder(@Nullable String purchaseOrder)
purchaseOrder
- public void setPurchaseOrderItem(@Nullable String purchaseOrderItem)
purchaseOrderItem
- public void setPricingDocument(@Nullable String pricingDocument)
The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area. The system uses the internal number to identify the different conditions.
pricingDocument
- public void setPricingDocumentItem(@Nullable String pricingDocumentItem)
The condition item number corresponds to the number in the originating document. For example, if the condition applies to a sales order, the condition item number corresponds to the item number in the sales order.
pricingDocumentItem
- public void setPricingProcedureStep(@Nullable String pricingProcedureStep)
pricingProcedureStep
- public void setPricingProcedureCounter(@Nullable String pricingProcedureCounter)
During automatic pricing, the system takes into account the sequence specified by the counter.
pricingProcedureCounter
- public void setConditionType(@Nullable String 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
- public void setConditionRateValue(@Nullable BigDecimal 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
- public void setConditionCurrency(@Nullable String conditionCurrency)
conditionCurrency
- public void setPriceDetnExchangeRate(@Nullable String priceDetnExchangeRate)
priceDetnExchangeRate
- public void setConditionAmount(@Nullable BigDecimal conditionAmount)
This value is used as a total for the condition in the pricing procedure.
conditionAmount
- public void setConditionQuantityUnit(@Nullable String conditionQuantityUnit)
conditionQuantityUnit
- public void setConditionQuantity(@Nullable BigDecimal 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
- public void setConditionApplication(@Nullable String conditionApplication)
conditionApplication
- public void setPricingDateTime(@Nullable String pricingDateTime)
pricingDateTime
- public void setConditionCalculationType(@Nullable String 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
- public void setConditionBaseValue(@Nullable BigDecimal conditionBaseValue)
The condition base value can be one of the following:QuantityWeightVolumeThe system multiplies the condition base value by the rate to produce the total amount for the condition. The total amount appears in the pricing procedure of a sales document.If, for example, you have a condition base value of 100 bottles and a rate of $10 per bottle, the amount for the pricing condition is $1000.
conditionBaseValue
- public void setConditionToBaseQtyNmrtr(@Nullable BigDecimal 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
- public void setConditionToBaseQtyDnmntr(@Nullable BigDecimal conditionToBaseQtyDnmntr)
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.
conditionToBaseQtyDnmntr
- public void setConditionCategory(@Nullable String conditionCategory)
conditionCategory
- public void setConditionIsForStatistics(@Nullable Boolean conditionIsForStatistics)
conditionIsForStatistics
- public void setPricingScaleType(@Nullable String 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
- public void setIsRelevantForAccrual(@Nullable Boolean isRelevantForAccrual)
If you mark this indicator, the condition appears in the document as a statistical condition.
isRelevantForAccrual
- public void setCndnIsRelevantForInvoiceList(@Nullable String cndnIsRelevantForInvoiceList)
cndnIsRelevantForInvoiceList
- public void setConditionOrigin(@Nullable String conditionOrigin)
conditionOrigin
- public void setIsGroupCondition(@Nullable String 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
- public void setCndnIsRelevantForLimitValue(@Nullable Boolean cndnIsRelevantForLimitValue)
E.g.: you can make the use of a particular condition record in the document dependent on a specified total value.This total value can be specified in the condition record.
cndnIsRelevantForLimitValue
- public void setConditionSequentialNumber(@Nullable String conditionSequentialNumber)
If you have assigned a condition supplement to the condition, the system automatically assigns the number.
conditionSequentialNumber
- public void setConditionControl(@Nullable String conditionControl)
The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.
conditionControl
- public void setConditionInactiveReason(@Nullable String conditionInactiveReason)
A condition can be inactive due to the following reasons:Condition is excludedSubsequent price deactivates conditionFormula deactivates conditionError during pricing
conditionInactiveReason
- public void setConditionClass(@Nullable String conditionClass)
Allows standardized processing of individual condition classes within the system.
conditionClass
- public void setFactorForConditionBasisValue(@Nullable Double factorForConditionBasisValue)
factorForConditionBasisValue
- public void setPricingScaleBasis(@Nullable String pricingScaleBasis)
pricingScaleBasis
- public void setConditionScaleBasisValue(@Nullable BigDecimal conditionScaleBasisValue)
You create a pricing condition based on a simple quantity scale:Quantity Price per unit10 $12100 $111000 $10A sales order item for 150 units qualifies for the $11 price. In this case, the scale base value that determines the price is 100.
conditionScaleBasisValue
- public void setConditionScaleBasisCurrency(@Nullable String conditionScaleBasisCurrency)
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.
conditionScaleBasisCurrency
- public void setConditionScaleBasisUnit(@Nullable String conditionScaleBasisUnit)
conditionScaleBasisUnit
- public void setCndnIsRelevantForIntcoBilling(@Nullable Boolean cndnIsRelevantForIntcoBilling)
cndnIsRelevantForIntcoBilling
- public void setConditionIsForConfiguration(@Nullable Boolean conditionIsForConfiguration)
conditionIsForConfiguration
- public void setConditionIsManuallyChanged(@Nullable Boolean conditionIsManuallyChanged)
conditionIsManuallyChanged
- public void setConditionRecord(@Nullable String conditionRecord)
The system uses the condition record number to store and retrieve information during processing (pricing, for example).
conditionRecord
- public void setAccessNumberOfAccessSequence(@Nullable String accessNumberOfAccessSequence)
accessNumberOfAccessSequence
- public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext
- public String toString()
toString
in class VdmObject<PurOrdPricingElement>
public boolean equals(Object o)
equals
in class VdmObject<PurOrdPricingElement>
public int hashCode()
hashCode
in class VdmObject<PurOrdPricingElement>
Copyright © 2018 SAP SE. All rights reserved.